How 5G & IoT Break Traditional TAP Billing

5G, IoT and the Roaming Billing Crunch

5G networks and billions of IoT devices are changing roaming traffic from predictable voice calls to a flood of low-value, high-frequency data events. Transferred Account Procedure (TAP) files, telecom’s legacy roaming settlement method, were built for yesterday’s usage patterns. As volumes soar, many operators face delayed invoicing, higher processing costs and unhappy enterprise customers. The Billing & Charging Evolution (BCE) framework offers a flexible alternative that supports modern rating and charging requirements.

The Pressure Points

• Micro-transactions: IoT sensors often transmit just a few kilobytes. TAP bundles events into daily files, and does not have the ability to account for small transactions or the amount of transactions will add unnecessary load and volumes to the TAP exchange process.
• Borderless fleets: Enterprises want one aggregated roaming bill. TAP generates separate statements per partner, complicating wholesale reconciliation.
• 5G network slicing: Premium slices carry distinct QoS classes. TAP lacks any field for slice ID, blocking differentiated charging.

Data check: The GSMA predicts 37 billion active IoT connections by 2030, with over 60 % using cellular technology.

5G, IoT and the Roaming Billing Crunch

5G networks and billions of IoT devices are changing roaming traffic from predictable voice calls to a flood of low-value, high-frequency data events. Transferred Account Procedure (TAP) files, telecom’s legacy roaming settlement method, were built for yesterday’s usage patterns. As volumes soar, many operators face delayed invoicing, higher processing costs and unhappy enterprise customers. The Billing & Charging Evolution (BCE) framework offers a flexible alternative that supports modern rating and charging requirements.

The Pressure Points

• Micro-transactions: IoT sensors often transmit just a few kilobytes. TAP bundles events into daily files, and does not have the ability to account for small transactions or the amount of transactions will add unnecessary load and volumes to the TAP exchange process.
• Borderless fleets: Enterprises want one aggregated roaming bill. TAP generates separate statements per partner, complicating wholesale reconciliation.
• 5G network slicing: Premium slices carry distinct QoS classes. TAP lacks any field for slice ID, blocking differentiated charging.

Data check: The GSMA predicts 37 billion active IoT connections by 2030, with over 60 % using cellular technology. ^[1]

Why TAP Falls Short

Operators continuing to rely solely on TAP risk billing disputes, manual adjustments and strained wholesale relationships.

How BCE Solves the Problem

BCE replaces file drops with near-real-time record transfer – Usage Data Report (UDR), Billing Settlements Reports (BSR) and Detailed Data Records (DDR). Key benefits include:

1. Real-time usage visibility – partners see traffic as it happens when generated in the home network.
2. Flexible business models – supports flat rates, bundles, thresholds and multi-network aggregation.
3. Lower operational cost – no  daily TAP file generation , instead monthly aggregated settlements files.
4. Future-proof fields – slice ID, QoS class and other 5G attributes included from day one.

Implementation Pointers

• Negotiate BCE agreements: Many major players are looking for partners that supports BCE, be an early adopter to gain market advantage.
• Assess data flows: Start with services like 5G and mIOT, over time map every TAP record type to its BCE equivalent.
• Align SLAs: Agree on latency and dispute windows with partners before cut-over.
• Pilot, then scale: Start with one high-volume IoT partner to validate processes.