Excerpt | ||
---|---|---|
| ||
Learn how you can configure and execute Prepaid Billing Run Run |
What does this section cover?
Table of Contents | ||
---|---|---|
|
What is Prepaid Billing Run ?
In CRM.COM Software the way to bill the customers in a batch mode is done via Billing Runs referred to as Prepaid Billing Runs.
Prepaid billing run is a billing mechanism which is used in cases where customers pay in advance and then they can start using the services that they subscribed to, by deducting the used amount from the paid amount, using the wallets module.
Prepaid billing 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 that usage
Optionally the prepaid billing run can:
- Stop subscription services which are left with no wallet credit
- Start services which were stopped and are now having enough wallet credit
- Estimate the date that the wallet amount will be consumed by the subscription services, based on their existing usage and billing term schemes.
No bills or financial transactions are generated by the prepaid billing run and unlike Normal Billing Runs, Prepaid billing run is only applicable on Subscriptions.Visit Interpreting Prepaid Billing Run Execution Steps for a complete description of all the available processes within Prepaid Billing Runs.
In order for the Billing Run to be created, a Prepaid Billing Run Definition needs to be set up in the system. Once the definition is set up, a new Prepaid Billing Run can be created and executed.
Anchor | ||||
---|---|---|---|---|
|
Creating, Editing & Deleting Validations & Restrictions
Action | Validations | Restrictions |
---|---|---|
Create |
| |
Edit |
|
|
Delete |
|
|
Prepaid Billing Run attributes
Name | Description |
---|---|
Number | An auto generated number which uniquely identified each prepaid billing run |
Type | Defines if the prepaid billing run was performed on a batch or individual mode. The supported values are BATCH and INDIVIDUAL |
Life cycle state | The life cycle state of the prepaid billing run. The supported states are the following:
|
Bill as of date* | Defines the date that prepaid billing run should be performed as. The bill as of date takes a default value based on the bill as of day setting specified in prepaid billing run definitions, although it be modified by users |
Enable Stop Service Step | It determines if the stop service step should be performed or not. It is automatically set on creating the prepaid billing run, based on the processing settings specified on the active prepaid billing run definitions. |
Enable Start Service Step | It determines if the start service step should be performed or not. It is automatically set on creating the prepaid billing run, based on the processing settings specified on the active prepaid billing run definitions. |
Enable Wallet Consumption Estimation Step | It determines if the wallet consumption estimation step should be performed or not. It is automatically set on creating the prepaid billing run, based on the processing settings specified on the active prepaid billing run definitions. |
CRITERIA | |
Consider billing term schemes* | The billing term schemes that should be considered by the prepaid billing run process. Only billable entities having billing terms of those schemes will be billed. Only billing term schemes classified as prepaid can be included in this list. It is mandatory to select at least one billing term scheme |
Consider accounts receivable classifications* | The accounts receivable classification be considered by the prepaid billing run process. Only billable entities owned by accounts receivable having one of those classifications will be billed. It is mandatory to select at least one accounts receivable classification |
Filters | |
Accounts receivable | A list of accounts receivable that are used as filters. If specified then only the those accounts receivable will be billed by the prepaid billing run process |
Subscriptions | A list of subscriptions that are used as filters. If specified then only those subscriptions will be billed by the prepaid billing run process |
Groups | A list of Groups that are used as filters. If specified then only the accounts receivable owned by the specified Groups will be billed by the prepaid billing run process |
Scheduling Settings | |
Scheduling Settings* | Defines if the prepaid billing run is recurring or one time. In the case of recurring prepaid billing runs, the recurrence is inherited from the prepaid billing run definitions (and is visible to the user) |
Configuring a Prepaid Billing Run tailored to your company's needs
- Navigate to BILLING > BILLING > PERFORM PREPAID BILLING RUNS
- Either search for an existing one or from the Top Menu click on NEW
MAIN INFORMATION
Bill as of date: Click on the calendar and select a date
Life Cycle State: This is read only and will be automatically set by the system
Scheduled Date: This is read only and will be automatically set by the system
- Enable Stop Service Step by Default: Check the box if you would like to enable. (Related configuration can be found at Configuring Prepaid Billing Run Definitions
- Enable Start Service Step by Default: Check the box if you would like to enable and configure accordingly in Configuring Prepaid Billing Run Definitions
Enable Wallet Consumption Estimation Step: Select an option from the drop down list.
Info Skip estimation of wallets for faster execution
CRITERIA
- Billing Term Schemes
- Click on ADD and use the search modal to select the Billing term schemes to be included
OR - Click on ADD ALL BILLING TERM SCHEMES
- Click on ADD and use the search modal to select the Billing term schemes to be included
- Classifications
- Click on ADD and use the search modal to select the account Classifications to be included
OR - Click on ADD ALL CLASSIFICATIONS
- Click on ADD and use the search modal to select the account Classifications to be included
- Billing Term Schemes
FILTERS
- Groups
- Click on ADD and use the search modal to select the groups whose subscriptions should be included (Owned by Group)
- Accounts receivable
- Click on ADD and use the search modal to select the groups whose subscriptions should be included
- Subscriptions
- Click on ADD and use the search modal to select the subscriptions that should be included
- Groups
SCHEDULING SETTINGS
- Recurring: Check the box if the Billing Run should be recurring
- Recurrence Settings: The default values as defined in the Billing Run Definition are loaded.
- Provide a different number and select UOT
From the Top Menu click on SAVE
LOG INFORMATION
Include Page WIP:Log Information - GlobalWIP: Log Information - Global
Executing a Prepaid Billing Run
Once a Billing Run is created it will then need to be executed in order to actually bill the subscribers.Users will have the option to execute a Billing Run up to any of the 4 stages that are available. Visit /wiki/spaces/V4Manual/pages/9833562 for a detailed description of all the Billing Run stages available.
If the Billing Run is not in the final State, i.e. Formatting, then the the user will be allowed to continue with the execution of the Billing to any of the follow up steps.
- Navigate to BILLING > BILLING > PERFORM PREPAID BILLING RUNS
- Search for the Billing Run you would like to execute and click on the number to go to the data entry page
- From the Actions Menu click on Actions > Execute
- In the Execute Prepaid Billing Run Modal
- Execute Now: Check the box to execute the Billing Run directly
- Scheduled Date: Click on the calendar to select a date and time to start the execution. Click DONE when completed
- Click SAVE
Reading Prepaid Billing Run Results
- Navigate to BILLING > BILLING > PERFORM PREPAID BILLING RUNS
- Search for an existing Billing Run and click on the number to go to the Data entry page
RESULTS
- Number of Generated Wallet Transactions: Provides the total number of wallet transactions generated from the current execution of the billing run
- Start Date: Provides the Start Date of the Billing Run
- End Date: Provides the End Date of the Billing Run
- Results per Step: Provides all the steps taken for the specific Billing Run and gives analytically the Financial Transactions created and the entities included
EXCEPTIONS
- Accounts Receivable: Provides the accounts which were not billed due to some error
- Code: The code of the error that caused failure in billing the account
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Related Areas
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Popular Labels
|