Revenue recognition under ASC 606 and IFRS 15

Key takeaways

• ASC 606 and IFRS 15 apply one five-step model: identify the contract, identify performance obligations, set the transaction price, allocate it, and recognize revenue as each obligation is satisfied.
• A bundled price is split across distinct performance obligations in proportion to their standalone selling prices, so a discount is normally spread across every element.
• Revenue is recognized over time only if one of three criteria is met; otherwise it is recognized at the point control passes to the customer.
• A principal reports revenue gross and its costs separately; an agent reports only its net fee, which leaves gross profit unchanged but changes revenue and margins dramatically.
• Variable consideration is estimated by expected value or most likely amount and then constrained, so revenue that could reverse significantly is held back.
• Contract assets and contract liabilities record the gap between revenue recognized and amounts billed, and their movement is where aggressive recognition usually shows first.

The five-step model

Both standards organize revenue around the contract with a customer. A contract is an agreement between two or more parties that creates enforceable rights and obligations. It does not need to be written: a verbal agreement or an established business practice can qualify, as long as the parties have approved it, each party's rights and the payment terms can be identified, the contract has commercial substance, and it is probable that the company will collect the consideration it is entitled to.

The model then asks four more questions in order. What distinct promises did the company make? How much consideration does it expect to receive? How should that amount be divided among the promises? And when is each promise fulfilled? The answers produce the amount and timing of revenue for the life of the contract.

The core principle behind the steps is stated in both standards in almost identical words: a company recognizes revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which it expects to be entitled. Transfer happens when the customer obtains control, meaning the ability to direct the use of the asset and obtain substantially all of its remaining benefits. Control, not the transfer of risks and rewards and not the receipt of cash, is the test.

Performance obligations: what counts as distinct

A performance obligation is a promise to transfer a good or service that is distinct. A good or service is distinct if two conditions are both met. First, it is capable of being distinct: the customer can benefit from it on its own or together with resources readily available, such as goods sold separately by the company or by others. Second, it is distinct in the context of the contract: the promise is separately identifiable rather than an input into a combined output the customer actually bought.

The second condition is where the judgment lies. A machine sold with installation any competent contractor could perform is two performance obligations. A custom production line that integrates equipment, software and significant engineering into one working system is one, because the customer is buying the integrated output.

Some promises are easy to miss. An extended warranty that goes beyond assuring the product works as specified is a separate service obligation. So is a material right, such as a future discount the customer would not get without this contract. Internal setup activities, by contrast, transfer nothing to the customer and carry no revenue.

Transaction price and allocation

The transaction price is the consideration the company expects to be entitled to for the promised goods or services. It excludes amounts collected for third parties, such as sales taxes, includes variable elements (covered below), and is adjusted for a significant financing component, which both standards let a company ignore when payment and transfer are one year or less apart.

When a contract has more than one performance obligation, the price is allocated in proportion to each obligation's standalone selling price (SSP), the price at which the company would sell that good or service separately. The best evidence is an observable price from standalone sales. Where none exists, the company estimates it, using an adjusted market assessment (what competitors charge), expected cost plus a margin, or, only in limited circumstances, a residual approach that assigns what is left after the observable prices.

The consequence of proportional allocation is that a bundle discount is spread across every element, unless there is observable evidence that the discount relates entirely to specific items. That matters for timing. If an element delivered on day one absorbs part of a discount that economically relates to a service delivered over two years, less revenue is recognized up front than the invoice schedule might suggest.

Point in time or over time

Step five asks when each performance obligation is satisfied. The standards first test whether it is satisfied over time. It is, if any one of three criteria is met. First, the customer simultaneously receives and consumes the benefit as the company performs, as with cleaning, payroll processing or a software subscription. Second, the company's performance creates or enhances an asset the customer controls as it is built, such as a building on the customer's land. Third, the company's performance creates an asset with no alternative use to the company, and the company has an enforceable right to payment for performance completed to date, as with a highly customized product built to a contract that pays for work done if the customer cancels.

