The five-step model, applied to the contracts SaaS companies actually sign — annual prepay, implementation fees, usage tiers and mid-term upgrades.
At a glance
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.
Steps two and four are where SaaS judgement lives. Everything else usually falls out.
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.
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.
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.
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.
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.
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.