Revenue from Complex Contracts

Introduction

Revenue is often the largest and most closely scrutinized figure in financial statements. Complex contracts make its measurement difficult because a single arrangement may contain equipment, installation, software, support, warranties, bonuses, financing and later changes in scope. The accounting question is not merely when cash is received. It is when control of promised goods or services transfers to the customer and how much consideration should be attributed to that transfer.

IFRS 15 Revenue from Contracts with Customers and ASC 606 establish a substantially converged five-step model. This chapter primarily uses IFRS terminology while noting important jurisdictional considerations. Entities must consult the standards and applicable regulatory guidance when preparing financial statements.

Learning Objectives

After studying this chapter, students should be able to:

1. Apply the five-step revenue model to complex contracts.
2. identify performance obligations and allocate consideration using stand-alone selling prices.
3. Estimate variable consideration and apply the constraint.
4. Account for contract modifications and significant financing components.
5. Evaluate principal–agent relationships, warranties and licenses.
6. Recognize revenue from long-term contracts using appropriate progress measures.
7. Assess the ethical, governance and technological implications of revenue estimates.

1. The Five-Step Revenue Model

The core principle is that revenue depicts the transfer of promised goods or services to customers in an amount reflecting the consideration to which the entity expects to be entitled.

Figure: The five-step revenue recognition model.

Step 1: Identify the contract

A contract is accounted for under the revenue model only when:

• the parties have approved it and are committed to perform;
• each party’s enforceable rights can be identified;
• payment terms can be identified;
• the arrangement has commercial substance; and
• collection of the consideration to which the entity expects to be entitled is probable.

A contract may be written, oral or implied by customary business practice. Contracts entered into at or near the same time with the same customer may have to be combined when they were negotiated as a package, one contract’s consideration depends on another, or the promised goods and services form a single performance obligation.

Step 2: Identify performance obligations

A performance obligation is a promise to transfer either:

• a distinct good or service; or
• a series of substantially similar distinct goods or services transferred in the same pattern.

A promised item is distinct only if both conditions are satisfied:

1. Capable of being distinct: the customer can benefit from it independently or with other readily available resources.
2. Distinct within the context of the contract: the promise is separately identifiable from other promises.

The second condition prevents artificial separation of inputs used to produce one integrated output. Factors suggesting promises are not separately identifiable include significant integration, significant modification or customization, and high interdependence.

A server may therefore be capable of being distinct because it can operate with third-party software, but not distinct within a particular contract if the supplier integrates it with heavily customized software to provide one functional system. In that case, the server is an input to a combined performance obligation.

Administrative setup activities that do not transfer a service are not performance obligations. Conversely, a customer option may be a performance obligation if it gives the customer a material right, such as a discount unavailable without entering the original contract.

Step 3: Determine the transaction price

The transaction price is the consideration to which the entity expects to be entitled, excluding amounts collected for third parties. It may include fixed consideration, variable consideration, significant financing effects, non-cash consideration and consideration payable to the customer.

Step 4: Allocate the transaction price

The normal objective is to allocate consideration according to relative stand-alone selling prices (SSPs) at contract inception:

where:

• A_i = consideration allocated to performance obligation i, in currency units;
• T = transaction price to be allocated, in the same currency;
• SSP_i = stand-alone selling price of performance obligation i;
• j = index covering each performance obligation from 1 to n;
• n = total number of performance obligations; and
• ∑_j=1ⁿ SSP_j = sum of the SSPs of all performance obligations.

The formula assumes the consideration is allocated proportionately. A discount or variable amount is instead allocated entirely to one or more obligations when the relevant criteria demonstrate that doing so is consistent with the allocation objective.

If SSP is not directly observable, estimation methods include adjusted market assessment, expected cost plus margin, and—in limited circumstances—the residual approach. Estimation methods should maximize observable evidence and be applied consistently.

Worked example: relative SSP allocation

A contract includes equipment and maintenance for $250,000. Their SSPs are $240,000 and $60,000 respectively. Total SSP is $300,000.

