The rebate revenue you earned, captured and provable.
Volume tiers, special pricing agreements, billbacks, growth incentives, buying-group rebates — the off-invoice money a distributor earns from its vendors is hard-won, conditional, and spread across dozens of supplier agreements. When the tracking lives in spreadsheets, earned rebates leak: a threshold missed, a claim window closed, a qualifying purchase never tied back to the agreement that earned it. Aurgus keys every rebate to its source — the agreement, the qualifying purchases, the tier applied, the rule that fired — so what you earned, what you claimed, and what is still outstanding is queryable, not reconstructed.
Note: Aurgus is the governed-calculation substrate — immutable events, supersession rather than overwrite, replayable lineage. That pattern is what makes earned rebate revenue both easier to capture and defensible to an auditor. The product is the substrate; the captured margin is what it enables.
It isn’t effort. It’s a process stretched past its limits.
Missed rebates are rarely a people problem. They are what happens when varied supplier agreements, conditional terms, and high transaction volume meet manual tracking. Five places the margin slips.
- Every supplier agreement is different. Volume tiers, SPAs, billbacks, growth incentives, buying-group rebates — each with its own qualifying rules, thresholds, and claim windows. Holding all of them in spreadsheets means the rules live in someone’s head, not in the data.
- Earned isn’t the same as claimed. A rebate you qualified for still has to be claimed, inside a window, with the qualifying purchases attached. The gap between what was earned and what was actually recovered is where mid-market distributors quietly lose margin.
- The claim-to-miss ratio is unknown. Most teams can’t say with certainty how many rebate opportunities across every agreement ended in a filed, paid claim versus a missed one — because there is no single place that tracks every opportunity against its outcome.
- Reconciliation eats skilled time and still carries risk. Manually matching rebate data across suppliers is slow, and a single data-entry error can misstate an accrual. The cost is both the hours and the exposure.
- The accrual has to be defensible. Under ASC 705-20 a vendor rebate reduces the cost of goods purchased, so a mis-estimated or unclaimed rebate understates margin — and when the auditor asks you to defend the accrual, reconstructing it from spreadsheets is slow and fragile.
Every rebate keyed to its source — from agreement to claim.
Capturing earned revenue and defending the accrual are the same problem: knowing, per agreement, exactly what the number is and why. Aurgus writes that as the rebate is computed.
- 1
Each supplier agreement is modeled, not memorized.
Volume tiers, SPA terms, billback rules, growth thresholds, buying-group arrangements — captured as structured agreements, so the qualifying rules live in the data, not in a colleague’s spreadsheet.
- 2
Every qualifying purchase ties back to the rebate it earned.
As purchases flow in, Aurgus matches them to the agreement and tier that applies and writes the earned rebate as a recorded event — carrying the source line, the matched terms, and the rule that fired. Earned stops being invisible.
- 3
Earned, claimed, and outstanding are one view.
Because every rebate event carries its claim status, the gap between what you earned and what you have actually recovered is queryable per agreement — the claim-to-miss picture you couldn’t previously see.
- 4
Adjustments supersede, they don’t overwrite.
A true-up, a rate correction, a reconciled deduction posts an event that supersedes the prior figure and keeps it on the log. The history of what was earned, what changed it, and why is never erased.
- 5
Replayable, agreement by agreement.
Re-run any agreement against its source purchases and get the same result. From the accrual, click through to the qualifying purchases, the tier applied, and the agreement terms. Your auditor gets a queryable dataset, not a binder.
Most tracking captures the obvious ones — and leaks the rest.
Honest comparison of how mid-market distributor finance typically manages vendor rebates, and where each falls short of capturing everything earned.
Works until the rules change.
A workbook per vendor holds the terms someone remembered to enter. Thresholds move, programs get added mid-year, claim windows slip — and the sheet that overwrote last quarter can’t show what was earned but never claimed.
Shows spend. Not entitlement.
Your ERP knows what you bought, but it doesn’t model each vendor’s rebate terms or tie qualifying purchases to the agreement that earned them — so it tells you spend, not the rebate you’re owed.
Finds leaks. A year late.
A third-party recovery audit can claw back some missed rebates after year-end, usually for a share of what it recovers. Useful, but it’s a backstop for a process that already leaked — not a way to capture it the first time.
Entitlement, keyed to the data.
Every agreement modeled, every qualifying purchase matched to the rebate it earns, earned-vs-claimed queryable per agreement. The claim and the audit answer are written as the rebate is computed — not reconstructed after the window closed.
Distributor rebate revenue, honestly answered.
- Why do distributors leak vendor-rebate revenue they have already earned?Vendor rebate programs are varied and conditional — volume tiers, special pricing agreements, billbacks, growth incentives, and buying-group rebates each have their own qualifying rules and claim windows. When the tracking lives in spreadsheets across many supplier agreements, earned rebates go unclaimed because a threshold was missed, a claim window closed, or the qualifying purchases were never tied to the agreement that earned them.
- How is a vendor rebate accounted for by a distributor?Under ASC 705-20, consideration a distributor receives from a vendor is generally accounted for as a reduction of the cost of the goods purchased, not as revenue — so an unclaimed or mis-estimated vendor rebate directly understates margin. The accrual is an estimate that has to be supported with the qualifying purchases, the applicable rate, and the agreement terms behind it.
- What does it take to defend a distributor rebate accrual to an auditor?The auditor wants to trace each accrual back to the supplier agreement, the qualifying purchases, the tier or rate that applied, and the rule that produced the number — reproducibly, not reconstructed from spreadsheets at quarter-end. A calculation-native close writes that trail as the rebate is computed, so the documentation already exists when the question is asked. See also rebate audit trail.
- How does Aurgus help a distributor capture earned rebate revenue?Aurgus keys every rebate calculation to its source — the agreement, the qualifying purchases, the tier applied, the rule that fired — so what was earned, what was claimed, and what is still outstanding is queryable per agreement rather than reconstructed by hand. The same governed-calculation substrate makes the number both easier to capture and defensible to an auditor.
Other places distributors recover margin.
Find where your rebate revenue is leaking.
A working session with someone who understands vendor-rebate programs from the distributor’s side. No pitch. We map your current claim-to-miss picture — which agreements, which windows, which earned rebates you can’t yet prove — against what a governed close would capture.