Sanctions Screening: The IMO Number as Primary Key

Screen the vessel by its seven-digit IMO number first, then screen the four counterparties behind the port call: the owner or DOC holder, the technical manager, the commercial operator or charterer, and the paying party. That order matters because the IMO number is the only identifier that stays fixed while names, flags, managers and trading patterns change around it.

For ship chandlers, bunker suppliers, port agents and repair yards, sanctions compliance best practices come down to a repeatable procedure rather than a one-off check at quotation stage. A vessel that cleared screening last month can change technical manager this month, and the new manager may sit behind a different corporate structure entirely. The company behind the hull is what you are really screening.

Why the IMO number is the primary key

The IMO number is a permanent hull identifier issued under the IMO ship identification number scheme. It does not change when a vessel is renamed, reflagged or sold, which is exactly why it is the safest field to screen against. Name-based screening fails because vessel names are reused, transliterated inconsistently and changed for commercial reasons.

Screen the IMO number against the vessel-level entries on the relevant lists, then use it to pull the current registered owner, DOC holder and technical manager from your vessel database or AIS-derived record. Everything else in the screening file hangs off that number. If you only keep one field clean in your whole system, keep this one.

What to record at the vessel level

• IMO number, current name and previous names
• Flag state and any recent flag changes
• Registered owner and DOC holder as at the date of screening
• Technical manager and commercial operator
• Last port calls and the next declared port
• Date and time of the screening, plus the list versions used

Recording list versions matters. A screening that cannot be reproduced against the same list state is difficult to defend if a bank or insurer asks questions later. A dated export of the list you checked is worth more than a note saying the check was clean.

The four counterparties to screen on every port call

Every port call involves four distinct counterparties, and each one can carry its own sanctions exposure. Screening only the vessel, or only the party that signs your purchase order, leaves three gaps open. Each counterparty is a separate legal entity with its own registration number, address and ownership chain.

1. The owner or DOC holder

The Document of Compliance holder is the company ultimately responsible for the ship under the ISM Code. In many fleets the DOC holder differs from the registered owner, and it is the DOC holder that appears on safety management certificates and often on the enquiry itself. Screen it by legal entity name, registration number and registered address, not by trading name.

2. The technical manager

Technical managers handle maintenance, dry-docking, spares and much of the purchasing budget. A fleet can switch technical manager without changing owner or flag, so re-screen this party whenever the management agreement changes. This is the counterparty most often missed, because the enquiry email may come from a manager's shared inbox with no entity name in the signature. Technical management and purchasing are frequently the same desk, which is why the gap is easy to overlook.

3. The commercial operator or charterer

The charterer decides where the vessel trades and therefore which ports it calls. Time charterers and voyage charterers can be based in jurisdictions with different exposure profiles from the owner. Screen the chartering entity named on the fixture or in the agent's pre-arrival message, and record which of the two documents you relied on.

4. The paying party

Whoever settles the PDA, the bunker invoice or the repair yard account is a counterparty in its own right. Third-party payments, payments routed through an intermediary, and payments from an entity unrelated to the vessel are all patterns that warrant a closer look before you commit to supply. A paying party that appears nowhere else in the file is a prompt for questions, not a routine entry.

Which lists to check and how often

Screen against the lists that apply to your business, your bank and your insurers. For most maritime service providers that means the US OFAC sanctions lists including the SDN list, the UK sanctions regime administered by OFSI, and the EU consolidated list. Japanese METI end-user lists matter if you trade with Japanese-linked counterparties or banks.

Re-screen on a defined cadence and on defined triggers. A common practical baseline is:

1. At first enquiry, before you quote.
2. Before confirming supply or issuing a PDA estimate.
3. Before invoicing, if more than 30 days have passed since the last check.
4. Immediately on any change of owner, DOC holder, technical manager, charterer or flag.
5. Immediately when a new sanctions designation is announced that touches your trade lanes or counterparty jurisdictions.

Regional policy shifts create exactly this kind of trigger. Estonia, Latvia and Lithuania have called for an EU-wide ban on Russian grain transit, arguing that Moscow is redirecting agricultural exports through European transport networks as Black Sea disruption reshapes regional grain flows, according to Splash247 (October 2026). For a chandler or agent handling grain tonnage in the Baltic, that is a signal to re-check which operators are actually moving the cargo, not just which vessels are calling. The vessel may be unchanged while the chartering entity behind the cargo is not.

A worked example: one port call, end to end

