Skip to content
eDocument Tools

Free tools for electronic business documents

View, validate and debug UBL, UN/CEFACT CII, Factur-X and EN 16931 documents directly in your browser.

In these tools your document never leaves your device — no upload, no account, no document data in analytics.

Open the UBL viewer Open the CII viewer

Tools

Every tool here runs client-side. No tool uploads your file.

Supported standards

Reference pages written for engineers who have to make these documents work, not for procurement brochures.

The browser tools: your document never leaves your device

Processed in your browser

Files are read with the browser File API and parsed with the browser’s own XML parser. No tool has an upload step: the file is never sent anywhere.

Nothing is stored

The tools keep no database, no file storage and no session. Close the tab and the document is gone. Document content is never written to logs or analytics.

Hostile documents are refused

Documents carrying a DOCTYPE or entity declarations are rejected before parsing, which closes off XXE and entity-expansion attacks. Document values are never rendered as HTML.

Read exactly what is and is not processed

Validate from your own backend

Beta

The Validation API runs the same validation core as the tools above, as a server-side HTTP endpoint: one request, one explicitly named target, one report saying which layers ran and what each found. A document sent to it is processed in memory and discarded — the tools never upload anything, and the API only ever holds what you send it for as long as the request takes.

Explore the Validation API Getting started 
curl https://edocumenttools.com/api/v1/validate \
  -H "Authorization: Bearer $EDOCUMENT_API_KEY" \
  -F "target=en16931-1.3.16-ubl-2.1" \
  -F "file=@invoice.xml"

French e-invoicing

The French reform is built on UN/CEFACT CII, UBL and Factur-X. If you are implementing it, the CII viewer is the fastest way to see what your system is actually producing — and the reference pages explain how the syntaxes, the EN 16931 semantic model and the French rule sets relate to one another.

French e-invoicing overview The 2026–2027 timeline and obligations Validating a Factur-X before sending About Factur-X

Built for people who debug documents

Namespace-correct parsing

Elements are resolved by namespace URI and local name, never by prefix. A document that binds the UBL namespaces to foo and bar parses exactly like one using cac and cbc.

Values shown as written

Amounts, quantities and dates keep the lexical form found in your document alongside the interpreted value. A malformed decimal is shown, not silently corrected.

Honest about what ran

Checks that have not been implemented report “not run”, never a green tick. A validation layer is only reported as passing when it has actually executed.

No version guessing

All UN/CEFACT CII releases share one namespace, so the release cannot be read from a document. These tools say so instead of assuming D22B.

Frequently asked questions

Are these tools really free?

Yes. The browser tools need no account, no sign-up, no trial and have no usage limit. They run in your browser, so they cost nothing to operate per document.

Do my documents leave my device?

No. Every tool on this site reads and parses files locally using browser APIs. No file is uploaded, stored or transmitted, and no document content reaches analytics. The only network requests a tool makes are for this site’s own sample documents and, for the validator, its own schema and rule files. The Validation API is the one part of this project that works differently, because a developer sends it a document on purpose from their own server; it holds that document in memory for the request and stores nothing.

Which formats are supported today?

UBL 2.1 Invoice and CreditNote documents and UN/CEFACT Cross Industry Invoice documents can be viewed. UBL invoices can be validated against the OASIS UBL 2.1 XML Schema and the EN 16931 business rules. Factur-X and ZUGFeRD PDFs can be inspected — container, attachments, XMP metadata and declared profile — and the CII invoice embedded in them validated. French UBL and CII documents, and the supported Factur-X profiles, can be validated against the pinned France_RFE 1.4.0.04 rule packages. Despatch advices and receipt advices are modelled in the architecture and recognised, but not yet readable as structured documents.

Can I use this for French e-invoicing?

Yes. The France e-invoice validator runs the official FNFE-MPE France_RFE rule packages, release 1.4.0.04, pinned to an immutable commit and checksummed — the EN 16931 and EXTENDED-CTC-FR profiles for UBL and CII, and the Factur-X profiles the release supplies rules for. Every finding carries the rule identifier the artefact itself emitted; nothing is reimplemented. It is an independent tool, not an official or approved validator, and a clean result is not a compliance guarantee: transmission, lifecycle statuses, e-reporting and retention are not observable in a file. PDF/A-3 container conformance is not checked either, and every result says so.