Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt
hiddentrue

Learn how you can configure and execute Normal Prepaid Billing Run Run

What does this section cover?

Table of Contents
minLevel2

What is

Normal

Prepaid Billing Run ?

In CRM.COM Software the way to bill the customers in a batch mode is done via Billing Runs referred to as Normal Billing Runs or Prepaid Billing Runs.

Normal Prepaid billing run is a billing mechanism which is used in cases where customers pay in advance and then they can start using the services that were they subscribed to or delivered to them, and by the end of their billing frequency period they are charged for those services. Normal deducting the used amount from the paid amount, using the wallets module.

Prepaid billing run is usually performed on a monthly daily basis and  and is responsible to identify the billable services, rate them, invoice them per subscription or job, assemble each customer’s bill which includes all of those invoices and post them. Normal customers receive a bill which covers all the invoices related with their subscriptions or jobs, which is then sent to them in order to make their due payments. Normal billing run process is performed in various steps, as described in Understanding Normal Billing Run Execution:

  • Identify the service usage 
  • Rate the used services
  • Debit the related wallets based on that usage

Optionally the prepaid billing run can:

  • Stop subscription services which are left with no wallet credit
  • Start services which were stopped and are now having enough wallet credit
  • Estimate the date that the wallet amount will be consumed by the subscription services, based on their existing usage and billing term schemes. 

No bills or financial transactions are generated by the prepaid billing run and unlike Normal Billing Runs, Prepaid billing run is only applicable on Subscriptions.Visit Interpreting Prepaid Billing Run Execution Steps for a complete description of all the available processes within Prepaid Billing Runs.

In order for the Billing Run to be created  then ,  Normal  Prepaid Billing Run Definition needs to be set up in the system. Once the definition is set up, once a new Normal Prepaid Billing Run is created certain values will either be set by default as provided by the Normal Billing Run Definition or will be validated against it.can be created and executed.

Anchor
create
create
Creating a Prepaid Billing Run 

Creating, Editing & Deleting Validations & Restrictions

ActionValidationsRestrictions
Create 
  • Active Billing Run definition exists in the system
Edit
  • All mandatory fields have been defined
  • Life Cycle State = DRAFT
Delete
  • All mandatory fields have been defined
  • Billing Runs cannot be deleted
Normal

Prepaid Billing Run  attributes 

The billing frequencies that should be considered by the normal billing run process. Only billable entities having billing terms with these frequencies will be billed. Only billing frequencies which are supported by the active billing term definition can by included in this list

Name

Description

NumberAn auto generated number which uniquely identified each normal prepaid billing run
TypeDefines if the normal prepaid billing run was performed on a batch or individual mode. The supported values are BATCH and INDIVIDUAL
Life cycle state

The life cycle state  of the normal prepaid billing run. The supported states are the following:

  • Draft: The billing run was not executed yet
  • Identification & Rating: The billing run was executed up to this step
  • Invoicing: The billing run was executed up to this step
  • Assembling & Posting: The billing run was executed up to this step
  • Formatting: The billing run was executed up to this step
  • Completed: All billing run steps were executed successfully
  • Failed: The billing run was not executed and no bills were created
  • Completed with errors: the billing run was executed, with minor errors and bills were created
Bill as of date*

Defines the date that normal prepaid billing run should be performed as. The bill as of date takes a default value based on the bill as of day setting specified in normal prepaid billing run definitions, although it be modified by users

Transaction date*Defines the date that will be used as the financial transaction date. The Default value is set based on normal billing definitions, although it can be modified by users
Invoice due date proximity settings*

Defines how the due date of the generated invoices should be set. This setting is applicable only if the active accounts receivable definitions allows a proximity range. The specified period should be within the specified range as defined in the Accounts receivable Definition The settings consist of the following

  • Sign: - or +
  • Value: The actual value that will be added on the due date, which is calculated based on the active accounts receivable definitions due date rules

The sign and the value are validated against the proximity range definition which is again specified in the due date rules

