Seller-side cancellation is one of the most important controls in a subscription handover.
The buyer-side subscription should be ready before the seller-side subscription is scheduled to stop collecting future renewals.
Readiness requirement
A destination subscription is considered ready for source cancellation when it is in a collection-safe state such as active or trialing.
If the buyer-side subscription is not ready, seller-side cancellation should not be treated as complete.
Period-end behavior
For many migrations, the seller subscription should be marked to cancel at period end. This prevents the seller account from continuing to renew the customer while avoiding immediate interruption.
If the source subscription already has cancel_at_period_end set, RevBridge mirrors that flag onto the destination subscription. If the source instead has a custom cancel_at scheduled at or beyond its next renewal, RevBridge mirrors that exact timestamp at destination creation. The source-side write-scope verification preserves a scheduled cancel_at by re-writing the same value rather than writing cancel_at_period_end=false, which would clear the seller's pending cancellation.
Reconciliation
After execution, reconcile:
- Source subscription ID.
- Destination subscription ID.
- Destination subscription status.
- Destination billing period.
- Seller cancellation state.
- Audit timestamp.
Avoid overlap
Double billing usually happens when buyer activation and seller cancellation are not coordinated. Review this step carefully.