ZUGFeRD / XRechnung / Factur-X E-Invoicing for Magento 2

Key Features

ZUGFeRD 2.x output as an EN 16931-conformant PDF/A-3 hybrid invoice with the CII XML embedded as a file attachment

XRechnung (German B2G) generation in standards-compliant UBL or CII syntax

Factur-X (French) hybrid invoice support sharing the same EN 16931 semantic engine

Leitweg-ID and B2G routing fields added to customer, address and order entities for public-sector invoices

XML embedding into both Magento's native PDF renderer and common third-party PDF invoice extensions

EN 16931 XML schema and Schematron validation of every generated document before it is attached

Observer/plugin on invoice creation (sales_order_invoice_save_after / invoice service contract) so e-invoices generate automatically

Admin configuration with a dedicated ACL resource (system.xml) so only authorized roles manage e-invoicing settings

Mapping layer from Magento tax classes, payment terms and master data into the EN 16931 semantic model

Multi-store / multi-website seller profile configuration (VAT ID, legal name, address per store view)

REST and GraphQL accessibility so headless and PWA storefronts trigger the same invoice generation path

Optional cron job to (re)generate or batch-export e-invoices for orders created before install

Profile selector (ZUGFeRD / XRechnung / Factur-X) driven by buyer type and country

Generated XML and PDF/A-3 stored against the order for audit and re-download

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

This is a build-to-order extension, not an instant Marketplace download. ECOSIRE builds, installs and supports a custom Magento 2 module on your store to meet the EU's mandatory structured e-invoicing rollout (Germany, France and the EN 16931 standard, phasing in 2025–2028).

The module ships as a standard package under app/code/Ecosire/EInvoicing (or via Composer), wired through di.xml, with an admin ACL resource so only authorized roles configure it. When a Magento invoice is created — through the admin, REST/GraphQL, or a third-party flow — an observer on sales_order_invoice_save_after (or a plugin on the invoice service contract, depending on your setup) generates the structured document and attaches it to the PDF.

You get three output profiles from one engine: ZUGFeRD 2.x as an EN 16931-conformant PDF/A-3 hybrid with the CII XML embedded as a file attachment; XRechnung (German B2G) as standards-compliant UBL or CII; and Factur-X (the French equivalent of ZUGFeRD) hybrid output. Leitweg-ID and B2G routing fields are added to the customer/address and order so public-sector invoices carry the correct routing identifier.

Embedding works against both Magento's native PDF renderer and common third-party PDF invoice extensions — we adapt the integration to whatever you actually run, on Magento Open Source or Adobe Commerce. We map your tax classes, seller/buyer master data, payment terms and line items into the EN 16931 semantic model, then validate the generated XML before it leaves the store.

Because it's built to order, scope, tax edge cases and your exact PDF pipeline are confirmed up front. We don't pretend a generic download fits every German, French or EU merchant — it doesn't, which is exactly why this is custom work with a real lead time and named support.

What you get

A custom Magento 2 module (app/code/Ecosire/EInvoicing or Composer package) installed on your Open Source or Adobe Commerce instance

Configuration of ZUGFeRD 2.x, XRechnung and Factur-X profiles, seller master data and Leitweg-ID / B2G routing per store view

Integration of XML embedding with your actual PDF invoice pipeline (native or third-party)

EN 16931 validation wired into the generation flow plus sample validated invoices for your data

Admin ACL, system configuration and a short admin user guide

Knowledge-transfer session plus a defined post-launch support and update window

Who this is for

German B2G supplier

Sells to public-sector buyers and must issue XRechnung with a valid Leitweg-ID and correct routing fields, not just a PDF.

French / cross-border EU merchant

Needs Factur-X (and ZUGFeRD for German partners) to stay ahead of the 2025-2028 structured e-invoicing mandates across the EU.

Finance / ERP lead on Adobe Commerce

Wants embedded EN 16931 XML that downstream accounting and ERP systems can ingest automatically, validated before it leaves Magento.

How ZUGFeRD / XRechnung / Factur-X E-Invoicing for Magento 2 Compares

Criterion	ECOSIRE	Custom Build	Competitor
ZUGFeRD 2.x PDF/A-3 hybrid with embedded CII XML	Included	Partial support	Included
XRechnung (B2G) with Leitweg-ID and routing fields	Included	Partial support	Partial support
Factur-X (French) profile support	Included	Partial support	Partial support
Embeds XML into your existing third-party PDF pipeline	Included	Partial support	Not included
EN 16931 schema + Schematron validation before attach	Included	Not included	Partial support
Built, installed and supported on your specific store	Included	Included	Not included
Instant self-service download, no human involved	Not included	Not included	Included
Tailored to your exact tax classes and master data	Included	Included	Partial support

Frequently Asked Questions about ZUGFeRD / XRechnung / Factur-X E-Invoicing for Magento 2

How long does delivery take, since this is build-to-order?

Typical delivery is roughly 2 to 4 weeks from scope sign-off, depending on the complexity of your tax setup, how many profiles (ZUGFeRD / XRechnung / Factur-X) you need, and whether we integrate with Magento's native PDF renderer or a third-party invoice extension. We confirm a concrete timeline in writing before any payment-to-build, and we install on a staging environment first.

Do I get ongoing support and updates after launch?

Yes. Every build includes a defined post-launch support window and bug-fix period. Because the e-invoicing standards (EN 16931, XRechnung CIUS, Factur-X profiles) evolve as the 2025-2028 mandates phase in, we offer an optional ongoing maintenance arrangement to keep your module aligned with new schema and Schematron versions. We agree the terms up front rather than leaving it open-ended.

Does Magento generate ZUGFeRD or XRechnung out of the box?

No. Magento Open Source and Adobe Commerce produce a plain PDF invoice with no embedded structured XML and no Leitweg-ID or B2G routing fields. There is no native EN 16931 output. That gap is exactly what this module fills.

Will the XML embed into my existing third-party PDF invoice extension?

In most cases, yes. We adapt the embedding logic to your actual PDF pipeline using a plugin or observer rather than assuming the native renderer. If you run a third-party PDF invoice extension, we inspect how it builds the PDF during scoping and wire the PDF/A-3 attachment into that flow. Highly unusual or closed renderers are flagged before build so there are no surprises.

Does this work on Adobe Commerce as well as Magento Open Source?

Yes. The module uses standard Magento 2 architecture — di.xml, service contracts, observers/plugins, system.xml and ACL — so it runs on both Magento Open Source and Adobe Commerce, including multi-store and multi-website setups where seller master data differs per store view.

Is the generated e-invoice actually validated for compliance?

Yes. Each generated document is checked against the EN 16931 XML schema and the relevant Schematron rules before it is attached to the PDF, so malformed invoices are caught inside Magento. Note that we deliver technically conformant ZUGFeRD/XRechnung/Factur-X output; final regulatory and tax acceptance for your specific entity should still be confirmed with your tax advisor.