Revenue declarations: collection and arbitration

Every revenue declaration campaign looks the same. You open a window, you wait, you chase, you retype, you close a fortnight late — and then, when the supplier reports arrive, you discover that half the declarations do not match. The most visible automation, a web form replacing a spreadsheet sent by email, solves only a small part of that.

The five stages of a declaration campaign

Whether your members declare quarterly or annually, the campaign has the same skeleton, and each stage has its own failure mode. Naming them separately is what lets you tell which one is actually costing you time.

1. 1

   Opening the window

   The declared period, the deadline, the perimeter (which members, which suppliers, which product families) and the applicable scale vintage are all frozen at opening. A member who joined mid-period declares pro rata temporis: that is decided when the window opens, not when it closes.

2. 2

   Entry or import

   Two routes, never one. Online entry for the smaller members, file import for those who can produce a report out of their ERP. Accept the member's file format with a per-company column mapping that the system remembers, rather than imposing yours on sixty companies.

3. 3

   Checks at entry

   Plausibility against previous periods, totals that add up, unknown product families, unexplained negative amounts. A wrong figure caught at entry costs two minutes. The same figure caught in January costs two weeks.

4. 4

   Chasing

   Automatic, graduated, personalised. This is the stage that eats your permanent team's calendar and the one people forget to specify.

5. 5

   Closing

   The window shuts, declarations move to a frozen status, and any later change creates a new version rather than overwriting the old one. Without versioning you cannot explain a year-end statement six months later.

Data entry is the easy part

Effort naturally flows to the entry screen. It is visible, it demos well, and it is easy to specify. It does deliver: no more retyping, no more transcription errors, no more member-specific spreadsheet layouts. That is a genuine gain, and it is bounded — a few days per campaign for a group of sixty companies.

The time does not go there. It goes into two other places: chasing the members who have not declared, and investigating the gaps once the supplier figures arrive. In most groups those two together are worth several person-weeks a year. Automating entry alone wins the easy half of an afternoon and leaves the expensive part untouched — which is exactly why so many groups install a declaration portal and report, a year later, that January feels the same.

Chasing changes more than entry does

Manual chasing is thankless and politically awkward. A permanent staff member has to write, for the third time, to a member company that is also a shareholder of the group. So the email gets softened, then delayed, then not sent. What changes this is not a better email template: it is that the reminder stops coming from a person and starts coming from the system, on a published schedule, identically for everyone.

A chasing sequence that works is dull by design: a reminder ten days before the deadline, one three days before, one the day after, and an escalation to the company director a week later. Each message says exactly what is missing — which periods, which suppliers — and links straight to a pre-filled form. Behind it, a completeness dashboard the permanent team can read at a glance, and that some groups show to the board.

The side effect is the one that matters: the in-window declaration rate rises, and the close stops slipping. It is the only part of this project the permanent team feels every single day.

Arbitration: reconciling declared and invoiced

Here is the real subject. The revenue a member declares and the revenue a supplier reports having invoiced them never match exactly, and they do not have to. They are produced by two different accounting systems, with two different definitions of the period, the assessment base and the perimeter. The job is not to reach equality. It is to know, for each gap, which family it belongs to and who has to act on it.

That assumes you have the invoiced figure at all. It is the first obstacle, and it is contractual before it is technical: the supplier report has to be written into the approval agreement — frequency, format, level of detail, deadline — or you will receive an annual PDF carrying a single total, against which no reconciliation is possible. A flat file per supplier and per period, broken down by invoiced company and by product family, dropped onto a dedicated space rather than emailed, is entirely sufficient. The better-organised suppliers already produce one for other networks; the rest need to be asked formally, once, when the approval addendum comes up for renewal.

Investigating gaps without losing a month to it

Three levers make the difference between a week of arbitration and a month of it.

Materiality first. Only investigate gaps above both a percentage threshold and a euro threshold — with one non-negotiable exception: any gap that would move a member across a bracket threshold gets investigated whatever its size. On a tiered scale, a four-thousand-euro gap sitting on a threshold can be worth twenty-five thousand euros of rebate, and a flat percentage filter will silently drop it.

Ownership second. Every gap has exactly one owner — the member, the supplier, or the permanent team — a status and a due date. Without that, the gap queue reverts to a mailbox within a fortnight, and you have rebuilt the process you were trying to replace.

Traceability third. Each arbitration is recorded with its reason and its author, and it becomes a candidate rule. The second campaign has to be shorter than the first, and it only will be if the recurring gaps are classified automatically the next time round. A reconciliation tool that does not learn from last quarter's decisions is a reporting tool.

What stays human is the decision itself. You can automate detection, classification, assembling the case file — the two lines side by side, the history, the supporting document — and chasing whichever party owes an answer. You cannot automate the arbitration, and any vendor claiming otherwise has never looked at a year-end credit note.

A reconciliation is only as good as the reference data

You cannot compare two figures without being certain they describe the same company. A supplier entered three times, a subsidiary not linked to its parent, a product family renamed with no effective date: each of these generates gaps that are not gaps, and the team spends the campaign investigating noise. Worse, it erodes trust in the tool — after two campaigns of false positives, people go back to the spreadsheet.

• A single company reference, keyed on the parent registration number, holding establishments and dated parent-subsidiary links. A company that changes its trading name keeps its identifier — that is what keeps the history comparable.
• A deduplicated supplier reference, with invoicing entities attached to the approved contracting entity.
• A versioned product family nomenclature with effective dates, and an explicit mapping to each supplier's own nomenclature.
• An approval agreement that states in writing what enters the assessment base: excluding or including VAT, gross or net of credit notes, which families, which companies.
• One single attachment date, enforceable on both sides — the invoice date, in almost every case.

The measure of a declaration system is not the online entry rate, nor the number of forms sent. It is the number of days between the window closing and the moment every member's assessment base is settled without reservation. As long as that is counted in weeks, arbitration is still being done by hand — and that, not data entry, is where the month you are trying to recover has been hiding.