Team,
I'd be interested to hear from the community on what others may have done around the use of TMF defined resources for building an integration patter between a product order management platform and a billing/revenue management platform.
Reviewing the definition of TMF678 and some of the described use cases, I interpret it's use case more for actual billing data interactions, not so much for establishing the billing system entities such as subscription/service, charges (recurring, non-recurring), usage plans etc. There is possibly some way to utilise the "Applied Customer Billing Rate" resource but it feels to be defined for a different purpose.
Appreciate any real world experiences here to help guide our next steps with this.
Regards,
Peter Stelzer (he/him/his)
Head of BSS Application Services
D: +61 2 8381 2272 | ext +61 2 8381 2272 E: Peter.Stelzer@vocus.com.au
P: 1300 88 99 88 or +61 2 8999 8999 W: vocus.com.au
A: Level 12, 60 Miller Street, North Sydney, NSW 2060, Australia
I acknowledge and pay my respects to the
Traditional Custodians of the land on which I work.
