Customer rebates, promotional allowances, distributor incentives and payments made to support a retailer’s promotion can look like selling costs in a commercial plan. For financial reporting, however, the label in the sales agreement or ERP is not decisive. The controller needs to understand who receives the benefit, why the payment is made, how it relates to a revenue contract and whether the amount should reduce revenue or represent a purchase of a distinct good or service.
This issue is especially timely for US GAAP reporters. On October 22, 2026, the Financial Accounting Standards Board (FASB) issued a proposed Accounting Standards Update on payments made on behalf of a customer or to a customer of the entity’s customer. The proposal is open for comment through November 23, 2026. It is a proposal—not a final amendment—and companies should continue to apply the guidance currently in force while monitoring developments.
For controllers, the immediate opportunity is practical: make sure commercial incentives are complete, consistently classified, reasonably estimated, approved and supported before the close.
1. Build a complete inventory of customer-related payments
Start with the economic substance of payments, not just the general-ledger account name. Common arrangements include:
- Volume rebates, tiered discounts and annual growth incentives.
- Promotional allowances, advertising support and co-operative marketing funds.
- Credits, coupons, refunds, price protection and post-sale concessions.
- Payments to distributors, retailers or other parties in the distribution chain.
- Payments made on a customer’s behalf, including support routed through another party.
- Amounts described as service fees where the customer may also be providing a distinct service.
Reconcile the inventory to sales agreements, rebate-management systems, trade-promotion tools, accounts-payable data, credit notes, manual journal entries and legal or commercial side letters. A payment can be missed if the team searches only for accounts labelled “rebates.”
2. Determine whether the payment is linked to a customer relationship
For each arrangement, document the parties, the commercial purpose, the contract or contracts involved, the triggering event and the expected beneficiary. The critical question is not simply “Who receives the cash?” but “Why is the entity paying, and how is that payment connected to the promise made to its customer?”
The FASB’s October 22, 2026 proposal addresses an area where Topic 606 does not explicitly resolve every situation involving payments made on behalf of a customer or to a customer’s customer. The proposal would clarify when such payments are treated as consideration payable to a customer if they are made in connection with satisfying the entity’s promise to its customer and an explicit promise, implicit promise or in-substance price concession is present. Because this is proposed guidance, do not treat it as a new requirement before it is finalized and applicable.
Practical example: a manufacturer sells through a distributor and funds a retail promotion. The retailer may not purchase directly from the manufacturer. Finance should still assess the contractual chain, the purpose of the promotion and any promises or customary practices—not automatically classify the payment as advertising expense because the retailer is the payee.
3. Test whether a distinct good or service is actually received
Under US GAAP Topic 606, consideration payable to a customer generally reduces the transaction price and revenue unless the payment is in exchange for a distinct good or service transferred to the entity by the customer. If a genuine distinct service is acquired, the accounting is not automatically the same as a rebate; the controller needs evidence of what was received and an appropriate basis for measuring it. Any amount above the fair value of that distinct good or service is accounted for as a reduction of the transaction price under the applicable guidance.
Ask the business owner to provide tangible evidence: defined deliverables, dates, audience or placement data, campaign reports, service-level records, or other proof that the entity received the promised benefit. A contract that merely calls a payment “marketing services” is not enough by itself. If the entity cannot demonstrate a distinct service, escalate the classification for technical-accounting review.
Useful reference: the FASB’s Topic 606 revenue-recognition project overview summarizes the standard’s purpose and scope. Consult the authoritative FASB Accounting Standards Codification for the detailed requirements applicable to the reporting entity.
4. Estimate variable amounts before the period closes
Rebates and incentives often depend on cumulative sales, volume tiers, market-share targets, returns or other conditions. Waiting until the customer submits a claim can understate the liability or overstate net revenue if the underlying obligation has already arisen under the applicable accounting model.
Design a repeatable estimate that identifies:
- The eligible sales population and the period covered by each program.
- The contractual threshold, tier or formula and the evidence supporting expected attainment.
- Returns, cancellations, credits and other adjustments that affect the calculation.
- Any uncertainty, constraint or judgment required by the applicable revenue standard.
- The data source, calculation version, preparer, reviewer and date of approval.
For example, if a distributor has achieved most of an annual volume threshold by quarter-end, finance should calculate the expected rebate using validated sales data and the contract terms. It should not default to zero merely because the final annual claim has not arrived. Conversely, the estimate should not assume the highest tier without evidence that it is supportable.
5. Separate the accounting analysis by reporting framework
US GAAP and IFRS have closely related revenue models, but controllers should use the requirements applicable to each reporting entity rather than assume every detail is identical.
- US GAAP: Apply ASC Topic 606, including the guidance on consideration payable to a customer and the relevant variable-consideration requirements. Track the FASB proposal dated October 22, 2026 separately from requirements currently in force; the proposal’s comment deadline is November 23, 2026.
- IFRS: IFRS 15 paragraphs 70–72 address consideration payable to a customer, including certain payments to parties that purchase the entity’s goods or services from the customer. The standard generally treats such consideration as a reduction of the transaction price unless it is payment for a distinct good or service, subject to the detailed requirements. See the IFRS Foundation’s IFRS 15 overview.
- Canadian ASPE: Do not import ASC 606 or IFRS 15 conclusions automatically. Assess the applicable requirements of Section 3400, Revenue, and the entity’s facts. CPA Canada’s ASPE Section 3400 briefing provides additional guidance on revenue-recognition issues. Obtain current technical advice where a complex incentive arrangement is material.
For a group reporting under more than one framework, maintain a documented framework-by-framework conclusion and a controlled reconciliation of any differences. One global rebate calculation may be operationally useful, but the accounting memo should identify which rules support each reported result.
6. Connect commercial terms to ERP and close controls
In SAP or another ERP, a strong control starts before posting. Link each approved incentive program to a unique program or contract identifier, customer and relevant distribution partner, effective dates, eligible products, calculation basis, currency, approval evidence and accounting treatment. Restrict changes to rates, thresholds and dates; retain a change log and independent approval.
At month-end, reconcile the rebate subledger or trade-promotion system to the general ledger. Investigate differences between estimated accruals, credit notes issued, cash settlements and amounts claimed. Check for expired programs that remain active, overlapping programs, duplicate claims, manual postings outside the normal workflow and payments that lack a contract reference.
Where sales and rebate data move between CRM, pricing, trade-promotion, billing and finance systems, control interface completeness and rejected records. A reconciliation that proves only that two totals agree may miss errors if both systems omit the same population. Include record counts, key-field validation and exception follow-up.
7. Create an audit-ready evidence file
For each material program, retain the approved contract or program terms, commercial rationale, distinct-service assessment if relevant, calculation and source data, assumptions, sensitivity or threshold analysis, accounting conclusion, journal entry, reviewer sign-off and reconciliation to settlement. Keep evidence of subsequent credit notes and cash payments so the team can compare estimates with outcomes and refine the process.
Use a risk-based review. Prioritize large or unusual programs, manual overrides, new distribution channels, payments to parties outside the direct customer relationship, arrangements close to period-end and programs whose actual payouts repeatedly differ from accruals. Track exceptions to resolution rather than treating a review comment as closed merely because it was acknowledged.
Controller’s month-end checklist
| Control question | Evidence to retain |
|---|---|
| Are all material customer-related payments identified? | Reconciled program inventory, contracts, AP and credit-note data |
| Is the recipient and commercial purpose understood? | Distribution-chain map, rationale and approved terms |
| Is any claimed service distinct and supported? | Deliverables, service evidence and valuation analysis |
| Are variable amounts estimated consistently? | Eligible-sales data, formulas, assumptions and independent review |
| Is the framework conclusion documented? | ASC 606, IFRS 15 or ASPE analysis, as applicable |
| Do system balances reconcile and exceptions close? | Subledger-to-GL reconciliation, interface checks and issue log |
| Are new developments monitored? | Technical-accounting owner and documented assessment of relevant standard-setting updates |
Conclusion
Customer incentives sit at the intersection of commercial strategy, revenue recognition, systems and close discipline. Controllers can reduce misstatement risk by identifying payments broadly, understanding the economic relationship, distinguishing rebates from genuine purchases of services, estimating variable amounts using reliable data and retaining a clear audit trail. The FASB proposal issued on October 22, 2026 is a timely reason to review current processes, but it remains a proposal. Monitor its progress without prematurely changing accounting policy.
Informational only: This article is a practical control overview, not accounting, legal or tax advice. Apply the authoritative standards relevant to the reporting entity and obtain qualified advice for material or unusual arrangements.