Scheduling settings*Defines if the normal billing run is recurring or one time. In the case of recurring normal billing runs, the recurrence is inherited from the normal billing run definitions (and is visible to the user)
Conditions
Consider billing term schemesEnable Stop Service StepIt determines if the stop service step should be performed or not. It is automatically set on creating the prepaid billing run, based on the processing settings specified on the active prepaid billing run definitions.
Enable Start Service StepIt determines if the start service step should be performed or not. It is automatically set on creating the prepaid billing run, based on the processing settings specified on the active prepaid billing run definitions.
Enable Wallet Consumption Estimation StepIt determines if the wallet consumption estimation step should be performed or not. It is automatically set on creating the prepaid billing run, based on the processing settings specified on the active prepaid billing run definitions.
CRITERIA
Consider billing term schemes*The billing term schemes that should be considered by the normal prepaid billing run process. Only billable entities having billing terms of those schemes will be billed. Only billing term schemes classified as normal prepaid can be included in this list. Consider billing frequenciesIt is mandatory to select at least one billing term scheme
Consider accounts receivable classifications*

The accounts receivable classification that should be considered by the normal prepaid billing run process. Only billable entities owned by accounts receivable having one of those classifications will be billed. 

Consider payment preferences

The accounts receivable payment preferences that should be considered by the normal billing run process. Only billable entities owned by accounts receivable having one of those payment preferences will be billed.

Consider presentment preferences

The accounts receivable presentment preferences that should be considered by the normal billing run process. Only billable entities owned by accounts receivable having one of those presentment preferences will be billed.It is mandatory to select at least one accounts receivable classification

Filters
Accounts receivableA list of accounts receivable that are used as filters. If specified then only the those accounts receivable will be billed by the normal prepaid billing run process
SubscriptionsA list of subscriptions that are used as filters. If specified then only those subscriptions will be billed by the normal billing run processJobsA list of jobs that are used as filters. If specified then only those jobs will be billed by the normal prepaid billing run process
GroupsA list of Groups that are used as filters. If specified then only the accounts receivable owned by the specified Groups will be billed by the normal prepaid billing run process
Scheduling Settings
Scheduling Settings*
Configuring a Normal
Defines if the prepaid billing run is recurring or one time. In the case of recurring prepaid billing runs, the recurrence is inherited from the prepaid billing run definitions (and is visible to the user)

