Short answer: recipient and process decide

Format decision in practice

SituationLikely routeWhy
German public-sector recipient Check XRechnung B2G processes often require XRechnung, buyer references and defined portals or exchange routes.
B2B customer needs machine data and a readable invoice Check ZUGFeRD / Factur-X Hybrid PDF/A-3 with embedded XML can connect visual invoice and structured processing.
Automated processing without visual PDF XRechnung or UBL/CII profile Pure XML can be clearer for systems but needs review and rendering processes.
International exchange through a network Check Peppol / EN 16931 profile The exchange route may matter more than the local format label.
Video overview

German E-Invoicing Workflow in 3 Minutes: Requirements, Formats and Handoff

The video explains German e-invoicing requirements, XRechnung, ZUGFeRD, UBL/CII, Peppol, validation, archiving, project billing and accounting handoff as one connected workflow.

Decision tree for XRechnung, ZUGFeRD and Peppol by recipient, PDF need, channel, validation, archive and accounting.
Decision tree for XRechnung, ZUGFeRD and Peppol by recipient, PDF need, channel, validation, archive and accounting.

The format decision starts with the recipient and then has to fit validation, archiving and accounting handoff.

The format decision starts with the recipient and then has to fit validation, archiving and accounting handoff.
Accessible description and data

The infographic walks through a recipient-first decision tree for XRechnung, ZUGFeRD and Peppol, connecting format choice with validation, archive and accounting.

Common format mistakes

Format by familiarity

  • A format is chosen because it sounds familiar.
  • Recipient requirements, validation and archiving remain open.

Format by workflow

  • Recipient, channel, mandatory fields, visualisation and accounting are checked together.
  • The format decision becomes testable and documented.

Questions to answer before choosing a format

QuestionWhy it matters
Is the recipient a public-sector buyer or a B2B customer? B2G requirements, buyer references and portals differ clearly from many B2B workflows.
Does the recipient need a readable PDF? ZUGFeRD/Factur-X can fit when the embedded XML is also correct from a business perspective.
How will validation and archiving work? The chosen format must fit validation rules, visual copy, original file and accounting handoff.

Check the format decision in the workflow

Standards note

Portrait of Heinrich Ruhwasser wearing a dark suit and light blue shirt.
Author

Heinrich Ruhwasser

Your feedback

How would you rate this article?

Did this article help, or is something missing? Your feedback goes straight into improving our articles.

Related reading