TAP and NRTRDE files are the most granular record of how roaming traffic actually behaves: which partners generate it, what services it uses, how it distributes across time and geography, and what it costs to carry. Most organisations treat this data as a billing input. A smaller number have learned to treat it as a commercial intelligence source. The difference shows up in P&L.
The reconciliation-only trap
Reconciliation is necessary but it is not sufficient. Operators running settlement data through a pure reconciliation workflow can confirm that billed volumes match network records and that IOT charges are applied correctly. What they cannot surface is whether the IOT is commercially rational given current traffic composition, whether specific partner relationships are generating positive or negative contribution, or which inbound roamers are consuming disproportionate network resources at below-cost rates.
These questions are answerable from the same data. They require joining settlement records to cost ledgers, segmenting by partner and RAT, and running the analysis against current IOT schedules. The technical exercise is not complex. The organisational decision to treat roaming data as a commercial input rather than a finance function is.
Three commercial decisions the data can drive
IOT renegotiation prioritisation: per-partner margin attribution identifies which bilateral agreements are most economically misaligned and should be prioritised for renegotiation in the next negotiation cycle. Partner tier decisions: contribution margin by partner, normalised for traffic volume, provides an objective basis for partnership tier assignments that currently rely on relationship history and volume alone. Outbound steering optimisation: outbound steering rules can be evaluated against inbound margin data to identify cases where preferring a different partner improves the bilateral economic relationship.
None of these require new data sources. They require existing settlement data to be analysed at a different level of granularity and linked to commercial decision workflows that currently run independently of the analytics function.
Building the capability
Organisations moving in this direction typically start with a one-off margin attribution exercise against twelve months of settlement data. The output — which partnerships are profitable, which are marginal, and which are loss-making at current IOTs — creates the business case for ongoing analytics investment and identifies the immediate commercial priorities.
The recurring infrastructure that follows is simpler than the initial exercise: a regular join of incoming TAP/NRTRDE against a maintained cost ledger, segmented by partner, RAT, and service type, with output delivered to the commercial roaming team rather than the finance reconciliation team. The analytical work is straightforward; the change is in who uses the output and what decisions it informs.
