Question 1

What is XRechnung and how does it differ from ZUGFeRD?

Accepted Answer

XRechnung is the German XML format for structured e-invoices based on the European EN 16931 standard, maintained by KoSIT (the German coordination body for IT standards in public administration). It has been mandatory for invoices to federal public-sector buyers since November 2020 and carries the invoice data as pure XML — no PDF. ZUGFeRD, by contrast, is a hybrid format: a PDF/A-3 file with embedded XML. Norman generates both variants under EN 16931; XRechnung is the default when a public-sector buyer asks for it.

Question 2

As a private business, do I need an XRechnung solution from 2025?

Accepted Answer

Receiving: yes. From 1 January 2025, every business based in Germany must be able to receive B2B invoices in a structured format (XRechnung, ZUGFeRD ≥2.0.1) — a PDF is no longer enough for incoming invoices. Sending: the obligation to send structured B2B e-invoices phases in — from 1 January 2027 for companies with annual revenue above €800,000, and from 1 January 2028 for the rest. Norman already supports both receiving and sending today, so you can switch over in time.

Question 3

How do I send an XRechnung to a federal, state, or municipal buyer?

Accepted Answer

The invoice needs a Leitweg-ID, which the public-sector buyer assigns to you — it steers delivery. Norman emits the XRechnung XML, validates it against the KoSIT rules, and prepares it for sending: by email, download, via the ZRE (federal central intake platform), OZG-RE, or the relevant state portal. The XML format and mandatory fields stay identical — only the transport channel changes per buyer.

Question 4

How does Norman handle incoming XRechnungen from B2B clients?

Accepted Answer

Incoming XRechnungen arrive in Norman by email forwarding, upload, or API and are recognised automatically: amounts, VAT rates, due dates, and supplier data are read straight from the XML, posted into input VAT, and matched to the payment. The original XML is archived under GoBD with a timestamp, so it can be produced unchanged years later.

	Norman	Word + XML converter + inbox
Create XRechnung	Generated from the live invoice as EN 16931 XML with Leitweg-ID	Copy a Word invoice into an online XML converter
Validation	KoSIT rules checked before sending	Errors only surface at the buyer
Delivery to federal / state / city	Email, download, or intake portals (ZRE, OZG-RE, state)	A separate form per portal, every time by hand
Incoming XRechnung	Auto-read, posted, original archived	Open XML from the inbox and re-type the values

Create and receive XRechnung — no XML editor, no inbox patchwork

Built for anyone who has to issue, validate, and archive XRechnung

Automated bank categorization (SKR03/04)

Smart receipt matching

Real-time expense tracking

Financial overview at a glance

AI-powered insights

How XRechnung runs in Norman — from order to posting

Issue

Send

Receive and post

What Norman removes from day-to-day XRechnung work

Norman instead of a Word invoice plus a separate XML converter

Plans that grow with your workflow

Start XRechnung with Norman

FAQ