If none of the three is met, the obligation is satisfied at a point in time, when control passes. Indicators include a present right to payment, legal title, physical possession, the significant risks and rewards of ownership, and customer acceptance. No single indicator decides, and consignment and bill-and-hold arrangements (the customer is invoiced but the goods stay at the seller's site) need particular care.

For obligations satisfied over time, the company picks a measure of progress. Output methods use results delivered, such as milestones reached. Input methods use effort expended, most commonly cost-to-cost: costs incurred to date divided by total expected costs. It is simple, but it depends entirely on the estimate of total cost.

Principal or agent: gross versus net revenue

When a third party is involved in providing a good or service, the company must decide whether it is the principal, which promises to provide the good or service itself, or an agent, which arranges for another party to provide it. A principal reports revenue at the gross amount the customer pays and records the amount paid to the supplier as a cost. An agent reports revenue at the net amount it keeps, its fee or commission.

The deciding question is whether the company controls the specified good or service before it is transferred to the customer. Both standards list indicators that support control: the company is primarily responsible for fulfilling the promise, it bears inventory risk before or after transfer, and it has discretion in setting the price. Credit risk was an indicator under the old US rules but is no longer one. The assessment is made for each specified good or service, so a company can be principal for some sales and agent for others.

The choice leaves gross profit and cash flow untouched but changes revenue, gross margin, growth and every revenue multiple. It matters most for marketplaces, travel platforms, advertising networks and software resellers.

Variable consideration and the constraint

Consideration is variable when the amount the company will receive depends on future events. Volume rebates, prompt payment discounts, performance bonuses, penalties for late delivery, price concessions, rights of return and usage-based fees are all variable. The company estimates the amount it expects to be entitled to at contract inception and updates the estimate every reporting period.

The standards allow two estimation methods, and the company uses whichever better predicts the amount. The expected value method, a probability-weighted sum of possible outcomes, suits a large number of similar contracts or a range of possible outcomes. The most likely amount method, the single most likely outcome, suits binary situations such as a bonus that is either earned in full or not at all.

The estimate is then constrained. Variable consideration is included in the transaction price only to the extent that it is highly probable (IFRS 15) or probable (ASC 606) that a significant reversal of cumulative revenue will not occur when the uncertainty is resolved. The words differ, but the boards intended the same threshold. Reversal is more likely when the amount depends on factors outside the company's control, resolution is far away, or experience with similar contracts is limited.

Contract assets, contract liabilities and receivables

Revenue recognition and billing run on separate clocks, and the balance sheet records the gap. A receivable is a right to consideration that is unconditional, meaning only the passage of time is required before payment is due. A contract asset is a right to consideration that is conditional on something other than time, typically further performance: revenue has been recognized but the company is not yet entitled to invoice it. A contract liability, which most US filers still label deferred revenue, is an obligation to transfer goods or services for which the customer has already paid or for which payment is already due.

Contracts are presented net: a single contract is either a net contract asset or a net contract liability at any date. The movements are disclosed in the notes, and the roll forward of these balances is one of the richest sources of information about how revenue is being recognized.

The same revenue can create very different balances depending on billing terms: an annual subscription billed in advance creates a contract liability, while a project billed on milestones usually carries a contract asset between them.

What a diligence team checks

A quality of earnings review in a buyout, or a lender's diligence ahead of a financing, does not re-audit revenue. It tests whether reported revenue is real, correctly timed and repeatable. The first test is a proof of cash: reconciling revenue recognized to cash collected, adjusted for the change in receivables, contract assets and contract liabilities. Revenue that cannot be traced to cash over a reasonable period deserves an explanation.

The second is cut-off. Teams look at sales in the last weeks before a period end and credit notes, returns or reversals in the weeks after. A spike in shipments before quarter end followed by returns is the classic sign that revenue was pulled forward. Bill-and-hold arrangements, shipments to distributors with generous return rights, and contracts signed after period end but dated before it all surface here.

The third is contract review. Teams read a sample of large contracts in full, including amendments and side letters, and check that performance obligations, variable consideration and principal or agent conclusions match what was booked. Long-term contracts get extra attention: the history of estimate revisions shows whether management's cost forecasts are reliable, and loss-making contracts should already carry a provision.

Finally, teams ask what the accounting implies for the buyer's model. Moving customers from annual upfront billing to monthly billing after closing leaves revenue unchanged while consuming cash, and deferred revenue raises a purchase price question: working capital or a debt-like item.