The allocated amounts, rather than invoice labels, determine revenue for each performance obligation.

Step 5: Recognize revenue

Revenue is recognized when—or as—a performance obligation is satisfied through transfer of control. Control means the ability to direct use of, and obtain substantially all remaining benefits from, an asset while preventing others from doing so.

Revenue is recognized over time if at least one of these criteria is met:

1. the customer simultaneously receives and consumes benefits as the entity performs;
2. performance creates or enhances an asset controlled by the customer as it is created; or
3. performance creates an asset with no alternative use to the entity and the entity has an enforceable right to payment for performance completed to date.

If none applies, revenue is recognized at a point in time. Indicators include a present right to payment, legal title, physical possession, transfer of significant risks and rewards, and customer acceptance. These indicators support, but do not replace, the control assessment.

2. Variable Consideration and the Constraint

Variable consideration includes bonuses, penalties, rebates, returns, refunds, price concessions and usage-based charges. It is estimated using either the expected-value method or the most-likely-amount method, depending on which better predicts the amount of consideration.

For a range of probability-weighted outcomes:

where E(V) is expected variable consideration, v_k is outcome k in currency units, p_k is its probability, m is the number of possible outcomes, and ∑p_k = 1.

Example: A contractor may receive bonuses of $0, $20,000 or $50,000 with probabilities of 20%, 50% and 30%.

Estimation is not sufficient by itself. Variable consideration is included only to the extent that it is highly probable that a significant reversal of cumulative revenue will not occur when uncertainty is resolved. Relevant factors include susceptibility to external events, a long uncertainty period, limited experience, broad price concessions and numerous possible outcomes.

Estimates are reassessed at every reporting date. Under IFRS, “highly probable” expresses the constraint threshold; ASC 606 uses “probable” wording in this context but was designed to achieve a similar outcome given differences in the frameworks’ probability terminology.

For a license of intellectual property, consideration based predominantly on subsequent sales or usage is generally recognized only when the later sale or usage occurs and the associated performance obligation has been satisfied or partly satisfied. This sales- or usage-based royalty exception is not replaced by the ordinary expected-value calculation.

Returns also create separate accounting effects: revenue is recognized only for products expected not to be returned, a refund liability is recorded, and an asset is recognized for the right to recover returned products, adjusted for recovery costs and impairment.

3. Significant Financing Components

A contract contains a significant financing component when payment timing provides a significant financing benefit to either party. The entity adjusts promised consideration using the discount rate that would apply in a separate financing transaction at contract inception. The rate is not subsequently updated for changing interest rates or credit risk.

Factors include the difference between promised and cash selling prices, the time between transfer and payment, and prevailing market rates. No adjustment is required when payment and transfer are expected to differ by one year or less if the practical expedient is elected. A timing difference also may not represent financing—for example, when payment protects a party from non-performance or the variable timing is controlled by neither party.

Correct treatment of a customer prepayment

A customer prepays $110,000 two years before delivery. The arrangement provides financing to the entity. Assume a 5% annual effective financing rate and no other consideration.

The amount at delivery is:

Year 1 interest expense is $5,500; year 2 interest expense is $5,775. The accounting is:

Because the customer finances the entity, accretion creates interest expense, not interest income. By contrast, where the entity transfers goods before receiving substantially deferred payment, it generally recognizes interest income on a receivable.

4. Contract Modifications

A contract modification changes enforceable scope, price or both. Approval may be written, oral or implied by customary practice.

Separate contract treatment

A modification is treated as a separate contract if:

• it adds distinct goods or services; and
• the price increase reflects their SSP, adjusted where appropriate for contract circumstances.

Prospective treatment

If remaining goods or services are distinct from those already transferred but the added price does not reflect SSP, the original contract is treated as terminated and replaced prospectively. Remaining unrecognized consideration and modification consideration are allocated to remaining obligations.

