Magento Integration

Live

Generate compliant e-invoices straight from Magento 2 and Adobe Commerce — XRechnung, ZUGFeRD, and PDF live today, seven more formats coming Q3 2026. Free open-source module, paid e-invoice service.

Live today

PDF (all 14 supported countries)
XRechnung for Germany — BIS 3.0 / EN 16931
ZUGFeRD for DE/AT — hybrid PDF/A-3 with embedded XML

Coming Q3 2026

Factur-X (FR)
FatturaPA (IT)
Facturae (ES)
ebInterface (AT)
UBL (BE/NL/BG/RO)
ISDOC (CZ)
NAV (HU)

Features

Free module, paid service

MIT/OSL, free on GitHub and the Adobe Commerce Marketplace. Revenue lives in the invoice-api.xhub.io service subscription — the same model you trust for Stripe, PayPal, and Mollie.

Three formats live, seven more in 2026

PDF, XRechnung, and ZUGFeRD ship today. The remaining country-specific formats appear automatically in the dropdown once the backend supports them.

§14 UStG-compliant invoice numbering

Gap-free, race-safe sequential numbers via a custom DB table. Token format `2026-{seq:0000}` for legally compliant production use.

Multi-Store & Multi-Website

Separate seller data and template IDs per store view. Native Magento Stores → Configuration UI — no store-code modifications required.

Composer-native installation

A single `composer require` installs, a single `bin/magento setup:upgrade` activates. No ZIP upload, no manual file copy.

Custom invoice templates

Design your layout in the console, copy the Template-ID, paste into Stores → Configuration. Per-order override via order attribute is supported.

Install via Composer

Three terminal commands — no manual file deployment, no web-server root access needed.

composer require xhubio/magento2-invoice-api-xhub

bin/magento module:enable Xhubio_InvoiceApiXhub

bin/magento setup:upgrade && bin/magento cache:flush

Observer Event Flow

The module uses Magento's DI-aware Observer system — no override spaghetti, no preference conflicts. The `sales_order_invoice_save_after` observer fires only after the database commit.

sales_order_save_after

Observer

Invoice-api.xhub API

Stored Invoice + Email

Screenshots

Magento 2.4 Admin dashboard: Revenue / Lifetime Sales / Average Order widgets plus a Last Orders table showing two completed orders (Max Mustermann × €200) — invoices already generated by the plugin — Magento Admin dashboard — Last Orders widget after the plugin processed two test orders

Settings page with General (API key, base URL, country, format, trigger, number format, template ID, attach-to-email), Seller Details (name, VAT-ID, address, IBAN/BIC/Bank/Holder), and Diagnostics (effective configuration banner) all open at once — Stores → Configuration → Sales → Invoice-api.xhub: all three sections expanded

Expanded General group with all 8 plugin settings: API key, base URL, country, format (XRechnung selected), trigger, invoice number format, template ID, attach-to-email — General settings — API key, country, format, trigger, number format

Orders grid showing orders #000000001 and #000000002 in Complete state — Sales → Orders grid with completed test orders

Order #000000002 view with the Invoice-api.xhub section showing filename, invoice number, format, country, generated timestamp, Download link, Re-generate button, and effective-configuration banner — Order detail — Invoice-api.xhub metabox with Download + Re-generate

Seller Details group with the four bank-account fields populated (Demo: DE89370400440532013000 / COBADEFFXXX / Commerzbank / Beispiel GmbH) — required for ZUGFeRD and Factur-X — Seller Details — IBAN / BIC / Bank name / Account holder for ZUGFeRD SEPA

How it works

Install the module via Composer, sign up for an invoice-api.xhub.io account, paste the API key into Stores → Configuration, pick a country and format. When an order reaches the configured status, the Observer dispatches an async job: order data is POSTed to the API, the compliant invoice file is returned, stored on the order, and attached to the customer email. The whole setup takes about ten minutes.

Production-ready

DI-aware Observers with no preference conflicts, atomic invoice numbering via a custom DB table, per-store-view configuration, GDPR-compliant uninstall script, idempotency cache for duplicate-trigger protection, and native integration in the Magento admin under Stores → Configuration.

Who it's for

DACH B2B shops on Magento 2 or Adobe Commerce facing the XRechnung receive mandate (January 2025) and preparing for the 2027/28 send mandate. Cross-border EU shops that need PDF today and will receive country-specific formats automatically as they roll out. Enterprise setups with multiple stores, custom accounting infrastructure, and the need for a standardized, Composer-managed e-invoicing solution.

Use Cases

DACH B2B Shop on Magento

XRechnung mandate in Germany — receive since January 2025, send from 2027/28

1Install module via Composer, paste API key
2Set format to XRechnung, country to DE in Stores → Configuration
3Set order to configured trigger status
4Compliant XRechnung generated and emailed automatically

Cross-border EU shops

PDF today, country-specific formats automatically as they roll out from Q3 2026

1Select PDF format — works for all 14 supported countries
2Country-specific formats appear automatically in the dropdown
3No module update needed when new formats launch
4Single API for all EU markets

Multi-Store Enterprise

Separate seller data, template IDs, and trigger events per store view

1Multiple stores (DE store, AT store, CH store) in the same Magento instance
2Each store view has its own API settings and invoice numbering sequence
3XRechnung for DE, ZUGFeRD for AT, PDF as universal fallback for CH
4Central diagnostic overview in Magento admin for all store views

E-invoice API comparison: which solution fits Magento?

Overview of popular e-invoice APIs for XRechnung and ZUGFeRD — features, pricing, compliance.

Get started today

Install the module via Composer, sign up for an account, and send your first compliant e-invoice from your Magento shop in ten minutes.