Sanctions screening Export control & customs classification Custom or off-the-shelf

Custom trade compliance software development

If you import and export goods, you need to be able to show, for every counterparty and every shipment, that checks were carried out: against the consolidated EU sanctions list, against the dual-use rules and against the commodity code under which the declaration is filed. The hard part is rarely the rule itself, but the judgement behind it and the file that remains afterwards. Appfront builds software that supports and records that judgement, within your own order and shipping process.

What trade compliance covers, and who it is for

Trade compliance is the full set of checks around a cross-border flow of goods: are you allowed to supply this party, is the product subject to export control, under which commodity code does it enter the declaration, and is a licence needed that still has headroom. These questions touch sales, the warehouse, shipping and the customs department at the same time, and so they often run outside the system: in a spreadsheet, an email thread and the memory of one experienced employee.

We build this type of software for wholesalers, manufacturers and machine builders, for electronics and chemicals companies and for logistics service providers. What they have in common is that the check needs to sit inside the order process, not alongside it.

Is this the right page for you? If you screen counterparties because the Wwft (the Dutch anti-money laundering act) obliges you to carry out customer due diligence, that is KYC and AML, and you are better off reading KYC and AML compliance software. The matching technique is related, but the trigger and the supervisor are not. If your question is about setting up processing activities and the record of processing, it belongs with a GDPR compliance platform. This page is about goods that cross the border.

Sanctions screening is, at its core, a name-matching problem

The consolidated list of persons, groups and entities against which the EU has imposed financial sanctions is published by the European Commission and contains several name variants per entry. That is a necessity: names from Cyrillic, Arabic or Chinese have no single correct Latin spelling. The same person appears as Aleksandr, Alexander and Aleksander, with or without a patronymic. Companies are listed under their registered name while you know them by a trading name, or you do business with a subsidiary that is not itself listed.

That is where the real difficulty lies. Set the matching tight and a transposed letter or a missing second given name slips through unseen. Set it loose and an ordinary Dutch surname collides with a listing, so your team gets hits every day that almost all mean nothing. Both problems never disappear at the same time; you choose a position on that scale and must be able to explain it.

When it comes to ownership and control, name matching stops working altogether. A counterparty that is not listed itself still falls under the asset freeze if 50% or more of it is held by listed parties, added up across several interests, and control can exist even below that threshold. That is not a question for a list but for a shareholder structure; the EU Sanctions Helpdesk helps SMEs with this free of charge.

Every hit that is not cleared automatically ends up with a person, and that decision must be recorded. Without a record, a hit that was rightly released cannot be told apart from a hit that was missed.

  • List version and reference date of the screening
  • The rule and score that produced the hit
  • Fields compared: name, address, date of birth, country
  • Name, role and timestamp of the reviewer
  • The rationale for the release or block
  • When an exception expires

When you screen determines who is affected

Screening is not a one-off action, and where it sits in the process determines what happens when something comes up. All four moments below occur, usually in combination. The choice is about where you accept the delay.

1
When creating the relationship

The screening is separate from operations, so a hit costs no order lead time. The only drawback is that the assessment goes stale immediately and says nothing about the shipment that goes out later.

2
At order acceptance

There is still room to manoeuvre here: a hit means a delayed order confirmation, not a halt in the warehouse. The price is a reviewer who is available whenever orders come in, including outside office hours.

3
Just before shipment

The most current check, and the only one that takes the actual delivery address and the final recipient into account. The bill comes immediately: a hit stops a picked shipment and creates pressure to release it quickly.

4
Periodic re-screening

Lists are updated, so a relationship that was clean last month can be hit today. Re-checking your entire customer base is a process of its own, with its own work queue.

A commodity code is a judgement, not a lookup

The basis is the World Customs Organization's Harmonized System: six digits that apply worldwide. The EU adds two more digits to make the eight-digit CN code of the Combined Nomenclature for exports, and another two to make the ten-digit TARIC code for imports. That code drives import duty, anti-dumping duties, bans and licence requirements; one subdivision of difference changes what you pay and what you are allowed to do.

Yet the right code is rarely obvious. The same product falls under a different heading depending on composition, degree of processing or the form in which it is presented: a mixture follows the component that gives it its essential character, and a part is classified differently when it is part of a machine than when it is separate. That is a classification judgement based on the classification rules and case law, not a search in a table. Software records that judgement and makes it reusable; a binding tariff information decision from Customs, valid for three years, belongs in the same item file.

Export control is a second, separate classification. A product can have an ordinary CN code and still fall under Annex I of Regulation (EU) 2021/821, the dual-use regulation covering goods, software and technology with both civil and military applications. Article 4 also provides a catch-all: even a product not listed becomes subject to licensing as soon as you know the end use is problematic. You apply for licences for strategic goods at the Central Import and Export Office (CDIU) of Dutch Customs.

On top of that come measures per commodity code: the list of common high priority items flags HS codes with an elevated risk of diversion to Russia, and Article 12g of Regulation 833/2014 requires exporters, for certain annexes, to include a contractual ban on re-exporting there. Both belong in the system: as a risk signal at item level and as a condition on the order.

