Rebate 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.
60+
member companies whose rebates run on a platform we delivered
One statement
reproducible identically months later, from the same data
Fixed price
scope and price committed, historical migration included
In most buying groups we meet, the year-end rebate calculation lives in a workbook two people know how to open. It works — until one of them leaves, until a supplier asks for the breakdown of a three-year-old figure, or until a new product family fits none of the existing columns.
Why the spreadsheet always breaks eventually
A spreadsheet is not a bad calculation tool. It is a bad memory. It does not keep who entered what, why a line was corrected by hand in March, or which version of the scale applied when the statement was closed. While the group is small and the rules are stable, none of this shows. Past fifty or so members and two or three families of scales, every annual campaign becomes a reconstruction.
The most reliable symptom: nobody can replay last year's statement. The files still exist, but the formulas have moved on, the manual adjustment tabs have been overwritten, and the only evidence of the amount paid is the bank transfer itself.
| Campaign spreadsheet | Dedicated rebate engine | |
|---|---|---|
| Scales | Formulas copied across columns, duplicated for every new family | Versioned, dated scales, applied according to the period of the transaction |
| Manual corrections | Overwrite the calculated value, leaving no trace | Entered as adjustments, keeping author, reason and original amount |
| Replaying a past statement | Impossible once the formulas have changed | Recomputed identically from the data and the scale of the time |
| Supplier dispute | Manual reconstruction, several days | Line-by-line breakdown exported in minutes |
| Member joining mid-year | Pro-rata worked out by hand, often forgotten | Pro-rata applied automatically from the joining date |
| Closing | A frozen workbook archived on a network share | Locked, timestamped statement, exportable to accounting |
What the engine has to be able to compute
No two buying groups compute rebates the same way. The mechanics below are the ones we meet most often, and the ones a generic package models badly.
Tiered scales
Progressive or whole-tier rates, with a trigger threshold, a cap, and the structural choice between applying the rate to the tier or to the entire volume.
Multiple bases
Declared revenue, supplier-invoiced revenue, unit volumes, a base restricted to one product family: several bases coexist, sometimes for a single member.
Conditional rebates
Growth bonuses against the previous year, logistics or early-payment premiums, conditions tied to taking part in a commercial campaign.
Pro-rata and mid-year joiners
Members joining or leaving mid-year, approval agreements signed mid-campaign, scope changes half way through.
Split between group and member
The share passed on, the share retained by the central body, and allocation keys that differ by supplier or by family.
Traceable manual adjustments
The edge case no rule covers will always exist. It has to be enterable — but as an identified adjustment, never as a silent overwrite of the calculation.
Traceability matters more than the arithmetic
Computing a rebate is arithmetically simple. What is expensive is proving the figure six months later. A useful engine keeps, for every euro paid: the base used, the version of the scale applied, the source declarations, the adjustments with their author and reason, and the date the statement was locked.
That test is demanding, which is exactly what makes it useful. The gaps it reveals are almost never development errors: they are rules applied by hand, year after year, that nobody had written down. Finding them during acceptance costs a few days. Finding them during the first live campaign costs the members' trust.
How we deliver it
Capturing the existing scales
Two workshops to model the rules as they are actually applied — including the unofficial exceptions. The deliverable is a signed-off rules document, before a line of code.
Engine and historical test set
The engine is built and run against a complete past campaign. Every discrepancy is investigated with you until it is explained or corrected.
Parallel campaign
The first live campaign runs alongside your current method. You only switch once the two results reconcile.
Statement, export and archiving
Campaign locking, accounting export, per-member and per-supplier statements, and retention of the detail for later financial years.
What usually triggers the project
- The person who masters the workbook retires or changes role.
- A supplier disputes an amount and the reconstruction takes a week.
- The group outgrows the size at which a campaign can be run from memory.
- A new type of agreement — logistics, growth, own brand — no longer fits the file structure.
- The auditor asks for the audit trail of the calculation, and there is none.
None of these situations is urgent the day it appears. All of them become urgent at the annual close — which is the worst possible moment to start a project.
Frequently asked questions
- What is the difference between a rebate and a year-end bonus?
- Both describe a discount granted after the fact, based on the volume achieved. French practice distinguishes the accounting-side term (RFA, remise de fin d'année) from the term most buying groups use for the share passed back to members (BFA, bonification de fin d'année). From a software standpoint the distinction matters little: what matters is modelling several deferred-discount mechanics on different bases and tracing each of them separately.
- Can past campaigns be migrated?
- Yes, and we recommend it every time: it is the only credible acceptance data set. We migrate at least the last complete campaign to validate the engine, and usually three financial years so growth comparisons are possible. The migration is priced inside the fixed fee, not billed as an extra once the project has started.
- Do we have to replace the whole management system to get the engine?
- No. The engine can be delivered as the first batch, fed by an import of your existing declarations, and connected later to an online declaration module. It is in fact a common entry point, because it is the process whose pain is easiest to measure.
- How long does it take to go live?
- For a group of fifty to eighty members with two or three families of scales, expect eight to fourteen weeks between the scoping workshops and the first statement computed by the engine, including one campaign run in parallel. What lengthens the schedule is the number of unwritten rules to reconstruct, rarely the size of the group.
- Do we own the engine's source code?
- Yes. The source code and documentation are handed over, and reversibility is a contractual clause. It matters particularly on a calculation engine: the business rules it carries are an asset of the group, not of its supplier.
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 moreSupplier approval and contract software for a buying group
A framework agreement signed in November decides the scales applied fourteen months later, on a base nobody has measured yet. Between signature and year-end close, the negotiated terms get lost: they live in a filed PDF, in an email thread, and in a workbook where someone retyped them by hand.
Read moreRebuilding the management system of a 60-company buying group
A management system that never fails but that nobody can change any more costs more than one that breaks. That was the position this Lyon buying group was in: everything worked, nothing moved, and every new business need was being handled outside the tool.
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