Short answer: e-invoicing is a workflow topic

Preview of the downloadable asset E-invoicing Workflow Checklist

Recommended next step

PDFEnglishWorkflow review
Free resource

E-invoicing workflow checklist

Compact orientation for format, validation, archive and handoff

If German e-invoicing is moving closer on your roadmap, use the checklist as a focused starting point and then open the readiness check.

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.

What changed from 2025

Orientation for German e-invoicing

TopicMeaning for companies
From 2025 E-invoicing becomes the regular path for many domestic German B2B supplies; receiving capability becomes practical.
Transitional rules Issuing obligations become effective in phases. Revenue size, timing and case type need review.
PDF alone An unstructured PDF is not an e-invoice; it is treated as another invoice form.
B2G Public-sector invoicing has its own requirements, including XRechnung and buyer reference contexts.
ViDA EU digital VAT reporting plans make structured invoice data strategically more relevant.

Formats you should be able to place

FormatTypical contextNext step
XRechnung Public-sector recipients and XML-oriented processing. Compare with ZUGFeRD and check recipient requirements.
ZUGFeRD / Factur-X Hybrid invoice with PDF/A-3 plus embedded XML. Check whether people and systems can process the same invoice.
UBL / CII European syntax routes under EN 16931 and Peppol contexts. Treat as target syntax, not just a buzzword.
Peppol BIS Billing Network and exchange context, often in public procurement and cross-border processes. Go deeper only when a recipient or network path requires it.
Operating model for German e-invoicing with obligations, formats, recipient requirements, generation, validation, sending, receiving, archive and monthly close.
Operating model for German e-invoicing with obligations, formats, recipient requirements, generation, validation, sending, receiving, archive and monthly close.

The operating model shows how obligations, formats, recipient requirements and monthly close connect in a reliable German e-invoicing process.

The operating model shows how obligations, formats, recipient requirements and monthly close connect in a reliable German e-invoicing process.
Accessible description and data

The visual positions German e-invoicing as an operating model with preparation, generation, validation, sending or receiving, archiving and monthly close, supported by governance and data foundations.

The practical e-invoicing workflow

Invoice preparation

Clarify service, tax treatment, references, order numbers, payment terms and recipient requirements.

Format and validation

Generate the invoice from structured data and validate mandatory fields, syntax and business rules.

Sending or receiving

Email, portal, Peppol or another channel must fit the recipient and internal controls.

Archive and accounting

Original file, visual copy, attachments, review status and coding remain traceable.

Sources and limits

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