Italy Winery Compliance and SIAN Reporting: 2026/27 Guide

What does an Italian winery have to report?

Short answer: Italian wine businesses generally work through SIAN and the competent agricultural paying body to maintain the electronic wine register, report wine and must stocks held at July 31, and file annual harvest and production declarations when applicable. Wine movements can also require official accompanying documents such as MVV-E or, in excise-suspension cases, e-AD. Exact obligations depend on the operator, activity, region, wine category, and exemptions.

The core national framework is administered through the Sistema Informativo Agricolo Nazionale (SIAN), the Ministry of Agriculture, Food Sovereignty and Forestry (MASAF), its ICQRF inspection department, AGEA, and regional paying bodies. The current MASAF 2026/27 harvest vademecum is the best current national operational reference for winery teams.

Italian winery reporting at a glance

Source basis: MASAF 2026/27 harvest vademecum; DM 20 March 2015 n. 293; DM 18 July 2019 n. 7701 as amended; Commission Delegated Regulation (EU) 2018/273; Commission Implementing Regulation (EU) 2018/274. Campaign-specific extensions can supersede standing dates.

Which agencies and systems matter?

MASAF

Italy's Ministry of Agriculture, Food Sovereignty and Forestry. It issues national wine-sector rules and current operational guidance.

ICQRF

The ministry department responsible for quality protection and fraud repression in agri-food products. ICQRF oversees important winery register, communication, movement and control functions.

SIAN

The national agricultural information system. MASAF's 2026/27 vademecum states that the wine register is kept exclusively on the SIAN portal.

AGEA and regional paying bodies

AGEA coordinates agricultural payment and declaration processes nationally, while some regions use their own competent paying body and applications. The filing route therefore is not identical in every region.

CAA

A Centro di Assistenza Agricola can act as an authorized intermediary where the applicable procedure permits delegation.

1. Keep the SIAN electronic wine register current

Italy's national wine law and implementing rules require electronic recordkeeping for covered wine-sector operators. MASAF's 2026/27 guidance says the registro telematico is maintained exclusively through SIAN and may be operated by the legal representative or by a properly delegated CAA or other recognized specialized business. See the official SIAN electronic-register portal and the current consolidated text of Law 238/2016.

What goes into the register?

At EU level, the inward-and-outward register covers entries and withdrawals of wine products and specified production or cellar operations. Commission Implementing Regulation (EU) 2018/274 sets the core information and timing framework. Italy implements that framework through its SIAN register and national rules.

Typical cellar events that can create register entries include receipts, dispatches, crushing or transformation steps, blending, bottling, enrichment and other regulated oenological operations. The exact SIAN operation code and required attributes depend on the product and event. Do not map cellar actions to SIAN codes from a generic list alone. Use the current SIAN technical documentation and code tables.

How quickly must operations be recorded?

The EU baseline in Implementing Regulation (EU) 2018/274 requires, among other things, entries no later than the working day after receipt, most specified processing operations no later than the following working day, and enrichment on the day of the operation. Italy's DM 293/2015 adds detailed national timing rules and permits longer transmission periods in defined cases.

SIAN's official guidance shows that wineries with qualifying computerized accounting, and qualifying producers below 1,000 hl that produce predominantly from estate-grown grapes, may use a window of up to 30 days for certain records if the conditions are met. That is not a blanket 30-day rule. Enrichment and several sensitive operations or products have shorter deadlines. The official SIAN register timing tables and register FAQ explain the exceptions.

Small-winery register exemption

The current 2026/27 MASAF vademecum confirms a narrow exemption under Article 58(2) of Law 238/2016. For an oenological establishment producing 50 hl or less per year with an attached direct-retail or restaurant activity, the register obligation can be considered satisfied through the production and stock declarations, provided the operator also meets the applicable retail-dealer conditions. This is a conditional exemption, not a general exemption for every winery under 50 hl.

2. File the annual wine and must stock declaration

The dichiarazione di giacenza reports relevant wine and must stocks held at midnight on July 31. MASAF's 2026/27 vademecum states that products obtained from grapes harvested in the current calendar year's new harvest are excluded from that closing stock declaration.

2026 stock-declaration workflow

1. Reconcile physical stock to the SIAN register at July 31. Investigate missing movements, incorrect product classifications and unexplained differences before closing.
2. Review the July 31 electronic balances. SIAN's official web-service specification includes a stock-balance retrieval service for registered wine operators and CAAs.
3. Submit the stock declaration between August 1 and September 10. Use AGEA's applicable procedure or the procedure of the competent regional paying body.
4. Close the annual SIAN register by September 10. MASAF states that SIAN will perform the closure automatically if the operator does not.
5. Keep the receipt and final declaration. After the annual register is closed, MASAF warns that operations through July 31 can no longer be modified or integrated. The system carries the closing balances forward to August 1 through automatically generated GIIN operations.

