Urgent.News

What's breaking now, across hundreds of outlets.

Tech

German e-invoicing for developers: XRechnung and ZUGFeRD via REST API and MCP

From 2027, many German businesses have to send structured e-invoices to other businesses, and from 2028 almost all of them. Receiving them has been mandatory since 1 January 2025. If you build software that creates or processes invoices for German customers, this is now your problem too. This post covers what counts as an e-invoice, the two formats you will meet, how to validate them, and how we…

From 2027, German businesses must begin sending structured e-invoices to other businesses, with almost all having to do so by 2028. Receiving e-invoices has been mandatory since January 1, 2025. This article covers what constitutes an e-invoice, the two formats businesses will encounter (XRechnung and ZUGFeRD), how to validate them, and how to generate both formats from a single invoice object using the developers' API.

Key dates:

- January 1, 2025: All German businesses must be able to receive e-invoices.

- January 1, 2027: Businesses with prior-year revenue of €800,000 must send domestic B2B e-invoices.

- January 1, 2028: All other businesses must send domestic B2B e-invoices.

An e-invoice is a structured, machine-readable format that complies with the European standard EN 16931. While PDFs are not e-invoices, other agreed formats like EDI are allowed if the data can be extracted in a compatible way. Two main formats businesses will encounter are:

- XRechnung: pure XML (UBL or CII syntax)

- ZUGFeRD (Factur-X in France): a PDF/A-3 with the XML embedded

To validate e-invoices, two open validators are available:

- KoSIT validator for XRechnung

- Mustang (open-source Java library and CLI) for ZUGFeRD/Factur-X

Generating both formats from one invoice object:

1. Create a draft invoice with the desired recipient information, e-invoice formats, service date, payment term, and line items.

2. Finalize the draft invoice, which checks mandatory invoice fields required by §14 UStG. If something is missing, a validation_failed error is returned, and the invoice is immutable.

3. Fetch the XRechnung format using the invoice ID. This returns the XRechnung 3.0.2 (CII) format. The JSON wrapper will include the validation results and warnings, such as missing seller contact or buyer email address.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

Advice for the next 100 Rust GUIs

  • Rust GUI landscape has expanded with two dozen toolkits announced
  • Performance issues persist in cross-platform GUI applications
  • GPUI framework enables high-performance Rust UI in real-world apps

Customer Domain Support in Go: Why I Chose Apex Record Ownership

Retries belong behind a reconciliation check. For property managers publishing customer domains and mail authentication records, I would choose a documented apex A record and a www CNAME, accepting…

  • Apex A records and www CNAMEs recommended for customer domain support
  • Separate explanations for portal and mail readiness during onboarding
  • Capacity planning considers affected zones and retry budget

Is This Height Comparison Up to Scale? How to Draw One Correctly in JavaScript and SVG

"I've always wondered what a height different between a 4'10 person and a 5'7 person would look like … I found this image but idk if it's up to scale or not." That question, posted to…

  • Figures' feet should be on the same horizontal line (single ground line)
  • Scale must start at zero, consistent pixels per centimeter throughout
  • Incorrect scaling introduces bias, distorts visual representation

ILLA Builder's 92 Fingerprints Mark a Low-Code Control Plane With Data Connections

ILLA Builder's 92 Fingerprints Mark a Low-Code Control Plane With Data Connections ILLA Builder is designed to assemble internal tools from visual components, data sources, and actions.

  • ILLA Builder identified via 92 distinct fingerprints
  • Control plane connects to databases, APIs, MongoDB, Redis, Hugging Face
  • November 22, 2026: ZoomEye SDK finds 92 app name matches, 109 body content matches

More from Saturday 21 November →