Understanding Prepaid Billing

Back to Prepaid Billing Main Page

Table of Contents

What is Prepaid Billing?

Prepaid Billing is a business billing model where customers pay in advance for Services they want to buy or subscribe to, and the billing is handled by the execution of a Prepaid Billing Run.  The financial entity created by Prepaid Billing Runs is Wallet Transactions which are used to debit or credit the customer's Wallet.

This model supports:

  • Post-rated Services: Services are billed after being used for a certain period (usually daily), and funds are directly deducted from the Wallet.
  • Pre-rated Services: Services are billed for an upcoming period defined in the System and funds are directly deducted from the Wallet to cover the whole period. 

In such models, the Billing Run should be executed on a daily basis. 
While Normal Billing Runs can be used for Billing, for Physical Goods and for One Time Services, Prepaid Billing Runs can only be used for Subscription Services and Expenses and can only bill Subscriptions that follow a Prepaid Billing model. 

Prepaid Billing Glossary

TermDescription
Billing Term

Billing Term is the agreement between the customer and the company. It provides information with regards to billing, contract dates and billing periods.   Billing Terms are created every time a Billing Term Scheme is added or updated on the Job or Subscription.

The Billing Term determines whether a Subscription will be handled by Normal or Prepaid Billing.

Billing Term SchemesBilling Term Schemes are used to control the creation or modification of Billing Terms. They provide information on the options available when creating Subscriptions and Jobs, such as the products that can be added or the Price Plans that will be used for their billing. The Schemes also control Billing Engine processes by providing the billing rules and policies that should be applied during Billing Runs.
Prepaid BillingPrepaid Billing is a billing mechanism where customers pay for the Services before they can start using them.

Billable Entities

A set of entities which can be billed through the billing engine, i.e. Jobs and Subscriptions.

Concurrent Usage Based Pricing

Concurrent usage-based pricing is used to bill the customer by applying Price Plan rates based on the number of concurrent usage of the Services or the Physical Goods sold and a rate percentage, which is agreed between the customer and the company providing those services.

For example, in a Hotel Subscription, where the subscribed channels are shown in 100 rooms (Concurrent Usage = 100) and the concurrent percentage is set to 80%, if the rate for one subscription is €15, then the total price for the subscription is calculated as such:

Total = 80% * 100 * 15

Estimation of Wallet Consumption Date

The estimation of the date that the Wallet balance will be consumed, based on the Billing Terms and the usage of the Subscription Services.

Billing Effective DateThe date from which a service starts being billed.
Billable Period Start DateDetermines the start date of the billable period of each Subscription Service. For example, if a Service is effective from the 1st of June but the Billable Start Date is the 1st of August, then the Billing Engine will only start considering the Service from the 1st of August.

Post-Rate

 

Subscription Services are billed after being used for a certain period (usually on a daily basis), and funds are directly deducted from the Wallet.

Pre-Rate

Services are billed for an upcoming period defined in the system and funds are directly deducted from the Wallet to cover the whole period.
Termed ServiceA Subscription Service that is provided to customers and is charged recurrently.
Usage ServiceA Subscription Service that is provided to customers and is charged based on its usage (See UDRs).
One Off Service

A Service that is provided to customers as a one time service and is charged based on the hours spent to complete it.

Cannot be billed via a Prepaid Billing Run

