Intrastat reporting in Dynamics 365 Finance

Intrastat is the EU's statistical reporting system for intra-community trade — every EU business above a threshold must declare its arrivals (purchases from other EU countries) and dispatches (sales to other EU countries) periodically, by commodity code, country, weight, value, and transport mode. Dynamics 365 Finance handles Intrastat natively for EU country localisations, with configurable thresholds, exception handling, and direct submission to tax authorities.

The model. Each intra-community transaction (a sale to a customer in another EU country, a purchase from a vendor in another EU country) automatically generates Intrastat data at posting time:

• Commodity code — the EU Combined Nomenclature code identifying the goods.
• Country of origin — where the goods were made (different from where they're shipped from).
• Country of destination / dispatch — where they're going / coming from.
• Statistical value — typically the invoice value adjusted for transport cost.
• Net weight — the goods' weight in kilograms.
• Quantity in supplementary unit — for commodities measured beyond weight (pieces, litres, m², etc.).
• Transport mode — sea, rail, road, air, post, fixed installation, inland waterway, own propulsion.
• Transaction nature — the type of transaction (sale, return, free movement, processing, etc.).
• Statistical procedure — country-specific codes for special cases.

Setup. Configuring Intrastat involves:

• Item commodity codes — every product traded intra-EU needs a code. Maintained on the product card; auto-applies to transactions.
• Country of origin per item — for goods imported then resold, the origin is the original manufacturing country, not the seller's country.
• Vendor / customer country — for partner classification.
• Transport modes per shipping method.
• Transaction nature codes mapped to sales/purchase types.
• Statistical value adjustments — typical formula adding transport and incidental costs to invoice value.

The periodic declaration. Intrastat is submitted monthly (in most EU countries; some allow quarterly for small filers). F&O's Intrastat journal routine:

1. Collects all intra-EU transactions posted in the period.
2. Aggregates per commodity code, country, transaction nature.
3. Allows exception handling — manual additions, exclusions, corrections.
4. Generates the country-specific submission file or report.

The output format varies by country — XML for some, CSV for others, paper for the smallest jurisdictions. Electronic Reporting (Globalization Studio) handles country-specific formats.

Country variations.

• Threshold differences — each country sets its own value threshold below which Intrastat isn't required. Below threshold means no declaration; above means full reporting.
• Two-way vs one-way thresholds — some countries have different arrival vs dispatch thresholds.
• Special procedures — some countries require additional codes (delivery terms, port of entry, customs procedure).
• Submission portal — each country has its own submission system (HMRC in UK pre-Brexit, INSEE / DGDDI in France, ISTAT in Italy, Statistics Sweden, etc.).

Brexit complication. The UK exited Intrastat for outbound dispatches at end of 2021; arrivals continued for a transition period. UK businesses now use a different mechanism for trade with the EU. Northern Ireland has its own arrangements under the Northern Ireland Protocol.

Exception handling.

• Triangulation — A in Country 1 invoices B in Country 2 for goods shipped directly from C in Country 3 to B. Requires specific Intrastat coding.
• Free movements — goods moved between own subsidiaries without sale; reported under specific transaction codes.
• Returns — return shipments coded as such.
• Sample / promotional goods — typically excluded from thresholds.
• Lease and rental — special treatment.

Reconciliation. Intrastat values shouldn't dramatically diverge from VAT return values — Intrastat dispatches relate to zero-rated EU sales; arrivals relate to reverse-charge purchases. Comparison reports flag mismatches for investigation before submission.

Penalties. Late or wrong Intrastat submissions trigger country-specific penalties — typically minor financial penalties initially, escalating with repeated failure. The compliance bar is meaningful.

Common pitfalls.

• Missing commodity codes on items — transactions can't be classified and miss the report.
• Wrong country of origin — most common mistake for goods resold across borders.
• Forgetting threshold monitoring — businesses that grow past the threshold miss the registration moment.

Operational reality. Intrastat reporting is a monthly ritual; configure cleanly during implementation; automate the routine; review exceptions before submission.