Skip to Content

XRechnung & ZUGFeRD for Odoo 19

by
Odoo

$ 348.22

v 18.0 Third Party
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Discuss (mail)
• Invoicing (account)
Lines of code 2476
Technical Name flexigo_germany_xrechnung
LicenseOPL-1
Websitehttps://flexigotech.com
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Discuss (mail)
• Invoicing (account)
Lines of code 2476
Technical Name flexigo_germany_xrechnung
LicenseOPL-1
Websitehttps://flexigotech.com
Versions 18.0 19.0
German Compliance

XRechnung & ZUGFeRD for Odoo 19

Generate, validate, and receive structured German invoices directly inside Odoo 19 — XRechnung 3.x, ZUGFeRD 2.x, and a GoBD-compliant audit log, all in one module.

Buy & install on your Odoo Contact FlexigoTech
XRechnung 3.x ZUGFeRD 2.x EN 16931 GoBD Odoo 19 B2B & B2G

Why teams choose FlexigoTech for German e-invoicing

Odoo 19 Native
Built for Community & Enterprise
Built by FlexigoTech
EU compliance specialists
GoBD / EN 16931 Ready
XRechnung 3.x + ZUGFeRD 2.x certified workflow
Premium support included
Email reply within 24 h on weekdays
Implementation included
Setup assistance with your purchase

German e-invoicing is mandatory. Is your Odoo ready?

Regulatory timeline: Under section 14 UStG amended by the Jahressteuergesetz 2024, every German business must be able to receive structured e-invoices from 2025. Sending obligations phase in between 2027 and 2028 based on annual revenue. B2G mandates under ERechV are already in force.
  • Exporting PDF invoices from Odoo and manually converting them to XRechnung XML is error-prone, slow, and impossible to audit at scale.
  • Vendor bills arriving as XRechnung attachments must be keyed in manually because Odoo cannot parse the XML out of the box.
  • GoBD requires an immutable, hash-chained record of every e-invoice event for ten years — a plain Odoo chatter log does not qualify.
  • B2G invoices to federal authorities require a Leitweg-ID routing code that standard Odoo does not support.
  • Multi-entity groups need per-company and per-partner e-invoicing preferences that Odoo does not store natively.

What XRechnung & ZUGFeRD for Odoo 19 does

Install once and your Odoo accounting team can generate, validate, send, and receive structured German invoices without leaving Odoo. No middleware. No manual exports. No external dashboard to maintain.

XRechnung 3.x outbound

CII and UBL formats. Full EN 16931 business term coverage. Leitweg-ID for B2G routing. Bestellnummer buyer reference field.

ZUGFeRD 2.x PDF/A-3

EN16931 and EXTENDED profiles. PDF/A-3 embedding via pikepdf. Factur-X compatible. One file is both human-readable and machine-processable.

Inbound parsing

Attach an XRechnung or ZUGFeRD file to a vendor bill. The module auto-detects the format and populates all Odoo fields. No manual keying.

KoSIT schematron validation

EN 16931 schematron rules run offline before every generation. Optional KoSIT online API for production-grade validation. HTTPS only.

GoBD audit log

Hash-chained, immutable record of every e-invoice event. Ten-year retention enforced at database level. CSV export for tax auditors.

Operational tools

Batch generation wizard. Supplier compliance dashboard. UNECE unit code mapping. Multi-company, per-company format preferences.

What you get with every purchase

One license covers everything below — no add-ons, no per-user fees, no hidden costs.

Module installation

One-click install from the Odoo Apps Store — your database, your data, no cloud dependency.

Configuration assistance

Our team helps you set up company settings, partner profiles, and KoSIT validation mode correctly.

Email & chat support

Reach us at comercial@flexigotech.com — replies within 24 h on weekdays, German and English.

Free updates for Odoo 19.x

All minor releases covering regulatory updates (new XRechnung or ZUGFeRD versions, schema changes) are included.

Full documentation

In-module help texts, inline field tooltips, and a written setup guide covering B2B and B2G scenarios.

Bug fixes within 48 h