ExpenseA Service that is provided to customers as a one time service and is charged with a fixed amount.
Physical Good
    • Traceable: Good whose physical location is tracked (i.e. company's warehouse, specific customer)
    • Non-Traceable: Good for which only quantity is tracked.

     

    Cannot be billed via Prepaid Billing Run

Price PlansA set of rates which define the amount an Accounts Receivable should be billed, based on the Services or Physical Goods that were sold.
Additive DiscountsDiscounts that are taken into consideration by the Billing Engine and applied on Goods and Services during the billing process.
Buy in AdvanceRequests from customers to pay an amount of money in advance, which is taken into consideration during the billing process.
UDRSubscription Usage Detail Record. UDRs are used to hold raw information describing the use of Usage Subscription Services. For more information view Usage Detail Records.
Rated Billing ItemsInformation generated by the billing engine that represents a set of Services and Physical Goods that were provided to customers along with the applicable rates and information on how those rates were calculated. Rated Billing Items are created by the rating process of the billing engine, either during billing or by manual user intervention.

Prepaid Billing Key Processes and Concepts

Processes / ConceptDescription
Prepaid Billing Run Process

The Prepaid Billing is a mechanism in which customers pay in advance for the Services to which they are subscribed.
The value of the Services consumed is deducted from the customer's Wallet.

The Run is usually performed on a daily basis and is responsible to:

  • Identify the Service usage
  • Rate the used Services
  • Debit the related Wallets based on usage

Additional optional actions:

  • Stop Subscription Services whose Wallet credit has run out
  • Re-Start Services which were stopped due to insufficient Wallet credit which has now been restored
  • Estimate the date on which the Wallet amount will be consumed by the Subscription Services, based on existing usage and Billing Term Schemes.

As from CRM.COM R10 starting and stopping Subscription Services, is no longer handled by the Prepaid Billing Run.

Services are activated by agents, using the Activate Subscription or Start Service Subscription Actions, once Wallets are credited, and deactivated by the dedicated Deactivate Prepaid Subscriptions function.

Unlike in the Normal Billing Run, the user cannot select up to which step the Prepaid Billing Run will be executed.

View Understanding Prepaid Billing Run Execution Steps for a thorough description of the Prepaid Billing Run processes.

Get a Bill Preview of Prepaid Subscriptions

The Prepaid Billing Run is responsible for billing all Subscriptions executed in a batch mode.

Unlike Normal Billing, where the user has the option to bill individual billable entities, Prepaid billable entities cannot be billed on an individual basis. It is possible, however, to get a bill preview.

  • Individual Subscriptions can be previewed via the Subscription Action Bill Subscriber. Refer to Bill Subscriber for a walkthrough of the action.
  • Individual Accounts can be previewed via the action Bill Account, which is accessible via the Accounts Receivable details page.
Rated Billing Items created for Prepaid Billing

Rated Billing Items is information generated by the Billing Engine during the Rating Step of the Prepaid Billing Run, before the Financial Transaction is created. 
Rated Billing Items store information on the Services, Physical Goods and additional billing period information and give you the chance to make amendments and corrections before the Financial Transaction which is a legal document is created,

Visit Rated Billing Items for a thorough description of the processes available for handling Rated Billing Items.

Both Normal and Prepaid Billing Runs use Rated Billing Items.

Billing Prepaid Services in Advance

Subscription Services supported by Prepaid Billing Term Schemes can be billed in two ways:

  • Post-Rate: A prepaid Service which will be rated up to the date that the Prepaid Billing Runs is performed.
  • Pre-Rate: A prepaid Service which will be rated in advance for an upcoming period by Prepaid Billing Runs.

Pre-Rated (billed Services) which are amended (removed or cancelled) will be credited through Credit Wallet Transactions during Prepaid Billing Runs as part of this billing adjustment.

The "Billing Type" available in the Billing Term Schemes Services tab, enables the user to define whether a Service is Pre-Rate or Post-Rate. If the Service is Pre-rate, then the Period to Bill in Advance must also be defined.

Billing of Usage Services
AVAILABLE FROM CRM.COM R10.0.0
 

Billing of Usage Services, such as PPV movies, ordered by subscribers using the 'Add Service Usage' action results in the direct billing of the services
When adding Usage Services to a Subscription using the Add Service Usage action, the UDR is created, and the Usage Service is rated and billed immediately.Consequently, if there are no funds available in the Wallet of the subscriber, then the Service cannot be added to the Subscription.

Refer to Understanding Normal Billing to see how billing of Usage Services is handled for Normal Subscriptions. 

In releases before CRM.COM R10, a setting available in Billing Term Subscription Definitions allows the user to define whether the billing of the UDR is executed directly or during the next Billing Run. This applies to both Normal and Prepaid Subscriptions.

Estimating Consumption Values for Wallets

Wallets are used by Prepaid Billing process to fund Subscriptions. Wallets display the date on which a Prepaid Subscription expires (based on its products and the price plan rates)

Consumption Amount Calculation for long periods

  • The maximum estimated time is one year by default, but can be configured for more through Configuring Prepaid Billing Run Definitions.


The calculations below are performed by the Prepaid Billing Run:

  • Once a BR (Billing Run) is executed, the amount in the Wallet and the remaining product allotted amount are calculated.
  • The cost of the product is calculated per day according to the price on the Price Plan.
    • If more than one products exist, then the sum of all the products is calculated. For example:
      • Product Allotted = Cost per Product per day
      • Wallet = Sum of (Cost per Product per day)
  • Remaining consumption days (Wallet) = Remaining Balance / Sum of (Cost per Product per Day)
  • Remaining consumption days (Product) = Remaining Allotted Amount / Cost per Product per Day
     

Unless the UOT (Unit of Time) of a product in the Price Plans is set to Daily, the calculation of the daily rate will vary according to the number of days in each month, as in the example below:

 January (31 Days)February (28 Days)April (30 days)
Monthly Product Rate313131
Daily Rate Estimation31/31 = 131/28 = 1.1131/30 = 1.03
Multi Currency Billing
AVAILABLE FROM CRM.COM R10.0.0 
Multiple Currencies can exist in the System, but only one is defined as the default. The default Currency determines the currency of all pricing information in CRM.COM Price Plans, Reward Offers, Vouchers, Additive Discounts, Usage Service Catalogs.
An 'alternative currency' can be defined in the Accounts Receivable for account owners who wish their Billing information displayed in their currency of choice.
The Billing Engine will take into consideration the currency defined in the Accounts Receivable of the Subscription or Job that is being billed and will make the necessary conversions.

Prepaid Billing Access & Viewing Controls

Business Network Characteristics define the level of access for each record. i.e., whether it will be available for selection, viewing or editing.

EntityNetwork CharacteristicsDescription
Prepaid Billing RunPrepaid Billing Runs have no access restrictions. They can be viewed and selected by all Users.

Prepaid Billing Related Modules

EntityInteraction of Prepaid Billing with Entity
SubscriptionsSubscriptions with Prepaid Billing Terms are taken into consideration by Prepaid Billing.
Accounts ReceivableThe Accounts Receivable balance is updated according to Wallet changes; the Prepaid Billing may have caused, (if configured as such in the Wallet's Definition).
WalletsPrepaid Billing credits and debits the Wallet related to the Subscription.
VouchersVouchers can be used to top up Wallets.
Rated Billing ItemsRated Billing Items are created by the Prepaid Billing Rating Step.
Price PlansPrepaid Billing obtains the price rates from the Price Plan defined on the Billing Term of the Subscription.
Additive DiscountsAdditive Discounts present in the System are taken into consideration by the Prepaid Billing Run, before creating Rated Billing Items.

 

Prepaid Billing - Business Examples

The following section provides business examples of how the CRM.COM Prepaid Billing module is used.

Configuring Prepaid Billing Run Definition for Daily Invoicing Runs

Company ZX Daily Invoice Run

APPLICABLE UP TO CRM.COM R9.0.0

Business Requirement 

Company ZX has the following requirements regarding the billing if its subscribers:

  • A Billing Run is executed every day and the Bill As Of Date should be one day after the previous Billing Run Day
  • The Billing Run should be executed with 32 threads
  • Subscriptions that have been disconnected should be restarted if their Wallet balance is over 0
  • Subscriptions whose Wallet balance is 0 or less should be disconnected
  • The System should estimate Wallets that have changed since last Billing Run execution
  • Normal Debit Wallet Transaction Type should be created when executing Billing Run 

CRM.COM Solution

 Billing Run Definition 

A Billing Run Definition must be set up in the System with the following configurations:

 Solution
Prepaid Billing Run definitions

Billing Run executed daily with 32 threads

  • Settings - Generic
    • Recurrence Settings: 1 Day
    • Number of Threads: 32
  • Settings - Rating
    • X UOT after Previous Billing Run: 1 day

Subscriptions that have been disconnected should be restarted if their Wallet balance is over 0

  • Settings - Processing
    • Enable Start Service Step by Default
  • Settings - Start Service: 
    • Reconnection Amount Threshold = 0

Subscriptions whose Wallet balance is 0 or less should be disconnected

  • Settings - Processing
    • Enable Stop Service Step by Default
  • Settings - Start Service: 
    • Disconnection Amount Threshold = 0
System should estimate Wallets that have changed since last Billing Run execution
  • Settings - Processing
    • Enable Wallet Consumption Estimation Step: Re-Estimate Wallets with changes
Wallet Definitions
Normal Debit Wallet Transaction Type should be created when executing Billing Run
  • Wallet Causes - Debit Wallets
    • During Prepaid Billing Run
    • From the drop down list: Select Normal Debit

Prepaid Billing Run

Once a Definition is available then:

  • Create a Prepaid Billing Run, using the Criteria and/or Filters to define the Subscriptions that should be taken into consideration
    • Set the Billing Run to 'Recurring.'
  • Execute the Billing Run up to the Formatting Step
    Once the Billing Run is completed, a new  Prepaid Billing Run Job will be created in the Scheduler, scheduled for the next day.

Weekly Pre-rating for Prepaid Services

Company ZX Weekly Invoice Run

Business Requirement 

Company ZX provides a Prepaid Plan to its subscribers. The Services to be offered are billed directly and subtracted from the subscribers Wallet on a weekly basis.

  • Subscribers that cancel their Subscriptions or change to another Service that was already rated are credited and re-billed if necessary.

CRM.COM Solution

Configuration

The following modules should be configured with the following specifications:

 Solution
Prepaid Billing Term Scheme
Directly billed and subtracted from the subscribers Wallet on a weekly basis

Allowed Services Billing Type: Pre-rated

Period Billed In Advance: 1 week

Prepaid Billing Run definitions

Billing Run executed daily with 32 threads

  • Settings - Generic
    • Recurrence Settings: 1 Day
    • Number of Threads: 32
  • Settings - Rating
    • X UOT after Previous Billing Run: 1 day
System should estimate Wallets that have changed since last Billing Run execution
  • Settings - Processing
    • Enable Wallet Consumption Estimation Step: Re-Estimate Wallets with changes
Wallet Definitions
Normal Debit Wallet Transaction Type should be created when executing Billing Run
  • Wallet Causes - Debit Wallets
    • During Prepaid Billing Run
    • From the drop down list: Select Normal Debit

Subscribers that cancel their Subscriptions or change to another Service that was already rated are credited and re-billed if necessary.

  • Wallet Causes - Credit Wallets
    • During Prepaid Billing Run
    • From the drop down list: Select Normal Credit
 
  • Wallet Threshold
    • 0

The Billing Run can be configured to be executed on a daily or weekly basis. See below an example of how the Billing will function in each of the two configurations:

Billing Run executed on a daily basis

In this scenario, assume that the Billing Run is executed every day starting from 01.01.2016.

SubscriberEffective DateWallet Amount (Prepaid)Service Charge (per day)PreRate PeriodExecuting Billing Run Daily
     01.01.201602.01.201603.01.201604.01.201605.01.201606.01.201607.01.201608.01.2016
Subscriber A01.01.2016€7.001/per day1 week

Pre-Rated Amount = 7

Wallet Amount = 0

Pre - Rated to : 08.01.2016

Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00
Subscriber B02.01.2016€7.001/per day1 weekN/A

Pre-Rated Amount = 7

Wallet Amount = €0.00

Pre - Rated to : 09.01.2016

Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00Wallet Amount = €0.00

 

Billing Run executed on a weekly basis

In this scenario, assume that the Billing Run is executed every week right starting from 01.01.2016.

SubscriberEffective DateWallet Amount (Prepaid)Service Charge (per day)PreRate PeriodExecuting Billing Run Weekly starting on the 03.01.2016
     01.01.201602.01.201603.01.201604.01.201605.01.201606.01.201607.01.201608.01.2016
Subscriber A01.01.2016€7.001/per day1 week

Wallet Amount = €7.00

Wallet Amount = €7.00

Pre-Rated Amount = €7.00

Wallet Amount = €0,00

Pre - Rated to : 08.01.2016

Wallet Amount = €0,00Wallet Amount = €0,00Wallet Amount = €0,00Wallet Amount = €0,00Wallet Amount = €0,00
Subscriber B02.01.2016€7.001/per day1 weekN/A

Wallet Amount = €7.00

Pre-Rated Amount = €7.00

Wallet Amount = €0,00

Pre - Rated to : 09.01.2016

Wallet Amount = €0,00Wallet Amount = €0,00Wallet Amount = €0,00Wallet Amount = €0,00Wallet Amount = €0,00