AP e-Invoicing in Germany 2026: How to Receive, Validate & Archive

German businesses have had to receive structured e-invoices since January 2025. Issuing them is being phased in: transitional relief under § 27 Abs. 38 UStG ends on 1 January 2027 for issuers above 800,000 euros prior-year turnover, and on 1 January 2028 for the rest. Here is how AP teams should receive, validate, post and archive them.

Key Takeaways

• Receipt obligation has been live since 1 January 2025 for every domestic Unternehmer under § 2 UStG, including freelancers, landlords and Kleinunternehmer. No threshold, no exceptions, and an email inbox is sufficient.
• Issuance deadlines: 1 January 2027 for issuers above 800,000 euros prior-year turnover, 1 January 2028 for everyone else (§ 27 Abs. 38 UStG).
• Two valid format routes under § 14 Abs. 1 Satz 6 UStG: conform to EN 16931, or use a format agreed with the supplier that allows correct and complete extraction into an EN 16931-conformant or interoperable format.
• Validating and PO-matching an incoming e-invoice is not a legal obligation. It is where the commercial return sits.

What is AP E-Invoicing in Germany?

AP e-invoicing is the process of receiving, validating, processing, and archiving supplier invoices in a structured electronic format. Earlier, the AP team had to manually read an invoice and enter data into the ERP system. However, under e-invoicing, the ERP system can capture structured invoice data and use it across validation, matching, approvals, and posting.

The key term here is ‘structured’. Although a PDF document can be received via email, it does not qualify as an electronic invoice automatically. Under German VAT rules an e-invoice must be issued, transmitted and received in a structured electronic format that enables electronic processing. 

The format must either conform to EN 16931, or be a format agreed between issuer and recipient from which the VAT-required particulars can be extracted correctly and completely into an EN 16931-conformant or interoperable format.

How Does AP E-Invoicing Work in Germany?

There is no requirement from the German government that all B2B invoices must pass through an official clearance portal. Instead, businesses can use various transmission methods such as email, EDI, Peppol, or service provider platforms.

The BMF is explicit that the law prescribes no particular transmission route, and it also accepts an electronic interface, shared access to a central storage location within a group, or download from a portal.

The transmission route is a matter for the parties to settle commercially, and it is a separate question from whether the invoice format itself is compliant. For AP teams, the process typically works as follows.

1. Receive the Supplier Invoice

The supplier sends the invoice via the chosen channel. For instance, a supplier sends invoices in ZUGFeRD format via email. Another supplier might deliver its invoices via Peppol. A large supplier may deliver over an established EDI connection.

A business must ensure that its AP system can accommodate all these methods of invoice delivery without the need for setting up a specific procedure for each supplier.

2. Identify the Invoice Format

The AP system needs to determine whether the invoice received is XRechnung, ZUGFeRD, or any other structured format. This matters because the data may not look the same to the AP user. 

XRechnung is an XML-based structured invoice that does not contain a normal PDF that one can open and read. In contrast, ZUGFeRD is a combination of a human-readable PDF/A-3 document with an embedded structured XML.

3. Validate the Invoice

Validation should be done before an invoice goes through the accounting process. The system needs to determine whether the invoice meets the necessary structure and whether all mandatory elements have been filled in correctly. 

The legally mandatory particulars cover supplier and buyer details, invoice number, dates, VAT rates and amounts, line items, totals and currency. A purchase order reference (BT-13) is an optional field in EN 16931 and in XRechnung, so treat it as an internal business check rather than a compliance field.

4. Match the Invoice with Internal Records

Once the e-invoice has been validated, AP automation software can then cross-reference the invoice against the appropriate purchase order and goods receipt, along with the supplier master file.

In the case of three-way matching, this can involve:

Purchase Order -> Goods Receipt -> Supplier Invoice

If the quantities and values are equal, then the invoice can proceed towards automatic approval. If not, then the invoice will go into an exception queue. Here is where the value of good AP automation comes in. 

This is not about removing humans from the equation, but rather about ensuring that humans don't spend time validating invoices that aren't problematic.

5. Post the Invoice to the ERP

Once validated and approved, the invoice can be posted to the ERP or accounting system. The AP department need not enter data that is already available in the structured invoice. This is one of the major benefits of AP e-invoicing. Data from the supplier’s system can be moved to the buyer’s system without much manual effort. 

