Hi Mukesh
Welcome to the world of TMF, hope you'll be able to use the standards in your organization's work.
Applied Customer Billing Rate (ACBR), perhaps more colloquially known as a charge, is what will eventually appear on a bill or an invoice. In general, the billing run is the source of ACBRs, but it is possible that ACBRs might also be produced/requested by an external system. ACBRs are instance data, calculated by the billing and/or charging systems.
It is completely up to you how to manage the storage of these entities, TMF does not dictate or suggest best practices for internal persistence mechanisms (as far as I am aware).
Hope it helps.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Dec 09, 2021 05:56
From: mukesh se n
Subject: Billing Applied rate
Dear all,
I am working on billing management and am new to the TMF standards.
(1) I would like to know about AppliedCustomerBillingRate schema/entity and API uses. What is use of this AppliedCustomerBillingRate means all the billing rate which will be used for billing generation is configured in product/offering like oneTimeCharge/rate, monthlyCharge, Taxes etc. and all these rate will be fetched by billing module/API while generating Customer bill and what is use of AppliedCustomerBillingRate, AppliedCustomerBillingRateSpec, AppliedBillingTaxRate etc in billing module.
(2) Based on above question whether billing has to maintain separate data/schema for oneTimeCharge/rate, monthlyCharge, Taxes etc ( AppliedCustomerBillingRate, AppliedCustomerBillingRateSpec, AppliedBillingTaxRate ).
Please clarify my doubts
regards
Mukesh
------------------------------
mukesh se n
C-DOT
------------------------------