SaaS revenue recognition under ASC 606: the five steps, with worked examples

A software company can invoice a full year of service in January and report only one-twelfth of it as revenue that month, and still be following every rule. The reason is that the accounting standard asks a different question from the bank account: not “has the money arrived?” but “has the customer received what it paid for?” That gap between cash, invoices and revenue is where most SaaS finance confusion starts, and where most restatements start too.

This page walks through how that question is answered for subscription software. It covers the five-step model, the records that sit between a signed order and recognized revenue, and the situations that make SaaS accounting harder than selling a box: upgrades, refunds, usage fees, commissions and foreign currency. It sits in the metrics section because every metric on it, from ARR vs MRR to net revenue retention, is a different cut of the same revenue stream. Dollar figures in the worked examples are made up; the rules and the company figures come from the standard-setters, the SEC and three public filings.

What SaaS revenue recognition means

Revenue recognition decides when, and how much, revenue goes on the income statement. The core rule fits in one sentence: a reporting organization recognizes revenue when it satisfies a performance obligation by transferring a promised service to a customer, which is when the customer obtains control of that service¹. A performance obligation is a promise to provide a distinct good or service, or a series of them⁴.

For software delivered over the internet, the customer never takes possession of anything. It gets access, week after week. That is why the same two rules recur in every subscription company’s annual report: access that is committed for a term is recognized ratably over that term, and usage is recognized as it happens^{2, 3, 4}. The standard has a name for the test that produces this result: revenue is recognized over time when the customer simultaneously receives and consumes the benefits as the entity performs⁵.

Four words get mixed up in this area, and a clean vocabulary prevents most mistakes. Each is a different record of the same contract.

Two balance-sheet accounts sit in the gap. Deferred revenue, which Salesforce calls unearned revenue, represents amounts that have been invoiced in advance of revenue recognition³. HubSpot defines the same account as amounts billed for which revenue has not yet been recognized⁴. The opposite case also exists: unbilled revenue, which is recognized but not yet billable under the contract’s billing schedule⁸. Datadog reports approximately $127.0 million of unbilled accounts receivable at December 31, 2025, against $77.0 million a year earlier².

The importance of accounting standards: why this one exists

Two reasons make a common rulebook worth the effort, and both are visible in the primary record. The first is comparability. FASB’s summary describes the pre-2018 position bluntly: U.S. generally accepted accounting principles (GAAP) had complex, detailed and disparate revenue requirements for specific transactions and industries, software among them¹. The new guidance was written to replace numerous industry-specific requirements with one model¹. The International Accounting Standards Board (IASB) issued the matching standard, IFRS 15, effective for annual periods beginning on or after January 1, 2018⁶.

The second reason is that revenue is the number most often abused. The SEC’s 1999 staff bulletin on revenue cites a COSO study of 1987 to 1997 which found that over half of the financial reporting frauds it examined involved overstating revenue⁹. FASB’s summary puts the stakes from the reader’s side: revenue is one of the most important measures investors use to judge a company’s performance and prospects¹.

A 2022 SEC order shows how that plays out in software. Synchronoss Technologies announced in July 2018 a restatement of its 2013 to 2016 financial statements covering approximately $190 million in cumulative revenues¹⁰. Part of the restatement involved transactions in which the company sold software licenses together with multi-year supporting services and recognized the license revenue immediately instead of ratably over the arrangement¹⁰. The order records that, under GAAP at the time, companies had to take into account all material terms of an arrangement, including side letters, when recognizing revenue¹⁰. It also records that the company lacked a fair-value measure for the hosting service it often provided, which forced the whole arrangement to be recognized over time¹⁰. The individual in that order was involved in three transactions that produced approximately $10 million of improperly recognized revenue¹⁰.

The five steps

FASB’s summary lists five steps, and IFRS 15 lists the identical five^{1, 6}. Datadog, Salesforce and HubSpot each reproduce them as the framework in their annual reports^{2, 3, 4}. The table shows each step as a question, followed by the SaaS-specific answer.

Step 1: Identify the contract

A contract is an agreement between two or more parties that creates enforceable rights and obligations¹. The standard applies only to a contract that meets set criteria, among them that it is probable the company will collect the consideration it is entitled to¹. In some cases separate contracts should be combined and accounted for as one¹.

Step 2: Identify the performance obligations

A good or service is distinct if the customer can benefit from it on its own or with other readily available resources, and the promise to transfer it is separately identifiable from other promises in the contract¹. If it is distinct, it is accounted for separately¹. This single test decides whether an implementation project is its own line of revenue or part of the subscription.

