SID-compliant billing, explained for telecom operators
What the TM Forum SID data model defines, and how using it changes telecom billing, the product catalog and partner integrations.
TL;DR
If your billing system invents its own words for "customer", "product", and "subscription", every integration becomes a translation project. The TM Forum SID model gives the industry a shared vocabulary, and METAVSHN's billing engine is built on it.
What SID actually is
SID stands for Shared Information/Data Model. It is a set of entity definitions and relationships maintained by TM Forum and used across the telecom industry. The ones that matter for billing:
- Party: any individual or organization (customer, partner, employee)
- Party Role: what that party is in this context (Customer, Subscriber, BillResponsible). The relation is N:N, so one party can hold many roles.
- Product Offering: what you sell
- Product: an instantiated offering for a specific subscriber
- Customer Account: the billing scope
- Customer Bill: the invoice
Why N:N Party Roles matter
A real telecom relationship rarely looks like "one customer, one product". A parent pays the bill, a child is the subscriber, the legal entity owns the contract, and the technical contact gets the outage emails. SID handles this natively: one party, many roles, and the billing engine knows which role to use for each operation.
Where this shows up in METAVSHN
- Tax mapping rules attach to product offerings, not to invoices: change them once and they apply from then on
- Booking accounts (for accounting export) live on the product, so Bexio receives correctly coded line items
- Dunning targets the BillResponsible party role, not the subscriber, so the right person gets the reminder
Further reading
- Billing engine module
- Hosted checkout, where the same product offerings drive the order flow
Frequently asked questions
- What is TM Forum SID?
- SID (Shared Information/Data Model) is a standardized data model maintained by TM Forum that defines the entities used across telecom BSS and OSS, such as customer, party, product offering, subscription, service, resource, and so on.
- Why does SID compliance matter for billing?
- A SID-aligned billing engine speaks the same vocabulary as wholesale partners, regulators, and other telecom systems. Integrations are contracts instead of bespoke mappings, which removes whole categories of reconciliation bugs.
- Does SID work for small operators?
- Yes. The value is in the vocabulary, not the scale. A 5,000-subscriber MVNO using SID-aligned entities can integrate with a Tier-1 carrier's wholesale API as cleanly as a 5-million-subscriber operator.