Revenue recognition (ASC 606) for SaaS: a practical guide

ASC 606 is the US GAAP standard for revenue from contracts with customers (IFRS 15 is its international equivalent). For a SaaS company, it decides when the money on an invoice becomes revenue in the income statement. Getting it wrong delays the close, complicates the audit and can force restatements before a fundraise or an acquisition.

This guide is not accounting advice: work with your auditor on your policies. It explains what the standard asks for and what a quote-to-cash system can automate.

The five steps of ASC 606

1. Identify the contract with the customer.
2. Identify the performance obligations: the distinct promises in the contract (the subscription, onboarding, support, usage).
3. Determine the transaction price, including discounts and variable consideration such as usage.
4. Allocate the price to each performance obligation, based on standalone selling prices.
5. Recognize revenue when, or as, each obligation is satisfied.

For a plain monthly subscription, this is trivial: bill monthly, recognize monthly. It stops being trivial with annual prepayment, multi-year ramps, bundled services, usage and mid-term amendments.

Where SaaS revenue recognition gets hard

• Annual or multi-year prepayment. Cash comes in up front; revenue is recognized ratably. The difference sits in deferred revenue.
• Ramped deals. The price changes each year, but the allocation may need to be spread across the whole contract.
• Bundles. A subscription sold with onboarding or professional services is two performance obligations, recognized on different schedules.
• Usage and credits. Usage is recognized as consumed; prepaid credits are deferred until used or expired (breakage).
• Amendments. An upsell or a downgrade mid-term changes the contract, and the remaining revenue schedule with it.

Each of these starts in the quote. That is why revenue recognition belongs in the quote-to-cash process and not only in the ERP: if the contract terms do not flow from the quote into the revenue schedule, finance rebuilds them by hand.

What a quote-to-cash system should automate

• Revenue schedules generated from the signed contract, by performance obligation.
• Deferred revenue balances, updated at each invoice and each period close. 32 of the 44 tools we score document it.
• Revenue waterfall reporting: future revenue by month, from contracted schedules. 24 tools document it.
• General ledger entries posted to the ERP or accounting system (NetSuite, QuickBooks, Xero, Sage Intacct). 35 tools document it.
• Audit trail: who changed which contract, when, and its effect on revenue.

35 tools document ASC 606 / IFRS 15 revenue recognition, natively or through an add-on or partner. The tools that document ASC 606, deferred revenue and the revenue waterfall together:

Native, add-on or partner?

The level on each tool page tells you how revenue recognition is delivered:

• Core strength or Supported: schedules are produced in the tool itself.
• Add-on: a paid module or a sibling product from the same vendor.
• Via partner: the tool sends data to a revenue recognition product (such as a dedicated rev rec tool or the ERP) that does the work.

None is wrong, but each partner adds a sync to monitor at every close. Hyperline, for example, documents ASC 606 revenue recognition and general ledger entries as core strengths, with deferred revenue and the revenue waterfall supported natively.

A checklist for finance teams

1. Map each product you sell to a performance obligation and a recognition pattern (ratable, point in time, usage).
2. Bring a ramped multi-year deal with onboarding to the demo, and ask to see the revenue schedule.
3. Amend it mid-term: check that the schedule updates without a manual journal entry.
4. Ask which journal entries are posted to your ERP, at what frequency, and how errors are reconciled.
5. Ask your auditor which reports they need, and check the tool produces them.

FAQ

What is ASC 606 in simple terms?

ASC 606 is the US accounting standard that says when revenue from a customer contract is recognized: when each promise in the contract is delivered, not when it is invoiced or paid.

Does ASC 606 apply to private SaaS companies?

Yes. ASC 606 applies to public and private companies reporting under US GAAP. Private companies adopted it for fiscal years starting after December 15, 2018 (deferred later by one year for some entities).

Can billing software handle ASC 606?

Some can. The table above lists the quote-to-cash tools that document ASC 606 revenue recognition, deferred revenue and the revenue waterfall. Others send billing data to a separate revenue recognition tool or to the ERP.