Revenue Recognition Examples Explored

Why is revenue recognition one of the most difficult tasks your organization handles? The short answer is that by its very nature, revenue recognition is complicated. However, standards have and continue to be put in place to streamline this often problematic process. This blog provides revenue recognition examples and shows what you can do to alleviate the complexities of revenue recognition.

Designed to improve the clarity, consistency, and comparability when communicating financial information, generally accepted accounting principles (GAAP) is a common set of accounting principles, standards, and procedures issued by the Financial Accounting Standards Board (FASB) that public companies in the US must follow. If you do business internationally, there are other accounting principles that you must adhere to such as the International Financial Reporting Standards (IFRS).

Key Revenue Recognition Statistics & Benchmarks

Understanding the prevalence and impact of revenue recognition challenges helps context for why this matters to your business.

The Compliance Challenge

• 37% of companies have experienced revenue recognition audit findings or restatements (AICPA 2024 survey)
• 16% of private companies lack a documented revenue recognition policy, despite ASC 606 requirements
• Revenue restatements average $8.2 million in value and take an average of 15 months to correct (SEC Office of Inspector General)
• Manual revenue processes add an average of 21 days to month-end close (Deloitte CFO Survey)

SaaS Industry Specifics

• 68% of SaaS companies use multiple systems to manage revenue recognition, creating reconciliation headaches (Billing Platform Industry Report)
• Average SaaS revenue recognition error rate: 3.2% of total revenue before audit corrections (industry benchmark)
• Deferred revenue complexity: Companies with 30%+ of revenue deferred more than 12 months have 2.4x higher audit risk than those with shorter deferrals

Financial Impact

• Companies with strong revenue recognition systems close books 4 days faster on average (CFO.com survey)
• Audit costs for revenue issues average $145K for mid-market companies; manual processes increase this by 35-50%
• Staff time spent on revenue reconciliation: Mid-market companies spend an average of 260 hours/month manually managing revenue processes

Adoption Trends

• 81% of public companies report ASC 606 is “fully implemented” (FASB survey)
• 63% of private companies still rely heavily on spreadsheets for revenue recognition (down from 79% in 2020—adoption is accelerating)
• Companies with revenue recognition software report 94% accuracy versus 87% for manual processes

5 Steps of Revenue Recognition

Established by both the FASB and International Accounting Standards Board (IASB), ASC 606 and IFRS 15 are recent revenue recognition standard that affects all businesses (public, private, and non-profit) that enter into contracts for the transfer of goods or services. According to ASC 606 / IFRS15 principles, there are five steps that companies must adhere to in order to recognize revenue.

1. Identify the contract with a customer: Whether written, oral, or implied, the contract is a legally binding document that defines the rights and obligations of both parties.
2. Identify the performance obligations in the contract: Describes the products and/or services promised to the customer (i.e. performance obligations). If the products or services are distinct, they are accounted for separately within the contract.
3. Determine the transaction price: Establishes the amount the customer is expected to pay in exchange for the products or services.
4. Allocate the transaction price to the performance obligations in the contract: Explains how the transaction price is to be allocated across performance obligations (i.e. products or services).
5. Recognize revenue when (or as) performance obligations are satisfied: Revenue is recognized when performance obligations are satisfied by transferring the products or services from the seller to the buyer.

On the surface these steps look simple enough, however, revenue recognition is anything but easy. For starters, to ensure adherence with GAAP and other regulatory requirements, promote consistency, and ensure revenue is not misstated, a revenue recognition policy should be created and closely followed. This blog digs a bit deeper into creating a revenue recognition policy.

Although there are two main accounting methods – cash basis and accrual basis – there are a number of ways revenue can be recognized, adding to the complexity.

Revenue Recognition Quick Reference Checklist

Use this checklist to quickly assess whether your revenue recognition approach is compliant and complete:

Pre-Contract Assessment

☐ Customer has the intent and ability to pay
☐ Identified all performance obligations (separate products/services that customer benefits from independently)
☐ Determined if any obligations are satisfied over time vs. at a point in time
☐ Established standalone selling prices (SSPs) for each obligation
☐ Customer terms include no unusual contingencies or penalties that affect recognition

