Magento 2 EU E-Invoicing (ZUGFeRD / XRechnung / Factur-X)

Key Features

ZUGFeRD hybrid invoices as PDF/A-3 with embedded EN 16931 XML, generated from the standard Magento invoice flow

XRechnung XML output for German B2G (public-sector) buyers, conformant to the German CIUS of EN 16931

Factur-X support for France, including selectable profiles (MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED)

Structured XML physically embedded inside the PDF via PDF/A-3 file attachment, so one file is both human- and machine-readable

Leitweg-ID and buyer reference (BT-10) fields added to the order and invoice, captured at checkout and mapped into the XML

Observer on sales_order_invoice_save_after auto-generates the e-invoice when an invoice is created in admin or via API

Plugin/interceptor on the core invoice PDF renderer so your existing branded invoice layout is preserved

Store-scoped System Configuration (system.xml) for format, profile, seller VAT/legal identifiers, and tax category mapping

Admin 'Regenerate E-Invoice' controller action plus optional cron for batch (re)generation across historical invoices

REST and GraphQL endpoints to fetch the generated PDF/A-3 and raw XML for ERP, PEPPOL access point, or customer-portal pull

Dedicated admin ACL resources so only authorized roles can view, configure, or regenerate e-invoices

Schema validation of the XML against the EN 16931 / format XSD before the PDF is finalized, with errors surfaced in admin

Multi-store / multi-website aware: per-store seller identity, tax mapping, and default format

Works on both Magento Open Source and Adobe Commerce, compatible with the configured Magento 2.4.x line

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

European e-invoicing has moved from "nice to have" to legally mandatory. Public-sector buyers in Germany require XRechnung; France's reform makes Factur-X the national hybrid standard; and ZUGFeRD is the cross-border PDF/A-3 format that embeds machine-readable XML inside a human-readable invoice. Magento 2 core and the default Open Source PDF invoice generator produce none of these — they emit a flat, non-compliant PDF with no EN 16931 structured payload.

This is a build-to-order extension, not an instant Marketplace download. ECOSIRE scopes your invoicing rules, builds the module under app/code/Ecosire/EuEInvoicing, installs it on your Adobe Commerce or Magento Open Source instance, and supports it after go-live.

Architecturally it is a clean Magento 2 module. An observer on sales_order_invoice_save_after (and an admin "Regenerate E-Invoice" action) triggers a service-contract generator that builds an EN 16931-conformant XML tree, validates it, and embeds it into a PDF/A-3 container — producing the hybrid file ZUGFeRD and Factur-X require. A plugin/interceptor on the core invoice PDF renderer wires the structured XML into the existing document so your branded layout is preserved. Format selection (ZUGFeRD vs XRechnung vs Factur-X, and profile level such as BASIC/EN 16931/EXTENDED) is driven from a store-scoped System Configuration section under Stores → Configuration, defined in system.xml with values resolved through Magento's config service.

New Leitweg-ID and buyer reference (BT-10) fields are added to the order/invoice so German B2G routing IDs are captured at checkout and carried into the XML. Generated invoices are exposed over REST and GraphQL for ERP/portal retrieval, gated behind dedicated admin ACL resources, with optional cron for batch regeneration. Honest scope: ECOSIRE builds the e-invoice document and delivery hooks — connection to a specific national platform (PPF/PDP in France, a PEPPOL access point, or your e-mail/portal flow) is confirmed during scoping and quoted if it extends beyond document generation.

What you get

A custom Magento 2 module installed under app/code/Ecosire/EuEInvoicing (or delivered as a Composer package), wired via di.xml, events.xml, system.xml and acl.xml

Working ZUGFeRD / XRechnung / Factur-X generation on your invoices, validated against the relevant XSD before delivery

Leitweg-ID and buyer-reference data capture wired into your checkout and order/invoice entities

REST + GraphQL endpoints documented for retrieving the PDF/A-3 and XML payloads

Installation on your staging then production environment, including setup:upgrade, DI compile and static-content deploy

Configuration handover: a short runbook covering the System Configuration fields, ACL setup, and cron schedule

Post-go-live support window plus version-compatibility maintenance for your Magento 2.4.x line under the agreed plan

Who this is for

German B2G supplier on Magento

A merchant invoicing public-sector buyers who legally require XRechnung with a valid Leitweg-ID, and whose current Magento PDFs are rejected as non-compliant.

French merchant preparing for the e-invoicing reform

A France-based seller that must issue Factur-X hybrid invoices at the correct EN 16931 profile and route them through an approved platform as the national mandate phases in.

EU B2B exporter needing cross-border hybrid invoices

A company selling across Germany, France and the wider EU that wants one ZUGFeRD PDF/A-3 file that is both human-readable and machine-processable by customers' AP systems.

How Magento 2 EU E-Invoicing (ZUGFeRD / XRechnung / Factur-X) Compares

Criterion	ECOSIRE	Custom Build	Competitor
ZUGFeRD / XRechnung / Factur-X output out of the box	Included	Partial support	Partial support
Hybrid PDF/A-3 with embedded EN 16931 XML	Included	Partial support	Partial support
Leitweg-ID / buyer-reference capture for German B2G	Included	Partial support	Partial support
Built, installed and supported for your specific Magento instance	Included	Partial support	Not included
REST + GraphQL retrieval with admin ACL	Included	Partial support	Partial support
XSD validation of output before delivery	Included	Partial support	Partial support
Adapts to your tax mapping, multi-store and branding	Included	Included	Partial support
Ongoing updates as EU mandates and profiles change	Included	Not included	Partial support

Frequently Asked Questions about Magento 2 EU E-Invoicing (ZUGFeRD / XRechnung / Factur-X)

How long until it's delivered, and how does the build-to-order process work?

After purchase we run a short scoping call to confirm your Magento edition (Open Source vs Adobe Commerce), 2.4.x version, required formats and profiles, and your delivery/routing target. Typical delivery is around 2 to 4 weeks depending on complexity — we build the module, validate output against the relevant XSD on a sample of your real invoices, install on staging for your sign-off, then deploy to production. This is a custom build installed by ECOSIRE, not an instant Adobe Commerce Marketplace download.

What about ongoing support and updates after go-live?

Every build includes a post-go-live support window for fixes and questions, plus version-compatibility maintenance so the module keeps working across Magento 2.4.x patch and minor upgrades. Because EU e-invoicing rules and EN 16931 CIUS profiles evolve (especially the French reform timeline), we offer an ongoing maintenance plan to update XML mappings, profiles and validation as the standards change. Support terms are confirmed in your quote.

Does this replace my existing branded Magento invoice PDF?

No. We use a plugin/interceptor on the core invoice PDF renderer and PDF/A-3 embedding, so your existing layout and branding are preserved — the structured XML is attached inside the same file. The output is one hybrid invoice that humans can read and AP systems can parse.

Can the generated invoices be pulled into our ERP or a PEPPOL access point?

Yes. The module exposes both REST and GraphQL endpoints, gated by admin ACL, to retrieve the PDF/A-3 and the raw XML. That lets your ERP, a PEPPOL access point, or a customer portal fetch invoices programmatically. Connecting to a specific national platform (such as a French PDP/PPF or a particular PEPPOL provider) is scoped and quoted if it goes beyond document generation.

Will it work on Adobe Commerce as well as Magento Open Source, and across multiple stores?

Yes. The module is built against standard Magento 2 service contracts and APIs, so it runs on both Adobe Commerce and Magento Open Source on your 2.4.x line. Configuration is store-scoped via system.xml, so each website or store view can carry its own seller identity, default format, and tax mapping.