Finance

Structured E-Invoicing and ViDA Compliance

Issue legally structured e-invoices in every market you operate — EN 16931 semantics, UBL 2.1 for Peppol, CII for Factur-X and ZUGFeRD, and a cross-border VAT engine that knows where the supply happened.

Enable This Extension Book a Demo

The Problem

Why does this extension exist?

One country after another is making structured e-invoicing mandatory, and each one wants a different envelope: Peppol UBL here, Factur-X there, a national portal somewhere else. A PDF attached to an email stops being an invoice. If your charging platform can only produce PDFs, every new mandate becomes a project — and a cross-border charging session raises a VAT question nobody in the billing team wants to answer twice.

The Solution

What you get

EN 16931 semantic invoice model, with the monetary totals computed in full rather than copied from a PDF
UBL 2.1 output conformant to Peppol BIS Billing 3.0
UN/CEFACT CII output for Factur-X and ZUGFeRD hybrid invoices
Cross-border VAT engine: place of supply, reverse charge and intra-community treatment
EN 16931 and Peppol business-rule validation before anything is dispatched
Pluggable Peppol Access Point dispatch, so changing provider does not mean changing your invoicing
Invoices built straight from charging CDRs and sessions, with a log of every dispatch

🎯 Who is this for?

CPOs and eMSPs invoicing across EU borders, operators facing a national e-invoicing mandate, and finance teams preparing for ViDA rather than reacting to it.

Enable This Extension Browse All Addons

🔌 Modular by design

Enable or disable per tenant. Pay only for what you use. All addons integrate seamlessly.

Key Capabilities

Everything included

EN 16931 Semantics

The invoice is built as a semantic model, not as a rendering. Totals, taxes and allowances are computed from the lines, so what you dispatch is arithmetically defensible.

UBL and CII Output

The same invoice leaves as UBL 2.1 for Peppol BIS Billing 3.0, or as UN/CEFACT CII for Factur-X and ZUGFeRD. The format is a setting, not a rebuild.

Cross-Border VAT Engine

Place of supply, reverse charge and intra-community treatment are decided per invoice from the parties and the supply — with the rates you configured per country and operation type.

Validated Before Dispatch

EN 16931 and Peppol business rules run before the invoice leaves. A rejected invoice found on your side costs minutes; found at the access point it costs days.

Pluggable Dispatch

The Peppol Access Point is a provider you choose and can replace. Your invoicing does not have to be rebuilt because a contract changed.

Straight from Charging Data

Invoices are constructed from CDRs and sessions, not re-keyed from an export. The line that says 42.6 kWh is the line the charger produced.

Use Cases

See it in action

How operators around the world can use this extension to solve real problems and grow their business.

A German mandate met without a project

A customer in Germany asks for ZUGFeRD. The invoice already exists as an EN 16931 model, so the CII output is switched on and the next invoice arrives in the format their accounts payable expects — with no change to how charging is billed.

A Dutch driver charging in Belgium

A cross-border session raises the question of where the supply happened. The VAT engine applies place-of-supply and reverse-charge rules from the parties involved, and the invoice carries the treatment it applied so the accountant can check it.

A rejection that never reaches the access point

A missing buyer reference would have been rejected by Peppol. Validation catches it before dispatch, the field is filled, and the invoice goes out clean the first time instead of coming back three days later.

Simulated Case Study

eMSP moves 100% of B2B invoicing to structured formats ahead of the mandate

An eMSP invoicing corporate customers in six countries sent PDFs by email and handled two national formats by hand. Structured e-invoicing turned the same billing run into UBL for Peppol customers and CII for the German ones, with the VAT treatment decided per invoice. Rejections at the access point fell to near zero because validation now runs first, and the finance team stopped tracking mandates as separate projects.

100%

Of B2B invoices structured

Output formats from one model

Countries invoiced from one run

≈0

Rejections at the access point