At Contract Signing

☐ Total transaction price documented (including fixed and variable amounts)
☐ Revenue allocation calculated using SSPs
☐ Refund or return liability estimated based on historical data
☐ Contract modification rules established (if customer can change terms mid-contract)
☐ Collectibility assessment completed (especially for enterprise or long-term contracts)

Monthly Revenue Recognition

☐ Each performance obligation revenue recognized per its satisfaction schedule
☐ Deferred revenue reduced by amount recognized in current period
☐ Actual refunds/returns compared to accrual; adjustment made if variance exceeds 5%
☐ Variable consideration (bonuses, usage fees) included only if highly probable
☐ Aged receivables reviewed; collectibility concerns flagged and reserved against

Quarterly/Annual

☐ Revenue policies reviewed for consistency with recent contract types
☐ SSPs reviewed and updated if market conditions changed significantly
☐ Reconciliation completed: Total revenue recognized = Total deferred revenue used + Current period revenue
☐ Contract modifications logged and revenue adjustments prospectively applied
☐ High-risk contracts (bundled deals, performance-based, long-term) manually reviewed

Audit-Ready Documentation

☐ Written revenue recognition policy updated and on file
☐ Contract-by-contract revenue schedule prepared
☐ SSP methodology and supporting market data documented
☐ Refund liability calculation and historical support documented
☐ List of contract modifications and their revenue impact provided
☐ All significant revenue estimates (refunds, variable consideration, collectibility) assumptions documented

Common Mistakes to Avoid (Checklist)

☐ Do NOT recognize revenue when cash is received—only when earned
☐ Do NOT ignore refund/return liabilities—reserve conservatively
☐ Do NOT treat bundled contracts as single obligations—disaggregate properly
☐ Do NOT use guessed SSPs—document methodology and support with data
☐ Do NOT include variable consideration unless “highly probable”—be conservative
☐ Do NOT miss contract modifications—prospectively adjust revenue
☐ Do NOT overlook collectibility risk—assess customer credit before recognizing
☐ Do NOT operate without a written policy—document everything

What’s the Best Revenue Recognition Method for Your Business?

Before diving into the various ways revenue can be recognized, let’s take a look at pros and cons of both accounting methods.

Cash-basis accounting

As defined by Investopedia, cash basis refers to a major accounting method that recognizes revenues and expenses at the time cash is received or paid out.

Often used by start-up companies or small businesses, cash-basis accounting contains some restrictions that will prevent usage if you:

• Sell products or services on credit
• Require inventory to account for income
• Offer credit to customers
• Have annual gross receipts of more than $25 million for three preceding tax years, except if you’re a small business that doesn’t keep inventory

Accrual-basis accounting

Defined by Investopedia, accrual accounting measures a company’s performance and position by recognizing economic events regardless of when cash transactions occur.

Now that we’ve covered the two primary accounting methods, let’s discuss the five main ways revenue can be recognized.

1. Completed contract method: Allows you to recognize revenue when the entire contract is fulfilled and when all performance obligations have been met.
2. Cost recovery method: Prohibits companies from recognizing revenue related to a sale until costs associated with the sale have been paid by the buyer. In other words, you can only recognize revenue after recouping the costs associated with the performance obligations.
3. Installment method: Typically used for large dollar purchases, it enables the company to recognize a percentage of the total revenue as payments are received.
4. Percentage of completion method: Enables companies to recognize a percentage of the revenue as contractual milestones, deliverables, or other indicators are reached.
5. Sales-based method: Regardless of whether the customer pays with cash or credit, you can recognize revenue at the time of sale.

What’s the best revenue recognition method for your business? Essentially, it depends on your industry. For example, if you’re in retail sales the most logical choice would be the sales-based method. If you own a car dealership you may opt for the installment method.

Common Revenue Recognition Mistakes & How to Avoid Them

Even with ASC 606 standards in place, companies repeatedly make the same revenue recognition errors. Here are the most common pitfalls and how to prevent them:

Mistake 1: Recognizing Revenue When Cash Is Received (Not When Earned)

The Problem: Companies new to accrual accounting often default to cash-basis thinking. They recognize revenue the moment a check arrives or a credit card processes, regardless of whether the service has been provided.

