The last mile to the tax firm decides whether the automation holds. Documents have to arrive in DATEV Unternehmen online (DUO) in an audit-proof way, with the document image attached directly to the posting record, and failed transfers have to get noticed.
I set up this transfer the way it is documented in the DATEV integration whitepaper: automatic creation of XML/ZIP packages for DATEV DUO, GoBD-compliant, configurable per client and monitored. It is the final building block of the path that starts with receiving e-invoices and runs through account assignment.
Audit-proof transfer as XML/ZIP
Instead of batch emails with PDF attachments, the system automatically creates XML/ZIP packages and transfers them to DATEV DUO. The tax advisor finds the document image right on the posting record, with no more jumping between inbox, filing system and ledger.
Multi-client by design
Corporate groups rarely book into a single DATEV client. The documented solution is therefore multi-client by design: every module can be activated individually per DATEV client. Several legal entities, different process maturity, one setup, without parallel installations that drift apart.
Error handling and monitoring
Transfers fail; the question is not if but when. What matters is what happens next. The solution described in the whitepaper works with configurable notifications and manual retry actions: the error is reported, the document stays traceable, and the transfer can be repeated deliberately. Without such monitoring, many companies learn about interface errors from their tax advisor’s queries, exactly what the DATEV interface check asks about.
How the document transfer fits into the bigger picture of e-invoicing, account assignment and DATEV integration is shown on the E-Invoicing & DATEV overview.