The three filings reach different answers on purpose. HubSpot concluded that its subscriptions are distinct because once a customer has access, the product is fully functional and needs no additional development or customization⁴. Salesforce concluded that its professional services are distinct, after weighing four factors: whether other vendors offer the services, their nature, when the services contract was signed relative to the subscription start, and whether the service depends on the customer’s satisfaction with the work³. Datadog identified each of its monitoring services as a separate performance obligation².

Step 3: Determine the transaction price

The transaction price is the amount of consideration the company expects to be entitled to in exchange for transferring promised services, excluding amounts collected on behalf of third parties¹. HubSpot’s wording specifically excludes sales taxes collected for government agencies⁴. Datadog likewise excludes sales and other indirect taxes from subscription revenue².

The price can be fixed or variable, and in SaaS it is often both. Datadog’s transaction price is the fixed price for the contracted level of service plus variable consideration for additional optional purchases². The standard also adjusts the price for the time value of money when a contract includes a significant financing component¹. A practical expedient lets a company skip that adjustment when the gap between delivery and payment will be one year or less⁵, and Datadog applies the expedient to contracts of one year or less². Annual prepayment therefore does not normally require an interest calculation.

Step 4: Allocate the price to the obligations

A reporting organization typically allocates the transaction price to each performance obligation in proportion to the relative standalone selling price of each distinct promise¹. If a standalone selling price is not observable, the organization estimates it¹. Salesforce defines the standalone selling price (SSP) as the price at which it would sell a promised product or service separately to a customer³, and it weighs discounting practices, transaction size, customer demographics, geography and price lists when it has to judge one³.

Step 5: Recognize revenue when each obligation is satisfied

A performance obligation may be satisfied at a point in time, typically for goods, or over time, typically for services¹. For an obligation satisfied over time the company selects a measure of progress⁶. Datadog chose an output method, recognition over time, because it most faithfully represents when the customer simultaneously receives and consumes the value².

In practice the pattern per contract element is consistent across the three filings:

Revenue recognition for an annual plan: one prepayment, twelve months

Take a made-up customer that signs a 12-month subscription on January 1 and pays the full $12,000 up front. Under the five steps there is one contract, one performance obligation (access for the term) and a fixed price of $12,000, so the allocation step is trivial. The obligation is satisfied evenly, so each month carries one-twelfth of the price (our arithmetic)^{2, 4}.

Worked example (our arithmetic): $12,000 annual prepayment, recognized ratably (pattern from² and⁴; every amount is made up)

Twelve months at $1,000 add back to the $12,000 invoice. The monthly figure is $12,000 ÷ 12 = $1,000, and deferred revenue at any month end is $12,000 minus $1,000 for each month completed. Cash was collected once, in January, yet the income statement shows the revenue spread across the year. The chart at the top of the page draws the same schedule.

Billing the same made-up customer $1,000 each month (our arithmetic) produces the same revenue with no deferred balance, since each invoice covers the month just delivered. Chargebee’s guide makes the same point in vendor terms, that a company with high bookings but lower billings has a leading indicator of future cash flow problems⁸. For the metric side of this, see ARR vs MRR, which covers how a contract’s annual value is defined before it ever reaches revenue.

Deferred revenue, billings and remaining performance obligations

Public filings give a rare look at how the three records relate at scale. Salesforce’s roll-forward of unearned revenue for the year ended January 31, 2026 starts at $20,743 million, adds billings and other of $45,099 million, subtracts revenue recognized over time of $39,041 million and at a point in time of $2,484 million, and ends at $24,317 million³.

Worked example (our arithmetic): checking Salesforce’s roll-forward (inputs from³, in millions of dollars)

Billings equal revenue plus the growth in deferred balances: 41,525 + 3,574 = 45,099 (our arithmetic), which matches the filing line. The identity is the reason analysts read billings as a leading indicator, and why a falling deferred balance with flat billings is a warning. Salesforce also cautions that its balance does not represent the total contract value of annual or multi-year noncancellable agreements³. Seasonality, renewals, invoice duration and invoice timing all influence the balance, not just demand³.

A third figure covers what has been signed but not yet invoiced or delivered. Remaining performance obligations (RPO) are the aggregate transaction price allocated to obligations not yet delivered, or partially undelivered, at the end of the period². Datadog reports RPO of $3,461.2 million at December 31, 2025, against $2,273.1 million a year earlier, and expects to recognize substantially all of it over the next 24 months². Salesforce reports total RPO of approximately $72.4 billion at January 31, 2026, up 14 percent year over year³. HubSpot reports approximately $1.6 billion of RPO on contracts with original performance obligations longer than one year, and expects to recognize approximately 89 % of it over the next 24 months⁴.

