Skip to main content

E-invoicing API

E‑invoices by API, validated before they go out.

The invoice you already produce becomes the XRechnung or the ZUGFeRD file: to EN 16931, checked against the KoSIT rules, with one finding per violated rule. No second data path.

€0/month + 2.6% pay-as-you-go · fixed plans from €199/month · cancel monthly

What a PDF forgives fails here.

A structured invoice is validated. Data a PDF lets through shows up in the check. You can fix it on the customer before you finalize the invoice. Afterwards the only option is to issue it again.

  • VAT ID missing or malformed Result of the check: Validation fails
  • Billing address incomplete Result of the check: Validation fails
  • Buyer reference missing although the customer requires one Result of the check: BR-DE-15, document quarantined

Each customer carries a setting for whether an e-invoice is generated. Everyone else stays on the PDF. Documentation: e-invoicing ↗

The invoice that passes validation.

XRechnung and ZUGFeRD come out of the same invoice you already produce. No second data path, no export to Excel, no library you have to keep aligned with the KoSIT rules yourself.

From call to valid XML

Generate the document: pick a profile, reference the invoice.

POST /v1/e-invoicing/documents{ "invoice_id": "ad796aee-…",  "profile": "XRECHNUNG_3_0_UBL",  "jurisdiction": "DE" }→ 201 · "quarantined": true · 1 finding

Fetch the raw XML: exactly what the recipient receives.

GET /v1/e-invoicing/documents/{id}/raw→ 200 · application/xml · sha256 ae717a6e…

Read the findings: every violated rule with its id and XPath, not "invalid".

GET /v1/e-invoicing/documents/{id}/findings→ [ { "rule_id": "BR-DE-15", "severity": "ERROR", … } ]

What gets validated

Own rule engine

EN 16931, KoSIT BR-DE and PEPPOL BIS run as rules inside the service. No external schematron service that can be down.

The rules KoSIT actually checks

The BR-DE rules are transcribed from the KoSIT schematron, assertion by assertion. BR-DE-15 requires a buyer reference (BT-10) and leaves its value open: a Leitweg-ID and a purchase-order number both pass. A finding checked that way looks like this:

BR-DE-15 · ERROR Quarantined Sample data
/Invoice/BuyerReference

Buyer reference (BT-10) is missing. Add it on the draft with PATCH /v1/invoices/{id} "buyer_reference", then generate again:

0 findings · deliverable

Quarantine, not a silent failure

Findings are stored per document. A document that breaks the rules is quarantined instead of quietly going out to a public authority.

19 profiles in the catalogue

  • XRECHNUNG_3_0_UBL
  • XRECHNUNG_3_0_CII
  • EN16931_UBL_2_1
  • EN16931_CII_D16B
  • PEPPOL_BIS_BILLING_3_UBL
  • ZUGFERD_2_COMFORT
  • FACTURX_EN16931
  • ZUGFERD_2_XRECHNUNG
  • +11

Marked green: XML-only profiles the service produces itself. The eleven hybrid PDF/A-3 profiles (Factur-X, ZUGFeRD) also need a configured Mustang server.

Artifacts are archived with bytes and a hash chain, so the GoBD question "is this still the same invoice" has an answer.

What Kontier does not do on its own.

  • It sends nothing without a channel

    By default Kontier generates and archives the validated document and sends it nowhere. You deliver it through the route the customer names. If Kontier should submit it, configure a channel for your country, for example Peppol. A new channel starts in test mode.

  • Hybrid profiles need a server

    The eleven PDF/A-3 profiles (Factur-X, ZUGFeRD) require a configured Mustang server. XML profiles such as XRechnung are produced by the service itself.

Your first XRechnung, before the deadline.

Set up your plan, issue an invoice and download the XRechnung. Your payment provider stays connected.

€0/month + 2.6%Pay-as-you-go, net plus VAT

  • €0 base fee (+ 2.6% on revenue)
  • Fixed plans from €199/month
  • No setup fee
  • Cancel monthly

Book a demo

A technical demo: 15 minutes with an engineer on your pricing model and tax setup.

How we handle your details: privacy policy.

Prefer email? contact@frontieralgorithmics.com

Message Kontier

Write to us right here. We reply by email, usually within one business day.

How we handle your details: privacy policy.

Step 1 of 3

What do you bill with today?

Prefer email? contact@frontieralgorithmics.com