When you need this
- A German customer or supplier sent you an XRechnung and all you see is XML tags. An XRechnung is a pure XML file with no PDF. This tool turns it back into a readable invoice, with English labels; the item descriptions stay as the sender wrote them.
- You received a ZUGFeRD or Factur-X PDF and want to see what is really in it. These hybrid invoices carry the data twice: once as a PDF for the eye and once as embedded XML for software. A PDF reader only shows the first. Here you see the XML, line by line.
- Before you pay: amount due, due date, IBAN and payment reference at a glance, with the IBAN check digits and the totals recalculated.
- You create e-invoices yourself – from your own software, an ERP or a shop – and want to know whether a file passes the official rules before you send it to a German or French customer.
- Filing or passing it on: “Print / save as PDF” turns the view into a page that looks like a paper invoice, for your accountant or your records. The validation results and technical details are not printed.
What an e-invoice is
An e-invoice in the sense of the European standard EN 16931 is a structured file, almost always XML, that software can read without guessing. A PDF sent by email is not one, even though it is electronic. The standard defines the content – the business terms, numbered BT-1, BT-2 and so on – and allows two XML syntaxes for it: UBL (OASIS Universal Business Language 2.1) and CII (UN/CEFACT Cross Industry Invoice). This viewer reads both and shows them the same way.
Countries build their own formats on top of EN 16931:
- XRechnung is the German format: pure XML in UBL or CII, with extra German rules (BR-DE-…). The buyer reference (BT-10) is mandatory; for public bodies it holds the Leitweg-ID, their routing ID. The viewer checks its check digits.
- ZUGFeRD (Germany) and Factur-X (France) are the same hybrid format,
developed jointly by FeRD and FNFE-MPE: a PDF/A-3 with the CII XML embedded, usually named
factur-x.xml. Profiles say how much data the XML holds – MINIMUM, BASIC WL, BASIC, EN 16931 and EXTENDED. MINIMUM and BASIC WL have no invoice lines and are not complete invoices under EN 16931. - Peppol BIS Billing 3.0 is the UBL format of the Peppol network. The viewer reads and validates it against EN 16931; the extra Peppol rules are not checked (see below).
Validation messages carry rule IDs such as BR-CO-15 or BR-DE-15. A click on one opens the rule with its full wording in E-invoice validation rules.
Where e-invoices are mandatory
This page only covers the two countries whose formats the tool validates, each from the official source:
- Germany: since 1 January 2025 every business in Germany must be able to receive e-invoices from other domestic businesses. For issuing there are transition periods: paper and other formats remain allowed for supplies in 2025 and 2026, in 2027 only for issuers whose total turnover in the previous year was at most €800,000, and from 2028 the obligation applies to all. For hybrid formats such as ZUGFeRD, the XML part is what counts for tax purposes, not the visible PDF.
- France: according to impots.gouv.fr (page updated 26 May 2026), all businesses must be able to receive e-invoices since 1 September 2026; large and mid-sized companies must issue them from that date, small and micro businesses from 1 September 2027. Between French businesses the invoice has to go through an approved platform (plateforme agréée) – a Factur-X sent by plain email does not fulfil the obligation.
This tool is not a transmission platform. It sends nothing to anyone; it helps you read and check a file.
What the tool checks
Checking happens in three stages. The first runs as soon as you open a file, the other two when you press “Validate officially”.
1. Arithmetic check – recalculates the totals according to the rules of EN 16931 and, if something is off, shows the amount on the invoice next to the recalculated one:
- sum of lines = all line net amounts added up (BR-CO-10)
- document-level allowances and charges match their totals (BR-CO-11, BR-CO-12)
- total excluding VAT = sum of lines − allowances + charges (BR-CO-13)
- total VAT = sum of the VAT per rate (BR-CO-14)
- total including VAT = total excluding VAT + VAT (BR-CO-15)
- amount due = total including VAT − amount already paid + rounding (BR-CO-16)
It also checks the check digits of every IBAN and of a Leitweg-ID in the buyer reference.
2. XML schema (XSD) – checks the form of the file: is every element allowed, in the right order and with the right data type? An error here is a format error. The file is checked against the schema that belongs to it: UBL 2.1 or CII D16B, or for ZUGFeRD/Factur-X the schema of its profile. Profiles differ mainly in which elements they allow, so a MINIMUM file with invoice lines already fails the schema.
3. Business rules (Schematron) – several hundred rules on the content: mandatory fields, allowed codes, date formats, VAT categories, the arithmetic rules above and, for XRechnung, the German rules. The result separates errors, warnings and notes and names the place in the file for every message.
Which rules apply depends on the format. The tool reads the specification identifier in the file (BT-24) and chooses the checks the way the official validators do:
- XRechnung (UBL or CII): schema, EN 16931 and XRechnung 3.0 – the same sequence as the KoSIT validator used by German public administration.
- ZUGFeRD/Factur-X: schema and rules of the profile – MINIMUM, BASIC WL, BASIC, EN 16931 or EXTENDED – from ZUGFeRD 2.5.2 (Factur-X 1.09.2, published 4 August 2026). The profile rules include the EN 16931 rules where they apply to the profile.
- Other UBL invoices (Peppol, for example): schema and EN 16931, validation artefacts 1.3.17 of the European Commission.
For this, your browser loads 0.6 to 1 MB of validation rules from xmoo.app once; after that everything runs in your browser. Validation usually takes about a second.
Example: validation step by step
“View sample invoice” opens a made-up XRechnung in CII syntax from a German electrical contractor to a municipality, as such invoices really arrive – German item descriptions, a Leitweg-ID in the buyer reference. It has three lines: 100 m of sheathed cable at €0.89 (€89.00), 3 hours of installation at €65.00 (€195.00) and a reference book at €24.90. The arithmetic check goes like this:
- Sum of lines: 89.00 + 195.00 + 24.90 = €308.90 (BR-CO-10). With no allowances or charges, that is also the total excluding VAT (BR-CO-13).
- VAT per rate: 19 % on €284.00 = €53.96 and 7 % on €24.90 = €1.743, rounded €1.74 – the book is taxed at Germany’s reduced rate. Together €55.70 (BR-CO-14).
- Total including VAT: 308.90 + 55.70 = €364.60 (BR-CO-15). Nothing has been paid yet, so the amount due is also €364.60 (BR-CO-16).
The official validation reports no errors for this invoice. If the total including VAT said €364.61 instead of €364.60, BR-CO-15 and BR-CO-16 would fire, both in the arithmetic check and in the EN 16931 rules. Without the buyer reference, the XRechnung rule BR-DE-15 reports an error. If the invoice number comes after the invoice date, the file still holds all the data but fails the XML schema, because the order is wrong. The tool’s automated tests check exactly these cases with every change.
What the tool does not check
- Peppol BIS Billing 3.0 rules. Peppol adds its own Schematron on top of EN 16931: rules with IDs such as PEPPOL-EN16931-R… and PEPPOL-COMMON-R…, plus national rules for Germany, Denmark, the Netherlands, Norway, Sweden and other countries (DE-R-…, DK-R-…, NL-R-…). A Peppol invoice that shows no errors here can still be rejected by a Peppol access point.
- The French reform rules. The approved platforms in France apply the DGFiP business rules – for example the billing framework (G1.02) or that the seller’s and buyer’s SIREN must exist in the directory (G1.63). The French version of this viewer explains them.
- Whether the visible PDF matches the XML of a ZUGFeRD/Factur-X invoice, and whether the PDF conforms to PDF/A-3. The viewer shows you the XML so you can compare yourself.
- Whether the content is right – whether you got the goods and the price was agreed. No software checks that.
- Small differences in severity: the KoSIT validator rates a few rules differently from the rule set itself. The tool shows the severity written in the rules.
How your file is protected
The invoice is read only in your browser. There is no upload, no server reading along, and nothing is stored. For a ZUGFeRD/Factur-X PDF, the tool finds the embedded XML file and unpacks it with your browser’s own decompression.
The display also runs in a sealed frame. This page shows ads, but the frame has its own, opaque origin: the ad and analytics scripts of this page cannot look into it, and neither ads nor analytics run inside it. A security policy also forbids the frame to send anything over the network. For the official validation it only loads the fixed rule files from xmoo.app – your invoice does not go with them.
Limits
- ZUGFeRD 1.0 (before 2.0.1) is not supported. Encrypted PDFs cannot be read.
- The profiles MINIMUM and BASIC WL contain no lines, so the line list stays empty.
- Extra fields of the EXTENDED profile and of the XRechnung extension are only partly displayed. They are still fully validated.
- The rules are those of XRechnung 3.0 and ZUGFeRD 2.5.2 / Factur-X 1.09.2. Files made for older versions can show messages that would not be errors under their own version.
- Rule texts come word for word from the official artefacts: English for EN 16931 and ZUGFeRD/Factur-X, German for the XRechnung rules of KoSIT (BR-DE-…).
For developers: the same validation as an API
To validate e-invoices inside your own software – incoming invoices, a shop, an ERP – this tool’s validation is available as a REST API: the xmoo E-Invoice API. It uses the same core and the same official rule sets, returns every message with rule ID, severity and location as JSON, and can also parse, convert and render the invoice as a PDF.
Unlike this tool, the API sends the invoice to our server in Helsinki (EU); it is processed in memory only and never stored. Billing runs through RapidAPI, with a free plan of 50 requests a month to try it out.
Frequently asked questions
How do I open an XRechnung?
Drag the XML file into the box above or pick it with “Choose file”. The tool shows it as an invoice page that you can print or save as a PDF. You do not need any software for it.
How do I know whether a ZUGFeRD or Factur-X invoice is valid?
Open the PDF and press “Validate officially”. The tool finds the embedded XML, reads the profile and checks the schema and rules of that profile. “No errors” means the file conforms to ZUGFeRD 2.5.2 / Factur-X 1.09.2 in that profile. For MINIMUM and BASIC WL the tool also points out that these profiles are not complete invoices under EN 16931.
What is the difference between the XML schema and the business rules?
The schema checks the form: which elements exist, in which order and with which data type. The business rules check the content: whether mandatory data is there and the data fits together. A file can fail the schema and still contain all the data – or pass the schema and carry a wrong total.
Do I have to upload the invoice?
No. Reading and validating run entirely in your browser. Only the fixed validation rules are loaded from xmoo.app; your file goes nowhere.
Can I convert the invoice to another format?
Yes, with the e-invoice converter: XRechnung UBL to CII and back, XRechnung to a ZUGFeRD PDF or ZUGFeRD to XRechnung, validated with the same rules as here.
Is there a German or French version?
Yes: the E-Rechnung-Viewer in German and the Visionneuse Factur-X in French, with the same checks.
Sources
- Germany: German Federal Ministry of Finance, questions and answers on e-invoicing (in German, as of March 2026); BMF letter of 15 October 2025 – section 14.1 (11)–(14) UStAE on formats and ZUGFeRD profiles, 14.4 on the XML taking precedence; transition periods: § 27 (38) UStG
- France: impots.gouv.fr, Je découvre la facturation électronique (in French, updated 26 May 2026, retrieved 12 November 2026) – calendar and approved platforms; DGFiP external specifications, annex 7 “Règles de gestion” (G1.02, G1.63)
- ZUGFeRD 2.5.2 (Factur-X 1.09.2) of 4 August 2026: information package from FeRD; licence of schemas and rules: disclaimer and rights of use (Apache 2.0). The same files ship unchanged in the Python package factur-x 7.7, which is where they come from here.
- EN 16931 arithmetic rules and official validation: EN 16931 validation artefacts of the European Commission, version 1.3.17
- XRechnung: validation rules (version 2.6.0 for XRechnung 3.0) and test files of KoSIT; which checks the KoSIT validator runs for an XRechnung: validator configuration, release v2026-08-31, also the source of the UBL 2.1 and CII D16B schemas
- Peppol BIS Billing 3.0: specification
and rules (rule IDs from
rules/sch/PEPPOL-EN16931-UBL.sch, retrieved 18 November 2026) and the code lists used for the meaning of codes (UNTDID 1001, 4461, 5305, UN/ECE Recommendation 20/21) - ZUGFeRD test invoices: Mustang project (Apache 2.0)
Software used and licences
- SaxonJS 2.7 runs the validation rules in the browser. Copyright Saxonica Ltd, redistributed unchanged under the SaxonJS licence (which also contains the disclaimer). Includes big.js, copyright Michael Mclaughlin, MIT licence.
- EN 16931 validation artefacts 1.3.17, © European Union, under the EUPL 1.2. Used here in compiled form (SEF); the source is in the release on GitHub.
- XRechnung Schematron 2.6.0 of KoSIT, under the Apache License 2.0. Used here in compiled form (SEF); the source is in the release on GitHub.
- ZUGFeRD 2.5.2 / Factur-X 1.09.2, schemas and rules of FeRD and FNFE-MPE, under the Apache License 2.0. The rules are used in compiled form (SEF); the code list they load as a separate file is inserted into them. Taken from factur-x by Alexis de Lattre (Akretion), BSD licence.
- XML schemas UBL 2.1, copyright OASIS Open (with the included XML Signature schema, copyright The Internet Society and W3C), and UN/CEFACT CII D16B, copyright UN/CEFACT, each redistributed unchanged with its copyright notice.
- xmllint-wasm 5.3.0 checks the XML schema: libxml2 as WebAssembly, copyright the authors of libxml and libxml.js, MIT licence. Included here as a single script without a worker, with the WebAssembly embedded.
Page last updated: 18 November 2026