Revenue and expense recognition

Learning goals

• Separate cash, billing, delivery, and recognition dates.
• Apply an introductory contract-based revenue analysis.
• Allocate a bundled price using relative stand-alone selling prices.
• connect expenses to asset consumption, obligations, or the period benefited.
• Explain why IFRS and ASPE conclusions require current guidance and full facts.

Prerequisite check

1. What entry records cash received before service is delivered?
2. What entry records service delivered before it is billed?

Vocabulary

• Contract: enforceable agreement creating rights and obligations.
• Performance obligation: distinct promised good or service in an IFRS 15 analysis.
• Transaction price: consideration expected for promised goods/services, subject to relevant constraints and terms.
• Stand-alone selling price: price at which a promised item is sold separately.
• Point-in-time recognition: revenue recognized when control transfers at a point.
• Over-time recognition: revenue recognized as the entity performs when the applicable criteria are met.
• Capital expenditure: cost recognized initially as an asset because it creates future benefit.
• Period cost: cost recognized as expense in the period under the applicable treatment.

Core idea

Revenue is not “cash in” and expense is not “cash out.” At an introductory level, ask what was promised, what consideration relates to it, and when the entity satisfied the promise. Under IFRS 15, the familiar five-step model is:

1. identify the contract;
2. identify performance obligations;
3. determine the transaction price;
4. allocate the price to performance obligations; and
5. recognize revenue when or as obligations are satisfied.

ASPE Section 3400 has its own requirements and terminology. Similar fact patterns can produce similar mechanics, but do not claim the frameworks are identical. Returns, warranties, financing, principal-versus-agent questions, licences, variable consideration, and contract modifications need deeper study.

Why this treatment makes sense

Recognition follows economic performance so users can compare periods even when collection policies differ. Expenses arise when assets are consumed, a present obligation is created, or no future benefit remains. The goal is not a mechanical “matching rule” that permits smoothing; each asset and liability must meet its own recognition and measurement basis.

A repeatable method

Use PROMISE–PRICE–PROGRESS–PROOF–POST:

1. List enforceable promises and payment terms.
2. Determine and, if needed, allocate the price.
3. Assess progress/control separately for each promise.
4. Gather proof: delivery, acceptance, usage, time, costs, returns, collection facts.
5. Post revenue and related assets/liabilities/expenses; disclose judgment where required.

Worked example

Nova North Web Inc. receives $18,000 on September 1 for a website design plus six months of support. It normally sells design for $12,000 and six-month support for $8,000. Assume the promises are distinct, the contract qualifies, no variable consideration exists, the site transfers on September 30, and support is provided evenly October through March.

Relative stand-alone values total $20,000:

• Design allocation: $18,000 × $12,000/$20,000 = $10,800.
• Support allocation: $18,000 × $8,000/$20,000 = $7,200, or $1,200 monthly.

September 1:

September 30, on transfer of design:

October 31 support:

At October 31 the liability is $6,000. Cash is unchanged by the two recognition entries.

Suppose Nova paid a freelancer $3,500 specifically for completed design work. Under the assumed simple facts, recognize the related expense when the design is delivered unless the cost qualifies for asset treatment under applicable guidance.

Journal, ledger, and statement connection

The contract-liability ledger begins at $18,000 Cr, falls to $7,200 after design, then $6,000 after one support month. Cumulative revenue is $12,000, not the cash received. The income statement combines recognized revenue and related expenses; the statement of financial position shows the remaining obligation. The cash-flow statement will show the original customer receipt as an operating inflow.

Common mistakes

• Allocating the discount equally instead of by relative stand-alone prices without justification.
• Recognizing all revenue at signing or cash receipt.
• Recognizing straight-line revenue when service is not provided evenly.
• Ignoring returns, acceptance clauses, collectibility, or variable bonuses.
• Capitalizing ordinary advertising or start-up spending merely because management hopes it helps future sales.
• Calling every outflow an expense now, including inventory or equipment acquired.
• Applying an IFRS label to an ASPE entity without checking its elected basis.

Guided practice

A training firm sells an online course and two live coaching sessions for $1,050. Stand-alone prices are $900 for the course and $300 for coaching. The course access transfers immediately; sessions occur next month. Allocate the price and record the cash receipt and immediate revenue. Then state what evidence supports next month's coaching revenue.

Independent practice

Polar Office Systems receives $24,000 on November 1 for equipment and one year of maintenance. Stand-alone prices are $25,000 and $5,000. Assume both promises are distinct, equipment transfers November 15, maintenance is even from December through November, and the relevant framework supports this allocation. Prepare entries through December 31 and compute the ending contract liability. Explain how the answer changes if installation is essential and equipment is not usable until December 10.

Self-check and solutions

Guided: Total stand-alone price $1,200. Course allocation = $1,050 × 900/1,200 = $787.50; coaching = $262.50, or $131.25 each if each session is a separate equal promise. At receipt: Dr Cash $1,050 / Cr Contract Liability $1,050. On course transfer: Dr Contract Liability $787.50 / Cr Course Revenue $787.50. Attendance/completion records and evidence the session occurred support later recognition.

Independent: Allocate $20,000 to equipment ($24,000 × 25/30) and $4,000 to maintenance. Nov 1 Dr Cash $24,000 / Cr Contract Liability $24,000. Nov 15 Dr Contract Liability $20,000 / Cr Equipment Revenue $20,000. Dec 31 recognize one month maintenance: Dr Contract Liability $333.33 / Cr Maintenance Revenue $333.33. Ending liability $3,666.67. If essential installation means the equipment promise is not satisfied until Dec 10, delay equipment revenue until that date; verify whether installation is distinct rather than assume.

Reasoning check: allocation uses relative prices, not the equipment's invoice label. The $24,000 cash total never changes, but timing and category of revenue do.

Retrieval practice

1. Recite the introductory five-step IFRS 15 model.
2. Why is “cash received” insufficient to prove revenue?
3. How do you allocate a bundle using stand-alone prices?
4. What makes capitalization different from simply delaying an unwanted expense?

Exam-style application

A December contract promises a $9,000 device and $3,000 of support at stand-alone prices. The bundled customer price is $10,000. Device control transfers December 20; none of the support occurs by year-end. A student records $9,000 revenue. Calculate the support and device allocations and diagnose the error.

Target: Device allocation $10,000 × 9/12 = $7,500; support $2,500. Recognize $7,500 device revenue under the stated assumptions and retain a $2,500 liability. The student's December revenue and profit are overstated by $1,500.

Lesson summary

Start with promises and evidence, allocate consideration when needed, and recognize as performance occurs. Expense recognition likewise follows consumed resources and obligations—not management's desired profit pattern.