Cross-network billing is the process of charging an EV driver or fleet for a session that occurs on a different charging network than the one they have a contract with. It enables drivers to use multiple CPO networks with a single account (typically via an eMSP) while ensuring the correct parties are paid through roaming settlement and invoicing.
What Is Cross-Network Billing?
Cross-network billing happens when:
– A driver authenticates with credentials from Provider A (usually an eMSP)
– The charging session is delivered on Network B (a CPO network)
– Usage data and costs are exchanged between parties
– The driver is billed by Provider A, and Network B is compensated through settlement
This is a core commercial layer behind charging roaming.
Why Cross-Network Billing Matters
Cross-network billing matters because it:
– Enables “charge anywhere” access without multiple subscriptions
– Simplifies fleet expense management through consolidated invoicing
– Expands utilization for CPO networks by accepting more customers
– Creates predictable commercial settlement between market players
– Reduces friction for cross-border travel and corridor charging use cases
Without reliable billing between networks, roaming access becomes inconsistent and hard to scale.
How Cross-Network Billing Works
A simplified end-to-end flow typically looks like:
– Driver starts a session using an RFID/app/Plug & Charge credential issued by an eMSP
– The CPO’s CPMS records session details (energy, time, location, connector, timestamps)
– The session record is shared with roaming partners (often via a hub)
– Pricing rules are applied (CPO tariff and any agreed roaming fees/markups)
– A settlement process transfers value between eMSP and CPO (netting across many sessions)
– The eMSP invoices the end customer (driver or corporate account)
Who Is Involved in Cross-Network Billing
Cross-network billing usually involves multiple roles:
– CPO (Charge Point Operator) providing the charging session and meter data
– eMSP owning the customer relationship, wallet, and invoice
– Roaming hub / clearing house facilitating data exchange and settlement logic (in many models)
– Payment and finance systems handling invoicing, taxes, and reconciliation
What Data Cross-Network Billing Requires
Accurate billing depends on clean, consistent session data:
– Unique session ID and charger/connector identifiers
– Start and stop timestamps and session duration
– Energy delivered (kWh) and any time-based components
– Tariff applied and any roaming fees
– Authentication token ID and customer account mapping
– Tax/VAT fields where required for invoicing compliance
Data quality issues here directly cause disputes and revenue leakage.
Pricing Structures in Cross-Network Billing
Cross-network billing can support different tariff components:
– Energy-based pricing (€/kWh)
– Time-based pricing (€/min)
– Fixed session fees
– Idle fees or parking-related fees
Roaming agreements define how the end-user price is formed and how revenue is shared.
Cross-Network Billing vs Cross-Network Authentication
These concepts are related but different:
– Cross-network authentication: verifying the user can start a session on another network
– Cross-network billing: charging the user and settling value between providers after the session
A session can authenticate successfully but still fail financially if billing data exchange or settlement is broken.
Operational Impacts for CPOs and eMSPs
Cross-network billing affects day-to-day performance:
– Authorization and pricing transparency in the user experience
– Dispute handling (wrong tariff, missing kWh, duplicate sessions)
– Reconciliation workloads for finance teams
– Revenue assurance and payout timing for CPOs
– Reporting consistency for fleets and cost center allocation
Strong monitoring of billing exceptions helps protect charging station monetization.
Common Pitfalls
– Inconsistent tariff presentation across networks leading to customer complaints
– Delayed or missing session records causing incomplete invoicing
– Token mapping errors (wrong customer billed, corporate vs personal mix-ups)
– Duplicate sessions or mismatched timestamps creating reconciliation issues
– Weak VAT/tax handling across countries, especially for cross-border roaming
– Assuming roaming billing eliminates the need for contactless payments for ad-hoc users
Related Glossary Terms
Charging Roaming
Clearing House Billing
Clearing Houses
Cross-Network Authentication
Corporate Fleet Invoicing
Cost Center Allocation
CPMS (Charge Point Management System)
Charging Wallets
Charging Revenue Models