German Special VAT Audit: Process, Focus Areas, Lines of Defence

An audit finding is not an assessment. And a presumption is not proof.

The Umsatzsteuer-Sonderprüfung — Germany’s special VAT audit — is a fast, targeted external audit of VAT only: typically triggered by automated risk selection, limited to a few filing periods and to specific focus areas. Its speed is what makes it dangerous. This is where the authority’s first version of the facts is written — on input VAT, on intra-Community supplies, on your position in a supply chain — and that version later feeds amended assessments, “knew or should have known” allegations under Section 25f of the German VAT Act, liability proceedings and, in the worst case, the tax fraud investigation service. Auditing is legitimate; a state that refunds input VAT may verify promptly where refunds flow and chains branch. But the audit is a procedure with rules, limits and defence windows. Companies that know them negotiate at eye level. Companies that miss them end up signing someone else’s story.

The starting point: read the audit order within 24 hours

The special audit begins with the audit order (Prüfungsanordnung, Section 196 of the German Fiscal Code, AO). It is three things at once: a scope document (who is audited, which tax, which periods), a challengeable administrative act — and a blocking trigger: once it is served, a penalty-releasing voluntary disclosure (Selbstanzeige) is barred for the taxes and periods covered. The order therefore belongs on your advisers’ desk within 24 hours: Is the addressee correct? Which periods are covered? Is the stated scope narrower than the auditor’s actual conduct? Above all: is there correction potential for periods not yet covered? That junction — correction under Section 153 AO or voluntary disclosure — must be decided before the audit gathers pace, not in its midst.

A point of principle shapes everything that follows: under German doctrine the external audit is an investigation procedure, not the assessment procedure itself. It is a distinct arena in which facts are collected, weighted and interpreted. Defence therefore starts here — not when the assessment notice arrives.

Focus areas: where the special audit looks

The classic focus areas have been stable for years: input VAT from purchase invoices (supplier identity, description of supplies, invoice particulars), refund and surplus positions, intra-Community supplies with their documentary and accounting evidence, chain and triangular transactions, reverse-charge constellations, new counterparties and unusual margins. The administrative mandate for prompt, automation-triggered special audits dates back to a 2002 decree — the historical precursor of today’s risk selection from e-invoicing, CESOP and Eurofisc data. The administration’s data view keeps improving; all the more important that your own data trail tells the same story as your paper.

On data access: the German GoBD principles cover main, upstream and ancillary systems — ERP, merchandise management, payments, document management, interfaces. The auditor may see a great deal, but not everything: access is confined to tax-relevant data of the audit period. A prepared data filter (a dedicated auditor role in the system, defined export packages) prevents over-disclosure, speeds up the audit — and is living proof of organisation.

Cooperation — extensive, but not boundless

During the audit you owe extensive cooperation (Section 200 AO): information, documents, explanations. Two limits deserve particular attention. First, the fishing-expedition limit: requests must stay within the audit’s frame; Germany’s Federal Fiscal Court has expressly held that bank information requests may not be extended without additional grounds for suspicion. Second, the self-incrimination limit: once criminal or administrative-penalty proceedings have been initiated, cooperation duties may no longer be enforced by coercive means (Section 393 AO). Estimates remain possible — balancing cooperation, the right to silence and estimate risk then becomes a core defence task, not a bookkeeping reflex.

A third point is regularly underestimated: Section 160 AO. Whoever books payments must, on demand, be able to name the recipients — identity, address, economic function. In supply-chain cases this provision becomes a trap where onboarding was thin. In the Evidence Pack, recipient data are mandatory fields, not decoration.

The warning light: the criminal reservation in the closing meeting

The audit ends with the closing meeting (Schlussbesprechung) — nominally a wrap-up, in substance the most important negotiation round of the procedure. Findings are discussed, ranges explored, factual settlements (tatsächliche Verständigung) prepared. Two cautions: a factual settlement is only appropriate where the facts are genuinely hard to establish, and it must not become a premature surrender of your exculpatory case. And if the auditor expressly reserves the criminal or administrative-penalty assessment (Section 201(2) AO), that is not boilerplate — it is the signal to merge tax and criminal defence at the latest now.

After the meeting comes the audit report — and with it a principle that turns entire cases: a finding is not an assessment. An audit finding does not automatically produce a lawful amended assessment; the authority needs a correction provision, and its conditions can be attacked in their own right. The response to the report is therefore not a courtesy — it is the first brief of the appeal procedure.

Estimates: the silent escalation

Where the audit alleges accounting deficiencies or cooperation stalls, an estimate quickly enters the room — the point at which focus areas turn into seven-figure amounts. The limits are clearer than practice treats them: an estimate serves to determine the correct tax and must not have a punitive function. The authority bears the burden of proving that the accounts are substantively incorrect; only then does the estimation margin open. Blanket tools are under growing pressure — Germany’s Federal Fiscal Court has voiced doubts about the data basis of the official industry benchmark tables, and whatever the authority cannot explain on inquiry diminishes the evidential value of its own estimate. Above all, the boundary to the criminal case holds: safety surcharges and rough add-ons are not sufficiently fact-based for criminal procedure and must not be carried over; there, full judicial conviction and a minimum culpable amount are required — with the benefit of the doubt applying to the amount as well. For the defence this means: demand full disclosure of the estimate’s foundations, present your own verification and alternative calculations, and expressly object to any “contamination” of the criminal case by tax estimates. Input VAT, finally, is not an act of grace: even within an estimate it must be credited where the substantive conditions are objectively established.

The lines of defence — from day one

Keep the burden of proof where it belongs. Where the audit aims at “should have known” and chain contamination, the Court of Justice’s line applies: the authority must prove the objective circumstances to the requisite legal standard — presumptions and reversals of the burden of proof are expressly prohibited, and membership of a suspicious invoicing chain alone is not enough. The German Ministry of Finance circular on Section 25f confirms the administration’s burden. Every finding phrased as “must have recognised” or “should have noticed” is to be measured against that standard — what the tax office actually has to prove is the central question of the case.

Run your own factual narrative. Documented ignorance exculpates: where the company itself did not know the facts the auditor now describes, the subjective element of evasion or reckless understatement is missing. The ex-ante documented check path — who checked what, when, with what result — is the strongest counterpart to the auditor’s ex-post reading.

Use procedural rights. Put objections on record, document offers of evidence, keep a parallel defence file — judicial protection against the manner of an audit is limited, which makes your own seamless documentation the more important. Where the audit relies on material from other proceedings — control notices, findings at your suppliers, third-party criminal files — the Glencore line on access to the file and equality of arms applies: such material may only be used if you had effective access and a chance to comment.

Think one escalation ahead. If the audit ends in amended assessments, suspension of enforcement must be prepared in parallel; if security measures loom, the asset-freeze emergency plan. Treat the special audit as an isolated event and the second wave will surprise you. Treat it as round one of a potential major case and every later round is already prepared — the VSK team of German attorneys and tax advisers runs both tracks together from the start.

FAQ