OFAC Screening for Cross-Border Freight

Why this topic matters to a trucking operation

Compliance & Risk is not an isolated office task. It affects the driver’s available time, the truck’s utilization, customer service, document quality, safety exposure, and the final margin on the load. A weak decision at the beginning of the trip often creates several smaller problems later in the workflow.

The subject of “OFAC Screening for Cross-Border Freight” should therefore be handled as a repeatable operating process. The dispatcher needs reliable information, a clear owner for the next action, a deadline, and an escalation path when the plan changes.

Small fleets benefit from this discipline as much as large carriers. A documented process reduces dependence on one experienced employee and gives managers a consistent way to train new dispatchers, review exceptions, and improve performance.

Build the operating picture

Sanctions compliance belongs inside the freight workflow whenever a carrier, broker, shipper, consignee, warehouse, fuel supplier, payment recipient, beneficial owner, or other transaction party could be subject to U.S. restrictions. A name match cannot be resolved by intuition, and a clean result at onboarding does not prove that every later transaction is safe. Dispatch, compliance, accounting, and management need one documented process for collecting legal identities, checking current official lists, evaluating ownership and control, stopping a questionable load, and escalating the decision before cargo, money, equipment, or services move. The process is especially important on cross-border freight, where translated names, multiple business aliases, subcontractors, changed payment instructions, high-risk corridors, and time pressure can hide the party that ultimately benefits from the transaction. This is an operational control framework, not legal advice; carriers should use qualified sanctions counsel when a possible match, license question, blocked interest, reporting duty, or ownership issue cannot be resolved confidently. The practical goal is to make the next action obvious to the dispatcher, driver, and manager without searching across separate calls, messages, and spreadsheets.

A connected transportation management system gives the team one timeline for the load. That timeline should contain the current status, responsible person, supporting documents, and the next decision point.

Use this field playbook

Apply the process consistently to every applicable load, then make exceptions visible instead of keeping them in someone’s memory.

• Collect the identity needed for a real screening decision before booking. Record the legal name, trade names and aliases, physical and mailing addresses, country, registration or tax number, authority identifiers, verified phone and domain, bank beneficiary, key contacts, and the owners or controllers required by company policy. Do not screen only the name printed on a rate confirmation.
• Screen relevant parties against current official OFAC data at onboarding and again when the transaction changes. Include the customer, broker, shipper, consignee, warehouse, subcontracted carrier, payment recipient, beneficial owners, and any new party introduced through a reroute, reconsignment, factoring notice, fuel arrangement, or emergency service request.
• Treat an alert as a stop-and-review event, not proof of guilt and not something a dispatcher should clear alone. Hold tender acceptance, dispatch, cargo release, payment, and document sharing; compare identifiers beyond the name; preserve the search result; and route the case to the designated compliance owner or counsel.
• Apply ownership review in addition to list screening. OFAC states that an entity owned directly or indirectly, individually or in aggregate, 50 percent or more by blocked persons is also blocked even when the entity name does not appear separately on the SDN List. Document the source, date, and reasoning used to resolve material ownership questions.
• Build transaction-level red flags into the TMS. Escalate unexplained changes to the carrier, tractor, trailer, driver, pickup point, delivery address, beneficiary, bank account, email domain, or payment route; unusual urgency; resistance to ownership questions; mismatched documents; shell-company indicators; and instructions to avoid normal verification channels.
• Define the incident response before a match occurs. Identify who can place and release a compliance hold, who contacts counsel or OFAC, how blocked or rejected transactions are handled, what records must be retained, how drivers and customers are told to pause safely, and how the carrier reports a suspected violation without moving property or funds prematurely.

Measure the result

Measure whether the control works without turning screening into a box-checking exercise. Review screening coverage, list-update timing, alerts, false positives, unresolved cases, hold duration, ownership reviews, changed-party events, payment exceptions, training completion, and any load or payment released without required approval. A good program protects lawful freight by making legitimate parties easier to clear while giving the team a firm, documented reason to stop when identities, ownership, or instructions do not align. Track a small number of outcomes such as on-time performance, empty miles, document cycle time, accessorial recovery, calls per load, and contribution per truck-day.

Review exceptions weekly. The purpose of measurement is not to create more reporting; it is to find the recurring handoff or missing field that causes preventable work.

How to put the information into daily practice

Start by identifying where compliance & risk appears in the current dispatch workflow. Review what information is collected, who confirms it, where it is stored, and what event triggers the next action. If the answer depends on a private text message or someone’s memory, the process is difficult to audit and difficult to scale.

Use one load timeline to connect the booking decision, driver assignment, route and appointment plan, status updates, exceptions, supporting documents, accessorial approvals, and invoice readiness. Each update should answer three questions: what changed, who owns the response, and when the next update is due.

