• Mandatory Fields must be defined.
• Name and Code must be unique.

• Not applicable

• Not applicable

• Not applicable

• Mandatory Fields must be defined.
• Name and Code must be unique.

• Cannot be edited if used by one or more Subscription

• Use the Amend Action instead.
• If there are one or more versions of a Billing Term Scheme for Jobs, then a new Billing Term Scheme instance is created. The new instance will have the same values and Billing Term Code as the previous one, an augmented version number, and the modified information.

• Not applicable

• Billing Term Schemes cannot be deleted if there are Subscriptions and Jobs which are not terminated or if there is billable information which was not processed and billed yet.

• Not applicable

• Not applicable

• Not applicable

• Mandatory Fields must be defined.
• Name and Code must be unique.

• Not applicable

• Not applicable

• New Billing Term Scheme Instance
  • Version number will increase by 1
  • Effective Date will be set to the current date
  • All the configuration will be carried over from previous version
• Previous Billing Term Scheme Instance
  • Expired On will be set to the current date
  • Life Cycle Date will be updated to Terminated

Determines the Type of Billable Entity that will be able to use the Billing Term Scheme. In this case, the Classification is set to 'Subscriptions'.

Determines the Billing Type that will be used by the Billing Engine in order to bill Services and Physical Goods. The supported options are 'Normal' and 'Prepaid'. In this case, the Type should be set to 'Normal'.

• 'Draft' - State cannot be used to create Billing Terms.
• 'Effective' - State can be used to create Billing Terms and to apply Billing Rules during Billing Runs.
• 'Terminated' - State cannot be used to create new Billing Terms.

Each Billing Term Scheme has an 'Effective' and 'Expiration' Date, which are set automatically when the Scheme is created or replaced by another Scheme. A version number is used for each Billing Term Scheme that defines each specific instance.

An auto-generated number which is used to specify the version of each Scheme. If the specific version is already in use by a Subscription, a new Scheme version is created when the Scheme is amended, by the respective Action.

"VIEW PREVIOUS VERSIONS" link allows you to search and view the previous versions of the Definition.

Determines which Termed Services and Expenses are supported by the specific Billing Term Scheme.

The Subscription's associated Scheme defines its available Services.

This section is also used in order to define the Billing Type of each supported Termed Service, which can be one of the following:

• Post-Bill: Services which are billed after they have been used.
• Pre-Bill: Services which are billed before they have been used.

Expenses do not have a Billing Type as they are always billed by the next Billing Run.

AVAILABLE FROM CRM.COM R12.0.0 This section is also used to define which of the Services will be Excluded from Deactivation during the Deactivate Normal Subscriptions Run Process. This information is used by the System in the case that the Deactivate Type in Deactivate Normal Subscriptions Run Definitions is set to 'Deactivate Services'. Two options are available for selection per each Service:

• Yes: The Service will not be deactivated
• No: The Service will be deactivated

The Billing Frequencies which can be used by Subscriptions of the specific Billing Term Scheme.

The Binding Periods which can be used by Subscriptions of the specific Billing Term Scheme.

Check Box that determines whether it is mandatory to provide Binding Periods during the Billing Term configuration, when creating a new Subscription (through Subscription Actions or Jobs) and when amending a Subscription's Billing Terms (through Subscription Action AMEND BILLING TERMS).

Determines the Price Plans available during the creation of Billing Terms having that specific Billing Term Scheme. By default, all Price Plans can be selected in the allowed Price Plans of a Billing Term Scheme.

This section is used to determine Billing method can be used by Billing Terms of that specific Scheme. The supported options are:

• • Anniversary Billing: customers are billed for a period of time which starts on the Billing cycle day which is preferred by each customer.
  • Period Billing: customers are billed for a period of time which starts on the Billing cycle day which is specified by the Billing company.

• The Billing Cycle Day is the day of the month until which a Subscription will be billed by the Billing Engine.
  • For Period Billing: Automatically set on the Subscription as defined in the Allowed Cycle Day field of the Billing Term Scheme.
  • For Anniversary Billing: The user must set the Billing Cycle Day, when creating the Subscription. The range of allowed values is defined in the Allowed Cycle Day Range of the Billing Term Scheme.

Defines whether the Anniversary Date will be set automatically on the Subscription Billing Term when a Draft or Effective subscription is created.
If selected, the Billing Term Scheme's and Subscription Billing Term's allowed Cycle Days are not applicable.
Defaults to 'No'.

Defines whether the Anniversary Date will be automatically reset on the Subscription Billing Term whenever the Subscription goes back to the Effective Life Cycle State.
If selected the Billing Term Scheme's and Subscription Billing Term's allowed Cycle Days are not applicable.
Defaults to 'No'.

Determines the start date of the billable period of each Subscription Service (it answers the question “from which date should the Service be considered by the Billing Run”).  For example, if a Service is 'Effective' from the 1st of June but the Billable Start Date is the 1st of August, then the Billing Engine will only start considering the Service from the 1st of August.
Billable Period Start Date is set equal to the Subscription Service Effective Date, by default. The available options are the following:

• Subscription Action performed date
• Subscription Action performed date + X UOT (i.e. + 1 month)
• Subscription Service Initial Effective Date
• Subscription Service Initial Effective Date + X UOT (i.e. + 1 month)
• Subscription Service Latest Effective Date
• Subscription Service Latest Effective Date + X UOT (i.e. + 1 month)
• Binding Start Date
• Binding Start Date + X UOT (i.e. + 1 month)
• Agreement Date
• Agreement Date + X UOT (i.e. + 1 month)

The date on which a Service should start being billed. It is set equal to the Subscription Service Effective Date, by default. The available options are the following:

• Subscription Action performed date
• Subscription Action performed date + X UOT (i.e. + 1 month)
• Subscription Service Initial Effective Date
• Subscription Service Initial Effective Date + X UOT (i.e. + 1 month)
• Subscription Service Latest Effective Date
• Subscription Service Latest Effective Date + X UOT (i.e. + 1 month)
• Binding Start Date
• Binding Start Date + X UOT (i.e. + 1 month)
• Agreement Date
• Agreement Date + X UOT (i.e. + 1 month)

Determines if the Billing Terms will use a 'Fixed' or 'Flexible' pricing. If 'Fixed' pricing is selected, Additive Discounts cannot be applied on Subscriptions and Jobs having Billing Terms of this specific Scheme.

Determines which Subscription Actions on a can cause the extension of the Binding End Date.

• Extend based on days 'In Resting'
• Extend based on 'Not Effective' days
• Extend based on 'Grace Periods'.

Determines which Subscription Actions can cause the extension of the Allowed Cancellation Date.

• Extend based on days 'In Resting'
• Extend based on 'Not Effective' days
• Extend based on 'Grace Periods'.

Determines whether agreed Price Rates should be extended based on the Binding End Date, in case a Price Plan Rate modification occurred since the original agreement.