Learn to set up Normal Billing related business processes and rules.
Mandatory Configuration: Links to manuals of Normal Billing configuration modules that are required for the module to work correctly.
Related Configuration: Links to manuals of configuration modules other than the Normal Billing's that offer additional functionality or are required for the module to work correctly.
Optional Configuration: Links to manuals of Normal Billing configuration modules that offer additional functionality but are not required for the module to work correctly.
Mandatory Configuration
The following modules must be configured in order to use the Normal Billing Run:
| Module Name | Manual | Description |
|---|---|---|
Normal Billing Run Definitions | Configuring Normal Billing Run Definitions | Normal Billing Run Definitions is a set of business rules used to control the behaviour of Normal Billing Runs throughout their Life Cycle. Normal Billing Run Definitions are used to define business rules and default values applied during the Billing Run. |
| Billing Term Definitions | Billing Term Definitions is a set of business rules used to control the behaviour of Billing Terms throughout their Life Cycle. The billing rules affect both Jobs and Subscriptions. | |
| Billing Term Scheme Definitions | Billing Term Schemes are used to control the creation and modification of Jobs and Subscriptions Billing Terms. They are used to identify the entities to be included in Normal Billing based on their (Normal or Prepaid) Billing Method. |
Related Configuration
The following modules are related to, but are not a part of, the Normal Billing Run. Such entities either:
- Must be configured accordingly in order to be able to start using the Normal Billing Run module (Configuration Type = Mandatory)
OR - May be configured to use the Normal Billing Run module at its full capacity (Configuration Type = Optional).
| Module Name | Module Manual | Module Description | Configuration Type |
|---|---|---|---|
| Subscription Definitions | Configuring Subscription Definitions | A Subscription Definition is a set of business rules and conditions used in order 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 |
| Job Definitions | Configuring Jobs Definition | Jobs Definitions is a set of business rules that is used to control the behaviour of Jobs throughout their Life Cycle. Job Types must be defined in the Definition to be available for use. | Optional |
| Job Types | Configuring Job Types | Job Types define the behaviour and nature of each Job. Users with permission to create Jobs of the specific type can be can defined via Job Types. | Optional |
| Price Plans | Managing Price Plans | Price Plans are a company's price catalogs. Products must be added to at least one Price Plan in order 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 in order to determine how each product is billed. | Optional |
| Usage Service Catalogs | Managing Usage Service Catalogs | Usage Service Catalogs are the pricing catalogs used for billing Usage Services. In order to bill Usage services a Usage Service Catalog must be configured. | Optional |
Optional Configuration
The following entities are available and can be configured under the Normal 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 |