Calculate recognized and deferred revenue under ASC 606 / IFRS 15 principles. Model performance obligation delivery, contract timelines, and monthly recognition schedules.
The Revenue Recognition Calculator helps finance teams apply ASC 606 and IFRS 15 principles to determine how much contract revenue should be recognized in each reporting period. Under modern accounting standards, revenue is recognized when (or as) performance obligations are satisfied — not simply when cash is received. This creates a timing difference between billing and revenue that must be carefully tracked.
This calculator models the core revenue recognition pattern: given a total contract value, delivery timeline, and performance obligation completion percentage, it computes the recognized revenue, deferred revenue balance, and a period-by-period recognition schedule. It handles both point-in-time recognition (delivery-based) and over-time recognition (ratably over the service period).
Whether you're managing SaaS subscription revenue, professional services contracts, or multi-element arrangements, this tool provides the recognition math that aligns with the five-step ASC 606 framework: identify the contract, identify performance obligations, determine transaction price, allocate the price, and recognize revenue as obligations are fulfilled.
Incorrect revenue recognition is one of the top causes of financial restatements and audit findings. Even a simple SaaS subscription requires ratable recognition over the service period. This calculator automates the math so you can verify recognition schedules, plan cash flow versus revenue timing, and ensure your bookings-to-revenue waterfall is accurate before month-end close.
Monthly Recognition (Ratable) = Contract Value / Contract Duration (months) Recognized Revenue = Monthly Recognition × Months Elapsed Deferred Revenue = Contract Value − Recognized Revenue % Recognized = Recognized Revenue / Contract Value × 100 Performance-Based Recognition = Contract Value × % Performance Delivered Setup Fee Recognition = Immediate if distinct obligation, or spread over contract if not
Result: $60,000 recognized, $70,000 deferred
A $120,000 annual SaaS contract with a $10,000 setup fee has $130,000 total contract value. If the setup fee is a distinct performance obligation recognized at delivery, $10,000 is recognized immediately. The remaining $120,000 is recognized ratably at $10,000/month. After 5 months: $10,000 setup + $50,000 subscription = $60,000 recognized. Deferred revenue balance = $130,000 − $60,000 = $70,000.
Step 1: Identify the contract — an agreement creating enforceable rights and obligations, with commercial substance and collectibility. Step 2: Identify performance obligations — distinct promises to deliver goods or services. Step 3: Determine the transaction price — the amount you expect to receive, including variable consideration. Step 4: Allocate the price — distribute the transaction price to each obligation based on standalone selling prices. Step 5: Recognize revenue — as each obligation is satisfied, either over time or at a point in time.
Multi-year contracts with annual billing create a pattern where deferred revenue builds at billing and declines as services are delivered. For example, a 3-year contract billed annually at $100K creates three billing events, each generating deferred revenue that converts to recognized revenue over the following 12 months. The balance sheet shows the waterfall of all active contracts simultaneously.
The most common mistake is recognizing revenue at billing rather than delivery. Another frequent error is failing to separate distinct performance obligations in bundled contracts, leading to incorrect timing. Companies also struggle with variable consideration estimates — usage-based or success-based fees that require judgment to estimate. Establishing clear policies and training across sales, finance, and operations prevents most issues.
ASC 606 (Revenue from Contracts with Customers) is the U.S. GAAP accounting standard governing revenue recognition. It replaced ASC 605 in 2018 and established a five-step model: identify the contract, identify performance obligations, determine the transaction price, allocate the price to obligations, and recognize revenue as obligations are satisfied. IFRS 15 is the equivalent international standard.
Recognized revenue appears on the income statement and represents earned revenue for obligations already delivered. Deferred revenue sits on the balance sheet as a liability — it's cash you've collected but haven't yet earned. As you deliver the service or product, deferred revenue converts to recognized revenue over time.
SaaS revenue is typically recognized ratably (evenly) over the subscription period because the service is delivered continuously. A $12,000 annual subscription becomes $1,000/month of recognized revenue. If the full year is billed upfront, $11,000 starts as deferred revenue and converts to recognized revenue at $1,000/month.
A performance obligation is a promise to deliver a distinct good or service to the customer. It's the unit of revenue recognition. A software contract might have multiple obligations: the license, implementation services, and ongoing support — each recognized differently. Identifying and separating performance obligations is Step 2 of ASC 606.
Revenue is recognized over time when the customer simultaneously receives and consumes benefits (e.g., SaaS, managed services). It's recognized at a point in time when control transfers at a specific moment (e.g., product delivery, license activation). The key test is whether the customer benefits as you perform, or only upon completion.
Contract modifications (upgrades, downgrades, extensions) are treated as either a new contract, part of the existing contract, or a termination-and-new-contract, depending on whether additional goods/services are distinct and at standalone selling price. Each scenario affects the recognition schedule differently. Always document the modification and its accounting treatment.
A revenue waterfall (or bookings-to-revenue schedule) shows how current bookings will convert to recognized revenue over future periods. It's essential for revenue forecasting. If you book $1M in annual contracts this month, the waterfall shows $83K/month recognized over the next 12 months. Stacking multiple cohorts creates your total revenue forecast.
Variable consideration (discounts, refunds, usage-based fees, performance bonuses) must be estimated and included in the transaction price only to the extent it's probable a significant reversal won't occur. Use either the expected value (probability-weighted) or most likely amount method. Reassess estimates each reporting period and adjust the recognized amount accordingly.