Table of Contents
Navigating to Prepaid Billing Run Definitions
CONFIGURATION > BILLING APPLICATION > BILLING > SET UP PREPAID BILLING RUN DEFINITIONS
What are Prepaid Billing Run Definitions?
Prepaid Billing Run definitions is a set of business rules used to control the behaviour of Prepaid Billing Run throughout their whole life cycle. Prepaid Billing Run definitions are used to define several business rules that need to be applied during the Billing Run, but also default values, which are used while running Prepaid Billing Runs. The life cycle state of the definition must be set to active for the rules defined to be applied, and only one definition can be active at a time
Navigate to Prepaid Billing Run Definitions and explore existing records via the Summary page. Click on the link (name or number) of the record of your interest to enter the Data Entry page and have a better look of the available information. Use the Actions Menu to create a new (NEW) Prepaid Billing Run Definitions, modify (EDIT) or delete (DELETE) an existing one. Use the (BACK) link to go back to the summary page and (CANCEL) to cancel any unwanted changes made to the Prepaid Billing Run Definitions.
Check out the attributes table below for a thorough explanation of the information kept for Prepaid Billing Run Definitions and the Validations&Restrictions table to find out validations and restrictions applicable when working with Prepaid Billing Run Definitions.
Validations & Restrictions
| Action | Validations | Restrictions |
|---|---|---|
| General |
|
|
| Create |
|
|
| Edit |
|
|
| Delete |
|
|
Prepaid Billing Run Definition attributes
Fields and sections that have the following label: APPLICABLE UP TO R9 are deprecated from release R10 and forward
Name | Description |
|---|---|
| Name* | The name of the Prepaid Billing Run definition |
| Alternative code* | The alternative code of the Prepaid Billing Run definition |
| State | The state of the Prepaid Billing Run definition which can be active or inactive |
| Description | A description of the prepaid Billing Run definition |
| Generic Settings | |
| Number of threads* | The number of threads that should be used by the prepaid Billing Run process. The maximum number of threads specified in General Settings cannot be exceeded. |
| Recurrence settings APPLICABLE UP TO R9 | The recurrence settings which are applied on all Billing Runs which are classified as recurring, measured in hours, days, weeks, months or years AVAILABLE FROM CRM.COM R10.0.0 The recurrence setting is removed. The system is applying the default recurrence which is 1 day |
| Processing Settings | |
| Enable Stop Service Step by Default APPLICABLE UP TO R9 | It determines if the stop service step should be enabled by default while creating new Prepaid Billing Runs AVAILABLE FROM CRM.COM R10.0.0 The Enable Stop Service Step by Default is removed. The Prepaid Billing Run no longer applies stop services actions |
| Enable Start Service Step by Default APPLICABLE UP TO R9 | It determines if the start service step should be enabled by default while creating new Prepaid Billing Runs AVAILABLE FROM CRM.COM R10.0.0 The Enable Start Service Step by Default is removed. The Prepaid Billing Run no longer applies start services actions |
| Enable Wallet Consumption Estimation Step by Default | It determines if the wallet consumption estimation step should be enabled by default while creating new Prepaid Billing Runs |
Maximum Estimation Period
| This information defines the period to look ahead while the prepaid billing process is estimating the estimated consumption date for a specific subscription service.
|
APPLICABLE UP TO R9 - Rating Settings AVAILABLE FROM CRM.COM R10.0.0 -The whole section is removed. The date that the Prepaid Billing Run is performed will automatically be used as the bill as of date | |
Period to bill in advance* | Defines the period that should be billed in advance, which is applicable only on pre-billed services. The supported options are the following:
|
| Bill as of day settings | Rules on how to calculate the default bill as of day which is used by all Prepaid Billing Runs. Prepaid Billing Runs will default to this date unless a different date is specified. The settings consist of the following:
|
APPLICABLE UP TO R9 Start Service Settings Available only if enabled in Processing Settings | |
| Subscription Action Type | The subscription action type that will be used to start the services that should be started. Mandatory on Conditions: This is applicable and mandatory if subscription action types related to the start service behaviour code exists |
| Subscription Sub-Action Type | The subscription sub action type that will be used to start the services that should be started. Mandatory on Conditions: This is applicable and mandatory if subscription action types related to the start service behaviour code exists |
| Amount threshold* | The minimum amount (exclusive) that the wallet balance for each specific service should be, for the service to be started. For example, if set to 0 and the available amount for a not effective service is 1, then the service will be started. If the available amount for a not effective service is 0, then the service will not be started |
APPLICABLE UP TO R9 Stop Service Settings Available only if enabled in Processing Settings | |
| Subscription Action Type | The subscription action type that will be used to stop the services that should be stopped. Mandatory on Conditions: This is applicable and mandatory if subscription action types related to the stop service behaviour code exists |
| Subscription Sub-Action Type | The subscription sub action type that will be used to stop the services that should be stopped. Mandatory on Conditions: This is applicable and mandatory if subscription action types related to the stop service behaviour code exists |
| Amount threshold* | The maximum amount (inclusive) that the wallet balance for each specific service should be, for the service to be stopped. For example, if set to 0 and the available amount for a not effective service is 0, then the service will be stopped. If the available amount for a not effective service is 1, then the service will not be stopped |
Visit Understanding Prepaid Billing for business examples related to Prepaid Billing Run definition