Revenue recognition is a key topic for software-as-a-service (SaaS) businesses. Getting it right means handling complexities such as multifaceted subscription models, ongoing service obligations, and tiered pricing schemes. With the global SaaS market valued at $464.7 billion in 2025 and expected to reach over $1.1 trillion by 2033, the stakes are high for these businesses.

Below, we’ll explain revenue recognition for SaaS businesses, including what it is, the challenges they face, and what solutions and best practices you can use to counter them.

What’s in this article?

• What is revenue recognition?
  
• ASC 606 and IFRS 15: Accounting standards for revenue recognition
  
• Challenges of revenue recognition for SaaS businesses
  
• Solutions for effective revenue recognition in SaaS
  
• SaaS revenue recognition examples
  
• How Stripe can help SaaS businesses with revenue recognition
  

What is revenue recognition?

Revenue recognition is an accounting principle that outlines the specific conditions under which income is recorded (recognized) as revenue. It governs when a business can include certain amounts in its income statement. According to this principle, businesses can recognize revenue only when the key event leading to the completion of the intended sales process has occurred (i.e., when the revenue was earned or fulfilled, in full or in part) and the business can reasonably expect to collect payment for the goods or services provided.

ASC 606 and IFRS 15: Accounting standards for revenue recognition

Modern SaaS revenue recognition is governed by two frameworks: Accounting Standards Codification (ASC) 606 and International Financial Reporting Standard (IFRS) 15. ASC 606 was issued in 2014 by the Financial Accounting Standards Board (FASB), which primarily serves US companies. IFRS 15, effective since January 1, 2018, is the international counterpart to ASC 606. It was issued by the International Accounting Standards Board (IASB) and provides guidelines for businesses that operate globally.

The purpose of ASC 606 is to improve consistency in revenue recognition practices across industries, especially for complex, multicomponent contracts. IFRS 15 expands this harmonized approach globally. Both standards use a five-step approach for revenue recognition:

• Identify the contract with a customer: A contract is an agreement between two or more parties that creates enforceable rights and obligations. The contract must meet certain criteria to be recognized under ASC 606.

• Identify the performance obligations: Performance obligations are promises in a contract to transfer distinct goods or services to the customer. A company must identify each distinct good or service that’s promised.

• Determine the transaction price: The transaction price is the amount of compensation a company expects to be entitled to in exchange for transferring promised goods or services to a customer.

• Allocate the transaction price: If a contract has multiple performance obligations, a company must allocate a transaction price to each one. It should reflect the expected amount of compensation for satisfying each performance obligation.

• Recognize revenue when a performance obligation is satisfied: Revenue is recognized when control of the promised goods or services is transferred to the customer—either over time or at a specific point in time, depending on the criteria met.

Challenges of revenue recognition for SaaS businesses

Below are some of the challenges SaaS businesses face regarding revenue recognition.

Distinguishing between multiple-element arrangements

Bundled services or products are standard in SaaS. When a business combines several components under one price tag, it must decide how to divide revenue across each element. For example, a SaaS company might sell a package that includes software licenses, training, and customer support for a flat fee of $10,000. What’s the best way to break down that price? If the business sells the software alone for $8,000, training for $1,500, and support for $1,000, it can allocate the bundled revenue based on these stand-alone prices.

Determining the transaction price in contracts with variable consideration

Variable payment structures, such as those tied to performance bonuses or usage-based discounts, can complicate SaaS contracts. Setting an exact transaction price becomes trickier when the final amount fluctuates. For instance, a SaaS company might make a deal where it’ll get paid more if user adoption rates are high. If the rate is above 90%, the company will receive $20,000. But if the rate falls short, it will get only $15,000. If past data shows that the company hits that 90% mark 75% of the time, then the company would record revenue of $18,750 up front.

Recognizing revenue for post-contract support

After a contract ends, SaaS companies often still have commitments to keep, whether they’re updates, enhancements, or other support services. For example, a SaaS provider might sell software that comes with the promise of quarterly updates for a year. If each update brings new features, then the company would recognize the revenue for those updates gradually, as they roll out.

Addressing customer refunds and returns

There will always be customers who want refunds or decide to end their subscriptions early. Businesses must decide when and how to recognize this change. For instance, a SaaS company might know five out of every 100 subscribers will typically ask for refunds. Instead of recording all the projected revenue up front, the company might recognize only 95% of it. That way, it’s better positioned to handle the financial impact of those inevitable refund requests.

Solutions for effective revenue recognition in SaaS

• Automate revenue recognition processes: Manual accounting methods can lead to errors and inconsistencies. Automated tools can help correct them. Many SaaS businesses use automated accounting software to allocate revenue, adjust for changes, and guarantee compliance with standards such as ASC 606 and IFRS 15. For example, a SaaS company that gets 1,000 new contracts every month might use automation to manage them. This ensures that revenue is recognized accurately and on time.

