A behavior code denotes the type of behavior of an action that will be applied on subscriptions, such as addition of subscription service, removal of subscription service, addition of installed items etc.

A business classification code classifies the applied behavior into different categories and therefore giving a business meaning to the change that was applied and enabling additional process automation in the software such as billing, validations etc.

Settled subscriptions are the subscriptions related to accounts receivable with no amount in debt

Terminated subscriptions are the subscriptions that are no longer considered billable, that is, they are excluded by the billing engine as they were Regretted, Cancelled or Expired.

Effective Subscriptions are the subscriptions having services which are active, provisioned to the subscribers and charged by the billing engine.

 A physical good is a tangible commodity which is offered to customers, such as cameras, decoders, magazines etc. In most of the cases the customer has an exclusive ownership of the good that was purchased. Physical goods can be traceable or not traceable.

A service is an intangible commodity which is offered to customers, such as telephony, TV channels, repairs, installations, deliveries etc. In most of the cases the customer does not have an exclusive ownership of the service that was purchased but rather benefits from the service outcome. Services can be one off or recurring

Services that are provided upon customer request and are billed on a recurring basis, based on their usage

Services that are provided continuously and billed on a recurring basis, regardless of their usage

Subscription Distributors (also known as Subscription Provisioning Distributors) are mandatory for an effective subscription, however they are neither services nor hardware.
Distributors are used to:  

• Relate subscription services and subscription hardware to a specific Provisioning Provider, as CRM.COM offers integration with multiple Provisioning Providers.
• Define what services will be available from which device, if more than one device are available on a single subscription.
  For example if you would like to offer your customers the option to have more than one device on a single subscription, and then distribute different services on each device, then it is through the distributor that you would control, which services will be available from which device.

CRM.COM allows you to define discounted prices on services that will be provisioned via additional distributors
For more information visit /wiki/spaces/V4Manual/pages/9831566 

Provisioning Distributors can be created via one of the Provisioning Providers modules and must be added in the allowed distributors of a subscription type in order to be made available for selection, and are added on the Subscription when adding services and installed items to the subscription.

CRM.COM also allows you to use the same installed items (for example your box) for multiple providers.
In the case where you manage single subscriptions from multiple providers. For example Provider X will be used to provision the subscription with TV channels while Provider Y will be used for provisioning OTT services.
For more information visit Adding Single Installed Item to Multiple Distributors 

Each Subscription Action has a behaviour code and a business classification code

• A behaviour code denotes the type of behaviour that will be applied on subscriptions, such as addition of subscription service, removal of subscription service, addition of installed items etc.
• A business classification code classifies the applied behaviour into different categories and therefore giving a business meaning to the change that was applied and enabling additional process automation in the software such as billing, validations etc.

For example the business classification codes that could be set on a subscription action having a behaviour code removal of subscription service, would be:

• undo addition of subscription service
• regret subscription service
• cancel subscription service. 

Business classification code can be specified either by the user or the system.

Subscription action types and subscription sub action types provide the ability to set up different rules around subscription actions having the same behavior and business classification codes. Each subscription action type is related to a behavior code and consists of one or multiple subscription sub action types. Each subscription sub action type is related to a business classification code. Both subscription action types and subscription sub action types are configurable, and multiple subscription action types or subscription sub action types can be mapped to each behavior code or business classification code respectively.

Subscription action types and subscription sub action types are not mandatory in order to create and execute a subscription action. The behavior of the subscription actions depends entirely on the behavior and business classification codes; the subscription action types and subscription sub action types are taken into consideration only if they exist. Subscription action types and sub action types become mandatory only if the selected behavior code or business classification code are overridden by subscription action type or subscription sub action type configuration.

Subscriptions can be used for home usage or public usage. CRM.COM allows you to create a single subscription for public usage, for example used in restaurants or hotels, and bill the subscriber based on the number of concurrent usage of the services and a rate percentage which is agreed between the customer and the company providing those services.

The final rate is calculated based on the following formula

• Price Plan Rate * Number of concurrent Usage * Rate percentage amount / 100

Concurrent usage based pricing can be used only if it is supported by the related billing term scheme. In that case, both attributes are mandatory.

Subscription Life Cycle State History

A subscription life cycle state history determines the state of the subscription for a specific period of time.

• This information is used for reporting or troubleshooting purposes, but most importantly to determine if the subscription should be billed or not.
• No overlapping periods can exist for each subscription.
• An open period, representing the current state of the subscription, should always exist.

Subscription Service Life Cycle State History

A subscription service life cycle state history determines the state of the subscription service for that specific period of time.

• This information is used for reporting, troubleshooting but mostly for billing purposes. 
• Subscription service life cycle states history keep any required information based on which the related subscription services will be billed such as:
  • The period for which the service was in a specific state and whether this period is billable or not. 
• In order to bill a subscription service’s period, the history record will keep additional information such as:
  • Price Plansd 
  • Billing Terms
  • Accounts Receivable - DELETE. 
• No overlapping periods can exist for each subscription service state. 
• An open period, representing the current state of the subscription service, should always exist.

• Explicit Viewing Entity
• Account Based Entity

• Controlled Selection Access Entity

• Global Access Entity