ASC 606 is the accounting standard that determines when a SaaS company can record revenue. It matters to founders long before an audit, because it decides what your income statement says, what investors see, and whether your internal numbers will survive diligence.
This is a practical overview, not accounting advice. The treatment of any specific contract should be confirmed with a qualified accountant.
The core idea
Revenue is recognised when you transfer control of a promised service to the customer, in the amount you expect to be entitled to. Cash timing is irrelevant. A customer who prepays twelve months has given you cash, not revenue — the revenue arrives one twelfth at a time as you deliver the service.
Everything else is detail about identifying what you promised and how to spread it.
The five steps
- Identify the contract. An enforceable agreement with commercial substance where collection is probable. This includes click-through terms on self-serve signups.
- Identify the performance obligations. The distinct things you promised. Subscription access is one. Implementation services may be another, or may not be — see below.
- Determine the transaction price. Total consideration, adjusted for discounts, credits, refunds and variable amounts.
- Allocate the price to the obligations. Based on standalone selling price, which is what you would charge for each element separately.
- Recognise revenue as each obligation is satisfied. Over time for subscription access, at a point in time for something delivered once.
Where SaaS companies get it wrong
Setup and implementation fees
The instinct is to recognise a $10,000 implementation fee when the implementation is done. Often that is wrong.
If the implementation is not distinct — if the customer could not benefit from it without the subscription, and nobody else could perform it — it is not a separate performance obligation. The fee is bundled with the subscription and recognised over the contract term, or sometimes over the expected customer life, which can be longer.
This surprises founders regularly, because it turns a chunky upfront payment into a thin monthly trickle of recognised revenue.
Multi-year contracts with uneven pricing
A three-year deal priced at $100,000, $120,000 and $140,000 does not automatically recognise at those amounts. If the pricing pattern does not reflect changing delivery, revenue may need to be recognised evenly at $120,000 a year.
Deals with a free first period, steep ramps, or heavy back-loading all attract this treatment. Worth knowing before you structure the deal, not after.
Discounts across a bundle
If you sell a subscription and services together at a discount, the discount generally has to be allocated across both in proportion to their standalone selling prices. You cannot simply apply all of it to the element that is most convenient.
This requires knowing your standalone selling prices, which means having a defensible, documented view of what each element is worth separately.
Usage-based and variable consideration
Pure consumption revenue is generally recognised as the usage occurs, which is straightforward. Minimum commitments, tiered rates that reset, and credits that roll over are not. A committed-spend contract drawn down by usage needs careful treatment, particularly where unused commitment expires. See our piece on usage-based pricing for the commercial side of these structures.
Commission costs: the part founders forget
ASC 606 also covers the cost of obtaining a contract. Sales commissions that are incremental to winning the deal must generally be capitalised and amortised over the period of benefit — often the expected customer life rather than the initial contract term.
This means a commission paid in January on a one-year deal may be expensed over three years, because that is how long you expect to keep the customer. It changes reported margins, and it requires an estimate of customer life that you need to be able to defend.
There is a practical expedient allowing immediate expensing where the amortisation period would be a year or less, which many early-stage companies rely on.
Bookings, billings, revenue and ARR
Four numbers that get conflated and should not be.
- Bookings — total value of contracts signed. A forward-looking sales metric with no accounting meaning.
- Billings — what you invoiced. Drives cash, not revenue.
- Revenue — what ASC 606 says you earned this period.
- ARR — annualised value of recurring contracts at a point in time. Not a GAAP measure at all.
All four are legitimate; using them interchangeably is not. Investors will ask for the bridge between them, and a company that cannot produce it looks unprepared regardless of how good the underlying business is.
What to put in place early
You do not need an audit-grade revenue system at seed stage, but three habits make the eventual transition far cheaper.
- Store contract terms as structured data. Start date, end date, value, billing schedule, services component, discount. Not as PDFs in a drive folder.
- Keep a deferred revenue schedule from day one. A spreadsheet is fine. Reconstructing three years of it later is not.
- Write down your standalone selling prices and the reasoning, each time pricing changes. This is the single most commonly missing piece in diligence.
When to get professional help
Bring in an accountant with SaaS experience before you sign your first materially non-standard contract — a multi-year with uneven pricing, a bundled services deal, a reseller arrangement, or anything with a performance guarantee. The cost of advice is trivial compared with restating revenue during a fundraise.
The same applies before a first audit, a venture debt facility, or any process where a third party will examine the numbers closely.
A worked example
A customer signs on 1 July for a twelve-month subscription at $60,000, plus a $12,000 implementation fee, paid in full upfront. Implementation takes six weeks.
If implementation is not distinct — the customer cannot benefit from it without the subscription and only you can perform it — the total $72,000 is one performance obligation recognised over the twelve months. That is $6,000 a month from July. In the calendar year you recognise $36,000, and $36,000 sits in deferred revenue at 31 December.
If implementation is distinct — the customer could buy it separately, a third party could deliver it — then $12,000 is recognised as the work is performed, roughly over six weeks, and $60,000 over the twelve months. Calendar-year revenue becomes $42,000.
Same contract, same cash, $6,000 difference in reported revenue from one judgement. This is why the distinctness assessment is documented rather than assumed, and why two SaaS companies with identical contracts can report differently.
Signals that your treatment needs review
Four patterns that should prompt a conversation with an accountant.
- A material share of revenue comes from setup, implementation or professional services.
- Contracts routinely include free periods, ramped pricing or pricing that changes between years.
- You sell through resellers or partners, where the question of whether you are principal or agent determines whether you book gross or net revenue.
- Contracts include service credits, performance guarantees or refund rights, all of which are variable consideration.
Each of these is manageable and each is a common source of restatement when discovered late.
Frequently asked questions
Does ASC 606 apply to private companies?
It applies to any entity reporting under US GAAP, including private companies. Many early-stage companies run cash-basis books internally and convert later, which is workable but creates a cleanup cost.
What is the equivalent outside the US?
IFRS 15, which is substantially converged with ASC 606. The five-step model is the same, with some differences in disclosure and in specific applications.
Can I recognise an annual prepayment immediately?
No. Subscription access is delivered over time, so revenue is recognised over the term. The cash sits as deferred revenue until earned.
How does this affect my reported growth rate?
Recognised revenue growth lags bookings growth, sometimes by a lot in a fast-growing company. This is why ARR growth and GAAP revenue growth diverge, and why mixing them in a Rule of 40 calculation produces a meaningless number.
