Destroying Canceled Subscriptions

A subscription is destroyed in CloudBlue Commerce means that the subscription cannot be restored and the service can no longer be used:

  • A request is sent to the service vendor's system to destroy the service on the vendor's side, for example: terminate a VM, delete a tenant, unassign an IP address and so on. The request is processed on the vendor's side according to the vendor's policies.
  • In Billing, the subscription status becomes Terminated and the service status becomes Removed. The subscription billing data is preserved in the Billing database for audit purposes.
  • In Operations, immediately after a subscription is destroyed, it is assigned the Terminated status. Then, the subscription management data is deleted from the Operations database according to the retention policy.

Using the settings below, you can define subscription cancellation and termination policy in the following ways:

  • No destruction policy: Retain canceled subscriptions so that they can be restored at any time after cancellation. Such subscriptions can also be terminated manually at any time.
  • Automatic destruction policy: Destroy canceled subscriptions automatically.

To destroy a canceled subscription manually:

  1. In the Provider Control Panel, go to Billing > Subscriptions. Click the necessary canceled subscription with Service Status = Stopped.

  2. Click Destroy. The subscription becomes terminated when the service status changes to Removed.

Cancellation and Destruction Settings

Cancellation and Termination Scenarios

Scenario 1. Cancel a Subscription and Terminate the Service Immediately

If you want a subscription to be canceled without delay and then the service to be immediately destroyed, configure the settings in the following way:

Service Type: Various Classic Services Usage-based Services with Usage Rated on the Vendor's Side
Cancellation Scenario:

Scenario A:

  1. A customer cancels a subscription; the cancellation order is provisioned immediately.
  2. The service is destroyed immediately.

Scenario B:

  1. A customer cancels a subscription; the cancellation order is provisioned immediately.
  2. The service is destroyed; the cancellation date is recorded.
  3. The system invoices the customer for the usage data collected before cancellation.
  4. Late usage data is invoiced later separately.
General Configuration:

The Service Plan is based on:
Important Properties:
Yes
0 days (or not set)
N/A*
N/A*

*These settings do not affect the result and can have any valid values.

Scenario 2. Cancel a Usage-based Subscription, Process the Usage, and then Terminate the Service

For usage-based services, if you want to process usage data after cancellation and issue an invoice first, and only then to destroy the service, configure the settings in the following way:

Service Type: Classic Usage-based Services Usage-based Services with Usage Rated on the Vendor's Side
Cancellation Scenario:

Scenario A:

  1. A customer cancels a subscription; the cancellation order is delayed for X days while usage data is collected and processed; the subscription service is stopped.
  2. After X days, the cancellation order is provisioned including the usage data. After that, the service is destroyed.

Scenario B:

  1. A customer cancels a subscription; the cancellation order is delayed for X days.
  2. After X days, the cancellation order is provisioned and the service is destroyed.
  3. Independently, Vendor-rated Data Manager receives from the vendor and processes the rated usage data.
  4. The customer is billed for the remaining usage.

Note: This scenario is not recommended because delaying cancellation is redundant: usage data is processed by Vendor-rated Data Manager independently, an active subscription is not required.
General Configuration:
Important Properties:
Yes
X days
N/A*
N/A*

*These settings do not affect the result and can have any valid values.

Scenario 3. Cancel a Subscription and, After a Suspension Period, Terminate the Service

For various service types, including usage-based services, if you want to process usage data after cancellation and issue an invoice first, and only then to destroy the service, configure the settings in the following way:

Service Type: Classic Services and Usage-based Services with Real-Time Usage Collection Usage-based Services with Usage Rated on the Vendor's Side
Cancellation Scenario:

Scenario A*:

  1. A customer cancels a subscription; the cancellation order is processed immediately.
  2. The service is suspended for Y days; no usage is collected during this period.

  3. After Y days, the subscription is destroyed (by the Daily Billing Process without an order).

Scenario B:

  1. A customer cancels a subscription; the cancellation order is processed immediately.
  2. The service is suspended for Y days; during Y days, vendor-rated usage data is collected and sent for invoicing.
  3. After Y days, the subscription is destroyed (by the Daily Billing Process without an order); the cancellation date is recorded.
  4. Late vendor-rated usage data is continued to be collected and sent for invoicing.
General Configuration:
Important Properties:
No
0 days (or not set)
Y days
Yes

* This scenario does not apply to usage-based services with delayed usage collection.

Scenario 4. Cancel a Subscription and, After a Suspension Period, Give Customers a Chance to Restore It

For both non-PAYG and usage-based services, if you want to give customers a chance to restore canceled subscriptions or, alternatively, to terminate them manually at any time after cancellation, configure the settings in the following way:

Service Type: Non-PAYG Services Usage-based Services with Usage Rated on the Vendor's Side
Cancellation Scenario:

Scenario A:

  1. A customer cancels a subscription; the cancellation order is processed immediately.
  2. The service is suspended for Y days.

  3. After Y days, the subscription remains inactive and you can manually destroy or restore it.

Scenario B:

  1. A customer cancels a subscription; the cancellation order is processed immediately.
  2. The service is suspended for Y days; during Y days, vendor-rated usage data is collected and sent for invoicing.
  3. After Y days, the subscription remains inactive and you can manually destroy or restore it.
  4. Late vendor-rated usage data is continued to be collected and sent for invoicing. If you terminate the subscription manually, vendor-rated usage data is no longer collected.
General Configuration:
Important Properties:
No
0 days (or not set)
Y days
No

Scenario 5. Cancel a Classic PAYG Subscription, Postpone Cancellation to Process the Usage and then, After a Suspension Period, Terminate the Service

For classic usage-based services, if you want to postpone cancellation to process the usage and then, after a limited suspension period after the cancellation, terminate the service automatically, configure the settings in the following way:

Service Type: Classic PAYG Services Usage-based Services with Usage Rated on the Vendor's Side
Cancellation Scenario:

Scenario A:

  1. A customer cancels a subscription; the service is suspended for X days but the subscription is not canceled; the cancellation order processing is postponed for X days; during X days, usage data is collected and processed.
  2. After X days, the cancellation order is processed and the customer is billed for the processed usage. For additional Y days, the subscription remains suspended, the usage data is continued to be collected and processed.
  3. After Y days, the subscription is terminated (by the Daily Billing Process without an order). Usage data is no longer collected and processed.

Scenario B:

The configuration below is irrelevant for this service type.
General Configuration:
Important Properties:
No
X days
Y days
Yes

Scenario 6. Cancel a Classic PAYG Subscription, Postpone Cancellation to Process the Usage and Then Freeze the Subscription Until It Is Manually Restored or Terminated

For classic usage-based services, if you want to postpone cancellation to process the usage and then suspend the subscription indefinitely until it is manually restored or destroyed, configure the settings in the following way:

Service Type: Classic PAYG Services Usage-based Services with Usage Rated on the Vendor's Side
Cancellation Scenario:

Scenario A:

  1. A customer cancels a subscription; the service is suspended for X days but the subscription is not canceled; the cancellation order processing is postponed for X days; during X days, usage data is collected and processed.
  2. After X days, the cancellation order is processed and the customer is billed for the processed usage.
  3. After the X days, the subscription remains inactive until it is restored or manually terminated. Usage data is no longer collected and processed.

Scenario B:

The configuration below is irrelevant for this service type.
General Configuration:
Important Properties:
No
X days
Y days*
No

*These settings do not affect the result and can have any valid values.

© 2021 Ingram Micro, Inc. All Rights Reserved. Privacy Policy, Terms of Use and Legal