How to Validate E-Invoices in Germany: Step-by-step Guide

Validating an e-invoice in Germany means checking the structured invoice for format, business rules, and VAT content compliance so it can be received, processed, and deducted correctly under the country’s mandatory B2B e-invoicing obligations. 

Key Takeaways

• Validation must cover syntax, EN 16931 and XRechnung business rules, and the factual VAT content. 
• XRechnung is the core XML route for public invoicing, while ZUGFeRD adds XML to a PDF/A-3 file. 
• Missing mandatory fields can cause rejection, payment delays, and blocked input VAT deduction until correction. 

Germany’s E-Invoicing Mandate

Starting January 1, 2025, Germany has treated a domestic B2B e-invoice as valid only when it is issued, sent, and received in a structured electronic format that supports automated processing.

1. Transition Period: Paper and non-structured invoices remain permitted through 2026 (or 2027 for businesses under €800K turnover and EDI users), after which structured e-invoicing becomes mandatory for domestic B2B transactions.
2. E-Invoice Formats: Germany supports two structured formats, XRechnung (XML-based, common in public sector) and ZUGFeRD (a hybrid PDF/A-3 with embedded XML, where the XML takes precedence in case of conflict).
3. Transmission Channel: No specific delivery channel is mandated; businesses can use email, portals, or interfaces, as long as the invoice is structured and supports accurate VAT data processing.

What Is E-Invoice Validation?

E-invoice validation is the control process that tests whether a structured invoice is technically correct, semantically consistent, and complete enough for German VAT purposes. It is not just opening a file successfully. It is confirming that the invoice can be processed electronically and relied on for tax and accounting purposes. 

In practice, validation means checking three separate layers before the invoice is trusted.

1. Format Validation

This is the technical gate. The XML must conform to the expected syntax and schema, use valid structure, and contain the required machine-readable elements. If the XML is malformed, the invoice fails before any tax logic is even reviewed. 

2. Business Rule Validation

This is the semantic gate. The invoice may be well-formed XML and still fail because its values do not make sense together. Typical failures include missing required fields, invalid code lists, date conflicts, or VAT amounts that do not reconcile to taxable values and rates. 

3. Content Validation

This is the operational and tax gate. Even a technically valid invoice can still be wrong if the seller identity, buyer identity, VAT treatment, service description, or transaction values do not match the underlying deal. This is why validation software helps, but does not replace accounting review. 

How to Validate an E-Invoices in Germany: Step by Step Guide

This workflow keeps the process practical for finance teams, ERP owners, and invoice issuers.

Step 1: Identify the Format First

Start by confirming whether the file is XRechnung, ZUGFeRD, or another EN 16931-compliant structured format. XRechnung is XML only. ZUGFeRD is a PDF/A-3 file with embedded XML. This matters because ZUGFeRD needs one extra extraction step before technical validation. 

Step 2: Extract XML if the Invoice Is ZUGFeRD

For ZUGFeRD, the embedded XML is the authoritative invoice data. The PDF view is useful for humans, but compliance depends on the structured XML. If the XML and the visual layer differ, the structured part controls. 

Step 3: Run Schema Validation

Validate the XML against the applicable schema first. This confirms correct structure, namespaces, cardinality, and data types. At this stage, you are looking for technical faults such as malformed XML, missing required elements, or invalid encoding. 

Step 4: Run Business Rule Validation

After schema validation passes, run the invoice against EN 16931 and German CIUS rules. This is where mandatory field completeness, code list validity, calculation consistency, and conditional logic are checked. A file can pass schema validation and still fail here. 

Step 5: Review the VAT Content Manually

This is the part businesses often underestimate. BMF e-invoicing guidelines on e-Invoicing makes clear that all VAT-required fields must be present in the structured part, not merely referenced in an attachment. The invoice must also reflect the real transaction, including the correct parties, service description, supply date, VAT treatment, and totals. 

Step 6: Check the Mandatory German Fields

Before sending, confirm that all baseline EN 16931 fields are present and that Germany-specific requirements are handled correctly. For XRechnung, this often includes the buyer reference, and in public sector cases that means the correct Leitweg-ID. If this routing reference is missing, federal portals can reject the invoice outright. 

Step 7: Review the Validation Report and Correct Errors in Order

Fix technical errors first, then business rule errors, then content defects. This sequence matters because a broken XML structure prevents meaningful rule validation. Once the invoice passes, save the validation report as part of your compliance evidence. 

Step 8: Archive the Final Structured Invoice Properly

GoBD archiving matters as much as sending. The original structured invoice data must remain readable, unaltered, and accessible, and the 2025 GoBD amendment explicitly acknowledges the need for changes because mandatory domestic e-invoicing began on January 1, 2025. 

Step 9: Keep Validators and Rule Sets Current

Validation is not static. The European Commission continues updating EN 16931 validation artefacts and code lists, and KoSIT continues releasing validator configurations compatible with current XRechnung versions. A workflow that was compliant last year may start failing if the rule sets are not updated. 

Invoice Content and Mandatory Fields of an E-Invoice

The following table summarizes the field groups that matter most for German e-invoice compliance.

What Happens if Mandatory Information Is Missing?

Missing mandatory information can have the following effects

1. Immediate Rejection Risk

Missing mandatory fields can cause the invoice to fail validation and stop processing immediately. In federal or public workflows, missing routing or required data can trigger rejection before the invoice reaches the right department. In B2B workflows, the invoice may fail import into the buyer’s accounting system. 

2. VAT Deduction Risk

The bigger consequence is tax. If required VAT information is missing, the recipient may be unable to claim input VAT until a corrected invoice is issued. That turns a formatting failure into a cash-flow problem. 

3. Payment Delay and Extra Work

Missing data also delays payment. Suppliers must correct and resend the invoice, finance teams must recheck it, and approval workflows remain blocked. When this happens often, it becomes a supplier-performance issue, not just a document issue. 

How to Fix the Most Common E-Invoice Validation Errors

Most e-invoice validation failures come from a small set of recurring technical, data, and VAT issues, and they can usually be resolved quickly when the root cause is identified first.

Conclusion

e-Invoice validation is not a good to have requirement but a must have requirement. It is the checkpoint between invoice creation and tax usability. Businesses that treat validation as part of invoice design, master data governance, and archiving will move faster, get paid sooner, and defend VAT positions more easily. Businesses that treat it as a last-minute technical test will keep discovering the same failures after sending, when correction costs more and supplier credibility drops.