Validate XRechnung online
XRechnung 3.0 in UBL or CII, checked with KoSIT schematron 2.6.0 and EN 16931 1.3.17. Result in about a second.
10 free checks a day · €1 free with a key · then €0.02 per check
Processed on servers in Germany (Hetzner, Falkenstein). The uploaded file is checked in memory and not stored.
The verdict, profile, totals and every rule violation appear here.
PDF invoice → XRechnung or ZUGFeRD
A PDF, scan or photo of an invoice becomes a structured e-invoice in two steps: read the fields, then build and validate the XML.
Free in the playground: 10 checks a day per IP. With a key: €0.10 per document.
Step 1 sends the invoice text or image to a language model via OpenRouter. The uploaded file is not stored; the built e-invoice is kept 24 hours behind a signed link, then deleted.
The verdict, profile, totals and every rule violation appear here.
XRechnung checks
XRechnung is the German CIUS of EN 16931. It adds national rules on top of the European core: BR-DE-15 requires the buyer reference (BT-10, the Leitweg-ID for public buyers), BR-DE-2 to BR-DE-7 require a seller contact with name, phone and email, BR-DE-1 requires payment instructions.
For B2B the BMF accepts a placeholder such as “-” in the buyer reference, because a Leitweg-ID is only needed when invoicing a public authority (BMF FAQ, question 6).
Upload the XML or a PDF with the XRechnung attached. The validator detects the profile from CustomizationID and applies both rule sets.
Deadlines
What the law requires and when. Dates from the official sources linked under each country.
Germany
Formats: XRechnung and ZUGFeRD from 2.0.1, except the MINIMUM and BASIC WL profiles.
Source: BMF: FAQ on the mandatory e-invoice ↗Belgium
Peppol BIS is built on EN 16931: the core rules are checked here, Peppol-specific rules are not.
Source: FPS Finance: from when is e-invoicing mandatory ↗Poland
KSeF uses the national FA(3) schema, which this tool does not validate. It covers EN 16931 invoices exchanged with DE, BE and FR partners.
Source: Ministry of Finance: scope of mandatory KSeF ↗Price in plain numbers
A prepaid balance, no subscription. Charged only for a successful answer; errors are free.
A new key comes with €1 of free credit: 50 validations.
Credits never expire. No subscription.
Apple Pay, Google Pay or card on the monobank page. The key is created for you if you have none.
No key in this browser yet.
For developers
Same checks over REST and MCP. One header, JSON out.
curl https://api.finekot.com/v1/e-invoice \
-H "Authorization: Bearer fk_live_…" \
-F file=@invoice.xml
# → {"valid":false,"errors":2,"issues":[{"rule":"BR-DE-15",…}]}
# X-Cost: 0.02curl https://api.finekot.com/v1/e-invoice \
-H "Authorization: Bearer fk_live_…" \
-H "Content-Type: application/json" \
-d '{"op":"create","output":"pdf","invoice":{…}}'
# → Factur-X PDF url + validation report · X-Cost: 0.04claude mcp add --transport http finekot https://api.finekot.com/mcp --header "Authorization: Bearer fk_live_…"
Full reference: /llms.txt · /openapi.json · /.well-known/mcp.json