Rebate accounting under IFRS
The rebate money you’ve earned — or owe — is an estimate you have to re-prove every close. Under IFRS 15 a customer rebate is variable consideration, included only to the extent it’s highly probable no significant reversal will follow; a supplier rebate reduces inventory cost under IAS 2. Both are judgment, reassessed each period — and that gap between the booked estimate and the truth is where margin quietly leaks.
IFRS 15: a rebate is variable consideration
When you grant customers rebates, billbacks, volume incentives or price concessions, IFRS 15 treats them as variable consideration — paragraphs 50–51 name rebates, discounts, refunds, credits and incentives explicitly. You don’t wait for the money to settle; you estimate it and reduce revenue now.
You estimate it two ways
IFRS 15.53 gives you a choice of method, applied consistently: the expected-value method (a probability-weighted amount across many similar contracts — the natural fit for a volume-rebate program spanning many customers), or the most-likely-amount method (a single outcome — the fit when a bonus is simply earned or not).
The constraint is the brake
IFRS 15.56 lets you include that estimate in the transaction price only to the extent it is “highly probable” that a significant reversal of cumulative revenue will not occur once the uncertainty resolves. Long horizons, limited history, outcomes outside your control, and a habit of granting concessions all push you to constrain more.
And you re-prove it every period
IFRS 15.59 requires you to update the estimate — and re-run the constraint — at the end of every reporting period. An accrual that is rolled forward unchanged instead of re-derived from current attainment data is exactly what an auditor circles.
Some billbacks and co-op payments are paid to the customer. IFRS 15.70–72 treats consideration payable to a customer as a reduction of revenue — unless it buys a distinct good or service from them, at no more than fair value.
Source: IFRS Foundation, IFRS 15 Revenue from Contracts with Customers. Paragraph references 50–51, 53, 56, 59 and 70–72.
IAS 2: a supplier rebate reduces inventory cost
Rebates you receive from suppliers are a different question with a different home. IAS 2.11 states that “trade discounts, rebates and other similar items are deducted in determining the costs of purchase” of inventories — so the rebate reduces inventory carrying value and reaches the P&L as cost of sales only as that inventory is sold.
There is no single IFRS standard for it
Unlike US GAAP, IFRS has no dedicated standard for payments received from suppliers (“vendor allowances”). The treatment is a documented judgment under IAS 2, drawing on IFRS 15 by analogy. A widely-used Big 4 interpretation tests the substance in three steps: is the payment for a distinct good or service you provide back (then it’s revenue), a reimbursement of a specific cost (then it offsets that cost), or — the default — a discount on the goods (then it reduces purchase price and inventory cost)?
The allocation nobody wants to do
A volume rebate earned across a period has to be split between the inventory still on hand and the goods already sold: the first reduces the balance-sheet carrying value, the second reduces cost of sales. Pushing the whole rebate into COGS when some related stock is unsold misstates both margin and inventory.
Sources: IFRS Foundation, IAS 2 Inventories (para 11); EY, Applying IFRS: Accounting for payments from suppliers (Jan 2024). The three-step framework is a Big 4 technical interpretation, not a numbered IFRS requirement.
IFRS vs US GAAP: converged on revenue, split on supplier rebates
If you report under both IFRS and US GAAP, the customer side is substantially converged — the same five-step model, the same two estimation methods, the same constraint concept, the same reassess-every-period rule. The one wording difference that matters: IFRS 15 uses “highly probable” where ASC 606 uses “probable”. The boards chose different words but expected broadly similar outcomes, so in edge cases IFRS may defer slightly more variable revenue.
The supplier side genuinely diverges. US GAAP gives you a codified, bright-line rule — ASC 705-20 — presuming vendor consideration reduces the purchase price unless it meets specific exceptions. IFRS gives you IAS 2 plus judgment. The economic answer usually lands in the same place; the documentation burden does not. Dual filers end up maintaining both views of the same rebate and reconciling them.
The estimate is right on day one — and drifts from there
None of the following is a software requirement written into a standard. They are simply the places IFRS-reporting manufacturers and distributors tend to struggle, and where audit findings cluster:
- 1Re-estimating every close. Updating attainment and re-running the constraint each period (IFRS 15.59) — not rolling a static accrual forward.
- 2Retroactive tiers. Crossing a threshold that re-prices the whole period to dollar one forces a full recompute — with the reason, effective date, and before/after amounts preserved.
- 3Tracing the number. Walking one accrual back to the source transactions, the agreement clause, the rate, and the approval that produced it — most ERPs store the net figure, not the lineage.
- 4Inventory-cost allocation. Splitting a supplier rebate between unsold inventory and goods already sold, per IAS 2.
- 5Dual-GAAP reconciliation. Holding an IFRS “highly probable” view and a US GAAP “probable” view of the same accrual, reconciled with a documented bridge.
- 6Capturing the judgment. Because IFRS lacks ASC 705-20’s bright lines, the rationale itself has to be recorded — findings often arise not because the number is wrong but because the reasoning was never written down.
Where Aurgus fits. Aurgus is designed to work alongside the ERP you already run — reading its contracts, sales, claims and settlements, governing the rebate and incentive calculation outside it under IFRS 15 and IAS 2 (and ASC 606 / ASC 705-20 for dual filers), surfacing the estimate and its exceptions for a human to approve, and tying every number back to its source rows, the rule that fired, and the approval. It writes nothing back to your general ledger.
Rebates are an indirect-tax event too
The same post-supply discount that adjusts your revenue under IFRS 15 often has to be mirrored in GST or VAT — with its own conditions, credit-note mechanics, and time limits. Two jurisdictions where that trips companies up:
Questions teams ask
- How are customer rebates treated under IFRS 15?
- As variable consideration (IFRS 15.50–51), estimated by expected value or most-likely-amount (.53), included only to the extent a significant reversal is highly probable not to occur (.56), and reassessed every reporting period (.59).
- Do supplier rebates reduce revenue or inventory under IFRS?
- Inventory cost, not revenue. IAS 2.11 deducts trade discounts and rebates from the cost of purchase; the rebate reaches cost of sales as the inventory is sold. IFRS has no single vendor-allowance standard, so it’s a documented judgment.
- How does IFRS 15 differ from ASC 606 / ASC 705-20?
- Customer-side is substantially converged, with “highly probable” (IFRS) vs “probable” (US GAAP) the main wording difference. Vendor-side diverges: US GAAP’s ASC 705-20 is a codified bright-line rule; IFRS relies on IAS 2 plus judgment.
- How often must rebate estimates be reassessed?
- Every reporting period. IFRS 15.59 requires updating the estimate and re-running the constraint; a static, rolled-forward accrual is a common audit red flag.
Start with your own number
Estimate what may be leaking from your rebate programs in two minutes — no login, result on the page — then see how a governed calculation layer keeps the IFRS estimate honest every close.
Educational summary, not accounting advice. Standard references (IFRS 15, IAS 2) are to the IFRS Foundation texts; confirm paragraph numbers and treatment against the current standards and your auditor. Aurgus is in the design-partner phase.
Aurgus runs the rebate logic — agreements, tiers, accruals, claims, and the audit trail — alongside whatever ERP you run. Every number traces to its source rows, the rule that fired, and the approval.
Aurgus is in the design-partner phase. No delivered-customer outcomes are claimed; everything shown runs on synthetic data.
A product of MyDealsGroup LLC, Austin, TX. Aurgus works alongside the ERP you already run and is not affiliated with any standard-setter. IFRS and IAS are standards of the IFRS Foundation.