Register a new subscription from scratch. The action is triggered when NEW is clicked from the Action Menu of subscription Data Entry or Summary page.

The subscription can be created in either a 'Draft' or an 'Effective' life cycle state.  If the state is 'Draft' then the subscription is created but not activated, i.e. signals are not transmitted to the subscriber.

Services physical goods price plans and billing term schemes allowed to be added to the subscription are filtered based on the subscription type.

Once you Submit the action, the system checks that the subscription account is active, and restriction and dependency rules defined for services, physical goods and subscriptions in the subscription type and billing definition are met.

If conditions are met a new subscription is created and related to the account. services and installed items are added to the subscription with their distributions. The subscription and services life cycle state is set to 'Draft' or 'Effective' according to how you submit the action.

A billing term that holds all the information related to the contact is created and set to 'Effective'.

Activate all 'Draft' and 'Not Effective' services of a subscription.
A subscription can be activated in two cases:

• When its life cycle state is 'Draft', i.e. the subscription was created but was never activated, or
• When the life cycle state is 'Not Effective', i.e. the subscription is disconnected due to unpaid Invoices. 

The action cannot be used, if some of the services are 'Draft' or 'Not Effective'. 'Start Service' action must be used.

Once you Submit the action the system checks that the subscription account is active, and restriction and dependency rules defined for services, physical goods and subscriptions in the subscription type and billing definition are met, while services must belong in the billing term scheme of the subscription.

If conditions are met subscription and subscription services life cycle state arw set to 'Effective'.

The following will be set on the Subscription Services according to business rules:

• • Billable Start Period
  • Billing Effective Date
  • Billing Directives.

Instantly billed if billing term scheme requires prepayment.

Performed Date can be set on a date in the past and the billing of the Service(s) will start based on the Performed date. Even though Performed date can be set on a date in the past, it must be after the Service was added on the Subscription as 'Draft'

Bill a normal subscription or preview the dates on which a prepaid subscription is estimated to be disconnected, based on the available amount of money present in the subscriber's wallet.

Action is available only if subscription is in one of the following life cycle states:

• Effective
• Not Effective
• In Resting
• Regretted
• Cancelled
• Short Term Effective
• Short Term Not Effective

Once you Submit the action, the system checks that the subscription account is active. and that the specified date is equal to or further than the date that the subscription is already billed. i.e the latest Rated To Date.

If validations are passed then

• Normal Subscriptions: the Subscription is billed, using the normal billing process, and information is supplied regarding the billed items.
• Prepaid Subscriptions: estimations for the consumption date are calculated using the Prepaid Billing Run process

'Bill as of Date' cannot be set for prepaid subscriptions.

Normal subscription's bills can be settled directly by using the QUICK PAY action once the bill is created.

Disconnect all effective subscription services.
Disconnection can optionally pause billing as well as stop the transmission of signals to the subscriber's TV, depending on the provisioning distributor of the services.

Action is available only if subscription is in 'Effective' life cycle state.

Once you Submit the action the system checks that the subscription account is active.

If validations are passed then the Subscription and services life cycle state is set to 'Not Effective'.

Billable period start dates and billing effective dates are set based on the billing term scheme.

Binding end and allowed cancel date extensions are applied based on the billing term scheme.

Billing directive is set based on the additional Billing directions, specified on the billing definitions.

Accord a number of days to a subscriber who might be behind in payments before disconnecting them or to reactivate their subscription if it has already been disconnected.
Subscription in Grace are billed normally and excluded from disconnection

• Effective
• Not Effective
• In Resting

Once you Submit the action, the system checks that the subscription account is active and Grace rules set in the billing definition are met

If validations are passed:

If the subscription is 'Not Effective' then it is activated by applying the following steps:

• The subscription and the subscription services life cycle state are set to 'Effective'.

• The subscription service period bill effective date, billable start period and billing directives are set according to the business rules

The subscription is updated with extend grace period information (such as grace period start and end dates).

Grace period history records are created for the subscription.

Binding end and allowed cancel date extensions are applied based on the billing term scheme