Example: A customer originally buys 100 identical distinct units for $10 each. After 40 are delivered, 30 more are added for $8 each, although their SSP is $9. Assuming the pricing does not qualify as an SSP adjustment, remaining consideration is:

The prospective amount per remaining unit is:

Revenue already recognized for the first 40 units is not restated.

Cumulative catch-up treatment

If remaining goods or services are not distinct and form part of a partially satisfied performance obligation, the modification updates the existing obligation. Revenue is adjusted immediately on a cumulative catch-up basis.

Suppose a construction obligation originally had a $1,000,000 transaction price and estimated costs of $800,000. Costs incurred were $400,000, so progress and cumulative revenue were 50% and $500,000. A non-distinct modification increases consideration to $1,200,000 and estimated total cost to $1,000,000. Revised progress is 40%, producing cumulative revenue of $480,000. The entity records a $20,000 downward catch-up adjustment.

A mixed modification may require both approaches for different remaining promises.

5. Principal–Agent Relationships

When another party participates in providing goods or services, an entity determines whether it is a principal or agent for each specified good or service.

• A principal controls the specified good or service before transfer and recognizes gross revenue.
• An agent arranges for another party to provide it and recognizes the net fee or commission.

The assessment begins by identifying the specified good or service and evaluating control before transfer. Indicators supporting control include primary responsibility for fulfillment, inventory risk and discretion in setting price. They are not a checklist and are not individually conclusive.

Example: A platform collects $100 from a customer for a ticket supplied and controlled by an airline. It must remit $85 to the airline and has neither inventory risk nor responsibility for the flight. If the platform only arranges the sale, it recognizes revenue of $15, not $100. Cash collection alone does not make it the principal.

Judgment is particularly important for digital marketplaces, delivery applications, travel intermediaries and cloud resellers. The unit of account matters: an entity may be principal for one service, such as payment processing, and agent for another, such as third-party transport.

6. Warranties

Warranty accounting depends on the nature of the promise.

An assurance warranty confirms compliance with agreed specifications. A service warranty provides an additional service beyond basic assurance. Factors include legal requirements, coverage length and the nature of promised tasks.

A warranty may contain both assurance and service elements. The entity accounts for them separately when it can reasonably do so. If the assurance and service components cannot reasonably be accounted for separately, they are combined and accounted for as a single performance obligation. This prevents an arbitrary split unsupported by reliable evidence.

For example, a statutory 90-day defect warranty is normally assurance. An optional three-year maintenance plan that includes preventive servicing is a service. If one inseparable warranty package provides defect protection and substantive maintenance, the combined warranty is treated as one performance obligation.

7. Licensing

A license gives a customer rights to intellectual property (IP), such as software, patents, films, brands or franchises. The first question is whether the license is distinct from other promises. A software license that is significantly integrated with implementation or customization may be part of one combined performance obligation.

A distinct license is recognized either over time or at a point in time:

• Right to access IP: revenue is recognized over time when the entity undertakes activities that significantly affect the IP, the customer is exposed to their effects, and those activities do not transfer a separate good or service.
• Right to use IP: revenue is generally recognized at the point when the customer can use and benefit from the IP as it exists when granted.

Ongoing activities must genuinely affect the licensed IP; merely protecting legal rights or performing unrelated promotion does not automatically create a right-to-access license. ASC 606 includes more explicit classifications for functional and symbolic IP, so entities must apply their reporting framework carefully.

Restrictions defining the license’s scope—territory, period or permitted use—usually do not create extra performance obligations. A promise to defend a valid patent generally supports the transferred right rather than constituting a separate service unless additional services are promised.

8. Long-Term Contracts and Progress Measurement

Long-term construction, engineering, outsourcing and service arrangements require analysis of whether revenue qualifies for over-time recognition. Contract duration alone is not enough.

For an over-time obligation, progress may be measured using output or input methods.

Output methods

Output methods measure value transferred directly, using milestones, units delivered, surveys of work performed or appraisals of results. They can faithfully depict performance but may be costly or unavailable.

Input methods

Input methods compare resources consumed with expected total resources. A common cost-to-cost measure is:

