Skip to main content

SERVICES

Introducing E-Invoicing with Odoo

XRechnung, ZUGFeRD, Peppol, incoming invoices and archiving in Odoo – set up before the German mandate from 1 January 2027. Fixed price after readiness check.

1 Jan 2027

Mandate above €800,000 prior-year turnover

8 years

Retention, intact

€0

Peppol registration in Odoo

1 day

Reply to enquiries (business day)

Scope

What to expect

What this service includes.

01

Readiness check

We review issuing, receipt, archiving, recurring invoices and credit notes, then provide a prioritised list of the remaining steps.

02

XRechnung and ZUGFeRD setup

Format per customer in the customer record, mandatory fields in the structured part, Leitweg-ID for public authorities.

03

Peppol

We register your database with Peppol and test it in demo mode before going live. Odoo serves as the access point.

04

Incoming invoices

An email alias and the Peppol inbox bring supplier invoices into the purchase journal as drafts. XML invoices need no OCR credits.

05

Archiving

The XML file and the validation report are kept intact for eight years, with controlled access.

06

Training

Accounting and sales practise reviewing and correcting e-invoices and issuing credit notes correctly.

07

DATEV coordination

We agree account mapping and the DATEV export with your tax adviser so they receive posting data in their usual format.

Why now

From 1 January 2027, companies whose total turnover exceeded €800,000 in the previous year must issue invoices to domestic businesses in Germany as e-invoices. From 1 January 2028 this applies to everyone. Receiving e-invoices has been mandatory since 1 January 2025. All deadlines with sources are in the e-invoicing overview.

Ruetech uses e-invoices for its own billing. We have also implemented e-invoicing with Odoo for clients in Germany and abroad.

Process

  1. Preliminary assessment: Together with accounting, we review the readiness check and one outgoing and incoming invoice. This identifies the remaining tasks and the scope for the fixed-price quote.
  2. Setup: format per customer, Peppol registration in demo mode, incoming invoices, archive and DATEV export.
  3. Test run with validation report: We validate real invoices and file the results. Format and mandatory fields must be correct before cutover.
  4. Go-live: switch to live Peppol operation and the first e-invoices to your customers.
  5. Post-launch support: We support your team through the first invoice runs and address questions from customers and your tax adviser.

Fixed price

The readiness check defines the scope. We then provide a binding fixed-price quote for implementation. Other packages are listed on the pricing page.

Standard, configuration or development

The overview distinguishes standard functions, configuration and development. It is based on Odoo 17 to 20 documentation and source code as of 27 September 2026.

TopicStandardConfigurationDevelopment
Generate XRechnungYes, module account_edi_ubl_cii (Community)Format per customer in the customer record–
Generate ZUGFeRD / Factur-XYes, EXTENDED profile only–Other profiles
Leitweg-ID (BT-10)From Odoo 20, from the customer recordAddressing scheme 0204 on the customerOdoo 17–19
Send and receive via PeppolYes, Odoo is an access point, registration freeRegistration, demo, live–
Incoming invoicesYes, email alias; XML without OCR creditsJournal, alias, review steps–
Validation reportNoKoSIT validator check in the processAutomatic filing of the report
Self-billing credit note as Factur-XNo, according to a user report on the Odoo forum–Yes
DATEV exportYes, Enterprise (DATEV DATA, DATEV ATCH)Account mapping with the tax adviser–
ArchivingGoBD audit trail (l10n_de)Storage location and access rightsConnecting an external archive

Further reading

Frequently Asked Questions

These are the questions we regularly discuss with management, accounting and IT before an Odoo project begins.

The readiness check identifies the formats, transmission routes and special cases you need. We then provide a fixed-price quote. Odoo Community can generate XRechnung and ZUGFeRD; DATEV export requires Enterprise. Licence costs are listed separately.

Not for generating e-invoices: XRechnung and ZUGFeRD are produced by the module account_edi_ubl_cii, which is part of Community in versions 17 to 20. Peppol registration is available there too. The DATEV export (DATEV DATA and DATEV ATCH), by contrast, comes with the Enterprise module l10n_de_reports.

The e-invoicing features we refer to are in versions 17 to 20. From Odoo 20, Odoo takes the Leitweg-ID for public authorities from the customer record; in versions 17 to 19 the standard sets “N/A” there. If you run an older version, plan the upgrade before the rollout.

According to Odoo’s documentation, registration is free and also available in Community. The documentation does not state per-document fees or volume limits. We clarify this with Odoo before the quote.

No, Odoo has no built-in KoSIT validation report. We set up the check in the process. It is worth it: you may rely on the technical result of a validation, and the report serves as evidence (Federal Ministry of Finance letter of 15 October 2025, para. 35a).

Yes. One Odoo database runs several entities with their own accounting. In France all companies receive e-invoices since 1 September 2026, and SMEs issue them from 1 September 2027 via an approved platform. Odoo is on the French tax administration’s list of platform operators (as of 22 September 2026).

Introduce e-invoicing with Odoo – before 1 January 2027

From 2027, companies with more than €800,000 prior-year turnover must issue e-invoices in Germany, from 2028 all of them. We check where you stand and set up format, Peppol, incoming invoices and archiving in Odoo.

Reply within one working day · Odoo Silver Partner