• Multiple Billing Term Subscription definitions Definitions can exist in the systemSystem, but each one should have a unique name and alternative codeName and Alternative Code.
• Only one active Billing 'Active' Billing Term Subscription  definition Definition can exist at any given time.

• If no active Billing 'Active' Billing Term Subscription definition Definition exists, then no Billing Term Subscription can be created.

• Mandatory Fields must be defined.
• Name and alternative code Alternative Code must be unique.

• Not Applicable

• Mandatory Fields must be defined.
• Name and alternative code Alternative Code must be unique.

• Not Applicable

• Not Applicable

• Cannot be deleted if its the active definitiondeletedifitsthe'Active' Definition.

It determines Determines the type Type of billable entities on which the billing term definitions Billing Term Definitions will be applied on. In this case, the classification Classification is set to Subscriptions.

Determines the rules Rules that are applied during billing term amendmentsBilling Term Amendments. The rules 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 Billing Term Schemes that the subscriptions should be following in order Subscriptions should follow, for the specified processing method to be applicable. Multiple billing term schemes Billing Term Schemes can be specified through that list.

Exceptions on specific users Users or units Units can also be defined per for each ruleRule.

Determines the rules Rules that are applied during prepaid billing runsPrepaid Billing Runs. The rules Rules consist of the following:

• Restrict the debiting wallets of Wallets with balance a Balance less than the stop service Stop Service threshold: If enabled then the prepaid billing run Prepaid Billing Run will debit wallets for just Wallets up to the remaining amount and not below thatBalance (not more). For example, if the wallet balance Wallet Balance is €10 , and the stop service Stop Service threshold is 0, and this rule 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 a Prepaid Billing Run for €15 will result in a Wallet Debit TransAction for €10 and not €15 euros, resulting to in a wallet balance Wallet Balance of €0 euros. If this rule the Rule is not enabled, then the wallet debit transaction Wallet Debit TransAction will be created for the amount of €15 euros, resulting to a wallet balance in Wallet Balance of - 5 euros€5.
• The disconnection threshold can be configured in the Prepaid Billing Run Definition under Stop Service Tab which becomes available only if once enabled .

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

Determines the rules Rules that are applied when there are changes in price plans whentherearemodificationinPrice Plans which are already used in billing termsBilling Terms. The rules 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 Billing Term Schemes that the Subscriptionsshouldfollowforthe specified processing method to be applicable. Multiple billing term Billing Term schemes can be specified through that list.

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

• Status
  colour Red title Applicable up to R9

  Processing Method (radio button): Defines if the usage services Usage Services should be processed and billed immediately on submitting when submitted them or if they should be billed by the billing run Billing Run process. The supported values are the following:
  • Billing run Run process (the default option)
  • Immediately after execution

• Status
  colour Green title Available from CRM.COM R10.0.0

  Maximum un-billed unbilled amount threshold: Defines the maximum rated total amount of among all usage services Usage Services that needs to be reached in order for them to be included in a bill. Bill (Applies only for Normal Subscriptions and not Prepaid Subscriptions).

• Status
  colour Green title Available from CRM.COM R10.0.0

  Maximum number of un-billed unbilled UDRs:  Defines the maximum number of unprocessed Usage Detail Records required in order for Usage Services to be included in a bill. Bill (Applies only for Normal Subscriptions and not Prepaid Subscriptions).

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

A set of rules which, if met, Rules/conditions which when satisfied override the default CRM.COM Credit Limit Rule of CRM.COM, which does not allow any of the events, blocks the execution of Events (Subscription actionsActions) to be executed if the customer's Credit Limit of the customer, as defined on their Accounts Receivable, is exceeded. i.e. if the balance Balance of the Accounts Receivable is greater than the Credit Limit.
If no rules Rules are defined, then the default behaviour of exceeding Credit Limit is applied and no where Subscriptions can cannot be activated unless the balance 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 .

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 in order for a subscription Subscription or a subscription service Subscription Service to become effective'Effective'. The condition set includes the following:

• Billing term schemeTerm Scheme
• Financial account classificationAccount Classification
• Credit ratingRating
• Outstanding Amount Less Than
• Outstanding for Less than x daysThan X Days
  If the actual  Due Due amount (due is calculated based on the x days agousing the number of X days that have lapsed) is more than or equal than the figure provided here, then the subscription to this amount, 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 to this amount, the Subscription will not be activated.

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