If progress faithfully depicts performance, cumulative revenue is:

Both numerator and denominator must use consistent currency units and include comparable costs. Costs caused by significant inefficiencies not reflected in price are excluded from progress. Special treatment may be required for uninstalled materials that do not proportionately depict performance. Estimates must be updated as circumstances change.

Worked example: A contractor has one over-time obligation with a transaction price of $2,400,000 and estimated eligible costs of $1,800,000. Eligible costs incurred by year-end are $720,000.

If no revenue was previously recognized, current-period revenue is $960,000, expense is $720,000, and gross profit is $240,000. Billings do not determine revenue; they affect receivables and contract assets or liabilities.

A contract asset arises when the right to consideration is conditional on something other than passage of time. A receivable is an unconditional right to consideration. A contract liability arises when payment is received, or becomes due, before related performance.

If progress cannot yet be measured reasonably but the entity expects to recover costs, revenue may be recognized only to the extent of costs incurred until progress becomes measurable. Expected losses and onerous contracts are addressed under relevant guidance, such as IAS 37 under IFRS, rather than by recognizing negative revenue.

9. Illustrative Integrated Case: Delta Analytics Platform

Background

This is a fictional illustrative case. Delta Systems agrees to provide a customer with specialized hardware, a perpetual software license, extensive integration and two years of technical support. Fixed consideration is $600,000. Delta can earn a performance bonus of up to $60,000 based on system-processing accuracy.

Estimated SSPs are:

Problem

Management must determine the performance obligations, transaction price, allocation and timing of revenue.

Analysis

The customer could use the hardware and software with alternative integration resources. They are therefore capable of being distinct. However, Delta provides significant integration and heavily modifies the software so the inputs operate as one customized platform. The items are not distinct within the context of the contract and form one combined system performance obligation. Support is separately identifiable and is a second performance obligation.

Probability-weighted analysis initially produces an expected bonus of $45,000. Because final accuracy depends partly on uncertain customer data, management concludes that only $30,000 is highly probable not to result in a significant reversal. The constrained transaction price is therefore $630,000.

Assume the bonus terms relate specifically to successful delivery of the integrated system and allocating the $30,000 entirely to that obligation is consistent with the allocation objective. The fixed $600,000 is allocated by relative SSP:

Adding the constrained bonus gives a total system allocation of $556,153.85.

The customer controls the customized asset as Delta creates it on the customer’s premises, so the system obligation is satisfied over time. Eligible system costs incurred by year-end are $240,000 against expected eligible costs of $400,000:

Support has not yet begun, so no support revenue is recognized. Once support begins, the $73,846.15 allocation will ordinarily be recognized over 24 months on a pattern depicting service transfer, often straight-line if effort is even.

Approach and Outcome

Delta documents the integration judgment, bonus constraint, allocation exception and cost-to-cost inputs. It recognizes $333,692.31 of cumulative system revenue at year-end and reassesses total costs and the bonus constraint at each reporting date.

Learning Points

• Capable of being distinct does not necessarily mean distinct within the contract.
• Integration can combine hardware, software and services into one obligation.
• Variable consideration must be both estimated and constrained.
• Variable consideration may be allocated entirely to one obligation when the criteria are met.
• Revenue timing follows performance, not billing or cash collection.

10. Governance, Ethics and Professional Judgment

Revenue estimates can create incentives to accelerate earnings, meet targets or conceal deteriorating performance. High-risk judgments include optimistic completion percentages, unsupported SSP estimates, premature acceptance, weak variable-consideration constraints and gross reporting where the entity is only an agent.

Sound governance practices include:

• approval of non-standard contracts by accounting and legal specialists;
• a centralized contract repository and modification controls;
• documented SSP methodologies and periodic validation;
• independent review of bonuses, claims and progress estimates;
• reconciliation of operational systems with the general ledger;
• controls over contract assets, refund liabilities and manual journals; and
• audit committee oversight of significant judgments.

