Unified roaming billing is the process of consolidating and standardizing billing for roaming EV charging sessions across multiple charging networks, so costs, invoices, and settlement data are handled in a consistent way—despite different CPOs, tariffs, tax rules, and data formats. It enables drivers or fleets to charge across partner networks using a single contract (via an eMSP) while ensuring all roaming sessions are correctly priced, reconciled, invoiced, and settled.
What Is Unified Roaming Billing?
Roaming allows an EV driver to use chargers operated by different CPOs with one access method (app, RFID, Plug & Charge, or account). Unified roaming billing makes the back-end financial process consistent by:
– Collecting roaming session records from multiple CPOs
– Normalizing them into a standard billing schema
– Applying contract pricing rules (retail pricing for the customer)
– Managing B2B settlement (wholesale pricing between CPO and eMSP)
– Producing consolidated invoices and reports
It is “unified” because it reduces fragmented billing from many networks into one predictable invoice and reporting layer.
Why Unified Roaming Billing Matters
Roaming introduces complexity that scales with every additional partner network. Unified billing is critical for:
– A consistent driver or fleet experience (one invoice, one receipt format)
– Lower admin workload for fleets and finance teams
– Fewer billing disputes caused by tariff mismatches and missing data
– Correct tax handling (VAT, country-specific invoice requirements)
– Accurate margin control (retail vs wholesale spread, fees, FX where relevant)
– Stronger auditability and transaction reconciliation across partners
How Unified Roaming Billing Works
A typical workflow includes:
– Driver initiates a roaming session using an eMSP credential
– CPO authorizes the session and records the charge
– After completion, the CPO generates a Charging Data Record (CDR)
– CDR is exchanged to the eMSP via OCPI (or via a roaming hub/intermediary)
– eMSP validates and normalizes the CDR (IDs, timestamps, kWh, location, tariff references)
– Retail price is calculated for the end customer (fleet/driver contract)
– Wholesale settlement is calculated for the CPO based on roaming agreement
– Exceptions are flagged for review (missing meter values, inconsistent tariffs, time zones)
– The eMSP issues a consolidated invoice (and exports to finance systems)
– Periodic settlement occurs between eMSP and each CPO (netting, credit notes, disputes)
Key Data Elements for Accurate Roaming Billing
Unified roaming billing depends on consistent identifiers and high-quality data:
– Unique session ID and contract ID
– Start/stop timestamps with correct time zone handling
– Metered kWh and any time-based components
– Tariff version reference (and visibility into idle/minimum fees)
– Location identifiers (EVSE ID, connector ID)
– VAT/tax fields (country, invoice rules, B2B vs B2C classification)
– Currency and FX handling (if cross-border)
– Status codes and reason fields for failed or partial sessions
Common Challenges and Failure Modes
– Tariff mismatches: CPO tariff displayed vs tariff applied vs eMSP retail pricing
– CDR latency: invoices can’t be finalized until CDRs arrive and settle
– Time drift and time zones: billing errors for time-based fees and idle fees
– Rounding differences: kWh precision and billing granularity vary by platform
– Refunds and chargebacks: unclear responsibility across eMSP/CPO support chains
– Regulated metering: some markets require fiscal-grade metering and strict receipt formats
– Partner disputes: missing sessions, duplicated CDRs, or “out of contract” charging
Best Practices for Unified Roaming Billing
– Use standardized integrations (OCPI) with strict schema validation
– Implement strong transaction reconciliation rules and exception workflows
– Store tariff versions and apply deterministic pricing per session
– Maintain tolerances for rounding and metering resolution (documented and consistent)
– Separate “preliminary” vs “final” billing states until settlement data is confirmed
– Create clear dispute SLAs with roaming partners (timelines, evidence required)
– Monitor data quality KPIs (missing CDR rate, mismatch rate, average CDR latency)
Related Glossary Terms
Roaming payments
OCPI
OCPI roaming
Charging Data Record (CDR)
Transaction reconciliation
Interoperability billing
Per-kWh billing
Idle fees
Unified fleet billing
Payment gateway integration