Example: A SaaS company receives a $12,000 annual payment in January and immediately recognizes the full $12,000 as January revenue, leaving nothing for February-December. This violates ASC 606 and creates misleading financial statements.

The Fix: Implement deferred revenue (unearned revenue) accounts. Train accounting teams that cash receipt and revenue recognition are different events. Use billing software that automatically defers revenue and recognizes it on a schedule tied to service delivery.

Mistake 2: Underestimating or Ignoring Refund Liabilities

The Problem: Companies record revenue but fail to reserve for expected returns, credits, or cancellations. When actual returns exceed the accrual, companies must restate financial statements.

Example: A subscription platform recognizes $1 million in monthly recurring revenue but historically experiences 5% cancellations. If they only reserve 2%, they’ve overstated revenue by $30,000 in that month. Multiply by 12 months and auditors catch a $360,000 overstatement.

The Fix: Analyze historical return rates by customer cohort, contract type, and season. Use machine learning where possible to refine estimates. Reserve conservatively and adjust upward only when actual performance proves the historical rate has improved. Document your methodology for auditors.

Mistake 3: Failing to Identify Separate Performance Obligations in Bundled Deals

The Problem: Companies treat a bundle (e.g., software + implementation + support) as a single performance obligation and recognize all revenue upfront or on a single schedule, even though the components satisfy performance obligations at different times.

Example: A company bundles a perpetual software license ($500K) with 2 years of support ($50K). If they recognize all $550K upfront because it’s one “deal,” they’ve violated ASC 606. The support is a separate obligation that should be recognized over 24 months.

The Fix: Create a checklist for your sales team: “For each contract, does the customer benefit from each component independently, and is each component transferable?” If yes to both, it’s a separate obligation. Build this discipline into your revenue recognition policy and train sales to flag bundled deals early.

Mistake 4: Using Incorrect Standalone Selling Prices (SSPs)

The Problem: When allocating bundled contract prices to separate performance obligations, companies must estimate what each component would sell for on its own. Incorrect SSPs lead to misallocated revenue and audit findings.

Example: A company sells software + training as a bundle for $200K. They estimate the software’s SSP as $150K and training as $50K. But if market data shows the software typically sells for $120K standalone, the allocation is wrong, and revenue is misstated by $12K on this deal alone.

The Fix: Document your SSP methodology. Use market comparables (competitor pricing), cost-plus analysis, or adjusted market assessment to triangulate realistic SSPs. Review SSPs annually and update them as markets evolve. Have a revenue committee review SSP changes before contract approval.

Mistake 5: Prematurely Recognizing Variable Consideration

The Problem: Contracts often include performance bonuses, rebates, penalties, or usage-based fees that are variable. ASC 606 requires you to estimate variable consideration only if it’s “highly probable” won’t reverse in a future period.

Example: A contract includes a $50K performance bonus if the customer achieves a KPI. The company assumes it will be achieved and recognizes the $50K immediately. Later, the KPI isn’t hit. The company must reverse $50K in revenue, creating a restatement.

The Fix: Use the “most likely amount” or “expected value” method (whichever is more predictive) to estimate variable consideration. Be conservative. Only include variable amounts when you have historical data or contractual certainty. Document your assumptions.

Mistake 6: Mishandling Revenue from Subscription Downgrades or Changes

The Problem: Mid-contract changes (downgrades, add-ons, price increases) are contract modifications and must be accounted for correctly. Companies often fail to prospectively adjust revenue, causing timing errors.

Example: A customer pays $1,000/month for a premium subscription but downgrades to a $500/month standard tier mid-month. A company might continue recognizing $1,000/month instead of adjusting to $500/month going forward. Over a year, this creates a $6K overstatement.

The Fix: Build subscription management software that automatically detects changes, calculates the impact, and adjusts revenue recognition prospectively. Flag mid-month changes for manual review. Audit a sample of downgrades monthly.

Mistake 7: Ignoring Collectibility Risk

The Problem: ASC 606 requires revenue to be recognized only when “payment is probable.” If there’s significant doubt a customer will pay, revenue should not be recognized, even if all other criteria are met.

