See how ScaleXP works with Xero or QuickBooks.
In a 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.
ASC 606: Revenue Recognition in SaaS Companies
What ASC 606 means for SaaS: who it applies to, the five-step model, worked software examples, and how it differs from IFRS 15 and ASC 605. Plain English.
What is ASC 606?
ASC 606 is a revenue recognition standard issued by the Financial Accounting Standards Board (FASB) in the United States. It sets out the principles for recognizing revenue from contracts with customers and replaces the previous revenue recognition guidance, ASC 605.
ASC stands for “Accounting Standards Codification.” ASC 606 was developed by FASB working in conjunction with the International Accounting Standards Board (IASB) an independent private sector body that develops International Financial Reporting Standards (IFRS), with the intent of simplifying revenue recognition in the US and converging guidance internationally.
Does ASC 606 apply to my SaaS company?
ASC 606 applies to all entities that generate revenue from contracts with customers, including public and private companies, as well as non-profit organizations. In the United States, ASC 606 now applies to both public and private companies, so any business reporting under U.S. GAAP needs to follow it when recognizing revenue from customer contracts.
It’s important to note that compliance with ASC 606 is not just a one-time event. It requires ongoing monitoring and updating of revenue recognition policies and practices, ensuring continued compliance with the standard.
At ScaleXP, our platform is built for finance teams and leaders to automate tasks such as revenue recognition, while being compliant to both IFRS15 and ASC606, saving businesses both time and hassle when calculating their finances.
What does FASB say about revenue recognition?
The FASB’s standard, ASC 606, outlines a five-step model for recognizing revenue from contracts with customers:
- Identify the contract with the customer.
- Identify the performance obligations in the contract.
- Determine the transaction price.
- Allocate the transaction price to the performance obligations.
- Recognize revenue when (or as) the entity satisfies a performance obligation.
The ASC 606 guidance applies to all types of revenue-generating transactions, including the sale of goods, services, and intellectual property licenses.
How does the five-step model work on a real SaaS contract?
On January 1, 2026, a customer signs a 12-month subscription for $36,000. The contract also includes a one-time $3,000 setup fee for configuring the customer’s account, which gives the customer nothing it could use on its own. The customer is invoiced $39,000 upfront.
Step 1: Identify the contract
There is one approved contract with clear rights, payment terms and commercial substance, and collection is probable. It is a contract under ASC 606.
Step 2: Identify the performance obligations
There is one. The setup work only enables access to the software, so it is not distinct and is combined with the subscription. (If the setup were a separate implementation project the customer could buy from someone else, it would be a second performance obligation, recognized as the work is done. Our IFRS 15 guide works through that case.)
Step 3: Determine the transaction price
$36,000 plus $3,000 gives a transaction price of $39,000. There is no variable consideration.
Step 4: Allocate the transaction price
With one performance obligation, the full $39,000 is allocated to the subscription.
Step 5: Recognize revenue as the obligation is satisfied
The subscription is delivered evenly over 12 months, so revenue is $39,000 ÷ 12 = $3,250 a month. The setup fee is not recognized on day one.
| Month | Revenue recognized | Deferred revenue at month end |
|---|---|---|
| Jan 2026 | $3,250 | $35,750 |
| Feb 2026 | $3,250 | $32,500 |
| Mar 2026 | $3,250 | $29,250 |
| … | … | … |
| Dec 2026 | $3,250 | $0 |
| Total | $39,000 |
The journals
When the $39,000 invoice is raised on January 1:
| Account | Debit | Credit |
|---|---|---|
| Accounts receivable | $39,000 | |
| Deferred revenue (contract liability) | $39,000 |
At the end of each month from January to December:
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue (contract liability) | $3,250 | |
| Subscription revenue | $3,250 |
By December 31 the deferred revenue balance is zero. One caution: if the setup fee also gives the customer a right to renew without paying it again, that renewal right can be a material right, and part of the fee is then recognized over a longer period than the first 12 months.
How does it apply to software or SaaS companies?
Here are five examples of how ASC 606 applies to software or SaaS companies:
Perpetual license
If a software company sells a perpetual license to a customer, revenue recognition will typically occur at the point in time when the license is delivered to the customer. The amount recognized will be the part of the transaction price allocated to the license. Any bundled support or updates are separate performance obligations, recognized as they are provided.
Software sold as a subscription
If a software company sells a subscription to a customer, revenue recognition will occur over the subscription period. This means that revenue will be recognized each month (or other subscription period) as the company delivers the service to the customer. In an annual subscription, revenue will be recognized in monthly increments.
Upgrades and enhancements
If a software company offers upgrades or enhancements to its software to existing customers, revenue recognition will depend on the terms of the contract with the customer. If the upgrade or enhancement is considered a separate performance obligation, revenue recognition will occur when the obligation is satisfied. If the upgrade or enhancement is not a separate performance obligation, revenue recognition may occur at the same time as the original software sale.
For most SaaS companies, this means that the upgrade is recognized over the subscription term.
Professional services
If a software company provides professional services (such as implementation or customization services) to its customers, revenue recognition will typically occur over the period that the services are delivered. This may involve recognizing revenue over the course of a project, as milestones are achieved, or as services are performed.
Maintenance and support
If a software company provides maintenance and support services to its customers, revenue recognition will typically occur over the period that the services are provided. This may involve recognizing revenue monthly, as the company delivers the services to the customer.
What does ASC 606 require from a SaaS company?
For SaaS companies, ASC 606 requires them to recognize revenue over the contract period instead of recognizing it upfront at the time of sale (see how each revenue recognition method works).
To comply with ASC 606, subscription or SaaS companies must ensure that they have accurate and complete information about their contracts with customers, including the contract terms and details on pricing by service.
That information also has to stay current as contracts change. Our guide to staying GAAP compliant as SaaS subscription complexity grows covers what happens to revenue recognition once upgrades, extensions and mid-term changes multiply.
How is ASC 606 different from IFRS 15?
ASC 606 and IFRS 15 aim to ensure correct revenue recording and recognition. Both provide clear guidance, but there are differences:
Collectability threshold
ASC 606 requires probable collectability, while IFRS 15 requires it to be more likely than not.
Contract modifications
Both standards use the same criteria for treating a modification as a separate contract, so outcomes rarely differ.
Contract asset/liability presentation
ASC 606 has specific guidance, while IFRS 15 allows more flexibility.
Contract costs
Both require capitalization of qualifying fulfillment costs, but IFRS 15 requires later impairment losses to be reversed, while U.S. GAAP does not.
Variable consideration constraint
ASC 606 uses a “probable” threshold, while IFRS 15 uses a “highly probable” threshold.
Licenses
ASC 606 distinguishes between functional and symbolic intellectual property, while IFRS 15 does not.
Sale with a right of return
Both give specific guidance, treating expected returns as variable consideration with a refund liability.
These differences show the primary distinctions between ASC 606 and IFRS 15 in revenue recognition.
How is ASC 606 different from ASC 605?
ASC 606 and ASC 605 are US accounting standards that offer guidelines for recognizing revenue. ASC 606, the newer standard, replaced ASC 605 due to its limitations. Here are some key differences between the two:
1. Scope
ASC 606 applies to all industries and entities, while ASC 605 primarily applied to industries with specific revenue recognition guidance.
2. Core Principle
ASC 606 focuses on recognizing revenue when an entity transfers goods or services to a customer for the expected payment amount.ASC 605 lacked a consistent principle and was based on industry-specific guidance.
3. Five-Step Model
ASC 606 introduces a five-step model for recognizing revenue, while ASC 605 had no structured framework and instead used various specific rules and criteria.
4. Performance Obligations
ASC 606 emphasizes identifying distinct performance obligations within a contract, whereasASC 605 generally treated contract elements as separate accounting units only if they met specific criteria.
5. Variable Consideration
ASC 606 permits estimating variable consideration as part of the transaction price, subject to a constraint.ASC 605 required variable consideration to be fixed or determinable before recognizing revenue.
6. Contract Costs
ASC 606 provides guidance on capitalizing and amortizing certain contract acquisition and fulfilment costs, which ASC 605 did not address explicitly.
7. Disclosures
ASC 606 requires more comprehensive and qualitative disclosures than ASC 605 to help financial statement users understand contracts with customers better.
These differences illustrate the primary distinctions between ASC 606 and ASC 605. Implementing ASC 606 aimed to improve financial reporting consistency, comparability, and usefulness related to revenue recognition.
Has FASB changed ASC 606 recently?
FASB has not replaced or reopened the core model. Its 2024 post-implementation review of Topic 606, based on outreach with more than 2,200 stakeholders, found that most agree the standard’s long-term benefits outweigh the costs of applying it (FASB, Post-Implementation Review: Topic 606).
The most recent amendment is ASU 2025-07, issued September 29, 2025. It clarifies that share-based payment received from a customer (for example, shares or warrants given as payment) is noncash consideration within ASC 606 until the right to it is unconditional. It is effective for fiscal years beginning after December 15, 2026, with early adoption permitted (Deloitte, “FASB Releases ASU to Amend Guidance on Derivatives Scope Refinements and Make Revenue-Related Scope Clarification”, checked October 4, 2026). Few SaaS companies receive equity from customers, so for most it changes nothing.
How can software help with ASC 606 compliance?
Xero does not contain the functionality to comply with ASC 606, and QuickBooks Online Advanced includes a basic revenue recognition feature, but it doesn’t handle contract changes, multi-line invoices or audit-ready schedules at scale. Add-on software, such as ScaleXP, can help. ScaleXP imports all invoices directly from the accounting system and uses a sophisticated series of text recognition algorithms to fully automate revenue recognition. It connects to Xero and QuickBooks, and finance approves every journal before it posts.
Reporting under international standards? Read our guide to revenue recognition under IFRS 15, issued by the International Accounting Standards Board (IASB).
Revenue recognition is rarely the only manual workflow in the close. If accruals, prepayments and consolidation are costing your team the same kind of time each month, see what accounting automation covers beyond revenue recognition.
Frequently asked questions
When did ASC 606 become effective?
ASC 606 became effective for public business entities for annual reporting periods beginning after December 15, 2017, and for all other entities, including private companies, for annual periods beginning after December 15, 2019, after FASB deferred it with ASU 2020-05. Every company reporting under U.S. GAAP now applies it.
What is the main difference between ASC 606 and IFRS 15?
ASC 606 and IFRS 15 share the same five-step model, so most SaaS contracts are accounted for the same way under both. The differences are in the details: U.S. GAAP sets a higher collectibility threshold (“likely to occur” rather than “more likely than not”), does not allow impairment losses on capitalized contract costs to be reversed, classifies licenses as functional or symbolic, and offers policy elections for shipping and handling and for sales taxes.
What is a performance obligation under ASC 606?
A performance obligation is a promise in a contract to transfer a distinct good or service, or a series of substantially similar distinct services, to the customer. A promise is distinct if the customer can benefit from it on its own or with readily available resources and it is separately identifiable in the contract. In most SaaS contracts, access to the hosted software is one performance obligation satisfied over time.
How is SaaS subscription revenue recognized under ASC 606?
Under ASC 606, SaaS subscription revenue is recognized over the subscription period as the service is delivered, not when the invoice is issued or cash is received. For example, a $12,000 annual subscription billed upfront is recorded as deferred revenue and recognized at $1,000 a month. Upgrades that form part of the subscription are generally recognized over the remaining term.
How are implementation and setup fees treated under ASC 606?
Under ASC 606, implementation and setup fees depend on whether the service is a distinct performance obligation. If the customer benefits from it on its own, such as a separate implementation project, revenue is recognized as the work is performed. If it only enables access to the software, it is combined with the subscription and recognized as that service is delivered, not upfront.
How do you automate ASC 606 revenue recognition in Xero or QuickBooks?
ASC 606 revenue recognition in Xero or QuickBooks is usually automated with an add-on that reads invoice data and generates the revenue schedules and journals. ScaleXP connects to Xero and QuickBooks, builds deferred and accrued revenue schedules and journals from invoices, and posts them back to the ledger with an audit trail after the finance team reviews and approves them.
How ScaleXP does this
ScaleXP builds revenue recognition schedules from your CRM contracts and prepares the journals for Xero or QuickBooks. Finance approves them before they’re posted. See how revenue recognition works in ScaleXP
Recognition schedule calculatorSee how an invoice turns into cash and revenueTry itClose
$
Invoiced$12,000
Cash received$12,000
Revenue recognized$3,000
Deferred revenue$9,000
Totals at the end of December 2026. Revenue is $1,000 a month. Click any month to move through the schedule.
ScaleXP prepares the schedules and journals for every customer, invoice and invoice line item, and finance reviews and approves them before they’re posted to Xero or QuickBooks.
Book a demo →Invoiced in full at the start of the service period and recognized straight-line by whole month. Illustration only, not accounting advice.