Contract assets on ramped and price-escalating multi-year contracts

Multi-year SaaS contracts that ramp seat counts or step up pricing over time typically represent a single performance obligation delivered evenly, so revenue is recognized on a straight-line (or blended) basis over the term rather than mirroring the annual billing schedule; this creates a contract asset that builds up in early ramp years and unwinds in later years, and mistaking that contract asset for a simple receivable misstates both the balance sheet and the credit risk profile of the balance.

Does the ramp in seat count or pricing represent a single performance obligation delivered evenly, or genuinely distinct annual services with different scope each year? If a single obligation, is the blended straight-line revenue rate calculated as total consideration divided by the contract term, applied consistently regardless of the annual billing amount? Is the resulting contract asset balance clearly distinguished from an unconditional right to bill (a receivable), based on whether only the passage of time is required for payment?

1. Determine whether the ramp represents a single performance obligation (e.g., access to the platform regardless of the number of seats actually activated in a given year, where the ramp is really a pricing mechanism rather than a change in what is being delivered) or genuinely distinct annual services with different scope each year.
2. Where it is a single obligation delivered evenly, calculate the blended average transaction price by dividing the total contract consideration by the total contract term, rather than using the amount billable in each individual year.
3. Recognize revenue each period at this blended straight-line rate regardless of the invoicing schedule for that year.
4. Recognize the excess of cumulative revenue recognized over cumulative amounts billed as a contract asset in the earlier, under-billed years of the ramp.
5. As billing catches up and eventually overtakes the straight-line revenue pattern in later years, draw down the contract asset systematically until it reaches zero by the end of the contract term.
6. Continuously monitor whether the pattern of benefit is genuinely even; if the ramp instead reflects materially different service scope or intensity each year (not just seat count under one access right), reassess whether straight-line recognition remains appropriate or whether a different measure of progress better depicts delivery.

Measure the blended straight-line revenue rate as total contract consideration divided by the contract term in periods, applied consistently regardless of the annual billing amount. Track the contract asset balance each period as the cumulative excess of revenue recognized over cumulative billings, distinct from and not commingled with trade receivables arising from amounts already invoiced and unconditionally due. Apply the IFRS 9 simplified expected credit loss approach to the contract asset, using a risk profile appropriate to unbilled amounts rather than assuming it mirrors the billed receivables' aging, and monitor for indicators that collectibility of the full contract term has deteriorated (e.g., early signs the customer may not renew or complete the ramp).

Disclose: significant contract assets presented separately from trade receivables on the face of the statement of financial position or in the notes; the ramp or price-escalation mechanics driving the contract asset balance; the policy for determining whether a ramped arrangement is a single performance obligation with blended pricing; the expected pattern of contract asset build-up and unwind over the contract term; the ECL methodology and allowance applied to the contract asset.

• Recognizing revenue equal to the annual billed amount in each ramp year, mirroring invoicing rather than the blended straight-line pattern, which back-loads revenue recognition inappropriately
• treating the resulting contract asset as an ordinary trade receivable and including it in ECL aging analysis by invoice date rather than assessing its own risk profile
• failing to recognize that a ramp is really pricing mechanics within a single obligation and instead incorrectly treating each contract year as a separate, distinct performance obligation
• not monitoring the contract asset for impairment indicators separately from the receivables population
• miscalculating the blended rate by using only the final year'
• s price rather than the total consideration divided by total term.