RPO is not a revenue forecast. It is a contracted backlog measured at the allocated transaction price, and its timing is uncertain for drawdown contracts, where future revenue can vary significantly from past revenue². It also overlaps with deferred revenue, because RPO includes deferred revenue, multi-year contracts with future installment payments and certain unfulfilled orders².

Variable consideration: usage, overages and credits

Add-ons and metered billing

Usage-based and overage pricing makes the transaction price uncertain. The standard’s answer has two parts. The company estimates the variable amount, and then includes it in the price only to the extent it is probable that a significant reversal of cumulative revenue will not occur when the uncertainty resolves¹. In assessing that, an entity considers both the likelihood and the magnitude of a possible reversal⁵.

Salesforce applies it to overage fees, contingent fees and service level penalties, including an estimate in the total price only when a significant reversal is not probable³. HubSpot estimates variable consideration at contract inception and reassesses it at each reporting date⁴. In plain terms, upside that depends on future customer behavior waits until the behavior happens. DualEntry’s guide makes the same point for usage-based pricing: management must estimate variable consideration and constrain it, so that all potential upside is not booked today¹¹.

For pure usage plans the answer is simpler. Datadog recognizes revenue as the product is used for usage-delivered contracts, for monthly subscriptions based on usage, and for usage in excess of a ratable subscription². It bills committed annual or multi-year subscriptions in advance and bills usage above the commitment monthly in arrears².

Worked example (our arithmetic): committed subscription plus overage (pattern from²; amounts made up)

The overage is revenue in May, the month of use, even though the invoice goes out afterwards. The unbilled amount sits in unbilled receivables until the invoice is issued². Chargebee’s guide describes the same treatment for metered overages in vendor terms: recognized in the month in which they accrue⁸.

Plan upgrades and downgrades: contract modifications

A contract modification is a change in the scope or price, or both, of a contract that is approved by the parties⁵. Approval can be in writing, by oral agreement or implied by customary business practices⁵. Until a modification is approved, the company keeps applying the guidance to the existing contract⁵. Upgrades, downgrades and mid-term add-ons all count as modifications, which is why DualEntry’s guide treats them as a single topic¹¹. KPMG’s handbook notes that modifications continue to give rise to questions¹².

The standard gives three outcomes, and the decision tree is short.

1. A separate contract. If the scope grows because distinct services are added, and the price grows by an amount reflecting the standalone selling prices of those additions, the modification is accounted for as a separate contract⁵.
2. A termination and a new contract. If it is not a separate contract, and the remaining services are distinct from those already delivered, the company accounts for it as if the old contract ended and a new one began⁵. The consideration allocated to what remains is the unrecognized part of the original price, including cash already received, plus the new consideration promised in the modification⁵.
3. Part of the existing contract. If the remaining services are not distinct and form part of a single partly satisfied obligation, the effect is booked as a cumulative catch-up adjustment to revenue at the modification date⁵.

Many SaaS upgrades fit the second outcome. Access to the same platform after the change is a continuation of the same promise for the remaining term, and the contract is re-priced going forward.

Worked example (our arithmetic): a mid-year upgrade (rule from⁵; every amount is made up and the case is simplified)

In the made-up example the upgrade lifts monthly revenue from $1,000 to $1,500, and the first six months are not restated. If the extra module had been sold as a distinct add-on at its standalone price, the first outcome would apply instead, and the add-on would simply be recognized as its own contract⁵. A downgrade works the same way in reverse, with the new, lower price spread over the remaining term and any refund treated as in the next section⁵.

Cancellations and refunds

What happens to the deferred balance when a customer leaves depends on the contract, not on the calendar. The SEC bulletin states that the price in arrangements the customer can cancel is neither fixed nor determinable until the cancellation privileges lapse⁹. If the cancellation rights expire ratably across the term, the price becomes determinable ratably as well⁹. The current standard handles refunds differently: when a company receives consideration and expects to refund some or all of it, it recognizes a refund liability⁵.

Most enterprise SaaS contracts remove the question. Salesforce reports that substantially all its subscription arrangements are noncancellable and contain no refund-type provisions³. Where a refund is possible, the accounting depends on whether the company will pay it.

Worked example (our arithmetic): $12,000 prepaid, canceled after three months (rules from⁵ and¹¹; amounts made up)

Under the first case, a DualEntry example reaches the same place: with no refund, the deferred balance for the undelivered service is recognized immediately¹¹. The effect on metrics matters more than the accounting. A cancellation with no refund pulls the undelivered balance into one month’s revenue¹¹, which makes that month look strong while the recurring base has dropped. Net revenue retention and churn are measured on the recurring base, not on recognized revenue, which is one reason the metrics page keeps them apart.

