Startup finance
ASC 606 Explained: Revenue Recognition for SaaS Startups
ASC 606 is the US revenue recognition rule that decides when a company may call a customer payment revenue. The test is delivery, not cash: you recognize revenue as you hand over what you promised. A five-step model applies it, and for a SaaS startup the practical result is that annual prepayments sit on the balance sheet as deferred revenue and move to revenue month by month.
What ASC 606 is and who it applies to
ASC 606 is Topic 606, “Revenue from Contracts with Customers”, in the US GAAP codification, the official rulebook for US financial reporting. The FASB issued it as Accounting Standards Update 2014-09 together with the International Accounting Standards Board, which wrote a matching standard, IFRS 15. It replaced most of the older industry-by-industry revenue guidance. RevenueHub, a resource from the BYU School of Accountancy, describes the core principle as recognizing revenue when promised goods or services transfer to the customer, in the amount the company expects to receive for them.
Public companies adopted the standard first. Private companies that had not yet issued financial statements under it were allowed to start with annual periods beginning after December 15, 2019, according to a 2021 Journal of Accountancy article. RevenueHub’s page on revenue recognition, last updated in October 2026, says all entities have now completed adoption. So a startup preparing audited or reviewed financial statements under US GAAP should assume ASC 606 revenue recognition applies from day one, whatever the size of the company.
If you only file taxes and keep simple books, the standard may never be written into a policy document. It still matters, because investors, auditors and acquirers read your revenue recognition through it. Whether you must follow GAAP at all is covered in our comparison of cash and accrual accounting.
The five-step model
The steps run in order, and each one feeds the next. Auditors expect every contract to be traceable through all five, and a policy that is audit ready records the judgment made at each step.
- Identify the contract with the customer. A contract is an agreement that creates enforceable rights and obligations. A signed order form or accepted online terms usually count.
- Identify the performance obligations. These are the distinct promises in the contract: access to the platform, onboarding, training, a support tier. Spotting each distinct performance obligation is the heart of the exercise.
- Determine the transaction price. This is the amount you expect to be entitled to, including any variable parts such as usage fees or discounts.
- Allocate the transaction price to the obligations. If a contract bundles several promises, the standard requires you to allocate the total in proportion to what each would sell for on its own.
- Recognize revenue as each obligation is satisfied. Some obligations are satisfied over time, such as a subscription, and others at a point in time, such as a one-off deliverable.
Steps 2 and 4 are where most of the judgment lives for software companies. Whether onboarding is a separate performance obligation or simply part of getting access to the product changes how fast revenue appears, and the standalone selling price you pick for each obligation drives the split.
SaaS revenue recognition: how the steps apply to a subscription
SaaS revenue recognition starts from one fact: a subscription to hosted software is normally delivered continuously. The customer does not get a copy of the code. They get the right to use it for a period, and you are standing ready to provide it every day. That pattern points to SaaS revenue spread evenly across the term. A twelve-month plan produces about one-twelfth of the annual fee in each month of service, whether the customer paid monthly, quarterly or in one invoice.
Other terms in SaaS contracts need separate thought. The Orb billing-software guide and similar vendor explainers list the common ones, and each performance obligation they touch needs its own answer:
- Setup, implementation and onboarding fees. A fee that only enables access to the product is usually deferred and recognized across the subscription. Training or data migration that the customer could buy separately may be its own obligation, recognized as the work is done.
- Usage-based pricing. The fee depends on volume, so the consideration is variable. Companies estimate it with a stated method and hold back amounts that could reverse later. Where the invoice matches the value delivered, many apply a simplification that lets them recognize revenue as invoiced, which suits usage based plans well.
- Sales commissions. The incremental cost of winning a contract is generally capitalized and spread over the benefit period instead of expensed on the day the deal closes. A practical shortcut exists when that period is one year or less. This part comes from a different section of the codification, ASC 340-40, but it shows up in nearly every SaaS audit.
- Upgrades and amendments. Adding seats at normal prices can be treated like a new contract. Other changes adjust the original one, either going forward or through a catch-up.
ASC 606 compliance is mostly about these. Each of them shows up as variable consideration (the part of the price that can change), contract modifications or a standalone selling price question in the audit file, and finance teams should expect to explain them. These are descriptions from vendor guides, not the standard itself, so treat them as a map of questions for your accountant.
A worked example (hypothetical numbers)
Take an invented company, Northwind Metrics. On November 1 it signs a customer for a $60,000, twelve-month contract, invoiced and paid upfront. The contract includes platform access and a fixed-scope onboarding project. All figures below are made up for illustration.
Step 1. One signed contract with a customer exists.
Step 2. Two performance obligations: access to the platform, and onboarding that the company also sells on its own, so it counts as a distinct service.
Step 3. The transaction price is $60,000. There is no variable component.
Step 4. On a stand-alone basis, the company would charge $54,000 for a year of access and $9,000 for the onboarding project, $63,000 in all. The $60,000 is split in that proportion.
| Obligation | Stand-alone price | Share | Allocated from $60,000 |
|---|---|---|---|
| Platform access, 12 months | $54,000 | 85.7% | $51,429 |
| Onboarding project | $9,000 | 14.3% | $8,571 |
| Total | $63,000 | 100% | $60,000 |
Step 5. Under ASC 606, access is recognized evenly: $51,429 / 12 is about $4,286 per month. Onboarding is recognized as the work is performed, and assume it finishes in December.
Now look at the books on December 31, two months in:
| Item | Amount |
|---|---|
| Cash received | $60,000 |
| Revenue recognized: access (2 months) | $8,571 |
| Revenue recognized: onboarding (complete) | $8,571 |
| Total revenue so far | $17,143 |
| Deferred revenue (liability) | $42,857 |
The $42,857 is a liability because the company owes ten more months of service. It is not income and it is not profit, even though the cash is in the bank. A founder who read the bank balance as results would overstate the year by $42,857.
Deferred revenue, in plain terms
Deferred revenue, sometimes called unearned revenue or a contract liability, is money received, or billed and due, for service you have not yet delivered. It sits among the liabilities and shrinks as you deliver.
Stripe’s 2026 guide on accrual accounting gives a compact case: a customer pays $12,000 on December 1 for a year of software. Cash-basis books would show $12,000 in December. Accrual books show $1,000 per month and hold the other $11,000 as a liability.
Startups that sell annual plans upfront often carry a large balance of this kind. It says something good about cash collection and customer commitment, and very little about this month’s profit. Cash and reported results drift apart, so a 13-week cash flow forecast and the income statement need to be read side by side.
Bookings vs revenue vs billings
Founders and investors use three words that sound alike and measure different things, and the gap between bookings vs revenue is where most confusion starts.
- Bookings count the value of contracts signed. Companies define the term differently, and some use total contract value while others use the first year’s value.
- Billings count what you invoiced in the period.
- Revenue is what you earned in the period under ASC 606, recognized as each service is delivered.
Dave Kellogg, a SaaS executive who writes about subscription metrics, defines billings as revenue plus the change in the deferred balance for a period. His example is a $50,000 order signed on the last day of a quarter: it adds nothing to that quarter’s revenue, but it adds $50,000 to billings. He calls billings a rough proxy for new sales for that reason.
In the Northwind example, bookings at signing are $60,000, billings are $60,000, and revenue at the end of December is $17,143. Had the customer been invoiced quarterly, bookings would still be $60,000, billings would be $15,000 per quarter, and revenue would not change at all, because delivery did not change. That last point is the one to remember. Invoice timing moves cash and billings and leaves revenue alone.
Annual recurring revenue (ARR) is a fourth number and is not an accounting measure. It is a management metric for the yearly value of subscriptions, and no standard defines it. Metrics such as CAC payback depend on how you build it, as the guide on unit economics shows.
ASC 606 compliance for a startup: what reviewers look for
Auditors, investors’ accountants and acquirers check the same few things. Is there a written revenue recognition policy? Can each contract be traced through the five-step model, including the performance obligations you identified and the transaction price you used? Do the schedules tie to the ledger, and do they match the contract terms? Is the financial reporting consistent from one period to the next? Good answers come from habit, not from software. A founder who keeps clean contracts and a monthly reconciliation will pass most reviews, and finance teams that skip these steps tend to meet the questions during a funding round or sale, when time is short.
The standard also carries extensive disclosure requirements, which the Journal of Accountancy said in 2021 some preparers were still struggling to apply well. Financial statement footnotes about revenue recognition are where that shows up.
Mistakes startups make
- Recording prepayments as revenue. A founder collects a year of fees from several customers in December and shows it all as Q4 revenue. Under ASC 606 most of it belongs in later months.
- Reporting bookings to investors as revenue. The two can be far apart, so label each one clearly.
- Ignoring non-standard terms. Free periods, refunds, side letters and custom pricing change the transaction price.
- Skipping contract review. Revenue recognition is applied contract by contract, and the standard requires judgment, so a spreadsheet that only multiplies price by months will miss exceptions.
- Waiting until diligence. If an acquirer or an investor’s accountants rework your revenue, the restatement lands at the worst time. The due diligence and data room guide lists what reviewers typically ask for.
A related risk is mixing up retention metrics and revenue. Churn and expansion affect what you will recognize next, and the guide to SaaS activation, retention and churn covers how to measure them.
How to set it up without a big team
- Write a one-page revenue recognition policy, based on the standard: what you sell, when each item is delivered, how you treat setup fees and usage.
- Keep every contract in one place with start date, end date, price and billing schedule.
- Build a simple schedule that spreads each contract across its months and ties to the liability balance in the ledger.
- Reconcile it monthly. Billings minus revenue should equal the change in that balance.
- Ask an accountant to review the policy once contracts get complex, for example with multiple products, usage fees or reseller deals.
Who does this work changes as the company grows. A bookkeeper or outsourced accountant may start it, and a controller takes it over later. The comparison of CFO, controller and VP of finance roles shows where it usually lands. Plans built on these numbers also benefit from a clear startup budget and forecast.
Questions readers ask
Does ASC 606 apply to my pre-revenue startup? Not until you have contracts with customers. Once you sign paying customers and prepare US GAAP statements, it applies.
Can I recognize all annual revenue when the customer pays? Usually not for a subscription that runs for a year. Revenue follows delivery, so most of the payment is deferred at first.
Is ASC 606 the same as IFRS 15, and does it apply to every SaaS company? The two were developed jointly and use the same five-step model, and either applies to a SaaS company depending on where it reports. Details and wording differ in places, so companies reporting under IFRS should read IFRS 15 itself.
What is the difference between deferred revenue and ARR? The first is an accounting liability for service still owed. ARR is a management metric for the annual value of subscriptions, and it does not appear on the balance sheet.
Do I need an accountant for this? For simple monthly plans, a clear policy and a careful bookkeeper may be enough. For multi-part contracts, usage pricing or an audit, professional review is worth having.
Sources and limits
- RevenueHub, BYU School of Accountancy, “Overview of ASC 606” (revenuehub.org), updated October 2026: core principle, five steps, adoption status.
- Journal of Accountancy (AICPA and CIMA), “Revenue, lease accounting still challenge private companies”, August 2021: private company effective dates.
- Dave Kellogg, “Bookings vs. Billings in a SaaS Company”, kellblog.com, May 2018: billings and deferred revenue definitions.
- Stripe, “Cash vs. accrual accounting”, updated April 2026: deferred revenue example.
- Orb, guide to ASC 606 for SaaS companies (withorb.com, undated): setup fees, usage pricing, commissions, upgrades. A vendor guide, so read it as a list of topics, not authority.
The Northwind figures are invented. Interpretations of ASC 606 depend on facts in each contract. This page is not accounting, tax or legal advice.