WoluTools
Find a tool

E-Invoice Validator · XRechnung, ZUGFeRD, Factur-X, Peppol

Validate XRechnung and ZUGFeRD e-invoices

Check invoice XML or a hybrid PDF against the official rules. You see which rule failed, where in the file, and the invoice itself in readable form.

or drop it here

XRechnung, UBL, CII XML or ZUGFeRD / Factur-X PDF

Free: 3 checks a day, files up to 10 MB, no account. Pro: up to 200 checks a day. See plans

No file at hand? Try the prepared exampleOpen the validator

  • Failed checks are never counted
  • Encrypted, deleted after 24 hours
  • Business values never changed
EXAMPLE RESULTSample data
Rule failures · 3
<ubl:Invoice> · XRechnung 3.0BR-DE-15 · buyer reference missingBR-CO-10 · line sum mismatch✓ Safe transport fix available
Readable report · findings CSV
What you get for each invoiceFailed rules with rule ID and XPath, the invoice in readable form, HTML and PDF reports, a findings CSV and, for unsigned XML, optional transport-only repairs
Profile
XRechnung
Rule failures
3
Safe transport fixes
1
Formats, limits & file handling
Works with
XML, ZUGFeRD / Factur-X PDF
Limit
Free: 3 files of 10 MB each · with a plan: up to 25 files, 20 MB each, 200 MB per check
You receive
Readable report, findings CSV, manifest and optional repaired XML
File handling
Encrypted sources and results · 24 hours

Upload structured invoice XML or a ZUGFeRD/Factur-X hybrid PDF. See the invoice in plain language, the exact technical rejection rules and only those transport repairs that cannot change business values.

THREE CLEAR STEPS

From invoice file to exact rule findings.

  1. 01
    Add the invoice

    XML or a ZUGFeRD / Factur-X PDF. Type, size and XML safety are checked first.

  2. 02
    Read the findings

    Each failed rule with its ID and XPath, next to the readable invoice.

  3. 03
    Download the report

    HTML and PDF reports, findings CSV and optional repaired XML. Failed checks are never counted.

Interactive synthetic validation

See the rejection in the invoice, not just in raw XML.

Choose a fictional example. The browser switches prepared, versioned results and never uploads a file.

✓
No public uploadSynthetic invoice data only
Technical resultRejected · 2 errors
InvoiceINV-2026-0815
SupplierNorthstar Parts Ltd
BuyerExample Public Office
Payable€1,487.50
Error · BR-CO-15Amounts due for payment do not reconcile./Invoice/cac:LegalMonetaryTotal/cbc:PayableAmount

The payable amount must equal the gross total minus the paid amount plus rounding.

Error · BR-DE-21The buyer electronic address is missing./Invoice/cac:AccountingCustomerParty

Add the required buyer endpoint in the source system. WoluTools will not guess it.

Technical validation only.This is not tax, accounting or legal advice and does not guarantee recipient acceptance.

One upload, three useful layers

From machine format to an exact next step

  1. Add structured invoices.Upload one to 25 XML or supported hybrid PDF files. Type, size, XML safety and PDF encryption are checked first.
  2. Read before debugging.Invoice number, parties, dates, currency, totals and line items appear in a consistent human-readable view.
  3. Resolve exact findings.Blocking rules, warnings, source engine and XPath stay linked to the affected document.
  4. Confirm only safe repairs.Unsigned XML can receive transport-only fixes; financial and tax content is never guessed or silently changed.
  5. Download the evidence.Receive HTML and PDF reports, protected findings CSV, complete technical JSON, raw engine reports, unchanged originals, and a SHA-256 artifact inventory.

Pinned local validation

KoSIT 1.6.2XRechnung 3.0.2 rules released 31 January 2026.
Peppol 3.0.21May 2026 Billing BIS rules for UBL Invoice and CreditNote.
Mustang 2.26.0ZUGFeRD 2.5.2, Factur-X 1.09.2 and CEN EN 16931 Schematron 1.3.16.
Self-verifying manifestEvery other package artifact records its byte size and SHA-256 alongside engines, rules, repairs and boundaries.

Clear boundary

A normal visual PDF is not converted into an e-invoice. Signed documents are never repaired. Recipient-specific portal requirements can still exist outside the validated standards.

Technically valid but commercially wrong?

Compare the invoice with the purchase order.

The Invoice vs Purchase Order Checker finds price, quantity, receipt and unexpected-charge differences after document fields are confirmed.

Open Invoice vs Purchase Order Checker →
Which files can I validate?

Structured invoice XML in XRechnung, ZUGFeRD, Factur-X, UBL or Peppol form, or a hybrid PDF with the invoice XML embedded. Free checks take up to 3 files of 10 MB each; with a plan, up to 25 files, 20 MB each and 200 MB per check.

Can this create an e-invoice from a normal PDF?

No. The input must already contain structured invoice XML. Accounting data is never guessed from a visual invoice.

Which repairs are automatic?

None are applied without confirmation. Only transport-level repairs that cannot change business values are offered, and signed files are blocked from repair.

Does valid mean legally correct?

No. It means the file passed the pinned technical rules used for that report. Tax, legal, contractual and recipient-portal requirements remain separate checks.

What stays in the download?

Unchanged originals, readable HTML and PDF reports, a protected findings CSV, the complete technical JSON, the raw engine reports and a self-verifying SHA-256 manifest.

Available now

Understand the rejection before changing the invoice.

Use the prepared example now. The encrypted validation runs on your own files without an account.

Inspect sample validationReview safeguards