Include Page | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
What Comes First
To start using Normal Subscriptions, configure the System to support your business model. In the following table, you can find the configuration modules related to Normal Subscriptions
Sub-module | Type | Classification | Navigation | Dig In |
---|---|---|---|---|
Billing Term Schemes | Configuration | CONFIGURATIONBILLING APPLICATIONBILLINGSET UP BILLING TERM SCHEMES | /wiki/spaces/WIP/pages/10008620 | |
Subscription Types | Configuration | CONFIGURATIONBILLING APPLICATIONSUBSCRIPTIONSSET UP TYPES | /wiki/spaces/WIP/pages/10008626 | |
Subscription Definitions | Configuration | CONFIGURATIONBILLING APPLICATIONSUBSCRIPTIONSSET UP BUSINESS DEFINITIONS | /wiki/spaces/WIP/pages/10008628 | |
Billing Term Definitions | Configuration | CONFIGURATIONBILLING APPLICATIONBILLINGSET UP BILLING TERM DEFINITIONS | /wiki/spaces/WIP/pages/10008621 | |
Normal Billing Run Definitions | Configuration | CONFIGURATIONBILLING APPLICATIONBILLINGSET UP NORMAL Billing Run DEFINITIONS | /wiki/spaces/WIP/pages/10008768 | |
Subscription Action and Sub-Action Types | Configuration | CONFIGURATIONBILLING APPLICATIONSUBSCRIPTIONSSET UP SUBSCRIPTION ACTION TYPES | /wiki/spaces/WIP/pages/10008627 | |
Bill Sending Runs | Transactional | BILLINGBILLINGPERFORM BILL SENDING RUNS | Using Bill Sending Runs | |
Deactivate Normal Subscriptions | Transactional |
...
BILLINGSUBSCRIPTIONSDEACTIVATE NORMAL SUBSCRIPTIONS | Using Deactivate Normal Subscriptions Run Definitions | |||
Subscription Maintenance Utility | Transactional | BILLINGSUBSCRIPTIONSSUBSCRIPTION MAINTENANCE UTILITIES | Using Subscription Maintenance Utilities Run Definition |
---|
Anchor | ||||
---|---|---|---|---|
|
First, you must configure the Billing Term Schemes.
...
A Subscription Type defines the company's commercial policies which are applied on Subscriptions of that type, such as what Services and what Physical Goods can be added on each Subscription Type, which Billing Term Schemes will be made available for each Subscription Type as well as the company's departments (Organisational Units) can create Subscriptions of the specific Type.
Anchor |
---|
...
|
...
|
An active Subscription definition must then be configured.
A Subscription Definition is a set of business rules and conditions which are used in order to create and maintain Subscriptions throughout their Life Cycle. For example, through the Subscription Definitions, you can define the maximum number of Subscriptions you can have per account , or the maximum number of Main Services and Physical products that can be added on to a Subscription.
Subscription Definitions provide a number of restrictions and controls and can be used to define product dependencies. For example, a rule can be set where additional channels cannot be added unless one of the Main channels is added first.
...
Anchor |
---|
...
|
Billing Term Definitions come next. They are differentiated based on Classification, which can be Subscription or Jobs.
Billing Term is the agreement/contract between the customer and the company. It provides information with regards to billing, contract dates and billing periods. Billing Terms are created every time a Billing Term Scheme is added or updated on the Job or Subscription, and it determines whether a Subscription will be handled by Normal or Prepaid Billing. Billing Term behaviour is governed by Billing Term Definition rules.
Billing Term Definitions are used to define business rules used to validate several processes applied to Subscription or Jobs, via their related Billing Term.. For example, you can define rules where you will not allow Regret after a number of days, or define cancellation penalties based on a particular service and remaining binding period. Rules are used across all Billing Terms, regardless of their Schemes, however, for each rule, you can define whether it is only applicable to particular schemes.
...
Anchor |
---|
...
|
Time for Billing!!!
Normal Billing is the mechanism used to bill customers before or after they start using Services they have bought or are subscribed to. Normal Billing is handled by the execution of Normal Billing Runs that create Financial Transactions which are used to debit or credit the customer's Accounts Receivable and which are then grouped and presented to the customers through Bills.
Normal Billing Run definitions is a set of business rules used to control the behaviour of Normal Billing Runs throughout their whole Life Cycle. Normal Billing Run definitions is are used in order to define several business rules that are applied during the Billing Run, but also default values, which are used while running Normal Billing Runs.
Anchor actions actions
Step 6: Setting Up Subscription Action and Sub
actions | |
actions |
...
-Action Types, Bill Sending Runs, Disconnection and Activation Runs
Configure the following modules for additional functionality and categorisation. You can skip configuration of the modules if not required by your business model
Subscription Action Type:
The modifications performed on a Subscription when a Subscription Action is executed depend on the Subscription Action's Type, while the Subscription Sub-Action Type is used to apply a business meaning.There are 2 main characteristics that all Subscription actions have, and these are configured in the Subscription Action Type and Subscription SUb Action Type Level:
...
Sub ActionType Level.
Note There is no need to configure Subscription Action Types as you can find all available Subscription Action Types and Sub-Types in the Subscription's page.
Configure new Subscription Action Types and Sub-Types only if you want to
...
categorise actions executed.
...
...
...
Bill Sending Runs
...
: Once the Billing Run is executed Bills are created. Bill Sending Run Definitions are used to determine the business rules that are used to identify Bills to be sent through Email, SMS or an external System. Configure the Bill Sending Runs if you would like to directly handle Bill sending from CRM.COM
- Subscription Maintenance Utilities Run Definition provides a set of utility batch processes that can be used to maintain Subscriptions.
- Activate Settled Subscriptions
Activates 'Not Effective' Normal Subscriptions that belong to Accounts Receivable that have not exceeded their Credit Limit and that had their balance changed within a specified timeframe - Execute Scheduled Actions
Executes all Scheduled Subscription Actions whose Scheduled Execution date is equal or before the current date.
Note If not configured then deactivated Subscriptions will only be activated by the respective Activation Subscription action, while scheduled actions will never be executed
- Activate Settled Subscriptions
Deactivate Normal Subscriptions Run Definition are used to define the rules to be followed when executing Runs to deactivate Subscriptions. The decision on which Subscriptions should be deactivated is based on the criteria set on the Definitions, among which, you can define criteria related to the Accounts Receivable Classification, Subscription Type and Frequency.
Additionally, you can define whether the deactivation is done based on an Accounts Receivable outstanding amount or the Credit Limit of the Accounts Receivable or both.Note If not configured then Subscriptions will only be deactivated by the respective Deactivate Subscription action
Do it Yourself!!
Panel | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Let's see how you can quickly set up the System to start using Conditional Access module for your Subscriptions business Create the following Subscription Types | Name | Allowed Attributes | Allowed Organisational Units |
Tip |
---|
For the modules, sections and attributes not mentioned you don't need to make any configuration |
Billing Term Schemes
Name | Classification | Type | Allowed Attributes | Billing Rules | |
---|---|---|---|---|---|
Services | Price Plans | Generic | |||
Normal BT | Subscriptions | Normal |
| Main Price Plan |
|
Subscription Types
Name | Allowed Attributes | ||||||||
---|---|---|---|---|---|---|---|---|---|
Billing Term Schemes | Services | Physical Goods | Provisioning Distributors | ||||||
Normal | Normal |
|
|
|
|
|
| |
Create the following Subscription Definition
Subscription Rules | Service Rules | Installed Item Rules | Restrictions | Restrictions | Dependencies||
---|---|---|---|---|---|---|
Restrictions Per Distributor | Dependencies Per Distributor | Tiers | RestrictionsDependencies | Restrictions Per DistributorDependencies Per Distributor | ||
|
| |
|
Create the following Normal Billing Run Definition
Company ZX bills has the following requirements regarding its subscribers billing
- Billing Run executed once a month on the 20th charging the following month
- Transaction Date set on transactions is the 21st
- Due Date is set to the 10th of the next month
- Subscribers are always billed from the last day they were billed + one period. i.e. In July Billing Run, Monthly subscribers are billed from the 1st of August till the 1st of Septemeber, while biannual subscribers would be billed from the 1st of August till the 1st of February
- If a subscriber's total bill amount is less than 5 euro then the bill should not be created at all
- Bills with credit amount less than 50 should be marked for investigation
- All information should be included in the bill and displayed per service
CRM.COM Solution
A Billing Run definition will be set up in the System with the following configurations
Billing Term Definition
Name | Classification |
---|---|
Main Billing Term Definition | Subscriptions |
Normal Billing Run Definition
Requirement | Solution |
---|---|
Billing Run executed once a month on the 20th charging the following month
|
|
Transaction Date set on transactions is the 21st |
|
Due Date is set to the 10th of the next month | This is set in the Normal Billing Run |
Subscribers are always billed from the last day they were billed + one period. i.e. In July Billing Run, Monthly subscribers are billed from the 1st of August till the 1st of September, while biannual subscribers would be billed from the 1st of August till the 1st of February |
|
If a subscriber's total bill amount is less than €5 euro then the bill should not be created at all |
|
Bills with credit amount less than 50 should be marked for investigation |
|
The amounts should be rounded up to 2 decimal places |
|
All information should be included in the bill and displayed per service |
|