Revenue recognition and contract economics

Learning goals

• Identify distinct promises and allocate a transaction price.
• Decide whether revenue is recognized at a point in time or over time.
• Record contract assets, receivables, and contract liabilities accurately.

Prerequisite check

Cash collection and revenue recognition are different events. Cash received before performance normally creates a contract liability; an unconditional right to cash is a receivable, while a right conditional on further performance is a contract asset.

Vocabulary

• Performance obligation: a promise to transfer a distinct good or service.
• Stand-alone selling price: observable or estimated price of a promised item sold separately.
• Transaction price: consideration expected for transferring promised goods or services.
• Contract liability: obligation to provide goods or services after customer consideration.
• Variable consideration: price affected by discounts, rebates, returns, or performance.

Core idea

Under IFRS 15, entities identify the contract and distinct promises, determine and allocate the transaction price, then recognize revenue as each promise is satisfied. Private enterprises applying ASPE use Section 3400's revenue principles rather than automatically applying IFRS 15, so an exam must identify the framework. The economic question remains: what was promised, what consideration relates to it, and when did the customer obtain the benefit or control?

Why this treatment makes sense

Bundles and deposits can distort revenue if the invoice is treated as the answer. Allocation based on relative stand-alone prices reports each performance component when earned and prevents free-looking services from disappearing from the accounts.

A repeatable method

1. Confirm approved parties, rights, payment terms, commercial substance, and collectibility.
2. List promises and determine which are distinct.
3. Estimate transaction price, constraining uncertain amounts when required.
4. Allocate using relative stand-alone selling prices.
5. Identify point-in-time or over-time satisfaction for each obligation.
6. Record cash/receivable, contract balances, revenue, and related costs.
7. Reconcile contract balances and disclosures to the contract register.

Worked example

On October 1, Halifax Home Tech sells a smart control unit plus 12 months of remote monitoring for $1,080 cash. Stand-alone prices are $900 for the unit and $300 for monitoring. Both are distinct; the unit transfers immediately and monitoring is provided evenly.

Allocation: unit $1,080 × $900/$1,200 = $810; monitoring $270.

October 1 entry: debit Cash $1,080; credit Product Revenue $810; credit Contract Liability $270. At December 31, three of twelve monitoring months have been provided: $270 × 3/12 = $67.50. Debit Contract Liability and credit Monitoring Revenue $67.50. The remaining liability is $202.50.

If the unit cost $510, cost of goods sold and inventory are recorded separately on delivery. Total revenue recognized by December 31 is $877.50, not the $1,080 cash receipt.

Journal, ledger, and statement connection

The customer contract, delivery evidence, and service logs support the revenue subledger. Product revenue and cost occur on delivery; monitoring revenue and the contract liability unwind monthly. The closing contract-liability roll-forward must reconcile opening balance, billings/cash, revenue, and ending balance.

Common mistakes

• Allocating the bundle based on cost or invoice labels instead of relative selling prices.
• Calling every advance a receivable rather than a contract liability.
• Recognizing all service revenue when hardware ships.
• Ignoring expected returns or performance bonuses merely because cash was collected.

Guided practice

A $2,400 package includes equipment with a $2,000 stand-alone price and training priced at $1,000. Allocate $1,600 to equipment and $800 to training. If half the training is delivered, recognize $400 training revenue and retain $400 as a contract liability.

Independent practice

Level 1 — allocation: Allocate a $1,500 bundle between goods priced separately at $1,200 and service priced at $800.

Level 2 — timing: The goods transfer December 15; four equal service months begin January 1. Determine December revenue and contract liability.

Level 3 — judgment: A $50,000 bonus is payable only if a project finishes by June 30, and similar projects often finish late. Explain what evidence is needed before including the bonus.

Self-check and solutions

Level 1: Goods: $1,500 × 1,200/2,000 = $900. Service: $600.

Level 2: Recognize $900 goods revenue in December and report a $600 contract liability; no service has yet transferred.

Level 3: Estimate the probability and range using project status and reliable history, then include variable consideration only to the extent it is highly probable that a significant reversal of cumulative revenue recognized will not occur when the uncertainty is resolved. Reassess each reporting date; under ASPE, apply its framework rather than importing IFRS wording automatically.

Retrieval practice

1. What basis allocates a bundle price?
2. What balance usually results from cash before performance?
3. Does invoicing by itself prove revenue is earned?

Answers: relative stand-alone selling prices; contract liability; no.

Exam-style application

Build a one-page contract schedule showing promises, stand-alone prices, allocation, transfer evidence, recognized revenue, and closing contract balance. Then write one control recommendation for ensuring service logs reach accounting before close.

Lesson summary

Revenue follows satisfied promises, not cash or billing alone. Contract analysis, allocation, timing evidence, and balance reconciliation form one connected process.