Rounding Robin

Home › Guides › ASC 606 Revenue Recognition for SaaS: A Worked Example

ASC 606 Revenue Recognition for SaaS: A Worked Example

ASC 606 recognises revenue as a company satisfies its promises to a customer, which is rarely when the invoice goes out. This guide applies the five-step model to a typical software subscription sold with implementation services.

The five steps

  1. Identify the contract with the customer.
  2. Identify the performance obligations: the distinct goods or services promised.
  3. Determine the transaction price.
  4. Allocate the transaction price to the performance obligations.
  5. Recognise revenue when, or as, each obligation is satisfied.

The example contract

On March 1 a customer signs a one-year contract for $72,000: a software subscription listed at $60,000 and implementation services listed at $12,000, delivered over the first three months. The full $72,000 is invoiced on March 1. Sold separately, the subscription would be $66,000 and the implementation $18,000.

Assume the implementation is distinct from the subscription, so there are two performance obligations. Whether it is distinct is a judgment: services that only configure the vendor's own product for the customer often are, but heavy customisation may not be.

Step 4: allocate the price

The $72,000 is allocated in proportion to standalone selling prices, not the prices listed on the order form.

ObligationStandalone priceShareAllocated
Subscription$66,000.0078.57%$56,571.43
Implementation$18,000.0021.43%$15,428.57
Total$84,000.00100.00%$72,000.00

The discount of $12,000 is spread across both obligations. Implementation revenue is $15,428.57, not the $12,000 on the invoice.

Step 5: recognise revenue

The subscription is satisfied over time, evenly across the 365 days of the term: $56,571.43 ÷ 365 = $154.99 a day. March has 31 days, so March subscription revenue is $4,804.70. The implementation is also satisfied over time, across the 92 days from March 1 to May 31: $15,428.57 ÷ 92 × 31 = $5,198.76 in March.

The journal entries

When the invoice is issued, nothing has been earned:

AccountDebitCredit
Accounts receivable$72,000.00
Deferred revenue$72,000.00

At the end of March:

AccountDebitCredit
Deferred revenue$10,003.46
Subscription revenue$4,804.70
Services revenue$5,198.76

Deferred revenue is then $61,996.54, the amount invoiced but not yet earned.

Deferred revenue and contract assets

Deferred revenue, a contract liability, arises when billing runs ahead of revenue. A contract asset arises in the opposite case, when revenue has been recognised before the company has the right to invoice. The two are netted within a single contract, but not across different contracts. A contract billed monthly in advance usually carries little of either; one billed annually up front carries deferred revenue all year.

Remaining performance obligations

Companies disclose the transaction price allocated to obligations not yet satisfied, and when they expect to recognise it. In the example, at March 31 the remaining amount is $72,000 − $10,003.46 = $61,996.54, all expected within 12 months.

Common mistakes

Using the template

The revenue recognition template holds up to 200 performance obligations. It performs the allocation, recognises revenue by day or at a point in time, tracks billings, nets deferred revenue and contract assets by contract, and reports the next 12 months of revenue, remaining performance obligations and recurring revenue.

More guides

To report an error or request a calculator or template, send feedback.

This guide is general information, reviewed 2026-11-19. It is not accounting, tax or legal advice. Accounting standards require judgment; consult a qualified professional about your own circumstances. How this site checks its work.