Assign one authoritative billing record to each recurring hosting service and document which processes may invoice, collect payment and renew the provider resource. Clear ownership prevents overlapping automation after imports, migrations or manual workarounds.
01 Map the recurring workflow
- Identify the physical or provider resource and its customer-facing service record. Record the billing platform, service ID, customer, billing cycle and next relevant dates.
- List every process that can generate a charge: native service billing, a manual recurring invoice template, another billing installation or an external subscription.
- List collection mechanisms separately, such as automatic card capture and a gateway-managed recurring agreement. Confirm which one should settle the invoice.
- Record what triggers the provider action. Domain invoice payment, registrar renewal, hosting suspension and provider subscription renewal are related events but may have different owners.
- Resolve duplicate or obsolete schedules through their supported workflows. Review already-created invoices and provider requests before changing future automation.
- During a migration, define a clear handover point. Disable the source installation's live automation before the destination becomes the billing owner, and reconcile work already submitted.
- Test one complete cycle and compare the invoice, transaction and provider result. Keep an exception queue for mismatches rather than adding another recurring job as a workaround.
02 Watch for overlapping mechanisms
HostBill supports manual recurring invoice templates as well as normal account billing. Creating both for the same charge can produce separate invoices. In WHMCS, an external payment subscription can continue independently of a manual change to a service record; inspect the gateway agreement when changing the collection arrangement.
For domain renewals, compare the billing renewal setting with registrar-side renewal behaviour. A paid customer invoice is not the same evidence as an updated registry expiry date.
Common questions
Can we leave both old and new billing cron jobs running during migration?
Only a deliberately designed split with non-overlapping ownership could justify that arrangement. A normal full migration needs one active owner so both copies do not invoice, charge or provision the same services.
Does stopping a recurring template cancel invoices already generated?
Review existing invoices separately. Changing a future schedule does not necessarily reverse earlier financial documents or provider actions.