Skip to end of banner
Go to start of banner

Deactivating Prepaid Subscriptions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

On this page

Deactivating Prepaid Subscriptions


The Deactivate Prepaid Subscription process deactivates effective services of prepaid subscriptions which are eligible for deactivation. Prepaid billing run, executed before the deactivation process, decides which services should be deactivated and marks them accordingly. Services can then be deactivated taking into consideration the day or the day and hour they were activated.
In cases where a candidate subscription for deactivation exists and the subscriber makes a payment to cover for all of the services before the deactivation then the subscription will not be deactivated.

Setting up process to deactivate prepaid subscriptions

Billing > Subscriptions > Deactivate Prepaid Subscriptions

Configuring and executing prepaid subscription deactivation process

The deactivation process is configured once and scheduled to be executed on a recurring basis as needed by the business, based on the defined scheduling settings and throttling settings.

To create and execute the deactivation process

  1. Navigate to the process page and create a new deactivation by clicking on NEW through the Summary or Data Entry page
  2. Provide the values required as explained in the table below and SAVE the process
    Remember to provide scheduling and throttling settings to schedule either on a recurring basis or execute once and separate deactivation in batches
  3. SUBMIT the process through ACTIONS > SUBMIT from the Actions menu.
    A job is created and sent to the scheduler to be executed. If the deactivation process is recurring, once the current deactivation job is done the next one is scheduled

Deactivate Prepaid Subscription process fields

 Mandatory   Configurable 

Main Information

Life Cycle State: The life cycle state of the process which can be 'Effective' or 'Not effective' where only 'Effective' definitions can be submitted for execution.

Deactivation Method: The criterion used to decide which prepaid subscriptions will be deactivated:

  • Day and Hour based Deactivation: If this option is selected, the services will be deactivated considering the day and hour on which they were initially activated.
  • Day only based Deactivation: If this option is selected, the services will be deactivated considering (only) the day on which they were initially activated.

 

Logging Method: Defines the method to be used for logging process run's results. Two options are available:

  • Log Processed Successfully and Processed with Errors: If selected, both entities successfully processed and failed ones will be logged in the Process Run Log.
  • Log Only Processed with Errors: If selected then only entities which failed to be processed will be logged in the Process Run Log.

Input Settings

Subscription Action Type:The subscription action type that will be used to classify each deactivate subscription or stop service action that will be applied

Subscription Sub-Action Type: The subscription sub-action type that will be used to classify each deactivate subscription  or stop service sub-action that will be applied

Criteria

If nothing is specified, all subscription types, frequencies and account classifications are considered

Accounts Receivable CriteriaAccounts Receivable Classification: The accounts receivable classifications that are to be considered for deactivation.
Process Runs
Deactivation Run Information: Displays the Runs that were executed for the specific definition and are available once the process is executed. Each run includes the subscriptions that were processed. In case of an error, the error code and description is displayed.
  • No labels