Configuring a Prepaid Billing Run  tailored to your company's needs

  1. Navigate to BILLING > BILLING > PERFORM NORMAL PREPAID BILLING RUNS
  2. Either search for an existing one or from the Top Menu click on NEW
    NORMAL BILLING RUNImage RemovedPREPAID BILLING RUNImage Added
  3. MAIN INFORMATION

    1. Bill as of date: Click on the calendar and select a date

    2. Life Cycle State: This is read only and will be automatically set by the system

    3. Scheduled Date: This is read only and will be automatically set by the system 

    4. Enable Stop Service Step by Default: Check the box if you would like to enable. (Related configuration can be found at Configuring Prepaid Billing Run Definitions
    5. Enable Start Service Step by Default:  Check the box if you would like to enable and configure accordingly in Configuring Prepaid Billing Run Definitions
    6. Enable Wallet Consumption Estimation Step: Select an option from the drop down list. 

      Info

      Skip estimation of wallets for faster execution

  4. CRITERIA

    1. Billing Term Schemes
      1. Click on ADD and use the search modal to select the Billing term schemes to be included
        OR
      2. Click on ADD ALL BILLING TERM SCHEMES 
      Billing Frequencies
      1. Click on ADD and select from the drop down list the Billing Frequencies to be includedOR
      2. Click on ADD ALL BILLING FREQUENCIES
    2. Classifications
      1. Click on ADD and use the search modal to select the account Classifications to be included
        OR
      2. Click on ADD ALL CLASSIFICATIONS
    3. Payment Preferences
      1. Click on ADD and use the search modal to select the Payment Preferences to be included
        OR
      2. Click on ADD ALL PAYMENT PREFERENCES 
    4. Presentment Preferences
      1. Click on ADD and use the search modal to select the Presentment Preferences to be included
        OR
      2. Click on ADD ALL PRESENTMENT PREFERENCES 
  5. FILTERS

    1. Groups
      1. Click on ADD and use the search modal to select the groups whose subscriptions should be included (Owned by Group)
    2. Accounts receivable
      1. Click on ADD and use the search modal to select the groups whose subscriptions should be included 
    3. Subscriptions
      1. Click on ADD and use the search modal to select the subscriptions that should be included
      Jobs
      1. Click on ADD and use the search modal to select the jobs that should be included
  6. SCHEDULING SETTINGS 

    1. Recurring: Check the box if the Billing Run should be recurring
    2. Recurrence Settings: The default values as defined in the Billing Run Definition are loaded. 
      1. Provide a different number and select UOT 

    FINANCIAL TRANSACTION SETTINGS

    1. Financial Transaction Posting Date: Click on the calendar and select a date
    2. Invoice Due Date Proximity: Select between  + / - and provide an integer value for the proximity date
  7. From the Top Menu click on SAVE

  8. LOG INFORMATION

    Include Page
    WIP:Log Information - Global
    WIP:Log Information - Global

Executing a

Normal

Prepaid Billing Run

Once a Billing Run is created it will then need to be executed in order to actually bill the subscribers.Users will have the option to execute a Billing Run up to any of the 4 stages that are available. Visit /wiki/spaces/V4Manual/pages/9833562 for a detailed description of all the Billing Run stages available.

If the Billing Run is not in the final State, i.e. Formatting, then the the user will be allowed to continue with the execution of the Billing  to any of the follow up steps. 

 

  1. Navigate to BILLING > BILLING > PERFORM NORMAL PREPAID BILLING RUNS
  2. Search for the Billing Run you would like to execute and click on the number to go to the data entry page
    EXECUTING NORMAL BILLING RUNImage Removed
    Up to Rating State
  3. From the Actions Menu click on Actions > Execute Up to Identification & Rating
  4. In the Execute Normal Billing Run Modal 
    1. Execute Now: Check the box to execute the Billing Run directly
    2. Scheduled Date: Click on the calendar to select a date and time to start the execution. Click DONE when completed
    3. Click SAVE

    Up to Invoicing

  5. From the Actions Menu click on Actions > Execute Up to Invoicing
  6. In the Execute Normal
    EXECUTE PREPAID BILLINGImage Added 
  7. In the Execute Prepaid Billing Run Modal 
    1. Execute Now: Check the box to execute the Billing Run directly
    2. Scheduled Date: Click on the calendar to select a date and time to start the execution. Click DONE when completed
    3. Click SAVE 

    Up to Assembling & Posting

  8. From the Actions Menu click on Actions > Execute Up to Assembling & Posting
  9. In the Execute Normal Billing Run Modal 
    1. Execute Now: Check the box to execute the Billing Run directly
    2. Scheduled Date: Click on the calendar to select a date and time to start the execution. Click DONE when completed
    3. Click SAVE

    Up to Formatting

  10. From the Actions Menu click on Actions > Execute Up to Formatting
  11. In the Execute Normal Billing Run Modal 
    1. Execute Now: Check the box to execute the Billing Run directly
    2. Scheduled Date: Click on the calendar to select a date and time to start the execution. Click DONE when completed
    3. Click SAVE
Reading Normal Billing Run

Reading Prepaid Billing Run  Results

  1. Navigate to BILLING > BILLING > PERFORM NORMAL PREPAID BILLING RUNS
  2. Search for an existing Billing Run and click on the number to go to the Data entry page
  3. RESULTS

    1. Number of Generated BillsWallet Transactions: Provides the total number of bills generatedwallet transactions generated from the current execution of the billing run
    2. Start Date: Provides the Start Date of the Billing Run
    3. End Date: Provides the End Date of the Billing Run
    4. Results per Step: Provides all the steps taken for the specific Billing Run and gives analytically the Financial Transactions created and the entities included
      PREPAID BILLING RUN RESULTSImage Added
      RESULTSImage Removed 
  4. EXCEPTIONS

    1. Accounts Receivable: Provides the accounts which were not billed due to some error
    2. Code: The code of the error that caused failure in billing the account 
Panel
namegrey

Related Areas

Filter by label (Content by label)
showLabelsfalse
spacesV4Manual
showSpacefalse
excerpttrue
labelsprepaid-billing-basics-r7,prepaid-billing-advanced-r7,prepaid-billing-admin-r7

Panel
namegrey

Popular Labels

Popular Labels
spaceKeyV4Manual
styleheatmap