Take a supramax bulk carrier of about 60,000 DWT with a declared ETA at a North European port in four days. The agent forwards a pre-arrival message and the chandler receives a provision enquiry from a shared inbox. The screening file below is built before any stock is committed or berth time reserved.

Step 1: identify the vessel

Confirm the IMO number from the pre-arrival message and match it against AIS data. Check previous names and recent flag history. If the vessel changed flag within the last twelve months, note it in the file. A recent flag change is not a finding on its own, but it is a reason to look harder at the entity chain.

Step 2: identify the DOC holder

Pull the current DOC holder from the vessel record. Screen the legal entity against your lists and record the result with the list version and timestamp. If the DOC holder has changed since your last call at this port, treat the file as new rather than updating the old one.

Step 3: identify the technical manager

Establish which company handles technical management and purchasing for this hull. If the enquiry came from a manager rather than the owner, screen that manager separately. This is the step where a name-only check most often fails, because manager names are frequently similar across unrelated groups. A near match here needs a documented resolution, not a verbal one.

Step 4: identify the charterer

Ask the agent or check the fixture details for the chartering entity. Grain and bulk trades in particular can involve traders based in jurisdictions that change the risk profile of the whole port call. Note whether the fixture is a time charter or a voyage charter, because the entity that controls the trading pattern differs between the two.

Step 5: identify the paying party

Confirm who will settle the PDA and the final invoice. If the paying entity is not the owner, DOC holder, manager or charterer you have already screened, screen it as a fifth entity before you commit stock or berth time. Payments from a party with no other role in the port call are the pattern that most often turns a routine supply into a problem account.

Step 6: decide, document and re-screen

Record the decision, the reasoning and the date. Set the next re-screen date based on your cadence and flag the file for immediate review if any counterparty changes before the vessel sails. The file should read as a short narrative a colleague could follow without asking you what happened.

Record-keeping that survives a bank review

Keep a screening file per port call, not per customer. A single file should show which entities were screened, against which lists, on which date, by whom, and what the outcome was. Store the list version or a dated export alongside the result.

Where a match or a near match appears, document the resolution. False positives from common names are normal; what matters is that the file shows how the near match was cleared, and who cleared it. A file that shows the reasoning is far stronger than one that simply states a clean result.

Keep the file for the period your bank, flag state or insurer requires, and make sure it can be produced quickly. Compliance failures are usually documentation failures rather than analytical ones. Teams rarely miss the obvious designation; they miss the proof that they looked.

Where screening fits in the sales workflow

Screening is not separate from business development. The same vessel data that tells you a ship is inbound also tells you who owns it, who manages it and who charters it. Building screening into the enquiry stage means compliance work and sales work share one dataset instead of running as two disconnected processes.

The operational reality is that trade lanes move quickly. Tanker attacks in the Middle East reached their highest levels since the war began in early October, according to shipbroker Gibson via Hellenic Shipping News (October 2026). When routes and operators shift that fast, counterparty structures shift with them, and a screening file that is three months old tells you very little about the vessel now heading for your berth.

That is the practical argument for keeping the screening record and the sales record in one place. If your re-screen trigger and your outreach trigger both fire off the same vessel movement, neither process depends on someone remembering to start it.

How VesselReach helps

VesselReach, built by CatalystIQ, turns vessel movements at your chosen ports into a structured view of exactly the counterparties this procedure requires. You select the ports you serve, and the platform detects vessels currently near those ports plus vessels scheduled or expected to arrive, so your screening and your sales conversation start from the same record before the ship docks.

Its AI company targeting uses a language model to determine which company associated with each vessel is the right one to approach, which means you see the ship management company, owner, operator, technical manager or charterer rather than a bare vessel name. Decision-maker discovery then identifies the relevant people, including operations, port operations, commercial, chartering, fleet, marine superintendents, procurement and C-suite contacts, so your compliance question and your commercial question reach the right desk.

Multichannel outreach runs by email, WhatsApp and phone in staged, personalised sequences, and AI enquiry handling answers incoming questions using approved, verified information, escalating to a human representative rather than guessing when it cannot answer reliably. Automated follow-ups continue across all three channels and stop when appropriate, including on opt-outs, and the Android and iOS apps let your representatives take escalations and connect to calls directly. Outreach respects recipient preferences, consent and applicable messaging regulations, and humans stay in control.

If your team is re-checking the same counterparties by hand across spreadsheets and inboxes, book a VesselReach demo and see the workflow on the ports you actually serve. A 10-day free trial is offered after the demo meeting.