The principle is simple to state and difficult to apply. The hard part is identifying each performance obligation in a contract and determining the pattern over which it is satisfied, which is where ASC 606 and IFRS 15 do the real work.
Revenue recognition is the accounting principle that governs when a company can record a sale as revenue on its income statement. Under GAAP (ASC 606) and IFRS (IFRS 15), revenue is recognized as the promised goods or services are delivered to the customer, not when the contract is signed or the cash is collected. For a SaaS business, subscription revenue is recognized ratably over the contract term as the service is provided, which is why bookings, cash, and recognized revenue are three distinct numbers that rarely match in any single period.
The six things to understand about revenue recognition before you build a subscription P&L, close a quarter, or sit across from an auditor. Each one is a place real finance teams either report defensible numbers or quietly produce ones that fall apart in diligence.
Revenue recognition is the rule that revenue is recorded when it is earned by delivering goods or services to the customer, not when the contract is signed and not when the money arrives. The timing of cash is a separate question that lives on the balance sheet, not the income statement.
The current authoritative guidance in the United States is ASC 606, issued by the Financial Accounting Standards Board. The equivalent under international standards is IFRS 15, issued by the IASB. The two were deliberately converged and share the same five-step model, which is why a SaaS business can usually read one and apply the other with minor adjustments.
For a software-as-a-service subscription, access to the platform is a performance obligation satisfied continuously across the contract term. The transaction price is spread evenly across that term, usually by month or by day. A twelve-month annual contract signed on day one does not become revenue on day one. It becomes revenue in twelve equal parts.
Bookings is the total contract value of what was signed in a period. Cash is what was collected in a period. Recognized revenue is what was earned by delivery in a period. The three almost never match. A clean finance team reports all three and never substitutes one for another in investor or board material.
When a customer pays upfront for a year of service, the cash sits on the balance sheet as deferred revenue, a liability, because the service is still owed. Each month, the earned portion moves off deferred revenue and onto the income statement as recognized revenue. The deferred revenue balance is a leading indicator of future recognized revenue.
Auditors and the SEC treat revenue as the single highest-risk account on the financial statements, because misstatement is both common and material. Mature finance teams keep a written revenue policy, map each contract to the five-step model, and reconcile recognized revenue to the CRM contract record every period. The documentation is what makes the number defensible.
Both ASC 606 and IFRS 15 are built on the same five-step model. The cards below walk through each step in the order a finance team applies it to a signed contract. The output of the model is a schedule that says how much revenue to recognize, in which period, for every performance obligation in the contract.
A contract exists when both parties have approved the arrangement, their rights and payment terms are identifiable, the contract has commercial substance, and collection is probable. Verbal agreements, implied contracts, and master agreements with separate order forms all qualify, provided the criteria are met. The signed order form is where most SaaS contracts live.
A performance obligation is a distinct promise in the contract. SaaS access is one. Implementation services may be another. Premium support may be another. Training may be another. The question is whether the customer could benefit from each on its own, or whether they are so interdependent they form a single combined obligation. The answer drives everything downstream.
The transaction price is the total consideration the business expects to receive in exchange for the promised goods or services. Discounts, rebates, usage-based fees, performance bonuses, and refund rights all affect it. Variable consideration must be estimated and constrained. Non-cash consideration must be measured at fair value. The output is a single number that will be allocated in step four.
The transaction price is allocated across each performance obligation in proportion to its standalone selling price. If subscription access and implementation are bundled at a discount, the discount is spread across both in proportion to what each would have cost sold separately. Standalone selling prices come from observable sales data, pricing guidelines, or an acceptable estimate.
Revenue is recognized when control of each performance obligation passes to the customer. For subscription access, that happens continuously across the term, so the allocated amount is spread ratably. For a one-time implementation, it happens at a point in time, when the service is delivered and accepted. The pattern of satisfaction drives the pattern of recognition.
The five steps produce a schedule for every contract: how much revenue to recognize, in which period, for which performance obligation. The sum of the schedules across the whole book, read month by month, is the recognized revenue line on the income statement. The schedules are also the source for deferred revenue, unbilled receivables, and the roll-forward disclosures auditors expect.
The five-step model is general. The cards below describe how it lands on the specific contract shapes a SaaS business signs every week. Each card isolates a common fact pattern and the recognition treatment that goes with it, in the order a finance team would walk through a close.
A standard annual SaaS subscription is a single performance obligation satisfied over time. The annual contract value is divided evenly across the twelve months of the term. A one hundred twenty thousand dollar annual deal signed on the first of the month recognizes ten thousand dollars in each of the following twelve months, regardless of whether the customer paid upfront, quarterly, or monthly.
A three-year subscription at an annualized price recognizes the total contract value ratably across all thirty-six months. Multi-year prepayments inflate the deferred revenue balance but do not pull recognized revenue forward. The accounting answer is independent of the billing cadence, which is why bookings and recognized revenue diverge sharply for subscription businesses signing long-term deals.
A one-time implementation fee is a separate performance obligation if the service is distinct, meaning the customer could benefit from the implementation on its own or alongside another provider's software. If the implementation is so specialized it only has value when bundled with the subscription, it is combined into a single obligation and recognized ratably across the term.
Usage-based fees, overage charges, and metered consumption are variable consideration. They are estimated at contract inception where a reliable estimate is available, or recognized as incurred where it is not. Many SaaS businesses recognize usage overages in the month the usage occurs and keep the base subscription on the ratable schedule.
A mid-term upgrade is treated as a contract modification. If the additional services are distinct and priced at standalone selling price, the modification is accounted for as a separate contract. Otherwise, it is combined with the original contract and the remaining performance obligation is re-measured and re-allocated across the remaining term.
Refund rights and service credits reduce the transaction price at contract inception, not when the refund is claimed. The expected refund amount is estimated, constrained to the portion that is highly probable not to reverse, and excluded from recognized revenue. Credits actually issued move against the refund liability, not against future recognized revenue.
Revenue recognition is a close process, a disclosure requirement, and a diligence battleground all at once. The six cards below describe the places where getting it right or wrong has the largest consequences for a SaaS business, in the order they tend to surface across a company's lifecycle.
Every month, the finance team runs the revenue schedules for every active contract, confirms new deals have been scheduled, confirms churned deals have been stopped, and produces the recognized revenue line on the income statement. The close is where the model turns into reported revenue, and where ambiguity in the five steps becomes a specific number.
External auditors treat revenue as the highest-risk area on the financial statements. They test contract samples against the five-step model, confirm balances with customers, roll forward deferred revenue, and verify the mapping between the CRM contract record and the ledger entry. A defensible policy and clean documentation turn the audit into a review rather than a reconstruction.
In a financing round or an acquisition, buy-side teams routinely rebuild the recognized revenue schedule from the contract file to verify the number. Overstated ARR, bookings reported as revenue, or non-recurring one-time fees counted as subscription revenue get caught here. The diligence version of the number is the one that survives into the final term sheet.
Public filers disclose their revenue policy, performance obligations, disaggregation of revenue by category, remaining performance obligations, and contract balance roll-forwards. The disclosures are not a formality. They are how investors read the shape of the recurring book and how it moves. Thin disclosures invite questions about what is being hidden.
Gross margin, operating margin, net income, and most SaaS efficiency ratios use recognized revenue as a denominator or numerator. A misstated revenue line misstates every ratio built from it. The downstream effect is why auditors, boards, and investors look at recognition policy before they look at the metrics it produces.
Sales commissions are paid on bookings or cash, not recognized revenue, which is correct economically. ASC 606 also requires that the incremental cost of obtaining a contract be capitalized and amortized across the contract term, which affects reported margin. The commission liability, the deferred commission asset, and the recognized revenue schedule all have to tie out.
Strkr is a CRM where every subscription record carries its start date, end date, annualized value, and billing cadence. The contract is the source of truth for the revenue schedule, so recognized revenue, deferred revenue, and the bookings line all reconcile to the same account, instead of being reassembled from three systems at month end.
Revenue is recognized when it is earned, which means when the promised goods or services have been delivered to the customer. It is not recognized when the contract is signed and not when the cash is received. Signing creates an obligation. Collecting cash settles a receivable. Only delivery converts the obligation into revenue on the income statement, which is the single principle that drives both ASC 606 and IFRS 15.
ASC 606 is the revenue recognition standard issued by the Financial Accounting Standards Board, codified as Topic 606 in the FASB Accounting Standards Codification. It applies to contracts with customers under US GAAP and uses a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate the transaction price to the obligations, and recognize revenue as each obligation is satisfied.
IFRS 15 is the equivalent standard under international financial reporting standards, issued by the International Accounting Standards Board. It was developed jointly with the FASB and uses the same five-step model as ASC 606. For most SaaS businesses the practical effect is identical. Companies reporting under both frameworks maintain a single revenue policy that satisfies both standards, with footnoted differences where they exist.
For a standard SaaS subscription, access to the software is a single performance obligation satisfied continuously over the contract term. The transaction price is spread ratably across that term, usually in equal monthly or daily portions. A twelve-month contract signed on the first of the month recognizes one-twelfth of the contract value in each of the following twelve months. Multi-year contracts follow the same logic over a longer horizon.
Bookings is the total contract value signed in a period, including multi-year commitments. Recognized revenue is the portion earned by delivery in a period, as governed by the recognition schedule. Cash is what was collected in a period, driven by invoice terms. The three almost never match in any single period for a subscription business, and reporting one as if it were another is one of the most common sources of misstatement in diligence.
Deferred revenue is the balance sheet liability that holds cash received from customers for services not yet delivered. When a customer prepays for an annual subscription, the full prepayment lands in deferred revenue. Each month, the earned portion is reclassified onto the income statement as recognized revenue, and the deferred revenue balance decreases by the same amount. Deferred revenue is both a liability and a leading indicator of future recognized revenue.
It depends on whether the implementation is a distinct performance obligation. If the customer could benefit from the implementation on its own, or if a competing provider could do the implementation separately, the fee is distinct and recognized when the implementation is delivered. If the implementation is so specialized it only has value when bundled with the subscription, it is combined with the subscription obligation and recognized ratably across the contract term.
Revenue is the largest line on most income statements and the one most sensitive to judgment calls, which makes it both material and prone to misstatement. Auditors and regulators treat it as the highest-risk account by default. They sample contracts, test them against the five-step model, confirm balances with customers, and roll forward deferred revenue. A documented policy and clean source data in the CRM and ledger are what make the review efficient instead of adversarial.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
