xingen
REST API · KoSIT · XRechnung 3.0.2 · Peppol BIS 3.0

The API layer between
ERP and compliance.

POST an invoice. Get back structured validation results with rule IDs, field paths, and fix suggestions — for XRechnung, ZUGFeRD, EN16931, and Peppol BIS 3.0. No portal, no manual process.

AI extraction from PDF invoices
Hosting & AI inference in the EU
< 200ms
p99 API latency
99.9%
uptime SLA
OpenAPI 3.1
spec included
POST /api/v1/invoices/validate

// Request

curl -X POST https://api.xingen.de/api/v1/invoices/validate \
  -H "Authorization: Bearer $API_KEY" \
  -F "profile=XRECHNUNG" \
  -F "file=@invoice.xml"

// Response 422 Unprocessable

{
  "valid":    false,
  "errors":   [{
    "code":       "BR-DE-14",
    "severity":   "ERROR",
    "field":      "BuyerReference",
    "message":    "Missing Leitweg-ID",
    "suggestion": "Provide BT-10"
  }]
}

Built for developers, not compliance departments

A clean REST API that fits into your ERP connector, CI pipeline, or billing system — not a portal you have to log into.

01

POST XML, get structured JSON back

Send your invoice XML to one endpoint. Get back rule IDs (BR-01, PEPPOL-EN16931-R003), the failing field path, and a fix suggestion — all in machine-readable JSON. Wire it straight into your pipeline or UI.

02

OpenAPI 3.1 spec + Postman collection

Full spec ships with every endpoint. Import into Postman, generate a typed SDK, or use auto-complete in your IDE. No guessing, no undocumented edge cases.

03

Every European compliance path, one key

XRechnung 3.0.2, ZUGFeRD 2.x, Factur-X, EN16931 core, Peppol BIS 3.0. Switch profiles with a single query parameter — the same integration covers DE, FR, IT, and cross-border.

04

Turn any plain PDF invoice into ZUGFeRD

Drop a plain, non-standardized invoice PDF — scanned or digital — into the UI, or POST it to /v1/invoices/extract. Claude AI extracts the fields, validates them, and hands back a ready-to-send ZUGFeRD/Factur-X PDF.

Validated against the official rulesets

No home-grown rule interpretations. Xingen validates against the same Schematron rulesets that the German KoSIT validator and the Peppol network enforce — pinned to the current official releases.

XRechnung 3.0.2

Schematron 2.5.0

Full CIUS validation for the German XRechnung standard: every BR-DE business rule from the official KoSIT XRechnung Schematron release 2.5.0 — Leitweg-ID (BT-10), payment details, VAT and Kleinunternehmer rules included.

xrechnung-3.0.2-schematron-2.5.0

Peppol BIS Billing 3.0

OpenPeppol ruleset

The complete OpenPeppol BIS Billing 3.0 Schematron ruleset (PEPPOL-EN16931-R rules) as published in the official peppol-bis-invoice-3 release — for invoices exchanged over the Peppol network.

peppol-bis-invoice-3

KoSIT validator compatible

EN 16931 core

Validation results align with the official KoSIT validator (Prüftool) and its XRechnung validator configuration. The full EN 16931 core rule set (BR, BR-CO, BR-DEC, VAT category rules) runs underneath every profile.

validator-configuration-xrechnung

Frequently asked questions

Does Xingen validate against the official KoSIT validator?

Yes. Xingen implements the rules of the official KoSIT validator configuration for XRechnung and cross-checks results against the KoSIT Prüftool, so a green result from the API matches what German public-sector platforms like ZRE and OZG-RE expect.

Which XRechnung Schematron version does Xingen support?

Xingen validates against XRechnung 3.0.2 using the official KoSIT Schematron release 2.5.0 (xrechnung-3.0.2-schematron-2.5.0), including all BR-DE business rules such as BR-DE-14 (buyer reference / Leitweg-ID) and BR-DE-16 (seller VAT identifier).

Is Peppol BIS Billing 3.0 validation supported?

Yes. Xingen runs the complete OpenPeppol peppol-bis-invoice-3 Schematron ruleset, covering the PEPPOL-EN16931-R validation rules required for sending invoices over the Peppol network.

What is the difference between EN 16931 and XRechnung validation?

EN 16931 is the European core invoice standard (BR, BR-CO and BR-DEC rules). XRechnung is the German CIUS on top of it, adding national BR-DE rules like the mandatory Leitweg-ID. Xingen validates both layers in a single API call — select the profile with one parameter.

Can I convert a plain PDF invoice into ZUGFeRD?

Yes. Upload a plain, non-standardized invoice PDF in the dashboard, or POST it to /v1/invoices/extract. Xingen uses Claude AI to extract the invoice fields — including from scanned/image-based PDFs — validates them, and produces a downloadable ZUGFeRD/Factur-X hybrid PDF. Available via both the web UI and the API.

Simple, transparent pricing

Start free. Upgrade to Pro at no cost.

Free

€0 up to 500 calls/mo
  • 500 API calls / month
  • EN16931 validation
  • XRechnung & ZUGFeRD export
  • API key management (live + sandbox)
  • OpenAPI spec access
  • Community support
Get started free
Free Upgrade

Pro

€0 under fair use
  • High-volume API calls (fair use applies)
  • Heavy usage may qualify for custom pricing
  • All validation profiles (XRechnung, Factur-X, Peppol Italy CIUS)
  • All formats + conversions
  • Priority support
Get Started

Enterprise

Custom
  • Dedicated integration support
  • Custom ERP / SAP connectors
  • On-premise deployment option
  • Volume pricing
  • Named account manager
Talk to us