What CAS Partners See When They Close Distributor Rebate Accruals
Last updated: November 11, 2026
A CAS partner reviewing a distributor rebate accrual is making three judgments under time pressure: is the methodology documented, does the number reflect the actual program tier, and is there audit lineage? Under ASC 705-20-25-1 and ASC 705-20-25-10, the accrual estimate must be probable and reasonably estimable — but most clients cannot demonstrate that in real time. The gap between a number that ties and a number that can be defended is exactly where advisory value lives.
Consider a CAS partner doing monthly close support for a mid-size wholesale distributor. The last item on the trial balance review is the rebate accrual. The client’s controller sends over two things: the ERP balance and a spreadsheet that explains it. The partner has 20 minutes before the next client call. This scenario — repeated across dozens of engagements at firms serving distributors — is where the rebate accrual problem lands on the advisor side of the table.
The controller is not asking for a second opinion. They are asking for a sign-off. And the CAS partner has three options: accept the number, push back, or identify a structural gap the client hasn’t seen yet. That third option is what this piece is about.
What a CAS Partner Is Actually Evaluating
The rebate accrual review is not an audit. It is a close-support judgment call under time pressure. But the standard governing the number does not change because the reviewer is a CAS partner rather than an audit senior. Under ASC 705-20-25-1 and ASC 705-20-25-10, the distributor must account for vendor rebates as a reduction of the cost of inventory or cost of goods sold — not revenue — and the accrual estimate must be probable and reasonably estimable.
Three things a CAS partner is working through, whether explicitly or not:
1. Is the accrual methodology documented — or is “the ERP said so” the whole story?
ASC 705-20-25-10 requires that the estimate of cumulative tier rebates be based on what is probable as of the reporting date. That is an estimate judgment: the client’s team must have made a call about expected full-period volume and applied the appropriate rate. When the number comes out of an ERP batch process, the documentation question is what the ERP was told. What rate? What volume assumption? What tier structure? “The ERP said so” is not a methodology. It is the output of a methodology that may or may not exist.
A partner reviewing a number that cannot be explained by the client’s controller — where the controller’s honest answer is “that’s what the system calculated” with no supporting documentation of the inputs — is reviewing an estimate with no audit lineage. The number may be right. The question is whether it can be defended.
2. Does the number reflect the actual program tier?
Tiered rebate programs are common in wholesale distribution. A supplier may offer a base rate of 2% with a step-up to 3% if full-year purchases exceed a volume threshold — sometimes retroactive to dollar one. If the ERP tracks the base rate but not the tiered structure, the accrual systematically understates the probable liability on programs where the client is on track to cross a threshold.
This is a structural understatement, not a rounding error. And it is invisible in the ERP number because the ERP number simply reflects what the ERP was set up to calculate. A CAS partner who accepts the ERP balance without understanding whether the client’s programs have tiered structures — and whether those tiers are modeled — is implicitly accepting a methodology gap, not just a number.
The standard is explicit: ASC 705-20-25-10 addresses the cumulative tier estimate directly. The accrual on a tiered program must reflect the best estimate of the cumulative rebate for the full measurement period, not a point-in-time flat rate.
3. Is there audit lineage?
Consider a scenario where the client’s rebate accrual is later disputed by a supplier at year-end settlement. The supplier’s calculation of the qualifying volume differs from the client’s by enough to affect the settlement check. The question the client’s audit team will ask is: how was the accrual estimate derived, and what was the basis for the qualifying volume number?
If the answer is a spreadsheet that only the controller can interpret — or a workbook where the formulas reflect corrections made without version control — there is no audit lineage. There is an answer, possibly the right one, that cannot be proven.
The rebate accrual is an estimate. Estimates are not expected to be exactly right. They are expected to be governed: derived from documented inputs, by a named preparer, against a documented methodology, with a record of how the estimate changed from period to period as expectations moved. That governance trail is what makes the number defensible — to auditors, to a CFO asking about a Q4 swing, and to a supplier disputing year-end.
What “Good Enough” Looks Like vs. What Defensible Looks Like
There is a real gap between these two, and it matters to the CAS partner.
A “good enough” close produces a number that ties to the ERP, is in the range of prior periods, and doesn’t trigger an immediate question from the engagement partner. Most monthly close support lives here. The number is probably approximately right, and the engagement moves on.
A defensible close produces a number that can be explained from first principles: here is the agreement, here is the volume, here is the rate applied, here is why that rate — and not the base rate — is the correct one given expected full-period attainment. If the number changes from last month, there is a documented reason: the volume run-rate moved, the tier call was revised, the agreement was amended. The change itself is recorded as an estimate revision, prospectively, as ASC 705-20 expects.
The gap between these two is not primarily about the magnitude of the number. It is about whether the number can answer questions. “Good enough” can answer the question “what did you book?” A defensible number can also answer “why that amount, and what would have to be true for it to change?”
Most clients, in a candid conversation, are operating in the first category and would like to be in the second. Most CAS partners know the difference and have a preference about which one they are signing off on.
The Referral Moment
When a CAS partner identifies this gap at a client, there are three common paths:
The first is to absorb the risk silently. The number seems reasonable, the engagement is otherwise clean, and opening a conversation about estimate governance at monthly close is a scope conversation the partner is not positioned to have in 20 minutes. The accrual gets accepted.
The second is to add a caveat to the engagement letter. The partner documents that the rebate accrual estimate was provided by management with limited supporting documentation, and that the engagement did not include an independent review of the underlying methodology. This protects the firm but does not help the client.
The third is to identify a system gap and recommend a solution. The CAS partner says: the client’s ERP is not built to do this calculation correctly, the evidence is the documentation you can’t produce, and there is a category of close-operations software built specifically for this problem. This conversation — the one that names the gap and points to a solution — is the one that creates value for the client and positions the firm as an advisor, not just a reviewer.
That third conversation is the one Aurgus is built to be part of. A system that handles the accrual computation, governs the estimate, and produces the audit lineage the partner needs — before anyone asks for it — changes what the CAS partner can offer. Not just a review of the client’s number, but a referral to infrastructure that makes the number defensible by construction.
A Tool for the Conversation
If a client’s rebate accrual raises any of the three questions above, the ERP rebate gap assessment at /erp-rebate-gap-assessment/ is a 2-minute, 7-question scored tool designed to identify exactly where the gap is. It produces a scored result the CAS partner can share with the client’s controller to open the systems conversation from a neutral diagnostic rather than an opinion.
The rebate close checklist — 32 audit tests across six sections — covers the same terrain from the audit-preparation angle: what auditors will test on a distributor rebate accrual and what documentation the client needs to have ready.
For background on the specific failure patterns that produce year-end rebate surprises, rebate accrual close failure modes walks through the structural mechanisms — retroactive tier miscalculation, stale flat-rate accruals, and audit-trail gaps — that show up repeatedly in distributor close operations.
The accrual review moment — a CAS partner, a spreadsheet, 20 minutes — is where the advisor relationship either stays at sign-off or steps into something more useful. The gap is well-defined. The standard is clear. The only variable is whether there is infrastructure to close it.
Aurgus runs the rebate accrual computation, governs estimates, and builds audit-ready lineage from source purchase order to COGS entry. See aurgus.com/pricing/ for plan details.
For a discussion of how CAS partners evaluate vendor outreach in the rebate accounting space, see What Makes a CAS Partner Respond to Vendor Outreach About Rebate Accounting.
For a framework on how to present this to your distribution client, see How to Position Governed Rebate Accounting to a Distribution Client.
- FASB ASC 705-20-25-1 (vendor consideration treated as a reduction of the cost of products or services).
- FASB ASC 705-20-25-10 (cumulative tier estimate: probable and reasonably estimable threshold for tiered rebate accruals).
- AICPA, Client Accounting Services: Guidance for CPA Firms; AICPA practice resources for CAS practitioners.