XML & E-invoice Validator (XSD, Peppol, XRechnung, Factur-X)

What does the XML & E-invoice Validator do?

It validates XML documents and e-invoices you give it by URL, the way the receiving system will check them: against the XSD, DTD or RelaxNG schema and, for e-invoices, the Schematron business rules (EN 16931, Peppol BIS, XRechnung, national CIUS). You get one row per document with the verdict, the number of errors and warnings, and each finding with its line number, rule id (such as BR-CO-16) and a link that explains how to fix it.

It runs on xmlvalid.com, a streaming validator built on libxml2 and SaxonJS that handles files up to 1 GB.

What can it validate?

• E-invoices: Peppol BIS Billing 3.0, EN 16931 (UBL and CII), XRechnung, ZUGFeRD and Factur-X (including the XML inside the PDF), France CTC 2026, FatturaPA with the SdI checks, KSeF FA(3), Croatian eRačun (HR CIUS), Romanian e-Factura (CIUS-RO), Spain (SPFE, VERI*FACTU), Peppol PINT for the UAE, Singapore, Japan, Australia and Malaysia.
• Other XML formats in the schema catalog: UBL 2.1, ISO 20022 payments (pain, pacs, camt), CFDI, NF-e, ISDOC, Finvoice, SAF-T, HL7 CDA, FHIR, SOAP, WSDL, SAML, Maven POM, sitemaps, Atom, SVG, XHTML, GPX, KML and more.
• Any well-formed XML for syntax errors, and its own DOCTYPE.
• .zip archives document by document, and EPUB books file by file.

With schema left at auto, an e-invoice is checked against the profile it declares (its specification identifier, BT-24), so a mix of Peppol, XRechnung and Factur-X invoices can go in one run.

How to use it

1. Add the URLs of your documents, or paste one XML document.
2. Leave Schema at auto, or pick a catalog name such as peppol-bis-3-invoice, xrechnung-3-cii or ubl-2.1-invoice.
3. Run it, and open the Results or Findings view of the dataset, or export it as JSON, CSV or Excel.

Turn on Make a shareable report link to get one HTML report for all documents, open for 30 days, in the run's OUTPUT: handy to send to whoever has to fix the invoices.

Output

{
  "source": "https://example.com/invoices/INV-1042.xml",
  "valid": false,
  "outcome": "invalid",
  "schema": "peppol-bis-3-invoice",
  "schemaName": "Peppol BIS Billing 3.0 Invoice",
  "errorsTotal": 1,
  "warningsTotal": 0,
  "firstError": "Line 139: [BR-CO-16] Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114).",
  "errors": [
    {
      "line": 139,
      "level": "error",
      "type": "schematron",
      "rule": "BR-CO-16",
      "message": "Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114).",
      "help": "https://xmlvalid.com/rules/BR-CO-16"
    }
  ],
  "warnings": [],
  "sizeBytes": 9227,
  "durationMs": 35,
  "validationId": "val_01m55d4m0rtw2n0szg5f3ybmas",
  "error": null
}

outcome is valid, warnings (valid, with warnings), invalid, schema (the schema could not be used), input (the document could not be read or downloaded), failed, or error when the request was refused (the error field says why).

How much does it cost?

You pay per document validated, as listed on the Pricing tab, plus a tiny fee per run. Documents that are refused before they are checked are not charged.

Already an xmlvalid user? Enter your own API key and the validations count towards your xmlvalid plan instead (Free: 100 a month; Pro: 10,000), with your saved schemas (my-12) available too. You then pay Apify only for the run.

Privacy

Documents are downloaded by xmlvalid's servers in the EU, validated and deleted as soon as the check finishes; results are kept for 24 hours. See Security and the DPA.

Other ways to validate

• In the browser, free, without uploading anything: xmlvalid.com/validate
• REST API, CLI and GitHub Action, MCP server for AI agents

Questions or a format you need: support@xmlvalid.com