• Multiple Billing Term Subscription definitions can exist in the system, but each one should have a unique name and alternative code
• Only one active Billing Term Subscription  definition can exist at any given time

• If no active Billing Term Subscription definition exists, then no Billing Term Subscription can be created

• Mandatory Fields must be defined
• Name and alternative code must be unique

• Not Applicable

• Mandatory Fields must be defined
• Name and alternative code must be unique

• Not Applicable

• Not Applicable

• Cannot be deleted if its the active definition

It determines the type of billable entities on which the billing term definitions will be applied on. In this case the classification is set to Subscriptions

Determines the rules that are applied during billing term amendments. The rules consists of the following:

• Restrict binding period extension
• Restrict binding period adjustment
• Restrict binding period renewal

Applicable on Billing Term Schemes (drill down): Defines the billing term schemes that the subscriptions should be following in order for the specified processing method to be applicable. Multiple billing term schemes can be specified through that list.

Exceptions on specific users or units can also be defined per each rule

Determines the rules that are applied during prepaid billing runs. The rules consist of the following:

• Restrict debiting wallets with balance less than the stop service threshold: If enabled then the prepaid billing run will debit wallets for just the remaining amount and not below that. For example if the wallet balance is 10, the stop service threshold is 0, this rule is enabled and the prepaid billing run rated an amount of 15 euros, then a wallet debit transaction will be created for the amount of 10 euros and not 15 euros, resulting to a wallet balance of 0 euros. If this rule is not enabled then the wallet debit transaction will be created for the amount of 15 euros, resulting to a wallet balance of -5 euros.
  The disconnection threshold can be configured in the Prepaid Billing Run Definition under Stop Service Tab which becomes available only if enabled 

Applicable on Billing Term Schemes (drill down): Defines the billing term schemes that the subscriptions should be following in order for the specified processing method to be applicable. Multiple billing term schemes can be specified through that list.

Determines the rules that are applied when there are changes in price plans which are already used in billing terms. The rules consist of the following:

• Applying price changes only on customers in binding
• Applying price changes only on customers out of binding

Applicable on Billing Term Schemes (drill down): Defines the billing term schemes that the subscriptions should be following in order for the specified processing method to be applicable. Multiple billing term schemes can be specified through that list.

Defines the billing rules that should be applied on usage services based on a set of conditions. Multiple rules can be specified but the conditions should not be contradicting

• APPLICABLE UP TO R9 Processing Method (radio button): Defines if the usage services should be processed and billed immediately on submitting them or if they should be billed by the billing run process. The supported values are the following:
  • Billing run process (the default option)
  • Immediately after execution
• AVAILABLE FROM CRM.COM R10.0.0 Maximum un-billed amount threshold: Defines the maximum rated amount of among all usage services that needs to be reached in order for them to be included in a bill. (Applies only for Normal Subscriptions and not Prepaid)
• AVAILABLE FROM CRM.COM R10.0.0 Maximum number of un-billed UDRs:  Defines the maximum number of unprocessed Usage Detail Records required in order for Usage Services to be included in a bill. (Applies only for Normal Subscriptions and not Prepaid)

• Applicable on Billing Term Schemes (drill down): Defines the billing term schemes that the subscriptions should be following in order for the specified processing method to be applicable. Multiple billing term schemes can be specified through that list.

A set of rules which, if met, override the default Credit Limit Rule of CRM.COM, which does not allow any of the events, (Subscription actions) to be executed if the Credit Limit of the customer, defined on their Accounts Receivable is exceeded. i.e. the balance of the Accounts Receivable is greater than the Credit Limit
If no rules are defined, then the default behaviour of exceeding Credit Limit is applied and no Subscriptions can be activated unless the balance of the Accounts Receivable is less than the Credit Limit of the Account

This set of rules define the required conditions that should be met in order for actions to override the Credit Limit Rule and be applied on Subscriptions.

Determines the conditions that should be fulfilled in order for a subscription or a subscription service to become effective. The condition set includes the following:

