XRechnung is Germany's national e-invoice format, and it arrives as an XML file, not a PDF. That is why your email client shows nothing but code. To read it you need a viewer, a "visualisation application" in German tax guidance. Free options include "E-Rechnung ansehen" from the German tax administration at e-rechnung.elster.de, your own invoicing software, and browser viewers run by software vendors. A validator tells you whether the file is technically valid; whether the invoice is correct is still your own check. What you keep for eight years is the XML file as received. A PDF of the readable view does not replace it.
This article takes the recipient's side. Who has to send and receive e-invoices in Germany is covered in German E-Invoicing: Dates and Exemptions. This isn't tax advice; it is the German legal position according to the provisions cited in the text, as of November 2026.
How to tell that an e-invoice has arrived
In Germany an e-invoice usually comes in one of two shapes:
- A plain XML file. That is XRechnung. The attachment ends in
.xml, and in a text editor you see field names in angle brackets. You can recognise an XRechnung by the field "Specification identifier" (BT-24), which for version 3.0 starts with urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0. XRechnung exists in two syntaxes, UBL and UN/CEFACT CII, and a decent viewer reads both.
- A PDF with an embedded XML file. That is ZUGFeRD from version 2.0.1, the German sibling of the French Factur-X. You see the PDF as usual, and the actual e-invoice sits inside it as a file. For tax purposes the structured part counts: if the PDF image and the XML differ, the structured data prevails, and input VAT can only be deducted from the structured part (sections 14.4 (3) and 14c.1 (4a) of the German VAT Application Decree, UStAE).
A normal PDF without an embedded file is an "other invoice", not an e-invoice. To receive e-invoices, the email inbox you already have is enough (section 14.1 (5) UStAE).
XRechnung viewers: the free options
Everything in this table is the vendor's own statement from their website, as of November 2026, not from a hands-on test.
With an online viewer, an invoice with names, addresses and bank details ends up on someone else's server. For day-to-day use, the viewer inside software you already have a contract for, or a local tool, is the calmer choice. KoSIT, the office that publishes XRechnung, only provides building blocks for software vendors, not an app to double-click.
If you already use invoicing software, look there first. Lexware Office, for example, says an uploaded e-invoice is flagged in receipt capture and "the XML file is stored unchanged". Which tools do this at what price is compared in Accounting Software for Small Businesses.
Reading an e-invoice: the fields that matter
Viewers label fields differently, but the numbers are fixed by the European standard EN 16931:
BT-84 deserves a second look: if the IBAN does not match your records for that supplier, confirm it by phone before you pay.
Validating an e-invoice is not the same as checking it
The German Federal Ministry of Finance (BMF) keeps two checks apart.
The technical check (validation). A validator tests syntax and the business rules of the standard. The BMF letter of 15 October 2025 distinguishes:
- Format errors: the file does not match the permitted syntaxes. Then, for VAT purposes, it is not an e-invoice but an "other invoice in another electronic format" (para. 6a).
- Business rule errors: information is missing or contradictory, for example a VAT amount that does not match the stated rate. If the error affects a mandatory invoice detail under sections 14 and 14a of the VAT Act, the invoice is not compliant. If only a field such as BT-10 "Buyer reference" is missing, that is irrelevant for VAT (paras. 6b and 35a).
Free validators as of November 2026:
- E-Rechnungs-Validator run by BITBW, the IT service provider of the state of Baden-Württemberg. Per its documentation, you upload the XRechnung and get a green, yellow or red report to download. It uses the XRechnung 3.0.2 configuration plus rules for invoices to that state, so not every warning concerns a business-to-business invoice.
- Mustang, an open-source command-line tool (Java). With
--action validate it checks ZUGFeRD, Factur-X and XRechnung 3 on your own machine, per the project page. Quba builds on it.
- The KoSIT validator is the reference tool for developers; KoSIT notes it can temporarily report errors while rules are being updated.
The BMF says that a business acting with ordinary commercial care may rely on the technical result of a suitable validation tool, and suggests keeping the validation report as evidence (para. 35a).
The content check. A wrong VAT rate can sit in a perfectly valid file. Validation "does not replace the recipient's obligation to check the invoice for completeness and correctness", in the BMF's words. Service, quantity and price you check against order and delivery, as with any invoice. The steps for that are in 3-Way Match for Contractors, Step by Step.
When the file is broken
If the validator shows red, first check which rule is broken. For a format error or a wrong mandatory invoice detail, ask the sender for a corrected file and attach the report, because where an e-invoice is mandatory, an "other invoice" does not in principle entitle you to deduct input VAT (section 15.2a (1) UStAE, with exceptions in (1a)). Per the Baden-Württemberg validator's documentation, the maker of the invoicing software is generally responsible for a faulty invoice.
Refusing an e-invoice because you cannot open it does not help: a business that cannot receive it or refuses it has no right to a paper or PDF invoice instead (section 14.1 (5) UStAE).
Filing it properly: what you keep for eight years
Under section 14b (1) of the German VAT Act (UStG) you keep every invoice you receive for eight years, counted from the end of the calendar year in which it was issued. Section 147 (3) of the Fiscal Code (AO) also sets eight years for accounting vouchers. E-invoices add three rules:
- In the format received. Incoming invoices are kept in the format in which they arrived, so an XRechnung stays XML (section 14b.1 (1) UStAE, para. 131 of the GoBD, Germany's rules for electronic bookkeeping). The structured part has to remain intact in its original form and machine-readable.
- The readable view is no substitute. A PDF produced by your viewer is a reading aid. The GoBD say explicitly that the structured part must not be deleted by a format conversion (para. 125). You may file the PDF as well, but never instead of the XML.
- For ZUGFeRD, the structured part is enough. You only have to keep the PDF image if it contains additional information relevant for tax, such as booking notes (paras. 119 and 131 GoBD as amended on 14 July 2025). If you file the original file, you have both anyway.
In practice: file the original XML, and next to it, if useful, the validation report and a PDF view, all with the same name. For VAT purposes alone, storing the file outside a GoBD-compliant system is not in itself a breach, says the BMF; for bookkeeping under the Fiscal Code the GoBD still apply. Filing a stranger can follow is described in Digital Receipt Filing That Holds Up.
Where an AI employee helps
In my business, Peter, my AI employee for receipts, screens newly arrived receipts in my bookkeeping interface in the browser. He assigns the receipt type, matches the credit card statement line by line and reports what doesn't add up. He can also check invoices. He follows a written process description; whatever isn't in it, he doesn't do. He doesn't book entries: every month he uploads the receipts to DATEV Unternehmen online with my login, and final approval stays with me and my accountant.
An e-invoice tends to make that groundwork easier, because amount, date, invoice number and IBAN sit in the file as fields. The whole route from inbox to receipt is described in AI Agent for Bookkeeping and Inbox.
Frequently asked questions
How do I open an XRechnung for free?
With a viewer: "E-Rechnung ansehen" at e-rechnung.elster.de, a vendor's browser viewer or your own invoicing software. The free desktop app Quba opens XRechnung and ZUGFeRD locally.
Why do I only see code when I open it?
Because an XRechnung is XML, which according to the BMF is "not suitable for visual inspection by the human eye".
Can I save the XRechnung as a PDF and delete the XML?
No. You must keep the structured part in the format received for eight years; a PDF of the view may be filed in addition.
What is the difference between a viewer and a validator?
The viewer makes the file readable. The validator checks technical compliance and produces a report. Neither tells you whether price and service are right.
Do I have to validate every e-invoice?
The BMF letter does not state an explicit obligation. It describes validation as support for your check of completeness and correctness and suggests keeping the report.
What to do next
Take the last e-invoice from your inbox and do three things: open it in a viewer, run it through a validator once, and check whether the original XML sits where your receipts stay for eight years. Then you know whether your process holds or whether only the PDF ended up in the folder. If you have to send e-invoices yourself, ZUGFeRD: How to Create a German E-Invoice covers the other direction.
For your individual case, we can look at it together: get in touch via the contact page. Peter is available as a template to download in my community, the AI Employee Framework, where you adapt him to your own process.