EMSP: Self-Managed Outbound Roaming

Self-Managed Outbound Roaming lets you set up your own roaming connections directly with charge point operators (CPOs), so your drivers can charge on their networks on terms you've agreed. You then track all usage, connections, parties, tariffs and sessions for those connections in Monta Hub.

This is different from Outbound Roaming explained, where Monta provides and manages the CPO connections for you. New to roaming? Start with the Roaming overview.

Quick answers

Question	Answer
Who pays the CPO?	You do, directly, against the CPO's invoice. Monta does not settle with the CPO on your behalf.
Where does my driver's payment go?	Into your operator wallet. For every session on a self-managed outbound CPO, the driver's payment lands in your wallet, so you can settle with the CPO when they invoice you.
Who issues the driver's receipt or invoice?	You do. As the reseller of these sessions, you are responsible for any invoice your drivers need.
Can I see sessions and CDRs?	Yes. Every session is listed in Hub, close to real time, with its CDR data.
What do my drivers pay?	The CPO's tariff plus VAT plus your app's roaming fee.
Do I need my own ID?	Yes. You need an eMSP party ID (Operator ID) registered to your company.
Does Monta write the agreement with the CPO?	No. The agreement is between you and the CPO. See the checklist below.

Key terms

• Party — the roaming CPO you're roaming with, identified by its party ID (for example ES*ABC).
• Connection — the actual OCPI connection. A single connection can carry many parties.
• CDR — the raw Charge Detail Record for a session. It is raw session data, not an invoice.
• eMSP party ID (Operator ID) — the ID that identifies you as the provider of your drivers' charge keys (for example ES*XYZ).

Where to find it

In Hub, go to EMP / Fleet → Outbound roaming (/roaming/outbound) and open the Self-Managed Roaming tab. It has the tabs Overview, Connections, Parties, Tariffs and Sessions. Settlement is not available for Self-Managed Roaming.

Before you start

Have these ready before you contact the Monta Roaming team:

1. Your eMSP party ID. You need an Operator ID registered to your company with the national registry (in Spain, for example, the national access point). A party ID you already hold as a CPO can usually be used as an eMSP ID too, but check with your registry that it covers the eMSP role. See How do I register an Operator ID? You can see the ID Monta holds for you under Operator settings → General → Company details → Roaming operator ID.
2. A signed agreement with the CPO. See "What to put in your agreement with the CPO".
3. A CPO on OCPI 2.1.1 or 2.2.1. These are the only versions supported.
4. The CPO's Tariffs module. Without it, the CPO's charge points can still appear, but there is no price to show your drivers before they charge. Ask the CPO to enable it.
5. A technical contact at the CPO for the connection set-up.

Setting up the connection

Self-Managed outbound connections are established together with the Monta Roaming team:

1. Agreement — sign an agreement directly with the roaming CPO. This is made between you and the CPO, outside the Monta platform.
2. Bring in the Monta Roaming team — open a shared channel between you, the CPO and the Monta Roaming team.
3. Prerequisites — the CPO must be on OCPI 2.1.1 or 2.2.1 with the Tariffs module (see above).
4. Connection — the Monta Roaming team establishes the Self-Managed outbound connection with the CPO and links your party ID to it. The Monta Roaming team also sets up how payments for these sessions are handled on your account.
5. Confirmation — once live, the connection appears under Outbound roaming → Self-Managed Roaming → Connections and Parties with the status Connected. Before that, the status is Pending.

To get started, contact the Monta Roaming team.

What to put in your agreement with the CPO

Monta does not draft or sign this agreement. It should cover at least:

• The parties: both legal entities and both party IDs (your eMSP ID and the CPO's ID).
• Technical scope: OCPI version and modules (Locations, Tariffs, Sessions, CDRs, Tokens, Commands).
• Pricing: energy, time, session-start and idle fees; currency; whether prices include VAT; how much notice the CPO gives before changing prices.
• Invoicing and payment: CDRs as the basis for invoicing, invoice frequency, payment terms, and a deadline for disputing a CDR.
• How drivers start a session: RFID card, app, or both.
• Support: contacts on both sides, how incidents are escalated, and expected availability.
• Data protection: GDPR obligations and a data processing agreement where needed.
• Liability for failed sessions, incorrect CDRs and unpaid sessions.
• Term and termination, including notice periods and how open sessions and final invoices are handled.

Verify the tariff and run a test session

Once you're connected to the CPO, you can review the tariff the CPO has sent under Tariffs → Received or in your WL App (White-Label App) to confirm the correct price has been applied before your drivers charge.

You can also run a test session at one of the CPO's charge points to verify the price in practice. The session and its CDR are made available in near real time, so you can check the tariff is correct rather than waiting for the first invoice to surface a problem.

What your drivers pay

Your driver pays the tariff the CPO sends via OCPI, plus VAT, plus the roaming fee set for your app.

How you pay the CPO

A CDR is not an invoice — it's the raw session data for each charge. The CPO sends you a separate invoice. Use Sessions → Export CDR batch to reconcile the CPO's invoice against the sessions Monta recorded. The export is emailed to you and covers up to 31 days, for all CPOs or one CPO.

Invoicing your drivers

You are the reseller of these sessions, so you are responsible for any invoice your drivers or business customers need, and for applying the correct VAT treatment.

See your data and download CDRs

Under Roaming → Outbound Roaming → Self-Managed Roaming you'll find:

• Overview — "Where are your drivers charging?": your drivers' energy delivered, spend and unique keys/contracts, plus energy per CPO, energy share by CPO, country share and top CPOs. Choose Last 7, 30 or 90 days, Year to date, All time, or a custom range. Spend excludes Hubject sessions.
• Connections — your connections with partner, role, OCPI version, status, bilateral agreement and exclusivity. This list is read-only. Monta sets connections up for you.
• Parties — the CPOs you roam with: party ID, name, connection, sessions in the last 30 days, locations, AC and DC EVSEs, and status.
• Tariffs (where enabled) — shows the tariffs each CPO has sent you: base price excl. VAT, validity (Active, Scheduled or Expired), EVSEs and last update.
• Sessions — every session your drivers run on those CPOs. Open a session to see its details. Use Export CDR batch to have a CDR file emailed to you for reconciliation or dispute handling. A batch covers up to 31 days.