Germany Requirements EDEKA GS1 ZUGFeRD EN 16931

EDEKA sets its own field rules on top of EN 16931

An invoice can pass validation against the European standard and still be rejected by the buyer. The EDEKA supplier guide of 15 October 2026 shows where the gap sits. The short version is here, the full requirements on the EDEKA page.

11 November 2026

4 min read

On 15 October 2026 EDEKA issued version 1.0 of its e-invoicing guide for suppliers, a handbook of 131 pages describing every element the group expects in an incoming invoice. It is based on EN 16931 and uses ZUGFeRD 2.xx and ZUGFeRD Extended in the CII syntax.

The document matters beyond EDEKA's own supplier base, because of what it does to the European standard: it takes fields the standard leaves optional and makes them mandatory. That is the gap between a technically valid invoice and a payable one, and the German mandate does not close it.

There is a date attached. The regional guide of EDEKA Nordwest, published on 3 June 2026 and publicly available, states that from 1 January 2027 invoices that do not meet its requirements will be returned for correction, with an automatic rejection naming the missing or incorrect content.

Five fields the standard leaves optional

A supplier reading the guide for the first time will find most of the effort concentrated in a small number of elements.

Seller GLN, BT-29

Mandatory, thirteen digits, schemeID 0088. Name and address do not replace it.

Item GTIN, BT-157

Mandatory on every line, schemeID 0160, in 8, 12, 13 or 14 digits.

Ship-to GLN, BT-71

Mandatory, and separate from the buyer. The invoice names both the paying entity and the location that received the goods.

Buyer reference, BT-10

Carries one of three fixed GLNs naming the contracting entity inside the group. Mandatory for suppliers under a central contract.

Payment reference, BT-83

Mandatory. Optional in the European standard.

These are master data questions before they are mapping questions. A GTIN for every article and a GLN for every legal entity and delivery location have to exist before a field can be filled. Obtaining and maintaining them takes longer than changing an output template.

Three requirements that touch the process, not the format

Alongside the field list, the guide sets three rules that no converter can satisfy on its own.

An invoice number may be issued only once per calendar year, and a repeated number leads to rejection of the data. As a rule one invoice is expected per delivery note, with anything else to be agreed bilaterally. And agreed article conditions have to be shown as line-level allowances rather than quietly netted into the price.

The guide also fixes its own vocabulary where EN 16931 leaves a choice: five unit codes, four document type codes, a closed list of discount reason codes, euro as the only accepted currency, and fixed keywords for deposit, transport equipment and organic control numbers.

One invoice per delivery note is a constraint on the billing run. A supplier that consolidates several deliveries into one monthly invoice is not solving a data mapping problem when it changes that. It is changing how and when invoices are created.

The requirements in full

We have worked through the handbook element by element and written the result up on its own page: the accepted formats and profiles, the mandatory details with their business terms, the delivery route including the rules for the transport mail, the fixed code lists, the profile decision between ZUGFeRD BASIC and Extended, and the deadline that applies to EDEKA Nordwest.

E-invoicing to EDEKA, requirements in detail

Formats, mandatory details, GS1 identifiers, delivery route and the questions suppliers ask most often.

Open the requirements page

How we help

We convert what your ERP produces into the profile and the field set your recipient expects, including the identifiers and references that sit outside the mandatory core of EN 16931. You can check what your current output contains with our free E-Invoice Validator for XRechnung, Peppol BIS Billing and ZUGFeRD.

Note: a converter can place an identifier in the right element, but it cannot create one that does not exist. Where a GTIN or a GLN is missing from the master data, that gap is resolved in the source system or with GS1, not in the invoice output.

Go through your own invoices with us

Book 30 minutes and we will look at your formats, your identifiers and the requirements of your recipients.

Request a demo

Frequent questions

Is a GLN or a GTIN legally required on an e-invoice?

No. Neither is required by the German VAT rules or by EN 16931, and GS1 Germany states that the GLN is not legally prescribed for electronic invoices. They become binding where a buyer requires them, and in retail that is common.

Can an invoice be rejected even though it conforms to EN 16931?

A conforming invoice meets the formal requirements. Whether the recipient can process it depends on the data its own verification needs, and GS1 Germany notes that missing information can lead to rejection in the same way as incorrect information.

Does the German mandate replace EDI in retail?

No. EDI invoices remain permissible where the parties agree and the format is interoperable with EN 16931. In food retail, EDIFACT-based exchange remains the dominant channel alongside the new formats.

Where do buyer-specific requirements have to be agreed?

GS1 Germany places extensions to the core invoice in the category of bilateral agreement. In practice the agreement is the buyer's invoicing guide, and a supplier should obtain the current version rather than assume the previous one still applies.

Sources

EDEKA Nordwest: supplier guide on electronic invoice transmission, version 1.0 of 3 June 2026 (PDF, in German) GS1 Germany: recommendation on implementing EN 16931 and ZUGFeRD/Factur-X, Part 1, version 2.0 (December 2025) GS1 Germany: e-invoicing with GS1 standards, including GLN, GTIN and EDI interoperability FeRD: ZUGFeRD and Factur-X, specification and profiles Section 14 of the German VAT Act (UStG)

The central EDEKA invoicing handbook referred to in this article is a supplier document and is not published on a public page. Suppliers obtain the current version from the invoicing entity. The regional EDEKA Nordwest guide is publicly available and linked above.

Stay informed

Get the latest updates on e-invoicing regulations and compliance straight to your inbox.