What does this section cover?

What is Binding & Cancel Date Extension

A subscription's Binding End Date denotes the date for which the contract of a customer ends. 
For example, a Pay TV company may offer a package with 10% discount but with the condition that you will be their subscriber for at least 12 months. This means that you are obliged to remain as a subscriber for 12 months. i.e the Binding End Date will be 12 months from your Contract's Start Date

A subscription's Allowed Cancel Date denotes the earliest date for which a subscriber can cancel his/her subscription with no penalties. While in most cases Binding End Date and Allowed Cancel Date are the same, you might want to differentiate between them, keeping the Binding End Date static while updating the Allowed Cancel Date.

Subscription Binding End Date and Allowed Cancel Date can be extended based on the actions which are applied on the subscription. On extending those dates the initial information and the causes of each extensions are kept and can be used for troubleshooting.

The dates will never be extended automatically (by default) but its up to the user to make the required configurations. The only default behavior, is the extension of the allowed cancel date, which is always extended up to the binding end date, if the binding end date is set after the existing allowed cancel date. 

How does Binding End and Cancellation Date extension  work?

As explained above the only default system behavior for extending dates is that both dates are extended together.

However, CRM.COM offers you complete control over what will make each of the dates to be extended, and they need to be set in one of the configuration modules. The allowed configuration is primarily based on Subscription Actions that according to Business rules of each company will or won't extend one or both of the dates. 

The allowed configurations for extending the binding end date are the following

• Extent based on days in resting, as specified in Extend Binding End Date causes
• Extent based on not effective days, as specified in Extend Binding End Date causes
• Extent based on grace periods, as specified in Extend Binding End Date causes
• Extend based on new services that were added as effective, as specified in Services Extending Binding

The possible causes that might extend the allowed cancel date are the following

• Extent based on days in resting, as specified in Extend Allowed Cancel Date causes
• Extent based on not effective days, as specified in Extend Allowed Cancel Date causes
• Extent based on grace periods, as specified in Extend Allowed Cancel Date causes
• Extend based on new services that were added as effective, as specified in Services Extending Binding

According to the set configurations, when any of those actions are executed in the system then the Binding End Date and the Allowed Cancel Date will be extended accordingly, however the initial dates will be kept.

Configuration can be done at Configuring Billing Term Schemes, in the Billing Information section and the Service Extend Binding section.