For a charge point operator running sites in more than one EU country, VAT stops being a checkbox and becomes an operational obligation. The rate differs, the invoice format differs, and the filing differs — and the platform underneath has to handle all of it without manual rework.
This article is a practical overview, not tax advice. Always confirm obligations with a qualified advisor in each market you operate.
VAT on charging is supplied where it happens
The starting point most operators get right: a charging session is generally treated as a supply of goods or services at the location of the charger. A session in Spain follows Spanish VAT; a session in Italy follows Italian VAT. For a cross-border network, that means your platform has to apply the correct rate per site, not per company.
Reverse charge and business customers
When you invoice a VAT-registered business in another member state — a fleet customer, a roaming partner — the reverse charge mechanism often applies: you do not charge VAT, and the customer accounts for it in their own country.
That only works if you can validate the customer’s VAT number. The EU’s VIES service exists for exactly this, and a platform that bills cross-border should validate VAT numbers against it — and keep the result as evidence.
The part that surprises operators: fiscal formats
Where it gets genuinely hard is that several countries do not just want a VAT number on a PDF. They want a specific machine-readable fiscal document, filed or cleared in a specific way:
- Italy requires electronic invoices in the FatturaElettronica XML format, cleared through the SDI exchange system.
- Spain has the Facturae electronic invoice format, with further real-time reporting obligations expanding.
- Portugal requires SAF-T accounting data export.
These are not optional formatting preferences. In the markets that mandate them, an invoice in the wrong format is not a valid invoice. An operator expanding into a new country inherits that country’s fiscal regime on day one.
What this means for platform choice
A CPMS that treats VAT as “add a percentage” will not survive a multi-country network. What the platform actually needs:
- Per-jurisdiction VAT rates applied at the site level.
- VIES validation for cross-border business customers, with the result retained.
- Reverse-charge handling for qualifying B2B supplies.
- Country-specific fiscal document generation where it is mandated.
- A monthly VAT reporting output the finance team can file against.
How Sparqly handles it
Sparqly’s billing layer generates branded invoices, receipts, and fiscal documents through a document template engine. An EU VAT module adds VIES validation with caching, reverse-charge handling, country fiscal formats including the Italian SDI electronic invoice, and periodic VAT reporting. It is available as a marketplace module, so operators turn it on for the markets that need it.
VAT will never be the exciting part of running a charging network. But in the EU, getting it wrong is one of the fastest ways to turn an expansion into a compliance problem — so the platform has to carry it.
