E-invoice validator for EN 16931 and XRechnung

The result checks invoice structure, fields and totals against EN 16931 version 1.3.16, plus XRechnung 3.0.2 national rules 2.6.0 when chosen. Each report names the version used. For final acceptance, send the corrected invoice through your recipient’s required channel and keep their response.

For Peppol delivery, ask your Peppol provider to check its rules and confirm delivery. We check official rule releases hourly; see the rule sources and checking details.

You can check an invoice up to 10 MB. If a check reaches a time or report limit, correct the reported errors and check the file again. For a larger invoice, contact support to arrange a check.

Pro US$9/month supports 25 files per batch; Team US$29/month supports 100. Existing plan limits apply; no separate invoice pricing. Batches run sequentially and can take several minutes. Compare plans.

EN 16931 guide · XRechnung guide · API, CLI and Actions documentation

UBL 2.1 and UN/CEFACT CII D16B are different XML vocabularies for the European invoice model. UBL uses Invoice or CreditNote roots and separate aggregate/basic namespaces. CII uses CrossIndustryInvoice with trade agreement, delivery and settlement structures. A field has different element paths in the two syntaxes; translate business terms rather than renaming tags.

Select EN 16931 for the fixed European semantic checks. Select XRechnung when the recipient asks for that German profile: it adds national constraints, including electronic addresses and buyer-reference requirements. A Leitweg-ID can be the buyer reference required for a German public recipient; confirm the actual recipient identifier instead of inventing one. Neither mode sends the invoice to a portal.

Snapshot checked on 2 November 2026. These dates describe selected scopes and transitions; the format accepted by a particular recipient still matters.

• EU public procurement: central receiving obligations from 18 April 2019, with a possible subcentral extension to 18 April 2020. EN 16931 itself is not a universal B2B mandate. Directive 2014/55/EU.
• Germany: federal B2G supplier obligations from 27 November 2020, subject to exceptions. Domestic B2B receipt from 1 January 2025; issuance transitions through 2027/2028 depend on turnover and exceptions. XRechnung is not the exclusive B2B format. Federal FAQ · BMF guidance.
• France: receipt for all businesses and issuance for large and intermediate businesses from 1 September 2026; issuance for small businesses and microbusinesses from 1 September 2027. Official timetable.
• Poland: KSeF issuance from 1 February 2026 for businesses above PLN 200 million 2024 sales; from 1 April 2026 for others, with a small monthly-sales transition through 2026 and exclusions. KSeF receipt from 1 February 2026. KSeF is a separate system and is not validated here. Official KSeF scope.

These examples show invoice errors that can appear together. Open a rule to find the affected field and try a correction.

1. BR-S-08: Standard VAT taxable base must match the lines (281 mutation reports)
2. PEPPOL-EN16931-R008: Empty XML elements are forbidden (111 mutation reports)
3. BR-CO-10: Line net total must equal the sum of lines (108 mutation reports)
4. BR-CO-04: Each line needs a VAT category code (77 mutation reports)
5. BR-25: Each invoice line needs an item name (72 mutation reports)
6. BR-21: Each invoice line needs an identifier (51 mutation reports)
7. BR-27: Item net price cannot be negative (51 mutation reports)
8. BR-S-05: Standard-rated lines need a positive VAT rate (39 mutation reports)
9. BR-CO-15: Gross total must equal net total plus VAT (34 mutation reports)
10. BR-22: Each invoice line needs a quantity (24 mutation reports)

Search the complete pinned rule index.

First repair one invoice and keep its passing output as a regression example. Then sign in with Pro for up to 25 XML files per batch, or Team for up to 100. Select files in the invoice validator, choose the same fixed package and consent to server processing for each selected invoice. Checks run sequentially with a visible per-file result; a passing first file does not establish that the whole batch passes. Compare plans and limits · Run a batch.