• Adopt a performance obligation approach: Breaking down contracts into separate performance obligations can make revenue recognition smoother. If a contract promises software access, training, and support, each one must be treated as a distinct promise. By identifying each obligation and its stand-alone selling price, companies can recognize revenue as each is satisfied. For instance, a company might sell software with one year of support. If the software is delivered instantly but the support spans the year, revenue for the software can be recognized immediately while the support revenue is spread out over 12 months.

• Distinguish between one-time and recurring revenue: SaaS companies often earn revenue from both one-time sales and recurring subscriptions, and these sources of revenue are recorded differently. For example, if a customer pays for a yearly subscription and an add-on training session, the business will recognize the training revenue up front but spread out the subscription revenue over the year.

• Stay ahead with continuous training and updates: Regular training sessions and workshops can keep finance teams up-to-date on the latest guidelines and best practices for accounting standards. If the IASB tweaks something in IFRS 15, a well-informed business can adjust its practices right away and avoid potential noncompliance issues later.

• Set aside a provision for refunds and cancellations: SaaS businesses will always need to handle refunds. By setting aside a specific provision based on historical data, they can create a safety net; this makes it easier to manage the financials when refunds do occur. For example, if 5% of customers historically ask for refunds, a company can set aside that percentage from its recognized revenue.

• Treat refunds and concessions carefully:
  When refunds occur, it’s important to reverse the previously recognized revenue. If a customer receives a concession or a discount partway through their subscription, you’ll need to adjust revenue recognition for the remaining months.

• Engage with financial consultants: Working with financial experts or consultants who specialize in SaaS can provide insight into potential pitfalls and best practices.

• Be transparent with stakeholders: Being clear about how you recognize revenue builds trust with investors and board members, and within your team. You can regularly share insight into the company’s financial health and your methods.

• Simplify and standardize contracts: SaaS companies often juggle a range of subscription plans, add-ons, and bespoke deals. You’ll want to simplify and standardize these contract terms when possible. For example, if a SaaS business offers three primary subscription tiers, having template contracts for each one can make it simpler to determine how to recognize revenue for each subscriber.

• Account for free trials: Many SaaS companies offer free trials. Even though no money changes hands during the trial, it’s important to track these users. You’ll begin to record revenue only if and when they transition to a paid subscription.

• Monitor variable considerations:
  Some SaaS contracts might include performance-based bonuses or penalties. These can impact the amount of revenue recognized. If a customer receives a discount after hitting a usage milestone, your revenue calculations must account for that change.

• Dedicate a team to revenue recognition: If possible, SaaS businesses should have a specialized revenue recognition team. This team can handle complex subscription contracts, adjust revenue recognition when a customer upgrades or downgrades their plan, and coordinate with sales or customer success teams to ensure revenue is recognized accurately at all times.

• Invest in automated software: Accounting software that’s customized for the SaaS model can handle variable billing cycles, churn, and plan changes. For a SaaS business with monthly and annual subscribers who can change or cancel at any time, automated tools can adjust revenue recognition in real time.

• Keep detailed documentation: Given the fluid nature of SaaS subscriptions, detailed records are key. Suppose that a customer starts on a monthly plan, shifts to an annual plan, and then adds extra features six months in. Documenting each of these changes helps clarify how and when the revenue from this customer should be recognized.

• Conduct internal audits: Internal audits can identify areas where a SaaS business might be under-recognizing or over-recognizing revenue, helping it make data-driven adjustments.

• Communicate across departments: When the sales and finance teams communicate effectively, the finance team can be fully informed of any deal features (e.g., a special discount, a trial period) that might affect how revenue should be recognized.

• Standardize processes on a global scale: Many SaaS companies have a global customer base. Balancing generally accepted accounting principles (GAAP) and IFRS requirements can be tricky, but finding methods that comply with both creates consistency. If a SaaS company offers its platform in the US and Europe, standardized policies mean that revenue is recognized according to the same principles no matter where the customer is located.

• Adjust financial planning: SaaS businesses should adjust financial planning to mirror their revenue recognition. If there’s a surge in new annual subscriptions during a seasonal sale, forecasts should account for that revenue being recognized over the next 12 months, not immediately.

• Prepare for contingencies: Developing a plan to address potential disruptions (e.g., industry shifts, economic downturns, global crises) can help a SaaS company adjust its revenue recognition practices if and when those events occur.

SaaS revenue recognition examples

Revenue recognition in SaaS becomes complex when contracts move beyond monthly credit card charges. Here’s how standard ASC 606 and IFRS 15 principles apply across common SaaS billing scenarios.

Annual upfront subscription (deferred revenue)

• On January 1, a customer signs an annual contract and pays $12,000 up front for one year of cloud platform access. Because zero service has been delivered as of that day, $0 is recognized as revenue. The entire paid amount is recorded on the balance sheet as deferred revenue (contract liability). Over the 12-month term, the company fulfills its performance obligation evenly. It recognizes $1,000 in revenue each month and reduces deferred revenue by the same amount.
  

