AR E-Invoicing in Germany 2026: Format & How to Create

AR e-invoicing in Germany is moving from a process choice to a compliance requirement. From January 2027, businesses whose total turnover in the previous calendar year exceeded €800,000 will need to issue structured e-invoices for domestic B2B transactions. Other businesses follow suit from January 2028. For finance teams, the change is not simply about replacing PDFs. Invoice data, validation, customer delivery, and ERP integration need to work together from day one.

Key Takeaways

• From January 2027, businesses whose total turnover in the previous calendar year exceeded €800,000 must issue e-invoices for domestic B2B supplies, and the obligation extends to the remaining businesses from January 2028. 
• Some categories stay outside it permanently, including small entrepreneurs under § 19 UStG, invoices with a gross total of €250 or less, and passenger transport tickets.
• An e-invoice must be issued, transmitted and received in a structured electronic format that permits electronic processing, and that format must either follow the EN 16931 standard or be agreed between the two parties on the condition that all VAT-required information can be extracted correctly and completely into an EN 16931 compliant or interoperable format.
• AR teams need to think beyond invoice creation. Customer master data, tax information, validation, delivery, exception handling, and ERP integration all affect whether the process works properly.

What is AR E-Invoicing in Germany?

Accounts Receivable e-invoicing, or AR e-invoicing, is the process of creating, validating, sending, tracking, and storing customer invoices in a structured electronic format. In Germany, a compliant e-invoice must allow electronic processing and must use either an EN 16931 based format or a format the parties have agreed, provided the VAT-required data can be extracted correctly and completely into an EN 16931 compliant or interoperable format. 

Unlike a PDF, the invoice data can be read and processed directly by accounting systems. This is important due to the fact that accounts receivable departments have to deal with large volumes of invoices. 

Since invoice data used to be typically contained in PDF files, it was required to be extracted, validated, and entered into an accounting or ERP system by a person or software. However, a structured e-invoice eliminates most of the manual processes involved. It allows the automated processing of invoices, with only exceptions requiring manual intervention.

AR E-Invoicing vs AP E-Invoicing

The difference is quite simple. One deals with outgoing invoices, whereas the other deals with incoming invoices. Let’s break it down.

• AR e-invoicing deals with invoices a business creates and sends to its customers. The focus is on billing customers correctly, sending invoices through the required channel, tracking delivery and payment status, and managing exceptions.
• AP e-invoicing deals with invoices a business receives from its suppliers. The focus shifts to invoice capture, validation, purchase order matching, approval, posting, and payment.

For AR teams, the biggest operational risk is often not generating the invoice itself. It is sending an invoice with incorrect customer or tax data and discovering the problem only after the customer rejects it.

How Does AR E-Invoicing Work in Germany

The AR e-invoicing process starts well before the invoice reaches the customer. First, the business generates the invoice from its ERP, billing platform, or invoicing system. The customer details, invoice numbers, dates, line items, tax information, and payment details must be accurate.

The invoice is then converted into a permitted structured format, which the supplier and customer agree between themselves. Popular formats used in German e-invoicing are XRechnung and ZUGFeRD. XRechnung is a structured XML format based on EN 16931. ZUGFeRD can combine a human-readable PDF with structured XML in a single hybrid document. Not every XML file qualifies as an e-invoice. The underlying structure and business rules matter.

Before sending the invoice, the business should validate it. This is where many avoidable errors can be caught, such as missing mandatory information, incorrect VAT data, or inconsistent totals. The German Federal Ministry of Finance recommends validation as a useful control, although validation itself is not a separate condition for tax recognition.

The validated invoice can then be transmitted to the customer. Depending on the arrangement, businesses can use email, EDI, Peppol, direct ERP connections, or service provider platforms. Germany does not operate a general central B2B clearance model where every invoice must first pass through the tax authority.

Finally, the invoice and relevant records must be retained in a way that preserves their authenticity, integrity, and readability. The original structured data matters. Simply keeping a PDF copy of an XML invoice is not enough.

How to Create EN 16931 Compliant E-Invoices in Germany

