Skip to end of banner
Go to start of banner

Configuring Normal Billing Run Definitions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

What does this section cover?

What are Normal Billing Run Definitions?

Normal Billing Run definitions is a set of business rules used to control the behavior of Normal Billing Run throughout their whole life cycle. Normal billing run definitions is used in order to define several business rules that need to be applied during the billing run, but also default values, which are used while running normal billing runs.

Creating, Editing & Deleting Validations & Restrictions

ActionValidationsRestrictions
General
  • 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
Create
  • Mandatory Fields must be defined
  • Name and alternative code must be unique
  • Not Applicable
Edit
  • Mandatory Fields must be defined
  • Name and alternative code must be unique
  • Not Applicable
Delete
  • Not Applicable
  • Cannot be deleted if its the active definition

Normal Billing Run Definition attributes 

Name

Description

Name*The name of the normal billing run definition
Alternative code*The alternative code of the normal billing run definition
StateThe state of the normal billing run which can be active or inactive
DescriptionA description of the normal billing run definition
Settings
Generic settings
Number of threads*The number of threads that should be used by the normal billing run process.
The maximum number of threads specified in General Settings cannot be exceeded.
Recurrence settingsThe recurrence settings which are applied on all billing runs which are classified as recurring, measured in hours, days, weeks, months or years
Rating settings
Period to bill in advance*

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
Bill as of day settings

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 unless a different date is specified. The settings consist of the following:

  • Starting from day: The day of the month that should be used in the Bill as of Date
  • 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
Period cycle adjustment*

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
Invoicing Settings
Debit financial transaction type*The debit financial transaction type that will be used to create invoices
Credit financial transaction type*The credit financial transaction type that will be used to create credit notes
Minimum amount in debitThe minimum amount in debt which is needed in order to bill rated billing items. If the amount is below the minimum then the bill is not created
Invoice transaction date settings

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.

Assembling settings
Rounding options

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
Exceptional bill settings

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.
Formatting Settings

Usage formatting settings

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
Rating formatting settings

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

Defining your own Normal Billing Run  Definition tailored to your company's needs

  1. Navigate to CONFIGURATION > BILLING APPLICATION > BILLING > SET UP NORMAL BILLING RUN DEFINITIONS
  2. Either search for an existing one or from the Top Menu click on NEW
    NORMAL BILLING RUN DEFINITION

  3. MAIN INFORMATION

    1. Provide Information for the following fields
      1. Name
      2. Alternative Code
      3. Description
  4. SETTINGS

    1. GENERIC

      1. Number of Threads: Provide an integer value
      2. Recurrence: Provide an integer value and select UOT for the default recurrence settings
    2. RATING

      1. Period to Bill in Advance: Select an option from the drop down list
      2. Period Cycle Adjustment: Select an option from the drop down list
      3. Bill as of Day
        1. Day of the Month: Select an option from the drop down list
          OR
        2. Period After Previous Billing Run: Provide an integer value and select UOT for the default Bill as Of Date
    3. INVOICING

      1. Debit Financial Transaction Type:  Select an option from the drop down list
      2. Minimum Amount In Debit: Provide an integer/decimal value
      3. Credit Financial Transaction Type:  Select an option from the drop down list
      4. Set Transaction Date X UOT After Billing Run: Provide an integer/decimal value
    4. ASSEMBLING

      1. Rounding Options
        1. Apply Rounding: Check the box if rounding should be applied
          1. Rounding Method: Select an option from the drop down list
          2. Decimal Scale: Provide a decimal value
          3. Integer Scale: Provide an integer value
          4. Rounding Product: Search and add the rounding product using quick search or the search modal
          5. Debit Adjustment Type: Select an option from the drop down list
          6. Credit Adjustment Type: Select an option from the drop down list
      2. Exceptional Billing Settings
        1. Maximum Amount in Credit: Provide an integer/decimal value
        2. Maximum Credit Limit Amount:Select an option from the drop down list
          1. Define an integer/decimal value for either fixed credit or % account's Credit Limit
    5. FORMATTING

      1. Rating Formatting:Select an option from the drop down list
      2. Usage Formatting: Select an option from the drop down list
  5. From the Top Menu click on SAVE
  6. LOG INFORMATION

    Log information section keeps all the logging information related to the specific record

    • Basic set of information available in all entities
      • Created By User: The user that created the entity
      • Created By Unit: The unit of the user that created the entity
      • Updated By User: The user that last updated the entity
      • Updated by Unit: The unit of the user that last updated the entity
      • Date Created: The date the account was entity
      • Date Updated: The date the account was last entity
        LOG DETAILS

Deleting Normal Billing Run Definitions

  1. Search for the entity that you would like to delete
    Visit  Using Summary Pages   to find out how you can search using CRM.COM Summary Screens
  2. Click on the link of the record you would like to delete, to be transferred to the Data Entry page
  3. From the actions menu click on "DELETE"
     The entity will be deleted given that the validations are satisfied

Changing the Life Cycle State of Normal Billing Run Definition

Unable to render {include} The included page could not be found.

 

Visit Understanding Normal Billing for business examples related to Normal Billing Run Definition

Related Areas

Popular Labels

  • No labels