Skip to end of banner
Go to start of banner

Configuring Prepaid 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 16 Next »

Table of Contents

Navigating to Prepaid Billing Run Definitions

CONFIGURATION > BILLING APPLICATION > BILLING > SET UP PREPAID BILLING RUN DEFINITIONS

What are Prepaid Billing Run  Definitions?

Prepaid Billing Run Definitions are a set of business rules which are used to control the behaviour of Prepaid Billing Runs throughout their Life Cycle. Prepaid Billing Run Definitions are used to define several business rules that must be applied during the Billing Run, as well as default values that are used Prepaid Billing Runs.

Prepaid Billing Run Definitions can be edited, deleted and have their Life Cycle State changed.

  • Navigate to Prepaid Billing Run Definitions and explore existing entries via the Summary page
  • Click on the link (name or number) of the entry of your interest to access the Data Entry page and see more detail, or submit the Definition. 

  • Use the Actions Menu to create a NEW Definition, modify (EDIT), or DELETE an existing one.  

  • Use BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Definition. 

  • Click on the Audit Log button to view a log of changes performed on the displayed Prepaid Billing Run Definition.

Check the Validations & Restrictions Table below for a list of available Actions when working with Prepaid Billing Run Definitions, including each Action's related validations and restrictions.  View the Attributes Table for a comprehensive description of the Prepaid Billing Run Definitions fields.


PREPAID BILLING RUN DEFINITION

Validations & Restrictions

ActionValidationsRestrictions
Create
  • Mandatory Fields must be defined
  • Name, and Alternative Code must be unique
  • Only one Prepaid Billing Run Definitions can be 'Active' at any time
Edit
  • Mandatory Fields must be defined
  • Name, and Alternative Code must beunique
  • Not Applicable
Delete
  • Not Applicable
  • Cannot be deletedifitsthe'Active' Definition

Attributes 

An * indicates a field is mandatory.

Name

Description

Main Information
Name*The name of the Prepaid Billing Run Definition.
Alternative Code*The alternative code of the Prepaid Billing Run Definition.
StateThe state of the Prepaid Billing Run Definition which can be 'Active' or 'Inactive'.
DescriptionA description of the Prepaid Billing Run Definition.
Settings
Generic Settings
Number Of Threads*The number of threads that should be used by the Prepaid Billing Run process. The maximum number of threads specified in General Settings cannot be exceeded.
Recurrence Settings
APPLICABLE UP TO R9 

The recurrence settings which are applied on all Billing Runs which are classified as recurring, measured in hours, days, weeks, months or years.

AVAILABLE FROM CRM.COM R10.0.0

The recurrence setting is removed. The System applies the default recurrence of 1 day.

Processing Settings
Enable Stop Service Step By Default
APPLICABLE UP TO R9 

Determines whether the Stop Service step should be enabled by default when creating new Prepaid Billing Runs.

AVAILABLE FROM CRM.COM R10.0.0

The Enable Stop Service Step by Default is removed. The Prepaid Billing Run no longer applies Stop Service actions.

Enable Start Service Step By Default
APPLICABLE UP TO R9 

Determines whether the Start Service step should be enabled by default when creating new Prepaid Billing Runs.

AVAILABLE FROM CRM.COM R10.0.0

The Enable Start Service Step by Default is removed. The Prepaid Billing Run no longer applies Start Service actions.

Enable Wallet Consumption Estimation Step by DefaultDetermines whether the Wallet Consumption Estimation step should be enabled by default when creating new Prepaid Billing Runs.

Maximum Estimation Period

 

This information determines the look ahead periodofthePrepaid Billing process when estimating the Consumption Date for a Subscription Service. 
This is available only if the estimation method is set to 'Re-estimate All' or 'Re-estimate Only Wallet with Changes'.

  • Period
  • UOT: Measured in months or years

APPLICABLE UP TO R9 - Rating Settings

AVAILABLE FROM CRM.COM R10.0.0 -The section has been removed. The date on which the Prepaid Billing Run is performed will be used as the Bill As Of Date

Period To Bill In Advance*

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

  • Do not bill any period in advance
Bill As Of Day Settings

Rules to calculate the default Bill As Of Day used by all Prepaid Billing Runs. Prepaid Billing Runs will default to this date unless a different date is specified. The following settings are available:

  • Starting from day: The day of the month that should be used in the Bill As Of Date the first time (only) that the Prepaid Billing Run is executed.
  • Periodafterprevious Billing Run: The period is calculated from the time since the previous Prepaid Billing Run, measured in hours, days, weeks, months or years.

APPLICABLE UP TO R9

Start Service Settings

Available only if enabled in Processing Settings

Subscription Action Type

The Subscription Action Type that will be used to start the necessary Services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Action Types related to the Start Service behaviour code exist.

Subscription Sub-Action Type

The Subscription Sub-Action Type that will be used to start the necessary services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Sub-Action Types related to the Start Service behaviour code exist.

Amount Threshold*The minimum (exclusive) Wallet Balance necessary to start each specific Service. For example, if the Threshold is set to 0 and the available amount for a 'Not Effective' Service is 1, then the Service will be started. If the available amount for a 'Not Effective' Service is 0, then the Service will not be started.

APPLICABLE UP TO R9

Stop Service Settings

Available only if enabled in Processing Settings

Subscription Action Type

The Subscription Action Type that will be used to stop the Services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Action Types related to the Stop Service behaviour code exist.

Subscription Sub-Action Type

The Subscription Sub-Action Type that will be used to stop the Services.

Mandatory on Conditions: This is applicable and mandatory if Subscription Action Types related to the Stop Service behaviour code exist.

Amount Threshold*

The maximum (inclusive) Wallet Balance necessary to stop each specific Service. For example, if the Threshold is set to 0 and the available amount for a 'Not Effective' Service is 0, then the Service will be stopped. If the available amount for a 'Not Effective' Service is 1, then the Service will not be stopped.

Log Information
Log DetailsThe standard set of Log Details information available in all entities.

View Understanding Prepaid Billing for business examples related to Prepaid Billing Run Definitions.

  • No labels