Chapter 4: Revenue Recognition

Comprehensive Study Guide: Organized by Your Course Week

How This Chapter Maps to Your Course Weeks

Learning Objectives Map

Decision Flowcharts & Logic Trees

Exhibit 4-2 reconstructed: Schematic of the five-step process

Exhibit number and full content preserved exactly; ASCII schematic redrawn as Mermaid. [Visual upgrade, substitution]

flowchart TD
    S1["1. Identify contract<br/>with customer"]
    S2["2. Identify performance<br/>obligations — P.O."]
    S3["3. Determine<br/>transaction price"]
    S4["4. Allocate transaction price<br/>to performance obligations"]
    S5["5. Recognize revenue in<br/>accordance with performance,<br/>as each P.O. is satisfied"]
    PO1["P.O. #1"]
    PO2["P.O. #2"]
    PON["P.O. #N"]
    ALLOC["Dollar amount<br/>assigned to each P.O."]

    S1 --> S2
    S1 --> S3
    S2 --> PO1
    S2 --> PO2
    S2 --> PON
    S3 --> S4
    PO1 --> ALLOC
    PO2 --> ALLOC
    PON --> ALLOC
    S4 --> ALLOC
    ALLOC --> S5

Step 5 decision tree: Point in time vs. over time

IFRS 15 ¶38 indicators and ¶35 criteria, both quoted in your source. List form redrawn as a decision tree. [Visual upgrade, substitution]

flowchart TD
    START["Step 5: a performance obligation<br/>exists. When is it satisfied?"]
    START --> DEFAULT["IFRS presumes POINT-IN-TIME<br/>recognition by DEFAULT"]
    DEFAULT --> TEST{"Is ANY ONE of the three<br/>over-time criteria in<br/>IFRS 15 para 35 met?"}

    TEST -->|"a. Customer simultaneously receives<br/>and consumes the benefits<br/>as the entity performs"| OVER["RECOGNIZE OVER TIME<br/>Use percentage of completion"]
    TEST -->|"b. Performance creates or enhances<br/>an asset the customer controls<br/>as it is being created"| OVER
    TEST -->|"c. No asset with an alternative use<br/>AND enforceable right to payment<br/>for work completed to date"| OVER
    TEST -->|"None of the three are met"| POINT["RECOGNIZE AT A POINT IN TIME"]

    POINT --> IND["Assess the para 38 indicators:<br/>a. obligated to pay<br/>b. has legal title<br/>c. has physical possession<br/>d. bears risks and rewards<br/>e. has accepted the asset"]

WEEK 2 (May 18–22): The Five-Step Model

(Sections A–C.4; LO 4-1, LO 4-2)

A. Why revenue recognition needs to be constrained (LO 4-1)

The core problem: in theory, revenue could be recognized at any point along a business's value-creation process, there's no single "correct" moment. The chapter makes this concrete with a timeline of a generic business.

Exhibit 4-1 reconstructed: A business's value creation process

Time  ──────①──────────②──────────④──────────⑤──────────⑦──────────⑨──────→

①Invent good/service,   ②Receive      ④Finish       ⑤Time of      ⑦Complete    ⑨Expiry of
 discover resource        order         production     "sale"/       cash          warranty
                                                        delivery      collection

              ③Production           ⑥Collection period      ⑧Warranty period
              (between ② and ④)      (between ⑤ and ⑦)       (between ⑦ and ⑨)

