• Mandatory fields have been definedFields 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 are used by at least one entitySubscription

• Use the Amend action instead
• If there is at least 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

It determines Determines the type Type of billable entity 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' and 'Prepaid'. In this case theType should be set to 'Prepaid'.

• 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 schemeBilling Terms.

Each billing term scheme Billing Term Scheme has an effective and expiration date'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

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

The Billable Period Start Date used to determine how to automatically set the billable period start date on each new subscription service, which is the date that determines the start date of the billable period of each 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 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-Rate: Services which are billed after being used for a certain period (usually on a daily basis); funds are directly deducted from the Wallet.
• Pre-Rate: Services which are billed for an upcoming period defined in the System; funds are directly deducted from the Wallet to cover the whole period. 
  • Period Billed in Advance: This is the number of days/weeks/months that a Pre-Rated Service should be billed in advance.
    If the Wallet of the Subscriber does not have enough money to cover for the Pre-Rated period, then the Service(s) cannot be activated.  

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

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.

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. 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 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 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.

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

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.