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

• Only one Normal Billing Run Definition 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

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

• One Billing Frequency period ahead
• One Billing Frequency period ahead minus the post-bill prorated period

Defines how a billed period is adjusted when the calculated 'From' date is not equal to the Cycle date (as specified in the 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 to or before the threshold day. The date is adjusted to the next billing cycle if the date is after the threshold day.
• • • Threshold day: A number between 1 and 31 can be entered. This field is applicable and mandatory only if the "Nearest Billing Cycle Date" option is selected.

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:

• Day of the Month: The day of the month that should be used in the Bill As Of Date; this is only used the first time a Normal Billing Run is configured.
• Period after Previous Billing Run: The period that the Bill As Of Date of the next scheduled Billing Run is set equal to, measured in hours, days, weeks, months or years.

Determines the creation of the Invoice Transaction Date based on the date that the Billing Run is executed. The Transaction Date can be set to a unit of time measured in hours or days after the Billing Run execution date.

Defines whether further rounding adjustments should beappliedoneachbill, and the rules 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. a bill that is potentially problematic and should be investigated. Exceptional bills are created but 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 and a bill amount of 101 is generated, 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 either be 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 a fixed amount of 500 and a bill amount of 501 is generated, then the Bill will be classified as Exceptional.

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

• Don’t Include Usage Detail Records
• Group Usage By Subscription Service
• Group Usage By Usage Product
• Individual Entry For Each Usage Detail Record
  

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

• Don’t Include Rated Service Periods
• Group Rated Service Periods By Service
• Individual Entry For Each Rated Service Period