Issue
You build the invoice as usual: Norman emits an EN 16931-compliant XRechnung XML in parallel, including Leitweg-ID, mandatory fields, and VAT logic, without you touching XML.
We use cookies to analyze how our site is used. You can accept or reject these. Necessary cookies are always on. Privacy Policy.
Norman generates EN 16931-compliant XRechnung files with Leitweg-ID, validates them against the KoSIT rules, and sends them to German public-sector buyers. Incoming XRechnungen from B2B clients are detected automatically, posted, and archived in the original, ready for the German B2B e-invoicing mandate phasing in from 2025, 2027, and 2028.
Invoices leave Norman as valid EN 16931 XML, go out with a Leitweg-ID to federal, state, or municipal bodies, and come back as XRechnung in the same system: with posting, input VAT, and an audit trail.
Norman continuously assigns bank movements to the right accounts and suggests matching SKR03/04 postings.
Forward receipts via app or email. Norman extracts the data and matches them with transactions.
All expenses broken down by category, automatically updated, and available at any time.
Revenue, expenses, and open items in one dashboard that updates with every booking.
Norman identifies savings opportunities, flags unusual bookings, and gives you actionable recommendations.
The XRechnung workflow sits inside the live invoicing process, not in a separate compliance project.
You build the invoice as usual: Norman emits an EN 16931-compliant XRechnung XML in parallel, including Leitweg-ID, mandatory fields, and VAT logic, without you touching XML.
The XRechnung goes by email, download, or via existing intake portals (ZRE, OZG-RE, state portals) to the public-sector buyer, or directly to B2B clients who from 2025 must accept structured e-invoices.
Incoming XRechnungen are recognised automatically: Norman reads amounts, VAT rates, and due dates, books them into input VAT, and archives the original XML in line with GoBD.
Norman replaces manual XML tinkering, Leitweg-ID hunts, and PDF inboxes for incoming e-invoices with one running XRechnung workflow.
in foreign tools or a text editor
across emails and order paperwork
for incoming e-invoices from 2025
XRechnung creation, validation, sending, and receiving run in one system instead of bouncing between Word, an online converter, and a PDF inbox.
| 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 |
Start free and unlock tax, team, and automation features when you need them.
Free
Invoicing and bookkeeping.
/month (excl. VAT)
Pro
Reports, insights, and advisor tools.
/month (excl. VAT)
Max
Tax filings and team access included.
/month (excl. VAT)
Start for free and bring invoices, receipts, bookkeeping, and taxes into one workflow.
Start for freeXRechnung 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, with 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.
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.
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.
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.