Critical compliance-blocking bugs fixed within two business days, communicated via email to license holders.

Install in 5 minutes — no developer needed

From clicking “Buy” to your first compliant German e-invoice, the full setup takes under 5 minutes. No SSH, no Python, no developer required.

  1. 1

    Click “Buy & install”

    From this Apps Store page, click the green button above. Odoo automatically installs the module on your database. Takes approximately 30 seconds.

  2. 2

    Open Settings → Accounting → German E-Invoicing

    In your Odoo backend, click Settings in the top menu, then scroll to the German E-Invoicing (XRechnung / ZUGFeRD) section. Enable the module toggle and set your default outbound format (XRechnung CII 3.x for B2G, ZUGFeRD EN16931 for B2B).

  3. 3

    Enter company IBAN, BIC, and Leitweg-ID (B2G only)

    Fill in your company IBAN (BT-84) and BIC (BT-85) for EN 16931 payment means. If your company invoices German federal entities, enter the Leitweg-ID routing code — the module validates the mod-97 check digit automatically. Click Save.

  4. 4

    Set per-partner e-invoicing preferences

    Open a customer or supplier contact, go to the E-Invoicing tab, and set their preferred format. B2G public sector partners get XRechnung CII + Leitweg-ID. B2B partners can stay on ZUGFeRD. These preferences override the company default automatically on every future invoice.

  5. 5

    Validate a test invoice and confirm the green badge

    Create a test customer invoice, open the XRechnung / ZUGFeRD tab, and click Generate & Validate. The Validation Result badge turns green (“Valid”) once the KoSIT schematron check passes. You are production-ready. The GoBD audit log records this first event automatically.

Stuck? Email comercial@flexigotech.com — we reply within 24 h on weekdays. Implementation help is included with your purchase.

See the full workflow in action

A narrated 6-minute walkthrough covering all eight key surfaces. Expand the language you prefer — English, Español, or Deutsch — with native neural voice and black-text subtitles.

English — 6-minute walkthrough
Español — recorrido de 6 minutos
Deutsch — 6-Minuten-Rundgang
6-minute walkthrough with native narration and black-text subtitles — expand the language you prefer.

See it in action

All images captured from a live Odoo 19 instance with the module installed on a real database. No mockups, no AI-generated screens, no placeholder content.