Cancel a subscriber's subscription and all of its services.

• Draft
• Effective
• Not Effective
• In Resting

Once you Submit the action, the system checks that the subscription account is active and 'Cancellation inside and outside binding' rules set in the billing definition are met.

If validations are passed subscription services and distributions are removed. and the subscription life cycle state is set to 'cancelled'.

Cancellation penalties are applied as specified on the 'active' billing term definitions.

Any actions scheduled after the cancellation are deleted.

• Draft
• Effective
• Not Effective
• In Resting

Once you Submit the action, the system checks that the subscription account is active and 'Regret period' rules set in the billing definition are met.

If validations are passed subscription services and distributions are removed. and the subscription life cycle state is set to'regretted'.

Any actions scheduled after the regret are deleted.

Temporarily activate a subscription and its services before proper activation, without charging the subscriber for the activated period. 

Subscriptions in Short Term Activation can be deactivated automatically when the Short Term Activation end date is reached or through the Subscription Action End Short Term Subscription Activation.

Action is available if the subscription is in one of the following life cycle states: 

• Draft 
• Not Effective 

Once you Submit the action, the system checks that the subscription account is active. If the action is scheduled by using a value for the specific date or specific number of days, the Short Term Activation End Date must be greater than scheduled date.

The short term activation rules specified on the billing definitions, should be met

If validations are passed the life cycle state of all subscription and all its services which are in a 'draft' or 'not effective' is set to 'short term effective'. Bill effective date, billable start period and billing directives are set according to the business rules.

Instantly billed if billing term scheme requires prepayment.

Before submitting you must select when the short term activation should end:

• ON A SPECIFIC DATE: The date must be greater than the current date. 

• AFTER A SPECIFIC NUMBER OF DAYS: The value must be an integer greater than 0.

Deactivate subscriptions that were activated using Short Term Subscription Activation action and which the subscriber wishes to deactivate earlier than planned.

Action is available if the subscription is in a 'Short Term Effective' life cycle state.

Once you Submit the action, the system checks that the subscription account is active.

If validations are passed the subscription and services life cycle state is set to 'not effective'.Bill effective date, billable start period, and billing directives are set according to business rules.

The short term activation life cycle state period is updated by setting the end short term activation action as that which ended the period.

Temporarily deactivate a subscription for a short period and automatically reactivate.

Action is available only if the subscription is in a 'Effective' life cycle state.

Once you Submit the action, the system checks that the subscription account is active and that the short term deactivation rules defined in the billing definition are met.
If the action is scheduled by using a value for the specific date or specific number of days, the Short Term Deactivation End Date must be greater than scheduled date.

If validations are passed the life cycle state of the subscription and its services which are in a 'draft' or 'effective' life cycle state are set to 'short term not effective'. The subscription service life cycle state, bill effective date, billable start period and billing directives are set according to the business rules.

Before submitting you must select when the short term deactivation should end:

• ON A SPECIFIC DATE: The date must be greater than the current date. 

• AFTER A SPECIFIC NUMBER OF DAYS: The value must be an integer greater than 0.

Action is available only if the subscription is in a 'Short Term Not Effective' life cycle state.

Once you Submit the action, the system checks that the subscription account is active.

If validations are passed the subscription and subscription services life cycle state is set to 'effective' or 'not effective' according to the credit limit status of the customer. The short term deactivation life cycle state period is updated by setting the end short term deactivation action as that which ended the period.

Billable period start dates and billing effective dates are set based on the billing term scheme.

Binding end and allowed cancel date extensions are applied based on the billing term scheme.

• Effective
• Not Effective

Once you Submit the action, the system checks that the subscription account is active and that the resting rules defined in the billing definition are met.
If the action is scheduled by using a value for the specific date or specific number of days, the Resting End Date must be greater than scheduled date.

If validations are passed then life cycle state of the subscription and its services is set to 'in resting'.

Billable period start dates and billing effective dates are set based on billing term scheme.

Billing directive is set based on the additional billing directions specified on the billing definition.

