Both formats can satisfy the German B2B e-invoicing mandate but they are built on very different ideas, and with ZUGFeRD, compliance depends on which profile you use. Understanding the difference helps you make a choice you won't have to revisit in 2028.
ZUGFeRD: the hybrid format
ZUGFeRD combines a human-readable PDF with an embedded XML file (CII) in a single document. Its popularity in Germany is easy to explain: the invoice still looks like an invoice. Anyone can open it, read it, print it, archive it.
But the hybrid nature comes with trade-offs. ZUGFeRD invoices are typically exchanged by e-mail with no delivery confirmation, no sender verification, and no guarantee the receiving system actually processes the embedded XML rather than the PDF. Two versions of the same invoice in one file also means two potential sources of truth.
There's a technical catch, too. The XML inside a ZUGFeRD invoice always uses the CII syntax while much of the e-invoicing ecosystem, including the Peppol network, runs on UBL. In practice, that often means an extra conversion step before the invoice data can actually flow into your ERP or accounting system.
And compliance isn't automatic. ZUGFeRD 2.x is EN 16931-compliant only from the "EN 16931" (Comfort) profile upward the widely used Minimum and Basic WL profiles do not qualify as valid e-invoices under the German mandate. With XRechnung, there is no profile to get wrong.
XRechnung: the structured standard
XRechnung is Germany's national implementation of EN 16931: a pure, structured XML invoice with a single, unambiguous data set. It is the required format for invoicing German federal and state authorities (B2G), and it travels natively over the Peppol network.
That last point is where the real advantage lies.
Why XRechnung over Peppol is the smarter route
Germany does not prescribe a transmission channel but Peppol is where structured e-invoicing is heading, in Germany and across Europe:
"But our customers want a readable invoice"
They'll get one. Dokapi automatically renders every incoming XML invoice into a clean, human-readable PDF so your customers and their accounting teams see a familiar document, while their software processes the structured XRechnung data underneath.
In other words: everything the German market loves about ZUGFeRD, without giving up the reliability, reach and future-readiness of Peppol.
Side by side
More than a format switch
Too many businesses treat the mandate as a box to tick: swap PDF invoices for a compliant format and move on. That misses the point. Structured invoice data on a verified network is what makes real automation possible, touchless invoice processing, automated matching and approval, real-time status visibility, faster payment cycles. The companies that choose XRechnung over Peppol now aren't just becoming compliant; they're modernising their entire finance chain while their competitors are still converting PDFs.
Whichever formats your trading partners use, Dokapi's format conversion bridges the gap, your systems send and receive in the structure they expect. But if you're building for the next decade, XRechnung over Peppol is the choice that keeps paying off.
