Posting a ZUGFeRD Invoice in DATEV
A ZUGFeRD file combines a PDF with embedded XML. This guide walks through the general path into DATEV – from DATEV Unternehmen Online to a Buchungsstapel in DATEV Rechnungswesen – and explains why receiving the file is not the same as posting it.
June 5, 2026
In short
A ZUGFeRD invoice is a PDF with embedded XML following EN 16931. It typically reaches DATEV via DATEV Unternehmen Online / Belegtransfer, where the structured data is read, and is then posted in DATEV Rechnungswesen as a Buchungsstapel. Receiving the file is not posting it: the XML still has to be validated and turned into an accounting entry.
What a ZUGFeRD file actually is
ZUGFeRD is a hybrid format. On the surface it looks like an ordinary PDF you can open and read. But embedded inside that PDF is an XML file carrying the same invoice data in structured, machine-readable form, following the EN 16931 norm.
That dual nature is what makes the format useful. A person can look at the PDF, and software can read the XML. Compared with a plain PDF – which is just an image and not an e-invoice at all – ZUGFeRD lets the same document be both human-readable and automatically processable, and the structured XML is what makes downstream posting possible without re-typing.
The general path into DATEV
Getting a ZUGFeRD invoice into DATEV follows a consistent, general pattern. The exact screens vary by setup, but the route is the same.
Into DATEV Unternehmen Online
The ZUGFeRD file reaches DATEV through DATEV Unternehmen Online – for example via Belegtransfer, which moves documents and their structured data into the platform.
The structured data is read
Because ZUGFeRD carries XML, the embedded data – supplier, amounts, tax, line items – can be read out rather than re-keyed from the PDF image.
On to DATEV Rechnungswesen
From DATEV Unternehmen Online the document flows into DATEV Rechnungswesen, where the actual booking takes place.
Posted as a Buchungsstapel
In DATEV Rechnungswesen the invoice becomes an entry in a Buchungsstapel (posting batch) – with the right accounts and tax keys – before it is finally posted.
Receiving is not posting
This distinction is easy to overlook. Having a ZUGFeRD file in accounts payable – or even having its data read into DATEV Unternehmen Online – does not mean the invoice has been posted. Receiving means the file has arrived and its content is known; posting means it has become an accounting entry.
Important: The embedded XML still has to be turned into a Buchungsstapel. It needs the correct accounts, the right tax key and a check that it fits the order or contract. The structured format removes the typing, but the accounting judgement still has to happen.
Why validation still matters
A structured file is not automatically a correct one. Even with ZUGFeRD, the embedded XML should be validated against EN 16931 – whether it is well-formed, whether the mandatory fields are present, whether the totals reconcile. Beyond that format check, the content has to be verified – supplier, amounts and tax treatment – before anything is posted.
This is not only about tidiness. Once an invoice enters the books, the original file has to be archived in line with GoBD, and catching a malformed or incomplete e-invoice before it becomes a posting is far easier than correcting it afterwards.
A clean ZUGFeRD-to-DATEV flow, step by step
Putting it together, a reliable flow looks like this – deliberately general, since exact menus differ by configuration:
1. Receive and detect
The ZUGFeRD file arrives in accounts payable; the format is recognised and the embedded XML identified.
2. Read and validate
The structured data is read out and checked against EN 16931; the content is verified against the order or contract.
3. Transfer via DATEV Unternehmen Online
The document and its data move into DATEV Unternehmen Online, for example through Belegtransfer.
4. Post in DATEV Rechnungswesen
In DATEV Rechnungswesen the invoice is booked as a Buchungsstapel with the correct accounts and tax keys, then archived under GoBD.
For practices working with their accountant, this flow is also where collaboration with the tax advisor fits in: the structured data and the posting batch are exactly what gets handed over and reviewed.
In short
A ZUGFeRD file is a PDF with embedded, EN 16931-compliant XML. It reaches DATEV through DATEV Unternehmen Online – for instance via Belegtransfer – where its structured data is read, and it is then booked in DATEV Rechnungswesen as a Buchungsstapel. The step that is easy to underestimate is the difference between receiving and posting: the XML still has to be validated and turned into a proper accounting entry. With that handled well, the structured format takes the typing out of the process, so the team can focus on the accounting itself.
FAQ
What does a ZUGFeRD file contain?
ZUGFeRD is a hybrid format. It combines a human-readable PDF with embedded XML that holds the same invoice data in structured, machine-readable form following EN 16931. A person can read the PDF, and software can read the XML automatically.
How does a ZUGFeRD invoice get into DATEV?
The common path is through DATEV Unternehmen Online: the file is uploaded or transferred via Belegtransfer, where its structured data is read. From there it flows into DATEV Rechnungswesen, where it can be posted as a Buchungsstapel (posting batch).
Is receiving a ZUGFeRD invoice the same as posting it?
No. Receiving means the file has arrived and its data has been read. Posting means the invoice has become an accounting entry. The structured XML still has to be turned into a Buchungsstapel in DATEV Rechnungswesen, with the correct accounts and tax keys.
Does the ZUGFeRD file still need to be validated?
Yes. Even though ZUGFeRD is structured, the embedded XML should be checked against EN 16931 for completeness and correctness, and the data verified before posting. Validation catches malformed or incomplete files before they reach the books and have to be archived under GoBD.
With Orcha: The accounts payable agent reads the embedded XML from a ZUGFeRD file, validates it against EN 16931 and prepares the posting – so what reaches DATEV Rechnungswesen as a Buchungsstapel is already checked.
New tips straight to your inbox
Subscribe to our newsletter and receive practical AI tips for your daily work.