6. Archive the Original Invoice

Under § 14b Abs. 1 UStG a business must keep a copy of every invoice it issues and every invoice it receives for eight years, counted from the end of the calendar year in which the invoice was issued. For an e-invoice, at least the structured part has to be kept intact in its original form.

That is particularly important for ZUGFeRD invoices. Saving only the visible PDF while deleting the embedded XML can create a problem because the structured component is part of the e-invoice.

The archive should allow the invoice to be retrieved and the original structured data to remain intact.

AP Automation for Electronic Invoices

While e-invoicing and AP automation go hand-in-hand, they are two different processes. E-invoicing provides the AP department with structured data. AP automation dictates what is going to happen with this data. 

A basic setup may involve simply receiving an XML file and entering it into the ERP. However, a stronger AP workflow will involve validating the invoice, cross-referencing and matching it against the purchase order and goods receipt note, extracting the relevant fields, routing it for approval, flagging exceptions, and then posting it automatically to the ERP.

Let's consider a simple example:

A company based in Germany gets 5,000 supplier invoices per month. If each invoice requires a person to validate the supplier name, invoice number, VAT amounts, PO reference, and totals in order to post it, then the company has only digitised their invoices but has not automated their AP process.

Now, let's apply the same AP workflow to structured invoices. First of all, the system validates the invoices. Next, it will match the invoices with the POs and goods receipt notes, where applicable. The invoices that pass validation automatically are posted without any intervention. Only exceptions reach an AP employee. 

This approach changes the way AP teams measure results. Instead of the question ‘How many invoices have we processed?’ they should ask:

• How many invoices were validated automatically?
• How many invoices required human intervention?
• What are the most popular reasons for rejection?
• How many invoices are waiting for approval?
• How many didn't pass PO matching?
• How much time did it take to resolve an exception?

These metrics show if the integration is working effectively.

Common AP E-Invoicing Challenges in Germany

Once supplier invoices start coming in, things can get a little more complicated under e-invoicing. Different formats, channels, and validation issues can quickly create extra work for AP teams. Here are some of the common challenges that AP teams can anticipate with the onset of e-invoicing:

1. Receiving Invoices Through Different Channels

A company can receive a structured invoice through email, Peppol, EDI, or an ERP connection. Germany does not prescribe a mandatory channel for exchanging domestic B2B e-invoices. The AP workflow therefore needs to incorporate different channels into a single controlled process. Otherwise, the AP team ends up with one workflow for email invoices, another for Peppol, and a third for EDI.

2. Supporting Multiple Formats

Germany has more than one format for representing structured invoice data. XRechnung is XML-based. ZUGFeRD combines a PDF/A-3 document with an embedded XML. Peppol BIS Billing 3.0 uses structured UBL data and can be exchanged over the Peppol network when the parties use it. EDI needs to be looked at in two parts. 

An EDI procedure that allows the VAT-required particulars to be extracted correctly and completely into an EN 16931-conformant or interoperable format counts as an e-invoice and can continue indefinitely by agreement between the parties. An EDI procedure that does not meet that condition may only be used until 31 December 2027 under the transitional rule in § 27 Abs. 38 UStG.

An AP system should not force suppliers into one format unnecessarily. Instead, businesses must build a workflow where invoices can be received in multiple different formats and data extracted seamlessly thereafter into the AP system.

3. Handling Invalid Invoices

A machine-readable invoice is not automatically a correct invoice. The XML can be syntactically valid and still contain incorrect business information. For example, a supplier may submit a valid invoice with a wrong purchase order number. Or the invoice total may not tally with the line items. Or the VAT treatment may not match the transaction. The AP system needs to identify these issues and flag them for rectification.

Not every incoming document has to be an e-invoice. The obligation only bites where a VAT invoicing obligation exists, so it excludes B2C and supplies exempt under § 4 Nr. 8 to 29 UStG. Even where an invoicing obligation exists, no e-invoice is required for small amounts up to 250 euros gross (§ 33 UStDV), travel tickets (§ 34 UStDV), or supplies by Kleinunternehmer (§ 34a UStDV). AP rules should allow for these rather than treating them as exceptions.

4. Integrating with Existing ERP Systems

Most large businesses are not starting from scratch. They already have SAP, Oracle, Microsoft Dynamics, or another ERP, along with supplier master data, purchase orders, and approval workflows. The challenge is connecting e-invoicing to that environment without creating another standalone process.

