A correction is not a confession. But the wrong choice turns an error into a case.
Sooner or later every business finds an error in its own German VAT filings: a chain transaction assessed wrongly, input VAT deducted without entitlement, a supplier who turns out in hindsight to have been a missing trader. At that moment the most consequential question of German correction law arises: a simple notification and correction under Section 153 of the Fiscal Code (AO) — or a penalty-releasing voluntary disclosure (Selbstanzeige) under Section 371 AO? The two instruments look confusingly similar; both end in an amended return and a payment. Legally, they are worlds apart: the correction is the fulfilment of a statutory duty by an honest taxpayer. The voluntary disclosure is the emergency exit of an evader — with a completeness requirement, blocking grounds and surcharges. Set the switch wrongly and a duty performed becomes a confession, or a rescue attempt becomes an ineffective partial correction. And German administrative practice, in doubt, sets the switch against the taxpayer.
Understanding the junction: the mind decides, not the form
The difference lies not in the paperwork but in the state of knowledge when the original return was filed. Section 153 AO applies where the taxpayer recognises after the fact that a filed return was incorrect or incomplete — he must then notify the tax office without undue delay and correct. The original return was wrong in good faith; nothing criminal has happened, as long as the notification is timely. Section 371 AO addresses the other case: the return was intentionally wrong, and the voluntary disclosure buys back impunity — at the price of a complete supplementary declaration covering all non-time-barred offences for the tax type, payment within the set deadline and, above certain amounts, a surcharge. Between the two lies reckless understatement, for which Section 378(3) AO provides its own, milder correction track.
Setting the switch therefore requires a diagnosis: who knew what, when, in which role? And here lies the trap on the administrative side — the intent-assumption reflex. Supplementary declarations and audit adjustments frequently trigger criminal proceedings almost automatically, without any finding of intent; the literature documents cases in which the honest taxpayer’s own error report was treated like a confession. The Application Decree on Section 153 AO expressly pushes back: objective incorrectness alone does not indicate intent or recklessness — and an implemented internal control system is an indication against both. This is where a lived VAT compliance system pays off immediately: it evidences that the error was a system error in an honest business — not a covert plan.
The VAT-specific special cases: where the junction lies differently than it seems
Later knowledge of someone else’s fraud is not a correction case. If the company learns only after the transaction that a supplier was entangled in a carousel, the original filing does not retroactively become incorrect: what counts are the circumstances at the time of supply, and an input VAT deduction that arose lawfully does not lapse through later knowledge. There is then no notification duty under Section 153 AO — whoever “corrects” rashly here surrenders positions that may never have been lost, and simultaneously hands over the narrative for a “should have known” allegation. Before any reaction, the question of what the Kittel burden-of-proof rules actually require must be answered.
Preliminary returns and the annual return are separate offences. Germany’s Federal Court of Justice (BGH) has reordered its concurrence case law: incorrect preliminary VAT returns and the annual return for the same year are distinct procedural offences, and cumulative conviction for identical wrongdoing is excluded. In early 2026 it went further: where intentionally false preliminary returns are followed by a failure to file the annual return, that omission is a co-punished subsequent act — the centre of gravity lies with the preliminary returns. More important for correction practice is the second holding of the same decision: a corrected preliminary return does not operate as a voluntary disclosure where sham input VAT is deleted but output transactions remain concealed. Partial corrections do not cleanse — they document.
New notification duties after external audits. Since the DAC-7 implementation, Section 153(4) AO extends the correction duty to situations where audit findings continue to apply to later periods. The prevailing view reads the provision narrowly — the wording limit of Article 103(2) of the German Constitution stands behind that — but the compliance consequence is unavoidable: audit reports must be systematically monitored for knock-on effects, otherwise old findings breed new allegations. A tax CMS that does not translate audit results into subsequent filings has a documented gap.
Blocking grounds: the window closes earlier than most expect
A voluntary disclosure is effective only while no blocking ground has arisen — and the mesh is tight: service of an audit order for the taxes and periods covered, the auditor’s appearance, since 2015 also the officer’s appearance for a VAT inspection, notification that proceedings have been initiated, discovery of the offence. For VAT practice this means: with the audit order for a special VAT audit, the window closes for its scope; the correction analysis must come before any audit escalation. Add the time dimension: in serious cases, limitation periods and the mandatory correction package reach far back — and recent BGH case law on when an offence is “completed” shifts the start of limitation considerably later. Whoever corrects today rarely corrects a single year.
The special track of Section 371(2a) AO — and its limits
Indispensable for VAT practice is the partial-disclosure rule for preliminary returns: for preliminary VAT returns, impunity arises — by way of derogation from the strict completeness requirement — to the extent the person corrects or supplements the incorrect entries; the corrected or late preliminary return operates as an effective partial voluntary disclosure, and the discovery block does not bite with the same severity here. The legislature thereby recognised that the mass business of monthly and quarterly filings needs a channel for running corrections. But the special track has hard edges, and Germany’s Federal Court of Justice marked them in 2026: whoever cleanses only one side of the incorrectness — deleting sham input VAT while output transactions remain concealed behind credit notes without underlying supplies — files no effective disclosure but continues the concealment. The special track privileges honest in-year correction, not a dosed confession. And it ends at the year boundary: for the annual return, the full regime of Section 371 AO applies — including the completeness requirement across all non-time-barred periods. Whoever corrects in-year should therefore always consider which story the later annual return will tell.
The Correction-Pack method: correction as a procedure, not a letter
All of this condenses into a method. First: secure the facts before anything reaches the tax office. Which returns are affected, which periods, which amounts? Who knew what, when — evidenced by documents, not by memory? Second: diagnose the junction. Section 153, Section 371 or Section 378(3) AO — separately for each person and each period; in companies with several knowledge carriers the answer is rarely uniform. Third: construct completeness. If a voluntary disclosure, then properly: all non-time-barred offences for the tax type, robust figures, protective estimates where records are thin — a staggered or “slice-by-slice” disclosure is ineffective. Fourth: control the communication. The correction is drafted to document honesty rather than generate suspicion; unreflected correction letters can damage defence positions permanently. Fifth: secure the flanks. Payment and liquidity, where needed protection against enforcement, insurance notifications, language for banks and auditors.
The honest closing remark: the junction between Section 153 and Section 371 AO is not a form-filling question but the translation of a knowledge diagnosis into procedural law — under time pressure, with blocking-ground risk, and with long-term consequences for every later proceeding. The VSK team of German attorneys and tax advisers sets it with you in a structured way: facts, knowledge carriers, periods — then the filing. In that order, never the reverse.
FAQ
We found an error — can we simply adjust the next preliminary return?
No. Silent set-offs in later filings are the classic route from a correctable error to an evasion allegation. The error is assigned to the correct period and formally notified and corrected — on which track, the knowledge diagnosis decides.
How do I know whether Section 153 AO suffices or a voluntary disclosure is needed?
What counts is the state of knowledge when the original return was filed, per person and period: wrong in good faith → Section 153 AO; intentionally wrong → Section 371 AO; reckless → Section 378(3) AO. In companies the answer is rarely uniform — which is why the facts are secured first and the filing drafted second.
Our supplier apparently was a missing trader — must we now correct?
Not for that reason alone. If you learn of third-party fraud only after the fact, your return was not incorrect when filed; to that extent there is no notification duty under Section 153 AO. Hasty “corrections” surrender positions and hand the authority its “should have known” narrative — examine the evidence first.
What makes a voluntary disclosure ineffective?
Above all incompleteness and blocking grounds: partial corrections (for instance cleaning the input side while output transactions remain concealed — so expressly the Federal Court of Justice), forgotten periods, pending audits or inspections, offences already discovered, late payment. Hence: construct completeness before anything is filed.
Does our tax compliance system help at this junction?
Twice over. It documents good faith at filing — the Application Decree expressly recognises the internal control system as an indication against intent and recklessness — and it surfaces errors early enough for the correction to precede audit orders and discovery. That is exactly why the correction path is a mandatory module of every VAT compliance system.
Emergency line: same-day callback. Error discovered, audit announced, uncertainty about the right correction track? Tell us briefly the periods, magnitude and status — we will set the junction in a structured way before deadlines and blocking grounds set it for you. Professional confidentiality from the first call. [Call the emergency line]
Prefer to write — anonymously if you wish: The anonymous case outline without any identification requirement; response within 24 hours on business days.
Book your free 15-minute assessment →Or pick a slot now (Mon·Wed·Fri 10–12)