How TAP Is Failing Modern Roaming Settlement

Roaming traffic has exploded with 5G plans, connected cars, and enterprise IoT. Yet many operators still rely on Transferred Account Procedures (TAP), a 1990s file standard, to settle modern roaming usage. The result? Slow revenue recognition, missing data, and higher dispute rates. According to GSMA Intelligence, operators that adopt near-real-time BCE cut settlement disputes by 30 % within a year.¹ If any of the warning signs below sound familiar, it’s time to rethink your roaming settlement backbone.

Complex Deals Live in Spreadsheets

Tiered or volume-based roaming agreements rarely map cleanly to TAP fields. When teams copy rates into Excel, data silos grow and errors creep in.

Invoices Still Need Manual Reconciliation

Because TAP lacks robust validation logic, finance staff often match usage, rates, and credits by hand—burning hours and risking missed revenue.

5G and IoT Usage Doesn’t Fit TAP

5G network slicing and large IoT device fleets generate millions of micro-transactions. TAP’s record structure struggles to capture that level of detail, leaving operators unable to bill accurately.

Partners Are Requesting BCE Contracts

More roaming partners now ask to exchange Billing and Charging Evolution (BCE) messages. Declining these requests could cost you valuable traffic and revenue.

How BCE Solves the Problem

• Flexible JSON or XML records cover voice, data, SMS, 5G slices, and IoT sessions only when needed for dispute resolution.
• Automated validation rules flag rate mismatches before invoices are issued.
• Built-in dispute management keeps charge queries transparent and trackable.