Category: (5) eTOM Process Type
Process Identifier: 1.6.12.1.5.1
Original Process Identifier:
Maturity Level: 3
Process governing the Creation of Invoices and Bills. Invoice is a document which is used to acknowledge goods received or service rendered. A Bill is a notice for payment which is supposed to be preceded by an invoice in most cases.
Process governing the Creation of Invoices and Bills. Invoice is a document which is used to acknowledge goods received or service rendered. A Bill is a notice for payment which is supposed to be preceded by an invoice in most cases. Once a batch of invoices was generated, it will be verified for correctness and delivered to a predefined destination. Instead of summarizing per consumer, the Invoice will contain aggregated information per service (and a separate entity for details – in analogy very similar to retail detail bills In Financial Terms, there is a difference between Invoice & Billing. Invoice is a document which is used to acknowledge goods received or service rendered. It’s not a Bill. A Bill is a notice for payment which is supposed to be preceded by an invoice in most cases. Upon Payment, a Receipt is generated as proof of payment. Example: The wholesale contract states the terms of payment : 10% advance, 50% against infrastructure delivered (large installations) & Rest against Balance, then 10% & 50% are Invoices & the Rest 40% will be termed as Bill. For wholesale contracts of high value and long lead-time the payment is divided according to a schema with the separate payments connected to special conditions, e.g. 10% at order, 40% at physical delivery, etc. With continual service delivery (like interconnect) , partners agree to continually roll the settlement of balances. Retail combines both service rendered and request for payment in one artefact. Hence Invoice & Bill is also often used interchanged with Retail Customers. As described above this simplification cannot and should not be extrapolated for Wholesale or Corporate. Pre-paid mobile does not generate retail bills but does generate interconnect and partner invoices Whereas retail billing consists of millions of accounts each with a small amount of data; partner billing consists of far fewer accounts but each with a large volume of associated data
This was created from the Frameworx 16.0 Model