September 2026 Summaries

ASC 606 revenue recognition remains a closely scrutinized financial-reporting area, particularly for SaaS, subscription, and usage-based businesses, where variable pricing, contract changes, and performance-obligation judgments add complexity. The report cites a historical Anti-Fraud Collaboration review in which improper revenue recognition appeared in 43% of examined SEC fraud schemes, while noting that the SEC’s $8.2 billion in fiscal 2024 remedies covered all enforcement actions rather than revenue cases alone. PCAOB findings also showed deficiencies in revenue-testing procedures in 48% of 97 broker-dealer audits where revenue was tested, though these findings concern audit work rather than necessarily inaccurate company reporting. Since public companies began adopting ASC 606 in 2018, most S&P 500 adopters used the modified retrospective method, and disclosures often expanded substantially. FASB’s 2024 post-implementation review concluded that the standard is meeting its purpose and that its benefits justify its costs, despite one-time implementation expenses and higher ongoing judgment requirements for some organizations; IASB similarly found IFRS 15 to be working as intended. The report argues that automated revenue-management systems can reduce manual work and accelerate financial closes, citing research and vendor case studies, and presents Orb’s event-level usage tracking, billing lineage, accounting controls, and NetSuite integration as tools intended to support audit-ready ASC 606 workflows.

Revenue recognition is becoming more challenging for SaaS and AI companies as subscription and usage-based pricing expand, with the global subscription economy projected to grow from $557.7 billion in 2025 to $2.52 trillion by 2035. Under ASC 606, companies must recognize revenue as promised goods or services are delivered, requiring careful treatment of performance obligations, variable usage fees, prepaid credits, contract changes, and deferred revenue. Finance teams report difficulty scaling reconciliation and revenue-recognition processes, with 73% saying company growth outpaces finance capacity and more than half of SaaS and subscription businesses taking 6–14 days to close their books. Compliance remains a material concern, as improper revenue recognition was alleged in 69% of SEC accounting and auditing actions tied to announced restatements in fiscal 2022, while data complexity, data quality, and manual work are recurring obstacles. AI and automation adoption is increasing, though reported performance claims vary in methodological transparency; these tools can support reconciliation, forecasting, audit trails, and close processes but do not replace accounting judgment. The piece argues that usage-based billing particularly requires reliable, traceable raw usage data and automated accounting controls, and presents Orb’s billing and revenue-recognition platform as infrastructure intended to provide ASC 606-aligned reporting, period controls, auditability, and integrations with systems such as NetSuite.

Credyt is presented as a wallet-based billing platform focused on authorizing customer spend before AI inference, while the guide argues that growing usage-based businesses also need integrated metering, pricing, contracts, invoicing, credits, revenue reporting, and finance operations. It compares seven alternatives—Orb, Metronome, Lago, Stripe Billing, Chargebee, Maxio, and Zuora—according to their emphasis on usage metering, payment ecosystems, open-source deployment, subscription management, or enterprise financial workflows. The guide positions Orb, acquired by Adyen in July 2026 but described as continuing to operate independently, as a revenue design platform distinguished by retention of raw usage events, SQL-defined metrics, dimensional pricing, pricing simulations, enterprise contract management, prepaid credits, invoicing, and integrations with NetSuite and Salesforce. Metronome, acquired by Stripe in January 2026, is framed as a usage-billing option for organizations using Stripe; Lago offers an open-source and self-hosted model; Stripe Billing combines billing with payment infrastructure; Chargebee and Maxio emphasize subscription and financial operations; and Zuora targets large enterprises with quote-to-cash and revenue-management requirements. The guide concludes that the appropriate platform depends on operational priorities such as payment-provider preference, pricing flexibility, infrastructure control, contract complexity, finance integration needs, and the ability to test pricing changes against historical usage before deployment.

Fintech companies often require usage-based billing systems capable of handling transaction volumes, interchange pricing, credits, commitments, multiple currencies, customer hierarchies, contract-specific rules, and accounting compliance alongside traditional subscriptions. The comparison examines Orb, Stripe Billing, Zuora, Maxio, Chargebee, Metronome, and Lago, assessing capabilities such as raw usage-event retention, flexible metric definitions, hybrid and dimensional pricing, invoice correction processes, revenue recognition, ERP and CRM integrations, global operations, and deployment models. Orb is presented as particularly focused on usage-native billing, with persistent raw events, SQL and visual metric tools, pricing simulations, plan versioning, prepaid credits, accounting-period controls, and NetSuite integration, while Stripe Billing and Metronome emphasize connections to Stripe’s payments ecosystem, Zuora and Maxio target broader enterprise quote-to-cash and finance operations, Chargebee combines subscription and usage billing, and Lago offers open-source and self-hosted flexibility. The discussion notes that retaining granular events can support auditability, backfills, re-rating, and controlled adjustments, while finance integrations and revenue-recognition workflows can reduce reconciliation work. Adyen acquired Orb on July 1, 2026, although Orb continues to operate as a standalone product.