Open APIs

While reviewing the TMF678 Customer Bill API, we observed that several bill cycle-related fields like billingDate, billingPeriod, mailingDate, and paymentDueDate are directly present in the CustomerBill resource, even though there's also a reference to a separate BillCycle entity. This raises a question on whether these fields should be derived from the BillCycle or are meant to be stored independently during bill generation.

In TMF666, the BillingAccount is associated with a billingStructure, which includes billingCycleSpecification and other configuration details. We would like to understand if the billCycle in TMF678 is the same as the billingStructure in TMF666 or if it serves a different purpose-such as capturing actual runtime billing cycle details.

Clarification on the intended relationship between billCycle and billingStructure, and guidance on whether to use references or duplicate values in CustomerBill, would be helpful.

Hi,

both are specifically different and for different purpose. The Customer Bill TMF 678 refers to the transactional perspective of the Billing event and Account level TMF 666 provides the perspective of agreement to have billing event along with the attributes associated with billing event.