Example: A company ships goods to a customer with a history of payment disputes and deteriorating credit. They recognize the revenue because the product was delivered, but later the customer disputes the charge. Revenue must be reversed, but the product is already in the customer’s hands.

The Fix: Implement a credit review process before or at contract signing. Flag high-risk customers (startup phase, deteriorating credit, dispute history). For these, consider delaying revenue recognition until payment is received or reserving a collectibility allowance. Use revenue recognition software that flags age of receivable and allows manual holds.

Mistake 8: Not Documenting Revenue Recognition Policies

The Problem: Companies lack a written, detailed revenue recognition policy. This creates inconsistency—different contracts are treated differently—and audit headaches. Auditors expect to see a comprehensive, documented policy.

Example: One contract manager recognizes a performance bonus upfront; another defers it. Over time, similar transactions are treated inconsistently, creating audit findings.

The Fix: Document your revenue recognition policy in detail. Cover:

• How you identify performance obligations
• Your SSP determination methodology
• Variable consideration rules (thresholds, estimation methods)
• Refund/return policies
• Handling of contract modifications
• Any industry-specific treatments

Review and update this policy annually. Train all customer-facing teams (sales, CS, finance) on it. Get external audit review before filing.

Revenue Recognition for SaaS Companies

Unlike virtually any other business model, software as a service (SaaS) revenue tracking is notably more complex because of the unique characteristics of its revenue recognition. Focused on monthly recurring revenue (MRR), SaaS companies live by MRR figures to gain a better understanding of comparable business trends and to ensure financial growth. And, what do you think is at the center of MRR… revenue recognition!

Although the SaaS business model provides predictable and repeatable revenue streams, it’s not always easy to know when revenue and expenses should be recognized. While this business model boasts recurring revenue, accounting complications arise from upgrades and downgrades, packages, bundles, discounts, and promotions, lost revenue due to dunning, customer churn, credits or refunds, etc.

For these reasons, the accrual-basis accounting method is preferred by the majority of SaaS companies. Let’s use an example to explain why. We’ll assume that the ABC SaaS Company is operating as a subscription-based business and customers have their choice of being billed monthly, quarterly, or annually. Accrual-basis accounting enables SaaS businesses to recognize revenue when it’s earned. If a customer pays an annual subscription fee of $12,000 in advance, the ABC SaaS Company is able to recognize $1,000 in revenue for each month of the subscription. What happens to the revenue that was collected but can’t yet be recognized? Referred to as deferred revenue, it is placed in a liability account until the service has been provided.

Whether you’re just starting your SaaS business or are on track for substantial growth, one thing is certain – manually handling SaaS accounting functions is not only tedious and time-consuming but error-prone.

Real-world Revenue Recognition Examples

Revenue recognition principles look straightforward on paper, but they play out differently across industries and business models. Here are concrete examples that show how the five-step process actually works:

SaaS Company: Annual Subscription with Mid-Year Upgrade

Let’s expand on our ABC SaaS Company example. A customer signs a 12-month contract on January 1 for $12,000 annually, billed upfront. Under ASC 606 accrual-basis accounting, ABC SaaS recognizes $1,000 in revenue each month.

But what happens when the customer upgrades on July 1 to a premium tier for an additional $6,000 annually? This is where the complexity emerges:

• Contract modification: The upgrade is considered a new performance obligation as of July 1
• Standalone selling price: ABC SaaS must determine the fair market value of the premium tier ($7,200/year) versus the standard tier ($12,000/year)
• Revenue allocation: The remaining 6 months of the original contract ($6,000) plus the new premium service ($3,000 for 6 months) are recognized prospectively
• Monthly recognition: Starting July, ABC SaaS recognizes $1,500/month ($1,000 original + $500 upgrade)

This contract modification alone can trip up companies without proper systems in place. Manual tracking creates audit risk and often leads to restatements.

Manufacturing: Milestone-Based Long-Term Project

A construction equipment manufacturer signs a $5 million contract to build and deliver custom machinery. The contract spans 18 months with payment milestones:

• 30% down payment upon signing
• 40% upon delivery of core components (month 12)
• 30% upon final installation and acceptance (month 18)

