Billing Feed (FT-1007.005)

About this document

Scope

This document provides background information as well as a functional description of the FT-1007.005 Billing Feed standard feature. The described feature is supported from the release version 3.0 onward.

Note

Billing Feed 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

Benefits

MAVOCO CMP provides all the billing functionalities that a CSP might need. From functionality perspective, there is no need for an additional billing system. However, many CSPs already have a Billing System integrated into their landscape and still need to use it. For this reason, an integration of MAVOCO CMP into the CSPs' Billing System can be done through a Billing Feed file via sFTP. CMP will provide out of the box raw bill feed to the Customer’s Billing System for that system to process, apply taxes & create customer invoices.

Feature overview

Goals

The aim of the Billing Feed feature is to generate a Billing Feed file with usage and cost information to be used as an input into the external Billing System of the CSP.

Functionality of the feature

In most instances, CMP is integrated into an existing external CSP Billing System to consolidate IoT charges with other business of the Operator and produce Account Invoices. In such cases, CMP generates a Billing Feed file as an input into the external Billing System.

CMP offers a “Standard Billing Feed” as an OOB feature (which contains all created Accounting Items along with dedicated Charge Codes), however, it is usually customized as part of the integration, to fit all requirements of the external Billing System (like file output format, charge line logic, and delivery taxonomy).

The Billing Feed is generated as part of Billing Cycle execution, once the Billing Cycle has completed successfully.

CMP always executes the full Billing Cycle normally and always generates all cost items for one-time, recurring and usage charges (SIM and non-SIM related), however, not all of those might be exported and provided in the Billing Feed (as defined at the integration project).

Further, the Billing Feed can generate aggregated usage and cost items (as defined at the integration project) rather than a simple 1:1 mapping of the CMP charge items.

Typically, the following information is exported into the Billing Feed:

1. per SIM or Pool Price Plan, the total Usage for Data, SMS (MO/MT) and Voice (MO/MT)

2. per SIM or Pool Price Plan, the total Overage costs for Data, SMS (MO/MT) and Voice (MO/MT)

3. per Account, the One-Time Charges (credit or debit) added manually during the month

4. per Account, SIM or Pool Price Plan, the MRC (Monthly Recurring Charge)

5. per Account, SIM or Pool Price Plan, the One-Time Charges triggered by SIM or Pool Price Plan operations (like Activation Charge or Period Fee)