Skip to end of banner
Go to start of banner

Configuring & Executing Prepaid Billing Run

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 9 Next »

Table of Contents

Navigating to Prepaid Billing Runs

BILLING > BILLING > PERFORM PREPAID BILLING RUNS

What is Prepaid Billing Run ?

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 they subscribed to, by deducting the used amount from the paid amount, using the wallets module.

Prepaid billing run is usually performed on a daily basis and is responsible to:

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

Optionally the prepaid billing run can:

  • APPLICABLE UP TO R9 - Stop subscription services which are left with no wallet credit
  • APPLICABLE UP TO R9 - 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

Navigate to Prepaid Billing Runs and explore existing records via the Summary page. Click on the link (name or number) of the record of your interest to enter the Data Entry page and have a better look of the available information. Use the Actions Menu to create a new (NEW) Prepaid Billing Run, or modify an existing one if not already executed (EDIT). 
Use the (BACK) link to go back to the summary page and (CANCEL) to cancel any unwanted changes made to the Prepaid Billing Runs. Check out the attributes table below for a thorough explanation of the information kept for Prepaid Billing Runs and the Validations&Restrictions table to find out validations and restrictions applicable when working with Prepaid Billing Runs.
PREPAID BILLING RUN 

Executing Prepaid Billing Run

Once a Billing Run is created it will then need to be executed 

  1. From the Actions Menu click on ACTIONS > EXECUTE
  2. 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


Validations & Restrictions

ActionValidationsRestrictions
Create
  • Not Applicable
  • 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

Prepaid Billing Run Attributes 

Name

Description

NumberAn auto generated number which uniquely identifies each prepaid billing run
State

The life cycle state  of the 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
  • 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
Scheduled DateThis is a read only field which is available once you schedule a Run. The date provided shows the latest date that the run is scheduled to be executed.
Bill as of date*

Defines the date that prepaid billing run should be performed as.

  • APPLICABLE UP TO R9 - The bill as of date takes a default value based on the bill as of day setting specified in prepaid billing run definitions, although it be modified by users
  • AVAILABLE FROM CRM.COM R10.0.0 - The bill as of date is set equal to the date the Prepaid Billing Run is performed
Enable Stop Service Step
APPLICABLE UP TO R9 

It 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.

AVAILABLE FROM CRM.COM R10.0.0 Prepaid Billing Run no longer applies stop services actions

Enable Start Service Step
APPLICABLE UP TO R9 

It 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.

AVAILABLE FROM CRM.COM R10.0.0 Prepaid Billing Run no longer applies start services actions

Enable Wallet Consumption Estimation Step

It 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.

Skip estimation of wallets for faster execution

CRITERIA
Consider billing term schemes*The billing term schemes that should be considered by the prepaid billing run process. Only billable entities having billing terms of those schemes will be billed. Only billing term schemes classified as prepaid can be included in this list.
Consider accounts receivable classifications*

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

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 prepaid billing run process
SubscriptionsA list of subscriptions that are used as filters. If specified then only those subscriptions will be billed by the 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 prepaid billing run process
Scheduling Settings
Scheduling Settings*

Defines if the prepaid billing run is recurring or one time.

  • APPLICABLE UP TO R9 - In the case of recurring prepaid billing runs, the recurrence is inherited from the prepaid billing run definitions (and is visible to the user)
  • AVAILABLE FROM CRM.COM R10.0.0 - In the case of recurring prepaid billing runs, the recurrence is set to 1 day

Results & Exceptions

The 2 sections are available once the Billing Run is executed and provide you with the results of the billing

Results
  1. Number of Generated Wallet Transactions: Provides the total number of wallet 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
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 
Log Information
Log InformationThe standard Log Information

Related Areas

Helpful Links

  • No labels