• Mandatory Fields must be defined
• Name, and Alternative Code must be unique

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

• Mandatory Fields must be defined
• Name, and Alternative Code must beunique

• Not Applicable

• Not Applicable

• Cannot be deletedifitsthe'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.

Determines whether the Stop Service step should be enabled by default when creating new Prepaid Billing Runs.

Determines whether the Start Service step should be enabled by default when creating new Prepaid Billing Runs.

This information determines the look ahead periodofthePrepaid Billing process when estimating the Consumption Date for a Subscription Service. 
This is available only if the estimation method is set to 'Re-estimate All' or 'Re-estimate Only Wallet with Changes'.

• 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 available choice is:

• Do not bill any period in advance

Rules to calculate the default 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 following settings are available:

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

The Subscription Action Type that will be used to start the necessary Services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Action Types related to the Start Service behaviour code exist.

The Subscription Sub-Action Type that will be used to start the necessary services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Sub-Action Types related to the Start Service behaviour code exist.

The Subscription Action Type that will be used to stop the Services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Action Types related to the Stop Service behaviour code exist.

The Subscription Sub-Action Type that will be used to stop the Services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Action Types related to the Stop Service behaviour code exist.

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.