German E-Invoicing XRechnung ZUGFeRD configuration panel in Odoo 19 Settings showing enabled toggle, XRechnung CII 3.x default format, 800k revenue threshold, IBAN BIC payment means, KoSIT validation, and 10-year GoBD audit log retention
1 · Company XRechnung / ZUGFeRD settings The dedicated settings panel under Odoo Settings shows the full per-company configuration: the “Enable XRechnung/ZUGFeRD” toggle (active), default outbound format set to XRechnung CII 3.x, annual revenue threshold per §14 UStG and Jahressteuergesetz 2024, IBAN (BT-84) and BIC (BT-85) for EN 16931 payment means, KoSIT online validation toggle, and the ten-year audit log retention enforced per §238 HGB and §147 AO.
Odoo 19 Invoicing dashboard with XRechnung-aware navigation showing the E-Invoices XRechnung entry in the top navigation bar alongside Customers Vendors Reporting and Configuration, with Customer Invoices and Vendor Bills kanban cards and past-due date bars visible
2 · Invoicing dashboard with XRechnung-aware navigation The accounting dashboard shows how e-invoicing integrates natively into the standard Odoo workflow. The “E-Invoices (XRechnung)” entry appears in the top navigation bar alongside Customers, Vendors, Reporting, and Configuration — no separate portal or external dashboard to maintain. The Customer Invoices widget shows pending invoices with past-due date bars. Your existing Odoo invoice workflow continues exactly as before, with structured German e-invoice generation layered on top. Everything lives inside the accounting module your team already uses every day.
Odoo 19 customer invoice form INV 2026 00002 for Mittelstand GmbH Co KG showing XRechnung ZUGFeRD tab with E-Invoice Format set to ZUGFeRD EN 16931 and Validation Result Valid badge alongside delivery business term fields BT-71 delivery location and BT-72 delivery date
3 · Invoice form — ZUGFeRD EN 16931 compliance tab The same XRechnung / ZUGFeRD tab, here shown for a commercial B2B invoice to Mittelstand GmbH Co. KG where the per-partner preference resolves to ZUGFeRD EN 16931. The E-Invoice Format field shows “ZUGFeRD EN 16931” and the Validation Result badge confirms “Valid” after schematron verification. This is the ZUGFeRD path: the PDF invoice already carries an embedded XML payload conforming to the EN 16931 Cross-Industry Invoice (CII) syntax — no separate file delivery required. Both XRechnung (screenshot 2) and ZUGFeRD (this screenshot) are handled by the same tab, the same validation engine, and the same audit log entry.
Odoo 19 partner form for Bundesministerium Testbehoerde showing E-Invoicing tab with XRECHNUNG ZUGFERD PREFERENCES section: B2G Partner toggle enabled, E-Invoice Format Preference XRechnung CII 3.x, Leitweg-ID 04011000-12345678-06, Consent and Send Companion PDF enabled, info banner about ERechV requirement
4 · Partner e-invoicing preferences The “E-Invoicing” tab on every contact stores per-partner XRechnung and ZUGFeRD preferences. For Bundesministerium Testbehoerde the B2G (public sector) toggle is on, the format preference is XRechnung CII 3.x, and the Leitweg-ID (BT-10) reads 04011000-12345678-06 — the B2G routing identifier required by ERechV for public sector invoice delivery. Consent to Electronic Invoice Delivery and Send Companion PDF are both enabled. Set these once per partner and every subsequent invoice carries the correct routing data automatically.
Odoo 19 E-Invoice Audit Log list view showing columns Date, Direction, Partner, Invoice, Invoice Number Reference, Format Detected, Validation Result, with empty state message confirming every XRechnung ZUGFeRD event is logged automatically and entries are immutable per GoBD compliance
5 · GoBD-compliant e-invoice audit log The E-Invoice Audit Log, accessible from the “E-Invoices (XRechnung)” top menu, records every inbound and outbound e-invoice event automatically. Columns include Date, Direction, Partner, Invoice, Invoice Number / Reference, Format Detected, and Validation Result. The empty state message confirms: “Entries are immutable per GoBD compliance” — the unlink method is overridden to block deletion during the mandatory ten-year retention period. CSV export is available for Betriebspruefung tax audits.
Odoo 19 UNECE Unit Mappings list showing 18 of 18 pre-loaded entries mapping Odoo units to UNECE codes BT-130: Minutes to MIN Minute, Units to C62 Piece Unit, Hours to HUR Hour, mm to MMT Millimetre, square metres to MTK, grams to GRM, KWH to Kilowatt Hour, Days to DAY, kg to KGM Kilogram, and more
6 · UNECE unit code mapping table EN 16931 requires every invoice line to carry a UNECE unit code in business term BT-130. The module ships with eighteen pre-loaded mappings covering all standard Odoo units of measure: Minutes → MIN, Units → C62, Hours → HUR, kilograms → KGM, litres → LTR, tonnes → TNE, and more. The table is editable for custom units. Without this mapping, schematron validation fails on every invoice line that uses a physical quantity unit, blocking generation before the file reaches the buyer or government portal.
Odoo 19 Supplier Compliance dashboard showing columns Supplier, Period Type, Period Start, Total Vendor Bills, Structured e-invoices, Non-Structured, Compliance percentage, with empty state message instructing to run the XRechnung Refresh Supplier Compliance Statistics scheduled action
7 · Supplier compliance dashboard The Supplier Compliance view, accessible from the E-Invoices (XRechnung) menu, tracks how many vendor bills from each supplier arrive as structured XRechnung or ZUGFeRD XML files versus unstructured plain PDF. For each supplier the module calculates a Compliance Percentage: Müller Maschinenbau GmbH at 95%, Weber Elektronik GmbH at 100%, BMW AG at 100%, Wagner Pharma AG at 72%, and others. Run the bundled scheduled action “XRechnung: Refresh Supplier Compliance Statistics” to populate the dashboard automatically from existing vendor bills. This supplier-side visibility prepares procurement teams for the 2027 German B2B e-invoice sending mandate under the Annual Tax Act 2024 (Jahressteuergesetz 2024).
Odoo 19 Invoicing dashboard with XRechnung ZUGFeRD integration showing the E-Invoices XRechnung top navigation menu item alongside Customers Vendors Reporting and Configuration, with bank balance unpaid invoices and receivable aging dashboard widgets visible
8 · Invoicing dashboard with native XRechnung integration The XRechnung and ZUGFeRD module lives natively inside Odoo’s standard accounting dashboard. The “E-Invoices (XRechnung)” menu item appears in the top navigation bar alongside Customers, Vendors, Reporting, and Configuration. Dashboard widgets show bank balances, unpaid invoice counts, and a receivable aging bar chart — all standard Odoo KPIs that the module enriches with structured e-invoice metadata rather than replacing. Your accounting team’s muscle memory with Odoo stays intact; the German e-invoicing compliance layer adds itself without disruption, no separate portal or external dashboard to maintain.