For the legal baseline, Commission Implementing Regulation (EU) 2018/274 requires producers, processors, bottlers and merchants within scope to make the stock declaration by September 10, while the detailed applicability and electronic procedure are implemented nationally.

3. File harvest and production declarations

Italy uses annual harvest and wine-production declarations to report grapes destined for vinification and the wine or must produced in the campaign. Current regional implementation guidance, including the AGREA SitiFarmer service and Piemonte's annual wine-declaration service, confirms electronic filing and illustrates why the competent regional path matters.

Harvest declaration

For covered grape producers, the harvest declaration reports the producing vineyard area, quantity of grapes harvested and destination of those grapes. Commission Implementing Regulation (EU) 2018/274 sets those minimum data elements. In Italy, the standing national harvest deadline is November 30 following DM 555831/2022, unless a campaign-specific measure changes it.

Production declaration

For covered wine or must producers, the production declaration reports the current campaign's production. EU rules require information such as the producer, place products are held, product inputs, suppliers, vineyard area and volumes obtained. Italy allows production data from the SIAN electronic register to support the declaration, reducing duplicate entry when the register is accurate.

For 2026/27, use the deadline-watch box near the top of this guide. The new MASAF vademecum says November 30 for the declarations, while the underlying production rule historically uses December 15. Until the campaign filing circular resolves the wording, do not build a December 15 production deadline into an automated compliance calendar for 2026/27.

DOP / IGP production claims

Where a winery claims protected-origin or protected-geographical-indication production, the declaration workflow also supports the rivendicazione of DO / IG production against the vineyard register. The latest available AGEA campaign instructions and regional implementation materials should be checked for the exact fields and local workflow.

4. Use the correct wine movement document

Moving wine-sector products can require an accompanying document. MASAF's current 2026/27 guidance covers the electronic wine accompanying document (MVV-E), permitted validation/transmission procedures, and e-AD for movements that fall under the excise-movement rules.

Do not assume every shipment uses the same document. The correct document depends on the product, origin and destination, excise status, transport scenario and available exemptions. For current procedures, use the ICQRF wine-sector document page and the current MASAF harvest vademecum before configuring a shipping workflow.

Can winery software connect to SIAN?

Yes, SIAN documents application-to-application web services for authorized users. This is not accurately described as a generic public REST API. SIAN's official material describes cooperazione applicativa using web services, XML, SOAP and WSDL-based specifications, with test and production credentials and service-specific access rules.

This remains a live technical pathway. SIAN currently hosts a wine-register web-service technical document updated in January 2025, along with specifications for stock declarations, production declarations and operator communications. The official portal also describes a web-service interchange system for the electronic registers.

What an integration team should verify before building

• The winery or delegated party is enabled for the relevant SIAN service.
• The current WSDL / XSD and SIAN code tables are used, not copied fields from an old implementation.
• Each facility and operator identifier is taken from the live SIAN master data.
• Submission responses, validation errors and receipts are retained with the originating winery record.
• Campaign dates and regional paying-body routes are configuration data, not hard-coded assumptions.
• A test environment is used before switching authorized traffic to the production service.

Start with the official SIAN site map and technical-document areas. SIAN's FAQ identifies https://registri.sian.it as the web-service test system, while official credentials are used for production interchange.

What this guide intentionally does not mix into SIAN wine reporting

Italian electronic invoicing, VAT, telematic retail receipts, payroll and company financial-statement filings are real business obligations, but they are not the same workflow as the wine-sector SIAN register and annual vitivinicultural declarations. Their scope depends on tax status, legal form and sales channels. Keeping those systems separate makes the compliance map more accurate and prevents a winery-specific guide from turning generic corporate accounting rules into false wine requirements.

For those cross-industry obligations, confirm the current position with the Agenzia delle Entrate, the relevant chamber / business register, and the winery's commercialista.

2026/27 Italian winery compliance checklist