A successful AP e-invoicing implementation should fit into the existing finance architecture rather than asking AP teams to work across multiple disconnected systems.

5. Archiving the Wrong Version

This is an easy mistake to make. An AP team may save the invoice as a PDF because that is what users can read easily. But if the invoice contains structured XML, the original structured data also needs to be preserved.

For German VAT purposes the retention period is eight years under § 14b Abs. 1 UStG, reduced from ten years by the Viertes Bürokratieentlastungsgesetz with effect from 1 January 2025. The structured part of an e-invoice must remain available unaltered for that whole period.

How to Choose the Right AP E-Invoicing Solution

When choosing the right AP e-invoicing solution, the first question many businesses ask is "Does this platform support XRechnung?". However, this is only the starting point. A practical evaluation should cover the entire AP process from beginning to end.

1. Check Format Support

The solution should support the structured formats that your suppliers actually use, including XRechnung and relevant ZUGFeRD profiles. It should also have a clear approach to other EN 16931-compliant formats and existing EDI processes.

2. Check Transmission Channels

Do not assume Peppol is the answer for every supplier. Some suppliers may use Peppol. Others may use email or EDI. Your AP solution must be able to bring those invoices into a common workflow.

3. Look at Validation Capabilities

Ask what the platform validates. There is a difference between checking whether an XML file follows a schema and checking whether the invoice makes commercial sense. A good solution should support both technical and business validations.

4. Test the ERP Integration

The invoice should not become another file that someone manually uploads into the ERP. Check how the solution connects to your ERP, how invoice fields are mapped, how supplier master data is handled, and how exceptions move back to AP users.

This is often where implementation projects become challenging.

5. Understand Exception Handling

No AP system will make every invoice touchless. The better question to ask is what happens when something goes wrong. Can the system explain why an invoice failed? Can it send the invoice to the right person? Can the user correct the issue without restarting the entire process?

These details matter once invoice volumes increase.

6. Verify Archiving

Confirm that the solution preserves the original structured invoice and supports the applicable eight-year retention requirement. Do not settle for a generic document storage feature. The archive needs to support retrieval and preserve the integrity of the relevant invoice data as per German VAT rules.

How ClearTax Simplifies AP E-Invoicing in Germany

ClearTax brings invoice receipt, validation, processing, and archiving into a single workflow. For AP teams, this means that suppliers do not need to use one standard route for every invoice. 

ClearTax supports major German formats such as XRechnung and ZUGFeRD, along with channels such as Peppol, EDI, and email. Once an invoice enters the AP system, the structured data can be validated before it moves into the accounting workflow. 

Business rules can then be applied to identify issues such as missing information, incorrect values, or mismatches that require AP review. The workflow can also connect with the ERP system so that the validated invoice data does not need to be manually entered again.

ClearTax E-Invoicing can help with:

• ERP Integration: Connect ERP systems such as SAP, Oracle, and Microsoft Dynamics with the e-invoicing workflow.
• Data Transformation and Validation: Validate invoice data and convert it into compliant structured formats such as XRechnung and ZUGFeRD before transmission.
• Multiple Transmission Channels: Support Peppol, EDI, and email invoice transmissions through a centralised platform.
• Multi-country Support: Connect your ERP with e-invoicing requirements across Germany and other countries through a single integration framework.
• E-Invoice Lifecycle Tracking: Monitor invoice submission, delivery, validation results, and status updates through a unified dashboard.
• Archiving: Support compliant retention workflows for e-invoices and preserve the structured invoice data required for audit purposes.

The real benefit is not simply that ClearTax can read an XML invoice. It is that the invoice can continue through the AP process without losing its structure or creating another manual process. Further, a centralised workflow makes invoice statuses easier to track and manage. 

Conclusion

Businesses in Germany have already begun receiving e-invoices, and hence the setting up of AP e-invoicing is not something that can be delayed until 2027 or 2028. The first thing required is for the capability to receive structured e-invoices. The real opportunity lies in using this structured data to enhance the whole AP process.

Businesses that treat this as just a file-format change will probably end up with more manual work around a new format. While those that see it as an upgrade to their AP process will be able to automate the whole process of validation, matching, approvals, postings, and archiving using the same invoice information. That is the difference between being able to receive an e-invoice and actually being ready for e-invoicing.