• Billing term scheme
• Financial account classification
• Credit rating
• Outstanding Amount Less Than
• Outstanding for Less than x days
  If the actual  Due amount (due is calculated based on the x days ago) is more than or equal than the figure provided here, then the subscription will not be activated
• Account Balance
  If the actual Account Balance is more than or equal than the figure provided here, then the subscription will not be activated

The conditions are applicable on a set of events. More than one event can be selected per each condition set. The set of events include the following:

• Become effective subscriber
• Subscription activation
• End subscription resting
• Subscription service start
• Service upgrade
• Service downgrade
• Service swap
• Add service usage: If checked then the activation conditions will be applicable whenever an Add Service Usage is submitted.
• Short Term Subscription activation
• End Short Term Subscription deactivation

Determines the rules that are applied whenever a subscription goes into resting. The rules consist of the following:

• Allowed days in resting per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in resting per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days in resting per each time

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule.

Determines the rules that are applied whenever a subscription's grace period is extended. The rules consist of the following:

• Allowed days in grace per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in grace per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days in grace per each time

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule.

Determines the rules that are applied whenever a subscription or subscription service is regretted. The rules are enforcing the customers to regret within a specific period of time after the subscription or the service was activated.The rules consist of the following:

• Allow regretting a subscription
  • Maximum period after subscription effective date, agreement date or binding start date, measured in days, weeks, months or years
• Allow regretting a mandatory subscription service
  
  • Maximum period after subscription service effective date, agreement date or binding start date, measured in days, weeks, months or years
• Allow regretting an optional subscription service
  
  • Maximum period after subscription service effective date, agreement date or binding start date, measured in days, weeks, months or years

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule.

Determines the rules that are applied whenever a mandatory or optional service is swapped. The rules are enforcing the customers to swap services only if a period of time after the date that the subscription or the service was activated, has already passed.The rules consist of the following:

• Swap Type
  • Allow service upgrading
  • Allow service downgrading
  • Allow service switching
• Minimum period of time before swapping is allowed, starting from 
  
  • Subscription Effective Date
    Services can be swapped after Subscription Effective Date
  • Subscription Service Effective Date
    Services can be swapped after Subscription Service Effective Date
  • Binding start date
    Services can be swapped after Binding Start Date 
  • Agreement Date
    Services can be swapped after Agreement Date 
  • AVAILABLE FROM CRM.COM R11.0.0 Rated up to date
    Services can be swapped after the Rated Up to Date, if they are already rated

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule. This type of rules are configured separately for mandatory and optional services

Determines the rules that are applied whenever a billable entity is cancelled while not in binding. The rules are enforcing the customers to notify the service provide before cancelling a subscription or subscription service, X UOT before their requested cancellation date. The rules consist of the following:

• Cancellation type: 
  
  • subscription cancellation
  • mandatory subscription service cancellation
  • optionally subscription service cancellation
• Cancellation notice: A period of time before cancellation, which can be measured in days, weeks, months and years

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule

Determines the rules that are applied whenever a billable entity is cancelled while in binding. The rules are enforcing the customers to cancel their subscriptions or subscription services only if the cancellation date is near the binding end date or the allowed cancellation date. The rules consist of the following:

• Cancellation type:
  • subscription cancellation
  • mandatory subscription service cancellation
  • optionally subscription service cancellation
• Cancellation type: A period of time before the binding end date or the allowed cancellation date, which can be measured in days, weeks, months and years

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule. If not rules are specified or applied then cancellations while in binding are not allowed.

Determines the rules that are applied whenever a subscription is activated for a short period of time. The rules consist of the following:

• Allowed days in short term effective per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in short term effective per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days in short term effective per each time

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule.

Determines the rules that are applied whenever a subscription is deactivated for a short period of time. The rules consist of the following:

• Allowed days in short term not effective per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in short term not effective per year, starting either from the
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days in short term not effective per each time

