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

• If no active Normal Billing Run definition exists, then no Normal Billing Run can be created

• Mandatory Fields must be defined
• Name and alternative code must be unique

• Not Applicable

• Mandatory Fields must be defined
• Name and alternative code must be unique

• Not Applicable

• Not Applicable

• Cannot be deleted if its the active definition

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

• One billing frequency period ahead
• One billing frequency period ahead minus the post bill prorated period

Rules on how to calculate the default bill as of day which is used by all normal billing runs. Normal billing runs will default to this date when recurring Billing Runs are automatically scheduled. The settings consist of the following:

• Starting from day: The day of the month that should be used in the Bill as of Date (This will only be used the very first time a Normal Billing Run will be configured)
• Period of time after previous billing run: The date is calculated based on a period of time after the previous normal billing run, measured in hours, days, weeks, months or years. If the starting from day is specified then hours, days and weeks cannot be used

Defines how a billed period should be adjusted in case that the calculated from date is not equal to the cycle date (as specified on billing terms). This is applicable only on pre-billed services. 

• Adjustment Options:
• Previous Billing Cycle Date: The date is adjusted to the previous billing cycle date
• Next Billing Cycle Date: The date is adjusted to the next billing cycle date
• Nearest Billing Cycle Date based on Threshold Day: The date is adjusted to the previous billing cycle date if the date is equal or before the threshold day. The date is adjusted to the next billing cycle if the date is after the threshold day
• Threshold day: Applicable and mandatory only if the "Nearest Billing Cycle Date" option is selected

Defines how the invoice transaction date should be generated based on the date that the billing run is executed. The transaction date can be set to a date which is a period of time after billing run execution date, measured in hours or days.

Defines if further rounding adjustments should be applied on each bill, and the rules that should be used in order to generate those adjustments by specifying the following:

• Rounding method: 
  
  • Round half up
  • Round up
  • Round down
• Decimal scale
• Integer scale
• Rounding product: The product that will be included in the rounding debit or credit financial transaction
• Debit adjustment type: The financial transaction that will be used to create the adjustment invoice
• Credit adjustment type: The financial transaction that will be used to create the adjustment credit note

Defines rules that are applied in order to classify a bill as exceptional i.e. as a bill that might be problematic and should probably be investigated. Exceptional bills are created but they are classified so that they can be easily identified:

• Maximum amount in credit: The maximum amount that the customer should be in credit. For example, if this is set to 100, then if a generated bill amount is -101 then the bill will be classified as exceptional.
• Maximum credit limit amount: The maximum credit limit that can be provided to a customer, which can be either a fixed amount or a percentage of the customer's credit limit as specified on the customer's accounts receivable. For example if this is set to 500 (fixed amount), then if a generated bill amount is 501 then the bill will be classified as exceptional.

Defines how usage information should be exported in the XML file during the formatting step. The supported options are the following:

• Don’t include usage detail records
• Group usage per subscription service
• Group usage per usage service
• Individual entry per each usage detail record

Defines how rated service periods information should be exported in the XML file during the formatting step. The supported options are the following:

• Don’t include rated service periods
• Group rated service periods by service
• Individual entry per each rated service period