Validate an XRechnung invoice
Check an XRechnung invoice or credit note in UBL or CII against the XML schema, EN 16931 and the official XRechnung 3.0.2 rules. See each error with its rule ID and how to fix it.
- Free to use
- No signup required
- Invoice XML not stored
or drop your XML file here
XMLUBL or CIIUp to 5 MiB
No file to hand? Try a fictional sample:
The samples are fictional XRechnung 3.0 documents: every party, identifier and account in them is invented. Invoice, UBL, Invoice, CII, Credit note, CII, Invoice with an error, CII
It goes from your browser to Ironfang's servers in the UK, where it is processed and not stored. The result is shown here and not kept.
How your file is handled
- Your XML is sent only when you choose to validate or open it. A sample sends only that sample.
- It goes from your browser to Ironfang's servers in the UK, where it is processed and not stored. The result is shown here and not kept.
- Content-free request and security metadata, including your IP address, may be kept for up to 90 days.
- Anonymous rate limits apply. The largest document accepted is 5 MiB.
- See the privacy policy.
Need automated checks? Validate XRechnung in your application
A concrete example
The sample with an error is our CII sample invoice without its buyer reference, the Leitweg-ID. XRechnung requires it, so the validator reports BR-DE-15 and the invoice fails. Add the reference and it passes.
What is checked
Every layer, in order
The XML is read and checked against the schema of its syntax, UBL 2.1 or UN/CEFACT CII D16B, then the EN 16931 business rules, then the XRechnung rules. The result shows each layer and whether it was reached.
The official rules and levels
The rules are the official XRechnung 3.0.2 validator configuration, technical bundle 2026-08-31, run byte for byte, with the error, warning and note levels that configuration sets.
Findings you can act on
Each finding names its rule ID and where in the XML it applies. The most common XRechnung errors are explained in plain words, with the official rule text and the fix in both syntaxes.
Supported versions
- XRechnung 3.0.2, in the official technical bundle of 31 August 2026.
- UBL 2.1 Invoice and CreditNote, and UN/CEFACT CII D16B invoices and credit notes.
- The core XRechnung variant. The Extension and the CVD variant are recognised and reported as not supported yet, never checked as something else.
- XML only. PDF invoices, including ZUGFeRD and Factur-X, are not checked by this tool.
Validating is not viewing
To read an XRechnung as a document, with its parties, lines and totals, open it in the XRechnung viewer. Opening a document does not validate it.
Open the XRechnung viewerIronfang Finance API
Validate XRechnung in your application
Run the same checks through the Ironfang Finance API and handle the findings in your own workflow.
- The same outcome and findings as JSON, with the exact release that checked the document.
- Signed-in results are kept for 30 days, and an Idempotency-Key makes a retry return the same result without charging again.
- Peppol BIS Billing 3 validation and generation are available through the same API.
Questions
- Which XRechnung documents can I check?
- An XRechnung 3.0 invoice or credit note in XML, in UBL 2.1 or UN/CEFACT CII D16B, one document at a time, up to 5 MiB. It is checked against XRechnung 3.0.2, technical bundle 2026-08-31.
- Do I need an account?
- No. The validator on this page is free to use without signing up, within anonymous rate limits. An account is only needed to run the same checks through the API.
- What happens to my file?
- It is sent to Ironfang's servers in the UK only when you choose to validate it, processed there and not stored. Content-free request and security metadata, including your IP address, may be kept for up to 90 days.
- What does a pass mean?
- That the automated checks of the named release found no error in the XML you sent. It does not certify the invoice, does not guarantee that a recipient or a submission portal will accept it, and does not send it anywhere.
- Can I check a PDF, ZUGFeRD or Factur-X invoice?
- Not with this tool. It checks XRechnung XML. A PDF with an embedded invoice is a different check, and a normal PDF without invoice XML is not an electronic invoice at all.
- What about the XRechnung Extension and CVD?
- They are recognised and reported as not supported yet. They are never checked against the core rules as if they were something else.
Related
- XRechnung viewerOpen an XRechnung in UBL or CII and read it as a document.
- Peppol validatorCheck a Peppol BIS Billing 3 invoice against EN 16931 and the Peppol rules.
- XRechnung guideThe checks, the V2 API with a tested cURL example, reading results and the explained rules.
- Ironfang Finance APIValidation as JSON, results kept for 30 days, plans and pricing.
