Question 1

What is ZUGFeRD and how does it differ from XRechnung?

Accepted Answer

ZUGFeRD (Zentraler User Guide des Forums elektronische Rechnung Deutschland) is a hybrid e-invoice format: a PDF/A-3 file with embedded EN 16931 XML — maintained by FeRD under AWV. A single ZUGFeRD invoice is both a readable PDF and a structured data record in one file. XRechnung, by contrast, is pure XML without a PDF, mandatory for invoices to German federal public-sector buyers. For B2B recipients who want layout and structured data together, ZUGFeRD is often the more practical route.

Question 2

Which ZUGFeRD profiles exist, and which one fits my business?

Accepted Answer

ZUGFeRD 2.x ships with several profiles: MINIMUM (a few key figures, not EN 16931 compliant), BASIC WL (without line items), BASIC (short invoices with line items), EN 16931 (formerly COMFORT, fully aligned with the European norm), and EXTENDED (extra fields for sectors with complex order logic). EN 16931 is the default most B2B recipients and the German B2B mandate work with. Norman picks the right profile per invoice and ensures all EN 16931 mandatory fields are filled.

Question 3

Does ZUGFeRD satisfy the German B2B e-invoicing mandate from 2025?

Accepted Answer

Yes — as long as it's ZUGFeRD version 2.0.1 or newer in an EN 16931-compliant profile (e.g. EN 16931 or EXTENDED). From 1 January 2025, every business based in Germany must be able to receive B2B invoices in a structured format — XRechnung and ZUGFeRD ≥2.0.1 are the two recognised formats. Sending structured B2B invoices phases in: from 1 January 2027 for businesses above €800,000 annual revenue, and from 1 January 2028 for all remaining B2B issuers.

Question 4

How does Norman handle Factur-X and incoming ZUGFeRD invoices?

Accepted Answer

ZUGFeRD and the French Factur-X are technically the same hybrid format (PDF/A-3 with embedded EN 16931 XML). Norman recognises incoming ZUGFeRD and Factur-X invoices automatically, reads the structured values (amounts, VAT rates, due dates, supplier) from the embedded XML, posts them into input VAT, and matches the payment. The original PDF/A-3 is archived under GoBD with a timestamp — that covers the German B2B receiving mandate from 2025 and keeps the invoices auditable years later.

	Norman	PDF template + XML converter + inbox
Create ZUGFeRD	Generated from the live invoice as PDF/A-3 with embedded EN 16931 XML	Load the PDF into an external converter and manually attach the XML
Profile and validation	Norman picks the right ZUGFeRD profile and checks EN 16931 mandatory fields	You guess between MINIMUM, BASIC, EN 16931, and EXTENDED
Delivery to B2B buyers	One file by email or download — layout and data in a single PDF/A-3	PDF and XML separately, every buyer gets a different bundle
Incoming ZUGFeRD	Auto-read from the embedded XML, posted, original archived under GoBD	Only the PDF is read, values are re-typed by hand

Create and receive ZUGFeRD — one file, readable by humans and machines

Built for anyone who has to issue and receive ZUGFeRD invoices

Automated bank categorization (SKR03/04)

Smart receipt matching

Real-time expense tracking

Financial overview at a glance

AI-powered insights

How ZUGFeRD runs in Norman — from order to posting

Issue

Send

Receive and post

What Norman removes from day-to-day ZUGFeRD work

Norman instead of a PDF template plus a separate XML attachment

Plans that grow with your workflow

Start ZUGFeRD with Norman

FAQ