You can setup rules in the billing term scheme to extend the contact dates by the number of days the subscription is resting.

Before submitting you must select when the resting should end:

• ON A SPECIFIC DATE: The date must be greater than the current date. 

• AFTER A SPECIFIC NUMBER OF DAYS: The value must be an integer greater than 0.

Force a subscription out of a resting earlier than initially scheduled.

Action is available if the subscription is in an 'In Resting' life cycle state.

Once you Submit the action, the system checks that the subscription account is active.

If validations are passed then if the subscription and the services were 'effective' prior to resting, the system validates whether the subscription can become 'effective'. If it cannot, then the subscription and its services will be set to 'not effective', based on the activation conditions set in the 'active' billing definition.

Billable period start dates and billing effective dates are set based on the billing term scheme.

Binding end and allowed cancel date extensions are applied based on billing term scheme.

Instantly billed if billing term scheme requires prepayment.

Subscription that come out of resting will either be activated or dactivated depending on the activation conditions.  For example, if the amount of debt of the customer exceeds that allowed by the business threshold then the subscription is set as Not Effective.

Use to transfer the subscription from one account owner to another.

You can use an existing account or create a new one .  

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

Once you Submit the action the system checks the following:

• Unrated or not billed services don't exist.
• The new accounts should belong to a separate customer.
• The subscription should be owned by an active accounts
• Subscription restrictions defined at the billing definition are observed

If validations are passed a new accounts receivable is created (if new is specified).

A new contact information is created (if new is specified).

The accounts receivable related with the subscription is replaced with the new one.

A new billing address is created or the current one is updated.

A new subscription location is created or the current one updated.

Use the to change the subscription's account, to another one belonging to the same subscriber (i.e., to change the account that will be billed for the Subscription).

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

If validations are passed a new accounts receivable is created (if new is specified).

A new contact information is created (if new is specified).

The accounts receivable related with the subscription is replaced with the new one.

A new billing address is created or the current one is updated.

A new subscription location is created or the current one updated. 

Use when the contract needs to be re-adjusted to either start sometime in the future or moved to the past. The action resets both the Binding Start and End date of the contract.

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective
• In Resting

Action is not allowed if another scheduled 'Amend Billing Terms' action exists. You are allowed to schedule the action only after the execution of the scheduled action.

Once you Submit the action the system checks that billing term amendment rules defined in the billing term scheme are met.

If validations are passed the binding start and binding end dates are adjusted by a common period of time.

Adjust By: You can adjust using either positive or negative number (to the future or the past).

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective
• In Resting

Action is not allowed if another scheduled 'Amend Billing Terms' action exists. You are allowed to schedule the action only after the execution of the scheduled action.

Once you Submit the action, the system checks that billing term amendment rules defined in the billing term scheme are met.

