Rebate numbers that defend themselves.
For as long as anyone has run rebate programs, the number has been assembled — pulled together from systems and spreadsheets, its evidence reconstructed whenever someone asks. That is the old way, and it is why the auditor’s second question — “show me how this was calculated” — turns into a two-week fire drill. Aurgus is the new way: the number is computed once and keeps its own evidence, so the answer already exists. Aurgus is in design-partner stage; we say that plainly, and this is worth reading whether or not we ever talk.
The problem was never the number. It's the distance to its evidence.
A rebate accrual becomes indefensible for a structural reason, not a diligence one. The calculation and the ledger are separated by a batch, so the figure is a snapshot. The lineage — which transactions, which rate, which clause — is never retained, so it has to be rebuilt on request. And when a rate or an eligibility changes, the number is recalculated, not traced, so the before-and-after lives in job logs and someone’s memory. None of that is carelessness. It is simply what happens when a number is assembled instead of computed once and kept — the way it has always been done.
The old way, and the new one.
Not a faster version of the old way. A different shape — where the evidence is part of the number instead of a project you run to recover it.
| The old way | The Aurgus way |
|---|---|
| The number is assembled from many places | It's computed once, in one place |
| The calculation and its evidence live apart | The evidence is part of the number |
| Lineage is reconstructed when someone asks | Lineage is retained the moment the number is made |
| A change is recalculated inside the logs | A change is a new event that references the original |
| Three systems, three numbers, reconciled by hand | One governed number every function reads |
| The estimate cliffs at year-end | The estimate is disciplined from day one |
| Audit is an archaeology project | Audit is a drill-down |
| Trust depends on who built the workbook | Trust is in the record, not the person |
Ask the second question. See the answer appear.
This is a rebate accrual. In the old way, “show me how this was calculated” starts a two-week reconstruction. Here it is one click. Illustrative · synthetic data.
| Pacific Coast Dist. | GPU-9000 · INV-4471 | $180,000 |
| Pacific Coast Dist. | GPU-9000 · INV-4488 | $220,000 |
| Cascade Supply Co. | GPU-9000 · INV-4502 | $155,000 |
| Pacific Coast Dist. | GPU-9100 · INV-4530 | $310,000 |
| + 41 more qualifying transactions | $1,735,000 | |
| Qualifying base | $2,600,000 | |
One number, computed once, that keeps its own record.
The method, in five moves. Read it and the contrast above stops being a claim and becomes mechanics.
- 1
Computed once, on an append-only event log.
Every accrual, adjustment, reversal, and settlement is written once and never edited. Corrections are new events that reference the original. The current balance is derived from that history — so the same inputs always produce the same number, and nothing has to be re-run to know why.
- 2
Every number carries its lineage.
From any accrued dollar, drill to the contributing source transactions, the rate applied, the cohort, and the agreement clause that authorized it. The lineage is retained as a record, attached to the number — not reconstructed when an auditor asks. The evidence travels with the figure.
- 3
Conservation-checked, so it can't quietly drift.
A reconciliation check verifies that value is conserved through the chain: nothing appears or disappears between accrual and settlement without an event that explains it. When something doesn’t reconcile, Aurgus surfaces it rather than absorbing it — the number tells you when to trust it.
- 4
Estimated with discipline, not at the cliff.
Tiered and volume rebates accrue at the expected outcome from day one — a documented most-likely-amount method — with a cumulative catch-up when the forecast moves. The year-end surprise, where a top-tier crossing hits the whole year at once, stops being a surprise because it was already in the accrual.
- 5
Human-approved where it counts.
Aurgus computes, explains, and proposes — but every action with financial consequence carries a named approver in the audit trail. The intelligence surfaces the evidence; the operator decides. The gate is in the data model, not a review step someone can skip.
Built for the requirement. Honest about the proof.
A proper read deserves honest inputs. Here is both.
Your problem is defending the number.
If your pain is that accruals can’t be traced, reproduced, or explained under scrutiny, that is exactly what this method is built for.
Your programs span more than one system.
When rebate economics depend on data outside a single ERP — distributor POS, partner claims, a second system after an acquisition — the calculation reads across sources rather than being blind to what sits outside one of them.
You need a referenceable production deployment this quarter.
Aurgus is design-partner stage. If your process requires a long reference list now, we’re not there yet — and we’d rather say so here than in month three.
Partner-facing claim workflow is your operational core.
Deep claim matching and dispute state are on our roadmap, not our shipped product. If that’s the center of your operation, keep what works.
The method, honestly answered.
- What does it mean that a number 'defends itself'?It means the calculation carries its own evidence. From any accrued dollar you can drill to the source transactions that produced it, the rate applied, the cohort it belonged to, and the agreement clause that authorized it — retained as a record, not reconstructed on request. When someone asks how a number was calculated, the answer is already attached to the number. That is the difference between a figure you present and a figure you can defend.
- What is the append-only event log, in plain terms?Every calculation event — an accrual, an adjustment, a reversal, a settlement — is written once and never edited. Corrections happen by adding a new event that references the original, so the full history of how a number came to be is always intact. The current balance is derived from that history. Nothing is overwritten, so nothing has to be reconstructed later — the record is the calculation.
- How does Aurgus keep the number honest as estimates change?Two ways. First, tiered and volume rebates accrue at the expected outcome from the start (a documented most-likely-amount method), with a cumulative catch-up when the forecast moves — not cliff accounting that detonates at year-end. Second, a conservation check verifies that value is conserved through the chain: nothing appears or disappears between accrual and settlement without an event that explains it. If the numbers don't reconcile, Aurgus says so rather than hiding it.
- Where does the human stay in control?Everywhere it matters. Aurgus surfaces context, computes, and explains — but every action with financial consequence (an agreement, an adjustment, a settlement) requires a named human's approval, captured in the audit trail. The intelligence proposes and evidences; the operator decides. That gate is part of the data model, not an optional review step.
- Is Aurgus proven at scale yet?No — and we won't pretend otherwise. Aurgus is in design-partner stage: it is working with a small group of finance teams, not a long list of production references. What is real today is the method described here and a free diagnostic you can run against your own control posture. If you need a referenceable production deployment this quarter, we're honest that we're not there yet.
See where your controls stand before the auditor does.
The free Off-Invoice Control Index scores your rebate and incentive controls across the same requirements this method is built on, benchmarked to published research. Three minutes, no email to see your score.