We have a requirement where the Billing rates are grouped and aggregated to show a summary view to the B2B customer and they can drill down the summary view to get the individual billing rates using the online interfaces and this grouping and summary is performed by a formatting layer which runs after the billing process.
This output of formatting layer needs to be presented to the B2B customer as their bill. So we intend to expose this output as a customerBill resource ( i.e. the output of the formatting layer) and use appliedCustomerBillingRate resource to also represent the summary charge, even though this summary charge was not created by the core billing process rather it was created by the formatting layer.
As this is a summary bill, it is kind of processed and enriched invoice data with some logic used to group items, and includes aggregated product and usage charge details.
So I was looking to get some feedback about this approach of using appliedCustomerBillingRate to represent the summary charge.
#CustomerExperience
#OpenDigitalArchitecture
#OpenAPI
------------------------------
Sajid Ali Deshmukh, (Ex-Amdocs)
Telstra Corporation.
------------------------------