What is revenue recognition?
Revenue recognition is the accounting rule that decides when a company can record revenue from a signed contract on its income statement. In US GAAP it follows ASC 606, and in IFRS it follows IFRS 15. Both frameworks use the same five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate the price to each obligation, and recognize revenue as each obligation is delivered. The timing matters because a signed order, a sent invoice, and recognized revenue almost never happen on the same day.
Read the full answer →
What is the difference between ratable and usage-based recognition?
Ratable recognition spreads a fixed subscription fee evenly across the service period, so a 12,000 annual contract books 1,000 of revenue each month regardless of how much the customer uses the product. Usage-based recognition records revenue as the customer actually consumes units, so a metered contract may book 400 one month and 2,100 the next. Most SaaS seats are ratable because access itself is the deliverable. API calls, messages sent, data processed, and compute hours are usage-based because the obligation is satisfied unit by unit.
Read the full answer →
What is the difference between bookings, billings, and revenue?
Bookings is the total contract value signed in a period, including future years. Billings is the amount invoiced in a period, which is often just the first year of a multi-year deal or the next billing cycle. Revenue is what accounting actually recognizes in the period under ASC 606, which for subscription seats means a fraction of the contract spread over the service term. A 36,000 three-year deal signed on day one shows as 36,000 of bookings, 12,000 of billings, and 1,000 of revenue in month one.
Read the full answer →
What is deferred revenue?
Deferred revenue is cash a company has collected (or invoiced) for services it has not yet delivered. On the balance sheet it sits as a liability, not revenue, because the obligation to the customer is still open. A customer who prepays 12,000 for an annual subscription creates 12,000 of deferred revenue on day one, which releases to the income statement at 1,000 per month as the service is delivered. Deferred revenue is one of the first balances an auditor samples because it ties directly to the ASC 606 performance-obligation model.
Read the full answer →
How are multi-year contracts recognized?
Under ASC 606, a multi-year contract still recognizes revenue over the service period, not at signing. A three-year 36,000 deal with annual auto-renew prices locked in creates 36,000 of bookings on day one and roughly 1,000 of revenue per month across 36 months. If the contract bills annually, each year drops into deferred revenue when invoiced and releases monthly. Price escalators, ramp deals, and upfront discounts have to be allocated across the periods they apply to, which is why finance usually wants to see the full schedule before close.
Read the full answer →
How is SaaS revenue recognized differently from services revenue?
SaaS subscription revenue is almost always ratable: the customer gets continuous access to the platform, so each day of the term is a performance obligation satisfied over time. Services revenue, like implementation or onboarding, is treated as a separate obligation and recognized either at completion (milestone) or as hours are delivered (percentage of completion). If a SaaS contract bundles a free implementation with the subscription, finance has to split the transaction price between the two obligations using standalone selling prices, then recognize each piece on its own pattern.
Read the full answer →
Who owns revenue recognition inside the company?
Primary ownership sits with finance. The Controller owns the day-to-day application of ASC 606: contract review, schedule setup, deferred revenue releases, and close-cycle accuracy. The CFO owns the policy, the audit relationship, and any disclosure in the financial statements. Sales ops and RevOps own the clean data that feeds the schedules: contract start dates, line-item amounts, billing frequency, and any non-standard terms. External auditors review the policy and sample schedules every year. Legal reviews custom clauses that could change the recognition pattern.
Read the full answer →
What are the audit implications of revenue recognition?
Revenue is almost always the highest-risk area in an annual audit. Auditors sample signed contracts, trace them to the revenue schedule, test the performance-obligation split, and verify deferred revenue balances tie to open obligations. Side letters, verbal commitments, and non-standard discounting are red flags that can force a restatement. The practical sales-ops impact is that every unusual deal needs the paper trail attached in the CRM before close, because a missing addendum discovered six months later can delay the audit and move revenue between periods.
Read the full answer →
How does revenue recognition affect sales commissions?
Most plans pay commission on bookings at close, not on recognized revenue, because reps need a near-term incentive and the full contract value is already locked in. Finance then capitalizes the commission under ASC 606 and amortizes it over the expected customer life, which is a balance-sheet entry, not a change to the rep paycheck. Clawbacks matter: if a customer churns inside a defined window or a deal is unwound, part of the commission is recovered. Multi-year uplifts, ramp deals, and services splits are the common places plans and schedules disagree.
Read the full answer →
What is the five-step model under ASC 606?
Step one, identify the contract with the customer. Step two, identify the distinct performance obligations in the contract. Step three, determine the transaction price, including variable consideration like usage overages or discounts. Step four, allocate the transaction price to each performance obligation using standalone selling prices. Step five, recognize revenue when (or as) each obligation is satisfied, either at a point in time or over time. The model applies to every customer contract and is the backbone of every revenue schedule a Controller signs off on.
Read the full answer →
What triggers a change in revenue recognition on an existing deal?
Contract modifications are the common trigger: an upsell that adds seats, a renewal that resets the term, a downgrade, or a mid-term price change. ASC 606 treats each modification as either a new contract, a termination plus replacement, or a cumulative catch-up, depending on whether the added goods or services are distinct and priced at standalone value. The sales-ops job is to make sure the modification is captured in the CRM with its effective date, so finance can route it to the correct accounting treatment and keep the schedule accurate.
How does CRM data quality affect revenue recognition?
Every revenue schedule is only as good as the contract metadata behind it. Service start date, service end date, billing frequency, line-item amounts, and performance-obligation split all have to be correct in the system of record before finance can book the entries. If sales ops lets reps enter free-text start dates or skip contract line items, the Controller rebuilds the schedule by hand every month-end. A CRM with required fields at close, structured line items, and clean attachments cuts the close cycle and keeps auditors out of the forecast review.
Read the full answer →