(Numbering 1–9 is the textbook's own, note it skips straight from ② to ④ and ⑤ to ⑦, with ③⑥⑧ representing the durational stages "Production," "Collection period," and "Warranty period" that span the gaps between the point-in-time events. The chapter notes this ordering can differ by business type.)

Reading the timeline left to right, from earliest possible revenue-recognition point to latest:

• Point ①, discovery/invention (e.g., a biotech company discovers a new vaccine, a mining company finds an aluminum deposit). Value is arguably created right here, a publicly traded company's stock price may move on the discovery alone. But recognizing revenue this early would require forecasting drug approval odds, future price, future demand, insurance coverage decisions, and competitor treatments, a "daunting forecasting exercise" that's neither precise nor verifiable.
• Points ②③④, order received, production, production finished. Production itself adds value.
• Point ⑤, the traditional "sale"/delivery point.
• Point ⑥, the collection period (if sold on credit, the seller is effectively also providing a lending service).
• Point ⑦, cash fully collected.
• Point ⑧⑨, the warranty period and its expiry, the most conservative possible point to recognize revenue, since only now has every guarantee obligation lapsed.

B. Overview of the five-step process (LO 4-2)

The criteria live in IFRS 15: Revenue from Contracts with Customers (issued 2014, jointly by the IASB and the US FASB, a rare case of true international convergence, unifying many previously disparate revenue rules).

Scope note: "contract" includes written, verbal, or business-practice-implied agreements, a grocery sale and a skyscraper-construction contract are both in scope. Explicitly excluded from IFRS 15: lease contracts (IFRS 16, Chapter 17), insurance contracts (IFRS 17), financial instruments (IFRS 9, Chapters 7 & 11–14), and non-monetary exchanges between same-line-of-business entities that merely facilitate sales to customers.

The five steps (memorize this, it's the spine of the whole chapter):

1. Identify the contract with the customer.
2. Identify the performance obligation(s).
3. Determine the transaction price.
4. Allocate the transaction price to performance obligations.
5. Recognize revenue in accordance with performance.

The logic, in plain language: a contract has two sides, what the entity must do (step 2) and what it will receive (step 3). Once you've split the price across each promise (step 4), you record revenue as each promise is actually fulfilled (step 5).

Exhibit 4-2 reconstructed: Schematic of the five-step process

①Identify contract with customer
          │
          ▼
②Identify performance obligations (P.O.)  ③Determine transaction price ($)
          │                                          │
          ▼                                          ▼
   P.O. #1 ──┐                              ④Allocate transaction price
   P.O. #2 ──┼──── $ assigned to each ◄──────  to performance obligations
   P.O. #N ──┘
          │
          ▼
⑤Recognize revenue in accordance with performance (as each P.O. is satisfied)

Exhibit 4-3 reconstructed: Simple example: sale of a car

Car dealership sells a car (cost $57,000) for $63,000 cash, no maintenance/warranty add-ons.

Dr. Cash                      63,000
    Cr. Sales revenue                  63,000
Dr. Cost of goods sold        57,000
    Cr. Inventories                    57,000

Why this matters: most everyday transactions (a restaurant meal, this car sale) collapse the five steps into something trivial, one performance obligation, satisfied instantly, at a fixed price. The chapter spends the rest of the material on the exceptions, where one or more steps get genuinely hard.

C.1–C.4: The five steps in detail

Exhibit 4-4 reconstructed: Key IFRS 15 requirements per step

Step 1: Identify the contract

Requirements (a)–(c) are largely self-explanatory. (d) Commercial substance rules out shams, e.g., two mining companies swapping identical coal for no real economic reason. (e) Collectability rules out recognizing revenue when there's too great a chance you won't actually get paid, directly tied back to the "reduce uncertainty to an acceptable level" theme from Section A.

Step 2: Identify the performance obligation(s)

A good/service is distinct only if both: (a) the customer can benefit from it alone or with other readily available resources (an inherent test), and (b) it's separately identifiable within the contract (a contextual test). Classic case where (a) holds but (b) fails: bricks, piping, wiring, and labour in a building-construction contract are each inherently usable alone, but in context they're all just inputs to one promise, a finished building, so they are not separated.

Also covers "a series of distinct goods/services that are substantially the same", e.g., a contract to deliver 5,000 tonnes of aluminum every month for 24 months. This has consequences for Step 5 (recognizing revenue as a stream rather than 24 separate one-off sales).

Step 3: Determine the transaction price

Usually simple (fixed consideration), but four complications matter:

(a) Non-cash consideration. Estimate the non-cash item's fair value and add it to any cash received. Example: buyer trades in an old car (fair value $7,500 estimated) plus pays $20,000 cash → transaction price = $27,500. If the trade-in's fair value can't be reliably estimated, back into it using the new item's stand-alone selling price instead: if the new car's stand-alone price is $28,000 and cash paid is $20,000, implied trade-in value = $28,000 − $20,000 = $8,000.

(b) Significant financing component. When payment timing differs substantially from delivery timing, you must strip out the implicit interest, record revenue at the amount that would have been recorded for an equivalent cash sale. Worked example: sell goods for $121,000 payable in 2 years, interest rate 10% → transaction price = $121,000 ÷ 1.10² = $100,000 (the $21,000 difference is interest revenue, recognized over the 2 years, not sales revenue upfront). Practical expedient: IFRS 15 lets you skip this adjustment entirely if you expect to collect within one year of delivery, which covers almost all ordinary trade credit.

(c) Consideration payable to the customer. When a seller promises cash back to anyone in the supply chain (e.g., manufacturer-issued consumer coupons redeemed at a grocery retailer), the estimated payout must be deducted from transaction price, you cannot record revenue at the gross/artificially high price and only later record the giveback.

Worked example: Superclean Corp (Exhibit 4-5 reconstructed): sells 200,000 units of detergent to Best Grocery Wholesale at $3/unit (manufacturing cost $1.50/unit); issues 400,000 coupons worth $2 each, estimates 30% redemption.

Upon delivery of 200,000 units:
Dr. Accounts receivable (200,000 × $3)              600,000
    Cr. Sales revenue                                        360,000
    Cr. Consideration payable to customers                   240,000
        (30% × 400,000 coupons × $2/coupon)
Dr. Cost of goods sold (200,000 × $1.50)            300,000
    Cr. Inventories                                           300,000

When retailers submit actual coupon claims ($250,000 — more than the $240,000 estimated):
Dr. Consideration payable to customers               240,000
Dr. Sales revenue                                     10,000
    Cr. Accounts payable                                      250,000

(d) Variable consideration. Whenever the final amount is uncertain (the coupon example above is one case, actual redemptions exceeded the estimate by $10,000). A very common case is volume discounts.

Worked example: Best Quality Bicycles/BQB (Exhibit 4-6 reconstructed): normal price $100/unit; 10% discount (→$90/unit) retroactively applied to all units purchased in the year if a retailer buys ≥500 units. Retailer X was predicted (high probability) not to hit the threshold.

• H1: buys 200 units. BQB expected no threshold → records 200 × $100 = $20,000 at full price.
• H2: buys 400 more (600 total), threshold is hit, discount now applies retroactively to all 600 units.

So H2's recorded revenue is only $34,000 ($36,000 new sales − $2,000 reversal on the earlier units) even though 400 units were delivered at $90 each.

Two extra wrinkles on variable consideration:

1. Estimation method, use whichever is more suited to the facts: expected value (probability-weight every possible outcome and sum) or most likely amount (best when there are only a small number of discrete outcomes). BQB is a two-outcome case (hits threshold or doesn't), so most likely amount ($100 or $90) is more appropriate than some blended expected value between $90–$100.
2. The variable consideration constraint (¶56, quoted directly): only include variable consideration in the transaction price "to the extent that it is highly probable that a significant reversal … will not occur." Note the deliberately high bar: "highly probable," not merely "probable" (i.e., not just "more likely than not"). This constraint is one-sided: reversals should be rare, but additional revenue can be recognized regularly as uncertainty resolves in the seller's favour.

Step 4: Allocate the transaction price to performance obligations

Allocate based on relative stand-alone selling prices (the price at which the entity would sell that good/service separately).

Exhibit 4-7 reconstructed: Allocation example

Contract with 3 performance obligations, transaction price $900 (a bundled discount off the $1,000 sum of stand-alone prices):

When stand-alone prices aren't observable, IFRS 15 ¶79 offers three estimation approaches (others may also be suitable):

WEEK 3 (May 25–26): Performance Over Time, Warranties, and Other Situations

(Sections C.5, C.6, D, E; LO 4-2)

C.5: Recognize revenue in accordance with performance: point in time vs. over time

This is Step 5, and it's genuinely the trickiest step, because you first have to decide when control transfers.

Point-in-time indicators (IFRS 15 ¶38), when deciding if control transferred at a point in time, consider whether the customer:

a. is obligated to pay for the asset; b. has legal title; c. has taken physical possession; d. bears the significant risks and rewards of ownership; or e. has accepted the asset.

By default, IFRS presumes point-in-time recognition unless the entity satisfies its obligation over time, which happens if any one of these three criteria (¶35) is met:

a. the customer simultaneously receives and consumes the benefits as the entity performs; b. the entity's performance creates or enhances an asset the customer controls (as it's being created); or c. the entity's performance creates no asset with an alternative use, and the entity has an enforceable right to payment for work completed to date.

The unifying idea behind all three over-time criteria: the entity never really "holds" a finished, sellable asset at the end, because either the customer has already consumed it, already controls it as it's built, or the entity is legally guaranteed to be paid for progress even if the specific asset has no other buyer. Over-time recognition matters most for contracts spanning more than one reporting period, a haircut or restaurant meal is "over time" in theory but has zero accounting consequence because it completes within the same period.

(Long-term contracts, the deepest application of "over time" recognition, get their own full treatment in Week 4's Section F.)

C.6: Multiple performance obligations in practice

a. Warranties

Two fundamentally different types:

| Assurance-type | Guarantees the product meets the quality/spec promised in the contract (e.g., "1-year warranty against manufacturing defects") | No, inseparable from the production process itself | Record a warranty liability (provision) for estimated fulfilment cost, per IAS 37 (Chapter 11) | | Service-type | Extra coverage beyond basic quality assurance (e.g., accidental damage coverage, extended term) | Yes, a genuinely separate promise | Allocate part of the transaction price to it; recognize as deferred revenue, released as the service is performed |

Worked example: BMW i4 sale, $65,000 total price including 4 years of maintenance. Car alone is worth $63,000; maintenance contract $2,000; dealer's cost $57,000.

Upon delivery:
Dr. Cash                              65,000
    Cr. Sales revenue                          63,000
    Cr. Deferred revenue (service contract)      2,000
Dr. Cost of goods sold                57,000
    Cr. Inventory                              57,000

The $2,000 is a liability, not revenue, at the point of sale. If the 4-year service pattern is estimated at 20%/25%/25%/30%, Year 1's entry is:

Dr. Deferred revenue                     400
    Cr. Service revenue (20% × $2,000)           400

(Service costs (materials, labour) are expensed as incurred, separately from this revenue recognition.)

b. Franchise fees

A franchisor licenses trademarks/business practices to a franchisee (e.g., 90%+ of McDonald's restaurants are franchised) in exchange for (1) an initial fee and (2) an ongoing fee (fixed or royalty-based). The ongoing fee is straightforward revenue. The initial fee is the hard part, it's not automatically all revenue at signing, because it usually bundles multiple obligations (setup services now, support/supply commitments later), and professional judgment is required to decide how much to defer and over what period.

Worked example: Delicio Restaurants, northwest Calgary franchise, 10-year term. Initial fee $200,000 + 2% royalty on sales. First-year sales = $2,000,000. Management estimates $80,000 of the initial fee corresponds to services already rendered (location analysis, staffing, training); the remaining $120,000 relates to services spread evenly over the 10-year term.

Upon receipt of the initial fee:
Dr. Cash                              200,000
    Cr. Franchise revenue                       80,000
    Cr. Deferred revenue                       120,000

Recognizing Year 1 revenue on the initial fee:
Dr. Deferred revenue                   12,000
    Cr. Franchise revenue ($120,000 ÷ 10 yrs)     12,000

Recognizing Year 1 royalty revenue:
Dr. Cash                               40,000
    Cr. Franchise revenue (2% × $2,000,000)       40,000

D. Other related issues

1. Expense recognition. IFRS gives little specific guidance here, it flows from the Conceptual Framework (Chapter 2): expenses are recognized when there's a decrease in assets or increase in liabilities, reliably measurable. Where possible, match the expense to the related revenue (e.g., cost of goods sold recorded alongside the related sale, see Exhibit 4-3). (ESG note directly from the text: the same logic means costs like carbon-capture or carbon-tax expenses should be matched to the revenue from the electricity/product that generated them.) Where there's no direct revenue link (e.g., office equipment), use a systematic and rational allocation instead, depreciation is the classic example. And by default: an expenditure is an expense unless it independently satisfies the asset definition and recognition criteria (arises from past events, is controlled, has probable, reliably measurable future benefits), this is the same asset test from Chapter 2, just applied in reverse.

2. Contract costs. Costs incurred to obtain a contract (bid preparation, legal fees, sales commissions) can be capitalized as an asset only if they are incremental, i.e., would not have been incurred otherwise. Bid-document preparation costs are not incremental (you'd spend that whether or not you win) → expense them. Legal fees and sales commissions tied to actually winning the contract are incremental → capitalize them, then amortize consistent with satisfying the performance obligations. Practical expedient: expense them immediately if the amortization period would be one year or less.

3. Onerous contracts (general definition, the long-term-contract-specific illustration is in Week 4, and is the gap flagged at the top of this guide). An onerous contract (IAS 37 ¶68) is one where the unavoidable cost of meeting the contract's obligations exceeds the expected economic benefits. Businesses sometimes enter these deliberately (a "loss leader" to build a long-term relationship), or a contract that was profitable at inception can become onerous as circumstances change (e.g., new environmental/safety/accessibility regulations raising costs). Key accounting rule: unlike a normal, profitable contract (where you recognize revenue/expense only in proportion to progress), an onerous contract requires recognizing 100% of the expected loss immediately, in the period you identify it as onerous, even if the contract is only, say, 20% complete.

E. Specific revenue recognition situations

These three cases all illustrate the same underlying theme: Step 5 hinges on whether control has genuinely transferred, and each case is a scenario where the obvious "point of delivery" is not actually the point of control transfer.

1. Consignment sales. The consignor ships goods to a consignee who can return unsold goods, so the consignor retains legal title and the risks/rewards of ownership; the consignee owes nothing until it actually sells the goods. Revenue is deferred until the right of return lapses, not recorded at delivery to the consignee. (Why use consignment? It shifts demand risk off the retailer, which encourages more retailers to stock more inventory, magazines are the classic example, since browsability drives circulation and the marginal cost of extra copies is low.)

Worked example: Prestige Publications: delivers 100,000 copies (retail $4.95, price to distributor $1.20) on March 1; distributor returns 25,000 unsold copies on April 15. Revenue recognized on April 15: 75,000 × $1.20 = $90,000 (not on March 1's delivery).

2. Installment sales. Buyer takes the product immediately but pays over an extended period, often without legal title transferring until fully paid (e.g., furniture on a 36-month plan). Because collectability is genuinely uncertain (failing Step 1's criterion (e)), it may be inappropriate to book full profit at delivery, instead, recognize profit in proportion to cash actually collected. This is a professional-judgment call, not an automatic rule.

Worked example: Durable Furnishings: $1,000,000 retail installment sales in January, cost $800,000 (20% gross margin).

Initial sale (January):
Dr. Installment accounts receivable    1,000,000
    Cr. Inventory                                800,000
    Cr. Deferred gross profit (a liability)      200,000

(No revenue recorded yet, just the inventory reduction and a deferred-profit liability.)

February: $50,000 collected (net of interest)
Dr. Cash                                50,000
    Cr. Installment accounts receivable            50,000
Dr. Deferred gross profit ($50,000 × 20%)   10,000
Dr. Cost of goods sold ($50,000 × 80%)      40,000
    Cr. Sales revenue                                50,000

→ February shows $50,000 revenue, $40,000 COGS, $10,000 gross profit, and the deferred-profit liability shrinks by that same $10,000.

3. Bill-and-hold arrangements. Goods are fully ready, inspected, accepted, and paid for, but the customer asks the seller to hold onto them (storage constraints, awaiting other deliveries, etc.). Because every revenue-recognition criterion is otherwise satisfied and the seller is just providing incidental warehousing, revenue can be recognized even though the goods physically remain on the seller's premises.

WEEK 4 (June 1–5): Long-Term Contracts

(Sections F–I; LO 4-3, LO 4-4, LO 4-5)

Your pre-lecture list names a "Kennedy Construction" example for both the general long-term-contract mechanics and the onerous-contract extension. Your uploaded chapter's own running example is Delta Engineering (and, for cost-plus, Adobe Building Company): I don't have a "Kennedy Construction" example in the source material, so everything below uses the textbook's own companies. The general mechanics (percentage of completion, cost-to-cost, the 5-phase accounting cycle) should transfer directly to whatever numbers your lecture used for Kennedy Construction, the formulas and logic are identical.

F.1: Cost-plus contracts

Two contract types, with very different risk allocation:

Worked example: Adobe Building Company, contracted by Century Homes (which has the staff expertise to supervise the project and is willing to bear cost-plus risk) at cost + 5% margin (vs. a typical 20% margin on fixed-price work):

Key insight: the original cost estimates are irrelevant to the accounting, only actual costs (+5%) drive revenue. This is exactly why cost-plus removes the contractor's incentive to control costs: better cost management doesn't change reported profit margin at all.

F.2: Fixed-price contracts and the percentage-of-completion method

Simplified case (no uncertainty): Delta Engineering, fixed-price bid of $120 million on the same 360-condo project:

Critical principle: the percentage-of-completion method allocates revenue, not expenses. Costs are always just the actual costs incurred each year, the % complete only drives how much revenue gets recorded.

Realistic case (with uncertainty), now actual experience departs from the original plan:

Solution, using labelled formula rows (this is the pattern to memorize):

Notice: Year 1 gross profit is $0 even though the project is 20% complete, because actual costs ($24M) happened to exactly equal the revenue recognized ($24M) that year. Profit and percentage-complete do not have to move in lockstep.

The general formula (Exhibit 4-15):

$$\text{Revenue} = \text{Percentage complete} \times \text{Contract price} - \text{Revenue previously recognized}$$

F.3: The cost-to-cost approach (an alternative way to estimate % complete)

Instead of an engineer's judgment call, estimate percentage complete from cost data directly:

$$\text{Percentage complete} = \frac{\text{Cost incurred to date}}{\text{Estimated total cost}}$$

Applying this to the same Delta Engineering facts:

Compare the two methods side by side, same total revenue ($120M) and total profit ($16M), but a very different year-by-year pattern: engineer's estimate shows $0M/$16M profit across the two years; cost-to-cost shows $6M/$10M. Neither is "more correct", they're both legitimate, and the difference is purely which underlying assumption (engineering judgment vs. cost-proportionality) you trust more.

Combined formulas (substituting the cost-to-cost formula into the revenue/profit formulas):

$$\text{Revenue} = \left(\frac{\text{Cost incurred to date}}{\text{Estimated total cost}}\right) \times \text{Contract price} - \text{Revenue previously recognized}$$

Worked check, Year 2: (104 ÷ 104) × 120 − 30 = $90 million ✓ (matches the table above)

$$\text{Gross profit} = \left(\frac{\text{Cost incurred to date}}{\text{Estimated total cost}}\right) \times \text{Estimated gross profit} - \text{Gross profit previously recognized}$$

Worked check, Year 2: (104 ÷ 104) × (120 − 104) − 6 = 16 − 6 = $10 million ✓

F.4: The accounting cycle for long-term contracts (5 phases)

Why Phase 2 looks unfamiliar: in ordinary sales, billing a customer credits revenue directly. Here it credits "Billings on CIP" instead, a contra-inventory account, because the actual revenue amount for the period isn't determined by the invoice; it's computed separately in Phase 4 using percentage-of-completion.

Why Phase 4 looks unfamiliar: both revenue and cost of sales appear in the same entry, with the difference (gross profit or loss) flowing into the CIP inventory account itself, i.e., the contractor is adjusting the carrying value of its own work-in-progress inventory for the profit/loss earned that period.

By project completion: CIP (accumulated costs + accumulated profit/loss adjustments) and Billings on CIP (accumulated invoices) should both equal the total contract price, so Phase 5 simply nets them to zero.

Full worked example: Delta Engineering (using the cost-to-cost numbers above), assuming invoices of $28M/$92M and cash receipts of $25M/$95M in Years 1/2:

T-accounts (running balances):

By the end of the contract, every account tied to it nets to zero.

Chapter 4: Focus on Data Analytics (sidebar)

Revisiting Delta Engineering's Exhibit 4-13: the swing between the planning estimate (30% complete) and the engineer's actual estimate (20% complete) cost $12 million of Year 1 revenue recognition versus what was originally projected. The chapter's point: better percentage-complete estimates need better underlying data, not just a single expert's gut call, e.g., tangible metrics (volume of concrete poured, length of road built), resource metrics (labour-hours, materials consumed), and environmental/terrain-difficulty data already navigated versus still ahead. Robust tracking of this data both sharpens the accounting estimate and surfaces project inefficiencies early enough to actually fix them.

G. Risk of earnings overstatement in long-term contracts (LO 4-5)

Two distinct risk categories:

1. Intentional overstatement, earnings management. Recall the two Delta Engineering results side by side:

The cost-to-cost approach is especially exposed: recall $\text{Gross profit} = (\text{Cost to date} / \text{Estimated total cost}) \times \text{Estimated gross profit} - \text{Prior profit}$. Underestimating future costs to complete does double duty for a manager who wants to inflate current profit: it shrinks the denominator (raising % complete) and raises estimated total gross profit, both effects push current-period profit up (and correspondingly reduce future periods' profit).

2. Unintentional overstatement, the winner's curse. Separate from deliberate manipulation, plain errors happen (e.g., omitting a cost, a unit-conversion mistake). But long-term contracts have a second, more subtle unintentional bias: in a competitive first-price sealed-bid auction (lowest bidder usually wins), if the "true" unbiased cost is uncertain, some bidders will underestimate and some will overestimate, and the contract tends to go to whoever underestimated the most.

Worked example (Manitoba government bridge): architect's unbiased cost estimate = $720M + $80M profit margin = $800M total. Five contractors bid based on their own best information: A $705M, B $737M, C $810M, D $855M, E $893M. With no offsetting qualitative factors, A wins at $705M, nearly $100M below the unbiased estimate. This might reflect real efficiency, or it might mean A underestimated the work most severely. (Real example cited: a foreign contractor bidding on a Canadian bridge project once omitted provincial sales tax on construction materials entirely, simply from unfamiliarity with the Canadian tax environment.)

Winner's curse: the winning bidder tends to be whoever underestimated costs the most, raising the odds of an eventual loss. Important distinction: this is not the same as an error, an error is a mistake given the information available at the time; the winner's curse happens even when every bidder used their own information correctly, it's a structural consequence of differing information/experience across bidders, not sloppiness.

H. Presentation and disclosure

General: report revenue separately by activity type (goods, services, royalties, interest, dividends), including the portion arising from non-monetary exchanges. Disclose revenue recognition policies in the notes (and, for services, the method used to measure stage of completion). Also disclose a disaggregation of revenue (e.g., by contract duration, geography, customer type) to help users assess the nature/timing/uncertainty of revenue and cash flows, professional judgment governs exactly how to categorize this.

Long-term contracts specifically: the net CIP-vs-Billings position for each contract determines a balance sheet asset or liability: CIP > Billings → asset; Billings > CIP → liability. Critical rule: you cannot net contracts against each other. (Example directly from the text: Delta Engineering's Year-1 net position is a $2M asset (CIP $30M − Billings $28M); if a second contract separately had a $5M net liability position, the company reports both, a $2M asset and a $5M liability, not a single netted $3M liability.) Required disclosures: contract revenue recognized in the period; the revenue recognition method used (percentage of completion, cost recovery, etc.); and the method used to estimate percentage complete (cost-to-cost, engineering estimates, etc.).

I. Substantive differences: IFRS vs. ASPE

Chapter Summary (Section J, by Learning Objective, from your source)

LO 4-1: Value creation happens across many business processes (research, development, production, delivery, collection, guarantees), and conceptually revenue could track any of them. Standards instead prescribe recognition at later stages of value creation, once procurement/demand/price/credit/indemnity risks are sufficiently low.

LO 4-2: Revenue recognition is a five-step process: identify the contract → identify performance obligations → determine the transaction price → allocate the price to performance obligations → recognize revenue as/when performance occurs.

LO 4-3: IFRS prescribes the percentage of completion method for performance recognized over time, proportional to progress. Estimates of percentage complete can come from engineering judgment, the cost-to-cost approach, or other sources. Changes in these estimates get prospective treatment. Cost-to-cost expresses % complete as cost incurred ÷ estimated total cost.

LO 4-4: When a loss is expected on a contract, prudence requires recognizing 100% of that loss immediately. The cost recovery method applies when the contract's outcome cannot be reasonably estimated. ASPE-eligible enterprises may alternatively use the completed contract method.

LO 4-5: Because business practice varies so widely, choosing the right revenue recognition policy requires professional judgment informed by users' information needs. Since that judgment can be misused, auditors/readers should stay alert to how susceptible a given policy is to manipulation, the cost-to-cost approach in particular is vulnerable to understated future-cost estimates.

Executive Summary (One Page)

Chapter 4 answers a question left open by the Conceptual Framework in Chapter 2: given that "recognition" requires probability and reliable measurability, exactly when, along a business's entire value-creation timeline, does revenue actually become recognizable? Conceptually, revenue could be tied to any point from initial discovery through to warranty expiry, but earlier recognition points require progressively more speculative estimates and are progressively less verifiable, which, per Chapter 1's information-asymmetry logic, makes them less useful for judging management's real performance and easier to manipulate. IFRS 15 resolves this by prescribing a uniform five-step model (identify the contract, identify performance obligations, determine the transaction price, allocate that price across obligations, and recognize revenue as each obligation is satisfied) that pushes recognition to a middle point where uncertainty is low enough to be reliable but not so late that the information is stale.

Step 3 (the transaction price) carries most of the real-world complexity: non-cash consideration must be fair-valued, significant financing components must be stripped of implicit interest (with a one-year practical expedient covering most ordinary trade credit), consideration payable to customers (like manufacturer coupons) must be deducted up front, and variable consideration (like retroactive volume discounts) must be estimated using either expected value or most likely amount, subject to a deliberately asymmetric "highly probable" constraint against overstatement.

Step 5 hinges entirely on whether "control" has transferred (by default at a single point in time, unless one of three over-time criteria is met) and this distinction plays out concretely in warranties (assurance-type warranties are not distinct and simply generate a liability under IAS 37, while service-type warranties are distinct obligations recognized as deferred revenue), franchise fees (where initial fees often must be split between services already rendered and services owed over the franchise term), and three specialized situations, consignment sales (revenue deferred until the right of return lapses, since the consignor retains ownership risk), installment sales (profit deferred in proportion to cash actually collected when collectability is genuinely uncertain), and bill-and-hold arrangements (revenue recognized despite physical retention, because every other criterion is satisfied).

Long-term contracts are the chapter's deepest application of "recognition over time." Cost-plus contracts are mechanically simple (revenue = actual cost + a fixed margin) but create a moral hazard, the contractor's profit rises with cost, removing any incentive for cost discipline, vividly illustrated by Vancouver's Olympic Village housing contract ballooning 69% over budget.

Fixed-price contracts use the percentage-of-completion method, with percentage complete estimated either through engineering judgment or the cost-to-cost ratio (cost incurred ÷ estimated total cost), critically, this method allocates revenue, not expenses, so reported gross profit in any single year can look nothing like the percentage physically completed, and any revision to estimates is a prospective change in accounting estimate, never a restatement of prior periods. The five-phase accounting cycle for these contracts (incurring cost, billing, collecting cash, recognizing revenue/adjusting inventory for profit or loss, and closing out at completion) deliberately does not credit revenue directly at billing, that number is only ever determined through the percentage-of-completion calculation in the fourth phase.

This flexibility is also the chapter's central risk theme: identical total profit can be spread completely differently across reporting periods depending on which estimation method and which cost assumptions management chooses, creating both a legitimate professional-judgment call and a real earnings-management opportunity (understating future costs to complete inflates current profit through two separate channels at once), on top of which unintentional overstatement can arise structurally from the "winner's curse" in competitive bidding, where the winning low bid tends to belong to whichever contractor most underestimated true costs, a bias that exists even when every party acted on their own information in good faith.

Key Takeaways

1. Revenue could conceptually be recognized anywhere along the value-creation timeline (Exhibit 4-1), but standards deliberately push recognition to a point where uncertainty is low enough for reliability without being so late the information goes stale.
2. The five-step model (contract → performance obligations → transaction price → allocation → recognition) is the organizing structure for the entire chapter, nearly every complication in the chapter is really a complication within one specific step.
3. Step 3 (transaction price) is where most real-world complexity lives: non-cash consideration, significant financing components, consideration payable to customers, and variable consideration all require adjusting the "obvious" price.
4. The variable consideration constraint is deliberately asymmetric, "highly probable" no significant reversal, biasing toward conservatism in revenue recognition, not toward maximizing reported revenue.
5. Step 5 (recognition) depends entirely on whether control has transferred, by default at a point in time, over time only if one of three specific criteria is met.
6. Assurance-type warranties are not a distinct performance obligation (→ liability/provision under IAS 37); service-type warranties are distinct (→ deferred revenue).
7. Consignment, installment sales, and bill-and-hold all hinge on the same question: has control genuinely transferred, regardless of physical delivery?
8. Cost-plus contracts remove the contractor's incentive to control costs (a moral hazard); fixed-price contracts place all cost-overrun risk on the contractor.
9. The percentage-of-completion method allocates revenue based on percent complete, expenses are always just the actual costs incurred, which is why gross profit doesn't track percent-complete in a simple way.
10. Changes in percentage-complete or cost estimates are changes in accounting estimate, always prospective, never a restatement of prior periods.
11. Total profit over a contract's life is identical regardless of which estimation method (engineering vs. cost-to-cost) is used, only the timing/pattern of recognized profit differs, which is exactly why this area is vulnerable to earnings management.
12. Onerous contracts require immediate recognition of 100% of the expected loss, regardless of percentage complete, the opposite treatment from a profitable contract.
13. The "winner's curse" in competitive bidding is a structural (not careless-error) source of unintentional cost underestimation, the winning bid tends to belong to whoever most underestimated costs.
14. You can never offset a net-asset contract position against a net-liability contract position on the balance sheet, each contract's position is reported separately.

Common Misconceptions and Mistakes

• Assuming revenue recognition timing is just "when you get paid" or "when you deliver." Both are only two of many possible points on the value-creation timeline (Exhibit 4-1), and neither is automatically correct (see consignment, installment sales, and bill-and-hold, where delivery and recognition explicitly diverge).
• Treating credit risk as part of determining the transaction price. It explicitly is not, collectability is addressed at Step 1 (identifying the contract), not folded into the transaction price itself.
• Confusing "probable" with "highly probable." The variable consideration constraint specifically uses the higher "highly probable" bar, don't apply an ordinary "more likely than not" standard here.
• Assuming all warranties are the same. Assurance-type (not distinct, → liability) and service-type (distinct, → deferred revenue) get fundamentally different treatment, the test is whether the warranty goes beyond guaranteeing the product matches contracted quality.
• Assuming percentage-of-completion allocates expenses too. It only allocates revenue. Expenses are always actual costs incurred each period, this is precisely why gross profit and percent-complete can move independently (Year 1 of the Delta Engineering example showed $0 profit at 20% complete).
• Treating a change in percentage-complete estimate as an error requiring restatement. It's a change in accounting estimate, prospective treatment only, per Chapter 3/IAS 8. Don't restate prior years.
• Believing the cost-to-cost approach is "more objective" than engineering estimates because it's formula-based. It still depends entirely on an estimate of remaining costs to complete, which is exactly the lever most exposed to earnings management (understating remaining costs inflates current profit through two channels simultaneously).
• Assuming a low winning bid on a long-term contract signals superior efficiency. It might, or it might be the winner's curse (structural underestimation), which is not the same thing as sloppy bidding.
• Netting long-term-contract asset and liability positions across different contracts. Not allowed, each contract's net CIP-vs-billings position is reported separately as its own asset or liability.
• Assuming cost-plus contracts are "safer" for the buyer because the contractor is reimbursed for all costs. The opposite, cost-plus shifts cost-overrun risk to the buyer and removes the contractor's incentive to contain costs (Vancouver's Olympic Village example).

Cheat Sheet

The five-step revenue recognition model

Point-in-time indicators (¶38), has control transferred?

Customer: obligated to pay; has legal title; has physical possession; bears risks/rewards; has accepted the asset.

Over-time criteria (¶35), any ONE triggers over-time recognition

(a) Customer simultaneously receives and consumes benefits; (b) performance creates/enhances an asset the customer controls; (c) no alternative use and enforceable right to payment for progress to date.

Warranty types

Formulas

• Non-cash consideration = cash received + fair value of non-cash item (or, if unavailable: stand-alone selling price of good given up − cash received).
• PV with significant financing = Future amount ÷ (1 + r)ⁿ. Example: $121,000 ÷ 1.10² = $100,000.
• Percentage of completion revenue: Revenue = % complete × Contract price − Revenue previously recognized.
• Cost-to-cost % complete: % complete = Cost incurred to date ÷ Estimated total cost.
• Revenue (cost-to-cost combined): Revenue = (Cost to date ÷ Est. total cost) × Contract price − Revenue previously recognized.
• Gross profit (cost-to-cost combined): Gross profit = (Cost to date ÷ Est. total cost) × Estimated total gross profit − Gross profit previously recognized.
• Onerous contract: recognize 100% of expected loss immediately, regardless of % complete.

Contract type risk comparison

The 5-phase long-term-contract accounting cycle

IFRS vs. ASPE: revenue recognition

Key terminology glossary

End of study guide.

Cross-Chapter Connections

• Chapter 1: Information asymmetry. Section A explicitly invokes Chapter 1: less reliable revenue numbers are easier to bias, which is why standards constrain the recognition point.
• Chapter 2: Recognition criteria. The five-step model is the revenue-specific implementation of the Framework's general recognition criteria.
• Chapter 3: Changes in accounting estimates. Every revision to percentage complete or cost to complete is a change in estimate, applied prospectively. Never restate.
• Chapter 6: Consignment. Chapter 6's inventory-ownership rules and Chapter 4's consignment revenue rules are two views of the same control question.
• Chapter 11: IAS 37. Assurance-type warranty provisions and onerous contracts are governed by IAS 37, treated in full in Chapter 11.
• Chapter 10: Biological assets. The IFRS/ASPE difference on agricultural income cross-references directly to IAS 41 in Chapter 10.

Common CPA Exam Traps

Key IFRS/ASPE Rules

Journal Entry / Calculation Walkthrough

Memory Anchors

Adversarial CPA Mini-Scenario

🎯 Key Takeaways for CPA Candidates

1. Revenue could conceptually be recognized anywhere on the Exhibit 4-1 timeline; standards force it into a band where uncertainty is low enough to be reliable but not so late the information is stale.
2. The five-step model is the chapter's spine. Nearly every complication is a complication within one specific step.
3. Step 3 carries most real-world difficulty: non-cash consideration, significant financing, consideration payable to customers, variable consideration.
4. The variable consideration constraint is "highly probable" and one-sided, biased toward conservatism.
5. Collectability is a Step 1 matter (¶9(e)), never a transaction-price adjustment.
6. Point in time is the default; over time requires any one of three ¶35 criteria.
7. Assurance-type warranties → IAS 37 provision, no price allocated. Service-type → distinct obligation, deferred revenue.
8. Percentage of completion allocates revenue only. Cost of sales is always actual cost incurred.
9. Revisions to percentage complete or cost to complete are changes in estimate, prospective, never restated.
10. Onerous contracts: 100% of the expected loss immediately (IAS 37 ¶68), regardless of percentage complete.
11. Total lifetime profit is identical across estimation methods; only the pattern differs, which is exactly why this area is exposed to earnings management. Understating cost to complete inflates current profit through two channels at once.
12. Completed contract is ASPE-only. Never offer it under IFRS. And never net contract positions across different contracts.

Retrieval Practice

Questions visible, answers hidden. Attempt each before expanding.

Source Fidelity & Obsidian QA