What Is XRechnung and What Is ZUGFeRD? A Quick Overview
XRechnung vs ZUGFeRD starts with understanding what each format actually is. XRechnung is Germany’s national CIUS (Core Invoice Usage Specification) a German-specific extension of the EN 16931 European standard. It is maintained by KoSIT (Koordinierungsstelle für IT-Standards) under the mandate of the IT Planning Council. XRechnung exists in two syntaxes: UBL 2.1 (Universal Business Language) and UN/CEFACT CII (Cross Industry Invoice). Both syntaxes encode the same invoice data; the choice between them is usually determined by your ERP vendor’s implementation. XRechnung is the mandatory format for invoicing German federal and state government bodies, and it is the default format for PEPPOL transmission in Germany.
ZUGFeRD format explained: ZUGFeRD stands for Zentraler User Guide des Forums elektronische Rechnung Deutschland. It is a hybrid format maintained by the Forum FeRD and is based on the Factur-X standard developed jointly with France. A ZUGFeRD invoice is a PDF/A-3 file an archival-grade PDF that carries an XML file as an embedded attachment. The XML follows the UN/CEFACT CII syntax (same as one of XRechnung’s syntaxes). ZUGFeRD comes in six profiles of increasing data richness: Minimum (below EN 16931), Basic WL (below EN 16931), Basic, EN 16931, Extended, and XRechnung. Only the EN 16931 and Extended profiles and the XRechnung profile, which is identical to XRechnung in the XML component qualify as compliant E-Rechnungen under German law.
Key Takeaways
- XRechnung vs ZUGFeRD difference: XRechnung is pure XML with no visual component, while ZUGFeRD is a hybrid PDF with embedded XML. The PDF is designed for people to read, and the XML supports machine processing.
- Best e-invoice format Germany for B2G invoicing: XRechnung is widely used for government invoicing. Federal portals such as ZRE and many state portals using OZG-RE have specific format requirements that businesses should check before submitting invoices.
- ZUGFeRD format explained: ZUGFeRD provides multiple profiles. The EN 16931 profile and Extended profile can support compliant structured e-invoicing when applicable requirements are met. Minimum and Basic WL do not qualify as EN 16931-compliant E-Rechnungen.
- XRechnung format for businesses: Businesses issuing high invoice volumes can benefit from automated XML generation, validation and direct ingestion into accounts payable systems, reducing manual document handling.
- Germany e-invoice format comparison: XRechnung and compliant ZUGFeRD formats support structured invoice data under EN 16931. Choose the format based on workflow requirements, human readability, system compatibility and whether customers are B2G authorities or B2B businesses.
XRechnung vs ZUGFeRD: Key Differences in Structure and Readability
XRechnung vs ZUGFeRD difference in structure is fundamental. An XRechnung file is a standalone XML document, typically 3–15 KB for a standard invoice. It contains nothing that can be displayed by a standard PDF viewer or email client only an XML parser or a dedicated e-invoice viewer can render it meaningfully. A ZUGFeRD file is a PDF document that ranges from 50 KB to several hundred KB depending on logos and attachments. It opens in any standard PDF viewer, displays exactly like a printed invoice, and contains the embedded XML as an invisible attachment. Open the PDF in Adobe Acrobat, click the paperclip icon, and the factur-x.xml file is there. This structural difference has significant downstream effects on customer acceptance, AP processing, and dispute resolution.
The Germany e-invoice format comparison on readability is stark. An XRechnung format for businesses is entirely machine-dependent: human review requires either a dedicated XRechnung visualiser (like the Mustermann renderer from KoSIT, or commercial tools like E-Rechnung Viewer) or an ERP module that renders the XML into a readable layout. A ZUGFeRD invoice requires nothing any PDF viewer shows it. This readability gap matters most in three situations: sending invoices to customers without sophisticated AP automation (who need to read the invoice before approving payment); during dispute resolution (where humans need to review invoice details quickly); and in archive audits (where a Betriebsprüfer may want to review invoice content without specialised tools). ZUGFeRD format explained in practice: it reduces the human interface overhead of structured e-invoicing to near zero.
| Feature | XRechnung | ZUGFeRD (EN 16931 profile) | Impact on Businesses |
|---|---|---|---|
| File format | Pure XML (.xml) | Hybrid PDF with embedded XML (.pdf) | ZUGFeRD is readable by any PDF viewer; XRechnung requires XML viewer |
| File size | 3–15 KB typical | 50–300 KB typical (PDF adds size) | Negligible for most B2B volumes; relevant for very high-volume issuers |
| Human readability | Not human-readable without viewer tool | Fully human-readable as PDF | ZUGFeRD reduces customer acceptance friction; XRechnung requires viewer software |
| EN 16931 compliance | Yes — XRechnung CIUS (German extension) | Yes — at EN 16931 or Extended profile | Both satisfy §14 UStG B2B mandate; identical mandatory fields |
| B2G (government) use | Mandatory for federal B2G via ZRE/PEPPOL | Accepted in some state portals; not universally required | B2G suppliers should use XRechnung; pure B2B can use either |
| Transmission method | Email (XML attachment), PEPPOL, ZRE/OZG-RE portal | Email (PDF attachment), PEPPOL, portal (where accepted) | Email delivery is common for both; PEPPOL preferred for high volume |
| Software support | All major ERP systems; KoSIT open-source tools; PEPPOL access points | All major accounting software; simpler implementation than XRechnung for SMEs | ZUGFeRD has broader SME software support; XRechnung in more ERP systems |
Which E-Invoice Format Is Accepted for German B2B and B2G Invoicing?
XRechnung vs ZUGFeRD acceptance differs significantly between B2B and B2G channels. For B2B transactions, §14 UStG treats both formats equally a ZUGFeRD invoice at EN 16931 profile and an XRechnung are both valid E-Rechnungen for a domestic B2B supply. The buyer cannot mandate one over the other under the current legal framework; both are compliant. In practice, large corporate buyers with AP automation often prefer XRechnung or PEPPOL BIS because pure XML is cleaner to ingest programmatically than a PDF with embedded XML. But neither the law nor the buyer can refuse a compliant E-Rechnung in the other format.
Best e-invoice format Germany for government invoicing is unambiguously XRechnung. Since 2020, the Federal E-Invoicing Ordinance (E-Rechnungsverordnung) has required XRechnung for invoices to federal government bodies, transmitted via ZRE (Zentrale Rechnungseingangsplattform des Bundes) or PEPPOL. Most German state governments followed with similar portals (OZG-RE portals) accepting XRechnung. ZUGFeRD is not accepted on ZRE, and acceptance on state OZG-RE portals varies. If you invoice any public authority, using XRechnung from the start eliminates format risk in the B2G channel. Businesses with a mixed customer base some government, some B2B typically implement XRechnung as the base format and add ZUGFeRD generation for customers who prefer the PDF experience.
Pros and Cons of XRechnung and ZUGFeRD for Businesses
XRechnung vs ZUGFeRD has different trade-offs depending on your business profile. XRechnung’s main advantage is full process automation on both sides: a sender’s ERP generates pure XML; a receiver’s AP system ingests pure XML with no PDF-parsing overhead. For high-volume issuers above 1,000 invoices per month, this machine-to-machine efficiency reduces costs and error rates. XRechnung format for businesses with existing PEPPOL connections is particularly seamless XRechnung over PEPPOL is a single integration covering both format and transmission. The main disadvantage of XRechnung is the human interface gap: any process that requires a human to review an invoice approvals, dispute resolution, customer service requires a separate visualisation step that adds friction.
ZUGFeRD format explained from a practical advantages perspective: the embedded PDF eliminates the human interface gap entirely. Customers receive an invoice that looks identical to their current PDF invoice; the only difference is that it now carries a machine-readable XML inside. Accounts payable teams can continue reviewing the PDF while AP automation picks up the XML. This backward compatibility makes ZUGFeRD the best e-invoice format Germany for businesses serving a diverse customer base that includes both automated AP systems and smaller buyers who still review invoices manually. The main limitation of ZUGFeRD is the larger file size (though usually negligible) and the B2G channel restriction federal government portals do not accept ZUGFeRD, so B2G suppliers must maintain XRechnung capability alongside ZUGFeRD.
How to Choose Between XRechnung and ZUGFeRD for Your Business
XRechnung vs ZUGFeRD decision follows from answering four questions about your business. First: do you invoice German public authorities? If yes, implement XRechnung there is no choice for the B2G channel. Second: do your largest B2B customers require a specific format? If a major customer specifies XRechnung or ZUGFeRD in their supplier portal requirements, that customer’s preference determines your priority. Third: what format does your current invoicing software generate natively? Most German SME accounting software (DATEV, Lexware, sevDesk, Fastbill) supports ZUGFeRD natively; XRechnung may require an additional module. Starting with the format your software already supports reduces implementation risk. Fourth: do you have high-volume, fully automated AP customers? If most of your invoices go to corporate buyers with EDI or PEPPOL-connected AP systems, XRechnung’s pure XML structure offers downstream automation benefits.
The Germany e-invoice format comparison for most SMEs resolves to ZUGFeRD. For a business invoicing fewer than 500 customers per month, with a mix of corporate and mid-market buyers, ZUGFeRD at EN 16931 profile is the path of least resistance: minimal software change, no visualiser required, backwards-compatible PDF experience for all customers. For larger businesses with established PEPPOL connections, high invoice volumes, or significant B2G revenue, XRechnung is the stronger long-term foundation. The good news is that the two formats are not mutually exclusive many larger businesses generate both XRechnung and ZUGFeRD from the same ERP invoice record, sending whichever format each customer requires. Best e-invoice format Germany is therefore not a single answer; it is the combination that serves your specific customer mix.
XRechnung and ZUGFeRD Examples: Sample Files and Software Support
XRechnung vs ZUGFeRD examples are freely available from official sources. KoSIT publishes reference XRechnung sample files both UBL and CII syntax at xeinkauf.de, including annotated examples that label each XML element with its EN 16931 Business Term identifier. These sample files are useful for verifying that your software’s output matches expected structure before going live. ZUGFeRD sample files are available from the FeRD website (ferd-net.de) in all profiles, including the EN 16931 profile. Downloading and opening these samples in Adobe Acrobat reveals the embedded XML structure; using a PDF extraction tool to pull the factur-x.xml and validating it against the ZUGFeRD schema confirms the XML component’s structure.
For Poland Advintek helps businesses prepare for KSeF e-Invoicing requirements with automated invoice generation, XML data validation, accounting and ERP system integration, and secure digital archiving. The platform supports streamlined invoice processing, accurate data exchange, and improved visibility across financial workflows, helping businesses simplify e-Invoicing operations and prepare for applicable Polish tax authority requirements.
| Software Category | Product | XRechnung Support | ZUGFeRD Support | Notes |
|---|---|---|---|---|
| ERP (large enterprise) | SAP S/4HANA | Yes — UBL and CII | Yes — EN 16931 and Extended | Standard from SAP S/4HANA 2021 FPS01; earlier versions need add-on |
| ERP (mid-market) | Microsoft Dynamics 365 | Yes — via certified add-on | Yes — via partner add-on | Several certified German ISV partners; check current marketplace |
| Accounting (SME) | DATEV Unternehmen Online | Yes — via Belegübertragung | Yes — EN 16931 profile | Standard update; no additional module purchase required from 2026 |
| Accounting (SME) | Lexware Office | Yes | Yes | Available as standard feature; verify profile on ZUGFeRD output |
| Cloud invoicing | sevDesk | Yes | Yes — EN 16931 profile | ZUGFeRD native; XRechnung available from Business tier |
| Cloud invoicing | Fastbill / Easybill | Yes | Yes | SME-focused; confirm EN 16931 profile on ZUGFeRD output |
| Validation tool | KoSIT validator (xeinkauf.de) | Yes — validates XRechnung XML | Yes — validates embedded XML from ZUGFeRD | Free online tool; also available as downloadable Java application |
Frequently Asked Questions
1. Can I send both XRechnung and ZUGFeRD to the same customer?
Technically yes, but commercially it creates confusion. Agree with each customer which format they prefer, and stick to it. Most B2B customers will specify a preferred format in their supplier onboarding requirements; follow that specification.
2. Is ZUGFeRD just a PDF with a sticker on it?
No a ZUGFeRD PDF is technically a PDF/A-3 file with a machine-readable XML file embedded as a file attachment. The XML is structured invoice data conforming to EN 16931; it is not metadata or a label. An accounts payable system that processes ZUGFeRD reads the XML, not the visual PDF.
3. XRechnung vs ZUGFeRD: which one does the German tax authority prefer?
The Finanzamt does not specify a preference for private B2B invoicing both satisfy §14 UStG. For government invoicing (Finanzamt as a buyer), XRechnung via ZRE or PEPPOL is required.
4. Does ZUGFeRD work with PEPPOL?
Yes, with conditions. ZUGFeRD invoices can be transmitted via PEPPOL if the receiving access point supports ZUGFeRD. However, PEPPOL’s standard format is PEPPOL BIS Billing 3.0, not ZUGFeRD. Check with your PEPPOL access point provider whether ZUGFeRD transmission is supported for your specific counterparties.
5. My customer rejected my ZUGFeRD invoice saying it is not an E-Rechnung what went wrong?
The most likely cause is that your ZUGFeRD invoice is at a profile below EN 16931 for example, Basic WL or Minimum. Check your software settings and confirm that the generated invoice uses the EN 16931 or Extended profile. Run the file through the KoSIT validator to confirm the profile.
Source by:
Image by Gemini
