Category: (4) eTOM Process Type
Process Identifier: 1.6.12.1.5
Original Process Identifier:
Maturity Level: 3
The Process that captures services (telco, physical, supportive) delivers of a period or multiples thereof, and timely communicate such detail, often including the price of such service. This includes aiding, rating, applying adjustments, presenting it in various formats and finally ensuring delivery (secure & auditable)
Process generally follows will equal the “balance forward” from the previous invoice plus current charges. It will contain an aggregate of services consumed. But notably not on FLN (Fixed Line Number) or DN (Directory Number) level of detail. Have strong similarities with Retail - 1.1.1.10 Bill Invoice Management and are often initially perform by the same internal services for smaller operators. As the offerings differentiates more (i.e. for Tier 1), it not unusual to see a dedicated Chain for Wholesale & Business Party Billing Invoices, that allows quick re-billing, manual adjustments etc. Wholesale Bill Invoice Management processes ensure the bill invoice is created, electronically produced and distributed to Business Parties, and that the appropriate taxes, discounts, adjustments, rebates and credits for the products and services delivered to customers have been applied. These processes are accountable for assuring that enterprise revenue is billed and invoices delivered appropriately to Business Parties. Major Differentiation Factors for a separate Invoice Generation: • Invoice Timeliness - Generation happen monthly but often also biweekly. In contrast to Retail where it is critical customer's invoice is being generating on time, (Cost of Infrastructure, ability to re-invoice, apply adjustments) and dependency on reconciliation (often manually externally driven), requires • Invoice Accuracy – The tolerance for accepting differences between the balance of two invoices is much higher than for retail. By implication checks and balances The Invoice document does not summarize to total outstanding payment or payments due. The Bill contains the payment due date and Balance. Interconnect charges may be incurred for all call attempts rather than just those that succeed and are charged to the retail customer Further Sub processes impacted Tax Jurisdiction Applied -The process of applying Taxes according to applicable Jurisdictions for National and Multinational Customers applicable for various services. In certain countries it is standard practice to outsource sub functions of Tax Determinations to specialized external entities. Interconnect charges may be incurred for all call attempts rather than just those that succeed and are charged to the retail customer. Reflect the whole route of the call, not just the origination and termination points. As a consequence, for example the Interconnect Invoice will be generated from • Data & Voice CDRs that is only billable for Interconnect providers. Eg: Outgoing calls (revenue shared), Outgoing Transit calls, Incoming calls, etc. The model simplifies it in terms of a balance in MOU (minutes of use). The Outgoing calls are the expense and Incoming calls are the revenue for the Telecom Provider.
This was created from the Frameworx 16.0 Model