What to Expect from a Rebate Accounting Diagnostic Conversation
Last updated: November 11, 2026
A rebate accounting diagnostic covers four areas: accrual methodology documentation, ERP audit trail capability, settlement reconciliation practice, and audit documentation depth. The conversation is 80% questions, 20% explanation — it is not a demo. The output is a specific finding about where the process gap exists under ASC 705-20-25-1 and ASC 705-20-25-10.
Illustrative framing: the scenario below describes a typical situation CAS practitioners encounter. It does not represent any specific firm or client.
A CAS partner at a regional accounting firm has just agreed to a 20-minute diagnostic conversation with Aurgus about one of their distribution clients. The client has eight active vendor rebate programs, closes on a fiscal calendar, and relies on a combination of ERP output and a close spreadsheet to record rebate receivables at period-end. The partner agreed to the conversation because the outreach they received identified the specific problem — not rebate management in the abstract, but the documentation gap between what the client’s ERP produces and what ASC 705-20-25-1 requires.
They are not sure what to expect from the call. Here is what should happen — and what should not.
What the Diagnostic Covers
A rebate accounting diagnostic has four areas. Each one is a question about the client’s current process, not a product demonstration. The goal is a clear assessment of where the gap exists and what it means.
1. Accrual Methodology
The first question is how the client estimates rebate receivables at each period-end. Specifically: is the methodology documented? Is the same logic applied consistently every close, or is it rebuilt from whatever materials are available each quarter?
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. “Reasonably estimable” means the estimate can be derived from documented inputs — program terms, period-to-date purchase volumes, applicable tier or rate — and explained to a reviewer who had no prior knowledge of the arrangement. If the partner’s client was asked to explain last quarter’s rebate accrual methodology to an auditor without reconstructing it after the fact, could they do it?
In most distributor close processes, the answer involves a spreadsheet that was built several years ago and updated manually each period. The methodology exists implicitly, in the person who updates it. It is not documented as a methodology. That gap — between an implicit calculation and a documented, defensible methodology — is what this area of the diagnostic assesses.
2. ERP Integration Limits
The second question is what the client’s ERP actually tracks. Specifically: does it track rebate agreements at the tier level, with version-controlled terms? Does it produce a period-end audit trail that links the COGS entry to the source agreement and the volume assumptions used?
Most ERP systems used in wholesale distribution — Infor, Epicor, SAP, NetSuite — were built to track purchases and apply rates. They were not built to govern rebate accounting. When terms change mid-year, the ERP rate changes and the prior terms are gone. At period-end, the ERP can produce a number; it cannot produce an explanation of how that number was derived that connects back to the specific agreement terms in effect at the time.
Under ASC 705-20-25-10, when the terms of an arrangement are modified, the effect is recognized in the period of modification. That 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 an accounting question. It is a systems architecture question. The diagnostic establishes whether the client’s ERP can support what the standard requires, or whether the gap has to be closed outside the ERP.
3. Settlement Reconciliation
The third question is what happens when the manufacturer’s year-end settlement arrives. Does the client run a formal reconciliation — their calculation against the manufacturer’s calculation, agreement by agreement — or is the settlement treated as the authoritative number and booked as received?
This is the moment where process gaps become financial exposure. A client whose accrual process is well-documented will have a clear view of what the settlement should have been before it arrives. When the manufacturer’s number differs, they can identify specifically where the variance originated: a rate difference, a volume measurement difference, a scope interpretation. That position is supportable. A client whose accrual process exists in a spreadsheet without audit lineage will accept the settlement calculation because they have no comparable document to dispute it with.
The diagnostic asks whether the client’s settlement reconciliation is a standard close step — planned, executed, documented — or an ad hoc response to a number that looks wrong.
4. Audit Documentation Depth
The fourth question is straightforward: if an auditor requested the support behind last year’s rebate accrual, what could the client produce?
There is a spectrum of answers. At one end: a system-generated audit trail with version-controlled agreement terms, period-end calculations linked to source data, and a formal settlement reconciliation showing how each agreement resolved. At the other end: a spreadsheet with numbers and no source links, plus PDFs of vendor agreements that may or may not reflect the terms that were in place at the time of the accrual.
Most distributor clients sit somewhere in between — with partial documentation that is sufficient for typical close review but insufficient for a detailed audit of a specific agreement. The diagnostic establishes where on that spectrum the client sits, and what it would take to close the gap.
What a Good Diagnostic Looks Like in Practice
The conversation is 80% questions, 20% explanation. The CAS partner describes how their client handles each of the four areas above. The Aurgus representative explains what the gap assessment measures in that area and what a governed process looks like by comparison. Neither party is performing. Both are assessing.
By the end of 20 minutes, the picture is clear. The partner knows whether the client has the gap — accrual methodology undocumented, ERP producing numbers without explanation, settlement treated as authoritative, audit documentation insufficient. The assessment maps directly to the ERP rebate gap assessment, which provides a scored view of where the ERP capability falls short of ASC 705-20 requirements. If the gap is confirmed, it is confirmed with specificity: which of the four areas is the problem, what the documentation risk is, and what a compliant process would need to include.
What makes this valuable to the partner is that specificity. The finding is not “your client might have a rebate accounting problem.” It is “your client’s settlement reconciliation process is informal and their accrual methodology is not documented at the agreement level — both of which create audit exposure under ASC 705-20-25-1 and ASC 705-20-25-10.”
What the Diagnostic Is Not
It is not a demo. No screen-sharing of the product unless the partner explicitly asks. The diagnostic is an assessment conversation, and introducing a product demonstration mid-conversation changes the dynamic in ways that are hard to recover from. The partner agreed to an assessment; if they receive a sales presentation instead, the conversation ends.
It is not a close attempt. The CAS partner is an advisor evaluating relevance for a specific client situation, not a buyer being presented with a purchase decision. The right output of the diagnostic is a clear finding, not a next step toward a contract.
It is not a commitment to anything. The partner leaves with an assessment. What happens next is their call — a conversation with the client, a decision about whether to recommend further evaluation, a note in the file. No obligation is created by participating in the diagnostic conversation.
What Happens After the Diagnostic
If the gap is confirmed, the dynamic changes. The CAS partner is now the person who identified a specific, documented process gap in their client’s rebate accounting — one that creates audit exposure and a risk of leaving rebate receivables on the table due to undocumented methodology. That finding came through a 20-minute conversation that was structured, specific, and honest.
When the partner brings that finding to the client, the introduction carries weight that a cold email never could: “In reviewing your rebate accrual process, we identified a methodology documentation gap that creates audit exposure under ASC 705-20. I spoke with a tool that maps specifically to this gap. Here is what I found.”
That introduction is the output the diagnostic is designed to produce — not a sale, but an informed, credible finding from a trusted advisor. What the client does with it is their decision. But the decision is now informed by a specific assessment, not a vendor’s self-description.
The transition from that conversation to a demo — if it happens — occurs at the client level, introduced by the partner, grounded in a documented finding. That is a different kind of conversation than cold outreach. It is a qualified one.
For CAS practitioners who want to begin the assessment before a diagnostic conversation: the ERP rebate gap assessment walks through seven questions that map ERP capability against ASC 705-20 requirements. It takes two minutes and produces a scored result. The assessment output is a useful starting point for any diagnostic conversation about a specific client.
For a detailed description of the governed rebate accounting standard that the diagnostic tests against, see What Governed Rebate Accounting Looks Like.
For current Aurgus pricing, see aurgus.com/pricing/.
For a complete picture of what the evaluation process looks like before any commitment, see Why Aurgus Publishes Its Methodology.
For a full description of the first exchange — before the diagnostic — see What Happens After You Reply to Aurgus.