• 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 deletedifitsthe'Active' Definition.

Determines the Type of billable entities on which the Billing Term Definitions will be applied. 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 follow, 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 for each Rule.

Determines the Rules that are applied during Prepaid Billing Runs. The Rules consist of the following:

• Restrict the debiting of Wallets with a Balance less than the Stop Service threshold: If enabled then the Prepaid Billing Run will debit Wallets up to the remaining Balance (not more). For example, if the Wallet Balance is €10 and the Stop Service threshold is 0, and this Rule is enabled, a Prepaid Billing Run for €15 will result in a Wallet Debit TransAction for €10 and not €15 euros, resulting in a Wallet Balance of €0. If the Rule is not enabled, then the Wallet Debit TransAction will be created for the amount of €15, resulting in Wallet Balance of - €5.
• The disconnection threshold can be configured in the Prepaid Billing Run Definition under Stop Service Tab which becomes available once enabled.

Applicable on Billing Term Schemes (drill-down): Defines the Billing Term Schemes that the Subscriptionsshouldfollowforthe specified processing method to be applicable. Multiple Billing Term Schemes can be specified through the list.

Determines the Rules that are applied whentherearemodificationinPrice 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 Subscriptionsshouldfollowforthe specified processing method to be applicable. Multiple Billing Term schemes can be specified through that list.

Defines the Billing Rules that should be applied to 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 when submitted 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 unbilled amount threshold: Defines the maximum rated total amount of all Usage Services that needs to be reached for them to be included in a Bill (Applies only for Normal and not Prepaid Subscriptions).
• AVAILABLE FROM CRM.COM R10.0.0 Maximum number of unbilled UDRs:  Defines the maximum number of unprocessed Usage Detail Records required for Usage Services to be included in a Bill (Applies only for Normal and not Prepaid Subscriptions).

• Applicable on Billing Term Schemes (drill-down): Defines the Billing Term Schemes that the Subscriptions should follow, for the specified processing method to be applicable. Multiple Billing Term Schemes can be specified through the list.

A set of Rules/conditions which when satisfied override the default CRM.COM Credit Limit Rule, which blocks the execution of Events (Subscription Actions) if the customer's Credit Limit, as defined on their Accounts Receivable, is exceeded. i.e. if the Balance of the Accounts Receivable is greater than the Credit Limit.
If no Rules are defined, then the default behaviour is applied where Subscriptions cannot be activated unless the Balance of the Accounts Receivable is less than the Credit Limit of the Account.

The Override Credit Limit Rules determine the conditions required for Actions to override the Credit Limit Rule and be applied on Subscriptions.

Determines the conditions that should be fulfilled 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 (calculated using the number of X days that have lapsed) is more than or equal to this amount, the Subscription will not be activated.
• Account Balance
  If the actual Account Balance is more than or equal to this amount, the Subscription will not be activated.

The conditions are applicable for the following set of Events (more than one Event can be selected for each condition):

• 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 enforced whenever a Subscription goes into Resting. The Rules consist of the following:

• Allowed days in Resting per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in Resting per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days each time a Subscription goes into Resting.

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 for each Rule.

Determines the Rules that are enforced whenever a Subscription's Grace period is extended. The Rules consist of the following:

• Allowed days in Grace per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in Grace per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days each time a Subscription goes into Grace.

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 for each Rule.

Determines the Rules that are enforced whenever a Subscription or Subscription Service is Regretted. The Rules enforce the customers to Regret within a specificperiodaftertheSubscription, or the Service was activated. The Rules consist of the following:

• Allow Regretting a Subscription
  • Maximumperiodafter 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 for each Rule.

Determines the Rules that are enforced whenever a mandatory or optional Service is Swapped. The Rules enforce the customers to Swap Services only if a period after the date that the Subscription or the Service was activated has passed. The Rules consist of the following:

• Swap Type
  • Allow Service upgrading
  • Allow Service downgrading
  • Allow Service switching
• Minimumperiodbefore Swapping is allowed, starting from:
  Services can be Swapped after the selected date
  
  • Subscription Effective Date
  • Subscription Service Effective Date
  • Binding Start Date
  • Agreement Date
  • AVAILABLE FROM CRM.COM R11.0.0 Rated Up To Date
    
    

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 for each Rule.

Determines the Rules that are applied whenever a billable entity is Cancelled while not in binding. The Rules enforce the customers to notify the Service provider 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
  • Optional Subscription Service cancellation
• Cancellation notice: A period 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 for each Rule.

Determines the Rules that are applied whenever a billable entity is Cancelled while in binding. The Rules enforce 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
  • Optional Subscription Service cancellation
• Cancellation Type: A period 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 for each Rule. If no 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. The Rules consist of the following:

• Allowed days in short-term effective per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in short-term effective per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days each time a Subscription goes into short-term effective activation.

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 for each Rule.

Determines the Rules that are applied whenever a Subscription is deactivated for a short period. The Rules consist of the following:

• Allowed days in Short Term Not Effective per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Allowed times in Short Term Not Effective per year, starting from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days each time a Subscription goes into short-term deactivation

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 for 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.
• 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 of Accounts Receivable).
• Add Installed Item
  Expense Service is automatically added when a new Installed Itemisaddedon the Subscription through the Add Installed Item Action.
• Swap Installed Item
  Expense Service is automatically added when a new Installed Itemisaddedon 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 for the Expense Service to beaddedontheSubscription. Multiple conditions can be defined for each 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)

The Subscription Action Type that will be used while performing ADD EXPENSE Action on a Subscription.

The Subscription Sub Action Type that will be used while performing ADD EXPENSE Action on a Subscription.

Used to determine additional Billing directions to extend the System's default behaviour. 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.BydefaulttheSystem 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 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.

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

• Subscription Services
• Subscription Type
• Billing Term scheme