OFAC Screening for Freight Forwarders, Carriers, and Logistics Companies: Who to Screen and When

Yes, Freight Forwarders and Carriers Need OFAC Screening

If you arrange, book, or move international cargo, OFAC's rules apply even though you never own the goods. Sanctions liability does not turn on who holds title, it turns on who facilitated the transaction. A forwarder who books a container, a carrier who issues a bill of lading, or an NVOCC who consolidates freight can all be found to have "facilitated" a prohibited shipment, and facilitation is treated the same as doing the deal directly. This is not just an ocean-freight problem: motor carriers and trucking companies are U.S. persons too, so a trucker or drayage operator has to screen the customers it hauls for and the parties named on its loads, even on domestic moves.

OFAC enforcement is also strict liability: intent is not a defense. It does not matter that you did not know the consignee was a front company, or that your customs broker filled in the paperwork. In September 2025, OFAC settled with Fracht FWO Inc., a Houston-based freight forwarder, for over $1.6 million over apparent violations tied to Venezuela and Iran sanctions, a reminder that forwarders show up in enforcement actions as often as the exporters and buyers whose shipments they arrange. "We don't own the cargo" is not a compliance program. Every party touching a shipment, and its routing, needs to be checked before it moves.

Who to Screen on Every International Shipment

On a bill of lading, screen the shipper, the consignee, and the notify party, not just one of them. At a minimum, screen each of these before the shipment moves:

• Shipper (exporter of record). Screen the legal entity name exactly as it appears on the commercial invoice, not just the account name in your system.
• Consignee. The highest-risk field on the bill of lading, since consignees are where sanctioned end users most often show up.
• Notify party. Frequently overlooked because it "isn't a party to the sale," but a notify party with no other connection to the transaction is a classic diversion red flag. OFAC does not exempt it from screening.
• Ultimate end user. Where the letter of credit or shipping instructions name a different end user than the consignee, screen that party too; the consignee is sometimes just a logistics intermediary.
• Banks on the transaction. Issuing and confirming banks on letters of credit, and any bank named in payment instructions. A sanctioned bank in the payment chain is a red flag independent of the cargo.
• The vessel or aircraft itself. Designated on OFAC's lists by name and IMO number, not just by owner. See the next section.

Names on shipping documents are frequently misspelled, abbreviated, or transliterated differently than how a sanctioned entity appears on a list, and the same company can appear three different ways across the invoice, bill of lading, and letter of credit. A tool built for exact-match-only names misses those variants, so fuzzy matching matters as much as which lists you check.

Vessels and Aircraft Are Sanctioned Parties Too

OFAC does not only designate people and companies, it designates specific ships and aircraft, listed by name and, critically, by IMO number. Screen on the IMO number, not the vessel name alone: sanctioned vessels change names and flags specifically to shed a bad reputation, but a tanker renamed and re-flagged last month is still the same hull carrying the same IMO number that OFAC's designation is tied to. If you charter vessels, screen by IMO number at the time of charter and again before loading.

Treasury's guidance to the maritime industry flags several patterns worth building into routine vessel review:

• Flag-hopping. Frequent changes of flag registry, especially to flags with weak oversight, without a commercial reason.
• AIS manipulation or "spoofing." A vessel disabling its Automatic Identification System transponder or broadcasting a false position to hide a port call or ship-to-ship transfer.
• Ship-to-ship transfers in unusual locations. Routine in legitimate shipping, but ones conducted far from normal transfer zones with AIS dark are a documented method for disguising cargo origin.
• Vessel history. A ship with recent port calls in heavily sanctioned jurisdictions, even under a different name, carries that history forward.

Sanctioned-Destination Traps: Transshipment and Diversion

