curatedapi

Check e-invoices before your customers send them

An API that checks invoices against EN 16931, Peppol BIS, XRechnung and Factur-X with the official rules, and says which rule failed and why. For invoicing apps, ERP plugins and online shops that bill businesses in the EU.

Free plan, no card needed. Test keys are never billed.

POST /v1/validate/einvoice/xrechnungRequest
jq -Rs '{xml: .}' xrechnung-01.01a-invoice-ubl.xml |
  curl https://api.curatedapi.com/v1/validate/einvoice/xrechnung \
    -H "Authorization: Bearer $CURATEDAPI_KEY" \
    -H "Content-Type: application/json" \
    --data-binary @-
200 OKResponse, shortened
{
  "validator": "einvoice/xrechnung@1",
  "result": {
    "valid": true,
    "scenario": "EN16931 XRechnung (UBL Invoice)",
    "document_type": "UBL Invoice",
    "specification_id": "urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0",
    "errors": 0,
    "warnings": 0,
    "notices": 1,
    "error_rules": [],
    "checks": [
      {
        "check": "XML syntax",
        "passed": true
      },
      {
        "check": "XML Schema for UBL 2.1 Invoice",
        "passed": true
      },
      "… 2 more"
    ],
    "messages": [
      {
        "rule": "BR-DE-TMP-32",
        "level": "information",
        "message": "[BR-DE-TMP-32] Eine Rechnung sollte zur Angabe des Liefer-/Leistungsdatums entweder BT-72 \"Actual delivery date\", BG-14 \"Invoicing period\" oder in jeder Rechnungsposition BG-26 \"Invoice line period\" enthalten.",
        "check": "Schematron rules for Invoice - CIUS XRechnung (UBL)",
        "location": "/Q{urn:oasis:names:specification:ubl:schema:xsd:Invoice-2}Invoice[1]"
      }
    ],
    "messages_truncated": false
  }
}
An official sample (xrechnung-01.01a-invoice-ubl.xml)

The problem

Belgium has required B2B e-invoices since January 2026. In France, every business has had to accept them since September 2026, and large and mid-sized companies must also send them; smaller ones start sending in September 2027. Germany has required businesses to accept them since 2025. From January 2027, companies with more than €800,000 turnover in the previous year must send them, and all others from January 2028. An invoice that breaks the rules can be rejected by the buyer's system, and a rejected invoice is an unpaid one.

The rules are long and change about twice a year. Keeping a validator up to date is work nobody on your team asked for. We run the rule owners' own files, pinned to a published release, and update them when the rules change.

What you get

  • Every finding with the rule's ID, its level and the rule owner's own message
  • EN 16931 (UBL and CII), Peppol BIS Billing 3.0, XRechnung and Factur-X / ZUGFeRD
  • Checked before every release with 1,818 official unit tests and the official sample invoices
  • Invoices are not stored or logged
  • The same key works for the REST API and the MCP server

What a month costs

Each of these invoice checks counts as 5 calls. The cheapest plan for each volume, in US dollars (euro plans cost the same number of euros), before any VAT or sales tax your country charges. A spend cap stops calls at the amount you choose.

Invoice checks a monthCallsPlanPer month
2001,000Free$0
10,00050,000Starter$9.00
100,000500,000Pro$29.00
400,0002,000,000Business$99.00

All plans are on the pricing section of the home page.

Endpoints

Each one is a POST endpoint and an MCP tool. Its page shows the inputs, an example and the sources it is checked against.

Missing something you need?

Tell us which format or country rules you need checked, and we will tell you whether and when we can add them. Write to hello@curatedapi.com.