Interface requirements for DATEV XML interface online
The DATEV XML interface online can be used to transfer digital receipts and structured receipt data to DATEV Unternehmen online via DATEV Belege transfer or DATEV Rechnungsdatenservice 1.0. The transferred data is used to generate document records for DATEV Belege online (extended processing form) or DATEV Kassenbuch online. Posting proposals for our DATEV accounting system can be generated using a provision process for the document records from Belege online/Kassenbuch online.
The requirements refer to the use of the DATEV XML interface online as part of an integration of the DATEV Rechnungsdatenservice 1.0.
Preparation & process
Converting the file format
The information contained in the interface descriptions of the DATEV XML interface online must be taken into account by the software companies. Only the newer XML variant "Document record data file" or "Ledger" (no INVOICE ) is to be used.
MUST: Implementation of the latest version of the LEDGER format for invoice & cash register data.
Schema validation
The XML files can be validated on the basis of the XSD files provided. The DATEV Rechnungsdatenservice 1.0 does not offer validation via API, neither in sandbox nor in production. Validation only takes place in the DATEV app itself and the result can be queried via the /protocol-entries endpoint.
MUST: Implementation of automated XSD validation when generating the XML files.
Test in DATEV App
The schema validation only covers technical errors based on the XSD file. However, other errors may occur that can only be detected at the time of import. For a complete validation of the files, a test import to DATEV Unternehmen online is always required.
SHOULD: Import the XML files into a test database in the production environment of DATEV Unternehmen online using DATEV document transfer or Rechnungsdatenservice 1.0.
Generate sample files for audit
Based on the functional use cases of the 3rd party app, sample files must be created for an audit by DATEV. The requirements for the various use cases that can be implemented online with the DATEV XML interface can be found in the "Requirements" chapter.
Appointment booking
Book an appointment via our appointment booking portal An e-mail template is integrated into the appointment booking, which clarifies questions about the range of functions. The files to be checked must then also be attached & sent in this e-mail.
Check by DATEV
The files sent in will be checked by a consultant on the booked date. The result of the check is then communicated promptly by email.
Requirements
The 3rd party app must be able to fill in certain technical data fields in the XML file so that the interface also offers added value compared to conventional posting, e.g. via a digital receipt. If one of the data fields from the requested basic data cannot be mapped in the manufacturer's 3rd party app, this must be explained in the email with the sample files. Depending on the use case, sample data is specified and suitable XML files are to be generated based on this data.
Sample files are only to be generated for the use cases that are also available in the 3rd party app.
Our DATEV XML interface can mainly be used to map the following use cases:
- Transmission of invoice data
- Incoming invoices
- Outgoing invoices
- Invoice correction
- Transmission of cash register data
- Daily log
- Single transaction
Invoice data
For the sample files to be checked, we provide here several incoming invoices & outgoing invoices as PDF and suitable XML files are to be generated on the basis of these documents. At least the following basic data must be provided within the XML files:
- Customer/supplier account [bpAccountNo]
- G/L account [accountNo]
- Customer/supplier name [customerName][supplierName]
- Customer/supplier location [customerCity][supplierCity]
- Invoice date [date]
- Invoice number [invoiceId]
- Amount [amount]
- Tax rate [tax]
- Currency code [currencyCode]
- Booking text [bookingText]
Incoming invoice/outgoing invoice
MUST: Create the sample files for an incoming and/or outgoing invoice based on the sample documents and enter at least the basic data. Use the prepared sample documents as a document for the sample files. The sample files are to be bundled as a ZIP file in the same way as they would be transmitted via the data service. The ZIP file must be named according to the use case and, if necessary, provided with a consecutive number (e.g. Outgoing invoices_1.zip)
Invoice correction
MUST: Create sample files for an invoice correction based on the sample documents from the incoming/outgoing invoice and enter at least the basic data. Use Create a document for the invoice correction for the sample files themselves. The sample files are to be bundled as a ZIP file in the same way as they would be transmitted via the data service. The ZIP file must be named according to the use case and, if necessary, provided with a consecutive number (e.g. Invoice correction_1.zip)
Cash register data
We do not provide any specific sample data for these sample files to be checked. The sample data must correspond to the use case described and contain the basic data. The XML files for POS data must be able to provide at least the following basic data:
- G/L account [accountNo]
- Date [date],
- Amount [amount],
- Tax rate [tax],
- Currency code [currencyCode],
- Document number (for at least one income/expense) [invoiceId]
- Booking text [bookingText]
Daily logs
Create a daily log for two days, each with several receipts and expenses. Different tax rates must be used among the income and expenses.
MUST: Create the sample files based on the description. The sample files are to be bundled as a ZIP file in the same way as they would be transmitted via data service. The ZIP file must be named according to the use case and, if necessary, provided with a consecutive number (e.g. Tagesprotokoll_1.zip)
Single transaction
Create sample files for several individual transactions (income/expenses) and use different tax rates for this. The individual transactions should be spread over at least two months.
MUST: Create the sample files based on the description. The sample files are to be bundled as a ZIP file in the same way as they would be transmitted via data service. The ZIP file must be named according to the use case and, if necessary, provided with a consecutive number (e.g. Einzeleltransaktion_1.zip)