An SME exporting to the UK discovers after Brexit that its commercial invoices lack the proper preferential origin declaration. Result: goods blocked at Dover, client delay penalties, and a freight forwarder sending the storage bill. The information existed in the system — but scattered across three Excel files, an accounting software and the export manager’s memory.
This scenario illustrates a structural problem: when international trade relies on manual processes disconnected from the ERP, every import-export operation becomes a risk. Customs risk, tax risk, sanctions risk. The ERP doesn’t replace the freight forwarder or customs broker, but it becomes the central hub where all data necessary for compliance converges.
Why International Trade Complicates ERP Management
Multi-Currency, Multi-Language, Multi-Regulation: The Complexity Triangle
A mid-market French company selling in Germany, importing components from Turkey and delivering to a Swiss client simultaneously manages three currencies (EUR, TRY, CHF), three different VAT regimes and three distinct regulatory frameworks. Each combination creates specific obligations: intra-EU VAT for Germany, customs duties and EUR.1 certificate for Turkey, QR invoices and multi-rate VAT for Switzerland.
The ERP must carry this complexity without transferring it to operations staff. Practically, this means the product master contains the HS code, the sales order automatically calculates the applicable VAT regime, and the delivery note generates the required customs documents according to the destination country.
The Risks of Manual Management
Customs classification errors are costly. An incorrect HS (Harmonized System) code on a customs declaration triggers retroactive adjustment on all similar operations — not only on the controlled declaration. UK customs processed over 95% of declarations in under 5 minutes in 2024, according to HMRC statistics. This fluidity relies on automation — and operators who don’t connect to it become bottlenecks in the circuit.
Beyond customs, manual management exposes to three major risks:
- Tax penalties: intra-EU VAT errors (forgotten reverse charge, wrong regime)
- Regulatory sanctions: violation of export control rules (OFAC, EU, UN sanctions lists screening not performed)
- Commercial losses: clearance delays, storage surcharges, client contractual penalties
Essential ERP Features for International Operations
Multi-Currency Management and Exchange Rate Accounting
The ERP must distinguish three currency levels: transaction currency (invoice currency), functional currency (accounting entity currency) and reporting currency (group currency). IAS 21 standard imposes precise rules on rates to apply — closing rate for balance sheet, average rate for P&L.
A properly configured ERP automatically calculates unrealized exchange differences (revaluation of open balances at closing) and realized differences (at settlement). Without this automation, each monthly closing becomes a manual reconciliation exercise between treasury software and accounting.
Intra-EU VAT and Reverse Charge
Within the European Union, intra-EU supplies of goods are VAT-exempt in the departure country, provided the acquirer has a valid intra-EU VAT number and transport proof is established. The ERP must automate VIES verification (VAT Information Exchange System), apply the correct tax regime according to sender/recipient country combination, and generate DEB/Intrastat declarations.
Reverse charge — where the buyer declares and deducts VAT simultaneously — concerns intra-EU acquisitions and certain cross-border services. ERP configuration must handle these cases without manual intervention, as a reverse charge error systematically triggers adjustment during tax audits.
Customs Classification in Product Masters
Every product crossing an external EU border must be classified according to the Combined Nomenclature (CN), derived from the 6-digit Harmonized System (HS), extended to 8 digits at European level. The HS code determines the applicable customs duty rate, potential tariff quotas and commercial policy measures (anti-dumping, safeguards).
The ERP must store the HS code in the product master, verify its validity (nomenclatures are revised annually by the World Customs Organization), and automatically inject it into shipping documents and customs declarations. A product without a correct HS code means a rejected declaration on hold.
Automatic Duty Calculation and Origin Determination
The applicable customs duty depends on three variables: the product’s HS code, country of origin, and any applicable free trade agreement. The EU has signed preferential agreements with over 70 countries and territories. When an agreement applies, the duty rate can drop from 12% to 0% — provided preferential origin of the product is proven.
Origin determination is a technical exercise: you must verify that the product has undergone “substantial transformation” in the country of origin, according to specific rules of the relevant agreement (tariff classification change, added value criterion, specific manufacturing operation). An advanced ERP automates this calculation by cross-referencing product nomenclature with origin rules of each agreement.
Sanctions and Embargo Screening
Screening sanctioned parties is a legal obligation, not an option. Any European company must verify that its clients, suppliers and partners don’t appear on EU, OFAC (United States), UN Security Council sanctions lists, and other bodies depending on markets addressed.
The ERP must perform this check automatically when creating a third party and at each transaction. Lists are updated several times per month — a manual process cannot follow this pace. Failure to screen exposes the company to criminal sanctions and exclusion from international banking circuits.
Focus on EU Customs Obligations
Customs Declarations and National Systems
Each Member State operates its own electronic customs clearance system: DELTA IE (France), ATLAS (Germany), CDS — Customs Declaration Service (UK post-Brexit). The Single Administrative Document (SAD) remains the common base, but electronic formats and transmission processes vary.
The ERP doesn’t replace approved customs software, but it feeds necessary data: CN codes, customs value, origin, Incoterms, net and gross weights. The more reliable and structured this upstream data, the faster clearance. Connected operators see their goods released in minutes; others wait hours, even days.
Preferential Origin and Free Trade Agreements
The EU maintains a network of free trade agreements (FTAs) covering a significant portion of its external trade. To benefit from preferential rates, the exporter must provide proof of origin: EUR.1 certificate (issued by customs), origin declaration on invoice (for REX — Registered Exporter registered exporters), or origin statement under the EU-UK agreement (TCA).
The REX system, gradually replacing old mechanisms, allows registered exporters to self-certify the origin of their products. The ERP must manage the REX supplier register, calculate origin cumulation when components come from several partner countries, and automatically generate required origin mentions on commercial documents.
CBAM: Carbon Border Tax
The Carbon Border Adjustment Mechanism (CBAM) entered its definitive phase on January 1, 2026, after a transitional phase started in October 2023. It covers six sectors: cement, iron and steel, aluminum, fertilizers, electricity and hydrogen (European Commission, CBAM).
Practically, any EU importer exceeding 50 tonnes of CBAM goods per year must have a CBAM account number, declare embedded emissions in imported products, and purchase CBAM certificates from February 2027 to cover 2026 emissions. The EU plans to extend scope to other steel and aluminum derivative products from 2028.
For the ERP, CBAM adds a new data field to trace per imported article: embedded CO₂ emissions, communicated by the supplier. It’s a traceability exercise added to existing customs classification.
Post-Brexit: UK-EU Origin Rules
The EU-UK Trade and Cooperation Agreement (TCA) grants duty-free and quota-free access to goods originating from both parties. But proof of origin is demanding: origin statement on invoice, justification kept for four years minimum, and a posteriori checks by customs.
For companies with regular UK-EU flows, the ERP must manage export declarations (absent before Brexit for intra-EU trade), origin proofs according to TCA specific rules, and import VAT on the British side. Companies exporting to the UK who haven’t adapted their ERP suffer recurring delays and documentary surcharges.
What Leading ERP Systems Offer
SAP S/4HANA — Global Trade Services (GTS) Integrated
SAP GTS is the market’s most comprehensive module for international trade management. It covers customs classification, sanctions screening (Sanctioned Party List), export control, license and permit management, and electronic customs declaration preparation. Native integration with SD (sales), MM (purchasing) and TM (transport) modules enables seamless flow from order to declaration.
The downside: SAP GTS is sized for significant volumes and structured organizations. License and implementation costs reserve it for mid-market companies and large groups. An 80-person SME has neither the budget nor internal resources to exploit GTS at full capacity.
Oracle Cloud — Global Trade Management
Oracle GTM covers tariff management, product classification, landed cost simulation, preferential agreement qualification, and customs document automation. The compliance rules engine allows defining commercial policies by country, product and partner.
Oracle GTM integrates into the Oracle Cloud SCM ecosystem, making it natural for companies already on Oracle. For others, entry cost and integration complexity are barriers.
Microsoft Dynamics 365 — Intrastat Connectors and Partner Solutions
Dynamics 365 Finance and Supply Chain Management natively integrates Intrastat management and intra-EU trade declarations. For extra-EU trade, Microsoft relies on partner solutions: Descartes (formerly Amber Road) for sanctions screening and customs classification, or specialized vendors like Integration Point.
This modular approach has the advantage of flexibility: an SME can start with the native Intrastat base and add external trade compliance building blocks when export volumes justify the investment.
Odoo — Community Modules and Connectors
Odoo manages multi-currency natively and offers community modules for Intrastat declarations. For advanced customs compliance (sanctions screening, HS codes, preferential origin), you need third-party modules or connectors to specialized platforms.
It’s the most accessible solution for an SME starting international operations: the ERP core handles fundamentals (multi-currency, intra-EU VAT), and compliance building blocks are added progressively. The absence of native GTS-like module is a limitation for complex operations.
Sage X3 — Native Multi-Legislation Management
Sage X3 is designed for multi-legislation environments: multi-company, multi-currency, multi-chart of accounts management in a single instance. Localization natively covers France, Germany, Spain, Portugal and the United Kingdom. For Intrastat declarations and customs compliance, Sage X3 relies on integrated modules and partner connectors.
Its strength for international operations: the ability to consolidate several legal entities in different countries, with local charts of accounts and unified group reporting. It’s a relevant choice for multi-country industrial mid-market companies who don’t want SAP or Oracle entry ticket.
Deployment Strategy for Exporting SME
Identify Import-Export Flows to Integrate First
Not all international operations justify the same level of ERP integration. Priority goes to recurring and high-volume flows: regular exports to the same country, raw material imports with significant customs duties, intra-EU operations subject to Intrastat declaration.
One-off or low-amount operations can remain manually managed initially. The objective is to automate first the 20% of flows that represent 80% of compliance risk.
Connect ERP to National Customs System
Direct connection between ERP and national customs system (DELTA IE in France, ATLAS in Germany, CDS in the UK) accelerates clearance and reduces re-entry errors. This connection usually goes through an intermediary: approved customs clearance software (Conex, Customs Bridge, AEB) that receives structured data from ERP and transmits it in the format required by administration.
Authorized Economic Operator (AEO) status significantly simplifies formalities. France counts approximately 1,600 AEO-certified companies, Germany lists over 6,000. AEO status offers concrete advantages: reduced physical controls, access to simplified clearance procedures, and mutual recognition with equivalent programs of partner countries.
Train Export and Logistics Teams
The tool is only as good as teams using it correctly. Training must cover three axes: product master configuration (HS codes, origin, applicable regulations), export order processes (required documents, VAT regimes, Incoterms), and compliance alerts reading (sanctions screening, export control).
A realistic training plan provides two to three days for export and logistics key users, with quarterly reminder sessions as regulations evolve.
Monitor Export KPIs
Four indicators allow steering international trade performance in ERP:
- Rejected declarations rate: percentage of customs declarations returned for error. Target: less than 2%
- Average customs lead time: time between declaration submission and release. Target: less than 30 minutes for AEO operators
- Landed cost variances: difference between estimated delivered cost and actual cost (duties, freight, insurance). Target: less than 5%
- Unresolved compliance alerts: number of sanctions screenings pending processing. Target: zero at D+1
These KPIs must be integrated into the ERP dashboard, not in separate reporting. A supply chain director who must juggle between three tools to have a complete view of international operations doesn’t have a tool — they have a problem.
To explore related issues, consult our guide on multi-site and multi-entity ERP management, our analysis of ERP and supply chain (WMS, TMS, demand planning), and our report on mandatory electronic invoicing in Europe.
To validate an adoption hypothesis on the international trade perimeter, start with a 3-month POC targeted on a recurring export flow (the country representing your largest volume). Typical budget: €15-30K. Result: Go/No-Go decision with real clearance data, not a PowerPoint mockup.