• Become effective subscriber
• Subscription activation
• End subscription restingSubscription Resting
• Subscription service Service start
• Service upgrade
• Service downgrade
• Service swapSwap
• Add service usageService 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 Rules that are applied enforced whenever a subscription Subscription goes into restingResting. The rules Rules consist of the following:

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

The rules Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each ruleRule.

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

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

The rules Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each ruleRule.

Determines the rules Rules that are applied enforced whenever a subscription Subscription or subscription service Subscription Service is regrettedRegretted. The rules are enforcing Rules enforce the customers to regret Regret within a specific period of time after the subscription specificperiodaftertheSubscription, or the service Service was activated. The rules Rules consist of the following:

• Allow regretting Regretting a subscriptionMaximum period after subscription Subscription
  • Maximumperiodafter Subscription effective date, agreement date or binding start date, measured in days, weeks, months or years.
• Allow regretting Regretting a mandatory subscription serviceSubscription Service
  
  • Maximum period after subscription service Subscription Service effective date, agreement date or binding start date, measured in days, weeks, months or years
• Allow regretting Regretting an optional subscription serviceSubscription Service
  
  • Maximum period after subscription service Subscription Service effective date, agreement date or binding start date, measured in days, weeks, months or years

The rules Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each ruleRule.

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

• Swap Type
  • Allow service Service upgrading
  • Allow service Service downgrading
  • Allow service Service switching
• Minimum period of time before swapping Minimumperiodbefore Swapping is allowed, starting from 
  Subscription Effective Datefrom:
  Services can be swapped after Subscription Effective DateSwapped after the selected date
  
  • Subscription Service Effective Date
  • Services can be swapped after Subscription Service Effective DateBinding start dateServices can
  • be swapped after Binding Start Date Agreement Date
  • Services can be swapped after Agreement Date Date

  • Status
    colour Yellow title 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 ratedTo Date
    
    

The rules Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each rule. This type of rules are configured separately for mandatory and optional servicesRule.

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

• Cancellation typeType: 
  
  • subscription Subscription cancellationmandatory subscription service
  • Mandatory Subscription Service cancellation
  • optionally subscription service Optional Subscription Service cancellation
• Cancellation notice: A period of time before cancellation, which can be measured in days, weeks, months and years

The rules Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each ruleRule.

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

• Cancellation typeType:
  • subscription Subscription cancellationmandatory subscription service
  • Mandatory Subscription Service cancellation
  • optionally subscription service Optional Subscription Service cancellation
• Cancellation typeType: A period of time before the binding end Binding End date or the allowed cancellation date, which can be measured in days, weeks, months and years

The rules Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each ruleRule. If not rules no Rules are specified or applied then cancellations while in binding are not allowed.

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

• Allowed days in short-term effective per year, starting either 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 either from one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days in short term effective per each time

• days each time a Subscription goes into short-term effective activation.

The Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling Term Schemes. Exceptions on specific users Users or units Units can also be defined per for each ruleRule.

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

• Allowed days in short term not effective Short Term Not Effective per year, starting either 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 Short Term Not Effective per year, starting either from thefrom one of the following dates:
  • First day of year
  • Subscription effective date
  • Billing start date
  • Agreement date
• Minimum and maximum days in short term not effective per each time

• days each time a Subscription goes into short-term deactivation

The Rules can be applied either on all billing term schemes Billing Term Schemes or only on specific billing term schemesBilling 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)

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 Billing directions to extend the default behavior of the systemSystem's default behaviour. Additional billing Billing direction consist of the following:

• Additional Billable Subscription Service Life Cycle States: Billable subscription service life cycle states Subscription Service Life Cycle States are used to determine which subscription service life cycle state history Subscription Service Life Cycle State History periods are billable or not. By default the system considers “Effective” and ".BydefaulttheSystem considers 'Effective' and 'Short Term Effective" ' periods as billable, but this can be extended by defining additional billable subscription service life cycle statesSubscription 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)

• • Binding State (in binding / out of binding)

• Additional Non Creditable -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 Subscription Service Life Cycle State History Periods should never be refunded (i.e. credited). By default, the system System considers “Effective”'Effective', "'Short Term Effective" ' and “Draft” 'Draft' periods as non-creditable, but this can be extended by defining additional non creditable subscription service life cycle states-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)

, which include the following:

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

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

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

• subscription services
• subscription type
• billing term Subscription Services
• Subscription Type
• Billing Term scheme