Creating a compliant e-invoice involves steps like identifying the required data elements, choosing the right format, and validating the invoice before sending it to the customer. Let’s break it down.

1. Identify the Required Data Elements

Creating a compliant e-invoice starts with getting the underlying invoice data right. The structured invoice should contain the information required under German VAT rules and the applicable EN 16931 business rules. This includes information such as:

• Seller and buyer name and address
• Invoice number
• Invoice date
• Date of supply or service, where applicable
• Description of goods or services
• Quantity and unit
• Net amounts
• VAT rate and VAT amount
• Total invoice amount
• Currency
• Applicable tax identification details
• Payment information and other relevant invoice information

The exact fields required can vary depending on the transaction. For example, reverse-charge transactions and other special VAT scenarios may require additional information.

The German VAT Act lays out the mandatory invoice information, while EN 16931 provides the structured semantic model and associated rules for electronic invoicing.

2. Choose the Right Format

For most businesses, the practical choice will be between an EN 16931-compliant implementation, such as, but not limited to, XRechnung or ZUGFeRD.

• XRechnung: XRechnung is a structured XML format based on EN 16931 and is widely used for German e-invoicing. It is machine-readable rather than designed for people to read directly.
• ZUGFeRD: ZUGFeRD is a hybrid format containing a human-readable PDF and an embedded XML. The XML component is what enables automated processing. Not every ZUGFeRD profile qualifies. The BMF accepts ZUGFeRD from version 2.0.1 onwards, with the MINIMUM and BASIC WL profiles excluded because they do not carry the full set of data required.

The mistake to avoid here is choosing a format simply because the invoice looks right on screen. Compliance is about the structured data underneath.

3. Validate Before Sending

Once the invoice has been generated, run it through an appropriate validation process. A good validation layer should check both the technical structure and relevant business rules. This step can help identify problems before the invoice reaches the customer.

That is particularly useful for AR e-invoicing because an invalid invoice can create a chain of problems. For instance, if a customer rejects it, the AR team will need to investigate the matter. Then the invoice is sent for correction, and a new document is issued. This could push the payment back by several days or weeks. A single incorrect field can create a surprisingly long rectification process.

How to Automate the AR E-Invoicing Process in Germany? A Step-by-Step Guide

Automation would be most efficient if implemented at an early stage in the accounts receivable process. Plugging an electronic invoicing tool into an already existing billing process is not going to solve the issue of poor quality invoice data.

Step 1: Generate the Invoice from the ERP

The ERP or billing system would still serve as the source of record for customer, transaction, and tax information. When an invoice is generated, the system would need to produce the required data in structured form instead of producing a PDF as the primary document.

Step 2: Map ERP Data to the Required Invoice Structure

This is one of the most important parts of the implementation. ERP fields do not always map neatly to EN 16931 requirements. Customer identifiers, tax numbers, payment information, product descriptions, and VAT data may sit in different fields or may not be captured consistently.

The mapping needs to be tested using real invoices with different types of transactions, and not just a sample invoice or two.

Step 3: Validate the Invoice

Send the structured invoice through a validation layer before transmission. The validation process should identify missing fields, invalid values, and business-rule errors. Where possible, errors should go back to the source system rather than becoming manual corrections downstream.

Step 4: Convert into the Required Format

The system can then generate the appropriate e-invoice format based on the customer's requirements and the applicable transaction. For example, the output may be XRechnung or an appropriate ZUGFeRD profile.

Step 5: Send the Invoice Through the Agreed-Upon Channel

The transmission method depends on the customer relationship and technical setup. A business may use email, Peppol, EDI, an API connection, or a service provider platform. The important point is that the transmission channel and the invoice format are two separate considerations. Sending an XML file through email does not make an otherwise non-compliant invoice compliant.

Step 6: Track Delivery and Exceptions

This is where the advantages of an efficient AR automation process become evident. The AR team must have visibility into whether an invoice has been created, validated, transmitted, accepted, rejected or paid.

In case the invoice gets rejected due to an invalid VAT ID or customer reference number, the exception should be noted by the system and passed on to the appropriate team for rectification. 

Step 7: Archive the Invoice Correctly

