EV Charging Invoicing: The Payments Problem Hiding Inside an Energy Business

The conclusion first: EV charging invoicing is, in commercial reality, a payments and tax compliance problem dressed up as an energy transaction. The industry has built up a set of conventions around who issues the invoice for a public charging session — usually the Charge Point Operator, sometimes the Demand Partner — and those conventions are workable when the Merchant of Record is the CPO selling its own energy. They become structurally fragile, expensive, and risk-laden when the Merchant of Record is a Demand Partner with users charging across multiple jurisdictions on infrastructure they do not own. NetworkCore is the platform that absorbs the entire EV charging invoicing layer — Merchant of Record, multi-jurisdiction VAT, fee-type tax classification, audit infrastructure — so that Demand Partners and CPOs each operate inside their proper commercial role without inheriting a compliance function neither of them was built to carry.

Why EV charging invoicing is a payments problem, not an energy problem

The instinctive way to think about a charging session is energy delivery. A vehicle plugs in. Electricity flows. The driver pays for the kWh consumed. This frame is correct at the physical layer and almost completely useless for understanding the commercial layer that actually has to settle behind the session.

A public charging session, viewed properly, is a multi-party financial transaction. The driver pays through whatever interface they used to start the session — a charging app, a fleet account, an OEM mobility programme dashboard, a fintech wallet, a roaming card. Money is captured at one point in the chain and has to flow correctly to several parties: the CPO that delivered the energy, the Demand Partner whose platform routed the driver to the station, the platform sitting between them, and the tax authorities of the jurisdiction where the session occurred. Each leg of that flow has its own commercial terms, its own currency considerations, its own settlement timeline, and its own invoicing obligations.

This is where EV charging invoicing stops being an energy problem and becomes a payments problem. The question is not "what does electricity cost?" — that is settled by the CPO's public tariff. The question is "who is the legal seller of record for this transaction, who collects which tax, who issues which invoice to whom, in which format, in which jurisdiction, on what timeline?" These are payments and tax questions, not energy questions. They are governed by financial regulation, not by electricity regulation. And the participants who underestimate this distinction routinely build operational positions that crack open the moment they move from a single-country deployment to a multi-country one.

What "Merchant of Record" actually means in EV charging

The Merchant of Record — MoR — is the legal seller responsible for a transaction. The MoR is the entity that:

• Captures the payment from the customer
• Collects and remits VAT or sales tax to the tax authority
• Issues the legal invoice for the transaction
• Holds the audit and compliance responsibility for the financial flow
• Carries the customer-facing legal relationship for the sale

In EV charging invoicing, the Merchant of Record is, in most current arrangements, the Charge Point Operator. The CPO sells electricity to the driver, captures the payment, charges the appropriate VAT, issues the invoice, and remits the tax in the jurisdiction where the station is located. This is the cleanest possible MoR position — the seller of record is the seller of the underlying service, in the country where the service is delivered, with the tax authority responsible for that country.

This works. It is operationally simple. It is structurally clean. It is the configuration the industry has defaulted to because it is the version that does not raise difficult questions.

The complications begin when the Merchant of Record is not the CPO.

When Demand Partners become the Merchant of Record — and why it gets complicated

In a number of current commercial arrangements, the Demand Partner becomes the Merchant of Record. This typically happens when the Demand Partner negotiates wholesale pricing with the CPO, marks up the price for its end users, and presents itself as the seller to the driver. The CPO invoices the Demand Partner at the wholesale rate. The Demand Partner invoices the driver at the retail rate. The Demand Partner carries the MoR responsibility for the sale to the end customer.

This is a workable model in narrow circumstances. It is a problematic model in most commercial realities, for reasons that compound the further the Demand Partner expands.

Multi-jurisdiction tax exposure. The moment a Demand Partner becomes the MoR for charging sessions across multiple countries, it inherits VAT or sales tax registration obligations in each of those countries — every market where its users charge. Each jurisdiction has its own rate, its own invoicing format requirements, its own audit retention rules, its own filing schedule, and its own enforcement posture. A single user charging in five countries triggers compliance obligations in five tax authorities for the Demand Partner that booked the transaction as MoR.

