FAQ

Does this connect to DATEV directly?

No, and that is deliberate. DATEVconnect and the DATEV Unternehmen online APIs are partner-gated — they need a contract most shops cannot get. The Buchungsstapel is the file every practice can already import, so that is what Datevz writes.

Which DATEV format does it write?

EXTF, header version 700, format category 21 (Buchungsstapel), format version 13 — 125 columns — with version 12 (121 columns) available for older releases. Debtor master data is category 16 (Debitoren/Kreditoren), format version 5.

Do I need to know the accounts myself?

No, but your Steuerberater does. Datevz ships SKR03 and SKR04 presets so you are not starting from a blank form, and everything is editable because the chart of accounts belongs to the practice. Send one test batch before you rely on the monthly rhythm.

Why is the BU-Schlüssel column empty?

Because the preset revenue accounts are Automatikkonten — 8400, 8300, 4400 and 4300 carry their own tax rate. Passing a BU key alongside one is a conflict, not extra safety. If your practice uses non-automatic accounts, put the BU key in the field beside the account.

Does it handle One Stop Shop?

Yes. Map a revenue account per destination country and EU distance sales book there instead of to your domestic accounts. It is off by default, because a shop that has not registered for OSS should still be charging home VAT — turning it on is a statement about your registration, not a preference.

What about reverse charge?

An EU order carrying a valid VAT ID for its own country books as a tax-free intra-community supply, with the customer's VAT ID written into the EU columns. A German customer pasting their Austrian supplier's number does not qualify, and Datevz checks that.

Does it validate VAT IDs against VIES?

No. It checks the syntax for all 27 member states, but never calls out. A checkout must not depend on a foreign service being up, and by the time you are booking the order, whether the number was valid at the time of sale is a matter for the invoice — not the export.

Can I export the same order twice?

Not by accident. An order in a batch is left out of the next one. You can include it deliberately, and the order's export count goes up so the panel can warn you. Deleting a batch releases its orders properly.

What happens to refunds?

They post the money back and reverse the revenue in the same proportions it was booked, off the same accounts, with the VAT coming back off too. You can turn the credit note off if your practice handles it separately — but posting only the money leaves the debtor account permanently out of balance.

Does it post payments?

If you switch it on. Each successful transaction books against the money account mapped for its gateway. Gateway fees are booked only when the gateway actually recorded one on the transaction — nothing is estimated.

Can it export orders from before I installed it?

Yes. The export is a query over completed orders in a date range; there is no marker Datevz needs to have written at checkout. Just watch the fiscal-year rule — one year per batch.

What if my Wirtschaftsjahr is not the calendar year?

Set its start month and day. Belegdatum carries only a day and a month, so the fiscal year in the header is what decides which year the postings land in.

Does it work with multiple stores or currencies?

Multiple stores, yes — filter the export by store. Multiple currencies, no: a Buchungsstapel declares one currency in its header, and booking another needs a Basis-Umsatz and an exchange rate that only you can supply. An order in the wrong currency is refused rather than approximated.

Is my data sent anywhere?

No. Datevz makes no outbound requests at all. The file is generated on your server and downloaded by you.

What does it cost?

$99, one edition, with everything in it. Updates are $79 a year; the plugin keeps working when that lapses.