INTEL
Status: blockedCLUSTERGolden Enterprise Shipping Limited added — likelyStatus: blockedCLUSTERbushehr shipping company limited added — likelyStatus: blockedCLUSTERmosakhar darya shipping co added — likelyStatus: blockedCLUSTERNovorossiysk-Turkish-Med Dark Fleet Cluster added — confirmedStatus: blockedCLUSTERPinnacle Petrol LLC added — likelyStatus: pendingCORPUS427 entities · 63 countries
Back to blog

Is a Pre-Deal Clearance Read the Same as KYC? No, and Confusing Them Costs You Speed and Compliance

Pre-deal clearance read vs. regulatory KYC: why a 30-second inception pre-screen is not CDD under FATF Rec 10, and how confusing them costs speed and compliance.

July 6, 2026By OilFlow Intelligence7 min readbuyer_intent

Screening a specific counterparty? Full 7-step dossier — $25, no account, report by email within the hour.

Is a Pre-Deal Clearance Read the Same as KYC? No, and Confusing Them Costs You Speed and Compliance

A pre-deal clearance read and a regulatory KYC are two distinct instruments used at two different moments in the transaction workflow. The pre-deal verdict is a sub-30-second pre-screen an originator runs at inception to decide whether a counterparty is worth pursuing; the full 7-step KYC dossier is the slower, regulator-grade record built once a deal is live and is what discharges your Customer Due Diligence obligation under FATF Recommendation 10. Running a fast clearance read does not satisfy a KYC obligation, and building a full dossier on every unsolicited LOI is friction you do not need.

That distinction sounds obvious in a compliance memo. It is routinely lost on the trading floor, where an originator who gets a green pre-screen read starts treating it as a compliance sign-off, and where an MLRO who sees the clearance step assumes the dossier is done. Both errors are expensive. One creates false confidence; the other creates unnecessary drag. This teardown takes apart the confusion, tool by tool, and shows where each belongs.

Why the market demands a fast filter at inception

Start with the tempo the originator actually works in. As of this read, Brent sits at $72.10 (+$0.30), WTI at $68.83 (+$0.14), and Dubai around $70.10, with the Brent-Dubai EFS near $2.00, wide enough to keep Atlantic Basin barrels competitive into Asian refiners. Spreads at that level move desks. An originator fielding a stack of unsolicited LOIs and ICPOs for EN590 or crude allocations cannot spend a full CDD cycle on each one before deciding which to even reply to.

Most of that inbound is noise. Broker-chained mandates, recycled letterheads, and copy-pasted procedure documents arrive daily. The originator's first question is not "can I bank this counterparty for the life of a contract." It is narrower and faster: "is there any reason to spend another hour on this at all." That is a triage question, and triage is precisely what a pre-deal clearance read answers.

What the pre-deal clearance read actually does

The pre-deal verdict is a pre-screen. It is built to return a fast read at inception, before a deal is live, so the originator can decide whether to proceed. It surfaces the obvious disqualifiers early: a name that pings against the OFAC SDN List, a mandate chain that collapses under its own weight, a document set that reproduces a known layer-cake template, a counterparty structure that carries the fingerprints of dark-fleet routing.

What it is not: it is not a record of record. A clearance read is a decision aid for one person at one moment. It does not build the audited, source-documented file that a regulator, an examiner, or your own MLRO will later ask to see. It answers "is this worth pursuing," not "have we identified and verified this customer and understood the purpose of the relationship." Those are different questions with different evidentiary standards.

Speed here is a design choice, not a shortcut. The value of a 30-second verdict is that it lets the originator kill 90 percent of the noise without touching the compliance function at all. That protects the KYC pipeline from being clogged with counterparties who were never real.

What regulatory KYC actually requires

Customer Due Diligence under FATF Recommendation 10 is a documented, four-part obligation: identify the customer and verify that identity using reliable independent source data, identify the beneficial owner and take reasonable measures to verify them, understand the intended nature and purpose of the business relationship, and conduct ongoing monitoring of the relationship and the transactions running through it. That is the floor, not the ceiling. Higher-risk counterparties trigger enhanced due diligence.

