Invoice corrections8 min
Usage billing with late events
Late usage is normal. The hard part is correcting the invoice in a way customers, support, and finance can all follow.
Blog
Billing articles for teams that have to explain the invoice
This is a working library for SaaS teams dealing with customer-visible billing pressure: delayed usage, mid-cycle plan changes, duplicate retries, webhook drift, migration risk, and audit questions that show up after launch.
Each article is written to help support, finance, product, and engineering reach the same answer faster — and make billing decisions easier to explain across the business.
Start here
7 articles
Browse by billing problem
Pick the situation your team is in right now: invoice corrections, proration questions, migration planning, duplicate retries, webhook reliability, or audit pressure in a shared system.
- Proration clarity7 min
Hybrid plans + proration
Upgrades, downgrades, and seat changes only feel fair when the customer can see exactly why a credit or debit appeared.
- Audit pressure7 min
Multi-tenant billing with audit requirements
What enterprise reviewers look for when one billing system serves many customers and every action needs a clear trail.
- Migration planning7 min
Migration off Stripe Billing
How to move with proof first: parallel runs, reconciliation, and a cutover boundary that keeps revenue risk contained.
- Retry safety6 min
Idempotency patterns for billing APIs
Retries are expected. The real requirement is making sure a second click or second webhook never becomes a second charge.
- Webhook reliability5 min
Webhook reliability: at-least-once delivery in practice
A webhook path that stays calm when providers retry, reorder, or redeliver the same event more than once.
- Usage rollups6 min
Usage aggregation windows (and handling late events)
How to close billing periods without pretending late-arriving usage does not exist.
Prefer these by email?
Engineering Notes turns the same reliability topics into a short guided sequence for teams that would rather read them in order than browse the archive.