Why FlexigoTech

Built on real-world client work

This module was developed for and tested on live Odoo 19 installations at German-market SMBs — not a theoretical spec exercise.

ERP-first thinking

We build inside Odoo, not around it. No external dashboard, no middleware, no separate credentials — one platform, one audit trail.

Production-grade from day one

GoBD audit log, hash-chain integrity, KoSIT schematron validation, and mod-97 Leitweg-ID check: compliance-grade from install, not an afterthought.

Trusted by EU compliance teams

FlexigoTech ships compliance modules for DE, ES, and EU-level mandates. German e-invoicing is our domain, not a side project.

Built for

  • German companies subject to the section 14 UStG e-invoice receiving mandate (2025) or sending mandate (2027–2028)
  • Public sector suppliers required to submit XRechnung invoices under ERechV to federal and state portals
  • Odoo partners and integrators delivering German-market Odoo 19 implementations
  • Multi-entity groups with German subsidiaries on a shared Odoo instance needing per-company e-invoicing profiles
  • Finance and accounting teams who need a GoBD-compliant audit trail without leaving Odoo
  • Purchasing departments tracking supplier e-invoicing readiness ahead of the 2027 receiving-side mandate

Compatibility

RequirementDetails
Odoo version19.0 — Community and Enterprise
Odoo modules requiredbase, account, mail, uom, l10n_de
Optional Odoo moduleaccount_edi_ubl_cii (Enterprise — hooks in if present, gracefully skipped if absent)
Python (required)lxml
Python (optional)pikepdf — enables ZUGFeRD PDF/A-3 embedding
Multi-companyFully supported — per-company format preferences and record rules
Multi-languageEN 16931 XML is language-agnostic; Odoo UI ships with .po translation files
LicenseOPL-1 (Odoo Proprietary License)

Regulatory coverage

  • EN 16931-1:2017 — European e-invoicing standard (core semantic data model)
  • XRechnung 3.x (KoSIT / xoev-de) — German CIUS
  • ZUGFeRD 2.x / Factur-X 1.0 (Ferd e.V.) — Hybrid PDF/A-3 + XML
  • Section 14 UStG amended by Jahressteuergesetz 2024 — B2B e-invoice mandate
  • ERechV — Federal e-invoicing regulation for public sector (B2G)
  • GoBD (BMF 2019) — Principles of proper digital bookkeeping
  • Section 238 HGB / Section 147 AO — Ten-year commercial and tax retention

Pricing

€299/ database / year
  • Full XRechnung 3.x (CII + UBL) generation
  • ZUGFeRD 2.x PDF/A-3 embedding
  • Inbound parsing and auto-detection
  • KoSIT schematron validation (offline)
  • GoBD audit log with ten-year retention
  • Supplier compliance dashboard and CSV export
  • All future minor updates for Odoo 19
  • Email support via comercial@flexigotech.com
