What is the difference between a pre-deal clearance screen and a regulatory KYC check?

A pre-deal clearance screen is a fast go/no-go read run at inception, before desk time is committed, to tell an originator whether a counterparty or vessel is worth pursuing. A regulatory KYC check is the structured, multi-step dossier built once a deal advances, the artifact you hand to an auditor, a correspondent bank, or a sanctions authority such as OFAC. Both look at the same subject, but they carry different burdens of proof and sit at different points in the transaction lifecycle. FATF Recommendation 10 governs the second, the customer due diligence record, not the first.

Confusing the two is a common and expensive operational error. A 30-second verdict is not a dossier, and a dossier is not a triage tool. Read on for where each belongs in the workflow and why substituting one for the other costs you deals or exposes you to regulators.

Why the distinction is urgent on today's tape

When sour barrels and geopolitical risk reprice together, counterparty and vessel scrutiny tightens across every desk. Brent settled at $88.09, up 4.6 percent. WTI closed $81.77, up 4.5 percent. Dubai printed $86.09, with the Brent-Dubai EFS narrowing toward $2.00 per barrel amid US-Iran exchanges and Strait of Hormuz headlines.

A repricing of this kind pulls new counterparties out of the woodwork. Cargoes that were uneconomic last week become live, intermediaries surface with fresh mandates, and vessels change hands or flags to chase the spread. That is exactly the moment when a desk needs to triage fast at inception and then, for the deals that survive triage, build a KYC record that will hold up when a bank or a sanctions authority asks how the counterparty cleared. The two functions do not compete. They run in sequence.

What the pre-deal clearance read actually does

The pre-screen exists to answer one question at inception: is this counterparty or vessel worth spending desk time on, or should the originator walk now?

The read is deliberately fast. It surfaces the disqualifying signals that make further diligence pointless. A vessel matched against public dark-fleet indicators. A named entity or beneficial owner that appears on or links to the OFAC SDN list. An obvious flag mismatch or a counterparty presenting a mandate chain that does not resolve. When the read comes back adverse, the originator declines before a single hour of structuring is spent.

What the pre-screen is not: it is not the evidentiary record. It does not document the customer due diligence steps a regulator expects under FATF Recommendation 10. It does not establish source of funds, verify the full ownership tree, or produce the sanctions-screening audit trail an MLRO signs off on. It is a filter, not a file.

The function is triage. Treat it as anything more and you have skipped diligence you are legally obliged to perform.

What the 7-step regulatory KYC dossier actually does

The KYC dossier is the regulator-grade record. It is the artifact you produce when a deal advances past triage and warrants full diligence, and it is what you show an auditor, a correspondent bank, or a sanctions authority when they ask you to justify the relationship.

A structured KYC build works through the customer due diligence obligations that FATF Recommendation 10 sets out: identify and verify the customer, identify and verify the beneficial owner, understand the purpose and intended nature of the business relationship, and conduct ongoing monitoring. Around that core, an oil-trade dossier documents the vessel history, the flag and registry record, the ownership and management chain, the sanctions screening against OFAC SDN and other lists, and the trade-document trail that supports the transaction.

This is the layer where you resolve the questions the pre-screen only flagged. If the fast read surfaced an ambiguous ownership structure, the dossier is where you unwind it. If the vessel showed an AIS gap, the dossier is where you establish whether that gap has an innocent explanation or fits a concealment pattern.

The function is proof. This is the record that survives contact with a regulator.

Where dark-fleet red flags sit in each tool

The standard dark-fleet typologies appear in both tools, but they do different work in each.

In the pre-screen, these signals are triggers. Any one of them can be enough to decline at inception:

• AIS gaps. A vessel going dark over waters associated with sanctioned-origin loadings.
• Flag-hopping. Rapid changes of registry, often to flags with weak oversight, to obscure history.
• Ship-to-ship (STS) transfers. Transfers in known concealment zones used to break the chain of custody and disguise origin, a classic layer cake step.
• Opaque ownership. Beneficial ownership that does not resolve to a verifiable natural person or that routes through shell layers.

In the KYC dossier, the same red flags become lines of documented inquiry. An AIS gap is not an automatic decline at this stage. It is a question you investigate, evidence, and record: what were the coordinates, what was the duration, what does the vessel's pattern of life suggest, and can the counterparty account for it. The dossier documents both the flag and the resolution.

That is the operational difference in a single frame. In the pre-screen a red flag ends the conversation. In the KYC record a red flag begins a documented investigation whose conclusion the MLRO owns.

The two moments in the transaction lifecycle

Map the tools to the paper trail and the sequencing becomes obvious.

Inception. An LOI or ICPO arrives. The originator wants to know whether to engage before committing desk time. This is the pre-screen moment. A sub-30-second read gives a defensible go/no-go signal so the desk does not chase a counterparty that was never viable.

Advancement. The deal survives triage and moves toward a firm offer, a soft corporate offer, or a bank instrument such as a DLC issued by MT700. Now the burden of proof rises. This is the KYC moment, where the 7-step dossier is built and the customer due diligence obligations under FATF Recommendation 10 are discharged and documented.

Substituting one for the other fails in both directions. Run only the pre-screen and advance to an MT700 without a dossier, and you have an unbanked, unauditable relationship your MLRO cannot defend. Insist on a full KYC dossier at inception for every inbound LOI, and you have buried your originators in diligence on deals that a 30-second read would have killed. You either expose yourself to regulators or you lose deals to slower throughput. Often both.

What compliance teams should do

• Use the fast read to triage at inception. Let originators run a pre-deal clearance read on every inbound counterparty and vessel before desk time is committed. Treat an adverse read as a decline, not a project.
• Build the KYC dossier when a deal advances. Once a counterparty clears triage and the deal moves toward a firm offer or a bank instrument, discharge the full customer due diligence obligations under FATF Recommendation 10 and produce the regulator-grade record.
• Never treat the pre-screen as the diligence record. A go/no-go verdict is not evidence of CDD. If a regulator or correspondent bank asks how a counterparty cleared, the pre-screen alone will not answer.
• Never treat the dossier as a triage tool. Full KYC on every inbound LOI destroys throughput. Sequence the tools so diligence effort follows deal viability.
• Document the resolution of every red flag. An AIS gap, a flag change, an STS transfer, or an opaque ownership layer that survived the pre-screen must be investigated and evidenced in the dossier, with the MLRO owning the conclusion.

The pre-screen and the KYC dossier are two tools for two moments. One triages at inception, the other proves diligence when a deal advances. Keep them distinct and you protect both your throughput and your audit position.

To see how a sub-30-second inception read and a structured 7-step KYC dossier fit a single workflow, request a demo or subscribe to the OilFlow Intelligence briefing for evergreen typology analysis compliance teams cite.