Skip to main content
Version: 2.4

Billing Module

Billing in tSM provides the operational layer for periodic billing documents based on customer services and configuration history. It is focused on practical cycle billing: recurring invoices, prorated charges, document generation, and invoice distribution.

Billing Scope in tSM

It can calculate monthly invoices from active services and historical configuration changes, calculate prorated charges, create multiple billing document types, and print/send invoices to customers.

Advanced Calculation with ocs.io

For advanced telco rating/calculation use cases, tSM can integrate ocs.io. The full billing UI and workflows remain in tSM, while ocs.io is used as an external calculation engine when needed.

Scope and Responsibility​

Billing is responsible for:

  • billing cycle definitions and execution periods,
  • billing document lifecycle (invoice and corrective documents),
  • billing document line composition,
  • billing document typing and status governance,
  • VAT and currency configuration for billing presentation and totals,
  • integration payload preparation (including SAP-oriented document export structures).

Key Entity Groups​

  • Billing cycles: BillingCycle, BillingCycleType, BillingCycleStatus.
  • Billing documents: BillingDocument, BillingDocumentLine, BillingDocumentType, BillingDocumentStatus, SapDocument.
  • Financial reference: Currency, VatRate.
  • Enums: BillingFrequency, CurrencyPosition, BillingDocumentAccountingType, BillingCycleStatus (value enum).

Detailed Subdocuments​

Configuration Model​

Billing follows the standard tSM configuration-first pattern:

  • code tables for type/status governance,
  • validity intervals (validityFrom, validityTo) on reference entities,
  • extensibility via chars, config, dataTags, and localizationData,
  • runtime-safe filtering using code-based foreign keys and explicit status references.

TM Forum Governance​

Billing aligns with TM Forum billing and revenue domains:

  • TMF678 Customer Bill Management for customer bill retrieval/management patterns,
  • TMF666 Account Management for billing account and receivables context,
  • TMF676 Payment Management for payment/refund notification handling,
  • TMF635/TMF767 and TMF677 patterns for usage and consumption contexts used by advanced charging implementations.

tSM applies pragmatic alignment: tSM entities remain the internal operational model, while TMF APIs are used as external integration contracts.