EDI E-Invoicing in Germany: What Happens to EDIFACT After 2027
EDI e-invoicing in Germany: the 2027 EDI transition rule in full, the year-end trap, and a field table to test whether EDIFACT INVOIC meets EN 16931.
Key takeaways
- For supplies made in 2027, EDI invoices that do not meet the e-invoice definition stay allowed with the buyer's consent, with no turnover limit (§ 27(38) no. 3 UStG).
- The rule only covers invoices issued by 31 December 2027. A January 2028 invoice for a December 2027 delivery is outside it.
- From 2028, EDI counts only as an agreed format whose data can be fully extracted into an EN 16931 format (§ 14(1) sentence 6 no. 2 UStG).
- CEN lists UN/EDIFACT INVOIC D14B as an optional syntax with its own validation rules; the mandatory EN 16931 syntaxes are UBL 2.1 and CII.
On this page
EDI e-invoicing in Germany remains possible: existing EDI processes such as EDIFACT may continue for supplies made up to 31 December 2027, with the buyer's consent (§ 27(38) no. 3 UStG). From 2028, an EDI invoice counts only if all required VAT data can be fully extracted into an EN 16931 format (§ 14(1) sentence 6 no. 2 UStG).
This guide is for finance, ERP and EDI teams in international groups that exchange invoices with German trading partners over EDIFACT, VDA or other agreed formats. It covers the legal text, a timeline with a year-end trap, and a field table you can hand to your EDI provider. The German rules apply only when both supplier and customer are established in Germany (§ 14(2) sentence 2 no. 1 of the German VAT Act, Umsatzsteuergesetz or UStG). Cross-border invoices are not in scope.
What does German law say about EDI invoices?
Two provisions decide the question: the definition of an e-invoice in § 14(1) UStG and the transition rule in § 27(38) UStG.
The definition. Under § 14(1) sentence 3 UStG, an e-invoice (elektronische Rechnung) is an invoice that is issued, transmitted and received in a structured electronic format and enables electronic processing. Sentence 6 says the structured format must either
- comply with the European standard EN 16931 and its list of syntaxes, or
- be agreed between issuer and recipient. In that case, the format must allow the "correct and complete extraction" of the information the VAT Act requires into a format that complies with the standard or is interoperable with it.
EDI falls under the second option. An EDI invoice is not an exemption from the mandate. It is one possible form of e-invoice, provided the extraction works.
The transition rule. § 27(38) no. 3 UStG allows an invoice for a supply made after 31 December 2026 and before 1 January 2028 to be issued until 31 December 2027 in an electronic format that does not meet § 14(1) sentence 6, subject to the recipient's consent, if it is transmitted by electronic data interchange (EDI) as defined in Article 2 of Commission Recommendation 94/820/EC of 19 October 1994.
Three details in the wording matter:
- No turnover limit. Unlike no. 2 (EUR 800,000 total turnover), no. 3 applies to every business, including large groups.
- Recipient consent. Without it, the transition rule does not apply.
- Issued by 31 December 2027. Both the supply date and the invoice date must fall within the window.
For the wider deadlines and exemptions, see the overview of the Germany e-invoicing mandate.
Timeline: which EDI invoice is valid when?
| Supply made | Invoice issued | EDI without EN 16931 extraction | EDI with complete extraction | Legal basis |
|---|---|---|---|---|
| 2025 or 2026 | by 31 Dec 2026 | allowed with consent | e-invoice | § 27(38) no. 1 UStG |
| 2027 | by 31 Dec 2027 | allowed with consent, no turnover limit | e-invoice | § 27(38) no. 3 UStG |
| 2027 | from 1 Jan 2028 | not covered by no. 3 | e-invoice | § 14(1) sentence 6 no. 2 UStG |
| from 2028 | from 2028 | not a valid e-invoice | e-invoice | § 14(1) sentence 6 no. 2 UStG |
The third row is the case many EDI roadmaps miss. Under the wording of no. 3, a 2027 delivery is not enough. The invoice itself must be issued by 31 December 2027.
Worked example: a German subsidiary across the year end
Muster Distribution GmbH, the German subsidiary of a foreign group, supplies Beispiel Retail AG in Germany. The two companies have exchanged EDIFACT INVOIC messages for years under a signed EDI agreement. Nobody has yet checked whether the message contains every mandatory field in an extractable form.
| Case | Delivery | Invoice no. | Result under the UStG |
|---|---|---|---|
| A | 15 Mar 2026 | RE-2026-0042, 16 Mar 2026 | Allowed under § 27(38) no. 1 UStG |
| B | 10 Nov 2027 | RE-2027-0815, 12 Nov 2027 | Allowed under § 27(38) no. 3 UStG |
| C | 20 Dec 2027 | RE-2028-0003, 5 Jan 2028 | Not covered: invoice issued in 2028 |
| D | 8 Feb 2028 | RE-2028-0120, 9 Feb 2028 | Allowed only if extraction demonstrably works |
For case C, the subsidiary has two options: issue December 2027 invoices before the year end, or make sure its EDI format already meets § 14(1) sentence 6 no. 2 UStG by then. For case D, only the second option exists. If your group runs a central billing batch in early January, plan this now.
How do you test whether an EDIFACT message passes the extraction test?
"Correct and complete extraction" means every item the VAT Act requires must be present in the message and map unambiguously to the matching EN 16931 business term (BT). A useful reference is the official validation artefacts published by the European standards committee CEN/TC 434. They list UN/EDIFACT as an "EN optional syntax" and provide Schematron rules for the INVOIC D14B message (release 1.0.0, 8 February 2018). The mandatory syntaxes are only UBL 2.1 and UN/CEFACT CII, set out in CEN/TS 16931-2:2017.
The table maps the German mandatory invoice details (§ 14(4) UStG) to EN 16931 business terms and to the segment the CEN rules check in EDIFACT INVOIC D14B:
| Mandatory detail (§ 14(4) UStG) | EN 16931 | EDIFACT INVOIC D14B | CEN rule |
|---|---|---|---|
| Supplier name | BT-27 | NAD+SE | BR-06 |
| Customer name | BT-44 | NAD+BY | BR-07 |
| Tax number or VAT ID | BT-32 / BT-31 | RFF+FC / RFF+VA in the seller group | BR-S-02 |
| Issue date | BT-2 | DTM+137, format 102 | BR-03 |
| Invoice number | BT-1 | BGM, document number | BR-02 |
| Quantity and description | BT-129, BT-153 | QTY+47, IMD+F | BR-22, BR-25 |
| Delivery date or service period | BT-72 / BG-14 | DTM+35 / DTM+167 and DTM+168 | indirect, e.g. BR-IC-11 |
| Net amount per VAT rate | BT-116 | MOA+125 in the VAT breakdown | BR-45 |
| VAT rate and VAT amount | BT-119, BT-117 | TAX+7+VAT, MOA+124 | BR-48, BR-46 |
EN 16931 also requires fields that are not German mandatory details but are needed for a valid document: the invoice type code (BT-3, BGM), the currency (BT-5, CUX) and the specification identifier (BT-24, FTX+DOC). The totals BT-106 to BT-115 sit in MOA+79, MOA+389, MOA+176, MOA+388 and MOA+9.
Here is a shortened EDIFACT INVOIC D14B fragment. The data is fictitious; this is an illustration and has not been run through a validator:
UNH+1+INVOIC:D:14B:UN'
BGM+380+RE-2027-0815'
DTM+137:20271112:102'
DTM+35:20271110:102'
FTX+DOC++P1+urn?:cen.eu?:en16931?:2017'
NAD+SE+++Muster Distribution GmbH+Hauptstrasse 1+Musterstadt++12345+DE'
RFF+VA:DE123456789'
NAD+BY+++Beispiel Retail AG+Marktplatz 5+Beispielstadt++54321+DE'
CUX+2:EUR'
LIN+1'
IMD+F++:::Copy paper A4, box'
QTY+47:10:C62'
MOA+203:200'
PRI+AAA:20'
TAX+7+VAT+++:::19+S'
UNS+S'
MOA+79:200'
MOA+389:200'
MOA+176:38'
MOA+388:238'
MOA+9:238'
TAX+7+VAT+++:::19+S'
MOA+125:200'
MOA+124:38'
The arithmetic at the end matters. CEN rule BR-CO-10 requires MOA+79 (BT-106) to equal the sum of all line amounts MOA+203 (BT-131), and BR-CO-15 requires MOA+388 = MOA+389 + MOA+176. The page on BR-CO-10 explains the same sum rule in UBL.
Typical gaps in legacy EDI formats
| Gap | Why extraction fails | Fix |
|---|---|---|
| No VAT ID or tax number, because the partner holds it in master data | A § 14(4) no. 2 UStG detail is missing from the message | Send RFF+VA or RFF+FC with every invoice |
| Delivery date only in the despatch advice (DESADV) | The time of supply is missing from the invoice | Add DTM+35 or a service period to the INVOIC |
| Parties identified by GLN only | Name and address are mandatory details | Fill NAD with name and address |
| VAT shown only as a grand total | Net amount and VAT per rate are missing | Add a VAT breakdown per rate (TAX + MOA+125/124) |
| Proprietary codes without mapping documentation | Extraction cannot be traced | Write down the mapping to EN 16931 BTs |
EDI, XRechnung and ZUGFeRD compared
| Criterion | EDIFACT INVOIC | XRechnung | ZUGFeRD 2.0.1+ (EN 16931) |
|---|---|---|---|
| Syntax | UN/EDIFACT (text segments) | UBL 2.1 or CII (XML) | CII (XML inside PDF/A-3) |
| Status in EN 16931 | optional syntax, own CEN rules | CIUS on the mandatory syntaxes | profile on the mandatory syntax CII |
| Basis in the UStG | § 14(1) sentence 6 no. 2 (agreement) | § 14(1) sentence 6 no. 1 | § 14(1) sentence 6 no. 1 |
| Agreement with the recipient | required | not required | not required |
| Typical channel | EDI connection or service provider | e-mail, portal, Peppol | mostly e-mail |
What counts as a structured e-invoice versus another invoice (sonstige Rechnung) is covered in what is a structured e-invoice. The 2027 rules and the EUR 800,000 threshold are in Germany e-invoicing 2027.
How to check your EDI mapping with docutools.pro
docutools.pro does not read EDIFACT. The XRechnung validator accepts UBL Invoice and CII files. It is still useful in an EDI project for checking the output of your conversion: if your EDI provider or ERP converts the INVOIC into an XRechnung or an EN 16931 CII file, the check shows whether the extraction is complete.
- Have one real EDI invoice converted to UBL or CII. Many EDI converters offer such an export.
- Open the XML file in the XML viewer and compare it field by field with the table above. The XML viewer runs in your browser, so the file does not leave your computer.
- Upload the file to the viewer for the "KoSIT validation". It checks the way the KoSIT validator does (configuration 2026-08-31). The file is sent to our server for this check.
- Read the result. "KoSIT-conformant" means the converted file passes the rules. If you see "Not KoSIT-conformant", the list of XRechnung error codes helps you identify the rule.
- If a detail is missing in the XML, it is usually already missing in the INVOIC. Fix the mapping at the source, not the XML file.
The free plan includes 2 uploads per day of up to 500 KB per file. Batch checks of ZIP files need the Pro plan, and they run a quick check only, not the full KoSIT validation. For a test plan before go-live, see test an e-invoice before sending.
Open questions
- Who decides what "complete extraction" means? The law sets the condition but gives no test procedure and no list of approved EDI formats. A documented mapping to EN 16931 is the obvious evidence.
- New administrative guidance. The Federal Ministry of Finance (BMF) published another letter on e-invoicing on 15 October 2026. Ask your tax adviser whether it affects your EDI process; this article relies on the statutory text.
More guides on deadlines and scope are on the e-invoicing mandate hub.
Sources
- § 14 UStG, issuing invoices (gesetze-im-internet.de, German) (opens in a new tab), para. 1 sentences 3 to 6 and para. 2
- § 27 UStG, general transitional provisions, para. 38 (gesetze-im-internet.de, German) (opens in a new tab)
- CEN/TC 434 validation artefacts for EN 16931, folder "edifact" (GitHub, ConnectingEurope) (opens in a new tab)
- XStandards Einkauf: XRechnung and the EN 16931 syntaxes (xeinkauf.de, German) (opens in a new tab)
Last reviewed: November 2026
This article is general information, not tax or legal advice.
Tools for this article
- XRechnung ViewerParse, validate & repair German e-invoices with GoBD-compliant audit trail.Open tool →
- XML ViewerPaste or upload any XML — collapsible tree view, syntax highlighting, XPath queries.Open tool →
- KoSIT Error HubSearchable reference for all XRechnung validation error codes with fix guides.Open tool →
Frequently asked questions
Is EDI allowed under the German e-invoicing mandate?
Yes, in two ways. Until the end of 2027, EDI invoices may continue unchanged for supplies made in 2027 if the buyer consents and the invoice is issued by 31 December 2027 (§ 27(38) no. 3 UStG). After that, an EDI format is a valid e-invoice only if the parties agreed on it and all VAT-relevant data can be correctly and completely extracted into an EN 16931-compliant or interoperable format.
Do foreign companies have to change their EDI invoices for Germany?
Only if both supplier and customer are established in Germany. The German e-invoicing obligation in § 14(2) sentence 2 no. 1 UStG applies to supplies between businesses that are both established in Germany or certain listed areas. A German subsidiary of a foreign group that invoices another German company is in scope; cross-border invoices to or from a foreign entity are not.
Does the EUR 800,000 threshold apply to EDI invoices?
No. The EUR 800,000 total turnover limit is only in § 27(38) no. 2 UStG and covers paper and other non-structured invoices from smaller issuers in 2027. The EDI rule in no. 3 has no turnover condition. A large group may therefore keep its existing EDI process for supplies made in 2027 if the recipient consents, regardless of its 2026 turnover.
Is EDIFACT one of the EN 16931 syntaxes?
Not one of the mandatory ones. The technical specification CEN/TS 16931-2:2017 lists UBL 2.1 and UN/CEFACT Cross Industry Invoice as the mandatory syntaxes. CEN/TC 434 has published separate validation rules for UN/EDIFACT INVOIC D14B and labels it an optional syntax. Under German law, EDIFACT therefore relies on the agreed-format route in § 14(1) sentence 6 no. 2 UStG.