What such a system needs to do in your process

Screening and classification are half the work. The other half is handling what comes out of them, and preventing the surrounding operation from grinding to a halt.

Blocking at the right level

A hit on one order line should not freeze the entire order, and a blocked relation should not still get supplied through a second customer number.

Licences that travel with the order

An export licence has a term, destination, end user and quantity. With partial deliveries, usage is deducted per shipment, so you can see when the remaining allowance is running out.

Rescreening as its own workflow

When a list version you use changes, only the difference is run against your relation base, with the results going into a separate queue. Otherwise rescreening drowns in the order flow.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

When custom is not the answer

To start with: nobody rebuilds the sanctions data. The EU, US and national lists, the name variants, the daily changes and the ownership and control data are something you buy from a specialist provider. That stays the case even if the software around it is custom.

For common situations there are also mature packages that combine screening, classification, licence management and customs documentation, with data feeds and regulatory updates included in the subscription. With a manageable portfolio, fixed destinations and an ERP for which such a package offers an integration, that is almost always the wiser route. Factor in what you take on with a self-build: if a regulation or list format changes, that maintenance is yours.

Custom software pays for itself in two cases. The first is deep integration: the check has to intervene in the middle of your order and shipping process, with blocks at line level, release by a specific role and an integration that genuinely stops picking. The second is a portfolio with unusual classification and licensing questions, such as configurable machines whose code differs per configuration.

Often the answer is not one or the other either: a package for the screening engine and the data, custom software for the layer that ties it to your process. If you are a financial entity with questions about ICT risk management and incident reporting, see DORA compliance software.

  • Blocking has to happen at order line level, not customer level
  • Classification differs per product configuration or specification
  • Your ERP or WMS has no existing package integration
  • Licence usage has to follow partial deliveries
  • Multiple entities with different export regimes
  • A supplier won't put a critical requirement on the roadmap

What the system connects to

A trade compliance system holds little data of its own. It lives off the item master and orders from your ERP, the shipment data from the warehouse, a sanctions data feed and the nomenclature. On the outgoing side, it supplies the code, the licence number and the status to the software you use to file declarations in the Dutch Customs Management System. Recommendation (EU) 2019/1318 from the European Commission provides a useful framework for the set-up around it, with transaction screening, record-keeping and internal control as separate core elements.

ERP: item and order master data WMS and shipping process Sanctions data feed from a data provider Consolidated EU sanctions list CN and TARIC nomenclature Declaration software for the Customs Management System EORI and licence registration REST APIs and webhooks Role-based authorisation Immutable audit logging

Frequently asked questions about trade compliance software

No, and you shouldn't want us to. The consolidated EU sanctions list, the national and US lists and the ownership and control data come from specialist data providers. We build the layer around them: ingesting the feed, version control on the list, the reference date for each screening, and re-screening whenever a list version that was used changes.

There is no right number. Every matching threshold is a trade-off between hits you miss and hits someone has to clear, and you must be able to justify that choice. What you can do is make the threshold configurable per list and per field, run any change against historical data first, and keep releases revocable as soon as the listing changes.

Often you should. Mature packages exist that combine screening, classification, licence management and customs documentation, including data feeds and regulatory updates. With a manageable portfolio, fixed destinations and an ERP that has an integration with such a package, that is the wiser route. Custom development pays off when the control needs to reach deep into your order and shipping process, or when your products raise classification questions the package doesn't cover.

In essence, that you had a process and that you followed it. For each assessed hit: the list version and reference date, the data compared, the reviewer, and the rationale for clearing or blocking. For each shipment: the commodity code with the grounds for that classification and, where applicable, the licence number with the volume drawn down.

The source code belongs to the client and sits in a repository on your own account. We work with mainstream languages, databases and API conventions, and document the data model and screening logic in readable documentation. The sanctions data remains with your data provider and runs through your own subscription.

No. The system prepares and records: it retrieves the right list version, shows which fields match and stores earlier decisions about the same counterparty. Whether a hit concerns the right party, and whether a product falls under a particular commodity code or under Annex I of the dual-use regulation, remains a human judgement. Responsibility for declarations and exports stays with the exporter.

Related services

If you are screening clients rather than goods flows, because the Wwft (the Dutch anti-money laundering act) obliges you to carry out customer due diligence and transaction monitoring, KYC and AML compliance software is the right page for you.

If you are a financial entity with questions about ICT risk management, resilience testing and incident reporting, see DORA compliance software.

If it is about the processing of personal data itself, with a record of processing activities, retention periods and data subject requests, that belongs with a GDPR compliance platform.

If you want to screen your counterparties against sanctions lists on an ongoing basis, take a look at our sanctions list screening tool.

If you want to track how many CBAM goods you import each year, take a look at our tonnage monitor for CBAM goods.

Want your trade compliance built into your systems?

Tell us how your order process runs, where screening currently takes place and which part of your portfolio raises the hardest classification and licensing questions. We'll look at whether an existing package is enough or whether a custom layer around your process is the better investment.

Edit content