Introduce the improvement on a small group of active loads before applying it to the whole fleet. Review the exceptions at the end of each shift, correct unclear fields or instructions, and then make the successful version the standard operating procedure.

• Collect the identity needed for a real screening decision before booking. Record the legal name, trade names and aliases, physical and mailing addresses, country, registration or tax number, authority identifiers, verified phone and domain, bank beneficiary, key contacts, and the owners or controllers required by company policy. Do not screen only the name printed on a rate confirmation.
• Screen relevant parties against current official OFAC data at onboarding and again when the transaction changes. Include the customer, broker, shipper, consignee, warehouse, subcontracted carrier, payment recipient, beneficial owners, and any new party introduced through a reroute, reconsignment, factoring notice, fuel arrangement, or emergency service request.
• Treat an alert as a stop-and-review event, not proof of guilt and not something a dispatcher should clear alone. Hold tender acceptance, dispatch, cargo release, payment, and document sharing; compare identifiers beyond the name; preserve the search result; and route the case to the designated compliance owner or counsel.
• Apply ownership review in addition to list screening. OFAC states that an entity owned directly or indirectly, individually or in aggregate, 50 percent or more by blocked persons is also blocked even when the entity name does not appear separately on the SDN List. Document the source, date, and reasoning used to resolve material ownership questions.
• Build transaction-level red flags into the TMS. Escalate unexplained changes to the carrier, tractor, trailer, driver, pickup point, delivery address, beneficiary, bank account, email domain, or payment route; unusual urgency; resistance to ownership questions; mismatched documents; shell-company indicators; and instructions to avoid normal verification channels.
• Define the incident response before a match occurs. Identify who can place and release a compliance hold, who contacts counsel or OFAC, how blocked or rejected transactions are handled, what records must be retained, how drivers and customers are told to pause safely, and how the carrier reports a suspected violation without moving property or funds prematurely.
• Assign a named owner and a due time for every unresolved exception.
• Keep customer and driver communication attached to the load record.
• Review the result after delivery and carry the lesson into the next similar load.

Common mistakes and practical risk controls

The most common mistake is acting with incomplete information because the load feels urgent. Speed is useful only when the basic facts are verified. Before committing the truck, confirm the parties, rate or cost exposure, equipment, timing, route constraints, required documents, and the person authorized to approve changes.

Another mistake is allowing an exception to remain inside a phone call. If detention, a missed appointment, an equipment problem, a route change, a rejected shipment, or a compliance concern is not recorded, the next person cannot make a fully informed decision. Written timestamps and supporting documents protect both service and payment.

Finally, avoid measuring activity instead of outcomes. More calls, messages, or status entries do not necessarily mean better control. The useful question is whether the process produced a safer trip, an on-time delivery, a complete document set, a satisfied customer, and an acceptable contribution margin.

• Do not promise an appointment before checking realistic transit and driver hours.
• Do not rely on an unverified email, changed phone number, or altered payment instruction.
• Do not close the load while documents, accessorials, or customer exceptions remain unresolved.
• Do not change a compliance process based only on a headline; confirm the official requirement first.

What managers should measure

A useful scorecard for compliance & risk should be short enough to review every week. Combine service, cost, workflow, and safety measures so that one improvement does not hide damage somewhere else.

Compare performance by customer, lane, dispatcher, equipment type, and exception reason. Trends become actionable when the team can see where a delay or cost begins, not only the final monthly total.

• On-time pickup and delivery percentage, including the documented cause of every miss.
• Loaded and empty miles, revenue per total mile, and contribution per truck-day.
• Average check-in, loading, unloading, and detention time by facility.
• Time from delivery to verified POD and time from verified POD to invoice.
• Number of avoidable exceptions, repeated data corrections, and unresolved driver issues.
• Safety or compliance events that required a dispatch change or management review.

A simple implementation checklist

Use this checklist during a dispatch meeting or process review. Each item should be visible in the company’s transportation management workflow and understandable to the person covering the desk after hours.

• The load has a verified customer or broker, rate, commodity, equipment type, weight, and reference number.
• Every stop has an address, appointment, contact, instructions, service-time allowance, and required document.
• The assigned driver and equipment can complete the plan safely and legally.
• Fuel, toll, deadhead, parking, and likely delay exposure are reflected in the operating decision.
• The driver knows the next action, expected updates, and the exceptions requiring immediate escalation.
• Delivery paperwork and accessorial evidence will flow directly into review and invoicing.
• A manager can reconstruct the load history without searching personal messages or separate spreadsheets.

Frequently asked questions