Intrastat reporting in Denmark looks deceptively simple: if you trade goods with other EU countries and exceed certain thresholds, you must submit monthly declarations. Yet many Danish companies, including subsidiaries of international groups, systematically make the same mistakes. These errors may seem minor, but they can lead to penalties, time‑consuming corrections, and in the worst cases, targeted audits by Statistics Denmark (Danmarks Statistik) or the Danish Tax Agency (Skattestyrelsen).
This article explains the most common Intrastat mistakes in Denmark, why they occur, and how to prevent them with practical, step‑by‑step improvements to your internal processes.
Misunderstanding When Intrastat Is Required
One of the primary sources of error is simply not knowing when Intrastat declarations are required. Many businesses assume that filing EU sales lists (EC Sales Lists / EU‑salg uden moms) or VAT returns is enough. It is not. Intrastat is a separate statistical report, with its own thresholds and its own rules.
In Denmark, Intrastat obligations are triggered when the value of your arrivals (imports from other EU countries) or dispatches (exports to other EU countries) exceeds the annual thresholds set by Danmarks Statistik. These thresholds are adjusted from time to time and differ for arrivals and dispatches. A typical pattern is that a company's trade grows slowly, pushing it over the threshold in the middle of the year, but the finance team continues to believe they are “too small” for Intrastat.
An additional complication is that thresholds apply per Danish VAT number. Groups with several Danish entities or branches sometimes add up figures group‑wide instead of per entity, which may lead some entities to under‑report and others to file Intrastat when they are not actually required to.
To avoid this, companies should implement an annual and mid‑year threshold check as part of their compliance calendar. This can be a simple comparison of cumulative EU purchases and sales of goods against the latest thresholds published by Danmarks Statistik. The key is that this check must be systematic rather than ad hoc.
Confusing Trade in Goods with Trade in Services
Another frequent mistake is including services in Intrastat declarations or, conversely, excluding goods because they are bundled with services. Intrastat in Denmark only covers physical movements of goods between Denmark and other EU member states. Pure services, such as consulting, software licences without a physical medium, or online subscriptions, are not reported in Intrastat.
Problems typically arise in scenarios where goods and services are billed on the same invoice. For example, a Danish company may purchase machinery from Germany with an installation service included. If the accounting system posts the total invoice under a single services account, the goods component can be overlooked for Intrastat purposes. On the other hand, some companies mistakenly declare the full invoice value, thereby including non‑reportable service elements.
The solution is to introduce a clear internal rule: whenever an invoice involves cross‑border EU trade, the finance or logistics team must separate goods and services at line level. That separation should be reflected in the ERP or accounting system, enabling accurate extraction of Intrastat‑relevant data. In practice, this may require close cooperation between procurement, logistics, and finance to define how mixed invoices are coded.
Using Wrong Commodity Codes (HS / CN Codes)
Incorrect classification of goods using the Combined Nomenclature (CN) is one of the most common and time‑consuming Intrastat errors in Denmark. Statistics Denmark uses CN codes to measure trade by product category, and misclassification distorts this data. For businesses, it also creates risk: during audits, authorities often focus on commodity codes to verify that declarations are consistent with the nature of the business.
Misclassification usually stems from three issues. First, companies may reuse old codes from previous products that are not fully comparable. Second, they may rely on supplier descriptions rather than applying the official classification rules. Third, they may fail to update codes when EU customs nomenclature changes, which happens annually.
From a practical perspective, relying on a single person's intuition or on informal spreadsheets tends to be risky. A more robust approach involves establishing a classification procedure:
1. Identify the main product groups traded across borders.
2. For each product, gather technical data, materials, and intended use.
3. Use the Danish customs tariff tool (Taric) or EU CN explanatory notes to identify candidate codes.
4. Document the reasoning behind the chosen code and store it centrally.5. Review and refresh the code list at least once a year, and whenever new products are introduced.
The advantage of this systematic method is that it reduces random code selection and makes it easier to justify your choices if questioned. The disadvantage is that it requires initial time investment and occasional external advice for complex products. Compared with a quick, ad hoc approach, the structured method clearly wins on accuracy and long‑term efficiency.
Incorrect Valuation and Reporting of Invoice Values
Another frequent error concerns the values reported in Intrastat. Companies in Denmark often use either the wrong currency conversion or the wrong basis (e.g. including VAT or excluding freight when it should be included). Intrastat requires reporting of the statistical value or invoice value of the goods, typically excluding VAT but including charges directly linked to the goods up to the Danish border (for arrivals) or up to the border of the partner EU member state (for dispatches), depending on the specific instructions in force.
Several pitfalls appear in practice. When invoices are issued in foreign currencies, some companies use the booking date rate instead of the invoice date rate, or vice versa, without any documented policy. Others use internal transfer prices that do not match commercial invoices. These inconsistencies cause discrepancies between VAT statistics and Intrastat figures that can trigger inquiries.
To minimise this risk, businesses should create a short written policy on valuation for Intrastat that covers three points: which exchange rate source is used (for example, National Bank of Denmark rates), which date is applied, and how freight and insurance are treated. This policy should ideally mirror the guidance from Danmarks Statistik and be embedded in the ERP system as much as possible, reducing manual calculation.
Misreporting the Country of Origin and Country Codes
The country of origin is often misunderstood in Denmark's Intrastat reports. Some businesses assume that the country from which the goods were shipped is automatically the country of origin. In reality, origin refers to where the goods were manufactured or substantially transformed, which may be outside the EU.
As a result, a company might receive goods shipped from a warehouse in Sweden but produced in China. If they report Sweden as the country of origin, the Intrastat statistics become inaccurate. Similarly, incorrect use of country codes (such as confusing GB and XI or misreporting territories) is a recurring error, especially for companies with complex supply chains.
The solution is to integrate origin data from customs and logistics documentation into the Intrastat process. Step‑by‑step, that usually looks like this:
1. Collect origin information from suppliers (via long‑term supplier declarations or certificates).
2. Store the origin at product or batch level in your ERP or product master data.
3. Ensure the Intrastat extract uses this origin field rather than the shipping location.
4. Train staff to distinguish clearly between country of origin, country of consignment, and country of destination.While this may seem demanding, especially for SMEs, the advantage is not limited to Intrastat. Correct origin data also supports customs compliance, free trade agreements, and customer declarations.
Omitting Triangular and Chain Transactions
Complex EU trade structures, such as triangular transactions or chain sales, often lead to Intrastat under‑reporting. For example, a Danish company may sell goods from its warehouse in Germany directly to a customer in France, with the invoice issued from Denmark. Or goods may move directly from a supplier in Italy to a Danish customer, invoiced through an intermediary in Denmark that never physically handles the stock.
The challenge lies in the basic Intrastat principle: it tracks the physical movement of goods, not merely invoicing flows. If your Danish VAT‑registered entity is responsible for the movement of goods into or out of Denmark, Intrastat may be required even if the invoice chain tells a different story.
Because of this, finance departments that only see invoices but not logistics information may overlook transactions where goods never enter Denmark, or they might incorrectly report flows that are merely invoiced from Denmark but do not involve Danish territory at all.
To address this, businesses should compare logistics flows (e.g. from warehouse management systems, carrier data, or dispatch notes) with financial flows. An internal map of “typical trade scenarios” with Intrastat rules for each type of transaction can be extremely helpful. The main advantage of this detailed mapping is a clear, repeatable approach to complex cases. The drawback is that it requires close cooperation between operations and finance, which some organisations initially find challenging.
Late or Missing Filing of Declarations
Even when data is correct, late or missing Intrastat declarations are a chronic issue in Denmark. Monthly deadlines are close to VAT filing dates, and teams under time pressure often prioritise tax returns over statistical reports. Because Intrastat is “only statistics,” some businesses wrongly believe it is less important.
In reality, ongoing non‑compliance can lead to reminders, fines, and increased scrutiny. Danmarks Statistik and Skattestyrelsen can cross‑check VAT data and Intrastat flows, significant discrepancies or repeated late submissions may trigger questions or targeted control.
Preventing late filings is largely a question of organisation. Intrastat should have a fixed place in the monthly closing process, with clear responsibility assigned to a named role, not just a department. Using a compliance calendar with internal deadlines a few days before the official ones, combined with simple checklists, can significantly reduce delays.
The main advantage of this structured approach is predictability and reduced stress around deadlines. The main disadvantage is that it requires discipline in months when resources are tight. However, compared with the cost of handling corrections and dealing with official reminders, most companies find that a disciplined routine ultimately saves time.
Inconsistent Data Between VAT, EC Sales Lists, and Intrastat
Danish authorities increasingly use data matching tools. If your Intrastat dispatches to the EU show DKK 50 million in goods while your VAT returns and EC sales lists indicate much lower or higher amounts of intra‑Community supplies, this inconsistency is an obvious red flag.
Differences may arise for legitimate reasons, such as different timing of recognition or inclusion of services in the VAT figures that are not reported in Intrastat. However, many discrepancies stem solely from poor data extraction or incomplete Intrastat coverage.
A practical way to manage this risk is to perform a monthly reconciliation between key Intrastat totals and corresponding VAT and EC Sales List figures. This does not need to match down to every krone, but large deviations should be understood and documented. For example, if a high‑value service contract is included in VAT but not in Intrastat, a short note explaining why can be kept with the period documentation. This approach helps during audits and internal reviews alike.
Over‑Reliance on Manual Processes
Despite modern ERP systems, many Danish companies still prepare Intrastat declarations largely by hand, using spreadsheets exported from accounting or logistics systems. While this can work for businesses with very low volumes, the risk of error grows rapidly as the number of transactions increases.
Manual sorting, copying, and retyping of data invite mistakes in commodity codes, values, quantities, and country codes. Furthermore, there is usually little transparency or documentation of how the spreadsheet is structured, making it vulnerable to staff changes or accidental formula changes.
The alternative is to automate as much of the process as reasonably possible. This does not always mean expensive software. Often, it simply involves more intelligent use of the existing ERP:
- Ensure Intrastat‑relevant fields (commodity code, origin, net mass, supplementary units) are stored at item level.
- Configure standard Intrastat or statistical reports, if the system supports them.
- Limit manual intervention to review and handling of exceptions rather than the entire dataset.
The advantage of automation is a substantial reduction in repetitive work and fewer errors. The potential disadvantage is the initial setup effort and the risk that incorrect master data propagates across many declarations. This is why process design should always include strong controls on master data quality.
Building a Robust Intrastat Compliance Framework in Denmark
Avoiding common Intrastat mistakes in Denmark is less about mastering obscure rules and more about creating coherent processes that align logistics, finance, and master data management. Companies that treat Intrastat as an afterthought tend to face recurring corrections, inconsistent figures, and occasional fines. Those that embed Intrastat into their monthly routines, invest modestly in classification and automation, and conduct periodic reconciliations typically experience fewer issues and less administrative burden.
For most businesses, a practical path forward includes a few key steps: confirm whether thresholds are exceeded, map logistics and invoicing flows, clean up commodity codes and origin data, formalise a short valuation policy and set up regular reconciliations against VAT and EC sales lists. While each step requires effort, the long‑term benefits include smoother audits, better data for management decisions, and reduced compliance risk.
Where trade volumes or product portfolios are particularly complex, consulting with specialists or directly with Danmarks Statistik can be a sensible investment. Comparing this approach with a purely internal, improvised method, the external‑advice route offers better assurance and faster resolution of grey areas, albeit at a cost. For many companies, a hybrid solution-internal process ownership supported by periodic external reviews-delivers the best balance of control, cost, and peace of mind.
FAQ
1. Do small Danish companies need to submit Intrastat reports?
Only if they exceed the annual Intrastat thresholds for arrivals or dispatches set by Danmarks Statistik. However, even smaller companies should monitor their EU trade volumes at least annually to ensure they do not unintentionally cross the threshold without noticing.
2. Are goods sent for repair or return included in Intrastat?
Movements of goods for repair, return, or processing can be reportable, but the rules differ depending on the specific scenario. In some cases, only the value of the goods is reported. In others, certain flows may be excluded. Each situation should be checked against the current Danish Intrastat guidance rather than assuming it is automatically in or out.
3. Can Intrastat be filed by an external accountant or service provider?
Yes, Danish businesses can authorise an external adviser to prepare and submit Intrastat declarations on their behalf. However, the legal responsibility remains with the company holding the Danish VAT number, so internal controls and data quality remain crucial even when reporting is outsourced.
4. How long should Intrastat documentation be kept in Denmark?
As a general rule, supporting documentation such as extracts, working files, and classification records should be retained for at least the same period as VAT and accounting records, so that you can substantiate your figures during any later review or audit.