Under ASC 606, the manufacturer cannot recognize revenue equal to cash received. Instead:

• Identify performance obligation: Delivery of the complete, functioning equipment system
• Determine transaction price: $5 million total
• Recognize over time: Because the customer simultaneously receives and consumes the benefit as the equipment is built, revenue is recognized using the “percentage of completion” method
• Monthly revenue: Based on costs incurred versus total estimated costs. If $1.5 million in costs are incurred by month 12 (30% of total estimated $5M project costs), the manufacturer recognizes $1.5 million in revenue—even though only $3.5 million has been collected.

The timing mismatch between cash and revenue creates working capital challenges that software systems help manage.

Healthcare: Subscription Plus Usage-Based Billing

A telemedicine platform offers two revenue streams: a $99/month subscription and $50 per consultation beyond included visits. Under ASC 606:

• Subscription revenue: $99/month is recognized monthly as the performance obligation (access to platform) is satisfied
• Usage revenue: Each consultation beyond the included limit creates a separate, variable performance obligation. The platform can only recognize usage revenue when the consultation occurs and the customer is billed (when the price is probable to be collected)
• Refund liability: The platform estimates returns/cancellations and defers that portion as a refund liability, recognized when the return risk expires (typically 30-60 days after the subscription month ends)

Many healthcare companies underestimate return likelihood, causing revenue restatements when actual returns exceed accruals.

Retail with Extended Warranties

A consumer electronics retailer sells a laptop for $1,200 with a 3-year extended warranty for $300 (sold together or separately).

Under ASC 606:

• Hardware revenue: $1,200 recognized at point of sale (performance obligation satisfied)
• Warranty revenue: $300 is NOT recognized at sale. It’s deferred as a liability and recognized ratably over 36 months ($8.33/month) as the warranty coverage is provided each month
• Claims adjustments: When warranty claims are filed, the retailer records a separate warranty expense against the deferred revenue

Without proper accrual systems, retailers often accidentally recognize warranty revenue upfront, overstating profit in year 1 and creating unexpected losses in years 2-3.

Bundled Software License Plus Implementation Services

A B2B software company sells a 3-year enterprise license ($300,000) bundled with implementation services ($150,000). The customer cannot benefit from the software without implementation.

The key question: Are these one performance obligation or two?

• Analysis: While bundled, implementation is distinct from the license itself. Other customers implement the same software themselves. Therefore, these are two separate performance obligations.
• Allocation: Using standalone selling prices, assume the license is $300,000 and implementation is $200,000 in a standalone market. Total standalone value is $500,000. The actual contract price is $450,000, so:
  • License allocation: $450,000 × ($300,000/$500,000) = $270,000
  • Implementation allocation: $450,000 × ($200,000/$500,000) = $180,000
• Revenue recognition:
  • Implementation revenue: $180,000 recognized as services are completed (monthly over 6 months, or based on milestones)
  • License revenue: $270,000 recognized over the 36-month term ($7,500/month)

Bundling creates systematic errors when companies don’t properly disaggregate obligations and determine standalone selling prices.

Simplify Revenue Recognition

Because of the complexity and uniqueness, SaaS companies need systems that are built for their pricing models, can automate repetitive financial tasks, and ensure ASC 606 and IFRS 15 compliance. BillingPlatform provides native cloud-based solutions that deliver this and much more. Our industry-leading BillingCloud solution gives you the freedom to easily transition from simple one-time subscription-based pricing models to creative metered and usage-based plans.

By simplifying revenue management with a rules-based revenue recognition engine, you’re able to define rules specific to your company and make assignments in real time, as billing, payments, and credit events take place. And that’s not all! To speed financial closure processes, BillingPlatform provides real-time subledger transactions that integrate into downstream enterprise resource planning (ERP) and accounting systems. With BillingPlatform, you get everything you need in a single cloud-based platform to run your business with greater efficiency, accuracy, and control. Does that sound like something your company could benefit from? If so, our team is ready to help.

 

Frequently Asked Questions About Revenue Recognition

Q: What’s the difference between ASC 606 and IFRS 15?

