Detect risks in customs declarations for compliance with import and export ban of Mercury Regulation

Customs

This algorithm helps Customs to select goods for control based on risks. Among other things, it uses declaration data from companies and assesses whether or not there are increased risks of exporting and importing substances listed in the Mercury Regulation in customs declarations.

Last change on 2nd of April 2025, at 12:33 (CET) | Publication Standard 1.0

• Publication category: Impactful algorithms
• Impact assessment: Field not filled in.
• Status: In use

General information

Theme

Public Order and Safety

Begin date

05-2013

Contact information

[e-mail]

Responsible use

Goal and impact

The purpose of this algorithm is to more efficiently select which declarations are potentially risk-sensitive in the context of enforcement of the Mercury Regulation. Strict conditions apply to the import, and export of substances containing mercury, due to (inter)national agreements. Those conditions relate to the movement of goods between the European Union (EU) and third countries. This algorithm focuses on the import and export of substances mentioned in the Mercury Regulation. It indicates in which declarations which regime applies to the specific substance. Customs checks companies based on the results of this algorithm.

Considerations

Customs processes 700 million declarations every year, including in the field of mercury-containing substances. This algorithm (risk profiles) allows Customs to assess declarations more efficiently and faster. Thus, declarations are approved or checked faster. And goods are released faster. The algorithm also ensures that 'known and reliable' companies are actually checked less.

Human intervention

If a declaration yields a match with a risk profile, a customs officer reviews the declaration. And asks for more information if necessary. The decision to approve a declaration, or to start checking it, is taken by a human being.

Risk management

A second customs officer always checks the risk profile before use. This is the 4-eye principle. And once the profile is in use, a weekly check is made for a profile to see how many declarations produce a match. If necessary, the profile can be adjusted. Periodically, Customs checks per profile whether it is still necessary to refine, extend or terminate it. Customs monitors internal and external complaints and incidents, for example if a profile is insufficiently specific and therefore designates too many declarations as higher risk.

Legal basis

Legal basis for Mercury Ordinance controls is in the Union Customs Code (DWU), the General Customs Act and the Environmental Management Act. These laws ensure that the export and transit of substances mentioned in the Mercury Ordinance goods is done properly. The use of risk profiles also relies on DWU section 46. That article says that customs controls should mainly rely on risk analysis by electronic data processing techniques.

Links to legal bases

• Douanewetboek van de Unie: https://wetten.overheid.nl/BWBR0003245
• Kwik Verordening: https://eur-lex.europa.eu/legal-content/NL/TXT/HTML/?uri=CELEX:32017R0852&from=EN#d1e40-1-1

Operations

Data

The algorithm can use any data from the goods declaration. For example, type of goods, commodity code, document code, weight, number of packages, consignee, declarant, consignor, country of consignment, EORI number, means of transport, etc.

Links to data sources

Gegevensvereisten douaneaangiften (zie Bijlage B Gedelegeerde Verordening Douanewetboek van de Unie + Bijlage VIa van de Algemene Douaneregeling): https://www.belastingdienst.nl/wps/wcm/connect/bldcontentnl/belastingdienst/douane_voor_bedrijven/naslagwerken_en_overige_informatie/andere_onderwerpen/gegevensvereisten/

Technical design

The algorithm consists of decision rules created in collaboration with content experts. These decision rules provide estimates of which declarations have a higher risk of exporting and importing mercury-containing substances. Decision rules are based on 'if-then-else' combinations. An example: if (if) the information we have on a shipment shows that the goods have an abnormal weight, (then) we manually check the declaration and the shipment may be selected for extended inspection. If the goods do not have an abnormal weight (else), then we do not stop the shipment. Or at least not based on this criterion.