What files can the detector inspect?

The detector inspects XML invoice files directly and scans PDF invoices for readable embedded XML markers.

Does the detector guarantee compliance?

No. It identifies likely file families and markers, but it does not certify legal, tax, or network compliance.

E-Invoice Format Detector

Identify the likely invoice family before you spend time opening or extracting the file.

This detector is deterministic and conservative. If the file does not clearly identify itself, the tool says so instead of inventing a standard.

Waiting for a file.

Upload an invoice file to see the detected family, confidence, and markers.

How to use this page

Upload the file first, then read the detected family and confidence together. A high-confidence result usually means the XML structure or invoice markers are explicit. A low-confidence result means the file may still be invoice-related, but the standard is not clearly declared.

What this output tells you

The detector reports the likely invoice family, the root or namespace markers that support that decision, and a short explanation of what the result means in practice.

That gives users something more useful than a label alone: they can tell whether to open the file in the viewer, try the extractor, or escalate to a finance or ERP workflow.

What to do next after detection

If the result points to UBL or another structured XML family, the next step is usually to open the file in the viewer and confirm the invoice number, supplier, buyer, totals, and line items.

If the file is a PDF and the result suggests hybrid invoice markers, the next step is to use the extractor and confirm whether an XML payload is actually present.

Typical use cases

Use this page when a supplier sends an unfamiliar invoice file, when an ERP export needs a quick first-pass identification, or when a finance handoff includes XML that should be classified before review.

What to look for

Use the detector when you receive an invoice file and need to know whether it is plain XML, a hybrid Factur-X or ZUGFeRD PDF, or something that does not match a standard invoice family.

For live lookup or legal validation, use the official registry or your accounting process. This tool only inspects the file you upload.

Limitations

PDF inspection depends on readable embedded markers. If a PDF stores the payload in a compressed or protected form, the detector may correctly report that it cannot confirm the standard.

Quick answers

Can this detect every invoice standard? No. It currently focuses on the families that matter most for this cluster: UBL, CII, Factur-X, and ZUGFeRD style markers.

What should I do after detection? Use the viewer if the file is structured XML, or use the extractor if the invoice is a hybrid PDF that should contain XML.

Why start here instead of opening the file directly? Because identification first reduces wasted time and helps users choose the correct next tool in the workflow.

Open the UBL viewer · Use the XML extractor · Compare invoice formats