...
Setting Up Prepaid Billing Runs
Before executing prepaid billing runs, perform the necessary 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.
| Info |
|---|
Configuration > Billing Application > Billing > Set Up Billing Definition > Prepaid Billing Settings |
...
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
| Info |
|---|
Billing > Billing > Perform Prepaid Billing Runs |
...
The table describes the sections of the Prepaid Billing Run Data Entry page and explains how the fields in on the page are used.
Mandatory Configurable
Main Information | |||||
|---|---|---|---|---|---|
Bill As Of Date: A read-only field that defaults to the The date on which the prepaid billing run is executed. Subscriptions with services 'Rated up to' and including the 'Bill as of' date are considered for billing. The Life Cycle State reflects the progress of the billing run: Draft (not yet executed)
Scheduled Date: A read-only field displaying Displays the next date on which the run will be executed. Enable Wallet Consumption Estimation Step: Can be pre-selected as configured Configured in the prepaid billing settings section of the billing definition.
| |||||
Criteria | |||||
Can be used to identify groups for billing (e
| Filters|||||
| Can be applied to bill selected entities (e.g., a group representing a specific geographical area). Filtering can be applied on accounts receivables, subscriptions, and groups. | |||||
| Scheduling Settings | |||||
| Recurring: Determines whether the billing run takes place once or repeatedly. The recurrence is read-only and set to one day. | |||||
Results (Information on bills created by billing run) | |||||
Include Includes the total Number of Generated Wallet Transactions, the billing run Start and End Date and the Results Per Step (a summary table listing the steps of the billing run, the wallet transactions that were created and the included entities). | |||||
| Exceptions | |||||
Display accounts excluded from billing due to errors. | |||||
Creating and executing a prepaid billing run
Under Billing > Perform Prepaid Billing Run, specify the criteria that match the run you are interested in, or use NEW from the Actions menu to create a new run. Provide the mandatory information and SAVE the run.
A billing run must be submitted when it is created. A run's progress is reflected in its life cycle state.
- Select Actions > Execute
- Execute immediately or schedule the run.
...
Batch Process Admin Board
| Info |
|---|
Foundation > Platform > Manage Admin Settings > Batch Processes Admin Board |
Use the board to stop the prepaid billing run from being executed or to view its logs.
- Navigate to the Board
- Go to Recurring System Process
- Find the prepaid billing run.
- Click on View Logs
or - Stop the run.
- Click on View Logs
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 which that have not been rated before or whose latest 'rated up to' date is up to and including the billing run's performed date.
...