A structured 7-step KYC dossier is what operationalizes that obligation. It is the slower instrument by necessity, because it has to be defensible. Each element carries a source. Beneficial ownership is traced, not asserted. Sanctions screening is documented with the list version and timestamp. The purpose of the relationship is recorded against the trade instruments in play, the LOI, the ICPO, the DLC MT700 that will eventually settle it. This is the file your MLRO signs off on and the file that survives an examination.

The dossier is the record of record. When a regulator asks how you knew who you were dealing with, the dossier is the answer. A screenshot of a clearance verdict is not.

The failure mode: swapping the two

Here is where desks get hurt. The confusion runs in two directions, and each has its own damage profile.

Treating the clearance read as KYC. The originator gets a clean pre-screen, closes the deal, and the file never gets built. Now the institution has a live relationship with no CDD record. If that counterparty later surfaces on an SDN designation, or the beneficial owner turns out to sit behind a shell that a real dossier would have exposed, there is no defensible file to point to. The clearance read said "worth pursuing." It never said "identified and verified." The gap between those two statements is the gap between a green light and a compliance failure.

Treating KYC as the pre-screen. The inverse is quieter but still costly. Desks that route every unsolicited inbound into a full CDD workup burn compliance capacity on counterparties who were never serious. The MLRO's team drowns in dossiers for broker chains that would have died in a 30-second read. Friction accumulates, real deals slow down, and the desk loses barrels to competitors moving faster on the same EFS spread. Depth applied at the wrong moment is not diligence. It is waste.

The root error in both cases is the same: collapsing two instruments that live at different points in the workflow into one. Speed and depth are a deliberate trade-off. The pre-deal read is fast because it is a filter. The dossier is slow because it is a record. Neither can do the other's job.

The correct sequence: triage, then build

The workflow is sequential, not either-or. Run the clearance read at inception, on the unsolicited LOI or ICPO, before you have committed anything. Use it to triage: kill the noise, flag the obvious disqualifiers, and identify the small set of counterparties worth real work.

Then, once you decide to proceed, build the 7-step dossier. That is the moment the CDD obligation attaches and the moment the record of record gets constructed. The pre-screen fed the pipeline; the dossier discharges the obligation. Ongoing monitoring under Recommendation 10 continues for the life of the relationship, because the dossier is a living file, not a one-time gate.

Sequenced correctly, the two instruments reinforce each other. The read protects the dossier pipeline from noise; the dossier protects the institution from the counterparties the read let through. Confused, they cancel each other out.

What compliance teams should do

  • Define the two instruments in policy, in writing. State explicitly that a pre-deal clearance read is a pre-screen and does not discharge a CDD obligation under FATF Recommendation 10. Ambiguity in the policy becomes false confidence on the floor.
  • Assign the read to the originator and the dossier to the MLRO function. The person triaging inbound is not the person building the record of record. Keep the moments and the owners distinct.
  • Gate deal progression on the dossier, not the read. No live relationship should exist on the strength of a clearance verdict alone. The green pre-screen advances the counterparty to KYC; it does not skip it.
  • Audit for the gap. Periodically check for live relationships that have a clearance read on file but no completed dossier. That gap is where false confidence hides.
  • Screen at both moments against current lists. A counterparty that cleared at inception can be designated later. The read uses the SDN list of the day; the dossier documents ongoing monitoring against it.

A pre-deal verdict pre-screens. A KYC dossier is the record. Run the read at inception to triage, build the dossier once you proceed, and never let one masquerade as the other. That is how you keep both your speed and your compliance.

OilFlow Intelligence builds the pre-deal clearance read and the structured 7-step KYC dossier as two instruments for two moments in the workflow. To see how the triage-then-build sequence runs on live inbound, request a demo or subscribe to the fraud-intelligence briefing.

Verified trade-fraud patterns, sanctions deltas, and regulator actions. Weekly, for compliance and risk teams.

Double opt-in. No spam. The quarterly Compliance Index ships to subscribers first.

This article is part of our scam-cluster intelligence series. Screening a specific counterparty? Run the free check, or order the full 7-step dossier.