Accountants should resist pressure to structure conclusions around desired earnings. Faithful representation requires neutral estimates, complete documentation and timely revision when evidence changes.

11. Technology and Contemporary Practice

Contract-management and revenue-subledger systems can identify clauses, maintain obligation schedules, allocate prices and generate journal entries. Artificial intelligence can assist in extracting renewal, warranty, termination and bonus terms from large contract populations. However, legal enforceability, control, distinctness and the variable-consideration constraint remain professional judgments.

AI tools may miss amendments, misinterpret jurisdiction-specific language or reproduce biased historical classifications. Best practice combines automated extraction with human review, version control, explainable decision rules and audit trails. Post-implementation reviews by standard setters and evolving digital business models continue to focus attention on principal–agent judgments, licensing, contract costs and disclosures.

Challenges and Limitations

The five-step model is conceptually coherent but does not eliminate estimation uncertainty. Similar facts may produce different conclusions when contractual rights differ. SSPs may be unobservable, progress estimates may change substantially, and principal–agent evaluations may be difficult in platform markets. Comparability therefore depends on transparent judgments and disclosures, not mechanical uniformity alone.

Differences also remain between IFRS and US GAAP in some areas, including collectibility consequences, intellectual-property licensing details, impairment reversals for contract costs and certain disclosure or practical-expedient requirements. Cross-listed and multinational entities must not assume complete equivalence.

Chapter Summary

The five-step model identifies the contract, performance obligations, transaction price, allocation and appropriate recognition pattern. A promised item must be both capable of being distinct and distinct within the contract before it is treated separately. Transaction prices may require estimates of variable consideration, application of the reversal constraint and adjustment for significant financing.

Relative SSPs normally govern allocation, although discounts and variable amounts may sometimes be assigned entirely to particular obligations. Contract modifications are accounted for as separate contracts, prospectively or through cumulative catch-up adjustments depending on pricing and distinctness. Principal–agent analysis determines gross or net reporting based on control rather than cash collection. Assurance warranties create liabilities, service warranties create performance obligations, and inseparable assurance and service components form one performance obligation. License revenue depends on whether the customer receives a right to access or right to use IP. Long-term contract revenue is recognized over time only when a specified criterion is met and progress can be faithfully measured.

Key Terms

Contract asset: A conditional right to consideration for goods or services already transferred.

Contract liability: An obligation to transfer goods or services for which payment has been received or is due.

Control: The ability to direct an asset’s use and obtain substantially all its remaining benefits.

Distinct good or service: A promise that is both capable of being distinct and separately identifiable in the contract.

Expected-value method: A probability-weighted estimate across possible consideration outcomes.

Material right: An incremental customer benefit not available without entering the original contract.

Most-likely-amount method: Estimation using the single most likely outcome.

Performance obligation: A promise to transfer a distinct good or service, or a qualifying series.

Principal: A party that controls a specified good or service before transfer to the customer.

Agent: A party that arranges for another party to provide a specified good or service.

Right-to-access license: A license providing access to IP affected by qualifying ongoing activities.

Right-to-use license: A license providing use of IP as it exists when made available.

Service warranty: Warranty coverage providing a service beyond assurance of agreed specifications.

Assurance warranty: Coverage confirming that a product complies with agreed specifications.

Stand-alone selling price: The price at which an entity would sell a promised good or service separately.

Transaction price: Consideration to which an entity expects to be entitled under a customer contract.

Variable-consideration constraint: Limitation designed to prevent a significant future revenue reversal.

Cumulative catch-up adjustment: Immediate revision of cumulative revenue for changes affecting a partially satisfied obligation.

Review Questions

Short Answer Questions

1. State the five steps in the revenue recognition model.
2. Distinguish “capable of being distinct” from “distinct within the context of the contract.”
3. What is the purpose of the variable-consideration constraint?
4. How does an assurance warranty differ from a service warranty?
5. Distinguish a contract asset from a receivable.

Long Answer Questions

