Intrastat Explained Simply: What Businesses Really Need to Know!
Intrastat is one of those topics that often gets overlooked in day-to-day operations—until problems suddenly arise.
You know how it goes: the statistical number is missing, there’s no indication of whether the shipment is final or not, and unfortunately, information on how the goods were shipped hasn’t been received either. Fields weren’t filled out, leading to unnecessary internal coordination efforts that could have been avoided.
Yet the reporting process isn’t complicated at all once you understand the principle.
What exactly is Intrastat?
Intrastat is a statistical report on the intra-Community movement of goods between EU member states.
As a business, you are required to report your intra-Community movements of goods to the Federal Statistical Office. This is governed by Regulation (EU) No. 2019/2152 . Together with EC Regulation 1982/2004, it governs the EU-wide collection of trade statistics and establishes minimum standards.
Important:
Intrastat has nothing to do with the advance VAT return or the Summary Declaration (ZM)—even if some of the data is similar.
Who is required to file Intrastat reports?
Your company is required to file reports if you exceed certain value thresholds. If you are required to file reports, you must report shipments (goods sent to EU countries), receipts (goods received from EU countries), and direct deliveries (e.g., drop shipments within the EU) .
The exact thresholds are set annually. If the threshold is exceeded, the reporting requirement applies starting the following year.
What is being reported?
Physical movements of goods, returns , and transfers of goods between EU member states (even without a transfer of ownership) must be reported on a monthly basis. This also includes shipments from your German warehouse location to an EU warehouse location. Services are excluded from the report.
Typical details for the Intrastat report include the commodity code (customs tariff number), value of goods, quantity/weight/unit, country of origin, country of destination, and the type of transaction (e.g., sale, return).
Intrastat in Business Central (Practical Overview)
In ERP systems in particular, many problems do not arise during the reporting process itself, but rather in the master data and processes. For example, if item numbers are entered incorrectly, goods and services are not clearly separated, or country and region codes are stored incorrectly, this directly affects the quality of the Intrastat report. Missing flags indicating Intrastat reporting requirements also frequently result in relevant movements not being included at all.
The situation becomes particularly critical with quantity conversions: if these are missing or incorrectly configured, it can quickly lead to inquiries or rejections by the Federal Statistical Office. The result is manual rework, additional effort, and, in the worst case, incorrect declarations. That is why it is worth regularly checking the underlying processes and master data—not just after the declaration file has already been rejected.
If your database is incorrect, your Intrastat declaration will automatically be incorrect.
It is also important to note:
Business Central requires corresponding line items for the Intrastat declaration. If no line items are generated for the respective business process, the Intrastat declaration will not be populated automatically.
Tips for a stable process
So what can you do to ensure a smooth process without having to chase down missing information?
Maintain your product codes centrally and review them regularly. The Federal Statistical Office updates these from time to time, so it’s always worth keeping an eye on them. You need to define clear rules for returns and credit memos. Use the pre-fill option for fields in Accounts Receivable/Accounts Payable to support the sales and purchasing process. Define required fields—the more information that must be entered in the documents, the less rework you’ll have. Check the Intrastat report regularly. Especially when implementing this for the first time, it’s worth reviewing the report even in the middle of the month. Define responsibilities, i.e., who checks the data and who reports it
Our conclusion
Intrastat isn’t rocket science—but it’s a typical “nitty-gritty” issue that can quickly cause problems if you let it run on the back burner.
If you have clean master data and clear processes, you’ll avoid follow-up questions, corrections, and unnecessary stress.
If your Intrastat reporting is currently just running on the back burner, it’s worth conducting a structured review. The effort involved is manageable—the benefits are significant.
Are you required to file Intrastat reports next year and need assistance?
Then sign up for our finance workshop:
“Intrastat – How to Prepare Accurate and Traceable Reports”
Stay up to date and subscribe to our PROTAKT blog!
About the author
Sabine Wigges · Functional Lead Consultant
My journey into the world of ERP began in day-to-day operations before I transitioned to consulting in 2019.
Today, I help companies map their processes in Microsoft Dynamics 365 Business Central in a structured way, always keeping the big picture in mind.
My focus is on clear system logic, transparent workflows, and business management. It is important to me that everything makes sense, remains verifiable, and can be analyzed. Liquidity, payment terms, dunning, and cash discount management are not secondary processes to me, but rather key levers for stability and profitability.
I combine operational experience with a consulting perspective. I know where the bottlenecks lie in day-to-day operations and how to address them in a structured and sustainable way.
Space for your comments