Billing Cycle Pre-Run (FT-1015.002)
About this document
Scope
This document provides background information as well as a functional description of the FT-1015.002 Billing Cycle Pre-Run standard feature. The described feature is supported from the release version 4.0 onwards.
Note
Billing Cycle Pre-Run is a standard feature and does not require a special license.
This feature is part of the Billing Cycle Management functionality with number FN-1015.
Feature Availability
Feature Version | Available from | Summary of changes |
---|---|---|
v1 | CMP Release 4.0 | Initial release |
Feature overview
Goals
The aim of the Billing Cycle Pre-Run feature is to allow Service Providers to review and update charges and credits for each Billing Cycle.
Functionality of the feature
CMP allows CSP Users to review invoice charges and credits for each Billing Cycle for accuracy and approve them for Customer Billing.
Pre-Bill Reports provide the ability to review charges and credits applied to each Account during a Billing Cycle, and they can be checked once the Pre-Run of a Billing Cycle Instance finished. At this time, all charges and credits already got materialized in the Database, and the Instance is ready to proceed with the next step.
Each Pre-Bill Report has to be manually approved, before Customer Invoices and the Billing Feed are created and exported. Customer Invoices are only created and sent for billing if the Pre-Bill Report got approved. If the Pre-Bill Report gets declined, no Customer Invoices will be created and all accounting items will be discarded. Note that this action is permanent and cannot be reverted.
Further, in case of any errors during the execution of a Billing Cycle Instance, an error report gets provided.
The Instance does continue processing on Accounts which have no errors.
Once finished, the error state has to be either approved (in which case the errors are accepted and related items are not created) or reset (in which case the Instance will try to re-execute the failed items).
In case the root cause of an error did not get resolved properly before, a reset will lead to the same error again.
In case, errors are not either fully resolved or approved, the Billing Cycle Instance will not finish, and the Billing Feed will not get generated.