Fee-type tax complexity. As covered in detail in EV Charging VAT Explained, a single charging session can include energy, initiation fees, idle fees, parking fees, and reservation fees — each of which can attract a different VAT rate within the same invoice in the same jurisdiction. The MoR is responsible for applying every rate correctly, on every fee type, for every session, in every country. The complexity scales with the number of markets multiplied by the number of fee structures the CPO networks use.

Real-time invoicing and certification regimes. Several jurisdictions require electronic invoicing certification at the moment of transaction — the invoice must be validated by the tax authority or an authorised intermediary in real time, before it is legally valid. The MoR is responsible for integrating into these regimes, maintaining the certification connection, and producing legally valid invoices for every transaction. Failures here are not paperwork issues. They are tax non-compliance issues, with proportional consequences.

Customer-facing legal exposure. The MoR is the legal seller. Disputes, refunds, chargebacks, consumer protection complaints, and any legal action arising from a charging transaction land on the MoR's balance sheet. A Demand Partner that became MoR to capture additional margin has also accepted the legal liability that comes with being the seller of record for every transaction it intermediated.

Operational overhead. All of the above translates into ongoing operational work — tax registrations to maintain, filings to submit, audit responses to prepare, invoice formats to keep current as regulations change. None of this is what the Demand Partner was built to do. None of it scales linearly with the platform's growth — it scales geometrically with the number of jurisdictions involved.

For a Demand Partner that is, at its core, a fleet platform, an OEM mobility programme, a fintech wallet, an insurance product, or a super-app — the MoR position on charging sessions is not a feature. It is a liability that the company acquired to participate in EV charging invoicing at all, because the alternative arrangements available in the market did not offer a cleaner path.

What "fine when it is the CPO" actually depends on

The reason the CPO-as-MoR configuration works is structural, and naming the structural reasons clarifies why the configuration breaks when it is not the CPO.

The CPO is the legal seller of the underlying service. Electricity is genuinely flowing from their station to the vehicle. The transaction is a sale of energy in the country where the station is located, governed by the energy and consumption tax regulations of that country. The MoR position aligns with the commercial reality.

The CPO's tax obligations are anchored in one jurisdiction — the country where the station operates. The CPO is, by virtue of operating physical infrastructure, already registered in that jurisdiction and already managing the compliance posture for its broader business. Adding charging sessions to that compliance footprint is incremental, not structural.

The CPO's pricing is the pricing visible to the driver. There is no markup chain to defend. The price displayed at the charger is the price on the invoice. Tax is calculated on the actual transaction value, not on a retail price reconstructed from a wholesale price plus a Demand Partner's margin. Audit defence is straightforward.

When the MoR is the CPO, EV charging invoicing is a properly aligned commercial transaction with a properly anchored tax obligation in a properly defined jurisdiction. The system works because the legal, commercial, and operational realities all line up.

When the MoR is the Demand Partner — particularly a multi-country Demand Partner that does not own physical infrastructure in any of the markets it serves — none of these alignments hold. The Demand Partner is the legal seller of an energy product it did not produce. Its tax exposure is multi-jurisdictional in ways its core business is not. Its pricing involves a markup chain that has to be defended in every audit. The system works in narrow cases and fails to scale in broader ones.

This is the point at which the EV charging invoicing architecture needs to be reconsidered structurally. Most platforms reach this point during their second or third country expansion, after they have already absorbed the operational consequences of a configuration that worked in one market and quietly broke when extended.

How NetworkCore handles the Merchant of Record question

NetworkCore is built so that the EV charging invoicing layer is absorbed by the platform infrastructure rather than delegated back to the Demand Partner.

The mechanics of how NetworkCore takes on the MoR responsibility — across jurisdictions, across fee types, across the regulatory regimes each market imposes — are handled inside the platform's regulated infrastructure. We do not detail those mechanics here, partly because they are operational specifics that vary by market and partly because the value to participants is not in the mechanism itself but in the outcome it delivers. What participants need to understand is the outcome, and the outcome is significant.

