UStVA — Umsatzsteuervoranmeldung (German VAT Pre-Declaration)

UStVA (Umsatzsteuervoranmeldung) is the German VAT pre-declaration that businesses must submit electronically to the tax office via the ELSTER portal. Frequency depends on prior-year VAT volume: monthly for established businesses with significant turnover, quarterly for smaller operations, annually-only for very small businesses or those with no VAT activity. Modern ERP systems automate the UStVA from the bookkeeping data, with the ELSTER export typically a one-click operation.

Submission cadence

The cadence is set by the tax office based on the prior year's VAT volume:

• Monthly: businesses with prior-year VAT payable above 7,500 EUR, and all new businesses in the first two years
• Quarterly: businesses with prior-year VAT payable between 1,000 EUR and 7,500 EUR
• Annual only: businesses with prior-year VAT payable below 1,000 EUR — UStVA is waived, only the annual VAT return (Umsatzsteuererklärung) applies

Submission deadline: 10th day of the month following the period, extendable by Dauerfristverlängerung (permanent extension) for an additional month against a deposit.

Typical ERP workflow

In a GoBD-compliant ERP (SAP S/4HANA, Microsoft Dynamics 365 Business Central, abas, proALPHA, weclapp, Lexware, DATEV-suite), the UStVA is generated automatically from the period's journal entries. The ERP categorises each transaction by VAT code, sums the boxes (output tax, input tax, intra-community supplies, reverse-charge etc.), and produces an ELSTER-XML file. The user reviews, signs digitally (with an ELSTER certificate), and submits. Total effort: typically 30-60 minutes monthly for a clean accounting setup.

VAT-code master data and common pitfalls

UStVA quality is determined upstream by VAT-code master data, not by the filing itself. The German UStVA form has 80+ boxes (numbered fields like 81, 86, 35, 41) covering domestic supplies at 19% and 7%, intra-community acquisitions, reverse-charge inbound, exports, EU triangular transactions, and not-eligible input tax. Each transaction in the ERP must be tagged with a VAT code that maps to the right UStVA box. Common pitfalls in mid-market accounting setups: (1) incorrect reverse-charge tagging on services from EU suppliers — a frequent source of correction filings; (2) missing one-stop-shop (OSS) code for cross-border B2C e-commerce under 10,000 EUR threshold versus above; (3) wrong tax-codes on advance payments (Anzahlungen) when goods arrive in a later period; (4) intra-community triangle deals where the German company is the middle party — box 42 specifically. A clean DATEV-style chart of accounts (SKR03, SKR04) with consistent automatic-tax-code assignment per account dramatically reduces these errors. ERP systems with DATEV interface typically inherit a validated mapping out of the box.

UStVA and adjacent compliance obligations

UStVA is one of several VAT-related filings under German law. Zusammenfassende Meldung (ZM): a separate monthly or quarterly report listing each intra-EU counterparty with their VAT-ID and turnover — this supplements UStVA and must reconcile to it. Annual VAT return (Umsatzsteuerjahreserklärung): due by 31 July of the following year (extended to end of February in the second following year if filed by a tax advisor), summarising the year and reconciling against UStVA pre-payments. One Stop Shop (OSS): separate quarterly filing for cross-border B2C e-commerce above 10,000 EUR annual threshold — UStVA only covers domestic and reverse-charge transactions then. Special pre-registration for VAT-grouping (Organschaft): multi-entity groups where the controlling entity files for all members. Modern ERP suites for the DACH market handle these end-to-end: SAP S/4HANA with the localisation pack, Microsoft Dynamics 365 BC with the DE-localisation, abas, proALPHA, Comarch ERP, weclapp, Xentral, Sage X3 Germany. For very small operations under 22,000 EUR annual turnover (Kleinunternehmerregelung), UStVA is waived entirely — a simple PDF invoice without VAT and no electronic filing obligation. Above that threshold, automation through ERP becomes increasingly important as transaction volume grows.

Practical UStVA workflow and common reconciliation patterns

In a mid-market German operation, the monthly UStVA workflow typically follows a defined sequence. Day 1–3 of the month: AP team posts the remaining supplier invoices for the prior period, AR team completes outgoing-invoice runs. Day 3–5: accounting closes the period, runs the VAT report, reviews exception items (unclear VAT codes, intra-community transactions, reverse-charge entries, advance payments). Day 5–8: tax accountant reconciles the UStVA pre-form against the GL (each box must equal a defined sum of GL accounts), reconciles ZM against UStVA box 41 (intra-community supplies), and checks deductible-input-VAT balance against the pendency in box 66. Day 8–10: ELSTER export, digital signature, and submission. With Dauerfristverlängerung, the deadline shifts to the 10th of the second following month, giving more comfort during month-end load. Common reconciliation issues: (1) advance-payment invoices double-counted in revenue and VAT, (2) supplier invoices in the wrong period because of late capture, (3) reverse-charge transactions posted without the offsetting input-VAT entry, (4) credit notes not properly netted against the original invoice in the VAT report. Modern ERP suites for the DACH market handle these correctly when configured well; many problems trace back to local customisations or to spreadsheet-based intermediate steps that bypass standard logic. The cleanest setups use the ERP's standard VAT-report as the single source of truth, with reconciliation against the GL as a control check, never the reverse. Late corrections after submission flow through a Berichtigung (correction filing) within the next-month UStVA — routine but tracked.

Related Topics

• GoBD
• ZUGFeRD