| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4295 |
| Technical Name |
l10n_de_xrechnung_generator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 4295 |
| Technical Name |
l10n_de_xrechnung_generator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
XRechnung Deutschland — XRechnung 3.x Generator (UBL + CII)
Germany B2G/B2B XRechnung 3.x in UBL 2.1 and CII syntax with real Leitweg-ID routing — for Odoo 18 & 19
A production XRechnung 3.x generator for the German e-invoicing mandate, built on the shared ZUGFeRD / XRechnung engine. Where the engine produces the UN/CEFACT CII syntax, this module adds the second XRechnung syntax — OASIS UBL 2.1 Invoice and CreditNote — and the German Leitweg-ID routing that decides whether an invoice goes to a public-sector buyer (B2G) or a business buyer (B2B), and over which transport route.
UBL 2.1 builder
Emits the XRechnung 3.x CIUS in the OASIS UBL syntax (Invoice / CreditNote) with the KoSIT CustomizationID / ProfileID, the BuyerReference (Leitweg-ID, BT-10), full supplier / customer parties with the mandatory German seller contact group (BR-DE-1…5), PaymentMeans IBAN credit transfer, TaxTotal / TaxSubtotal per category and EN 16931 invoice lines.
Real Leitweg-ID routing
The genuine ISO/IEC 7064 MOD 97-10 Leitweg-ID validator plus a route resolver: a buyer with a Bund prefix (00) routes to the federal ZRE, a Land / Kommune to the OZG-RE portal, and a plain business buyer to Peppol BIS Billing 3.0.
Dual syntax, one invoice
Choose UBL or reuse the engine's CII for the same invoice; both carry the identical XRechnung 3.0 conformance URN. Switch the default per company or per document.
Transport routes (BYOK)
Editable endpoints for ZRE, OZG-RE and your Peppol access point, per company, seeded from the official portal addresses. This module prepares and addresses the document; the actual delivery is handled by your own configured transport — bring your own key.
XRechnung 3.x validation
The KoSIT BR-DE business rules plus the routing rules: a B2G route requires a valid Leitweg-ID; a Peppol route requires a buyer electronic address; the seller must carry a VAT ID or Steuernummer and the mandatory contact group.
Onboarding & immutable log
A guided onboarding wizard with a live Leitweg-ID / route check, company / partner configuration, account.move actions and an immutable, content-hashed generation log for traceability.
Germany e-invoicing mandate
Germany requires the EN 16931 structured invoice for B2B issuance from 1 January 2027 (turnover above €800,000) and from 1 January 2028 for all businesses; public authorities have had to receive XRechnung since 2020 and all businesses since 1 January 2025. This module gets you mandate-ready in both XRechnung syntaxes.
Requires the shared engines
Built on einvoice_core_engine and zugferd_xrechnung_engine; install those first. No e-invoice data is transmitted by this module — transport is BYOK. Compatible with Odoo 18 and Odoo 19.
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