Germany Winery Compliance Reporting Guide: 2026 Deadlines & Digital Filing

Germany winery reporting at a glance

The key compliance mistake is treating every reporting stream as if it applies to every winery. It does not. The first four rows below are wine-sector records or declarations. The later rows are triggered by activities such as taxable sales, sparkling-wine production, intra-EU trade or placing system-participating packaging on the German market.

Legal basis and current guidance: Commission Implementing Regulation (EU) 2018/274, current consolidated text; Wein-Überwachungsverordnung; and the specialist official sources linked in each section below.

Who files what?

A German winery can occupy several legal roles at once. A vineyard operator can be a grape grower, wine producer, bottler, stockholder, packaging producer, intra-EU trader and excise-tax participant. Each role activates a different data set and often a different authority.

• Growers: keep harvest records and may owe a harvest declaration, depending on the state and exemptions.
• Wine producers: can owe a production declaration and stock declaration, plus official quality testing when using regulated German quality-wine designations.
• Bottlers and merchants: can fall within stock-reporting rules even if they do not grow grapes.
• Sparkling-wine producers or tax debtors: can owe Schaumweinsteuer declarations and may use EMCS for applicable excise movements.
• Intra-EU traders: add Intrastat only after crossing the applicable annual threshold.
• Businesses placing system-participating packaging on the German market: add LUCID registration, system participation and quantity-reporting duties.

Exact scope and exemptions depend on the business model and competent authority. That is why this guide separates national rules from Rheinland-Pfalz examples instead of presenting one state workflow as the German standard.

1. Herbstbuch: what federal law actually requires

The Herbstbuch is the harvest record that connects vintage intake to Germany's wine-control system. Under §14 of the federal Wein-Überwachungsverordnung, the required daily entries are:

1. natural alcohol content,
2. harvest quantity,
3. origin, and
4. grape variety.

Primary law: Wein-Überwachungsverordnung §14.

For a digital winery system, the cleanest practice is to preserve the statutory values as structured fields linked to the underlying lot or intake record. That supports traceability without changing what the law actually says.

2. Harvest and production declarations

EU Implementing Regulation 2018/274 sets the filing framework. Production declarations are due by January 15 at the latest, although a Member State may use an earlier date. The regulation also permits later timing, no later than March 1, for certain late-harvest or specific production situations. Harvest declarations, where required by a Member State, use the same January 15 outer deadline structure.

Primary EU source: Implementing Regulation (EU) 2018/274, Articles 22 and 24, consolidated 12 March 2025.

Rheinland-Pfalz example

The Landwirtschaftskammer Rheinland-Pfalz states that the Traubenernte- und Weinerzeugungsmeldung is due by January 15 and can be submitted through WIP. The state distinguishes own products from purchased or otherwise externally sourced products. Its guidance also provides exemptions for certain full-delivery cooperative members and for very small holdings under 10 are when the harvest is not marketed.

Official state guidance: Landwirtschaftskammer Rheinland-Pfalz, Traubenernte- und Weinerzeugungsmeldung.

For purchased or foreign products, Rheinland-Pfalz guidance uses additional reporting including the Meldung der Abgabe, Verwendung und Verwertung and supplier information. Follow the current WIP instructions for the reporting year rather than copying last year's field set.

Do not universalize state conversion factors

Some state guidance publishes conversion assumptions for its forms. For example, Bavaria's official instructions use 100 kg of grapes = 0.78 hl of wine as a form-specific calculation aid. That does not make 78 liters per 100 kg a single statutory conversion factor for every German winery filing. Use the instructions issued by the competent state authority for the actual declaration.

State example: Bayerische Landesanstalt für Weinbau und Gartenbau, harvest/production declaration guidance.

3. Wine and grape-must stock declaration

At EU level, producers, processors, bottlers and merchants within scope declare their wine and must stocks. Article 23 of Implementing Regulation 2018/274 sets September 10 as the latest filing date but allows Member States to set earlier dates. German official guidance uses stocks held on July 31 as the reference date.

Primary sources: EU 2018/274, Article 23; official Rheinland-Pfalz service portal stock-reporting guidance.

State deadline orientation

