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
| Status |
|---|
| colour | Red |
|---|
| title | 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 | Note |
|---|
| Status |
|---|
| colour | Green |
|---|
| title | 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
| Status |
|---|
| colour | Red |
|---|
| title | Applicable up to R9 |
|---|
|
| It determines if the stop service step should be enabled by default while creating new Prepaid Billing Runs | Note |
|---|
| Status |
|---|
| colour | Green |
|---|
| title | 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
| Status |
|---|
| colour | Red |
|---|
| title | Applicable up to R9 |
|---|
|
| It determines if the start service step should be enabled by default while creating new Prepaid Billing Runs | Note |
|---|
| Status |
|---|
| colour | Green |
|---|
| title | 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.
This information is available only if the estimation method is set to re-estimate all or re-estimate only Wallet with changes. - Period
- UOT: Measured in months or years
|
|---|
| Status |
|---|
| colour | Red |
|---|
| title | Applicable up to R9 |
|---|
|
- Rating Settings| Status |
|---|
| colour | Green |
|---|
| title | 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: - Do not bill any period in advance
|
|---|
| 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: - Starting from day: The day of the month that should be used in the Bill as of Date, (only) the first time that the Prepaid Billing Run will be executed
- Period after previous Billing Run: The date is calculated based on a period after the previous Prepaid Billing Run, measured in hours, days, weeks, months or years.
|
|---|
| Status |
|---|
| colour | Red |
|---|
| title | 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 |
|---|
| Status |
|---|
| colour | Red |
|---|
| title | 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 |
|---|