Overview

Prepaid subscriptions are funded directly from the wallets of subscribers. Subscription services can be pre-rated (billed for an upcoming predetermined period) or post-rated (billed after being used).  Billing takes place either when the service is activated or a prepaid billing run is executed. There must be sufficient funds in the wallet to cover the billing period in order for services to be activated. If there are insufficient funds during the billing run to cover billed services, the services become candidates for deactivation.

Setting Up Prepaid Billing Runs

In order for the prepaid billing run to be executed the necessary configurations in the Prepaid Billing Settings tab of the billing definition must be made.

Managing Prepaid Billing Runs

Once the billing settings are defined, the prepaid billing run is executed by a system background process (without the need for user intervention). The results of the billing run can be viewed from a dedicated page or through the Batch Process Admin Board (from where you can manage their schedule and view logs of all executed runs).

Prepaid Billing Run

The table describes the sections of the Prepaid Billing Run Data Entry page and explains how the fields on the page are used.

 Mandatory   Configurable

Batch Process Admin Board

Use the board to stop the prepaid billing run from being executed or to view its logs.

1. Navigate to the Board
2. Go to Recurring System Process
3. Find the prepaid billing run.
   1. Click on View Logs
      or
   2. Stop the run.

Executing a prepaid billing run

The steps of a run include:

• Identifying the items to be billed
• Rating the items 
• Debiting (or crediting) the subscription wallet.

Identification process 

Locates unrated billable items that, according to billing run conditions, are ready to be charged or credited. The following entities are considered:

• Subscription Usage Detail Records that should be charged or credited and have a 'Posted' life cycle state.
• Post-rated services that:
  • Should be charged or credited (depending on the value of the billing directive)
  • Are not yet rated 
  • Have a billing effective date up to and including the bill as of date.
• Pre-rated services that have not been rated before or whose latest 'rated up to' date is up to and including the billing run's performed date.

Terminated accounts are excluded from billing.

Rating 

Creates rated billing items for services using the rate from the price plan and information from the following entities:

• Usage services 
  Usage Detail Records (UDRs) with a 'Pending' (not yet processed) rating state are considered for billing.  The UDR billing directive specifies whether a debit or credit rated billing item should be created. The period to be billed is indicated by the 'Started on' and 'Ended on' dates. 
  
• Termed services
  The source of information for rating termed services is their life cycle states.  Each life cycle state represents one period.  The 'Started on' and 'Ended on' dates indicate the period.  Life cycle states in a 'Pending' rating state are considered for billing.   The billing directive of each life cycle state specifies whether a debit or credit rated billing item should be created. 
  • For post-rated services, a rated billing item is created covering the period from the last Rated Up To Date until the billing run's Performed Date.
  • For pre-rated services, a rated billing item is created covering the period billed in advance (as defined in the billing term scheme) up to the last 'Rated Up To Date'. 
• Expenses 
  The billing directive for the life cycle state of the expense specifies whether a debit or credit rated billing item should be created.
• Additive Discounts
  Additional discounts that should be applied to the subscription are taken into consideration after discounts that may have been applied through the price plans.

Rated billing items are created as long as they don't result in the wallet's balance falling below the threshold (established in the wallet definition). 
If the calculated balance of the wallet remains over the threshold:

• The wallet is debited
• The service is not rated for the upcoming period
• The prepaid state is set to 'Valid' and the service is not considered for deactivation.

If the calculated balance of the wallet drops below the threshold:

• The wallet is not debited
• The service is not rated for the upcoming period
• The prepaid state is set to 'Invalid' and the service is considered for deactivation.

If a service is coming out of a Grace Period, customers are also billed for the period spent in grace, unless the 'Decrease the prepaid pre-rated period by the total number of days in grace periods' setting is selected in the billing definition.

Wallet Debiting

Uses the rated billing items resulting from the rating step and previously unprocessed rated billing items, to generate debit or credit wallet transactions.

Wallet Consumption Estimations 

Calculates the date on which (or the number of days until) wallet funds (or the funds allotted for a specific product) will run out, based on the billing terms and use of subscription services.  The estimations must be enabled through the prepaid billing run.  

The maximum estimated time (one year by default) can be configured through the 'Prepaid Billing Run Settings' in the billing definition.  

Wallets

• Estimated consumption days
• Estimated consumption date

Wallet Product Consumption

• Estimated consumption days
• Estimated consumption date
• Latest date of estimation

Glossary