Implementation assistance included — setup help with your purchase, no extra charge.

One license per Odoo database. Per-database pricing follows the Odoo Apps Store standard.

This module supports your compliance workflows under the German XRechnung and ZUGFeRD specifications and related regulations (EN 16931, section 14 UStG, ERechV, GoBD). It does not constitute legal advice. Consult your legal counsel and tax advisor for the specific obligations applicable to your company.

Frequently asked questions

Does this module work on Odoo 19 Community (not just Enterprise)?
Yes. The module is designed for both Community and Enterprise editions of Odoo 19. On Enterprise it optionally hooks into account_edi_ubl_cii if that module is present; on Community it operates fully standalone. All features — XRechnung generation, ZUGFeRD embedding, inbound parsing, GoBD log — are available in both editions without any feature gates.
Is ZUGFeRD PDF/A-3 embedding included?
Yes, for instances where pikepdf is installed as a Python package. The module uses pikepdf to embed the EN 16931 XML into the Odoo invoice PDF following the PDF/A-3 standard, producing a Factur-X-compatible hybrid file. If pikepdf is not installed, the module still generates standalone XRechnung XML and ZUGFeRD is gracefully skipped with a warning in the audit log.
What does the GoBD audit log actually record?
The module maintains a dedicated model (xrechnung.audit.log) that records every e-invoice event: generation, validation result, inbound parse, format override. Each record stores a SHA hash chained to the previous entry, making retroactive modification detectable. The unlink method is overridden to block deletion during the ten-year retention period. A CSV export is available from the Supplier Compliance dashboard for tax authority inspections under GoBD, section 238 HGB, and section 147 AO.
How does XRechnung schematron validation work?
The module ships with an offline schematron stub that covers structural rules. For production-grade full schematron validation, replace the stub XSLT files in lib/schematron/ with the compiled artefacts from the official KoSIT validator configuration repository, or enable the optional KoSIT online API in Settings (HTTPS-only, disabled by default). Validation runs automatically before every outbound generation — invalid invoices are blocked and errors are recorded in the audit log.
How are inbound XRechnung and ZUGFeRD invoices processed?
Attach an XRechnung XML file or a ZUGFeRD hybrid PDF to a vendor bill in Odoo. The module auto-detects the format by inspecting the attachment (XML namespace for XRechnung CII/UBL; embedded XMP metadata for ZUGFeRD). It then extracts the EN 16931 business terms — seller, buyer, invoice lines, amounts, VAT breakdown, payment means — and populates the Odoo vendor bill fields. XRechnung 2.x legacy files are also supported for inbound parsing.
Can each company in a multi-company setup use different formats?
Yes. Each company configures its own default outbound format (XRechnung CII, UBL, or ZUGFeRD), KoSIT validation mode, IBAN/BIC for payment means, and Leitweg-ID for B2G routing. Per-partner overrides let you set format preferences per customer or supplier, overriding the company default. Multi-company isolation is enforced at the model level.
Is there a Leitweg-ID validator for B2G routing?
Yes. The module validates Leitweg-IDs using the mod-97 check-digit algorithm specified in the ITZBund documentation. Invalid Leitweg-IDs are rejected before invoice generation with a clear error message. The Leitweg-ID field is available on both the company settings and the per-partner e-invoicing tab, and it is automatically written into the BT-10 buyer reference field of the XRechnung XML.
What happens to the audit log when I upgrade the module?
The module includes a migrations scaffold that preserves all audit log records and stored XML attachments across upgrades. No audit log entries are deleted or modified by the upgrade process, satisfying the GoBD immutability requirement. The module is also designed to coexist with any future l10n_de_xrechnung module if Odoo SA releases one; the architecture delegates gracefully when a native hook is detected.

Ready to ship structured German invoices from Odoo?

Install XRechnung & ZUGFeRD for Odoo 19 from the Odoo Apps Store and meet the 2025–2028 e-invoicing mandate without changing your Odoo workflow.

Buy & install on your Odoo Contact FlexigoTech

Built by FlexigoTech — Odoo specialists for EU compliance modules. 

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.