Validate e-Factura XML

Instantly check whether an electronic invoice XML complies with the UBL 2.1 structure and the Romanian CIUS-RO customisation. Paste the content, upload a file or drag it into the page — validation runs in your browser and the file is never sent anywhere. You get immediately: valid/invalid status, structural errors (with each element's path), warnings and extracted data — number, date, supplier, customer, total, currency. Validation covers the root (Invoice/CreditNote), UBL namespace, cbc:CustomizationID (CIUS-RO marker), cbc:ID, cbc:IssueDate, document type code, currency, accounting parties and the payable amount. For full XSD + Schematron validation the official ANAF validator in SPV remains the authoritative tool.

Frequently asked questions

How do I validate an e-Factura XML?

Paste the XML content, upload a .xml file or drag it into the page. The checker immediately confirms the UBL 2.1 + CIUS-RO structure and extracts the number, date, supplier, customer and payable amount.

What is CIUS-RO?

The Romanian customisation of the European EN 16931 standard for electronic invoices. The cbc:CustomizationID field always contains the CIUS-RO marker followed by the version (e.g. CIUS-RO:1.0.1).

Why is my XML invoice invalid for ANAF?

Most common causes: incorrect UBL namespace, missing cbc:CustomizationID with the CIUS-RO marker, or absent mandatory fields (cbc:ID, cbc:IssueDate, document type code, currency, parties, payable amount). The checker lists exactly what is missing and where.

Is this equivalent to the official ANAF validator?

No. This is a quick structural check for UBL 2.1 + CIUS-RO. The official ANAF system additionally applies Schematron rules (VAT arithmetic, code lists). Use this as a pre-check before uploading to SPV.

Is the invoice data stored or sent anywhere?

No. Validation runs 100% in the browser. The XML is not sent to any server and is not saved — it works offline too.