Skip to end of banner
Go to start of banner

Prepaid Billing & Subscriptions Getting Started

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 »

A Subscription is a collection of Services which are provided to customers and billed on a recurring, usage or One-Time basis. The Subscriber is the customer who owns the account associated with the Subscription and receives its Services.

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.

What Comes First

Sub-moduleTypeClassificationNavigationDig In
Billing Term SchemesConfigurationCONFIGURATIONBILLING APPLICATIONBILLINGSET UP BILLING TERM SCHEMESConfiguring Prepaid Billing Term Schemes for Subscriptions
Subscription TypesConfigurationCONFIGURATIONBILLING APPLICATIONSUBSCRIPTIONSSET UP TYPES/wiki/spaces/WIP/pages/10008626
Subscription DefinitionsConfigurationCONFIGURATIONBILLING APPLICATIONSUBSCRIPTIONSSET UP BUSINESS DEFINITIONS/wiki/spaces/WIP/pages/10008628
Billing Term DefinitionsConfigurationCONFIGURATIONBILLING APPLICATIONBILLINGSET UP BILLING TERM DEFINITIONS/wiki/spaces/WIP/pages/10008621
Normal Billing Run DefinitionsConfigurationCONFIGURATIONBILLING APPLICATIONBILLINGSET UP PREPAID BILLING RUN DEFINITIONSConfiguring Prepaid Billing Run Definitions
Subscription Action and Sub Action TypesConfigurationCONFIGURATIONBILLING APPLICATIONSUBSCRIPTIONSSET UP SUBSCRIPTION ACTION TYPES/wiki/spaces/WIP/pages/10008627 

Step 1: Setting up Billing Term Schemes

First you must configure the Billing Term Schemes.

Billing 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.
Once created, Billing Term Schemes are added on Subscription Types.

Step 2: Setting up Subscription Types

A Subscription Type defines the company's commercial policies which are applied on Subscriptions of that type, such as what Services and what Physical Goods can be added on each Subscription Type, which Billing Term Schemes will be made available for each Subscription Type as well as the company's departments (Organisational Units) can create Subscriptions of the specific Type.

Step 3: Setting up Subscription Definition

An active Subscription definition must then be configured.

A Subscription Definition is a set of business rules and conditions which are used in order to create and maintain Subscriptions throughout their Life Cycle. For example, through the Subscription Definitions you can define the maximum number of Subscriptions you can have per account, or the maximum number of Main Services and Physical products that can be added on a Subscription. 
Subscription Definitions provide a number of restrictions and controls and can be used to define product dependencies. For example, a rule can be set where additional channels cannot be added unless one of the Main channels is added first.

Step 4: Setting up Billing Term Definitions

Billing Term Definitions come next. They are differentiated based on Classification, which can be Subscription or Jobs.

Billing Term is the agreement/contract 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 and it determines whether a Subscription will be handled by Normal or Prepaid Billing. Billing Term behaviour is governed by Billing Term Definition rules.

Billing Term Definitions are used to define business rules used to validate several processes applied to Subscription or Jobs, via their related Billing Term.. For example, you can define rules where you will not allow Regret after a number of days, or define cancellation penalties based on a particular service and remaining binding period. Rules are used across all Billing Terms, regardless of their Schemes however, for each rule, you can define whether it is only applicable to particular schemes.

Step 5: Setting up Prepaid Billing Run Definitions

Time for 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.


Prepaid Billing Run definitions is a set of business rules used to control the behaviour of Prepaid Billing Runs. Prepaid Billing Run Definition is used in order to define several business rules that are applied during the Billing Run, but also default values, which are used while executing the Billing Runs.

Step 6: Setting Up Subscription Action and Sub Action Types 

Configure the following modules for additional functionality and categorisation. You can skip configuration of the modules if not required by your business model

  • Subscription Action Type:
    The modifications performed on a Subscription when a Subscription Action is executed depend on the Subscription Action's Type, while the Subscription Sub-Action Type is used to apply a business meaning.

    • There are 2 main characteristics that all Subscription actions have and these are configured in the Subscription Action Type and Subscription SUb Action Type Level:

 

There is no need to configure Subscription Action Types as you can find all available Subscription Action Types and Sub Types in the Subscription's page.
Configure new Subscription Action Types and Sub-Types only if you want to categorize actions executed.

 


 

Once the Billing Run is executed Bills are created. Bill Sending Run Definitions are used to determine the business rules that are used to identify Bills to be sent through Email, SMS or an external System. Configure the Bill Sending Runs if you would like to directly handle Bill sending from CRM.COM

Do it Yourself!!

Let's see how you can quickly set up the System to start using Conditional Access module for your Subscriptions business

Create the following Subscription Types

NameAllowed AttributesAllowed Organisational Units  
 Billing Term SchemesServicesPhysical GoodsProvisioning Distributors   
NormalNormal
  • Pay Per View - Optional
  • Video On Demand - Optional
  • Basic Plan - Mandatory
  • Decoders
  • Smartcards
  • All
  • Marketing Community
  


Create the following Subscription Definition

Subscription RulesService RulesInstalled Item Rules
RestrictionsRestrictionsDependenciesRestrictions Per DistributorDependencies Per DistributorTiersRestrictionsDependenciesRestrictions Per DistributorDependencies Per Distributor
  • Normal 
  • Max subscriptions: 10
  • Scope: Subscriptions
  • Number of Mandatory Services: 1 -3
  • Number of Optional Services: 0 -5
    
  • Type: Smartcard & Decoder
  • Number of Installed Items: 0 -3
   

 


Create the following Prepaid Billing Run Definition

Company ZX bills has the following requirements regarding its subscribers billing

  • Billing Run executed every day and the Bill as Of date should be one day after the previous Billing Runs Day

  • Blling Run should be executed with 32 threads

  • Subscription that have been disconnected should be restarted if there wallet balance is over 0

  • Subscriptions whose wallet balance is 0 or less should be disconnected

  • System should estimate wallets that have been changed since last Billing Run execution

  • Normal Debit Wallet Transaction type should be created when executing Billing Run 





CRM.COM Solution

A Billing Run definition will be set up in the System with the following configurations

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

Subscription that have been disconnected should be restarted if there 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 been 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

 

 

  • No labels