One customer journey, several records
Telecoms operations connect customer accounts, network activity, commercial agreements and payments. Each participant records a different view of the same business events. Timing, identifiers and correction processes do not always align.
A working integration moves records. A dependable operating system also explains discrepancies and gives someone the means to resolve them.
Make the business rules explicit
Record how airtime, commissions and adjustments are calculated. Establish which source is authoritative for each field and how late-arriving data is treated. A rule hidden in a spreadsheet still belongs to the system.
Map exceptions as carefully as routine transactions. Refunds, reversals and corrected records often reveal the assumptions that the happy path conceals.
Reconciliation is a workflow
Differences need a queue, a responsible person and an audit trail. Preserve the source evidence and the reason for each resolution. Make it possible to distinguish a timing difference from a genuine commercial dispute.
Avoid correcting the same value independently in several systems. Define how a correction propagates and how it can be checked afterwards.
Modernise around a reliable record
Before replacing an operational component, establish the outputs that must reconcile. Use those outputs to compare the old and new paths during migration. That creates a practical acceptance test grounded in business behaviour.
The lesson extends beyond telecoms: when several parties hold records of the same event, traceability is part of the product.