Direct shipments to Iran, North Korea, Syria, Cuba, and Russia's sanctioned sectors are the obvious case. The harder case, and the one that actually catches forwarders, is transshipment: goods routed through Turkey, the UAE, or Central Asian hubs like Kazakhstan and Kyrgyzstan on their way to Russia, or through similar intermediary jurisdictions on their way to Iran, is a well-documented diversion pattern. Treasury and the Commerce Department's Bureau of Industry and Security (BIS) issue joint compliance guidance on this specifically because forwarders and freight consolidators are the choke point where diversion gets caught, or missed.

Red flags for transshipment diversion: a routing that adds cost and time with no commercial justification, a consignee in a transshipment hub with no obvious use for the goods, cargo re-documented mid-route, and forwarders in the chain who decline to name the ultimate consignee. None prove a violation alone, but under strict liability, ignoring an obvious diversion pattern is treated the same as knowing about it.

For the fuller list of sanctions programs and jurisdictions beyond the SDN List that logistics operations commonly encounter, see Beyond OFAC: Additional Sanctions Lists.

OFAC Sanctions vs. Export Controls: Why Logistics Firms Usually Need Both

OFAC and BIS enforce two related but distinct regimes, and logistics companies routinely need to check both. OFAC's lists prohibit transactions with specific designated parties and countries. BIS's Export Administration Regulations instead control what U.S.-origin goods and technology can go where, via its own lists, most notably the Entity List and the Denied Persons List, covering parties barred from certain U.S. exports for reasons that can be separate from OFAC sanctions entirely.

A shipment can clear an OFAC screen and still violate export control rules if the cargo or destination triggers a BIS licensing requirement, and a party can be clear of the Entity List while still being a designated OFAC party. Neither substitutes for the other. OFACScreen covers the BIS Denied Persons List alongside the OFAC SDN and Non-SDN Consolidated lists, the UN Consolidated List, and sanctions lists from the EU, UK, Canada, and Switzerland, eight lists in total, but the Entity List and export licensing stay a separate check for anyone moving controlled goods.

A Practical Screening Workflow for Booking Desks

Screening does not need to be a manual bottleneck. Three modes cover most logistics operations:

• Batch screening a day's bookings. Export the day's shippers, consignees, notify parties, and vessels and run them as one batch each shift, so nothing waits on an agent to remember. See Batch Screening Best Practices.
• API screening at booking creation. For higher-volume operations, wiring screening into the booking or TMS system checks a new shipper or consignee the moment it's entered, before a confirmation goes out. See API Integration for OFAC Screening.
• Free spot checks for one-off shipments. For an infrequent shipper booking a single container, a quick check at ofacscreen.com/screen/ takes a name and returns full results, no signup.

Documentation: Proof for a Carrier, Bank, or CBP

A shipment that clears screening is only half the job. If a carrier's compliance department, a confirming bank, or U.S. Customs and Border Protection later asks whether a party was screened and when, "we checked it" is not an answer anyone accepts without a record. OFACScreen's one-time $9.99 audit-ready PDF report gives each screened party a dated document showing the name searched, the lists checked, the list version, and the result, something to attach to the shipment file without a subscription for occasional bookings. Batch and API screening generate that same trail automatically.

Red Flags Checklist for Booking Desks

Beyond the screen itself, train booking staff to flag transactions for a second look regardless of what the automated check returns:

• Vague cargo descriptions. "General merchandise" or "machine parts" on a high-value shipment with no further detail is a documented diversion pattern, not just sloppy paperwork.
• Freight paid by an unrelated third party. If the party paying freight charges has no apparent connection to the shipper or consignee, ask why.
• Routing that makes no commercial sense. A longer, more expensive route through a known transshipment hub with no logistics reason for the detour.
• Reluctance to identify the ultimate consignee. A customer who resists naming who actually receives the goods.
• New customer, urgent shipment, unusual payment terms. Any one alone is common; together, on a first-time customer, they warrant a closer look before booking.

None of these prove a shipment is prohibited. But under strict liability, a booking desk that screens names and ignores an obvious red flag in front of it has not actually managed its risk. Treat a red flag as a hold on the booking until it is resolved, not a note to follow up on later.