Issue
You build the invoice as usual: Norman emits a ZUGFeRD PDF/A-3 with embedded EN 16931 XML in the right profile (e.g. EN 16931 or EXTENDED) and fills mandatory fields, VAT logic, and payment data automatically.
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 ZUGFeRD invoices as PDF/A-3 with embedded EN 16931 XML, in the right profile per buyer. Incoming ZUGFeRD invoices are recognised automatically, posted, and archived under GoBD. That covers the German B2B e-invoicing mandate for receiving from 2025 and sending from 2027 or 2028.
Invoices leave Norman as ZUGFeRD PDF/A-3 with embedded EN 16931 XML, incoming ZUGFeRD invoices are recognised automatically: with posting, input VAT, and audit-proof archiving.
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.
ZUGFeRD emerges from the live invoicing process, with no separate PDF editor or XML converter.
You build the invoice as usual: Norman emits a ZUGFeRD PDF/A-3 with embedded EN 16931 XML in the right profile (e.g. EN 16931 or EXTENDED) and fills mandatory fields, VAT logic, and payment data automatically.
The ZUGFeRD file goes by email or download to B2B buyers: one file with a human-readable PDF layout and structured data, compatible with Factur-X and the German B2B e-invoicing mandate from 2025/2027/2028.
Incoming ZUGFeRD invoices are recognised automatically: Norman reads amounts, VAT rates, and due dates from the embedded XML, books them into input VAT, and archives the original PDF/A-3 in an audit-proof way.
Norman replaces the double upkeep of PDF and XML, ZUGFeRD profile guesswork, and after-the-fact PDF/A-3 conversion with one continuous workflow.
across two tools with drift between layout and data
between MINIMUM, BASIC, EN 16931, and EXTENDED
patched together from regular PDFs after the fact
ZUGFeRD creation, profile selection, sending, and receiving run in one system instead of bouncing between a PDF editor, an XML converter, and an inbox.
| 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 |
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 freeZUGFeRD (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.
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.
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.
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.