• Mandatory fields have been defined

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

• Not applicable

• Not applicable

• Not applicable

• Mandatory fields have been definedFields must be defined.
• Name and Code must be unique.

• Cannot be edited if they have been added on at least one entityused by one or more Subscription

• Use the Amend action insteadAction 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 Schemes cannot be deleted if there are any billable entities Subscriptions and Jobs which are not terminated or have 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 allowed able to use this billing term schemethe Billing Term Scheme. In this case, the classification Classification is set to 'Subscriptions'.

Defines Determines the billing type Billing Type that will be used by the billing engine Billing Engine in order to bill services Services and physical goodsPhysical Goods. The supported options are the following:

• Normal
• Prepaid

'Normal' and 'Prepaid'. In this case, the Type should be set to 'Normal'.

• Draft: Billing term schemes having that life cycle state 'Draft' - State cannot be used to create billing termsBilling Terms.Effective: Billing term schemes having that life cycle state
• 'Effective' - State can be used to create billing terms Billing Terms and to apply billing rules during billing runsTerminated: Billing term schemes having that life cycle state Billing Rules during Billing Runs.
• 'Terminated' - State cannot be used to create new billing terms. Billing terms already related with a terminated billing term scheme will still be billed by applied the billing rules specified on that billing term scheme.

• Billing Terms.

Each Billing Term Scheme has an 'Effective' and 'Expiration' Date, which are set automatically when the billing term scheme Scheme is created or being replaced by another billing term schemeScheme. A version number is also kept on each billing term scheme that defines the version of each billing term scheme instance

This section is used to:

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.

• 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
: Anniversary billing is a method of billing where
• • Billing: customers are billed for a period of time which starts on
a billing
• • the Billing cycle day which is preferred by each customer.
  • Period
: Period billing is a method of billing where
• • Billing: customers are billed for a period of time which starts on
a billing
• • the Billing cycle day which is specified by the
billing
• • Billing company.
Determine the default billing cycle day during the creation of billing terms having that billing term scheme. 
If the billing term scheme is set to “Period billing”, then this value will be used to set the day of month until which the subscription

• The Billing Cycle Day is the day of the month until which a Subscription will be billed by the

Determines if the billing terms will use a fixed or flexible pricing. If fixed pricing is selected then ad hoc discounts cannot be applied on billable entities having billing terms of this scheme

Note: For May 14 release only the fixed option should be allowed.

• 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 Subscription Service (it answers to the question “from which date should I start billing this service”). Subscription service billable period start date is by default set equal to the subscription service effective date, but it can be overridden by the rules specified in these definitions or by the subscription action which is adding the subscription service, if the billable period start date is explicitly defined there. The supported 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 Action performed date
• Subscription action 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. Subscription service billing effective date is by default It is set equal to the subscription service effective date, but it can be overridden by the rules specified in these definitions or by the subscription action which is adding the subscription service, if the billing effective date is explicitly defined there. The supported Subscription Service Effective Date, by default. The available options are the following:

• Subscription action Action performed date
• Subscription action 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

Determines the causes of extending the allowed cancel date. Multiple options can be selected. The supported options are the following:

• Extend based on days in resting
• Extend based on disconnected days
• Extend based on grace periods

Determines the causes that should automatically extend the price rate (extend an offering that is already applied to a subscription). Multiple options can be selected. The supported options are the following:

• Extend based on binding end date

Determines which of the billing frequencies should be allowed to be used and provides a different name if needed, by specifying the following:

• Billing Frequency
• Billing Frequency Label

The default behavior is to allow all the predefined billing frequencies, except the custom ones. The Billing frequency that will be selected as the billing term scheme’s default billing frequency, will also be kept at the billing term scheme’s header.

Determines which of the binding periods should be allowed to be used and provides a different name if needed, by specifying the following:

• Binding Period
• Binding Period Label

The default behavior is to allow all the predefined binding periods, except the custom ones. The Binding period that will be selected as the billing term scheme’s default binding period, will also be kept at the billing term scheme’s header.

Determines which services are supported by the billing term scheme. This means that the billing term scheme related to a subscription will define which services are available to exist on the subscription. If a billing term scheme does not include any services as supported ones, then this means that all services are allowed for this scheme.

This section is also used in order to define the billing type per supported service in cases in which a services has a different billing type compared to the billing term scheme’s type, that is, override the billing term scheme’s billing type. The supported billing types are the following:

• Post Bill Services: Post Bill Services determine a set of services which should be billed after they have been used. Multiple services can be defined as post bill services. Services defined in this list should not be included in pre bill services list. If no services are specified then all services are considered to be pre billed.
• Pre Bill Services: Pre Bill Services determine a set of services which should be billed in advance, before they have been used. Multiple services can be defined as pre bill services. Services defined in this list should not be included in post bill services list. This list should be calculated dynamically and should include all allowed services which are not specified as post bill services.

Only termed, usage and expense services are allowed to be added in that list

All

Post bill and Pre bill categorisation is applicable only on normal schemes

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.