Revenue recognition and deferred revenue
The five steps of ASC 606, run on Northwind's October: a deposit earned on delivery, and a bundle split into a kit sold today and servicing earned month by month.
September left a promise on the balance sheet. A customer paid $3,000 for a dozen drills, and Northwind booked it as deferred revenue, a liability, because the drills were still on the shelf. October is when that promise is kept, and when Northwind signs its first contract with two promises in it. Both are revenue recognition, and in the United States the rule for it is ASC 606.
The standard turns that one principle into five steps, applied to every contract with a customer. Most of the time the five take a second, because a sale over the counter answers all of them at once. They earn their keep when a contract bundles things, runs over time, or has a price that can move.
- 1. ContractApproved, enforceable, collectible
- 2. PromisesA kit, and a year of servicing
- 3. Price$6,000, fixed
- 4. AllocateBy standalone selling price
- 5. RecognizeKit on delivery; servicing monthly
Step 1: is there a contract?
A contract is an agreement that creates enforceable rights and obligations. It can be written, spoken or implied by how a business normally trades. ASC 606 only starts counting once five things are true: both sides approved it and are committed, each side's rights can be identified, so can the payment terms, it has commercial substance, and it's probable Northwind will collect what it's owed.
Step 2: how many promises?
Each distinct good or service promised is a performance obligation, the unit revenue is recognized by. A promise is distinct if the customer can benefit from it, on its own or with resources readily available to it, and it's separately identifiable from the other promises in the contract. The contractor could use the kit without the servicing, and Northwind sells servicing by itself, so this contract has two obligations, not one. The standard uses almost this case as its own illustration: an asset can transfer while a separate promise to maintain it is still owed.
Wrong
Dr Accounts receivable 6,000 Cr Revenue 6,000
Right
Kit: revenue on delivery Servicing: deferred, earned $125 a month
Booking a bundle as one sale puts a year of service into the day it was signed. Revenue is then overstated in October and understated for the eleven months the work is actually done.
Step 3: the transaction price
The transaction price is what Northwind expects to be entitled to: $6,000, fixed. A price that can move, through a rebate, a refund right, a usage fee or a bonus, is variable consideration: estimated, and included only to the extent a significant reversal of revenue is not probable. Sales tax collected for the state stays out of it, as lesson 5 set up. And if Northwind were only arranging a sale another company fulfilled, principal versus agent would decide whether it reports the whole price or only its fee.
Step 4: allocate the price
The price is shared across the obligations in proportion to their standalone selling prices, so the discount is shared out too instead of landing on whichever line someone picks.
Step 5: when each promise is kept
A promise is kept either over time or at a point in time. Over-time recognition applies when one of three tests is met, and servicing meets the first: the contractor gets the benefit of each month's sharpening as it's done. So the $1,500 is earned month by month, $125 at a time. The kit fails all three, so it's recognized at a point in time, the day control passes. Northwind has the right to payment, the contractor has the kit, title and the risk of losing it, so that day is October 1.
The entries
Deliver the tool kit and invoice the contractor for the kit and a year of servicing. The kit is earned today; the servicing is owed.
| Account | Debit | Credit |
|---|---|---|
| 1200Accounts receivable | 6,000.00 | |
| 4000Revenue | 4,500.00 | |
| 2400Deferred revenue | 1,500.00 | |
| Balanced | 6,000.00 | 6,000.00 |
OCT-2, October 1. The whole price is invoiced, so the whole price is receivable. Only the kit is revenue; the servicing is owed.
The kit was bought in on the supplier's terms for this one order and handed over the same day, so its cost goes straight to cost of revenue against the supplier's bill.
| Account | Debit | Credit |
|---|---|---|
| 5000Cost of revenue | 3,000.00 | |
| 2000Accounts payable | 3,000.00 | |
| Balanced | 3,000.00 | 3,000.00 |
OCT-2C
Deliver the dozen drills the September 26 deposit paid for. The liability is earned.
| Account | Debit | Credit |
|---|---|---|
| 2400Deferred revenue | 3,000.00 | |
| 4000Revenue | 3,000.00 | |
| 5000Cost of revenue | 600.00 | |
| 1300Inventory | 600.00 | |
| Balanced | 3,600.00 | 3,600.00 |
OCT-3, October 6. September's deposit is earned the day the drills are handed over. No cash moves: it arrived in September.
Earn October's month of servicing out of deferred revenue.
| Account | Debit | Credit |
|---|---|---|
| 2400Deferred revenue | 125.00 | |
| 4100Service revenue | 125.00 | |
| Balanced | 125.00 | 125.00 |
OCT-11, October 31. One month of servicing delivered, one month earned.
OCT-2 is worth a second look. Invoicing the whole year up front gave Northwind an unconditional right to $6,000, a receivable, before it had done the servicing. The standard's answer is to show both: the receivable, and a contract liability for the work still owed. The reverse case, revenue earned before the right to bill is unconditional, is a contract asset, and the simpler case where only time stands between Northwind and payment is the unbilled receivable from lesson 8.
Revenue follows the promise, not the invoice and not the cash. Find the promises, price each one, and earn each when it's kept.
In this lesson: the deferred revenue balance these entries leave behind, rolled forward through October, has its own page below.
Pages in this lesson
1 page goes deeper, about 4 minutes in all. Read them in order, or open the one you need.
Where this lesson's rules come from
The sources behind this lesson's requirements, by kind. Background reading explains; it is never the authority for a rule. Anything marked as a convention is ours, not the rule-maker's.
- US GAAP
- ASC 606-10-05-3, -05-4; 606-10-25-23, -25-30 (opens in a new tab)Revenue from Contracts with Customers — the core principle, and recognition when control transfersFree after registration
- ASC 606-10-05-4 (opens in a new tab)The five steps of Topic 606Free after registration
- ASC 606-10-25-1 (opens in a new tab)Step 1 — when an agreement is a contract the Topic applies toFree after registration
- ASC 606-10-32-31 (opens in a new tab)Step 4 — allocate the price by relative standalone selling priceFree after registration
- ASC 606-10-25-27 (opens in a new tab)Step 5 — when a performance obligation is satisfied over timeFree after registration
- ASC 606-10-25-30 (opens in a new tab)Step 5 — the indicators that control has passed at a point in timeFree after registration
- ASC 606-10-45-2 (opens in a new tab)Deferred revenue is a contract liabilityFree after registration
- ASC 606-10-32-2A (opens in a new tab)Sales taxes collected may be excluded from the transaction price — a policy electionFree after registration
- Background reading — not an authority
- Wikipedia, “Revenue recognition” (opens in a new tab)Revenue recognitionFree to read
- Wikipedia, “Deferral” (opens in a new tab)DeferralFree to read
The full map is in US GAAP, and where these rules come from.
The words this lesson teaches
Each links to its glossary definition, which also names the authority behind it and the components that render it.
- Revenue recognitionDeciding when, and how much, revenue is recorded — under US GAAP, when (or as) control of a promised good or service transfers to the customer, at the consideration the entity expects to be entitled to
- ASC 606Topic 606, Revenue from Contracts with Customers — five steps: identify the contract, identify the performance obligations, determine the transaction price, allocate it, recognize revenue as each obligation is satisfied
- Contract with a customerAn agreement that creates enforceable rights and obligations — written, oral or implied by customary practice — accounted for under Topic 606 only once it is approved, each party's rights and the payment terms can be identified, it has commercial substance and collection is probable
- Performance obligationA promise in a contract to transfer a distinct good or service, or a series of substantially the same ones — the unit revenue is recognized by
- Transaction priceThe consideration an entity expects to be entitled to for the contract, including estimated variable consideration and excluding amounts collected for third parties such as sales tax
- Variable considerationAny part of the price that can change — discounts, rebates, refunds, credits, usage, bonuses, penalties — estimated and included only to the extent a significant reversal is not probable
- Standalone selling priceThe price at which an entity would sell a good or service separately — the basis for allocating the transaction price across performance obligations
- Over-time recognitionRecognizing a performance obligation's revenue as it is satisfied, measured by progress — required when the customer receives and consumes the benefit as the entity performs, controls the asset as it is built, or the asset has no alternative use and the entity has an enforceable right to payment to date
- Point-in-time recognitionRecognizing a performance obligation's revenue on the date control passes, judged by indicators: a present right to payment, legal title, physical possession, the risks and rewards of ownership, acceptance
- Deferred revenueConsideration received, or unconditionally due, before the goods or services are transferred — a liability until the performance obligation is satisfied. ASC 606 calls it a contract liability
- Contract assetRevenue recognized ahead of an unconditional right to payment — the right still depends on something other than the passage of time
- Remaining performance obligationsTransaction price allocated to obligations not yet satisfied — deferred revenue plus contracted, unbilled amounts — disclosed with when it is expected to be recognized
- Principal versus agentWhether the entity controls a good or service before it passes to the customer — a principal reports revenue gross, an agent reports only its fee or commission net
In the founder glossary
This lesson’s ideas, explained for the founder running the company. Each has an entry in the founder glossary.
See also
- Schedules, accruals & roll-forwardsEvery balance sheet account needs a schedule behind it, and the schedule has to tie to the GL. Most accounting products ship a ledger and statements and leave the schedules in spreadsheets. That handoff is where closes break.
- Order to cash (AR)The receivables stack from quote to revenue: quote → order → fulfillment → invoice → collection → cash application → revenue.
- Penny-exact allocationSplit 100.00 three ways and get 33.34 / 33.33 / 33.33, with nothing left in suspense.
- Prepaid & deferred releaseRelease a prepaid or deferred balance evenly or by days in each month.
- Journal entry for deferred revenueWhen an annual contract is invoiced up front, debit Accounts receivable and credit Deferred revenue. As each month of service is delivered, debit Deferred revenue and credit Revenue for that month's share.
- Journal entry for a customer depositWhen a customer pays a deposit, debit Cash and credit Customer deposits. On delivery, debit Customer deposits for the deposit, debit Accounts receivable for the balance, and credit Revenue for the full price.
- Journal entry for a bundled contract under ASC 606For a contract with several promises, debit Accounts receivable and credit Deferred revenue for the price when billed, allocate the price to each performance obligation by relative standalone selling price, and credit Revenue for each part as that promise is satisfied.
- Journal entry for a sale on accountFor a sale on credit, debit Accounts receivable and credit Revenue for the price; under a perpetual inventory system also debit Cost of goods sold and credit Inventory for what the goods cost. When the customer pays, debit Cash and credit Accounts receivable.
- Deferred revenue vs accrued revenueBilling or collecting ahead of the work creates deferred revenue, a liability. Doing the work ahead of the bill creates accrued revenue, an asset.
- Accrual vs deferralAn accrual recognizes revenue or expense ahead of the cash, which creates receivables and payables. A deferral parks cash that moved early on the balance sheet, as a prepaid or deferred revenue, until it's earned or used.
- SaaS revenue recognition under ASC 606, step by stepASC 606’s five steps applied to a startup SaaS contract: annual prepay, implementation fees, usage and multi-year deals, with the entries.
- Deferred revenue for SaaS startups, explainedAn annual prepayment is cash today and revenue over a year. How deferred revenue works under ASC 606, why it’s a liability, and the schedule behind it.
- MRR vs GAAP revenue under ASC 606MRR and ARR are operating metrics; revenue under ASC 606 is earned over time. How annual prepayments and churn split them, and how to reconcile the two.
- RevenueWaterfallDeferred balance recognizing by future period.
- ScheduleTableOne shell, seven presets. Prepaids through debt.
- RollForwardOpening → movements → closing → tie. The universal shape.
- JournalEntryDebit and credit as two columns. No signed-column variant.