Hypothetical worked example and primary educational references; not observed market data.
Separate receipt from performance
A customer can pay before a business satisfies its contractual promises. The cash receipt then comes with an obligation to deliver goods or services, rather than automatically creating earned revenue for the full amount. IFRS 15's overview connects recognition to performance obligations and transfer of control in its framework; US Topic 606 is related but not identical in every application. The analytical distinction is between collecting money and completing the activity that earns it. Advance payment can improve current liquidity, but it also commits future resources. A business receiving more customer cash is not necessarily earning an equal amount of current profit.
Supporting references: 1. IFRS Foundation: IFRS 15
Follow a hypothetical annual subscription
Suppose a service provider receives USD 1,200 upfront for twelve months of a single service assumed to be delivered evenly. Under the simplified model, monthly revenue is 100. After three months, cumulative revenue is 300 and the remaining contract liability is 900. After six months, cumulative revenue is 600 and the liability is 600. The original cash receipt remains 1,200 before costs and other movements. This pattern assumes even service delivery and no separate obligations, refunds, or variable terms. A real subscription may contain implementation, support, licenses, or other promises requiring a more detailed assessment.
Supporting references: 2. IFRS Foundation: IAS 7
Hypothetical worked example
Hypothetical evenly delivered annual service
Model setup
Read these assumptions before comparing the scenarios.
- All monetary amounts in this example are hypothetical U.S. dollars (USD), not current prices, quoted account terms or observed market data. Percentages, counts, time periods and index levels retain their stated units.
- Customer pays USD 1,200 upfront for twelve months.
- A single service is assumed to transfer evenly; no refunds, financing component, or other obligations.
Remaining liability (USD)
- 1. 3 months
- 900.00
- 2. 6 months
- 600.00
Shared zero-based value scale. Range: 0.00 to 900.00, in the units above. Case numbers match the labels; no probability or time trend is implied.
Hypothetical model, not observed market data or a forecast. Assumptions above; original values and calculations below.
| Elapsed service | Cash received to date (USD) | Revenue to date (USD) | Remaining liability (USD) |
|---|---|---|---|
| 3 months | 1,200 | 300 | 900 |
| 6 months | 1,200 | 600 | 600 |
Calculation details
- Three-month revenue
- 300.00 USD
((1200 / 12) * 3) - Six-month remaining liability
- 600.00 USD
(1200 - ((1200 / 12) * 6))
Interpret the liability commercially
A contract liability indicates promises associated with consideration received or due under the relevant recognition framework. It is not always equivalent to an ordinary bank debt requiring repayment of the same amount. Fulfillment may cost less than the liability amount, but refunds or cancellation terms can change the cash exposure. Examine contract terms and the costs needed to provide service. A business with heavy future labor needs may have less freely usable prepayment cash than a business whose incremental delivery cost is small. Do not apply a single liability haircut without evidence. The economic obligation depends on what has been promised and what resources fulfillment consumes.
Supporting references: 2. IFRS Foundation: IAS 7
Distinguish growth from timing effects
A rise in contract liabilities can reflect new customers, longer prepaid terms, renewal timing, or a changed billing policy. Those mechanisms have different implications. Asking existing customers to pay earlier can boost current operating cash without increasing annual service demand. A surge of new annual contracts can increase both future revenue obligations and the resources needed to serve them. Compare contract liability changes with revenue, cash receipts, and disclosed activity measures where available. The balance alone cannot establish customer retention or demand quality. A billing change may improve liquidity legitimately while still requiring a clear distinction from underlying business growth.
Supporting references: 2. IFRS Foundation: IAS 7
Avoid double counting future revenue and cash
When valuing a prepaid business, future recognized revenue from an existing contract may not produce a second customer receipt because cash was already collected. A forecast that treats all future revenue as new cash and also adds the original cash separately can overstate value. Model the cash and fulfillment obligations consistently. Likewise, reducing a contract liability through service delivery can increase recognized revenue without a current collection. IAS 7 provides cash-flow context, but the analyst must build the revenue-to-cash bridge. The hypothetical subscription illustrates the simplest version of that timing issue without introducing a valuation estimate.
Supporting references: 2. IFRS Foundation: IAS 7
Read prepayment strength with execution risk
Customer prepayment can reduce working-capital funding needs and indicate willingness to commit, but it does not eliminate refund exposure, service costs, or operational failure. A growing prepaid balance can support liquidity today while increasing the amount of work owed tomorrow. Read the revenue policy, liability roll-forward, and fulfillment commitments together. The example excludes separate performance obligations and assumes even delivery solely to make the mechanism visible. A useful conclusion states how much cash arrived, how much performance occurred, what remains owed, and which contract terms could alter the result. This keeps advance receipts connected to the obligation rather than treating them as unqualified profit.
Supporting references: 2. IFRS Foundation: IAS 7
Test another situationReserve fulfillment cash after a prepayment
A separate hypothetical case. Its inputs differ from the main worked example above.
Reserve fulfillment cash after a prepayment
Suppose a hypothetical customer prepays USD 2,400 today for a single twelve-month service delivered evenly. After three months, recognized revenue is USD 600 and the remaining contract liability is USD 1,800. Assume fulfillment costs USD 100 in cash each month, including the remaining nine months. Those future service payments total USD 900. The liability and expected fulfillment cash are different amounts with different meanings. Prepayment improves funding, but treating all bank cash as surplus would overlook the service still owed. No refunds, financing component, separate setup promise, or tax effects enter this constructed case, and no customer renewal is assumed.
Supporting references: 1. IFRS Foundation: IFRS 15
Keep revenue release separate from new receipts
IFRS 15 links recognition to performance. Build the later forecast so delivery releases the existing liability without assuming another collection for the same service. Separately model receipts from new contracts or renewals and the costs of their own promises. If a prepaid balance is added as excess cash in valuation while all later service revenue is also treated as a new receipt, the contract is counted twice. For liquidity, inspect refund terms and whether service costs rise when staffing capacity is reached. A low cash fulfillment estimate is not evidence that the full liability can safely be distributed.
Supporting references: 1. IFRS Foundation: IFRS 15
Check this case’s calculations
- Revenue after three service months
- 600.00 USD
((2400 / 12) * 3) - Remaining service liability
- 1,800.00 USD
(2400 - ((2400 / 12) * 3)) - Future fulfillment payments
- 900.00 USD
((12 - 3) * 100)
Limits of this additional case
- Even service transfer and constant monthly costs are stipulated; cancellation, refund, and staffing-step exposure can change available cash.
Limits of this analysis
- Real contracts may contain multiple obligations and nonuniform delivery patterns.
- Refund, cancellation, and variable-price terms can alter cash exposure.
- Future revenue from prepaid contracts may not generate a second cash receipt.
Sources and scope
- IFRS Foundation: IFRS 15
Performance obligations, transaction price and transfer of control.
Scope: IFRS overview; US Topic 606 is related but not identical in every application.. Reference accessed 2026-10-06.
- IFRS Foundation: IAS 7
Cash flow presentation and the operating, investing and financing categories.
Scope: IFRS overview; classification details and US GAAP may differ.. Reference accessed 2026-10-06.
Illustrative calculations are not forecasts or personal recommendations. Editorial standards
