The Sanctions Screening Step Your Finance Team Keeps Skipping

Ask a finance or procurement team in a mid-sized Indian exporter whether they do sanctions screening and the answer is usually yes. Ask when they do it, and the answer is almost always the same: at onboarding, once, by checking the counterparty's name. That single design choice quietly defeats the entire control, because sanctions lists change constantly, ownership structures hide listed parties behind clean names, and the riskiest moment is not when a vendor is created in the ERP but when money or goods actually move.

Why is screening at onboarding not enough?

Because sanctions lists change all the time, and a counterparty that was clean on the day it was onboarded can be designated the next week.

Sanctions screening is a point-in-time check against lists that are anything but static. The US Treasury's OFAC updates its Specially Designated Nationals (SDN) list throughout the year, the US Commerce Department adds names to the Entity List in batches, and the EU and UN consolidated lists move with every geopolitical development. A counterparty that was clean at onboarding can be designated the following week — and every shipment, payment, and service delivered after that date is a fresh exposure, not a continuation of an old, approved relationship.

For Indian companies, the obligation stack is layered. The UN Security Council sanctions lists are binding in India and implemented through domestic law, including orders under the Unlawful Activities (Prevention) Act. The Weapons of Mass Destruction and their Delivery Systems (Prohibition of Unlawful Activities) Act, 2005 prohibits dealings that could contribute to proscribed programmes. DGFT's SCOMET list controls dual-use exports, as we covered in detail in our explainer on SCOMET, EAR and ITAR. And on top of the strictly legal obligations sits the commercial reality: if your transaction touches US dollars, US-origin goods or technology, or US persons anywhere in the chain, US sanctions rules can reach it — and a violation can cost you your banking relationships even where no Indian law was broken.

What is the screening step finance teams skip?

The skipped step is rarely the onboarding check — vendor masters and customer masters usually get a name run against a list, even if informally. The step that disappears under deadline pressure is re-screening at the moment of the transaction: before the shipment is booked, before the payment is released, before the revised consignee on a redirected order is accepted. That is precisely the moment when three things the onboarding check never saw can surface.

1. The list has changed

Screening frequency has to match designation frequency. A counterparty base screened annually against lists updated weekly means your control is blind for most of the year. Serious programmes re-screen the entire master data set every time the major lists update, and screen each transaction's parties — buyer, consignee, end-user, bank, vessel, freight forwarder — at execution.

2. The name is clean but the owner is not

Under OFAC's 50 Percent Rule, an entity owned 50 percent or more, individually or in aggregate, by sanctioned persons is itself blocked — without ever being named on any list. Name-matching software will pass it every time. Catching it requires beneficial-ownership questions at onboarding and genuine curiosity when a buyer's ownership runs through two holding companies in jurisdictions known for opacity. This is the "knowing your counterparty" that regulators mean, and it cannot be delegated entirely to software.

3. The transaction has changed shape

Diversion is the classic pattern: the order is placed by a clean trading company, payment arrives from a third country, and shipping instructions change after contract signature to a new consignee or an unusual port. Each change is individually explainable and collectively a red flag. If your process only screens the original contracting party, every subsequent substitution walks straight through.

"The invoice was clean, the buyer was clean, the payment cleared. It was the freight forwarder's revised delivery address — added by email two days before shipment — that connected the transaction to a listed entity."

Why do finance teams skip transaction-time screening?

Not because they are careless — because the process design makes skipping the path of least resistance. Screening sits with one compliance resource who becomes a bottleneck at quarter-end. Alerts from screening tools produce false positives that take hours to clear, so hits get "resolved" with a glance. The person releasing the payment has a target for processing time, not a target for escalations raised. And nobody has told the shipping desk that a changed consignee needs a fresh check, because the procedure document says "counterparties are screened at onboarding" and everyone is, technically, following it.

What does “knowing your counterparty” mean for an Indian exporter?

For an Indian exporter or importer, a defensible screening programme has a short list of non-negotiables. Screen against the right lists: UN consolidated, OFAC SDN and sectoral lists, the US Entity List and Denied Persons List, the EU consolidated list, and any lists relevant to your specific markets. Screen the whole transaction, not just the buyer — end-users, consignees, banks, vessels, and intermediaries. Ask ownership questions and document the answers. Check the goods as well as the parties: dual-use classification under SCOMET and, where US-origin content is involved, the EAR, because a clean buyer purchasing a controlled item for an undisclosed end-use is still a violation. And keep the evidence — screening logs, alert dispositions, and end-use declarations are what stand between "we have a process" and "we can prove it" when a bank, a customer's auditor, or an enforcement agency asks.

How can you fix sanctions screening this quarter?

Move screening to the moment of the transaction, automate re-screening on list updates, capture ownership, treat changes as new transactions, and train the people who execute them.

1. Move screening to transaction time. Make release of payment and booking of shipment conditional on a current screen of all parties, not on the onboarding flag in the ERP.
2. Automate list-update re-screening. Every refresh of the major lists should trigger a batch re-screen of the counterparty master, with hits routed to a named owner within a defined turnaround.
3. Add ownership to onboarding. Capture beneficial ownership on the vendor and customer forms, and apply the 50 Percent Rule logic before approving high-risk-geography counterparties.
4. Treat changes as new transactions. A revised consignee, a new remitting bank, a substituted vessel or a third-party payment triggers a fresh screen — build it into the shipping and treasury checklists.
5. Train the people who touch the transaction. The accounts executive releasing the payment and the logistics coordinator accepting the address change are your real screening layer. They need to recognise diversion red flags, not recite regulations.

That last point is where most programmes are thinnest. Screening tools are only as good as the person who acts on the alert, and red-flag recognition is a trained instinct. Our Sanctions & Trade Compliance course is built for the finance, procurement, sales and logistics teams who execute transactions: the major sanctions regimes, list and ownership screening, diversion red flags, and what to escalate before — not after — the goods leave the dock. For role-based options, see our sanctions and trade compliance training hub.

The quarter-end pressure will not go away. The question is whether your process makes the screening step impossible to skip, or merely possible to tick. Right now, for most Indian companies, it is the latter.