Worked example · EX:revenue-from-contracts-with-customers/cedar-revenue-note-and-rpo

Review Cedar Trail's revenue note and RPO bridge

Map each revenue disclosure to its evidence, rebuild remaining performance obligations, and distinguish the result from backlog.

Updated Sep 20, 2026 Review due Dec 10, 2026
On this page
  1. Problem
  2. Give each disclosure a job
  3. Rebuild RPO
  4. State the interpretation boundary
Worked-example setupScope and assumptions
  • Cedar Trail Systems is fictional, and all amounts are whole US dollars.
  • The supplied RPO components use the same reporting entity, date, currency, and disclosure population.
  • The supplied ending timing bands cover all RPO in the quantitative disclosure.
  • The calculation does not establish whether any contract or consideration belongs in RPO.
Period
Year ended December 31, 20X4
Units
US dollars
Rounding
Whole dollars

Problem

Cedar Trail's draft note says only, “Revenue was $4.8 million. Remaining backlog of $1.1 million will become revenue.” The revenue schedule separates equipment transferred on delivery from monitoring recognized as service occurs. The contract-balance workpaper reconciles opening and ending receivables and contract balances. It also identifies revenue tied to the opening liability and explains a modification-driven balance change.

The RPO workpaper uses one controlled population. Opening RPO is $900,000. New allocated consideration is $620,000, a modification adds $40,000, and an acquisition adds $100,000. Revenue recognized from that population is $510,000. Cancellations remove $30,000, and currency translation reduces the balance by $20,000. The draft timing schedule assigns $660,000 to the next 12 months and $440,000 thereafter.

Cedar Trail also has short-duration service contracts omitted under an elected exemption. The note draft does not describe them. Management backlog includes unsigned renewals and ignores cancellation rights, so its population differs from RPO.

Give each disclosure a job

The note should disaggregate the $4.8 million so the point-in-time and over-time patterns remain visible. It should tie contract balances to the workpaper and explain transfer timing, payment timing, and the modification. Performance- obligation text should describe the promised equipment and monitoring, satisfaction and payment terms, and relevant returns, warranties, financing, or agent promises. The note should also explain significant methods, inputs, and assumptions and provide the required contract-cost information.

Each table needs the same entity, period, currency, units, and population as its support. An XBRL fact should retain its tag, period, units, scale, sign, dimensions, decimals, and exact note location. Matching that fact to the filing is evidence of what was reported, not proof of the accounting conclusion.

Rebuild RPO

The rollforward is:

Component Effect RPO
Opening RPO $900,000
New consideration +$620,000 1,520,000
Modification +40,000 1,560,000
Revenue recognized −510,000 1,050,000
Cancellations −30,000 1,020,000
Currency effect −20,000 1,000,000
Acquisition +100,000 1,100,000

The timing bands reconcile: $660,000 plus $440,000 equals ending RPO of $1.1 million. The note must identify the short-duration exemption and explain the excluded obligations. It must also explain consideration omitted from the transaction price and RPO, such as constrained variable consideration.

State the interpretation boundary

Management backlog includes unsigned renewals and uses different cancellation assumptions. It cannot replace the RPO disclosure. Neither measure guarantees revenue, cash, margin, or timing. A useful comparison first defines both populations and reconciles their differences.

The calculation checks the supplied RPO rollforward and timing-band total. It cannot establish contract enforceability, performance obligations, transaction price, exemption eligibility, recognition, cancellation effects, exchange rates, acquisition scope, or disclosure compliance.

Read ASC 606-10-50-1 through 50-12 for the main revenue disclosure requirements. Read ASC 606-10-50-13 through 50-16 for remaining performance obligations. Then complete the independent Northstar practice.

Verified calculation · revenue rpo rollforward

The curriculum loader recomputed this example before it entered the site build. Expand any structured input to inspect the stated facts.

acquisition effect
100,000
cancellations
30,000
currency effect
-20,000
modification effect
40,000
new consideration
620,000
opening rpo
900,000
reported ending rpo
1,100,000
reported timing bands
2 fields
Inspect data
{
  "next_12_months": 660000,
  "thereafter": 440000
}
revenue recognized
510,000

Recomputed result

Values recomputed by the curriculum loader
MeasureValue
ending rpo1,100,000
next 12 months timing amount660,000
thereafter timing amount440,000
timing band total1,100,000