Leak 14 · Suppliers & Procurement - Missed manufacturer rebates
Rebate agreements live in a filing cabinet. Purchases live in the ERP. The money you earned but never claimed lives nowhere, and it is often the largest single leak on this list.
What is it?
Manufacturer rebates come in many forms: volume tiers, growth incentives, SPAs and ship-and-debit claims on specific customers, marketing co-op, new-product introductions, early-pay discounts, and buying-group programs. Each has its own conditions, measurement period, claim process, and deadline.
The leak happens in three places. Rebates earned but never claimed, because nobody tracked the threshold or the deadline. Rebates claimed but under-calculated, because the purchase data used did not match the agreement’s definition. And rebates paid but never reconciled, so a short payment or a missed program is never noticed.
For distributors with dozens of supplier agreements, the total rebate income can be a meaningful share of net profit. Missing a few percent of it is a large number.
Where does it occur?
In the gap between the agreement, which is a document, and the transaction data, which is in the ERP. Ship-and-debit claims fail at the sales order, where the special price is applied but the claim is never filed. Volume tiers fail at year end, when a threshold was within reach and nobody knew.
- Family
- Suppliers & Procurement
- Primary owner
- Purchasing Manager / CFO
- Secondary owners
- Controller, Supplier Relations, Sales Managers
- Primary impact
- Gross profit
- Typical data source
- Supplier agreements, purchase history, sales history, rebate statements
- Detection difficulty
- 30-day measurability
Ask yourself
Can you list every rebate program you are enrolled in, the amount earned year to date, and the amount actually received?
Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.
What does it look like?
Warning signs. None of these proves the leak exists. They tell you where to look.
- Rebate agreements stored as PDFs and emails with no register of terms, periods, and deadlines.
- Rebate income that varies year to year with no explanation tied to purchase volume.
- Ship-and-debit or SPA prices applied to customer orders with no matching claim to the supplier.
- Year-end volume tiers missed by small amounts that a planned purchase would have covered.
- Rebate checks deposited without being matched to a calculation of what was owed.
- Only one person understands the rebate programs, and it is not their main job.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field | Example |
|---|---|
| Supplier | Apex Fasteners |
| Program type | Volume tier / Growth / SPA / Co-op |
| Measurement period | Calendar 2026 |
| Tiers and rates | 2% over $500K, 3% over $750K |
| Qualifying purchases definition | Net invoiced, excluding freight and returns |
| Claim deadline and method | 30 days after period end, via portal |
| Purchases to date from the ERP | $684,200 |
| Rebates claimed and received | $9,100 claimed, $8,650 received |
| For SPAs: customer, item, special price, quantity shipped | Acme / SKF-6205 / $17.10 / 1,150 |
The initial check
Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.
- 1List every supplier that offers you a rebate, from memory and from the agreements you can find. Note the type and the measurement period.
- 2For each, write down the rebate income you actually received last year.
- 3For the five largest suppliers, pull last year’s purchases and calculate what the agreement says you should have earned.
- 4Compare the two numbers. Then check whether any ship-and-debit prices on customer orders have a matching claim.
Rebate gap = rebate earned per the agreement − rebate actually received
Then ask one question: For how many of your rebate programs could you say today, with confidence, how far you are from the next tier?
The 30-day test
Build a rebate register: one row per program with supplier, type, period, tiers, qualifying purchase definition, claim deadline, and the source document. Then, for each program, calculate earned-to-date from ERP purchase data using the agreement’s definition, not the ERP’s default purchase total.
Reconcile earned against claimed and received for the last two complete periods. Classify every gap.
| Gap type | Programs | Earned | Received | Gap |
|---|---|---|---|---|
| Never claimed | 4 | $21,400 | $0 | $21,400 |
| Under-claimed (data mismatch) | 6 | $58,900 | $51,200 | $7,700 |
| Short-paid, not reconciled | 3 | $33,000 | $30,100 | $2,900 |
| SPA shipped, no claim filed | 2 | $14,600 | $3,200 | $11,400 |
| Tier missed by less than 5% | 2 | $12,000 forgone | — | $12,000 |
Hypothetical distributor, one year. Fictional numbers.
Some of these gaps are recoverable now: most suppliers accept late or corrected claims within a window. Some are lessons for next period. The register is the asset either way, because it turns the rebate program from one person’s memory into something the business owns.
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Σ over programs of (earned − received) for open claim windows, plus forgone tier value × probability of reaching the tier with planned purchasing
Worked example
- • $43,400 of unclaimed and under-claimed rebates within open claim windows
- • Assume 70% is recoverable after supplier review
- • $12,000 of tier value forgone last year, with a 50% chance of reaching similar tiers next year with planning
$43,400 × 70% + $12,000 × 50% ≈ $36,400 for the current year
Rebates are gross profit, not revenue. A recovered rebate is close to pure margin, which is why this leak is worth the tedious work of building the register.
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- No owner for rebate programs, no register, no calendar of claim deadlines, and no reconciliation of payments against a calculation.
- Data
- Agreement terms are in documents, purchases are in the ERP, and the two use different definitions of what qualifies.
- Technology
- Nothing tracks progress to tiers during the period, and ship-and-debit claims are not generated from the orders that earn them.
What should we do?
Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.
Level 1
Register
A single spreadsheet of every program with terms, period, deadline, and owner. This alone recovers a surprising amount.
Level 2
Calculation
A quarterly earned-to-date calculation from ERP purchases for each program, using the agreement’s definitions.
Level 3
Reconciliation
Every rebate payment matched to the calculation, with short payments queried within the supplier’s window.
Level 4
Workflow intervention
Tier tracking that alerts purchasing when a threshold is within reach before period end, and automatic ship-and-debit claims generated from qualifying sales orders.
Level 5
Agreement reading
Extract terms from new and renewed agreements as they arrive, populate the register, and flag changes from the previous version.
Where AI helps
- Reading rebate agreements, which are long, inconsistent, and different for every supplier, and extracting tiers, definitions, and deadlines into the register.
- Matching supplier part numbers and customer names on rebate statements to your records.
- Flagging agreement changes at renewal that would otherwise go unnoticed.
Where AI probably doesn’t
The rebate calculation itself must be deterministic and auditable, because you will be arguing about it with a supplier. Build it as ordinary code or a spreadsheet you can hand to the supplier. If you have no register at all, start with the spreadsheet.
Before you call it a leak
- Agreement definitions of qualifying purchases vary: net of returns, excluding certain product lines, based on supplier invoice date rather than your receipt date. Use the supplier’s definition or the claim will be rejected.
- Buying-group rebates are calculated by the group and may lag by months. Reconcile to the group’s statement, not just the check.
- Chasing a tier by buying inventory you do not need trades a rebate for a working-capital problem. See slow-moving inventory before buying ahead.
ERP note. Some distribution ERPs have a rebate module. In practice most distributors track rebates outside it because the module cannot represent the agreement’s terms. The purchase history export is what matters: supplier, item, invoice date, net amount, returns.
Think this might be happening in your business?
Turn the finding into a next step.
If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.
Related leaks
- Leak 15 · SuppliersMissed volume discount thresholdsBuying 480 units at the 100-unit price when 500 would have earned the next break. Or buying 500 units of something that does not move to get the break. Both cost money.
- Leak 19 · SuppliersSupplier terms not being capturedA 2% discount for paying in 10 days is a 36% annualized return. Paying on day 30 anyway, or paying on day 12 and missing it, throws that away.
- Leak 20 · InventorySlow-moving inventoryStock that turns once every three years ties up cash, takes space, and eventually becomes dead. The ERP already knows which items. Nobody has asked it.
- Leak 02 · PricingCost increases not reaching customer pricesA supplier raises cost. The customer price stays where it was. Margin on that item quietly compresses until someone notices, often a year later.
Let’s start with one thing.
What would better performance look like?
Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.
No transaction files needed for the first conversation.