Connecting DATEV: choose the data service before the interface.
Transfer documents and structured invoice or accounting data from one source system to the appropriate DATEV data service.
Read the German originalA document image is not an accounting entry
DATEV distinguishes several data services. A document image service transfers documents, while other services handle structured invoice or accounting data. The appropriate handover depends on what the source system provides and where further processing will happen.
Discuss a specific monthly workflow with accounting. Which data is currently added? Who knows the correct assignment? These answers determine whether an existing export function is sufficient or an API connection will actually reduce work.
References hold the context together
A document and its structured data must belong together unambiguously. This requires stable identifiers, a clear target client and understandable responses. Also check credit notes and amendments if they form part of the agreed process.
When a transfer is interrupted, establish its actual status. Sending everything again can create duplicates. Reconciliation between expected documents and those actually delivered is therefore part of the interface.
Include the accounting practice in testing
One source system, one target client and a few examples selected by the specialists are sufficient for a pilot. The responsible team checks whether the data is usable correctly in the next step. A technical success message alone does not answer that question.
Clarify the prerequisites of the chosen DATEV data service before development begins. After a successful handover, scheduling, monitoring and other document types can be added. Accounting decisions remain separate from technical data transfer.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
DATEV handover for your business software · Packages