--- title: "Usage-Based Revenue Recognition: ASC 606 Explained" url: https://getlago.com/blog/usage-based-revenue-recognition description: "Usage fees are variable consideration under ASC 606 and IFRS 15. That means estimating, constraining, and truing up revenue every period. Here's how it works." authors: ["Anh-Tho Chuong"] tags: ["Pricing & Monetization"] published: 2025-06-26 updated: 2026-10-13 reading_time_minutes: 4 --- # Usage-Based Revenue Recognition: ASC 606 Explained ‍**TL;DR** Usage-based revenue recognition records income **only when, or as, the customer actually consumes the service**. Because bills fluctuate with real-time activity (API calls, gigabytes stored, minutes streamed), today's accounting rules treat those fees as *variable consideration*. You must forecast, constrain, and true-up the numbers every close. When the data pipeline is airtight, revenue mirrors value delivered; when it isn't, expect cut-off errors, audit findings, and churn. ### What "Usage-Based Revenue Recognition" Means in Plain English Usage-based revenue recognition governs contracts whose prices rise and fall with customer activity: think Snowflake credits, Twilio SMS, or AWS Lambda invocations. The final bill is unknown on day one, so finance teams must **estimate, constrain, and true-up** revenue each period instead of straight-lining it. "AI is in a second digital gold rush. Without usage-level visibility, companies are gambling with pricing, profitability, even product viability." - **Ari Vanttinen, CMO, DigitalRoute (2025)** ### Why Usage-Based Revenue Recognition Is Crucial for SaaS and AI-First Companies **In**[**OpenView's 2021 survey**](https://techcrunch.com/2021/11/04/more-saas-companies-are-shifting-to-usage-based-pricing/)**of about 600 SaaS companies, 45% used usage-based pricing, up from 34% the year before.** Analysts link the surge to AI workloads, customer demand for cost transparency, and investor pressure for higher net-revenue retention. ### Usage-Based Revenue Recognition Under ASC 606 and IFRS 15 [**ASC 606 and IFRS 15 classify usage fees**](https://getlago.com/blog/ifrs-15-explained-key-points-for-tech-billing)**as variable consideration.** What that means for you: - **Estimate** the variable piece at contract inception using either the *most-likely amount* or the *expected value* method. - **Apply the constraint**: record only what is unlikely to reverse. - **True-up** revenue when actual usage differs from your estimate. - For IP licenses with usage-based royalties, recognize revenue **strictly when the usage occurs**, even if you estimate other variables. ### Five-Step Workflow for Usage-Based Revenue Recognition 1. **Identify performance obligations**: usually "stand-ready access" to the platform. 2. **Determine the transaction price** by combining fixed minimums and variable usage. 3. **Estimate the variable consideration** and apply the constraint. 4. **Allocate the price** (often everything lands on one obligation). 5. **Recognize revenue as usage happens,** layering in true-ups as data finalizes. ### Estimating Variable Consideration for Usage-Based Revenue Recognition - **Most-likely amount**: one high-probability number, ideal for tiered overages. - **Expected value**: probability-weighted average, better for high-volume micro-transactions. - **Constraint testing**: temper forecasts with history, seasonality, and contractual caps. - **True-ups**: post catch-up entries monthly or quarterly when actual usage lands. ### System Architecture Supporting Usage-Based Revenue Recognition *Metering → Rating → Billing → Sub-ledger → GL* 1. **Real-time metering** captures raw events. 2. **Rating engine** converts units into dollars. 3. **Billing system** assembles invoices. 4. **Revenue sub-ledger** posts debits and credits by customer and metric. 5. **Data warehouse** stores immutable logs for auditors. Key controls: synchronized clocks, idempotency checks, cut-off validation, and SOX-ready evidence. ### Upsides and Landmines of Usage-Based Revenue Recognition **Benefits** - Aligns cost with value delivered. - Scales revenue automatically with adoption. - Boosts net-revenue-retention optics. **Pitfalls** - Latent data can shift revenue into the wrong period. - Over-optimistic forecasts trigger reversals. - Siloed metering, billing, and GL slow reconciliations. - Customers may misunderstand unfamiliar metrics. ### Company Examples of Usage-Based Revenue Recognition in Action - **Snowflake** books compute revenue the moment credits burn, with no waiting for the invoice. - **Twilio** records SMS revenue daily based on delivered messages. - **Spotify Ads** recognizes revenue when impressions actually serve, not when budgets load. All three refine forecasts continuously and true-up at month-end close. [![Lago CTA](https://storage.ghost.io/c/ef/b6/efb6f9b5-d1e9-43f2-b2ce-f8bffdbba6a6/content/images/2026/08/final_playbook2.png)](https://getlago.com/academy/adding-usage-without-breaking-business?utm_source=blog&utm_medium=cta&utm_campaign=usage-based-revenue-recognition) ### FAQ on Usage-Based Revenue Recognition **Q1. Can I defer every penny of variable revenue until final usage data arrives?** You can, but you'll understate revenue and raise investor eyebrows. Auditors expect a defendable estimate unless the uncertainty is genuinely weather-like. **Q2. How should I treat prepaid platform credits?** Hold them as deferred revenue and recognize only when the customer *spends* the credits. **Q3. What if prepaid credits expire unused?** If you can reasonably predict breakage, recognize that amount in proportion to usage; otherwise wait until the credits are clearly unredeemable. **Q4. Are volume discounts fixed or variable consideration?** Tiered pricing is variable because the final unit rate depends on cumulative usage. **Q5. How do I handle usage files that arrive after month-end close?** Accrue an estimate based on historical patterns, then true-up when the late data hits. Document the logic. **Q6. Do minimum commitments get straight-lined?** Yes. Minimums are fixed consideration spread evenly over the contract term; overages layer on top as variable revenue. **Q7. How do I recognize revenue when the customer disputes the usage?** Record only the undisputed portion; defer the rest until resolution under the constraint rule. **Q8. What system evidence keeps auditors happy?** Immutable event logs with ISO-8601 timestamps that reconcile to invoices and the GL, plus a written estimation policy. **Q9. How do usage models change revenue forecasting?** Blend top-down (logo count, expansion rate) with bottom-up (per-event consumption) views. Update the model monthly, since volatility is higher. For related best practices, see our guide on [revenue leakage from billing errors](https://getlago.com/blog/revenue-leakage-saas-billing). For related best practices, see our guide on [tax automation and compliance](https://getlago.com/blog/billing-tax-automation). For related best practices, see our guide on [multi-entity revenue recognition](https://getlago.com/blog/multi-entity-billing). **Q10. What's an easy audit-readiness drill?** Trace one day's raw usage for a major customer from the event log through billing to the GL. Every gap you find becomes tomorrow's process fix. ### Actionable Next Steps for Implementing Usage-Based Revenue Recognition - **Clean your data feeds.** Timestamped, immutable events are non-negotiable. - **Write down your constraint logic.** Auditors will ask *why* each estimate is "probable." - **Automate the true-up.** Spreadsheets collapse once usage explodes. - **Cross-train finance, engineering, and product.** Everyone needs a shared "meter" vocabulary. - **Revisit forecasts quarterly.** Usage patterns shift; your model should too. ### Further Reading on Usage-Based Revenue Recognition - OpenView Partners, *State of Usage-Based Pricing* (2023) - PwC, "Variable Consideration under ASC 606" (2024) - Bain & Company, "Why SaaS Customer Success Is Failing" (2024) - RevenueHub, "Sales- and Usage-Based Royalties" (2024) - TechRadar Pro, "Usage Data Fuels the Next Wave of AI Monetization" (2025) ‍