Automated reporting for a buying group: figures you can defend
A buying group spends a remarkable amount of time rebuilding the same statements: the managing director's dashboard, the per-supplier summaries before annual negotiation, member statements, the board pack. Automating them saves days — provided the data underneath is consolidated and dated.
60+
member companies whose declarations feed the statements of a platform we delivered
~50
approved suppliers: the order of magnitude of a consolidation scope at this scale
Fixed price
scope and price committed, on migrated statements as well as new ones
In most member networks we meet, nobody can say how many hours a month go into producing statements. The figure is invisible because it is scattered: two hours here for a pivot table, half a day there to prepare a supplier meeting, three days in January for the board pack. Added up, it is a part-time job — and precisely what automated reporting removes, on one condition.
The statements a buying group actually produces
Before talking about tooling, name the statements. There are few of them, they recur constantly, and their audiences do not have the same requirements: the same revenue figure plays a different role depending on whether it feeds an internal decision or an invoice.
The managing director's dashboard
Revenue by supplier and product family, member declaration rates, variance against budget, rebates estimated for the current year. Read weekly, it decides where to apply pressure: a steering instrument, never a contractual record.
Per-supplier pack for annual negotiation
Volumes consolidated over three financial years, growth, the group's relative weight in the supplier's portfolio, rebates already paid, logistics terms applied. This is the document taken into the meeting, and it has to be right line by line.
Per-member statement
Declarations submitted and missing, revenue by supplier, rebates computed and paid, the share retained centrally. Every member checks it against their own accounts: any unexplained gap turns into a phone call.
Board pack
Full-year aggregates, comparisons with the previous year, movement in the number of member companies and approved suppliers. Produced three or four times a year, it must stay readable years later in exactly the version presented.
Accounting export
Rebate entries, membership fee invoicing, inter-company recharges. Not a document to read but a file destined for another system: its format, its timestamp and the fact that it cannot be replayed twice matter more than its layout.
Automated reporting is only worth its source data
This is the point most reporting projects deal with last, and the one that decides their fate. An automated statement creates no information: it exposes what the database already holds, faster, more often, to more people. If the quarter's revenue declarations are not all in, if two suppliers are recorded twice, if a member who left in June is still active in the reference data, automation corrects none of it.
The practical consequence is straightforward: every statement shows its own basis. Declarations expected and received, date of the last consolidation, scope applied, exclusions made. A statement without those markers cannot be defended in a meeting, and a member will contest it with good reason.
Steering figures and contractual figures
This distinction shapes the whole design. Both figures come from the same tables, but they obey different rules and must never sit side by side on the same page as if they were interchangeable.
| Steering figure | Contractual figure | |
|---|---|---|
| Purpose | Deciding, arbitrating, preparing a meeting | Invoicing, paying a rebate, closing a financial year |
| Expected freshness | As recent as possible, even if incomplete | As at closing, frozen on a known date |
| Error tolerance | An order of magnitude is enough, gaps correct themselves | None: the amount is enforceable against a third party |
| Mandatory markers | Extraction date, declaration completeness rate | Scope, scale applied, lock date, author of any adjustment |
| Later modification | The dashboard recomputes on every view | The issued statement never moves; a correction produces a new, dated statement |
Freshness, scheduled generation and archiving
Date every figure before publishing it
Each aggregate carries the timestamp of its last consolidation and the count of missing declarations. A figure without a date does not make it into a statement: this is the rule that costs the most discussion during scoping, and the one that prevents the most disputes afterwards.
Schedule the generation
Dashboard recomputed nightly, member statements produced the day after quarterly close, supplier packs generated on demand before a meeting. Scheduling removes the chore, not the review: a statement nobody opens before it goes out will eventually contain something absurd.
Distribute with an audit trail
Published to the member portal or sent by email, with a distribution log: who received which statement, when, in which version. Six months later, "what exactly did we send them?" has an answer.
Archive the statement as it was sent
A revenue statement sent to a supplier is a document, not a view. It is frozen as a PDF and as a data file, kept with its date, its scope and its scale version, and remains readable even after the source data is recomputed or corrected.
MEKANO is a Lyon-based development studio building the management applications of buying groups and member networks. Reporting almost always comes late in a programme, after revenue declarations and rebate calculation, for a mechanical reason: it is the only batch whose value depends entirely on the reliability of the batches before it.
What usually goes wrong
- Rebuilding an inherited pivot table exactly as it was, without asking who still reads it or which decision it triggers.
- Piling on indicators: a dashboard of forty figures is not consulted, it is printed.
- Sending statements to members before the declarations are reliable — the first wave of disputes costs more than the development.
- Publishing a steering figure with no freshness marker, then hearing it quoted in a board meeting as final.
- Forgetting the archive: the day a supplier produces the statement you sent last year, you need to be able to produce the same one.
- Confusing reporting with exploration: recurring statements should be automated, one-off analysis needs an export, not another screen.
Frequently asked questions
- Can reporting be automated without rebuilding the whole system?
- Yes, provided the data exists somewhere in a usable form. We regularly plug statements onto an existing system, including an old one, through a read database fed by imports. The limit is clear: if declarations still arrive by email and are rekeyed by hand, automating the reporting moves the work rather than removing it. In that case the declarations batch comes first.
- How quickly are the first statements delivered?
- We work in two-week sprints and usually deliver the two or three most time-consuming statements by the end of the first month — typically the dashboard and the per-supplier pack. The complete batch, including archiving and accounting exports, takes closer to six to ten weeks depending on how many sources have to be consolidated.
- Do we also need a business intelligence tool?
- Rarely, at this scale. A BI tool brings free-form exploration; what a buying group needs first is a dozen stable, dated, archived statements, which BI tools do not handle well. If your organisation genuinely needs ad hoc analysis, the right answer is to expose a clean read database and connect the tool of your choice to it, without duplicating the calculation rules.
- How do you guarantee a sent statement is still readable years later?
- By treating it as a document rather than a query. At generation the statement is frozen in two forms — a PDF to read, a data file to recompute from — and stored with its scope, its production date and the version of the scales applied. A later recomputation creates a new statement; it never replaces the previous one. That is what lets you answer a supplier waving a three-year-old document.
- Can statements differ from one member to another?
- Yes, and it is nearly always necessary. A regional head office, a large member company and a single-site member do not read the same aggregates. We model statement templates with per-profile variants and per-company visibility rights, rather than producing one universal statement that everyone then reworks on their own.
- Do we own the reporting code?
- Yes. The source code, the queries and the data schema are handed over, and reversibility is a contractual clause. On reporting it is decisive: a group's aggregation rules — scopes, exclusions, restatements — are an asset of the organisation, and locking them inside a supplier's tool amounts to renting your own memory.
Read next
Management applications for buying groups and member networks
The pillar: supplier approval, revenue declarations, rebate calculation, document management and a member portal, in one platform fitted to your rules.
Read moreSoftware for collecting members' revenue declarations
A buying group cannot compute a single rebate until it knows, period by period and supplier by supplier, what each member actually bought. That information arrives late, incomplete, in as many formats as there are members — and head office spends its quarters knocking it back into shape.
Read moreRebate and year-end bonus calculation software
Year-end rebates are the most scrutinised calculation a buying group runs: every member checks their figure, every supplier contests theirs, and the annual statement has to survive an auditor. We build the engine that runs your actual scales — not a package that asks you to bend your rules to fit it.
Read moreMember management software for a federation or a network
Not every network head office negotiates purchasing terms. A trade federation, a union, an employers' group or a retail brand maintains a directory, calls subscriptions, manages mandates and collects data from its members. The mechanics resemble those of a buying group, but the objects and the deadlines are not the same.
Read moreLet's talk about your situation
Thirty minutes, no commitment. You leave with a straight answer on feasibility, a budget order of magnitude and the next steps.
Book the call