What Governed Rebate Accounting Looks Like (And Why Most Distributors Don’t Have It)
Last updated: November 11, 2026
Governed rebate accounting is a process standard with five characteristics: agreement-level tracking with version-controlled terms, period-end accrual with documented methodology, audit lineage by agreement built before settlement arrives, formal settlement reconciliation as a standard close step, and post-settlement variance analysis. Under ASC 705-20-25-1 and ASC 705-20-25-10, the accrual must be probable and reasonably estimable. Most distributors have a number. Few have a process that meets that standard.
Rebate accounting under ASC 705-20 has two distinct requirements. The first is getting the right number. The second is demonstrating that the number was derived from a defensible process.
Most distributors focus on the first. Almost none have the second.
Under ASC 705-20-25-1, a vendor rebate is recognized as a reduction of cost of sales when it is probable and reasonably estimable. The standard’s drafters were precise about “reasonably estimable.” It does not mean a reasonable guess. It means the estimate can be derived from documented inputs — the program terms, the period-to-date purchase volumes, the applicable tier or rate — and explained to a reviewer who had no prior knowledge of the arrangement. If a controller was replaced mid-year, could the incoming person reconstruct the accrual from what is in the system? In a governed process, the answer is yes. In most ERP configurations, the answer is no.
ASC 705-20-25-10 extends this further: when the terms of an arrangement are modified, the effect is recognized in the period of modification. This requires knowing what the prior terms were, knowing when they changed, and having a record of how the estimate was revised as a result. That is not a journal entry question. It is a process question.
The gap between what the standard requires and what most distributor close processes actually deliver is not a matter of intent. It is a matter of infrastructure.
Five Characteristics of Governed Rebate Accounting
Governed rebate accounting is not a software feature. It is a process standard — a set of characteristics that, taken together, mean the accrual process meets what ASC 705-20 actually requires. Here is what it looks like when a distributor has it.
1. Agreement-Level Tracking
Every vendor rebate agreement is registered as a record with version-controlled terms: effective dates, tier thresholds, eligible SKU scope, measurement period, and settlement timing. When terms change mid-year — as they frequently do — the new terms are logged as a revision, and the prior version is retained. The agreement record is not a spreadsheet row. It is a system entry that makes the terms auditable at any point in time.
This matters because auditors do not test accrual rates in the abstract. They test whether the rate in the accrual matches the rate in the agreement. Without agreement-level tracking, that test requires pulling PDFs and email threads. With it, the answer is a query.
2. Period-End Accrual with Documented Methodology
At each close, the accrual estimate is derived from three inputs: the current terms, the period-to-date purchase totals, and an explicit rate-and-tier calculation. The methodology is consistent across periods. If the program has retroactive tiering, the methodology handles that correctly — recasting the full-period volume at the applicable rate — and the same logic is applied every period, not rebuilt each time.
Any change to the methodology is documented as an estimate revision: what changed, why, and what effect it had on the accrual. This is the traceability ASC 705-20-25-10 requires when arrangements are modified.
3. Audit Lineage by Agreement
For each rebate agreement, there is a traceable record — built before the settlement arrives — showing: what was accrued at each period-end, what rate and volume assumption was used, and who reviewed the estimate. This record connects the COGS entry back to the source purchase orders and program terms.
The audit lineage exists before the settlement arrives. That distinction matters. A distributor who can reconstruct the calculation after the fact is managing a documentation exercise. A distributor who has the lineage before the fact is managing a process. Auditors can tell the difference, and so can CAS practitioners doing a close review.
4. Settlement Reconciliation as a Standard Step
When the manufacturer sends its settlement calculation, the distributor does not simply accept or dispute it on instinct. It runs a formal reconciliation: its calculation against the manufacturer’s calculation, agreement by agreement, line by line. Differences are identified, explained, and documented — either accepted as a correction to methodology or flagged as a dispute with supporting evidence.
This reconciliation is part of the Q1 close. It is not an emergency response to a number that looks wrong. When settlement season produces a variance, the reconciliation step is what converts “this doesn’t match” into “here is specifically what drove the difference and here is our position.” Without it, settlement disputes are hard to work because the documentation required to support the distributor’s position does not exist in a usable form.
The practical consequence of skipping this step appears in the rebate accrual close failure patterns: disputes that age past 90 days, then past a year, until the settlement window closes. The amount is not a loss at the moment it enters dispute. It becomes one over time, through process failure.
5. Variance Analysis and Methodology Review
After settlement season, the distributor reviews its accrual accuracy. For each material agreement: how close was the accrual estimate to the final settlement? Which agreements had the largest variances, and what drove them — rate error, volume estimation error, tier calculation error, or agreement term that was not reflected correctly?
This review is not a performance assessment. It is a feedback loop into the following year’s methodology. A distributor that completes this review consistently will get more accurate over time. One that does not will have the same variance problems each cycle with no structural way to improve.
Why Most Distributors Don’t Have This
The gap is not aspirational. Most distribution finance teams know what good looks like. The problem is structural.
ERP rebate modules were built to track purchases and apply rates. They were not built to govern. They do not version-control agreement terms — when terms change, the ERP rate changes and the history is gone. They do not produce period-end audit trails that connect a COGS entry to a specific agreement’s terms and volume assumption. They do not run settlement reconciliations. They do not retain the prior-period methodology in a form that documents it as consistent.
The result is that “ERP rebate tracking” and “governed rebate accounting” describe two different things. ERP rebate tracking produces a number. Governed rebate accounting produces a number and an explanation of how the number was derived that will withstand audit review. The gap between them is not a configuration problem. It is an architectural one. ERP systems were not designed for the governance layer ASC 705-20 requires.
This is what the ERP rebate gap assessment tests: seven questions that map the ERP’s actual capability against each of the requirements above. For most distributors, the gap score is high not because the ERP was misconfigured but because the ERP was never designed for this.
See also: What to Ask Your ERP Vendor About Rebate Accounting — the five governance questions that separate a tracking system from a governed one.
What the Diagnostic Looks Like
A distributor can assess its own governance posture by working through the five characteristics above. For each one, the question is binary: does the process exist in a documented, consistent, auditable form — or is it approximated?
Agreement-level tracking: are vendor program terms stored as records, or as spreadsheet rows that get updated in place? Period-end accrual methodology: is the same calculation logic applied consistently every close, or rebuilt each time from whatever materials are available? Audit lineage: does the lineage exist before the settlement arrives, or is it reconstructed after? Settlement reconciliation: is it a standard step with a documented output, or an ad hoc response to a discrepancy? Variance review: does it happen systematically and feed next year’s methodology, or does it not happen at all?
Each of these maps directly to what the rebate close checklist tests across its 32 audit items. The governance gaps that show up on the diagnostic are the same gaps that show up as findings during fieldwork.
The settlement variance that results when these characteristics are absent is documented in When the Manufacturer’s Year-End Settlement Doesn’t Match — what the gap looks like when it surfaces in Q1 and what a defensible response requires.
Aurgus is built to close this gap: structured agreement tracking, period-end accrual calculation with documented methodology, audit lineage by agreement, and a settlement reconciliation workflow — the five characteristics above, running as a system rather than a set of manual procedures. See aurgus.com/pricing/ for subscription details.