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

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

• deletedifitsthe'Active' Definition

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

• One billing frequency Billing Frequency period ahead
• One billing frequency 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

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 Billing Run is executed. The transaction date Transaction Date can be set to a date which is a period unit of time after billing run execution date, measured in hours or days after the Billing Run execution date.

Defines if whether further rounding adjustments should be applied on each billbeappliedoneachbill, 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 Product that will be included in the rounding debit or credit financial transactionFinancial Transaction.
• Debit adjustment type: The financial transaction Financial Transaction that will be used to create the adjustment invoiceInvoice.
• Credit adjustment type: The financial transaction Financial Transaction that will be used to create the adjustment credit noteCredit Note.

Defines rules that are applied in order to classify a bill as exceptional Exceptional.  i.e. as a bill that might be is potentially 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 and a generated bill amount of 101 is -101 generated, then the bill Bill will be classified as exceptionalExceptional.
• Maximum credit limit amount: The maximum credit limit that can be provided to a customer, which can can either be either a fixed amount or a percentage of the customer's credit limit as specified on the customer's accounts receivableAccounts Receivable. For example, if this is set to 500 (a fixed amount ), then if a generated of 500 and a bill amount of 501 is 501 generated, then the bill Bill will be classified as exceptionalExceptional.

Defines how usage information should be exported in the XML file during the formatting step. The supported available 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

• 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 supported available options are the following:

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

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