Setup fees, add-ons and professional services

An upfront fee can look like immediate revenue, and the test is whether it buys something the customer can use on its own. DualEntry’s guide frames it as a rule of thumb: a setup fee that delivers nothing on its own is spread across the subscription rather than booked on day one¹¹. The SEC bulletin explains the principle behind it for nonrefundable fees received on entering an arrangement⁹. The bulletin’s example is a conveyed right or service that has no utility to the purchaser separate from the registrant’s performance of the other elements, so the fee follows those other elements⁹.

HubSpot recognizes onboarding, training and consulting as the services are provided, since it treats them as distinct obligations⁴. Salesforce recognizes time-and-materials work as rendered, fixed-price work on a proportional performance basis, and subscription-based services ratably³. Add-ons that extend access, such as extra seats, follow the modification rules above, and Datadog prices its additional services at or above the standalone selling price², which fits the separate-contract test of a price reflecting standalone selling prices⁵.

Annual subscription with add-ons

Worked example (our arithmetic): bundle with a discount (allocation rule from¹; SSPs and price are made up)

In the made-up bundle, the $1,500 discount is shared in proportion, not charged to one line. The rule has an exception: when a discount or variable amount relates entirely to one obligation, the standard specifies when it goes to that obligation alone¹.

Sales commissions and other contract costs

The standard also covers the cost side. A reporting organization recognizes as an asset the incremental costs of obtaining a contract that it expects to recover, meaning costs it would not have incurred if the contract had not been obtained¹. As a practical expedient, it may expense those costs when incurred if the amortization period is one year or less¹.

SaaS filings show what that looks like. Salesforce capitalizes sales commissions on new and renewal contracts, with the associated payroll and benefit costs and success fees paid to partners³. It amortizes costs on new contracts over four years, on a straight-line basis, because that reflects the estimated average period of benefit including expected renewals³. HubSpot defers commissions and amortizes them over approximately two to four years⁴.

Worked example (our arithmetic): one commission, capitalized (method from¹, four-year period from³; amounts made up)

Multi-geo and FX challenges: global billing and currency

A SaaS company that bills in euros but reports in dollars adds a second layer on top of the five steps. Revenue timing still follows delivery of the service; the exchange rate affects the dollar amount and creates gains or losses between invoice and payment¹¹. DualEntry gives the case of a U.S. company that bills €100,000 to a European customer and is paid in euros, with FX gains or losses reaching the profit and loss statement while revenue recognition stays tied to delivery¹¹.

Worked example (our arithmetic): a euro invoice (made-up exchange rates; simplified to a single usage charge)

Revenue stays at $110,000 because the service was delivered when the receivable was set up. The $5,000 shortfall is a separate currency effect.

Impact: what can go wrong, and why metrics depend on it

The failures in this area fall into a few repeated shapes, and each shows up in the primary record. Revenue taken up front on a bundle that has a service running through the term is the Synchronoss pattern¹⁰. Terms hidden in side letters change the accounting even when the main contract looks clean^{10, 9}. A refund that is expected but not recorded as a refund liability overstates revenue⁵.

The accounting also feeds the public metrics investors use. Annual recurring revenue, net revenue retention and churn appear nowhere in the five steps; they are management measures built from the same contracts that revenue recognition covers. A clean revenue schedule is therefore the base any metric definition has to reconcile to. The disclosures give outsiders a window into the schedule: FASB’s summary requires contract balances with opening and closing amounts of receivables, contract assets and contract liabilities¹. That is the roll-forward Salesforce publishes³.

The 3-3-2-2-2 rule and where it fits

Searchers often connect revenue recognition with a “3 3 2 2 2” rule. It is a growth benchmark, not an accounting rule. The pattern is T2D3, “triple, triple, double, double, double”, a mantra a venture investor named to describe a SaaS company’s annualized revenue growth⁷. The path starts at $2 million in ARR, triples to $6 million, and then follows the doubling years⁷. It is not the only growth path to SaaS success⁷.

Worked example (our arithmetic): the T2D3 path from $2 million (pattern from⁷)

The link with this page is the definition of ARR itself. A growth benchmark is only as good as the recurring revenue figure underneath it, and that figure comes from contracts that must first be recognized correctly. ARR vs MRR covers how companies define the base, and net revenue retention covers expansion on that base.

Limits of this page

The examples above are simplified. Allocation, constraint and modification calls depend on each company’s own contracts, which is why Salesforce flags both the distinct-obligation call and the standalone selling price as judgments³. The full standard, not a summary page, governs a real set of financial statements. For the related operating pages, see net revenue retention, SaaS churn rate and the metrics hub.