The original electronic invoice and associated records need to be retained in an auditable form. For structured invoices, retaining the original structured data is important. Businesses should also maintain the controls needed to demonstrate the authenticity and integrity of the records.

Common AR E-Invoicing Challenges

The biggest challenges in AR e-invoicing are rarely about the invoice format itself. It usually is the data sitting behind it. Some common AR e-invoicing challenges include:

1. Incorrect Customer Master Data

An inaccurate VAT identification number or billing address can cause an invoice to fail validation or be rejected by the customer, and a missing buyer reference will fail the XRechnung business rules even though the BMF regards that field as irrelevant for VAT purposes. AR staff will have to review and clean up the master data before implementing e-invoicing to prevent validation issues in the future.

2. ERP Data Does Not Map Cleanly

Older ERP systems may not store information in the structure required for EN 16931. This often causes complications during integration projects. Though some of the information may be enough to generate a PDF invoice, it would still lack the information needed to generate an electronic invoice.

Businesses will have to map the invoice data from their ERP system to the required EN 16931 information and run validation checks to ensure that no information is missing in an invoice before it is issued.

3. Customer-specific Requirements

Not all customers will have the same technical environment. Some customers may be fine with receiving a structured invoice via e-mail. Other customers might request Peppol. A large enterprise client may have its own portal or EDI connection.

AR teams need to find a way to manage all these modes of invoice transmission from a single platform without creating a separate process for each customer.

4. Invoice Rejection and Exception Handling

While an e-invoice may have been generated automatically, it would still need human intervention if it fails validation. Businesses need to determine what happens in case of invoice rejections due to validation errors, delivery issues, or any other reasons. This step is often overlooked at the implementation stage.

5. Maintaining Audit-ready Records

Implementing e-invoicing does not mean that record-keeping obligations under VAT rules will cease to apply. In fact, invoices and their supporting records will now need to be retained according to the German VAT law in their original form. 

Saving the PDF of an e-invoice is no longer enough if the embedded XML is not saved in its original form. Invoices must be kept for eight years under § 14b(1) UStG, a period reduced from ten years with effect from 1 January 2025, and the clock starts at the end of the calendar year in which the invoice was issued

How to Choose an AR E-Invoicing Solution?

Selecting an AR e-invoicing solution only for its ability to produce an e-invoice in XRechnung or ZUGFeRD is not the right approach. A proper solution must be capable of so much more, spanning ERP integration, handling various kinds of invoice formats and transmission methods, and providing AR teams with real-time invoice status updates.

Here are five criteria that will help make your decision easier.

1. Compliance: Does the solution support EN 16931, the required structured invoice formats, and relevant German VAT rules? Can it keep up when regulatory rules change?
2. Integration: Can it connect with the ERP without creating another manual data-entry step?
3. Validation: Does it validate invoices before transmission and provide timely error messages?
4. Connectivity: Can it support the channels required by customers, such as Peppol, EDI, email, APIs, or customer portals?
5. Monitoring: Can AR teams get visibility into invoice status, delivery failures, and exceptions from one place?

The last point is typically easily overlooked. A solution that creates compliant invoices but gives the AR team no visibility into failures is only solving half the problem.

How ClearTax Simplifies AR E-Invoicing

ClearTax E-Invoicing helps German businesses 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.

For AR teams, this can reduce the manual work involved in creating and transmitting invoices while providing greater visibility into invoice status and exceptions. The focus should not be on creating an invoice in a new system. It should be on making the existing billing process work reliably in an e-invoicing environment.

Conclusion

There is more to AR e-invoicing in Germany than mere format changes. The process involves a shift in how companies create, validate, transmit, and archive their customers' invoices. The current implementation timelines provide ample opportunities for preparation and testing. 2026 should be the year the German businesses evaluate service providers, integrate their ERP systems, and perform rigorous testing of all use case scenarios to be e-invoicing-ready by 2027.

Accounts receivable teams must start by reviewing invoice data, followed by testing the ERP integration, and thereafter checking customer needs, validations, invoice transmissions, and exception handling. Businesses that build these controls early will have a much easier transition when the German e-invoicing requirements become fully applicable.