Validate the First Export

Run a small manual export before enabling email delivery or a schedule. Choose a short period containing one invoice whose values you already know.

Check document selection

Confirm the selected store, document type and document states. DATEV Export filters invoices and credit memos by their creation date, so compare the period with the document rather than the original order date.

Check the accounting header

Verify the consultant number, client number, fiscal-year start, account framework and account length with the receiving accountant. These values can be technically valid while still being wrong for the client's DATEV account.

Check the booking rows

Compare the exported gross amount, tax, currency, document number, date, debtor account and revenue account with the Magento document. If a value comes from a custom mapping, confirm its variable path and any default used when the source field is empty.

Check the actual import

Open CSV files as Windows-1252 or import them directly into the target accounting software. Validate XML packages against the selected schema. When both formats are selected, import the accounting-data ZIP and XML document ZIP separately through their matching interfaces. A clean file preview is useful, but a successful test import is the meaningful acceptance step.

For transfer-compatible XML packages, open document.xml and compare its document references with the PDF names inside the ZIP. Each referenced PDF must exist under the same transfer identifier.

Add optional output afterward

Once the basic booking file is accepted, test PDFs, customer master data, email delivery and automation separately. This keeps a delivery or packaging issue from being mistaken for a mapping problem.

For a specific failure, continue with Common Issues. The FAQ explains formats, date selection, master data and OSS at a higher level.