It determines the type of billable entity that will be allowed to use this billing term scheme. In this case the classification is set to Subscriptions

Defines the billing type that will be used by the billing engine in order to bill services and physical goods. The supported options are the following:

• Normal
• Prepaid

• Draft: Billing term schemes having that life cycle state cannot be used to create billing terms.
• Effective: Billing term schemes having that life cycle state can be used to create billing terms and to apply billing rules during billing runs
• Terminated: Billing term schemes having that life cycle 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.

Each billing term scheme has an effective and expiration date, which are set automatically when the billing term scheme is created or being replaced by another billing term scheme. 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:

• Determine which of the two billing methods can be used by billing terms having that billing term scheme. The supported options are:
  
  • Anniversary: Anniversary billing is a method of billing where customers are billed for a period of time which starts on a billing cycle day which is preferred by each customer.
  • Period: Period billing is a method of billing where customers are billed for a period of time which starts on a billing cycle day which is specified by the 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 will be billed by the billing engine. This value will be selected based on the billing term scheme’s configuration and will not be allowed to be set on the billing term level.
  • If the billing method on the billing term scheme is set to “Anniversary” then it is the billing term that will define the billing cycle day. At the billing term scheme level, a range of allowed billing cycle days is specified so at the billing term level, the billing cycle day must be set within this range.

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.

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

Billing Effective Date definition is used to determine how to automatically set the billing effective date on each new subscription service, which is the date that determines when a subscription service should start being billed. Subscription service billing effective 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 billing effective date is explicitly defined there. The supported 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 the causes of extending the binding end date. Multiple options can be selected. The supported options are the following:

• Extend based on days in resting
• Extend based on not effective days
• Extend based on grace periods

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 listCRMCOM-3101 -Ability to create, maintain and use Expense ServicesIN PROGRESS

All

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