Accounting standards
ASC 606 in plain English: the five steps every owner should know
November 17, 2026 · 10 min read
Quick answer
ASC 606 says you record revenue when you deliver what you promised, not when you invoice or get paid. You get there in five steps: identify the contract, list the separate promises in it, work out the price, split the price across the promises based on what each would sell for alone, and recognize each piece as you deliver it. For a lot of small businesses that just means spreading upfront invoices over the months of service.
You close a $40,000 deal in January, invoice half of it, and the January P&L looks like your best month ever. Then February looks terrible, July looks great again, and nobody can tell from the monthly numbers whether the business is growing.
That's what happens when revenue follows invoices. ASC 606 (the US GAAP standard for revenue from contracts with customers) fixes it by tying revenue to delivery instead. It applies to every company that reports under GAAP, private ones included. If a lender, investor, buyer or auditor reads your statements, they expect it.
The standard has a reputation for being complicated, and for some industries it is. But the logic is five steps, and once you've seen them applied to one real contract they stop being abstract. That's what this post does.
Step 1
Identify the contract
An enforceable agreement with a customer. It can be written, oral or implied by how you normally do business.
Step 2
Identify the performance obligations
Each distinct thing you promised to deliver.
Step 3
Determine the transaction price
What you expect to receive, including estimates for discounts, rebates and bonuses.
Step 4
Allocate the price
Split it across the promises based on their standalone selling prices.
Step 5
Recognize revenue
When (or as) you deliver each promise and the customer gets control.
The example we'll use
Say you run a small software company. On January 1 a customer signs a 12-month contract for $40,000 that includes:
- a 12-month subscription to your platform (January to December)
- an implementation project to set up and configure the platform, finished and accepted in January
- a one-day training workshop, delivered in March
Billing terms: $20,000 invoiced in January and $20,000 invoiced in July.
You also know what you normally charge for each piece when you sell it on its own: $36,000 for a year's subscription, $9,000 for an implementation like this one, and $3,000 for a training day. Add those up and the customer would pay $48,000 buying separately. They're getting the bundle for $40,000.
Hold onto those numbers. We'll walk them through all five steps.
Step 1: Is there a contract?
A contract under ASC 606 is an agreement that creates enforceable rights and obligations. Both sides have approved it, you can identify what each party has to do and the payment terms, it has commercial substance, and it's probable you'll collect what you're owed.
Our signed agreement clears that easily. Where small businesses stumble is the informal stuff: a client who says "go ahead" by email, a purchase order that never got a signature, a renewal that runs on autopilot. Those can still be contracts. It depends on whether they're enforceable, which is why your standard terms matter more than people think.
Step 2: What exactly did you promise?
Each separate promise is a performance obligation, as long as it's distinct. A good or service is distinct when the customer can benefit from it on its own (or with things they can easily get elsewhere) and it's separately identifiable from the other promises in the contract.
In our example:
- The subscription is distinct. You sell it on its own all the time.
- The implementation is distinct here, because it's standard configuration work that other firms could also do and the platform works without it. If it were heavy customization the software can't function without, the answer might be different.
- The training is distinct. Customers can benefit from it on its own, and you sell it separately.
So we have three performance obligations. Getting this step right matters more than any other, because everything after it depends on how many pieces you're splitting the price into.
Step 3: What's the price?
The transaction price is what you expect to be entitled to in exchange for delivering everything. Here it's simple: $40,000, fixed.
In real life this step gets harder when the price moves. Volume discounts, rebates, performance bonuses, penalties for missed deadlines, usage fees: those are variable consideration, and you estimate them upfront and update the estimate as you go. A financing component (being paid long before or after delivery), noncash payments and amounts you pay back to the customer can also change the price.
Step 4: How do you split the price?
You allocate the $40,000 across the three promises in proportion to their standalone selling prices, which is what each would sell for on its own. The bundle discount gets spread across all three, not dumped on one.
| Performance obligation | Standalone selling price | Share of total | Allocated price |
|---|---|---|---|
| 12-month subscription | $36,000 | 75.00% | $30,000 |
| Implementation | $9,000 | 18.75% | $7,500 |
| Training workshop | $3,000 | 6.25% | $2,500 |
| Total | $48,000 | 100% | $40,000 |
The math: $40,000 × 36,000 ÷ 48,000 = $30,000. $40,000 × 9,000 ÷ 48,000 = $7,500. $40,000 × 3,000 ÷ 48,000 = $2,500. Every piece carries the same 16.67% discount ($8,000 off $48,000).
If you don't sell something separately, you estimate its standalone price, for example by looking at what competitors charge or by taking your expected cost plus a normal margin. A residual approach is allowed only in narrow cases where pricing is highly variable or uncertain.
Step 5: When does each piece become revenue?
Each performance obligation is recognized when the customer gets control of it, either over time or at a point in time.
- Subscription: over time. The customer receives and uses the service every day, so the $30,000 is recognized evenly, $2,500 a month for 12 months.
- Implementation: in January. The work is done and accepted in January, so the $7,500 is recognized in January.
- Training: in March. The $2,500 is recognized when the workshop is delivered.
Here's the result month by month, next to what you'd show if revenue simply followed your invoices:
Monthly revenue from one $40,000 contract
Recording revenue when billed vs recognizing it under ASC 606
- When billed
- ASC 606
Hypothetical example. ASC 606: subscription $2,500 a month, plus implementation $7,500 in January and training $2,500 in March. Both columns total $40,000 for the year.
Show the numbers
| When billed | ASC 606 | |
|---|---|---|
| Jan | $20,000 | $10,000 |
| Feb | $0 | $2,500 |
| Mar | $0 | $5,000 |
| Apr | $0 | $2,500 |
| May | $0 | $2,500 |
| Jun | $0 | $2,500 |
| Jul | $20,000 | $2,500 |
| Aug | $0 | $2,500 |
| Sep | $0 | $2,500 |
| Oct | $0 | $2,500 |
| Nov | $0 | $2,500 |
| Dec | $0 | $2,500 |
Both versions add up to $40,000 for the year. The difference is the shape. Billing-based revenue says January and July were huge and the other ten months were empty. ASC 606 says you earned $10,000 in January (setup month), $5,000 in March (training) and a steady $2,500 every other month. Only one of those helps you understand the business.
Where do deferred revenue and contract assets come from?
When billing and delivery don't line up, the difference sits on the balance sheet.
- If you've billed or collected more than you've earned, the difference is a contract liability (usually called deferred revenue).
- If you've earned more than you've billed, and you can't bill it yet, it's a contract asset.
- Once you have an unconditional right to be paid (only the passage of time stands in the way), it's a receivable.
Here's our contract at a few points in the year:
| Date | Billed so far | Revenue recognized so far | On the balance sheet |
|---|---|---|---|
| January 31 | $20,000 | $10,000 | $10,000 deferred revenue |
| March 31 | $20,000 | $17,500 | $2,500 deferred revenue |
| June 30 | $20,000 | $25,000 | $5,000 contract asset |
| July 31 | $40,000 | $27,500 | $12,500 deferred revenue |
| December 31 | $40,000 | $40,000 | Nothing left |
Check the June line: January $10,000, February $2,500, March $5,000, then April to June at $2,500 each is $7,500. That's $25,000 earned against $20,000 billed. By July 31 you've billed the full $40,000 and earned $27,500, so $12,500 is deferred and comes into revenue at $2,500 a month from August to December.
Common mistakes
Recognizing setup or onboarding fees on day one. If the setup activity doesn't transfer a separate service to the customer, the fee usually isn't revenue when you charge it. It's typically spread over the service period it relates to, and sometimes longer if the customer can renew without paying it again.
Putting the whole bundle discount on one item. It's tempting to say "the training was free." Unless you have solid evidence the discount relates to one specific promise, it's spread across all of them by standalone selling price.
Treating every task as a separate obligation, or lumping everything into one. Both distort timing. The test is whether each promise is distinct, not how it's listed on the invoice.
Ignoring variable consideration. A volume rebate you'll probably have to pay at year end reduces revenue now, not when you cut the check.
Letting invoices drive revenue in the software. QuickBooks Online and Xero record revenue when you invoice unless you set them up otherwise. If you bill in advance, you need a deferred revenue account and a monthly entry (or a revenue recognition tool) to move it into income.
The deal
- Is it enforceable, and is collection probable?
- What exactly did we promise, and which promises are distinct?
- Is any part of the price variable (rebates, bonuses, usage, penalties)?
The numbers
- What does each promise sell for on its own?
- How is the total split across the promises?
- Is each piece delivered over time or at a point in time?
The books
- Is anything billed before it's earned (deferred revenue)?
- Is anything earned before it can be billed (contract asset)?
- Does the monthly schedule tie to the contract total?
When to get help
If you sell one thing, bill as you deliver it and get paid shortly after, ASC 606 changes very little for you. Your invoices already match your revenue.
It's worth getting help when you sell annual plans paid upfront, bundle products with services, offer volume discounts or rebates, run long projects that span months, or are heading into a review, audit, fundraise or sale. A good revenue schedule built once saves a lot of rework later. If you'd like a second pair of eyes on how your contracts are being recorded, talk to us.
Frequently asked questions
Does ASC 606 apply to small private companies?
Yes, if you prepare financial statements under US GAAP. If you only keep cash-basis or tax-basis books for your own use, it doesn't apply to those, but lenders and investors who ask for GAAP statements will expect it.
Is ASC 606 the same as how revenue is taxed?
No. Tax rules have their own timing for advance payments and other items. Your CPA will reconcile book revenue to taxable income. Don't change your tax reporting based on this post.
What's the difference between deferred revenue and a contract asset?
Deferred revenue (a contract liability) means you've billed or been paid before delivering. A contract asset means you've delivered before you're allowed to bill. One is a debt of service you owe; the other is value you've earned but can't invoice yet.
How do I find a standalone selling price if I never sell the item separately?
Estimate it. Common ways are looking at what competitors charge for similar items or taking your expected cost plus a normal margin. Document how you did it, because a reviewer or auditor will ask.
We do fixed-fee projects that run for several months. Is that revenue over time?
Often, yes, for example when the customer controls the work as you do it, or when you're building something with no other use to you and you have a right to be paid for work done so far. Then revenue follows your progress, such as hours spent against hours expected. If not, it's recognized when the work is handed over.
The bottom line
ASC 606 boils down to one idea: revenue follows delivery, not invoices. Work through the five steps for each contract type you sell, write down your standalone prices, and keep a monthly schedule that moves billed amounts in and out of deferred revenue. Your monthly numbers will finally show how the business is actually doing, and the people reading your statements will trust them more.
Sources
This article is general information, not advice for your situation. Rules change and details matter, so talk to us or your CPA before acting on it.
More articles
- ASC 842 for small businesses: what changes on your balance sheet
November 17, 2026
- The 2026 shortcut for estimating bad debts on current receivables (ASU 2025-05)
November 17, 2026
- 1099-NEC vs 1099-MISC: which to file, deadlines and how-to
November 17, 2026
Have a question about this article?
Ask us. A real person will reply by email within one business day. Your question isn’t published.
Ready for books you can trust?
Book a free 30-minute consultation. We'll review where your finances stand today and show you exactly how we'd help.