Back to Prepaid Billing Main Page
| Excerpt | ||
|---|---|---|
| ||
Find out what configurations should be performed before the CRM.COM Prepaid Billing module is used |
Learn to set up Prepaid Billing related business processes and rules.
Mandatory Configuration: Links to manuals of Prepaid Billing configuration modules that are required for the module to work correctly.
Related Configuration: Links to manuals of configuration modules other than the Prepaid Billing that offer additional functionality or is required for the module to work correctly.
Optional Configuration: Links to manuals of Prepaid Billing configuration modules that offer additional functionality but are not required for the module to work correctly.
| Anchor | ||||
|---|---|---|---|---|
|
The following modules must be configured to use the Prepaid Billing Run
| Module Name | Manual | Description |
|---|---|---|
Prepaid Billing Run Definition | Configuring Prepaid Billing Run Definitions | Prepaid Billing Run Definitions is a set of business rules used to control the behaviour of Prepaid Billing Runs throughout their Life Cycle. Prepaid Billing Run Definitions are used to define business rules, and default values applied the Billing Run. |
| Billing Term Definition | Billing Term Definitions is a set of business rules used to control the behaviour of Billing Terms throughout their Life Cycle. The rules affect Subscriptions with regards to Billing. | |
| Billing Term Scheme Definition | Billing Term Schemes are used to control the creation or modification of Billing Terms for Subscriptions. They are used to identify the entities to be included in Prepaid Billing based on their (Norma or Prepaid) Billing Method. |
| Anchor | ||||
|---|---|---|---|---|
|
The following modules are related to but are not a part of, the Prepaid Billing Run. Such entities either:
- Must be configured accordingly to be able to start using the Prepaid Billing Run module (Configuration Type = Mandatory)
OR - May be configured to use the Prepaid Billing Run module at its full capacity (Configuration Type = Optional).
| Module Name | Module Manual | Module Description | Configuration Type | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Wallets Definitions | Configuring Wallet Definitions | A Wallet Definition is a set of business rules used to control the behaviour of the Wallet throughout its Life Cycle. It is mandatory to define the Types of Wallet Transactions to be created by Prepaid Billing, as well as the rules on debiting and crediting the Wallets.
| Mandatory | ||||||
| Voucher Definitions | Configuring Voucher Definitions | A Voucher Definition is a set of business rules used to control the behaviour of a Voucher throughout its Life Cycle. Vouchers can be used to top up Wallets which in turn can be used by Prepaid Billing to pay for related Debit Wallet Transactions. | Optional | ||||||
| Subscription Definitions | Configuring Subscription Definitions | A Subscription Definition is a set of business rules and conditions used to create and maintain the Subscription throughout its Life Cycle. | Optional | ||||||
| Subscription Types | Configuring Subscription Types | The Subscription Type determines the application of the company's commercial policies for each type of Subscription. This includes which Services and Physical Goods can be added, which Billing Term Schemes are available, and which Organisational units can access the Subscriptions. | Optional | ||||||
| Subscription Action Types | Configuring Subscription Action and Sub-Action Types | Used to define custom Subscription Action Types | Optional | ||||||
| Price Plans | /wiki/spaces/WIP/pages/10008533 | Price Plans are a company's price catalogs. Products must be added to at least one Price Plan to be eligible for billing. Multiple Price Plans can be configured and each CRM.COM billable entity in the system (Subscriptions and Jobs) can be billed from a different Plan. Price Plans can be conditional; Several discounts and promotions can be provided to customers through Price Plans provided certain conditions are met. Price Plans are required to determine how each product is billed. | Optional | ||||||
| Usage Service Catalogs | Usage Service Catalogs | Usage Service Catalogs are the pricing catalogs used for billing Usage Services. To bill Usage services a Usage Service Catalog must be configured. | Optional |
| Anchor | ||||
|---|---|---|---|---|
|
The following entities are available and can be configured under the Prepaid Billing Run. A working CRM.COM model can exist without them being configured.
| Module Name | Module Manual | Module Description |
|---|---|---|
| Not applicable | Not applicable | Not applicable |
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Related Areas
|