Is a Pre-Deal Clearance Check the Same as KYC? No, and Confusing Them Costs You Deals or Compliance

A pre-deal clearance check and a regulatory KYC dossier are not the same instrument. A pre-deal clearance is a fast inception pre-screen, a sub-30-second go/no-go read that tells an originator whether a counterparty is worth spending time on, often including a live cross-reference against the OFAC SDN List. A regulatory KYC is the full customer due diligence record built to satisfy FATF Recommendation 10, the auditable file your MLRO must produce when an examiner asks how the desk cleared a counterparty. One protects your origination time. The other protects you in an audit. Treating either as a substitute for the other is a structural error.

The confusion, and what it costs both ways

On most physical trading and commodity finance desks, the phrase "we ran KYC" gets applied to almost any counterparty check. Someone Googled the company. Someone pulled a name against a sanctions tool. Someone got a passport scan of the signatory. All of that gets filed mentally under "KYC," and the deal moves.

This conflation fails in two directions.

The first failure is at inception. A desk that has no fast screening step lets relationship managers pour hours into a counterparty that a thirty-second read would have killed. The originator drafts the LOI, chases the ICPO, coordinates on the DLC MT700 wording, and only later, when the compliance file is being assembled, discovers the buyer sits one hop from a designated entity or is a shell with no operating history. That is origination time burned on a counterparty that was never bankable.

The second failure is downstream and more dangerous. A desk that leans on the fast pre-screen as though it were the record has no defensible file. When the examiner or the correspondent bank asks for the CDD documentation, a screenshot of a sanctions hit and a note saying "looked clean" is not a KYC dossier. It does not establish beneficial ownership. It does not document the mandate chain. It does not evidence the risk rating decision. FATF Recommendation 10 does not recognize a triage verdict as due diligence. The desk that confused the two now has a compliance gap that surfaces at exactly the wrong moment, after funds have moved.

The fix is not to run more diligence earlier or to lighten the KYC. The fix is to understand that these are two tools for two moments, held by two different actors, carrying two different burdens of proof.

Pre-deal clearance: the inception triage filter

A pre-deal clearance read exists to answer one question for the person at first contact: should I spend time on this counterparty at all?

The actor is the originator or relationship manager. The moment is inception, the first email, the first WhatsApp introduction, the first LOI landing in the inbox. The burden of proof is low by design, because the output is a decision to engage or walk, not a decision to transact.

A pre-deal read is fast because it is narrow. It answers questions like: does this counterparty name or its obvious affiliates appear on the OFAC SDN List or another primary sanctions list? Is there an immediate red flag in the corporate identity, the jurisdiction, the vessel history if a cargo is named? Is this a known layer cake pattern, a chain of intermediaries with no economic logic? Is there any signal of dark fleet exposure in the shipping leg?

The pre-deal read is a triage filter. It is a smoke detector, not a fire investigation. Its value is speed and its purpose is protecting origination bandwidth. OilFlow's fast pre-deal read is built for exactly this function, a sub-30-second verdict at first contact so the desk does not commit hours before it knows whether a counterparty clears the most basic screens.

What a pre-deal read is not: it is not evidence. A thirty-second verdict does not establish beneficial ownership, does not verify source of funds, does not document the RM's risk assessment, and does not create the paper an auditor needs. It was never meant to. Asking a triage filter to serve as your regulatory record is asking the wrong tool to carry a burden it was never designed for.

Regulatory KYC: the record built to survive audit

A regulatory KYC dossier exists to answer a different question, for a different reader: can the desk defend, in front of an examiner, that it knew who it was dealing with before it committed?

The actor here is the compliance function and, ultimately, the MLRO. The moment is before commitment, before the DLC is issued, before the desk is contractually and financially exposed. The burden of proof is high, because the output is a file that must survive audit, correspondent bank review, and, in the worst case, an enforcement inquiry.

This is where the full seven-step KYC dossier lives. It maps onto the customer due diligence obligations that FATF Recommendation 10 sets out: identifying the customer and verifying that identity using reliable independent sources, identifying and verifying beneficial ownership, understanding the purpose and intended nature of the business relationship, and conducting ongoing due diligence throughout. Recommendation 10 also requires that the depth of diligence scale with risk, which means the enhanced measures for a higher-risk counterparty are themselves part of the defensible record.

A regulatory KYC file documents the mandate chain, establishing that the party presenting the LOI or ICPO actually has authority to act. It records the corporate structure and the natural persons behind it. It captures the risk rating and the reasoning that produced it. It preserves the source documents. The point of all of this is not speed. The point is defensibility. When someone asks the MLRO to prove the desk did its job, the KYC dossier is the answer.

A fast pre-screen cannot do this and should not be asked to. The two instruments carry different burdens because they answer to different readers, the originator on one side, the examiner on the other.

The handoff: mapping both tools to the workflow

The cleanest way to hold both tools correctly is to place them at their proper moments in a single workflow.

Inception. A counterparty makes contact. Before the RM invests any structuring time, the pre-deal clearance read runs. If the counterparty fails the fast screen, an SDN hit, an obvious layer cake, a vessel with dark fleet indicators, the RM walks and no origination time is wasted. This is the go/no-go gate.

Deal progression. The counterparty cleared the fast screen. The RM engages, terms take shape, the LOI and ICPO exchange, DLC MT700 wording gets discussed. The pre-deal verdict has done its job. It has bought the desk permission to spend time, nothing more.

Before commitment. Now the full seven-step KYC runs. Beneficial ownership is verified. The mandate chain is documented. The risk rating is set and reasoned. The dossier is assembled to the standard FATF Recommendation 10 expects. Only when this record exists does the desk commit, issue the instrument, and expose capital.

Same workflow, two instruments, two actors, two moments, two burdens of proof. The pre-screen never becomes the record. The record never has to run in thirty seconds. Neither is asked to do the other's job.

What compliance teams should do

• Name the two tools separately in your procedures. Do not let "we ran a check" stand for both. Write the pre-deal clearance read and the regulatory KYC into policy as distinct steps with distinct owners and distinct outputs.
• Put the fast screen at inception, before origination time is spent. A go/no-go read that includes an OFAC SDN cross-reference at first contact protects RM bandwidth and kills unbankable counterparties early.
• Never file a pre-screen as your KYC record. A triage verdict does not satisfy FATF Recommendation 10. Require the full CDD dossier, beneficial ownership, mandate chain, risk rating, source documents, before any commitment.
• Map both tools to the transaction lifecycle explicitly. Pre-screen at inception, deal progresses, full KYC before the DLC issues. Make the handoff a documented control, not an informal habit.
• Give the MLRO the audit-grade file, every time. The question is not whether the counterparty looked clean at first contact. The question is whether the desk can prove what it knew before it committed.

Run the fast read to protect your deals. Build the KYC to protect your compliance. They are complements, not substitutes.

To see how a sub-30-second pre-deal clearance read and a seven-step KYC dossier sit inside one workflow, request a demo or subscribe to the OilFlow Intelligence newsletter for evergreen typology briefings.