Bundled setup fees and platform access

• A customer purchases a one-year contract for $24,000 and pays a mandatory $6,000 onboarding and setup fee for $30,000 total. Accounting treatment differs based on how onboarding is classified:

  • Onboarding isn’t distinct: If the setup has no stand-alone value without the software, it isn’t a distinct performance obligation. The entire $30,000 payment is combined and recognized at $2,500 a month over the one-year contract period.
    
  • Onboarding is distinct: This is true for cases such as complex data migration and custom training that could be provided by a third party. The business recognizes the $6,000 fee immediately at a point in time when setup is complete. And it recognizes the $24,000 contract over time at $2,000 per month.
    

Midcycle upgrade (contract modification)

• A customer that pays $1,200 a year for their current plan upgrades on July 1 to a premium tier that costs $2,400 a year for the remaining six months. For the first six months of that year, the business recognizes $100 a month for $600 total. Because the remaining services are distinct and priced at the premium rate, the business treats the change prospectively. It recognizes $200 a month for the remaining six months for $1,200 total. So for that year, the business recognizes a total revenue of $1,800 for that customer.
  

Hybrid subscription plus usage-based billing

• An application programming interface (API) platform charges a flat monthly platform fee of $500, plus $0.01 per API call billed in arrears at month-end. In March, the customer executes 50,000 API calls for $500 in usage. The platform recognizes the $500 platform fee once in March, then the $500 usage bill as the calls are consumed to satisfy the variable consideration requirement. By the end of the month, it’ll fully recognize the total revenue of $1,000.
  

Early cancellation with a partial refund

• A customer pays $6,000 up front for a six-month contract. At the end of the second month, they cancel and receive a $4,000 refund for the remaining four months. The business recognizes $2,000 as earned revenue for the first two months. At cancellation, it clears the remaining $4,000 in deferred revenue directly against the cash refund.
  

How Stripe can help SaaS businesses with revenue recognition

Stripe Revenue Recognition is a comprehensive solution for high-growth businesses. As your business scales, revenue recognition becomes more challenging and time-consuming. Revenue Recognition can automate all your accrual accounting needs, recording your transactions, billing terms, and revenue, and generating reports that comply with accrual accounting. This automation allows you to focus on your business’s core operations.

And as financials become more complicated when you’re working with upgrades, downgrades, refunds, and disputes, Stripe can automate the process of recording these revenue changes. This ensures that you have audit-ready financial statements that offer a thorough view of your business operations.

Here’s a detailed breakdown of what Stripe Revenue Recognition offers.

Holistic view of your earnings

• Consolidation is key: Stripe Revenue Recognition shows you all your Stripe transactions and terms, including subscriptions, invoices, and individual payment transactions.

• Data integration: If your revenue stream also includes non-Stripe sources, you can import that data to Revenue Recognition for one consolidated dashboard that logs all revenue, fulfillment schedules, and service terms in one place. This gives you a true picture of your financial health.

Streamlined reporting

• Automated dashboards: Stripe automates the accounting report process, creating instantly available accounting reports that feature detailed tables, charts, and journal entries compliant with standards such as ASC 606 and IFRS 15.

• Revenue waterfall: A revenue waterfall is a detailed monthly breakdown that displays both booked and recognized revenue by month, which allows you to easily visualize changes over time.

Custom features

• Tailored revenue rules: Stripe allows you to create and automate custom rules for recognizing revenue based on your specific accounting practices and needs.

• Flexible accounting protocols: With Stripe, you can handle a variety of revenue types effortlessly, whether you need to exclude pass-through fees, manage tax recognition schedules, or open and close accounting periods to make historical adjustments.

Real-time audit preparedness

• Instant traceability: Stripe can make it easier to prepare for audits. Trace any revenue amount from any report in Revenue Recognition back to its root, whether that’s a specific customer or one-time transaction.
  

Beyond its dedicated Revenue Recognition solution, Stripe’s broader suite of financial tools and services can also help simplify the complexities of revenue recognition for businesses. Here’s where this can help.

Subscription billing

Stripe’s subscription billing service automates recurring billing cycles and can adjust to different pricing models, pricing changes, and customer upgrades—reducing the burden on accounting departments.

Automated invoicing and billing

Stripe offers automated invoicing and billing features that speed up the billing process and ensure error-free reports. These features can be customized according to your business’s billing practices.

Integration with accounting software

Businesses can integrate Stripe with several types of accounting software, allowing for automated data transfer. This reduces manual data entry and enables easier tracking of revenue figures over time.

Flexible financial architecture

Stripe’s platform can scale with your business, providing more advanced features when you need them. This adaptability allows the revenue recognition process to remain consistent and manageable even as business operations expand.

Learn more about revenue recognition with Stripe.