Implementation
Choosing a Billing Cutover Date Without Splitting the Wrong Period
By the Orvlin team · · 2 min read
Billing system cutover planning: what to decide
A new system starts on the first day of the month, but old jobs continue reporting to the previous pipeline. The calendar boundary looks neat while ownership of real activity remains unclear. Cutover requires rules, not just a launch date.
Specify event routing, historic replay and invoice responsibility separately. Account anniversary periods may span the proposed cutover. Define how in-flight tasks and adjustments are handled so neither system sends an unintended duplicate invoice.
An illustrative case
An account’s period runs from October 15 to November 15. A November 1 platform switch can either preserve one system’s invoice ownership or deliberately split usage under a tested policy. Assuming calendar-month boundaries would miss this account.
The important caveat
A rollback plan needs the same clarity. If the new system has already issued documents or consumed credits, returning to the old system requires reconciled state—not merely changing a traffic flag.
Review these decisions
- Identify billing schedules and in-flight work.
- Assign event and invoice ownership.
- Define late-arrival handling.
- Rehearse rollback with reconciled balances and documents.
Frequently asked questions
- Is month-start always the safest cutover?
- No. It helps calendar-month accounts but may split anniversary contracts. Choose according to actual schedules and operational constraints.