Table of Contents
Sanctions screening in a TMS means checking every party on a shipment against government watchlists before that shipment moves. A transport management system already holds your shippers, consignees, carriers, and notify parties. That data is exactly what you need to screen. Doing the check inside the TMS keeps compliance close to the load, not stuck in a separate tool.
This guide explains how sanctions screening tms workflows actually run. You will see where screening fits in the booking process, which lists to check, how matches get reviewed, and what records to keep. It is written for freight forwarders, 3PLs, and shippers who want screening to work without slowing down operations.
What sanctions screening inside a TMS covers
A TMS tracks the movement of goods. It stores the names and addresses of the companies and people tied to each shipment. Sanctions screening takes those names and matches them against restricted party lists. If a name matches a listed party, the system flags it. You then review the flag before you let the shipment proceed.
This is a form of denied party screening applied to logistics data. The goal is simple. You must not ship to, from, or through a party the government has blocked. Screening inside the TMS makes that check part of daily work instead of a side task.
Which parties get screened
Do not screen only the buyer. A shipment involves many parties, and any one of them can be listed. Screen every entity tied to the load.
- Shipper and consignee
- Notify party and any intermediate consignee
- Carrier, trucker, and ocean or air line
- Freight forwarder and customs broker
- Bank or payer named on the transaction
- End user, when known
Freight forwarders carry extra exposure because they touch so many parties. Our guide on denied party screening for freight forwarders goes deeper on that role.
Which lists a TMS should screen against
A single list is not enough. Different agencies publish different lists, and they change often. Most screening tools pull from a merged feed to cover the main ones at once.
The U.S. government offers the Consolidated Screening List, which combines the key export and sanctions lists into one download. Good TMS screening connects to that feed or an equivalent commercial one. Learn more in our piece on the Consolidated Screening List.
| List | Agency | Why it matters for transport |
|---|---|---|
| SDN List | OFAC (Treasury) | Blocked persons and entities. No dealings allowed. |
| Entity List | BIS (Commerce) | Parties needing a license for many exports. |
| Denied Persons List | BIS (Commerce) | Parties barred from export privileges. |
| Unverified List | BIS (Commerce) | Parties BIS could not verify. Red flag. |
| Non-US lists | EU, UK, UN | Needed for cross-border and non-US legs. |
Lists update on no fixed schedule. A name added today can appear on a load you booked yesterday. So the feed inside your TMS must refresh often, ideally daily.
Where screening fits in the TMS workflow
The best moment to screen is early. Catch a problem before the truck is loaded, not after. A TMS gives you several natural checkpoints.
Screening at each stage
- When a new customer or partner is added to the address book
- When a booking or order is created and parties are entered
- When shipment details change, such as a new notify party
- On a schedule, to rescreen your whole database against new list entries
The first check happens during onboarding. See how that works in sanctions screening in customer onboarding. The last check matters most and gets missed most. Parties clean at booking can be listed later. Batch rescreening catches that.
| Checkpoint | Trigger | What it catches |
|---|---|---|
| Onboarding | New party record | Bad actors before any shipment |
| Booking | Order created | Listed party on this specific load |
| Edit | Party added or changed | Late substitutions |
| Batch rescreen | List update or schedule | Parties newly added to a list |
How the match works
Screening is not a plain text search. Listed names come with spelling variants, aliases, and translations. So the engine uses fuzzy matching. It scores how close a party name is to a listed name and flags anything above a set threshold.
A low threshold flags more names and creates more noise. A high threshold catches fewer names and risks a miss. You tune it to your risk. Most teams start strict, then adjust as they learn their traffic.
The 50 percent rule
A party does not have to be listed by name to be blocked. If listed parties own 50 percent or more of a company, that company is blocked too. Name matching alone will miss this. You need ownership data. Read our guide on the 50 percent rule in sanctions screening to see why.
Handling a hit
A flag is not a verdict. Many flags are false positives. A common name or a shared word can trigger a match with no real link to a listed party. Every hit needs a human review before you clear or block the shipment.
- Compare full name, address, and country, not just the name
- Check date of birth or ID numbers for individuals
- Look at the specific list and the reason for listing
- Record why you cleared or held the party
- Hold the shipment while a real match is checked
Steps for clearing a flag are covered in how to resolve a false positive. For the wider process, see how to process denied party screenings.
Automated screening versus manual checks
Small volumes can be screened by hand. Once you move many loads a day, manual checks break down. People skip steps under pressure. A listed party can slip through. Screening built into the TMS runs on every booking, every time.
Automation does not remove the human. It handles the volume and flags the risk. People still judge the hits. Our comparison of automated versus manual screening weighs the trade-offs.
Ways to connect screening to your TMS
Not every TMS ships with screening inside it. There are three common ways to close that gap. Pick the one that fits your volume and your tech.
- Native module. Screening is built into the TMS and runs on booking. Least friction, if your vendor offers it.
- API integration. The TMS sends party data to a screening service and gets results back in real time. Good for high volume.
- Manual lookup. You screen in a separate tool and paste the result into the shipment record. Fine at low volume, weak at scale.
Whichever route you choose, the screening result must attach to the shipment. A check that lives in a separate system, with no link back to the load, is hard to prove later. Aim to keep the result and the shipment together.
Records and audit trail
Screening is not done when the flag clears. You must prove you screened. Regulators can ask for evidence years later. A TMS should log every check and store it with the shipment.
- Who was screened and when
- Which lists and list version were used
- What the system returned
- Who reviewed a hit and what they decided
This creates an audit trail tied to each load. Keep it for the required period. See record keeping for denied party screening for how long and in what form.
Frequently Asked Questions
Does a TMS screen automatically or do I run it?
It depends on setup. Many systems screen at booking without a manual step. Good practice is to make screening a required gate. The order cannot advance until parties are checked.
How often should the lists refresh?
As often as possible. Lists change without notice. A daily refresh is a sensible floor. Pair it with batch rescreening so new entries catch existing parties.
What if my TMS has no screening built in?
You can connect a screening service through an integration or API. Party data flows out, results flow back. If neither exists, you screen in a separate tool and log the result against the shipment.
Do I still screen if I only move domestic freight?
Yes. Sanctions lists include domestic parties. A blocked person can sit inside your own country. Screening applies to the parties, not only the border crossed.
Key Takeaways
Sanctions screening in a TMS puts compliance where the shipment data already lives. Screen every party, not just the buyer. Use a merged list feed that refreshes often, and rescreen your database as lists change. Match with tuned fuzzy logic, review every hit by hand, and account for ownership under the 50 percent rule. Log each check so you can prove it later. Done well, screening runs quietly inside your booking flow and keeps blocked parties off your loads. If you want help setting this up, contact us or start with our denied party screening hub.