The rules can be applied either on all billing term schemes or only on specific billing term schemes. Exceptions on specific users or units can also be defined per each rule.

A list of events upon which the Expense service might be eligible to be automatically applied on a subscription as long as the policy's Conditions are met. Only one event can be selected each time. The following events are available:

• Subscription Initiation
  Expense Service is added automatically whenever a new subscription is created and activated or when a draft subscription is activated.
• Short Term Subscription activation
   Expense service is added automatically whenever a subscription is activated for a short period of time
• Subscription Cancellation
  Expense Service is added automatically whenever a subscription is cancelled 
• Subscription Regret
  Expense Service is added automatically whenever a subscription is regretted 
• Change Subscriber
   Expense Service is added automatically whenever the subscriber changes on the subscription (change of subscription owner, not just the accounts receivable).
• Add Installed Item
   Expense service is automatically added when a new installed item is added on the subscription.through the Add Installed Item action
• Swap Installed Item
  Expense service is automatically added when a new installed item is added on the subscription through a swap installed item action
• Remove Installed Item
  Expense service is automatically added when an installed item is removed from the subscription through a remove installed item action 

A set of Conditions that should be met in order for the Expense Service to be added on the subscription. Multiple conditions can be defined per event-based conditional expense policy. The conditions set includes the following:

• Subscription Types
• Billing Term Schemes
• Binding state
  • In Binding
  • Out of Binding
• Existing Installed Item
  • Existing Installed item product (available for all type of events)
  • Existing Installed item product type (available for all type of events)
  • Existing Installed item product family (available for all type of events)
• Installed Item to be added
  • Installed Item product to be added (available only if the event is add installed item or swap installed item)
  • Installed Item product type to be added (available only if the event is add installed item or swap installed item)
  • Installed Item product family to be added (available only if the event is add installed item or swap installed item)
• Installed Item to be removed
  • Installed Item product to be removed (available only if the event is remove installed item or swap installed item)
  • Installed Item product type to be removed (available only if the event is remove installed item or swap installed item)
  • Installed Item product family to be removed (available only if the event is remove installed item or swap installed item)

Used to determine additional billing directions to extend the default behavior of the system. Additional billing direction consist of the following:

• Additional Billable Subscription Service Life Cycle States: Billable subscription service life cycle states are used to determine which subscription service life cycle state history periods are billable or not. By default the system considers “Effective” and "Short Term Effective" periods as billable, but this can be extended by defining additional billable subscription service life cycle states. The supported states are the following:

• • Draft
  • Not Effective
  • In Resting
  • Short Term Not Effective

• Additional conditions are available, which include the following:
  • Subscription Services
  • Subscription Types
  • Billing Term Schemes
  • Binding state (in binding / out of binding)

• Additional Non Creditable Subscription Service Life Cycle States: Additional non creditable subscription service life cycle states are used to determine which subscription service life cycle state history periods should never be refunded (i.e. credited). By default the system considers “Effective”, "Short Term Effective" and “Draft” periods as non creditable, but this can be extended by defining additional non creditable subscription service life cycle states. The supported states are the following:
  • Draft
  • Expired
  • Not Effective
  • In Resting
  • Cancelled
  • Swapped
  • Removed
  • Short Term Not Effective

Additional conditions are available, which include the following:

• Subscription Services
• Subscription Types
• Billing Term Schemes
• Binding state (in binding / out of binding)

Cancellation penalties are used to determine the penalties that will be applied when a service is cancelled either within or outside of binding.

Cancellation penalties can be specified either as a fixed amount or as a percentage. In the case of cancellation within binding the percentage is applied on the remaining time up to the binding end date. Different cancellation penalties within binding can be configured to cover different periods before binding end date. For example 20 percent if the cancellation is 12 to 6 months before the binding end date and 10 percent if the cancellation is 6 months before the binding end date.

Multiple cancellation penalties can be defined. Each cancellation penalties can be applied on all subscribers or on specific subscribers based on their:

• subscription services
• subscription type
• billing term scheme