Checklist

E-Invoice 2027 — developer readiness

A practical list for product and engineering teams embedding invoices in Germany.

1. Receive path — Can you ingest supplier XRechnung (UBL/CII) into your domain model? See /v1/invoices/parse.
2. Issue path — Do you generate XRechnung 3.0 (UBL and/or CII) for B2G and the coming B2B mandate?
3. Authoritative validation — Do you run KoSIT (or an equivalent that maps to it), not only XSD?
4. Leitweg-ID / buyer reference — Public-sector BT-10 is the most common reject. See BR-DE-15.
5. Error UX — Can a developer fix a failed invoice without reading raw Schematron? Try the free validator.
6. Build vs buy — Library ownership vs API. Read OSS vs API.
7. Quotas & retries — Idempotent generate, free validate fair-use, no bill on failed docs.

Ready to wire it: get a free API key or open the playground.

Deutsche Fassung →