The monthly run
At the start of the month the schedule exports the previous month and mails the file to the tax firm.
Six steps to everyday use.
- Create the tenantThe assistant asks for what DATEV needs in five steps: advisor and client number, sales channels, chart of accounts and fiscal year, revenue accounts, debtor and taxation.
- Handout to the tax firmOne click on the Export page creates the handout as a PDF: master data, format, booking logic and every account in use. The tax firm sees in advance what is coming and says what it wants differently.
- Test export of a booked monthTake a month the tax firm has already booked. The test export is a real file, but it locks nothing and says "Testexport" in its header.
- Trial import and comparisonThe tax firm imports the file as a trial and compares it with its own booking. If something differs, you change accounts or settings and export the same month again - as often as needed.
- The first binding monthOnce the test fits, you export the first month the tax firm has not booked yet - bindingly. From now on every binding run locks its documents.
- Switch on the scheduleOnce a month has run cleanly by hand, the schedule takes over.
your-shop.com/admin
Period
August 2026September 2026Custom period
From01.08.2026
To31.08.2026
The document date counts. Already exported documents are skipped automatically; the file is then ready to download from the run and is kept in the history.
Start the export
Create previewShows totals and rows. Produces no file and locks no document - the history lists it as a preview.
Create test exportProduces a real, complete file for checking. The run does not count as an export and the documents stay free - the file header says "Testexport".
Create exportBinding: writes the file and locks the documents against a second export.
Advisor info sheet (PDF)How bookings are formed, which accounts and number ranges are used, what the export deliberately leaves out and how to import the file.
What makes switching over easy.
- Orders from before the installation count too: the basis is the documents in Shopware, not a log from the day of installation.
- A test export locks nothing, and repeating it costs one click.
- Every account can be overridden on the tenant, and all but the debtor per sales channel too - so the export adapts to the tax firm's accounts, not the other way round.
- Do not export months bindingly that the tax firm has already booked another way - otherwise they would be in DATEV twice.
What gets asked about it.
Which month should we start with?
With the first month the tax firm has not booked yet. Earlier months stay as they are; a test export over them helps with the comparison but does not count.
What if the first binding run was wrong after all?
In the history, from its row menu: "Give up as a test run". Its documents then count as not exported again. If the tax firm has already booked the file, it has to undo that on its side - agree it beforehand.
The other examples
Several companies in one shop
One tenant per company with its own accounts, its own advisor number and its own channels.
Selling into the EU
A revenue account per destination country and a delivery threshold that warns before it is crossed.
Catching up a year
A fiscal year in one run, in steps and in several files if needed.