Transfer to DATEV
NCS-DATEV offers two routes for handing documents and postings over to DATEV. Both produce the same payload – they only differ in transport. The route is a setting and can be changed later.
The two routes compared
| Route A – file | Route B – online interface | |
|---|---|---|
| Result | ZIP document package with a descriptor file, posting data and the PDF files | Direct requests against the DATEV interface |
| Delivery | via DATEV Belegtransfer (monitored folder) | by the application itself, secured with OAuth 2.0 and OpenID Connect |
| DATEV approval required | no | yes |
| Availability | from the first release | to be added later |
Which route fits?
Route A is the quickest start: the standard DATEV Belegtransfer is enough and no separate approval by DATEV is needed.
Route B works without an intermediate folder and transfers immediately, but requires registration and approval with DATEV.
Route A – file via Belegtransfer
NCS-DATEV builds a document package: a ZIP archive that contains the document files themselves plus a descriptor file with the index data and the structured posting data. The package is placed in a folder monitored by DATEV Belegtransfer, which forwards it to the tax office automatically.
Details and setup: Document transfer (file)
Route B – DATEV online interface
On this route NCS-DATEV talks to the DATEV interface directly. Sign-in uses an authorisation flow (OAuth 2.0 with OpenID Connect); access is granted once and refreshed automatically afterwards.
This requires the application to be registered and approved with DATEV.
Details and setup: DATEV online interface
What is identical either way
- assembling the data from SAP Business One or DocuWare
- the field mapping
- the validation before sending
- the logging of every transfer (Monitor)
Switching the transport route therefore leaves your mappings and validation rules untouched.
DATEV specifications
The binding technical specifications from DATEV (schema files and validation tool) must be obtained from the DATEV Developer Portal and may not be redistributed. This documentation only refers to them.