If validations are passed a new billing term (the customer's contract) instance with no binding terms, which replicates the previous one is created and activated. The existing billing term is replaced and set it to 'inactive'.

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective
• In Resting

Action is not allowed if another scheduled 'Amend Billing Terms' action exists. You are allowed to schedule the action only after the execution of the scheduled action.

Once you Submit the action, the system checks that billing term amendment rules defined in the billing term scheme are met.

If validations are passed a new billing term instance which replicates the previous one is created and activated.

The binding end date is extended by a number of days while the binding start date remains the same.

Existing billing term is replaced and set to 'inactive.'

• Extend By: As only the Binding can be extended, only positive values can be used.
• Binding End: Set to the date on which the contract will expire (Read-only). It will be automatically calculated based on the current Binding End and the Extend By value.

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective
• In Resting

Action is not allowed if another scheduled 'Amend Billing Terms' action exists. You are allowed to schedule the action only after the execution of the scheduled action.

Once you Submit the action the system checks that billing term amendment rules defined in the billing term scheme are met.

If validations are passed a new billing term instance which replicates the previous one and has identical binding terms is created and activated.

The existing billing term is replaced and set to 'inactive'.

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective
• In Resting

Action is not allowed if another scheduled 'Amend Billing Terms' action exists. You are allowed to schedule the action only after the execution of the scheduled action.

Once you Submit the action the system checks that billing term amendment rules defined in the billing term scheme are met.

If validations are passed a new billing term instance which replicates the previous one and has identical binding terms is created and activated.

The binding start date is set to the date of execution and the binding end date is set equal to the binding start date plus the binding period.

The existing billing term is replaced and set to 'inactive

Agreement Date: Regardless of the Agreement Date, the Binding Start will be set to the date of the execution. The Agreement Date only defines the date on which the contract was signed.

• Billing Term Scheme
• Billing Frequency
• Price Plan
• Binding Period
• Binding Start
• Binding End
• Concurrent Usage
• Concurrent Usage Rate Percentage

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective
• In Resting

Action is not allowed if another scheduled 'Amend Billing Terms' action exists. You are allowed to schedule the action only after the execution of the scheduled action.

Once you Submit the action the system checks that billing term amendment rules defined in the billing term scheme are met.

If validations are passed a new billing term instance which replicates the previous one and has identical binding terms is created and activated.

The existing billing term is replaced and set to 'inactive'.

On switching from prepaid post-rated to prepaid pre-rated billing term scheme the system checks that there are enough funds in the wallet to cover the service which is charged by the next scheduled prepaid billing run.

On switching from prepaid pre-rated to prepaid post-rated billing term scheme no billing actions are applied. The services that changed from pre-rated to post-rated will be credited for the period that was billed in advance and will be billed again through the next scheduled prepaid billing run. The period to be credited will start from the date after the action was executed up to the date that the service was billed in advance.

Instantly billed if the subscription changes to a normal billing term scheme that requires prepayment.

The following fields are only visible and available for selection if certain conditions are met:

• Binding Period: Billing Term Scheme is Normal
• Binding Start: Billing Term Scheme is Normal
• Concurrent Usage: Billing Term Scheme supports concurrent usage.
• Concurrent Usage Percentage: Billing Term Scheme supports concurrent usage

Use to change the subscription address, which indicates the physical address where the services are received. The action can be used to:

• Create a new address and define it as the subscription address
• Change the subscription address to an existing address
• Change address details of existing subscription address
• Assign the billing address as the subscription address

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

Use to select and apply one of the pre-configured discounts to the subscription.

For more information view Additive Discounts

Use to provide subscribers with the possibility to be billed for a period longer than that of their normally contracted billing frequency or prepaid/pre-rated period, in exchange for a discount.

Billing Frequency applies to Subscriptions with Normal Billing Term Schemes and Prepaid / Pre-rated period applies for Subscriptions with Prepaid Billing Term Schemes. 

For more information view Buy in Advance

Buy in advance definition must be configured.

No other 'Effective' or not billed Buy in Advance request exists for the specific Subscription.

If the subscription has a Prepaid Billing Term Scheme, at least one pre-rate subscription service must exist.

Once you Submit the action the system checks that the specified duration is within one of the settings defined in the Buy in Advance Definitions.

For normal subscriptions the specified duration is more than the existing billing frequency of the Subscription and for prepaid subscriptions the specified duration is more than the existing pre-rated period of at least one of the Subscription services. If the request is submitted

If the request is for a specific subset of prepaid pre-sated subscription services in which case the specified duration must be more than the maximum pre-rated period among all of the selected services bought in advance.

• The submitted Buy In advance Request keeps track of the selected pre-rated Services defined. If no specific pre-rated Services are defined, then the submitted Buy in Advance request will be applied on all of the pre-rated Services.

Use to assign or switch subscription services and installed items to a different provisioning distributor or if the existing distribution must be cancelled.

When you use the action on a service you can

• Move a service which is already distributed to another distributor
  OR  
• Enable the distribution of a device with no distribution to an existing distributor
  OR 
• Remove distribution of service from its related Distributor.
  
  

When you use the action on an installed item

• Move an installed item which is already distributed to another distributor 
  OR 
• Enable the distribution of an installed item with no distribution to an existing distributor 
  OR 
• Remove the distribution of an item from its related distributor.

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

Once you Submit the action the system will check that restrictions and dependencies on services and installed items set on the billing definition are met.

If validations are passed then related provisioning distributors are added if not already there.

The initial distribution of the specified installed item or service is removed if an installed item's distribution change was specified.

The installed item and/or service are distributed to the new distributors, as long as they are specified.

The new subscription provisioning distribution record is marked as 'not initialised'.

The new subscription provisioning distribution record is marked as 'not authorised.

Instantly billed if billing term scheme requires prepayment.

Use Enable and Disable Links to add or remove services and Installed Items from and to Provisioning Distributors.

Use to provide alias names to provisioning distributors used by the subscription. For example, if a subscriber  labels Twin 1 distributor as Master Bedroom and has the Gold service and a Roku box distributed to the Twin 1 then the following is displayed wherever the distributor is shown:

• Gold  - Master Bedroom (Twin 1)
• Samsung Decoder - Master Bedroom (Twin

Use to amend a subscription by adding or removing termed services and /or installed items or amending distribution of either of the 2.

Allowed only if subscription life cycle state is not or will not be equal to draft or cancelled

This action is applicable only if the subscription type is classified as "Flexible selection of services"

Once you Submit the action the system checks that subscription type, billing definition and provisioning provider rules, restrictions and dependencies are not violated

If validations are passed and according to what you use the action for the system executes the same things as in the following actions

• Add service
• Remove service
• Add installed item
• Remove installed item
• Change subscription distribution 

Scheduling is allowed only if the subscription's life cycle state is not 'draft' or scheduled to be cancelled during that period of time.

If the action is used to add new installed items then it cannot be scheduled.

Instantly billed if billing term scheme requires prepayment.

Use to add termed services (services charged on a recurring basis) whose activation must be done at a later stage. services that should be activated directly (i.e., those ready to be billed) should be added as 'Effective', using the Add Service as Effective action. You can also use the action to add Installed Items.

Action is available if the subscription is in one of the following life cycle states:

• Draft

• Effective

• Not Effective

• In resting

Only services, distributors and physical goods allowed by the subscription type and billing term scheme are available for selection.
Services and physical goods are further filtered by the selected distributor.
The installed items available to be added are as defined in the active inventory management definition.

• Activate
• Deactivate
• Short term deactivation
• Terminate
• Rest

If validations are passed then draft services and distributors are added to the subscription and billing dates are set according to the rules.

If installed items are added then they are added along with their distributors to the subscription, removed from the warehouse using a stock out warehouse transaction and the installed item history is updated.

Action is available if the subscription is in an 'Effective' life cycle state.

Only services, distributors and physical goods allowed by the subscription type and billing term scheme are available for selection.
Services and physical goods are further filtered by the selected distributor.
The installed items available to be added are as defined in the 'Active' inventory management definition.

Once you Submit the action the system checks that subscription type and billing definition rules are met.

If any of the following actions is also scheduled for the subscription then the new service cannot be added before the scheduled date:

• Activate
• Deactivate
• Short term deactivation
• Terminate
• Rest

Service and installed items dependencies and restrictions defined on the subscription type are observed.

If validations are passed then effective services and distributors are added to the subscription and billing dates are set according to the rules.

If installed items are added then they are added along with their distributors to the subscription, removed from the warehouse using a stock out warehouse transaction and the installed item history is updated

Instantly billed if billing term scheme requires prepayment.

The Performed Date can be set in the past (it must be after the service was added on the subscription as 'Draft') and the billing of the service(s) will start on that date.

The subscription is in one of the following life cycle states:

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

Only expenses allowed by the subscription type and billing term scheme are available for selection.

If validations are passed then the expense is added on the subscription and set as 'Effective'

Its bill effective date, billable start period and billing directive are set according to the business rules.

Instantly billed if billing term scheme requires prepayment.

The same expense can be added as many times as necessary.

Expenses can also be automatically added to a subscription through the execution or scheduling of another subscription action, provided pre-defined conditions are met. For more information, refer to the POLICIES section in billing definitions. 

Use this action to add usage services (services charged based on their usage, such as movies, telephone logs or games) ordered by a subscriber. The available usage services are defined in the 'Usage Service Catalogs' unlike the rest of the services that are defined as products..

A termed service may have to be selected as a prerequisite (depending on the configuration of the 'termed service requirements' in the usage service catalog), with a life cycle state not

• Draft
• Not Effective 

• Cancelled
  
  

Usage Service Catalogs are filtered on the following conditions:

• Catalog is 'Effective;
• Catalog is valid during the period that the action is scheduled to be executed
• provisioning provider of the catalog (if one is defined) is the same as at least one provisioning provider of the selected termed service
• Subscription conditions defined on the catalog are fulfilled
• accounts receivable conditions specified on the catalog are fulfilled
• The user adding the service belongs to one of the allowed organisational units defined on the catalog

If a catalog is specified, then the available usage services are filtered based on the services included in that catalog.

If a catalog is not specified, then the available usage services are filtered based on the services included in all the available catalogs (considering the usage service catalog filtering logic described above)

Once you Submit the action the system checks that the subscription is owned by an active account.

Once the action is executed, provisioning signals are sent to the subscriber's device to enable the ordered item, and a 'UDR' is created in the system and  billed immediately or in the next Billing Run.

For prepaid subscriptions usage service orders are always billed instantly and if there are no funds available in the subscriber's wallet , then the service cannot be added.

For normal subscriptions usage service orders are billed according to the configuration of 'Usage Service Billing Rules' set in the billing term scheme. 

Instantly billed if billing term scheme requires prepayment.

When an action whose scheduling Information set to NOW is submitted, both the submitting and executing steps take place directly.

When an Action is submitted as scheduled then only the submitting step takes place. The execution step takes place once the scheduled Action is executed.

On submitting the subscription action:

A UDR is created for each submitted usage service with the information defined in the action. If the action is scheduled the UDR is created as scheduled. Otherwise the UDR is created as 'Posted'.

• Billing effective date is set equal to the date on which the Action is scheduled to be executed
• Billing Directive is set to 'To Be Billed'

On executing the Subscription Action:

• Service provisioning distributions are created based on the selected termed subscription service and provisioning distributor
• Provisioning commands are sent to the related provisioning provider to enable the signal. provisioning commands are sent directly
• Usage services are rated and billed if they should
• If the action was scheduled then the UDR is updated to 'Posted'

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective (if Service that are'Not Effective' are present)
• Not Effective

The subscription services are in one of the following life cycle states:

• Draft
• Not Effective

The subscription services that will become 'Effective' must be allowed by the subscription type, billing term scheme and provisioning distributor. 

Once you Submit the action the system checks that the subscription is owned by an active account.
If any of the following actions is scheduled, the service can only be activated after the scheduled date:

• Activate
• Deactivate
• Short Term Deactivation
• Terminate
• Rest

Service and installed items dependencies and restrictions defined on the subscription type are observed.

If validations are passed then the service is set as effective.

Instantly billed if billing term scheme requires prepayment.

The Performed Date can be set in the past (it must be after the service was added on the subscription as 'Draft') and the billing of the service(s) will start o

Subscription life cycle state is set to 'Effective' if is in a 'Draft' or 'Not Effective' state and the life cycle state of the subscription services is set to 'Effective'.

Billable period start date, billing effective date, binding end and allowed cancel date extensions are set based on the billing term scheme.

Billing directive is set based on the billing directives specified in the 'Active' billing definition

Action is available only if the subscription service is in an 'Effective' life cycle state.

Service and installed items dependencies and restrictions defined in the subscription type are observed.

If the validations are passed the subscription life cycle state is set to 'Not Effective' if no other 'Effective' services exist and the service life cycle state to 'Not Effective'

Binding end and allowed cancel date extensions are applied based on the billing term scheme. 

Billing directive is set based on the billing directives specified in the 'Active' billing definition.

The action can be applied to all or to a selection of subscription services.

Use to change an existing subscription termed service to a different one. There are three available swapping classifications:

• Upgrade (Swapping to a more expensive package)
• Downgrade (Swapping to a cheaper package)
• Switch (Swapping to a package of the same price)

The system distinguishes between swap classification on submitting the action without the need of user assistance. If a Classification is selected by the agent, then available services will be filtered based on it.
Tiers defined in the 'Active' subscription definition, determine the filtering and choice of swap classification.

The action is available if subscription service is in one of the following life cycle states

• Draft
• Effective
• Not Effective

The available services to swap are the ones allowed by the subscription type, billing term scheme and provisioning distributor.

The available services to swap to follow the Tier rules specified in the subscription type

Once you Submit the action the system checks that the subscription is owned by an active accounts receivable.

Service and installed item dependencies and restrictions defined in the  subscription definition type are observed as well as the service swap rules defined in the billing definition

If validations are passed then the new subscription services are added together with the related provisioning distributors, if not already there.

The removed subscription services are removed together with their distribution.

The life cycle state of the added service is set equal to the life cycle state of the removed one.

The life cycle state of the removed service is set to 'Swapped', and the initial life cycle state Period is 'Closed'.

Billable start period and billing effective date are set based on the billing term scheme.

Billing directive is set based on the active billing definition.

Instantly billed if billing term scheme requires prepayment.

If there are multiple lever of tiers in the subscription definitions, then when selecting a mandatory service belonging to a leading tier to switch to, optional subscription services (if any) following the same tier will be displayed.

Action is available if the subscription is in one of the following life cycle states:

• Draft
• Effective
• Not Effective

and only for subscriptions that already have at least one service of type Flexible Bundle.

Once you Submit the action the system checks that bundle service composition rules defined at the Product are met.

If validations are passed then subscription service components are either added or removed along with their related provisioning distributions.

For removed subscription service components the subscription service life cycle state is set to 'Removed' while for added it is set equal to the life cycle state of the bundled service.

Instantly billed if billing term scheme requires prepayment.

Use MODIFY to open the modal and select components.

Use VIEW PRODUCT BUNDLE COMPOSITION link to see the allowed composition structure.

Use product, product type and product family filters to filter the available service components.

Use SELECT to add a new component to the bundle.

Use REMOVE to remove an existing or a newly added component to the bundle.

Action is available if the subscription is in one of the following life cycle states:

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

The expense is not already billed.

The expense has not already been cancelled.

The expense life cycle state is set to 'Cancelled'.

If the expense is rated (but not billed), related rated billing items are cancelled.

Use this action when a termed service is no longer required by the subscriber and they wish to cancel it. The time by which a service can be cancelled and whether penalties are applied, depends to your business rules. 

The Cancel Service action is a child of the Cancel Subscription action where the former cancels specific services while the latter cancels all services. Refer to billing definition for more information on validations and penalties that can be applied on the Cancel Service and Cancel Subscription Actions.

Action is available if the subscription service is in one of the following life cycle states:

• Effective
• Not Effective
• In resting
• Short Term Effective
• Short Term Not Effective

Once you Submit the action the system checks that the subscription is owned by an active account.

Service and installed item dependencies and restrictions defined in the subscription type must be met.

Cancellation outside or during binding rules, defined in the 'Active' billing definition are observed. 

If validations are passed services and provisioning distributors that are no longer distributing any subscription services or installed items are removed.

Service life cycle state is set to 'Cancelled' and subscription life cycle state is set to 'Not Effective' if no other services exist.

Cancellation penalties are applied as specified on the billing definition.

Any actions scheduled for after the cancellation are deleted.

Use this action to remove a termed service, soon after it was added due to customer regretting.

The action can also be used to regret a Service swap. i.e., use it if a subscriber recently changed their service from P1 to P2 and would like to return to P1. 

Regret Service action is a child of the Regret Subscription action where the former regrets specific services while the latter regrets all the services of the subscription.

• Effective
• Not Effective
• In resting
• Short Term Effective
• Short Term Not Effective

Once you Submit the action the system checks that the subscription is owned by an active account, and the service dependencies and restrictions defined in the subscription type must be met. Regret rules defined in the billing definition must also be met.

If validations are passed then services and provisioning distributors that are no longer distributing any subscription services or installed items are removed.

Service life cycle state is set to 'Regretted' and subscription life cycle state is set to 'Not Effective' if no other services exist

If the subscription services to be regretted were added by the swap subscription service process, then the previous subscription service is restored with its former (pre-swap) attributes.

Billable period start date and billing effective date are updated based on the billing term scheme.

Any actions scheduled for after the cancellation are deleted.

Action is available if the subscription is in one of the following states:

• Draft
• Effective
• Not Effective
• In resting
• Short Term Effective
• Short Term Not Effective

and subscription services are in a 'Draft' life cycle state.

When the action is execute services and provisioning distributors that are no longer distributing any subscription services or installed items are removed.

Subscription service life cycle state is set to 'Removed'.

Any actions scheduled for after the cancellation are deleted.

Use to add traceable physical goods to a subscription such as decoders smartcards, modems, or telephones, which may be required for its operation.
For example, a customer subscribed to an internet service will need a modem in order to receive that service. 

The action is available if the subscription has one of the following life cycle states:

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

Physical goods that can be selected must be allowed by the subscription type and the provisioning provider of the selected distributor.

The installed items available to be added are as defined in the active inventory management definition.

You cannot add a new item, if there is a 'New Subscription Job' related to this subscription which is not 'Cancelled' or 'Completed'.

Once you Submit the action, if the subscription is effective then the system checks the installed item restrictions and dependencies defined on the billing definition.

If validations are passed then the installed items are distributed to their related distributors, removed from the warehouse using a stock out warehouse transaction and the installed item history is updated.

For more information on adding Installed Items using the action follow the links below:

• Adding Fixed bundle Installed Items
• Adding Single Installed Item to Multiple Distributors

Use to remove an installed item from a subscription in case the subscription is cancelled or regretted, or the item is no longer necessary.

Action is available if the subscription is in one of the following life cycle states:

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

Once you Submit the action the system checks that the subscription is owned by an active account and that a valid warehouse to store the removed item exists, as defined in the active inventory management definition exists.

If the subscription is effective then the system checks the installed item and service restrictions and dependencies defined on the subscription type and subscription restrictions defined on the billing definition.

If validations are passed then if the installed item was rented then it's added back to a warehouse as specified in the active inventory management definition using a 'stock in' warehouse transaction and installed items history is updated. If the item was sold it will be removed from the subscription and remain in the account as an asset,

Action is available if the subscription is in one of the following life cycle states:

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

The installed items available to be added are as defined in the active inventory management definition.

Once you Submit the action the system checks that the subscription is owned by an active account and that a valid warehouse to store the removed item exists, as defined in the active inventory management definition exists.

If the subscription is effective then the system checks the installed item and service restrictions and dependencies defined on the subscription type and subscription restrictions defined on the billing definition.

If validations are passed then new installed items are distributed accordingly, and removed from the warehouse using a 'stock out' warehouse transaction and installed items history is updated.
Existing installed items: If the installed item was rented then it's added back to a warehouse as specified in the active inventory management definition using a 'stock in' warehouse transaction and installed items history is updated.

When swapping an installed item related to a fixed product bundle you have 2 options:

• Swap the whole bundle with a new one. Refer to Swap Bundle
• Swap a component of the bundle with another Installed Item (that will be of the same type). Refer to Swap Component

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

Installed items exist on the subscription.

There are more than one subscriptions related to the account.

If either the source or target subscription is 'Effective' then restrictions and dependencies set on the subscription type must be met.

 The installed items and distributors must be allowed by the target's subscription type..

If validations are passed then the installed item is removed from the source subscription and added to the target subscription and distributed accordingly. The installed item history is updated by specifying the source subscription and the subscription to which the installed item is moved.