Category: (3) eTOM Process Type
Process Identifier: 1.6.12.2
Original Process Identifier:
Maturity Level: 3
The Control Settlement processes oversee the efficacy of Settlement process according to party settlement agreements, including revenue share modelling, optimizing expenditures (Least Cost Routing), Dispute Handling, Handling Legal and Government Financial Requests, Tracking the Execution(Implementation/Deprioritization) of cases identified by Fraud, Handling of various type of planned Service constraints (Embargo), Write-off of Assets from various causes, Recovery of Assets and Revenue, Collection of Payments or Collaterals. It means controlling (specifically the efficiency) of the Settlement workflow. That does not include doing the specific settlement specialization of job (i.e. interconnect, MVNO,...).
The Control Settlement processes oversee the efficacy of Settlement process according to party settlement agreements, including revenue share modelling, optimizing expenditures (Least Cost Routing), Dispute Handling, Handling Legal and Government Financial Requests, Tracking the Execution(Implementation/Deprioritization) of cases identified by Fraud, Handling of various type of planned Service constraints (Embargo), Write-off of Assets from various causes, Recovery of Assets and Revenue, Collection of Payments or Collaterals The Control Settlement process aims to ensure the efficiency and effectiveness of the operational process and touches on the following functions/ services entails (referenced from ITU-T D.170/Suppl.4) 1) Record Capture 2) Mediation 3) Rating 4) Generation Outbound Declarations/ Invoices 5) Receipt Inbound Declarations /Invoice 6) Ongoing creation & update of Settlement Statement for various partners 7) Validation of Settlement Statement 8) Reconciliation (which includes negotiations) 9) On Settlement Statement Acceptance - Payment & Remittance The Control Settlement processes controls the efficiency Settlement process according to party settlement agreements. It means controlling (specifically the efficiency) of the Settlement workflow. That does not include doing the specific settlement specialization of job (i.e. interconnect, MVNO,...), but the primary aim is to ensure 1) that its cost effective, whether logically (without knowing the underlying contract), pricing (knowing the contract conditions apart from the Network Layout), or a optimum of both. 2) allowing a sub process for handling of differences (disputes), also including mechanisms to handle dynamic change of resource costs (i.e. in mobile networks this is more static). 3) Analyzing the history (i.e. usage patterns) to predict the probabilities and relative importance of optimizing a specific route. As per the definition above, we'll expand the notion of record capture to include all types of usage, events, coming from the network, or other domains, for the purpose of determining monetary value (This includes CDR’s, TDR’s, IPDR’s, and more). Settlements are created as defined in agreement - daily, weekly, monthly Settlement statement include i) sub-totals for each service per currency and per carrier ii) net value per entry iii) grand total per currency and carrier iv) total net value per currency and carrier Settlement Statements excludes i) traffic volumes ii) IMF rates iii) product level detail.
This was created from the Frameworx 16.0 Model