• Confirm the winery's SIAN access, facility records and delegation status before harvest.
• Confirm whether the winery qualifies for any electronic-register exemption or extended recording window before relying on it.
• Keep cellar receipts, dispatches, bottling and regulated oenological operations synchronized with the SIAN register.
• Reconcile physical wine and must inventory to SIAN at July 31.
• Submit the stock declaration from August 1 through September 10 and retain the receipt.
• Complete the annual register balance and closure by September 10.
• Before moving wine, choose the correct MVV-E, e-AD or other permitted transport documentation for the specific movement.
• Reconcile vineyard, grape, must and wine data before the annual harvest and production declarations.
• For 2026/27, plan internally for November 30 for both harvest and production until the competent campaign instructions confirm the production deadline.
• Archive final declarations, protocol / acceptance receipts and supporting source records together.

Common reporting mistakes to avoid

Treating the 30-day register window as universal

It is conditional. Some operations retain much shorter timing requirements. Configure deadlines by operation and eligibility, not by winery size alone.

Closing July before the cellar is reconciled

The 2026/27 MASAF guidance warns that once the annual register is closed, operations through July 31 cannot be modified or integrated. Reconcile first, close second.

Assuming every region uses the same filing screen

AGEA coordinates nationally, but competent regional paying bodies and applications can differ. Build the workflow around the winery's actual paying body.

Hard-coding an old annual deadline

Campaign extensions happen, and the current 2026/27 guidance itself creates a production-date conflict that must be watched. Use an annual rules check before harvest.

Calling SIAN a public REST API

SIAN publishes web-service interoperability specifications, but access and formats are controlled. Current official materials describe authorized SOAP/XML/WSDL-style application cooperation.

Regulatory filings are easiest when the source records are already clean. Solera brings vineyard, production, cellar, inventory, bottling, compliance and reporting data into one winery system, so teams can reconcile the operational facts that feed a filing without rebuilding the vintage from disconnected spreadsheets.

For Italy, the safe use case is recordkeeping, reconciliation, reporting preparation and workflow control. This guide does not claim that Solera currently submits filings directly to SIAN, AGEA or a regional paying body.

See Solera's winery management features or browse the Solera winery compliance guides.

Official sources and references

1. MASAF, ICQRF. Vademecum vendemmiale, campagna vitivinicola 2026/2027. Current campaign operational guidance. Accessed August 5, 2026. Italian.
2. Normattiva. Law 12 December 2016, n. 238, consolidated text. Last official consolidated update shown in 2026. Accessed August 5, 2026. Italian.
3. SIAN. Registri telematici di carico e scarico. Current official portal for electronic registers. Accessed August 5, 2026. Italian.
4. SIAN. Il registro telematico per il settore vitivinicolo. Official timing and workflow tables for the wine register. Accessed August 5, 2026. Italian.
5. SIAN. FAQ sul registro vitivinicolo, Version 6. Official register FAQ covering timing, exemptions and web services. Accessed August 5, 2026. Italian.
6. SIAN. Web-service technical specification for the electronic wine register. Current SIAN-hosted document updated January 28, 2025. Accessed August 5, 2026. Italian.
7. SIAN. Web-service rules for the wine/must stock declaration. Version 2.0, July 31, 2018. Still published in the current SIAN API documentation area. Accessed August 5, 2026. Italian.
8. SIAN. Web-service rules for the wine production declaration using wine-register data. Version 01, September 30, 2019. Still published in the current SIAN API documentation area. Accessed August 5, 2026. Italian.
9. European Commission / EUR-Lex. Commission Implementing Regulation (EU) 2018/274. Register and declaration requirements. Accessed August 5, 2026. English.
10. MASAF. DM 555831 of October 31, 2022. Changes the harvest declaration deadline to November 30 from the 2022/23 campaign onward. Accessed August 5, 2026. Italian.
11. MASAF. 2025/26 decree extending harvest and production declaration deadlines. Confirms the standing underlying dates before that campaign's temporary extension. Accessed August 5, 2026. Italian.
12. Regione Piemonte. Annual declarations for viticultural and oenological businesses. Authoritative regional filing guidance; confirms electronic filing and standing national deadlines. Accessed August 5, 2026. Italian.
13. AGREA, Emilia-Romagna. SitiFarmer wine declaration service. Authoritative regional application and instructions. Accessed August 5, 2026. Italian.

Verification notes

This page was checked against the current 2026/27 MASAF harvest guidance, the current consolidated Italian wine law, official SIAN portal and technical documents, EU wine-record and declaration rules, and recent national and regional filing instructions. The uploaded research draft was treated as a lead source only. Claims that could not be supported by current official material were removed or narrowed.

Important correction from older guidance: annual declaration dates have been changed and temporarily extended in recent campaigns. The 2026/27 campaign also contains the production-deadline inconsistency described above. That item is intentionally visible rather than silently resolved in favor of an older date.