The Billing and Charging Evolution standard was designed in 2018 to solve a specific problem: TAP was built for voice roaming in a world where a megabyte of data transfer was an anomaly, not the unit of commerce. Eight years later, with 5G NR roaming active in most Tier-1 markets and IoT device roaming growing at double-digit rates, the structural inadequacy of TAP is no longer a planning problem. It is a live revenue visibility problem. Operators still running wholesale settlement on TAP-only infrastructure cannot see what they are owed, and they cannot negotiate from evidence.
What TAP cannot price that BCE can
TAP was designed around IMSI-based voice call records and data volume aggregates. BCE introduces per-session granularity, RAT-specific (Radio Access Technology) charging records, QoS-tier differentiation, and the ability to settle IoT device traffic — which may involve millions of low-volume connections from a single partner — at the individual device or SIM level rather than as an aggregate.
For 5G SA roaming specifically, where network slice allocation, latency tier, and uplink/downlink symmetry are all commercially relevant, TAP records offer almost no useful signal. An operator serving inbound 5G SA roamers on a network-sliced architecture and settling that traffic through TAP is effectively charging a flat rate for a differentiated service. BCE creates the accounting layer that makes QoS-tiered wholesale pricing operationally possible.
The analytics gap operators cannot afford to ignore
Kaleido Intelligence projected that nearly half of wholesale roaming revenue settlement would migrate to BCE by 2026, and the majority of participating operators have targeted 2026-2027 as their deployment year. The operators already running BCE receive settlement records with sufficient granularity to identify margin compression at the per-partner, per-RAT level. Those on TAP see only the aggregate.
The commercial consequence is asymmetric negotiating position. When an operator arrives at IOT renegotiations with per-RAT margin attribution, per-partner traffic quality data, and BCE-sourced session analytics, and the counterparty arrives with TAP aggregates, the outcome of that negotiation reflects the data asymmetry. The $2 billion in untapped IoT roaming revenue that the industry cites as a BCE opportunity is not automatic — it requires the analytics layer to identify, claim, and price it.
What the transition requires in practice
BCE deployment is not a swap of settlement files. It requires updates to mediation, rating, and clearing interfaces — and, critically, to the analytics layer that interprets the richer record structure. Operators running BCE data through legacy roaming analytics platforms built for TAP structure lose most of the signal advantage. The commercial value of BCE is only realised when the analytics layer can process per-session, per-RAT, per-QoS-tier records at the volume and granularity the standard provides.
The operators capturing the most value from BCE in 2026 are those that treated it as a commercial analytics upgrade rather than a billing infrastructure replacement. The filing format changed; the strategic question is whether the platform sitting downstream of the files can turn the richer input into margin intelligence that actually changes partnership decisions.
