What is DATEV and why does a German company need a compatible export?

DATEV is the data format and platform that most German tax advisers use to receive and process client accounting data. A ledger that cannot produce a DATEV-compatible export forces the adviser to re-enter the accounts manually, which is slow, billed by the hour, and a source of errors that then have to be reconciled back. It is the practical interchange standard rather than a legal requirement.

What does GoBD require of accounting records?

That records are complete, correct, timely, orderly and, critically, unalterable, with a documented process describing how they are maintained. The unalterability point is what catches cloud ledgers: an entry that can be silently edited after the fact does not satisfy it. Corrections are made by reversing entries so the original and the correction are both visible.

When is the German VAT return due?

The Umsatzsteuer-Voranmeldung is generally due by the 10th of the month following the reporting period, monthly or quarterly depending on the prior year's liability and whether the business is newly established. A permanent extension, the Dauerfristverlängerung, moves the deadline back by one month, usually against a security payment for monthly filers. The annual return is filed separately.

Can a foreign cloud ledger be used by a German GmbH?

Yes, provided it meets the GoBD requirements for completeness, traceability and unalterability, retains records for the required period, and can hand data to the tax adviser in a usable form. The system's country of origin is not the issue. How corrections are handled and whether data can leave the system are the issues.

Does OSS reporting replace the German VAT return?

No. OSS covers cross-border B2C supplies to consumers in other member states; domestic German supplies stay on the domestic return. Running the two from different sources is how the same sale ends up on both returns or on neither, which is why they belong in the same monthly close.

SaaS · 🇩🇪 GermanyScenario

DATEV export and GoBD: why a cloud ledger fails German year end

A German year-end handover fails for two separate reasons that get confused with each other: the ledger produces no DATEV-compatible export, and corrections are made by editing original entries, which does not meet the GoBD unalterability requirement. This is an illustrative example of how Salt approaches German bookkeeping process, using a Berlin GmbH on an international cloud ledger as the profile.

Ask how we'd handle this

Scenario — an illustrative example of how Salt approaches this problem. Not a description of a specific client engagement.

The business shape it describes: Berlin GmbH, EU-wide software sales, monthly VAT filing.

Scenario covers: Bookkeeping process rework and DATEV export setup, with GoBD-compliant record-keeping and OSS reporting brought into the monthly cycle
Jurisdiction: Germany
Sector: SaaS

The setup

Take a Berlin GmbH selling software across the EU, running an international cloud ledger chosen by its US parent for group reporting reasons.
Every year end, the company's Steuerberater re-keys the accounts because the export is unusable. It is expensive, slow, and introduces errors that then have to be found.

What usually turns out to be wrong

No DATEV-compatible export. DATEV is the interchange standard between German companies and their tax advisers, and its absence turns a data transfer into a re-keying project.
Corrections made by editing original entries. GoBD requires that records be complete, traceable and unalterable, so an edited original leaves no audit trail even when the final number is right.
OSS reporting for EU distance sales maintained in a separate spreadsheet, disconnected from the ledger the domestic return comes from.
No documented procedure for how corrections are made, so the practice varies by person and by month.

How this would be worked

Implement a DATEV-compatible export path so the Steuerberater receives data in the format the German advisory workflow expects.
Change the correction procedure to reversing entries with a documented reason, so the original record stands and the correction is visible alongside it.
Write the correction procedure down, because GoBD expects the process to be documented, not just followed.
Bring OSS reporting into the same monthly cycle as the domestic Umsatzsteuer-Voranmeldung, generated from the same ledger.
Leave German tax advice with the Steuerberater. The bookkeeping process, the export path and the evidence trail are built to serve that adviser, not to substitute for one.

Why we'd be the right fit

The visible problem is the export format; the correction procedure is the one that matters. An export path alone hands the Steuerberater tidy data with an unsupportable audit trail behind it.
Solving it without migrating the parent off its international ledger means working inside a system the German side did not choose and cannot replace.

What the business would be able to do

The year-end handover would move data rather than re-key it, so the adviser starts from the company's records instead of rebuilding them.
Corrections would leave the original entry intact with a documented reversal beside it, which is what GoBD asks for.
The domestic return and the OSS return would come from one ledger on one monthly cycle rather than from two disconnected sources.

What we'd flag

Germany does not follow the pattern the other jurisdictions here do, and the two problems have to be fixed together. Fixing the export alone produces clean files with a weak audit trail underneath, which is arguably worse than the visible mess it replaces.

Answers

DATEV export and GoBD: why a cloud ledger fails German year end

Where this applies

BookkeepingService Tech Stack MigrationService All services in GermanyHGB More scenarios42 illustrative, labelled examples

Start with a number

Recognise this shape in your own books?

Tell us where you trade and what shape the books are in. You get scope, price and a start date in writing within one business day — no obligation.

Get a quote in 24 hoursBook a call instead