Stripe invoices aren't revenue: how to turn them into ASC 606 schedules with a webhook

Businesses often face a distinction between when cash is received or an invoice is issued, and when revenue is actually earned under accounting standards like ASC 606 or IFRS 15. For instance, a customer paying $2,400 upfront for a year yields cash immediately, but the revenue is recognized gradually as the service is delivered. While Stripe handles billing effectively, its internal revenue recognition system is noted as a closed system with percentage-based volume fees, which may limit alignment with external accounting requirements.

The defrr API offers a way to bridge this gap by calculating month-by-month schedules for billed, recognized, and deferred revenue. This is achieved by extracting the service period and amount from a Stripe invoice line item upon finalization, typically via a small webhook handler, and sending this data to defrr. The API provides a stateless calculation of the schedule, ensuring daily ratable accuracy without relying on probabilistic estimation.

A practical consideration highlighted is the importance of correctly interpreting Stripe's Unix epoch timestamps using the accounting timezone. A mismatch can lead to revenue starting a day early and incorrect allocation, which may not be immediately apparent as both incorrect and correct schedules will still balance. The defrr tool can either provide a pure calculation, which holds no customer data, or record the contract in a defrr workspace for finance team approval and reporting, requiring additional customer and product details.