The official Rheinland-Pfalz service portal publishes the following orientation dates for state stock declarations. These dates show why a September 10 reminder is unsafe as a single Germany-wide deadline. Confirm the current year with your own competent state authority before filing.

Source for state orientation: Serviceportal Rheinland-Pfalz. The table reproduces only the states and dates listed by that official guidance. It is not a substitute for each state's current-year notice.

4. Filing in Rheinland-Pfalz through WIP

Rheinland-Pfalz operates the Weininformationsportal (WIP) for online wine-sector administration. Registration and access are handled through the official WIP site.

1. Confirm your business and reporting role. Determine whether you are filing as grower, producer, stockholder, purchaser or another reporting role.
2. Register or sign in to WIP. Use the official portal and make sure the correct permissions are active before the deadline.
3. Choose the reporting workflow. For the 2026 stock declaration, LWK Rheinland-Pfalz directs users to Weinbaukartei > Bestandsmeldung.
4. Reconcile before entry. Match vineyard, intake, production and stock records to the reporting date. Resolve unit and category mismatches before submission.
5. Submit by the state deadline and retain evidence. Keep the submitted data and confirmation with the records supporting the declaration.

Official portal: WIP Rheinland-Pfalz. Registration information: WIP registration.

5. AP number and official quality testing

German quality-wine terminology is tied to official testing. Under the Wine Act and Wine Ordinance, wines marketed under designations that require an Amtliche Prüfungsnummer (AP number) must pass the applicable official quality process. Weinverordnung §24 states that a new application is required for each filled partial quantity for which the AP-number process applies.

Primary law: Weingesetz §19 and Weinverordnung §24.

Operationally, keep the application, analysis, lot identity, filled quantity and assigned AP number traceable to the same production record. Do not generalize the AP-number rule to every wine or every bottling activity regardless of designation.

6. Activity-triggered reporting beyond wine declarations

These obligations can be important to a winery, but they are not all winery-specific and they do not all apply to every business.

VAT through ELSTER

Under §18 UStG, the standard VAT advance-return period is the calendar quarter. If the prior-year VAT exceeds €9,000, the advance-return period is monthly. If prior-year VAT does not exceed €2,000, the tax office may exempt the business from advance returns. The advance return and payment are generally due on the 10th day after the reporting period. Special rules can apply to new businesses and particular circumstances.

Primary law: Umsatzsteuergesetz §18. ELSTER developer information: ELSTER Entwickler.

Software note: ERiC is a developer library and interface package used by registered software manufacturers. It is not a generic public REST API that every winery must integrate directly. A winery can file through the official ELSTER environment or compliant tax/accounting software.

Sparkling-wine tax and EMCS

Germany levies Schaumweinsteuer at €136 per hectoliter for sparkling wine with at least 6% alcohol by volume and €51 per hectoliter below 6% alcohol by volume. Where the regular monthly declaration rule applies, §15 SchaumweinZwStG requires the declaration by the 10th day of the following month. German Customs identifies Form 2401 for the monthly declaration.

Official sources: German Customs, tax rates; Schaumwein- und Zwischenerzeugnissteuergesetz §15.

For applicable intra-EU excise movements, EMCS may also be part of the movement-control workflow. German Customs provides special rules for qualifying small wine producers whose average annual production is below 1,000 hl. The simplified treatment is specific to the conditions described by Customs and should not be read as a blanket exemption from movement controls.

Official source: German Customs, Besonderheiten bei Wein.

Intrastat for intra-EU goods trade

The old roughly €500,000 threshold sometimes repeated in winery material is outdated. Germany's current thresholds are more than €1 million for dispatches and more than €3 million for arrivals. A business above the applicable threshold reports monthly, with the return due by the 10th working day after the reporting month. Destatis supports electronic reporting through IDEV and .CORE; official 2026 guidance describes supported file formats and reporting methods.

Official Destatis sources: current Intrastat thresholds and 2026 Intrahandelsstatistik guidance.

LUCID packaging reporting

If a winery is a producer subject to system participation under the Verpackungsgesetz, quantity reports made to the system operator must be mirrored in the LUCID Packaging Register. There is no single statutory “quarterly winery filing” schedule. The reporting rhythm follows the quantity-reporting relationship with the system operator and can therefore differ by contract and reporting type.