Demand Partners on the network do not carry MoR liability for the charging transactions their users complete through the integration. The legal seller-of-record position for sessions flowing through NetworkCore sits in the appropriate place within the platform's infrastructure for each jurisdiction the session occurred in. The Demand Partner is the distribution channel. It earns a defined revenue share per session. It does not register for VAT in every country its users charge in. It does not file in jurisdictions where it has no other commercial presence. It does not carry the customer-facing legal exposure for the energy sale. It does not absorb the operational overhead of multi-country tax compliance. This is what makes the broader Add New Revenue Streams framing actually work in practice — the revenue layer is genuinely passive because the compliance layer beneath it is held by the right entity.

CPOs on the network operate inside the configuration that was always commercially clean for them. The CPO sells its energy at its public tariff. The financial flow is structured so that the CPO's compliance obligations align with the jurisdiction where its infrastructure operates. The platform handles the multi-Demand-Partner side of the EV charging invoicing layer without disrupting the CPO's existing tax and operational posture.

The driver receives correctly issued invoicing for every session. The invoice format complies with the requirements of the jurisdiction where the session occurred. The VAT or applicable consumption tax is applied correctly per fee type. The legal seller is properly identified. The audit trail is complete. The driver does not see any of the underlying complexity — they see a clean transaction record for the charging session they completed.

The compliance and audit infrastructure is centralised inside the platform. Multi-jurisdiction VAT calculation, e-invoicing certification where required, retention of audit-ready records, AML and KYC processes for the financial flow, transaction monitoring — all of this lives inside NetworkCore's regulated infrastructure rather than being replicated across every Demand Partner connecting to the platform.

This is the EV charging invoicing value proposition in operational terms. The complexity does not disappear — it is real and it grows with the number of markets involved. What changes is who carries it. NetworkCore carries it. The Demand Partner does not. The CPO continues operating in the configuration that was always cleanest for it.

What this means commercially for participants

For Demand Partners, the absorption of MoR responsibility into the platform layer changes the EV charging invoicing picture from a multi-jurisdiction compliance liability into a passive revenue stream. The platform's user base monetises through charging activity. The financial flow is handled. The legal seller-of-record position is held appropriately. The operational footprint is zero.

For CPOs, the architecture means the CPO's own MoR position is preserved exactly as it should be — selling its energy, in its jurisdiction, at its public tariff, with its own compliance footprint. The platform sits beside the CPO's existing operations rather than displacing them, adding distribution without inheriting the CPO's invoicing relationships in any way that would create operational friction.

For the broader market, the EV charging invoicing problem is finally addressable as infrastructure rather than as an ongoing series of bilateral compliance projects. The complexity is real. It does not vanish. It is held by the entity built to hold it, which is what regulated financial infrastructure is for.

The decision worth taking seriously

If your platform is currently the Merchant of Record for charging transactions across multiple jurisdictions — or considering becoming one as part of an upcoming charging integration — the EV charging invoicing architecture beneath that decision is worth examining carefully before the operational consequences compound. The configuration that works in one country does not extend cleanly to four. The exposure that is invisible in early-stage deployment becomes a board-level conversation when a tax authority audit lands.

The alternative is integrating with a platform that handles the EV charging invoicing layer as part of the infrastructure — with the legal seller-of-record position properly anchored in each market, multi-jurisdiction compliance absorbed into the platform's regulated entity, and the Demand Partner's role reduced to what it should always have been: distribution, not compliance.

Companion reading: EV Charging VAT Explained covers the fee-type tax mechanics; EV Charging Revenue Model sets out the broader transaction framing; Who Gets Paid in EV Charging? explains the financial flow mechanics across the value chain.

NetworkCore is built for that configuration. The transactions flow through the platform. The invoicing is handled. The MoR question is settled correctly per session per jurisdiction. The Demand Partner monetises its user base without acquiring the regulatory weight that has been quietly accumulating in the industry's current invoicing arrangements.

Reach the team at networkcore.org to discuss what the EV charging invoicing picture would look like for your platform's specific position.