Skip to content

Invoice XML Validator

Find the exact line and column where invoice XML breaks, then check what it says.

Or drop an XML file here

Try a sample

Quick Tool Overview

The Invoice XML Validator finds the exact line and column where invoice XML stops being well-formed, explains the fault, and then checks what the XML says — EN 16931 rules for UBL and CII, recomputed totals for plain invoice XML, a structure report for anything else.

What it does
Validates invoice XML files
You give it
Any XML invoice
You get back
Syntax faults located and invoice checks
Best for
Hand-edited and exported XML
Invoice Tools Free, unlimited use No sign-up Runs in your browser

About the Invoice XML Validator

Most rejected XML invoices are not wrong about VAT. They are not XML: an ampersand in a company name written as a bare &, a tag closed in the wrong order after a hand edit, a namespace prefix nobody declared, a second root element pasted onto the end. Parsers report these badly, and a receiving system often just says the file is invalid.

This checks invoice XML in two layers. First the syntax, with the exact line and column of the first fault, a plain explanation and the offending lines shown with a marker. Then, once the XML is well-formed, what kind of invoice it is: a UBL or CII e-invoice is checked against the EN 16931 business rules; the category’s plain invoice XML has its stated totals recomputed from its lines; any other XML gets a structure report of its root, namespaces, depth and elements.

The file is read by a strict parser in your browser, which behaves the same in every browser and never uploads the invoice.

Key features of the Invoice XML Validator

Strict parser

The same result in every browser.

Fault excerpt

The broken lines shown with a marker.

Namespace checks

Undeclared prefixes and wrong namespaces caught.

Invoice-aware

Business rules or recomputed totals once it parses.

Private

Nothing leaves your browser.

How to use the Invoice XML Validator

  1. 1

    Paste or drop the XML

    Any size; it is parsed locally.

  2. 2

    Fix syntax errors first

    The line and column are marked, with what the parser expected.

  3. 3

    Read the invoice checks

    Business rules for e-invoices, recomputed totals for plain XML.

  4. 4

    Check the structure

    Root element, namespaces and element counts.

Frequently asked questions

That the file follows XML’s own grammar: one root element, every tag closed in order, attribute values quoted, special characters escaped, namespace prefixes declared. A file that is not well-formed cannot be read at all.

Reviews of the Invoice XML Validator

What people who use the Invoice XML Validator think of it. Reviews come from visitors and are posted as written.

No ratings yet

Yours would be the first.

  • 5 0 reviews rated 5 stars
  • 4 0 reviews rated 4 stars
  • 3 0 reviews rated 3 stars
  • 2 0 reviews rated 2 stars
  • 1 0 reviews rated 1 star

Write a review

Used this tool? Your rating helps the next person decide.

Your rating

Plain text only — links, email addresses and HTML are not accepted. Your name and review are shown publicly; nothing else is collected. See the privacy policy.

0 reviews

Newest first

No reviews yet

Be the first to rate the Invoice XML Validator. It takes half a minute and no account.

Write the first review

More invoice tools