The export calculates the whole period before it writes a file, checks its own result and records for every document why it was booked that way. If something is wrong, no file is created - neither half a one nor a wrong one.
All three calculate the same period with the same rules. They differ in what remains afterwards.
| Preview | Test export | Export | |
|---|---|---|---|
| File for DATEV | |||
| Check report and protocol | |||
| Reconciliation for completeness | |||
| Locks the documents | |||
| Hash chain (SHA-256) | |||
| Repeatable | any number of times | any number of times | only takes stragglers |
The file header of a test export says "Testexport" - DATEV shows it on import, so a mix-up with the binding file stands out.
At the top are the findings by kind, split into errors that stop the export and notices that let it carry on; below, every affected document on its own. Every finding explains the cause and leads to the place where it can be fixed.
If an error stops the run, no batch is created, not even half of one. Nothing is locked and nothing is added to the chain. The check report and the protocol still remain in the history, so it is clear what was missing.
The protocol answers the question "why?". For every document it shows the outcome with its reason: booked with tax case, date and accounts; skipped as a duplicate, as a superseded invoice or outside the period; blocked with the error.
The check report says whether what was booked is right - the reconciliation, whether it is complete. Four checks, each with its result.
Of the documents in the period: how many booked, how many already in an earlier run, how many not, how many deliberately excluded.
Which orders have the custom field "Exclude from DATEV export" set.
Every cancelled order whose invoice is already booked has its cancellation or credit note.
If the volume jumps noticeably compared with the previous run, it is flagged.
"Not booked" is not automatically an error: a document for 0.00 or a superseded invoice belong there, and the protocol names the reason for each. What an earlier run already booked is counted separately.
What a binding export has written cannot be quietly changed and cannot be quietly repeated.
The documents of a binding run are recorded. By default a new export of the same period only takes stragglers, such as invoices created afterwards; on the tenant this can be changed under "Already exported documents".
Every locked document carries a fingerprint of its lines. If the shop differs from it later, it shows as soon as the same period is exported again.
Every binding run forms a SHA-256 fingerprint across its booking and master data files and chains itself to its predecessor with it; the document packages carry their own checksums. That shows if a run or a file is missing or has changed afterwards.
This is the plugin's own chain. The freeze in DATEV is a flag in the file header that you set on the tenant.
The history lists every run with period, progress, outcome, kind and findings. Files and document packages can be downloaded again at any time, every file with its own checksum.
The "Email" tab shows what went out for a run: recipients, attachments with size, the delivered wording and, per address, whether the mail went out.
Yes: in the history, through the "…" menu at the end of its row, with "Give up as a test run". File, check report and protocol stay, its documents count as not exported again and come along with the next export. If it was not the most recent run, the hash chain shows a gap at that point. If the file has already been booked at the tax firm, discarding changes nothing about that - agree it beforehand.
Every exported document carries a fingerprint of its lines. If you export the period again and something in the file has changed (amount, account, tax key, date, even the posting text), the run stops: the correction belongs in the next export as a credit note or cancellation. If only the cost centre or the personal account has changed, the document is skipped with a note and the file is created.
Through the document number in document field 1, the link to the document image in field 20 and, if switched on, the order number in field 95. In the shop, the "DATEV" tab on every order shows what was exported for it.
What a tenant is, the five-step assistant and when you need several.
Revenue, cash, shipping and voucher accounts, the four ways to the debtor and the cost centres.
Period, preview, test export and export, the running run and the history.
Errors that stop and notices that do not - and the way to fix each one.
Every setting on the tenant and the global switches, with default and effect.
Booking batch, general reversal, freeze and the other words from DATEV and Shopware.