The revenue stage turns billed and collected amounts into reported revenue. Under ASC 606 and IFRS 15, revenue is recognized as the work is delivered, not when the invoice is sent or paid, so subscriptions, milestones, and usage each follow their own schedule.
This is where the whole cycle is measured: deferred revenue, recognized revenue, and the reports leadership uses to judge growth. Gaps anywhere upstream show up here as manual adjustments at close.
ASC 606 trips up agencies and consulting firms more than any other business type. This guide explains the 5-step revenue recognition model in plain English, with specific examples for milestone billing, retainers, and project-based engagements.
Usage-based billing, ramp deals, and entitlements have broken legacy revenue recognition. Here's what modern SaaS RevRec needs to handle - and where most teams fall short.
A technical walkthrough of how the ASC 606 five-step model applies to token and credit-based AI pricing: variable consideration, breakage, output-method progress measurement, true-ups, and contract modifications.
Token-based billing looks simple from the outside: count tokens, multiply by price, send an invoice. In practice it is a four-layer stack with its own architecture, its own vendor category, and its own revenue recognition problems. Here is how it actually works.
A step-by-step guide to turning a contracts spreadsheet into a live, interactive deferred revenue waterfall using Claude Cowork's Live Artifacts, including how to handle mid-term contract modifications under ASC 606.