SaaS revenue recognition: ASC 606 and IFRS 15 basics for subscriptions

You closed an annual contract, the cash is in the bank, and your accountant says you earned only a small part of it this month. Your investor update shows bookings, your income statement shows revenue, and the two never match. You need to know why, so you can read your own numbers and ask your accountant the right questions.

Revenue recognition is the set of rules that decides when money from a customer counts as revenue. Under U.S. GAAP the rules sit in ASC Topic 606; under international standards, in IFRS 15. Both apply to subscription software as described in What is SaaS?. This guide explains the shared model in plain words. It is not accounting advice: how the rules apply to your contracts is a judgment for your accountant and auditor.

Revenue recognition in plain terms

Think of a gym that sells a year’s membership for $600 in January. The gym has the cash on day one, but it still owes you eleven more months of access. Each month it delivers, it earns $50. Until then, the unearned part sits on its balance sheet as something it owes you.

Two terms carry the whole topic:

• Deferred revenue: money billed or received for service not yet delivered. Some filings, such as Salesforce’s, call it unearned revenue.
• Performance obligation: a distinct promise in the contract, such as software access or an onboarding project.

The five steps

The IFRS Foundation summarizes IFRS 15 in five steps. FASB’s Topic 606, issued as Accounting Standards Update 2014-09 in May 2014, uses the same model. The IFRS Foundation says IFRS 15 was issued “together with” Topic 606 and applies to annual periods beginning on or after 1 January 2018. The two are not identical in every detail, and FASB publishes a comparison of them, so check which standard your company reports under.

Step	What the standard asks	The SaaS question
1. Identify the contract	Which agreement or agreements exist with the customer	Is the contract the order form, the online terms, or both?
2. Identify the performance obligations	Which distinct promises the contract makes	Is onboarding, support or a term license separate from access?
3. Determine the transaction price	How much consideration you expect to receive	What about discounts, credits and usage fees you cannot know yet?
4. Allocate the price	Split it across the promises by relative stand-alone selling price	Does a “free” onboarding package still take a share of the price?
5. Recognize revenue	As each promise is fulfilled, when the customer obtains control	Is access delivered over the term or at one point in time?

The core principle, in the IFRS Foundation’s words, is that a company “recognises revenue to depict the transfer of promised goods or services to the customer”, in the amount it expects to be entitled to.

How a public SaaS company applies it

Salesforce’s annual report for the year ended January 31, 2026, shows the model at scale (Form 10-K):

• Revenue from cloud services is generally recognized ratably over the contract term.
• Term licenses are “generally recognized at the point in time when the software is made available to the customer.”
• Customers are generally invoiced “in advance, in annual installments”, which is why unearned revenue builds up on the balance sheet.
• Remaining performance obligation, the contracted revenue not yet recognized, was about $72.4 billion. About $35.1 billion of it, or 48%, was expected to become revenue in the next 12 months.

The last figure shows the gap between signing and earning: $35.1 billion / $72.4 billion = 0.485, so roughly half of what customers had committed would turn into revenue within a year.

Worked example: a 12-month contract with onboarding

Example: a labeled hypothetical, for illustration only. On January 1 you sign a 12-month contract. Your list prices are $12,000 for a year of access and $3,000 for onboarding, $15,000 in total. You give a 10% discount, so the customer pays $13,500 up front. Assume your accountant concludes that onboarding is a distinct promise, completed in January, and that list prices are the stand-alone selling prices. If the conclusion is instead that onboarding is not distinct, it is combined with access. Its fee is then recognized with the access, not in January, and the table below would change.

Step 4 splits the $13,500 by relative stand-alone selling price:

• Access: $12,000 / $15,000 = 80%, and 80% x $13,500 = $10,800, or $10,800 / 12 = $900 a month.
• Onboarding: $3,000 / $15,000 = 20%, and 20% x $13,500 = $2,700, recognized when delivered in January.

Date	Event	Revenue this month	Deferred revenue after the event
January 1	Invoice paid, $13,500 cash	$0	$13,500
January 31	Onboarding done, one month of access	$2,700 + $900 = $3,600	$13,500 - $3,600 = $9,900
February 28	One month of access	$900	$9,900 - $900 = $9,000
Each month to December	One month of access	$900	falls by $900
December 31	Last month of access	$900	$0

Check the total: $3,600 + 11 x $900 = $3,600 + $9,900 = $13,500, the full contract. The discount did not land only on onboarding or only on access. Both carry 10% less than list, because step 4 spreads it in proportion.

Bookings in January are $13,500. Revenue in January is $3,600. Neither number is wrong; they answer different questions. Metrics such as MRR and ARR are management measures and are not defined by either standard, so label them when you report them. For how billing events like upgrades and proration show up in those metrics, see SaaS subscription.

Usage fees and multi-year deals

Usage fees. A usage charge is unknown when you sign. Step 3 asks for the amount you expect to be entitled to, so estimates enter the analysis. This is a judgment area: document how you bill usage and take the contracts to your accountant.

Multi-year contracts. A three-year deal billed annually does not change when access is delivered. Revenue still follows delivery, month by month, while billing follows the payment schedule. Remaining performance obligation counts all contracted revenue not yet recognized, billed or not, so it also includes the later years not yet invoiced. The license metric and term in the contract, covered in SaaS licensing, feed directly into steps 2 and 3.

Common mistakes

1. Booking an annual invoice as revenue in the month it is paid. It makes one month look large and the next eleven look empty. Why it happens: a cash-based ledger records money when it arrives. Instead: record deferred revenue and release it as the service is delivered.
2. Treating a bundled “free” service as worth nothing. If the package is a distinct promise, step 4 allocates by stand-alone selling price, so it can still take a share of the contract. Why it happens: the invoice line shows $0. Instead: keep a list price for every promise you make.
3. Reporting bookings or ARR as revenue. Investors and auditors read them as different numbers. Why it happens: bookings are the figure sales celebrates. Instead: show bookings, revenue and deferred revenue side by side, each labeled.
4. Deciding setup-fee or usage treatment alone. These are the judgment areas of the standards. Why it happens: they look like bookkeeping. Instead: write down the contract terms and get your accountant’s view before the first audit or due diligence.

Sources

• IFRS Foundation, IFRS 15 Revenue from Contracts with Customers, checked October 17, 2026.
• FASB, Accounting Standards Update 2014-09, Revenue from Contracts with Customers (Topic 606), May 2014.
• Salesforce, Inc., Form 10-K for the fiscal year ended January 31, 2026, SEC EDGAR, checked October 17, 2026.

In three sentences

ASC 606 and IFRS 15 share one five-step model: identify the contract and its promises, set and allocate the price, and recognize revenue as each promise is delivered. In the example, a $13,500 prepaid contract produces $3,600 of revenue in January and $900 a month after that, with deferred revenue falling to zero by December. Keep bookings, revenue and deferred revenue apart, and take setup fees, usage charges and bundles to your accountant, because those are the judgment calls.