LUCID supports XML file upload for data preparation. That should not be described as a public submission API. The Zentrale Stelle Verpackungsregister also states that the data notification generally may not be delegated to an external third party; it must be made by the registered producer or an authorized person within the company, subject to the register's stated exceptions.

Official ZSVR sources: LUCID data-reporting duties and XML data upload.

7. What can actually be integrated?

“Digital filing” is not the same thing as “public API.” Germany's reporting landscape includes web portals, developer libraries, certified participant software and file-upload workflows. The distinction matters when evaluating winery software.

This is the most useful test for any “government integration” claim: ask for the official interface specification, participant requirements, supported form or file schema, and current authority documentation. If those cannot be produced, treat the feature as data preparation rather than direct filing.

8. A practical compliance workflow for German wineries

1. Map legal roles. Record whether the business is a grower, producer, bottler, stockholder, merchant, packaging producer, intra-EU trader and excise participant.
2. Map the competent authority by filing. Wine declarations are state-administered. VAT, Customs, Destatis and LUCID use separate federal channels.
3. Capture harvest data once. Preserve the federal Herbstbuch minimum and link richer operational data without replacing the statutory values.
4. Reconcile production and stock. Tie harvest intake, purchased product, transfers, processing, bottling and July 31 stock to auditable lot-level records.
5. Build deadline logic by state. Do not use the EU outer deadline when the state publishes an earlier filing date.
6. Validate before portal entry. Check units, origins, varieties, product categories, exemptions and reporting identities.
7. Submit through the official route. Use WIP, ELSTER, Customs, Destatis or LUCID as applicable. Do not substitute an undocumented interface.
8. Retain the evidence set. Store the submitted values, confirmation and the operational records that reproduce them.

9. Records, corrections and retention

Article 35 of the current consolidated EU Implementing Regulation 2018/274 requires specified wine-sector accompanying documents and inward/outward registers to be kept for at least five years under the conditions in that article. Vineyard-register data follows its own retention framework. German tax, commercial, payroll or packaging records can have different retention periods, so do not apply one five-year rule to every business record.

Primary EU source: Implementing Regulation (EU) 2018/274, Article 35.

If a submitted declaration is wrong, preserve an audit trail of the original data and the correction. Use the correction route provided by the competent portal or authority for that filing. Avoid silently rewriting source records after submission in a way that makes the filed figure impossible to reconstruct.

10. Common Germany winery compliance mistakes

• Using September 10 as the only stock deadline. It is the EU outer deadline. Many German states are earlier.
• Overbuilding the federal Herbstbuch schema. Federal §14 lists four daily data points. Other details may be useful or locally required, but they are not all federal Herbstbuch fields.
• Calling WIP an API. Online filing is verified; a general public API for the winery declarations covered here was not found in the official material reviewed.
• Treating ERiC as a public REST API. ELSTER describes ERiC as a C library and developer interface package.
• Using an old Intrastat threshold. Current thresholds are more than €1 million for dispatches and more than €3 million for arrivals.
• Assuming LUCID is always quarterly. The LUCID quantity notification mirrors system-operator reporting, and the cadence varies.
• Letting an external service submit LUCID data by default. ZSVR restricts external delegation of the data notification.
• Applying a state conversion key nationally. Use the calculation instructions from the authority responsible for the actual filing.
• Assuming every wine bottling needs an AP number. The official testing rules depend on the designation and applicable quality-wine regime.

Verification and change log

August 5, 2026: English guide built and fully re-verified. Corrected the federal Herbstbuch field set; removed unsupported WIP API/CSV/XML claims; replaced the outdated Intrastat threshold; corrected VAT frequency rules; corrected LUCID cadence and delegation claims; separated state from EU wine-declaration deadlines; clarified AP-number scope; and added the January 1, 2027 online obligation for sparkling-wine Form 2401.

Next review: October 1, 2026, or sooner if a competent authority changes a portal, deadline or filing specification. High-volatility items are the state stock-declaration dates, WIP screen paths, Intrastat thresholds, LUCID workflow rules and the 2027 Form 2401 online rollout. Monitor LWK Rheinland-Pfalz, EUR-Lex, German Customs, Destatis, ZSVR and ELSTER.