1. Explain how an entity identifies performance obligations in a contract containing equipment, software and installation.
2. Discuss transaction-price allocation and the circumstances in which consideration may be allocated entirely to one performance obligation.
3. Compare the three possible accounting treatments for contract modifications.
4. Explain how control determines whether an entity reports revenue as principal or agent.
5. Evaluate the recognition requirements for right-to-access and right-to-use licenses.

Analytical / Application Questions

1. A customer prepays $200,000 three years before delivery. Using an appropriate market rate of 4%, calculate the contract liability and revenue at delivery, and explain the financing entries.
2. A construction contract has a transaction price of $5 million, estimated eligible costs of $4 million and costs incurred of $1.6 million. Determine cumulative revenue under a valid cost-to-cost method and discuss assumptions required for that method.
3. Analyze a contract containing a product, mandatory installation, an optional extended warranty and a completion bonus. Identify the judgments required at each step of the revenue model.

Multiple Choice Questions with Answers

Question 1

Which condition is required for a promised good to be distinct under the revenue model?

A. It must be invoiced separately.

B. It must be both capable of being distinct and distinct within the contract.

C. It must be delivered before every other promised item.

D. It must have an observable stand-alone selling price.

Correct Answer: B. It must be both capable of being distinct and distinct within the contract.

Question 2

A contract price is $250,000. The SSPs of equipment and maintenance are $240,000 and $60,000. How much is allocated to maintenance using relative SSPs?

A. $50,000

B. $60,000

C. $62,500

D. $200,000

Correct Answer: A. $50,000

Question 3

A customer prepays $110,000 two years before delivery. At a 5% annual effective rate, what revenue is recognized on delivery, assuming a significant financing component?

A. $99,773

B. $110,000

C. $115,500

D. $121,275

Correct Answer: D. $121,275

Question 4

Which financing effect arises when a customer significantly prepays the entity?

A. The entity generally recognizes interest expense as the contract liability accretes.

B. The entity recognizes interest income on the contract liability.

C. The customer prepayment is immediately recognized as revenue.

D. The entity records no liability because cash has been received.

Correct Answer: A. The entity generally recognizes interest expense as the contract liability accretes.

Question 5

When added goods are distinct and their price reflects stand-alone selling prices, a contract modification is generally accounted for as:

A. A cumulative catch-up adjustment

B. A separate contract

C. A prior-period error

D. Variable consideration in the original contract

Correct Answer: B. A separate contract

Question 6

An online platform collects $100, remits $85 to the service provider and merely arranges the service. What revenue should it recognize?

A. $0

B. $15

C. $85

D. $100

Correct Answer: B. $15

Question 7

How are inseparable assurance and service components of a warranty accounted for?

A. Both are ignored until a claim occurs.

B. Both are always treated solely as an IAS 37 provision.

C. They are combined as one performance obligation.

D. They are recognized immediately as revenue.

Correct Answer: C. They are combined as one performance obligation.

Question 8

When is sales-based royalty revenue from a license generally recognized?

A. Entirely at contract signing

B. When the subsequent sales or usage occurs and the related obligation has been satisfied or partly satisfied

C. Only when cash is collected

D. Evenly over the license term regardless of sales

Correct Answer: B. When the subsequent sales or usage occurs and the related obligation has been satisfied or partly satisfied

Question 9

A long-term obligation has a transaction price of $2,400,000, eligible costs incurred of $720,000 and estimated total eligible costs of $1,800,000. What is cumulative revenue under a valid cost-to-cost method?

A. $720,000

B. $864,000

C. $960,000

D. $1,680,000

Correct Answer: C. $960,000

Question 10

Hardware can function with another supplier's software, but the seller significantly integrates it with customized software into one system. Which conclusion is appropriate?

A. The hardware is incapable of being distinct.

B. The hardware must be a separate obligation because it can function independently.

C. The hardware is capable of being distinct but may not be distinct within the contract.

D. The entire contract is outside the revenue standard.

Correct Answer: C. The hardware is capable of being distinct but may not be distinct within the contract.