Get your first month of Zinance free.Get your first month free.Claim my free monthClaim
ASC 606

SaaS revenue recognition under ASC 606

The five-step model, applied to the contracts SaaS companies actually sign — annual prepay, implementation fees, usage tiers and mid-term upgrades.

Parag Jain, CPA
Parag Jain, CPAFounder, Zinance·Last updated August 2026·7 min read

Summarize this article

At a glance

Framework
ASC 606, five stepsRecognise as obligations are satisfied
Standard SaaS
Ratably over the termThe subscription is one obligation delivered continuously
Where it gets hard
BundlesImplementation, support and usage may be separate obligations

ASC 606 replaced industry-specific rules with one principle: recognise revenue as you satisfy what you promised. For a plain monthly subscription that is uneventful. For the contracts SaaS companies actually sign, it takes some thought.

The five steps

  1. Identify the contract with the customer.
  2. Identify the performance obligations in it.
  3. Determine the transaction price.
  4. Allocate that price to the obligations.
  5. Recognise revenue as each obligation is satisfied.

Steps two and four are where SaaS judgement lives. Everything else usually falls out.

Annual prepay

A customer pays twelve months upfront. That is one performance obligation — access to the platform — delivered continuously across the term. Cash arrives on day one; revenue is recognised across twelve months; the unearned portion sits as deferred revenue.

Implementation and onboarding fees

The question is whether implementation is distinct. If the customer could take that setup work and use it independently, or another vendor could have performed it, it may be a separate obligation recognised as delivered.

Usually it is not distinct

For most SaaS, onboarding has no standalone value — it exists only to make the subscription usable. Where that is the case, the fee is not recognised upfront. It is combined with the subscription and recognised across the term, which is not what the cash-flow instinct suggests.

Usage-based pricing

Where a fee corresponds directly to value delivered in a period, it is generally recognised in that period rather than estimated across the contract. Overage billed monthly for that month's usage is recognised in that month.

Mid-term upgrades

A customer upgrading in month five creates a contract modification. Whether it is treated as a separate contract or a blended remainder depends on whether the additional services are distinct and priced at their standalone value. Both answers are defensible; picking one and applying it consistently is what matters.

What this means for your close

A revenue schedule that reconciles to the P&L, a documented recognition policy, and deferred revenue that rolls forward cleanly. Our SaaS bookkeeping service runs it monthly.

Frequently asked questions

Can we recognise implementation fees upfront?+
Only if the implementation is a distinct performance obligation — broadly, if it has standalone value to the customer. For most SaaS onboarding it does not, and the fee is recognised across the subscription term instead.
Do early-stage companies need to apply ASC 606?+
If you report on accrual under US GAAP, yes. In practice the discipline matters most from the point investors, lenders or auditors read your statements — but setting it up before there are fifty contracts is far cheaper than after.
How do we handle a customer who upgrades mid-term?+
It is a contract modification. Depending on whether the added services are distinct and priced at standalone value, it is either a separate contract or a blended recognition over the remaining term. Choose the treatment that fits and apply it consistently.

Numbers you can actually trust

Zinance is outsourced bookkeeping, tax, and fractional-CFO support built for fast-growing companies, flat pricing, a dedicated human, and books that stay current every day.

Live in 7 business days No long-term contracts Your books belong to you