Three Systems, Three Numbers: Why Your Rebate Liability Doesn't Reconcile at Close
Somewhere in most channel-finance organizations, three numbers describe the same obligation, and they do not match. There is the rebate accrual finance carries on the balance sheet. There is the figure sales operations believes it owes, the one baked into its margin models and partner conversations. And there is the number the partners themselves will eventually claim, visible only when their statements and deduction notices arrive. Ask three people what the company owes its channel and you get three answers, each defensible in its own frame, none reconciling cleanly to the others.
The instinct is to treat the gap as an error — a reconciliation task, something a careful analyst should be able to chase to zero.
The gap is not an error. It's a structural feature of how the three numbers are produced.
Understanding why is the difference between chasing the gap every quarter and removing the reason it exists.
The three numbers, and why each is what it is
The finance number
Finance's best estimate, under ASC 606, of the variable consideration it will ultimately credit back1. Struck at a reporting date, constrained so a later reversal is improbable, and tuned to not overstate.
The sales-operations number
The figure baked into margin models and partner conversations. It runs richer than the accrual because it counts what finance's constraint excludes — the tier a partner is likely to hit but has not yet, the promotion verbally extended.
The partner number
What the distributor asserts it is owed, computed from their records of volume, price, and eligibility — records never reconciled to yours. Where it exceeds your accrual, you have a dispute; where it falls short, you may be over-accrued and not know it.
Three numbers, three different source datasets, three different timing conventions, three different readings of eligibility. They were never going to be equal. They were computed by three systems that share no common substrate.
Why they can't reconcile with the infrastructure most teams have
Reconciliation requires a shared spine — a common set of underlying facts that all three numbers can be traced back to and differenced against. The typical infrastructure has no such spine. Finance's accrual is computed in a spreadsheet or a period-end batch from an ERP export. Sales ops runs its own models against CRM data. The partner computes against records you never see until the claim lands. Each number is internally coherent and externally unanchored.
Two structural facts make it worse. The first is identity: the same product, partner, or transaction is keyed differently in each system, so even where the underlying event is identical, the systems cannot agree that it is identical — the hyphen in a product code is enough to break the join2. The second is time. Terms change mid-period, and most infrastructures record only the current terms. So when finance strikes the accrual under this quarter's terms and the partner claims under the terms in force when the sale actually happened, the two numbers are computed against different rulebooks — and nothing in the system remembers that the rulebook changed3. You cannot reconcile two numbers when the basis of one has been overwritten.
What the gap costs
An unreconciled gap is not a cosmetic problem. It has four distinct costs, and they compound.
Disputes and working capital. Every partner claim that exceeds your record becomes a dispute to work, and disputes tie up cash — the claim sits unpaid, the relationship frays, and the resolution consumes analyst time that produces nothing. The gap is a queue of future disputes you have not worked yet.
Audit variance. When the accrual and the eventual settlements diverge quarter after quarter, the variance band widens, and a widening band on a variable-consideration estimate is precisely what draws audit-committee and external-auditor attention under the ASC 606 constraint1. The gap you tolerate operationally becomes the variance you defend at audit.
Restatement risk. If the accrual has been systematically wrong in one direction — over- or under-stated because the three numbers never reconciled — the correction, when it comes, is a prior-period adjustment. That is the tail risk of the gap: not a hard quarter, but a restatement.
Decisions made on the wrong number. Sales ops prices and commits against its expectation; finance plans against its accrual; neither is the number the partners will actually claim. Every downstream decision inherits whichever of the three numbers happened to be at hand.
What one defensible number requires
The goal is not to force the three numbers to be equal — they answer slightly different questions and some spread is legitimate. The goal is a shared substrate that lets you decompose the gap: to say precisely how much of the difference between accrual and claim is timing, how much is an eligibility disagreement, how much is a terms-version mismatch, and how much is genuine error. A gap you can decompose is a gap you can defend and work down. A gap you can only observe is one you chase forever.
Three things are required for that substrate. Shared lineage: all three numbers computed from, or reconciled to, the same underlying transaction and terms records, so a difference can be traced to a specific cause rather than waved off as reconciliation noise. Identity resolution: a single mapping of products, partners, and transactions across systems, so the same real-world thing is recognized as the same thing regardless of how each source keyed it. Preserved history of terms: the ability to compute a number under the terms in force at any past moment, so accrual and claim can be compared on the same rulebook even after the rulebook has changed. With those three, the three numbers stop being three unrelated assertions and become one number with an explainable, worked-down variance around it.
Which of the three is your problem
Most organizations feel the gap without having localized it — they know the numbers do not tie out but not why, because localizing the cause requires exactly the shared lineage they lack. The first useful step is not a system; it is an honest read of where your own divergence comes from and how wide it runs.
If you already know the numbers don't reconcile and want to think through what closing the gap actually takes in your specific case — not a demo, a conversation in the same frame as this note — twenty minutes are on the calendar.
Footnotes
- FASB Accounting Standards Codification Topic 606, Revenue from Contracts with Customers. Channel rebates are variable consideration (ASC 606-10-32-5 through 32-10), estimated by expected value or most likely amount (32-8) and subject to the constraint (32-11 through 32-13) that limits included consideration to the amount for which a significant revenue reversal is not probable. A widening gap between accrued and settled amounts directly implicates the constraint.
- AIMDek Technologies, 10 Rebate Execution Failures Causing Revenue Loss, on product-identifier mismatch as a driver of valid-claim rejection and reconciliation failure. aimdek.com
- Enable, 7 Common Problems with Accounting for Rebates, on reconciliation failures and the difficulty of accounting for rebates when terms and program complexity outrun the supporting systems. enable.com