DATEV export
Deutsch View in the StoreStore
  1. Home
  2. Examples
  3. The monthly run

Example On the first of the month, last month is with the tax firm.

One shop, one company, accrual taxation, the schedule set to monthly at 6 a.m. This is how an ordinary month runs.

The sequence

From the end of the month to the import.

  1. On the first, 6 a.m.August is completely over. At the set hour the schedule starts the run for the whole month.
  2. The run calculates and checksAll invoices, credit notes and cancellations of the month, every document with its tax case and accounts. Check report and reconciliation are created as with an export by hand.
  3. The documents are lockedThe run records its documents and joins the hash chain. The same month does not end up in DATEV twice by accident.
  4. The email goes outTo the tax advisor, the second address at the tax firm and to you: the booking batch attached, with diverse addresses or individual debtors the master data too, the document packages as a link.
  5. The tax firm importsFirst the debtor master data, if the tenant books with diverse addresses or individual debtors, then the booking batch, then the document packages. The document link connects booking and document image by itself.
  6. You look at the dashboardLast export, documents waiting, bookings and findings of the last run - one look is enough.

your-shop.com/admin

Orders › DATEV export › Tenants

Muster Handels GmbH

CancelSave

Master dataBookingAccountsTax & OSSExportSales channels

Scheduled export

Whether this client exports on its own, in which cadence and in which hour

Automatic scheduled export

Export intervalMonthly (on the 1st, for the previous month)

Export time6:00 - 6:59

Due next: 01.09.2026 - 30.09.2026.Last exported: 01.08.2026 - 31.08.2026.

Mail after the scheduled export

Whether and to whom the export mail goes. Each address gets its own mail with the same content.

Send the mail

Advisor emailpost@kanzlei.example

Second advisor addressteam@kanzlei.example

Your own addressoffice@muster.example

When things go differently

Three cases that happen in every shop.

An invoice comes late

On 3 September an invoice is created, dated 31 August. The next run reports it with the month it belongs to. You export August once more - the new file holds only the straggler. An export from the admin sends no email: fetch the file from the history and pass it to the tax firm.

An invoice was wrong

The correction goes into the next export as a cancellation, together with the new invoice. DATEV then has invoice, cancellation and new invoice side by side.

A month is blocked

If, say, an account for a new tax rate is missing, no file is created. The tax firm and you get a notice; after the fix the schedule tries again at its hour.

Questions

What gets asked about it.

Do I have to do anything on the first?

No. You can check in the history whether the run went through; the dashboard shows the last export and its findings.

The other examples

Switching over

Test export, trial import and reconciliation before the first binding run counts.

Selling into the EU

A revenue account per destination country and a delivery threshold that warns before it is crossed.