A lot of UK businesses assumed Intrastat reporting ended when the UK left the EU. That assumption is only half right, and the half that is wrong has caught out more than a few finance teams who stopped filing too early or never realized they still needed to.
Intrastat did not disappear after Brexit. It changed shape. The UK side of Intrastat reporting for goods moving from Great Britain to the EU was withdrawn, but businesses moving goods from Northern Ireland to the EU still have to report under the Windsor Framework rules, and any UK business receiving goods into Great Britain from the EU above the reporting threshold still has an active Intrastat obligation. On top of that, EC Sales Lists were formally replaced, but the underlying need to track and report cross-border goods movement never went away, it just moved into new forms with new names.
For a UK business still trading with the EU, the practical result is a reporting landscape that looks simpler on the surface but is genuinely easy to get wrong underneath. Here is what the current rules actually require, who they apply to, and why software that connects trade data directly to operational records matters more now than it did before Brexit, not less.
What Intrastat actually requires today
Intrastat exists to give HMRC and EU authorities visibility into the physical movement of goods across borders, separate from VAT returns, which only capture the financial side of a transaction. Since Brexit, the obligation splits into two distinct groups.
Arrivals reporting still applies to any VAT-registered business in Great Britain that receives goods from the EU above the annual arrivals threshold, currently £500,000. If a business imports stock, components, or materials from EU suppliers and crosses that threshold, it still has to file Intrastat arrivals declarations every month, tracking commodity codes, net mass, quantity, and value for each movement.
Dispatches reporting, covering goods sent from Great Britain to the EU, was withdrawn after the transition period ended. Those movements are now treated as exports and handled through customs declarations instead.
Northern Ireland sits under a different set of rules entirely. Because Northern Ireland remains aligned with EU single market rules for goods under the Windsor Framework, businesses moving goods both into and out of Northern Ireland from the EU still have both arrivals and dispatches obligations, much closer to the pre-Brexit system than the rest of the UK.
Why EC Sales Lists still matter, just differently
Before Brexit, EC Sales Lists tracked VAT-registered sales of goods and services to VAT-registered EU customers, supporting the zero-rating of those transactions. Great Britain to EU sales are now treated as exports rather than intra-community supplies, so the traditional EC Sales List no longer applies to most GB businesses in the way it once did.
Northern Ireland businesses, again, are the exception. Goods movements from Northern Ireland to the EU still fall under EC Sales List-style reporting because Northern Ireland retained its position within the EU VAT area for goods.
The pattern across all of this is consistent. Post-Brexit trade reporting did not get simpler across the board, it fractured into different rule sets depending on which direction goods move and where in the UK they originate. That fracture is exactly where manual tracking starts to fail.
Where businesses get this wrong
The most common mistake is not filing incorrectly, it is failing to recognize an obligation exists at all. A business that used to file both arrivals and dispatches assumes the entire Intrastat requirement ended with Brexit, stops monitoring its EU purchase volume, and only discovers months later that it crossed the arrivals threshold and missed several filings.
The second common mistake happens at businesses operating across Great Britain and Northern Ireland, where finance teams apply a single reporting logic to both, when the two locations genuinely sit under different rules. A goods movement that requires no report from a Great Britain entity might require a full Intrastat declaration from a Northern Ireland entity moving the identical product.
The third mistake is threshold blindness. The £500,000 arrivals threshold is not a one-time check. It applies annually, and a business that sat comfortably under it last year can cross it this year simply by growing its EU sourcing relationships, without anyone deliberately deciding to increase reporting obligations.
Why this needs software, not a quarterly reminder
Intrastat and its related trade reporting requirements share a common weakness with VAT scheme selection: they depend on accurate, current transaction data, and they get missed most often when that data lives separately from where the actual buying and selling decisions happen.
A finance team relying on manual tracking has to pull EU purchase data from purchase orders, match it against commodity codes, monitor cumulative value against the threshold, and repeat that process monthly, on top of everything else finance already owns. It is exactly the kind of recurring, detail-heavy task that slips when the business gets busy, and the penalty for getting it wrong is not just a fine, it is the operational risk of HMRC treating the business as non-compliant on trade reporting more broadly.
Software that connects purchasing and branch activity directly to trade reporting removes the manual pull-and-match step entirely. When goods movement data already lives inside the same system that generates purchase orders and supplier records, the reporting obligation gets tracked automatically instead of reconstructed after the fact.
ALSO READ: Odoo vs Monesize Core: The Real Cost of Open-Source ERP
How Monesize Core approaches this
Monesize Core keeps purchasing, branch activity, and supplier data inside one connected system, which means the underlying data Intrastat reporting depends on, commodity codes, values, quantities, and origin, is already accurate and already tied to real transactions rather than pulled together separately each month.
For a UK business trading across Great Britain, Northern Ireland, and the EU, that connection matters because the reporting rules differ by entity and by direction of trade. A platform built around branch-level operations can apply the right reporting logic to the right location automatically, rather than relying on someone in finance to remember which rules apply where.
That does not remove the compliance obligation. It removes the manual reconstruction work that causes most of the actual mistakes, missed thresholds, misapplied rules between GB and Northern Ireland, and declarations filed late because nobody was tracking cumulative EU purchase value in real time.
Staying compliant without the manual overhead
Post-Brexit trade reporting did not go away, it got more fragmented, and fragmented rules are exactly where manual processes break down. The businesses that stay compliant without losing finance time to it are the ones that connect their trade data to their operational systems, rather than treating Intrastat as a separate quarterly exercise handled in isolation.
If your business trades with the EU and nobody has recently confirmed which reporting obligations still apply to it, that is worth checking before HMRC does it for you.
Automate Intrastat and EC Sales List tracking with Monesize Core. Book a demo to see how it connects to your existing trade activity.