Open APIs

Hi,

I have a question regarding TMF666 Account Management.

In the bill structure, is it possible to define a single billing format while allowing multiple values for bill presentation media.

The API User Guide provides an example of a billing format with two values: "simple invoice" and "detailed invoice." However, in our case, we also have some internal formats such as XML/CSV and e-invoicing standards like: EDIFACT – A traditional, complex international EDI standard, OIO – An XML-based e-invoicing standard.

Customers may request invoices in multiple formats simultaneously. Additionally, not all bill presentation media will be compatible with every format (e.g., post mail may not support some electronic formats).

Is the "billing format" field appropriate for defining these types of formats? Or is it primarily intended for standard document types that can be printed, with additional formats needing to be handled as an extension of the standard TMF666 API?

------------------------------
Tomasz Ruchała
Comarch S.A.
------------------------------

Hi @Tomasz

this will allow (TMF666) to define the different values but if the XML/CSV bill format needs to support by bill presentation(email) right!! that is logically not correct.

EX: i have used below different definitions for TMF 666, CRM will update the billing system based on customer preference.