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

• Mandatory Fields must be defined
• Name, and alternative code Alternative Code must be uniqueNot Applicable

• Only one Prepaid Billing Run Definitions can be 'Active' at any time

• Mandatory Fields must be defined
• Name, and alternative code must be uniqueAlternative Code must beunique

• Not Applicable

• Not Applicable

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

The recurrence settings which are applied on all Billing Runs which are classified as recurring, measured in hours, days, weeks, months or years.

It determines if the stop service Determines whether the Stop Service step should be enabled by default while when creating new Prepaid Billing Runs.

It determines if the start service Determines whether the Start Service step should be enabled by default while when creating new Prepaid Billing Runs.

This information defines determines the period to look ahead while the prepaid billing process is estimating the estimated consumption date for a specific subscription serviceperiodofthePrepaid Billing process when estimating the Consumption Date for a Subscription Service. 
This information is available only if the estimation method is set to re'Re-estimate all All' or re'Re-estimate only Only Wallet with changesChanges'.

• Period
• UOT: Measured in months or years

Defines the period that should be billed in advance, which is applicable only on pre-billed services. The supported options are the followingavailable choice is:

• Do not bill any period in advance

Rules on how to calculate the default bill as of day which is Bill As Of Day used by all Prepaid Billing Runs. Prepaid Billing Runs will default to this date unless a different date is specified. The settings consist of the followingfollowing settings are available:

• Starting from day: The day of the month that should be used in the Bill as of Date, As Of Date the first time (only) the first time that the Prepaid Billing Run will be is executed.
• Period after previous Periodafterprevious Billing Run: The date period is calculated based on a period after from the time since the previous Prepaid Billing Run, measured in hours, days, weeks, months or years.

The subscription action type Subscription Action Type that will be used to start the services that should be startednecessary Services.

Mandatory on Conditions: This is applicable and mandatory if subscription action types Subscription Action Types related to the start service Start Service behaviour code existsexist.

The subscription sub action type Subscription Sub-Action Type that will be used to start the necessary services that should be started.

Mandatory on Conditions: This is applicable and mandatory if subscription action types Subscription Sub-Action Types related to the start service Start Service behaviour code existsexist.

The subscription action type Subscription Action Type that will be used to stop the services that should be stoppedServices.

Mandatory on Conditions: This is applicable and mandatory if subscription action types Subscription Action Types related to the stop service Stop Service behaviour code existsexist.

The subscription sub action type Subscription Sub-Action Type that will be used to stop the services that should be stoppedServices.

Mandatory on Conditions: This is applicable and mandatory if subscription action types Subscription Action Types related to the stop service Stop Service behaviour code existsexist.

The maximum

(inclusive)

Wallet Balance necessary to stop each specific Service. For example, if the Threshold is set to 0 and the available amount for a

'Not Effective' Service is 0, then the

Service will be stopped. If the available amount for a

'Not Effective' Service is 1, then the

Service will not be stopped.