They are essentially the same standard. ASC 606 is the U.S. GAAP version (issued by FASB), while IFRS 15 is the international version (issued by IASB). Both were developed together and have the same five-step framework. The practical difference: U.S. public companies must use ASC 606; non-U.S. companies and some private companies use IFRS 15. Implementation guidance differs slightly, but the core principles are identical.

Q: Can we still use the “completed contract” method instead of ASC 606?

No. ASC 606 replaced the older revenue recognition methods (completed contract, percentage of completion, installment, etc.) effective January 1, 2018 for public companies and January 1, 2019 for private companies and nonprofits. While legacy contracts signed before the effective date can use old rules if preferred, new contracts must follow ASC 606.

Q: How do we determine if our revenue is “probable” to be collected?

ASC 606 doesn’t define a bright-line rule (e.g., “95% probability”). Instead, evaluate the specific customer:

• Credit rating and payment history
• Current financial condition
• Age of similar receivables (are overdue payments common?)
• Contractual terms (can they dispute or withhold payment?)
• Economic conditions (are they in an industry in decline?)

If you have 5+ years of history, calculate your actual collection rate by customer type. Use that as a baseline. For new customers or high-risk geographies, apply a lower probability assumption or delay recognition.

Q: If a customer cancels or returns within our return window, do we still recognize revenue?

Yes, but with a liability. ASC 606 requires you to recognize revenue at the time of sale AND establish a refund liability for expected returns. The liability reduces net revenue. As the return window closes without a return, the liability is reversed and revenue is finalized. Example: Recognize $100 in revenue but set a $5 refund liability = $95 net revenue recognized. If no return occurs by day 31, reverse the $5 liability and net revenue becomes $100.

Q: How do we handle revenue for customers in countries with different accounting standards?

If your company is public or consolidated by a public company, you must follow U.S. GAAP (ASC 606) globally for consolidated financial statements. However, if you operate subsidiaries in specific countries, those subsidiaries may follow local GAAP or IFRS 15. The best practice is to use ASC 606/IFRS 15 everywhere for consistency, then reconcile to local requirements if needed.

Q: What happens if we get revenue recognition wrong? Are there penalties?

Yes. Consequences include:

• Audit adjustments and qualification of your audit opinion
• Restatement of prior financial statements (expensive and damaging to reputation)
• Penalty taxes if the error is deemed material and intentional
• SEC enforcement if material misstatements mislead investors (public companies)
• Litigation risk from shareholders claiming you overstated earnings
• Creditor concerns: Banks and debt covenants often require revenue compliance

It’s why strong revenue systems and documentation are critical!

Q: Can we recognize revenue before a contract is fully signed?

Generally, no. ASC 606 requires a signed contract (written, oral, or implied through conduct). However, if you can demonstrate that both parties are committed and the contract terms are substantially agreed, you may recognize revenue even if the signature page is pending. The key: you must be able to enforce the contract. If the customer can still walk away without consequence, hold revenue.

Q: How should we handle performance bonuses or success fees?

Performance bonuses are variable consideration. ASC 606 says you can only recognize them if you’re “highly probable” won’t reverse. In practice:

If bonus is tied to customer performance (e.g., they achieve a KPI), include it only if historically achieved 90%+ of the time.
If bonus is tied to your performance (e.g., you deliver a feature by a date), include it only if you’re highly confident you’ll meet the deadline.
If uncertain, defer the bonus revenue until the performance is certain.

Q: How often should we update our revenue recognition policy?

A: At minimum, annually. However, you should update it whenever:

• You enter a new industry or business model
• You introduce bundled products or services
• A major customer contract type changes (e.g., you now offer performance-based pricing)
• Accounting guidance updates (rare but can happen)
  You experience an audit finding or adjustment related to revenue

Assign policy ownership to your Controller or Chief Accounting Officer, and include it in your internal control testing annually.

Q: Do we need to disclose all revenue contracts in our financial statements?

Public companies must disclose:

• Disaggregated revenue (by geography, product line, contract type, performance obligation category)
• Key accounting judgments and assumptions
• Unfulfilled performance obligations (backlog that will be recognized in future periods)
• Significant contract modifications

Private companies have fewer requirements but should still document contracts supporting material revenue transactions in case of audit.