Supplier turnover declarations: collect, check and validate

A year-end rebate is only as right as the turnover it is calculated on. The method that works: each period, the supplier declares its cumulative turnover since 1 January, split by product family when the agreement requires it; the purchaser checks the variances before validating, gives a reason for every refusal and keeps a record of every figure. Here is how to organise the collection, which checks to apply and how to avoid year-end disputes.

Why turnover declarations drive the rebate

A rebate is computed on a base: the turnover achieved with the supplier over the year. In most relationships, that base comes from the supplier’s declaration, which the purchaser reconciles with its own purchase records. A declaration error therefore flows straight into the amount: with a whole-rate scale, an error of a few thousand euros near a bound can even change the tier reached and double or halve the rebate.

Collecting once a year, at year end, puts every problem at the worst possible moment: variances found too late, chasing, a negotiation on disputed figures. Collecting regularly during the year spreads the work and lets you track the distance to the next tier.

Periods and cumulative figures: organising the collection

The year is split into contiguous periods: twelve months, four quarters, two halves or any other split. Each period has an entry window, when the supplier declares, and a validation window, when the purchaser checks.

Each period, the supplier declares its cumulative turnover since 1 January, not the turnover of that period alone. This has three advantages: a correction (a credit note, a missed invoice) is absorbed naturally in the next cumulative figure; the last period’s cumulative figure is directly the annual rebate base; and comparison with the prior year needs no additions.

On top of its declarations, the supplier can keep a landing up to date: its estimate of full-year turnover. It is not validated, but it feeds projections and accruals (see accruing year-end rebates).

Splitting turnover by product family

When the agreement includes family scales, the supplier must split its turnover between the families and an “other” line for the rest. Two rules prevent inconsistencies:

• In intermediate periods, the families plus “other” must not exceed the declared total; some families can be left empty.
• In the last period, every family and “other” must be filled in and must add up exactly to the total: for example Outdoor €400,000, Tools €150,000 and other €700,000 for a total of €1,250,000.

The “other” line should be entered, not derived as a difference: entering it makes the supplier check its split, and a gap becomes visible instead of being silently absorbed.

Which checks should you run before validating?

Validating a declaration means accepting it as the basis of the calculation. Before you do, a few simple checks catch most errors. None proves an error on its own: they are signals that justify a closer look or a question.

Validate, refuse or ask a question

Each declaration follows a simple cycle that both parties see the same way:

1. To enter, then draft: the supplier can save a partial entry without submitting it.
2. Submitted: the declaration awaits the purchaser’s check. The supplier can still replace it until it is validated.
3. Validated: the figure is frozen and will be used in the calculation. Reopening it should stay exceptional, reserved to a manager, with a reason.
4. Refused: a refusal always comes with a reason. The supplier corrects and resubmits; sending back exactly the same figure without explanation makes no sense and should be blocked.

Between validating and refusing there is often a third way: asking the supplier a question, with the declaration staying submitted until it answers. A well-phrased question (“the P3 cumulative figure is lower than P2’s, could you confirm it?”) settles most variances without conflict. Declarations without any signal can be validated in bulk.

Onboarding suppliers at the start of the year

The quality of declarations is decided before the first period. A few simple steps prevent most errors:

• One named contact per supplier, invited personally, who receives the reminders and answers questions.
• An explanation of cumulative figures: confusing period turnover with cumulative turnover is the most frequent first-year error.
• The full calendar of entry windows, shared as soon as the agreement is signed.
• The list of families and the rule for the “other” line, so the last period’s split comes as no surprise.
• A file template for suppliers who prefer to prepare their figures in a spreadsheet, rather than a free format to be retyped.
• The supplier’s language: a French supplier declares more accurately in a French interface with French messages, and an international one in English.

Keep a record of every figure

At year end, the question is not just “what is the figure?” but “who entered it, when, who validated it, and what changed?”. An audit log that records every action, its author, the value before and after, and the reason for a refusal or a reopening turns a discussion from memory into a check of facts. It is also what an auditor or internal control will ask for.

Excel, email or a declaration platform?

The most common setup, a spreadsheet emailed to each supplier and consolidated by hand, quickly hits its limits: multiple versions, chasing, broken formulas, no record of validations. We compare the approaches in managing rebates in Excel vs dedicated software.

In Palier, each supplier declares online, in a grid per period with the entry windows, the family split and its landing, or imports its own Excel file (the template it exports from Palier) in two steps: a cell-by-cell preview, then confirmation. The supplier remains the single source of its figure: the purchaser neither enters nor imports on its behalf. The purchaser validates from a dedicated queue, refuses with a reason, validates clean declarations in bulk, and every action goes into the audit log. See the features.

What the AI assistant changes

Palier’s assistant first computes the checks in the table above, deterministically, without AI. It then reads those signals, the supplier’s history and past decisions to recommend an action: validate, ask a question or refuse, with a rationale grounded in the numbers and a draft message in English and French. The purchaser approves in one click, edits or dismisses the recommendation: the assistant never validates a figure itself. Discover the AI assistant.

Key takeaways