ASC 606 rebate compliance, audit-defensible by construction.
FASB’s ASC 606 made variable consideration on rebates, billbacks, and incentives a quarterly conversation with your audit firm — and IFRS 15, its international twin, imposes the same discipline. Every accrual is an estimate; every estimate requires reasonable certainty; every defense requires lineage. Aurgus writes that lineage at the moment each accrual posts — not reconstructed at quarter-end from spreadsheets. Compliance becomes a property of the data model.
Note: Aurgus doesn't ship an “ASC 606 module.” The calculation engine's pattern — immutable events, supersession not overwrite, replayability — is what makes variable consideration defensible by construction. The product is the substrate; the compliance is what it enables.
The estimate is a judgment call. The judgment requires evidence.
PCAOB inspections increasingly focus on variable-consideration estimates as a high-risk area. The questions auditors ask have shifted — and the spreadsheet-based defenses many teams rely on are no longer reliably accepted.
- Estimating consideration is a judgment. ASC 606 requires either expected-value or most-likely-amount method, constrained so a significant revenue reversal isn't probable. Reasonable people disagree on the inputs.
- Defending the estimate requires reproducible inputs. Your audit firm wants to see the contract terms, the qualifying sales, the cohort eligibility, the rate applied, and the rule that fired — for each accrual, not in aggregate.
- Spreadsheet defenses are increasingly rejected. PCAOB inspection findings on variable consideration have pushed Big-4 firms to require machine-readable lineage. Reconstructed binders don't pass the bar they used to.
- Adjustment events get worse if they overwrite. When the estimate updates next quarter, overwriting the original loses the audit-defensible history of what was estimated and why. Supersession (not overwrite) is the right pattern — and the typical ERP rebate module overwrites.
- Restatement risk is no longer hypothetical. Public manufacturers have restated for variable-consideration accrual errors. The PCAOB has flagged this in inspection reports. Boards and audit committees are asking.
Lineage as a property of the data model — not a quarter-end pass.
Audit defensibility isn't an export feature. It's how the calculation engine writes its events from the first transaction onward.
- 1
Every accrual is an immutable Accrual event.
Written at the moment the qualifying transaction is ingested. Carries the source POS row, the matched condition record, the rule that fired, the bucket configuration, and the operator who approved the underlying agreement.
- 2
Estimates update via Adjustment events, not overwrites.
When the consideration estimate adjusts — true-up at settlement, mid-quarter program change, deduction reconciliation — Aurgus posts an Adjustment event that supersedes the original. The original Accrual stays on the log forever. The chain of what was estimated, why, and what corrected it is fully traceable.
- 3
Operator approval is a first-class event.
Every approval (initial activation, mid-quarter adjustment, settlement authorization) is captured as an Approval event with the operator's reasoning, the platform's confidence, and the source-cited rationale. The judgment is documented as it's made.
- 4
The lineage chain is machine-readable.
From the Settlement event, click through to the contributing accruals, then to the source rows, then to the rules. Export it as CSV. Your audit firm gets a queryable dataset, not a binder.
- 5
Replayable end-to-end.
Re-run any agreement against its source feed and get the same result. The deterministic engine guarantees same inputs → same number, every time. Reproducibility is the audit standard; Aurgus is built around it.
Most defenses were built before PCAOB raised the bar.
Honest comparison of what most finance teams use to defend variable-consideration estimates — and where each falls short.
Reconstructed at quarter-end.
The most common pattern: build the defense binder when the auditor asks. Pulls reports from the ERP and the rebate suite, joins them to contract terms manually, explains variances in narrative. Increasingly fails the reproducibility bar PCAOB inspections raised.
Better than Excel. Still reconstructed.
Custom ABAP or SQL reports against your rebate module's tables produce machine-readable output, but they're still reconstructions — running the report tomorrow may give a different number if the underlying batch ran again.
Expensive. Periodic. Not a substrate.
Big-4 firms can advise on ASC 606 methodology and review your defense annually. They can't be the calculation substrate that makes the defense automatic. Their fees often exceed the platform fee for a calculation-native solution.
Lineage as the data model.
Every Accrual, every Adjustment, every Approval is written with full chain at the moment it occurs. Replayable, queryable, machine-readable. The audit defense isn't a quarter-end project — it's the byproduct of normal operation.
ASC 606 rebate compliance, honestly answered.
- What does ASC 606 require for rebate accruals?ASC 606 classifies rebates, billbacks, sales incentives, and trade promotion spend as variable consideration. Companies must estimate the consideration they expect to be entitled to, using either the expected-value or most-likely-amount method, and must constrain the estimate to the extent that a significant revenue reversal is not probable. The estimate must be updated each reporting period — and the supporting evidence for the estimate must be defensible to your audit firm.
- Why is ASC 606 compliance harder than it looks?Because the estimate is a judgment call, and judgment calls require evidence to be auditable. PCAOB inspections increasingly focus on variable consideration estimates as a high-risk area. Audit firms now ask for reproducible lineage from the original sales transaction to the accrual to the eventual settlement. Defending estimates with spreadsheet exports and tribal knowledge is increasingly insufficient.
- How does Aurgus help with ASC 606 compliance specifically?Aurgus writes the supporting evidence as a side-effect of normal operation. Every accrual posts as an immutable Accrual event with full lineage to the source POS row, the matched condition record, the rule that fired, and the operator approval. When the estimate adjusts, Aurgus posts an Adjustment event that supersedes — never overwrites — the original. The audit-defense chain is machine-readable and queryable, not reconstructed at quarter-end. See also variable consideration audit defense.
- Is Aurgus a substitute for accounting judgment?No. ASC 606 estimates remain judgment calls made by your Controller, your CFO, and your audit committee. Aurgus is the substrate that makes the judgment defensible — it doesn't make the judgment. The deterministic engine produces reproducible numbers; the operator approves; the audit trail is the evidence.
Other places to tighten the audit defense.
Discuss your ASC 606 exposure.
Thirty minutes with someone who's defended variable-consideration estimates to PCAOB-inspected firms. No pitch. We map your current evidence trail against the bar your auditor will hold to.