Recognized Revenue
Total revenue recognized under the company's accounting standard (ASC 606 / IFRS 15) during the period — distinct from billings (what was invoiced) and from ARR (an annualized run-rate snapshot). The income-statement top line and the basis for GAAP reporting. Common pitfall: confusing recognized revenue with ARR — for a company with mid-year contract starts, ARR exit will exceed recognized revenue for that year; the gap shrinks as the cohort matures. Boards reviewing a recognition-heavy investor pack should always see ARR alongside revenue to avoid mis-pricing growth. — Sales KPI, I'mBoard-authored (editorial tier).
I'mBoard-authored (editorial tier)
No public third-party standard anchors this KPI yet, so I'mBoard authors and maintains the definition — transparently labeled as editorial tier. See the ontology methodology for the published vs editorial tier system and the back-attribution workstream.
Rogue ID: sales.total_revenue
Type: Currency
Domain: Sales
Definition
Total revenue recognized under the company's accounting standard (ASC 606 / IFRS 15) during the period — distinct from billings (what was invoiced) and from ARR (an annualized run-rate snapshot). The income-statement top line and the basis for GAAP reporting. Common pitfall: confusing recognized revenue with ARR — for a company with mid-year contract starts, ARR exit will exceed recognized revenue for that year; the gap shrinks as the cohort matures. Boards reviewing a recognition-heavy investor pack should always see ARR alongside revenue to avoid mis-pricing growth.
Formula
Recognized Revenue = Sum of revenue earned during the period under ASC 606 (or IFRS 15). For subscription contracts, recognized ratably over the contract term; for usage / professional services, recognized as delivered. Distinct from bookings (signed contracts) and billings (invoiced amounts). Public-reporting companies should reconcile this line to the income statement.Why it matters
The audited top line that anchors every GAAP-based valuation multiple, debt covenant, and tax filing. Boards need it to track the path to profitability (revenue − cost), which subscription ARR alone cannot show.
How to interpret
For an early subscription business, recognized revenue typically lags ARR by 20–40% on an annual basis depending on contract-start distribution within the year; the gap shrinks at steady state. A material divergence between recognized-revenue growth and ARR growth in the same period usually signals either a billing-policy change or a contract-mix shift (e.g. shift to upfront-billed multi-year).
Calculation policy
How an AI agent should compute this KPI from messy company data. Free-text rules consumed at reasoning time — not a deterministic DSL. The most common ways to get this wrong are listed under Common miscomputations.
Inclusion rules
- Revenue earned during the period under the company's accounting standard (ASC 606 / IFRS 15): subscription value recognized ratably over the contract term, usage / overage recognized as consumed, professional services recognized as delivered.
- All income-statement revenue lines for the period — subscription, usage, AND one-time services — because this is the GAAP top line, not a recurring-only run-rate.
- Public-reporting companies: reconcile this figure to the income-statement revenue line.
Exclusion rules
- Bookings (signed contract value not yet earned) and billings (invoiced amounts) — recognized revenue is neither.
- ARR / run-rate snapshots —
sales.arris an annualized point-in-time contracted run-rate, NOT period-earned revenue. Keep the two distinct (see edge cases + miscomputations). - Deferred revenue still on the balance sheet (invoiced-but-unearned) until it is actually earned.
Required inputs
- Period revenue split by recognition category (subscription ratable, usage-as-consumed, services-as-delivered).
- Contract start dates and terms (to drive ratable subscription recognition).
- Period boundaries.
Data-source priority
- Audited / reviewed income statement (or the revenue sub-ledger that rolls up to it).
- Billing + revenue-recognition system (Zuora / Chargebee RevRec, NetSuite) when the close is not yet final.
- Spreadsheet revenue schedules only as a last resort — flag uncertainty in the output.
Edge cases
- Mid-year contract starts: recognized revenue for the year lags exit ARR by 20–40% depending on start-date distribution; the gap shrinks as the cohort matures.
- Multi-year upfront-billed contracts: recognize ratably regardless of the billing schedule — cash and recognized revenue diverge in that period.
- Multi-currency: convert each revenue stream on the period recognition-rate convention; never mix rates within a series.
Validation checks
- Recognized revenue ≤ cumulative billings to date (absent unbilled / accrued revenue) — a material breach signals a recognition-schedule error.
- Recognized-revenue growth and ARR growth in the same period should move together; a large divergence flags a billing-policy change or contract-mix shift (e.g. shift to upfront-billed multi-year), not a story.
- Sum of the monthly recognized-revenue numbers reconciles to the period total within rounding.
Common miscomputations
- Reporting ARR — or MRR × 12, or run-rate revenue × the period count — as recognized revenue. ARR is a contracted run-rate snapshot; for mid-year starts it exceeds recognized revenue, so the swap overstates the GAAP top line. See
sales.arr. - Reporting billings or bookings as revenue — invoiced / signed is not earned.
- Dropping one-time services from the GAAP top line (or, conversely, folding them into a "recurring revenue" figure) — recognized revenue is ALL earned revenue; recurring-only belongs in
sales.arr. - Mixing cash receipts with recognized revenue on upfront-billed contracts — collapses the rev-rec schedule that this line exists to honor.
Related KPIs
sales.arrsales.carrsales.bookings_backlogsales.bookings_backlog_totalsales.gross_marginsales.growth_rate_yoy
Source
I'mBoard editorial — authored and maintained by I'mBoard, first published 2026-04-01. No third-party standard is cited for this KPI; when one emerges, the definition is back-attributed and promoted to the published tier (a minor version bump). Read the ontology methodology for the published vs editorial tier system, attribution rules, and dispute process.
Stage relevance
| Company stage | Priority |
|---|---|
| Pre-Seed | Recommended |
| Seed | Recommended |
| Series A | Core |
| Series B | Core |
| Series C+ | Core |
| Public | Core |
Suggested for stages: Pre-Seed, Seed, Series A, Series B, Series C+, Public.
Default owning functions
- Finance
Machine-readable
- This KPI as JSON:
/api/ontology/sales/total_revenue.json - All Sales KPIs:
/api/ontology/sales.json - Full catalog:
/api/ontology/index.json
Sales Strategic Context
Executive-summary narrative for the sales section of the board pack — the CRO/CEO's one-screen synthesis of overall sales performance, market dynamics, and the story behind the quarter's numbers. Categorical state derived from operational reporting — no calculation. Renders via ExecutiveCommentary widget as multi-section tabbed prose with per-section word counts. Common pitfall: writing it as a numbers-recap repeats what the KPI table already shows; the goal is the connective tissue — why the numbers moved, what changed in the market, what the next 90 days look like. Boards read this first when scanning the deck. — Sales KPI, I'mBoard-authored (editorial tier).
Weighted Pipeline Forecast
Total pipeline value with each deal multiplied by its stage-based close probability — the canonical probabilistic forecast number. More forecasting-useful than raw pipeline value because it accounts for the conversion-likelihood mix across stages (early-stage deals weighted ~10–25%, mid-stage ~40–60%, late-stage ~70–90%). Common pitfall: using globally-flat probabilities (e.g. always 50%) instead of stage-specific calibrated ones — a reliable weighted forecast requires the stage probabilities to be back-tested against actual close rates from prior periods. — Sales KPI, I'mBoard-authored (editorial tier).