How to test variable consideration in a revenue contract under Ind AS 115

Testing variable consideration means testing, for every contract term that makes the transaction price uncertain — a volume rebate, a prompt-payment discount, a performance bonus, or a late-delivery penalty — that the entity estimated the expected amount using either the expected value method or the most-likely-amount method, whichever better predicts the consideration the entity will actually be entitled to, and then applied the constraint: including in the transaction price only the amount for which it is highly probable that a significant reversal will not occur when the uncertainty is resolved.

Why the constraint is a separate test, not a rounding adjustment

An entity can produce a mathematically sound expected value for a rebate and still overstate revenue, because Ind AS 115 does not allow the full expected value to be recognised where there is meaningful uncertainty about whether it will hold. The constraint is a deliberate downward adjustment built into the standard, and testing whether it was applied — not just whether the underlying estimate was computed correctly — is where this procedure earns its place.

The testing sequence

1. 01Identify every contract term that creates variability in the priceVolume-based rebates that step up with cumulative purchases, early-payment or trade discounts, rights of price protection, performance bonuses, and liquidated-damages or penalty clauses for late delivery, each read from the actual contract wording rather than assumed from the contract type.
2. 02Determine which estimation method the entity used and whether it fits the fact patternThe expected value method, a probability-weighted average, suits a contract with a large number of similar outcomes — a volume rebate across many customers. The most-likely-amount method suits a contract with only two possible outcomes — a bonus that is either earned in full or not earned at all. Using the wrong method for the fact pattern is a common source of a misestimate.
3. 03Recompute the estimate independently from the contract terms and the entity's own dataFor a volume rebate, recompute using the customer's actual purchase trajectory and the tiered rebate schedule in the contract; for a performance bonus, recompute using the entity's own track record of meeting or missing that specific performance measure.
4. 04Test whether the constraint was applied and how it was calibratedLook for factors Ind AS 115 specifically flags as increasing the likelihood of a significant reversal — high susceptibility to factors outside the entity's influence, a long period before the uncertainty resolves, limited experience with similar contracts, or a broad range of possible outcomes — and test whether the entity's constrained estimate reflects them.
5. 05Test the entity's own history of estimate reversalsCompare prior-period variable consideration estimates to the amounts that actually settled. A pattern of estimates that consistently needed significant downward revision after the uncertainty resolved is direct evidence the constraint has not been applied tightly enough.
6. 06Recompute the refund liability or rebate accrual arising from the constrained estimateThe liability recognised for amounts not yet paid out, or the contra-revenue accrual, should tie to the constrained transaction price, not to the unconstrained expected value.
7. 07Reassess the estimate at each reporting date, not just at contract inceptionVariable consideration is updated at the end of each reporting period as uncertainty resolves or new information becomes available; an estimate carried forward unchanged from an earlier period despite new actual data is itself an exception.