A 30-second verdict is not a KYC file. Desks that treat them as interchangeable either burn onboarding capacity on approaches that were never deals, or let fabricated paperwork enter a formal record where the file itself starts conferring legitimacy.

Is pre-deal clearance the same as regulatory KYC? No, and here is where each control belongs

Pre-deal clearance and regulatory KYC answer different questions at different moments in the workflow. Pre-deal clearance is an inception-stage triage run by the originator on the deal artifact itself, the LOI, the ICPO, the claimed allocation, the proposed DLC MT700 structure, and it answers whether the purported transaction is internally coherent enough to justify an hour of desk time. Regulatory KYC, the customer due diligence obligation set out in FATF Recommendation 10 and codified in instruments such as the US CDD Rule at 31 CFR 1010.230 and the EU anti money laundering directives now consolidating into the AMLR, answers a completely different question: can this named legal entity be lawfully onboarded and transacted with, screened against the OFAC SDN List and other applicable sanctions regimes, with beneficial ownership identified and the file built to survive examination. The second question only matters after the first one clears.

The sequencing problem: what is the originator actually asking?

An unsolicited approach lands. It might be a mandate letter, an LOI on letterhead, a "soft probe" for EN590 with a claimed refinery allocation, or an ICPO from a party three names deep in a mandate chain that nobody on the desk has met.

At that instant, the originator's question is narrow and operational: is this worth an hour?

That is not a KYC question. KYC is a legal-entity question. It presupposes there is a counterparty worth identifying. The approach in the inbox may not describe a real transaction at all. It may describe a cargo that does not exist, moving on a vessel profile inconsistent with the stated route, under a payment instrument structure that no confirming bank would ever issue in that sequence.

Running full customer due diligence on that approach does not resolve the coherence problem. It resolves a different problem, one you do not have yet. And it consumes the scarcest resource on any compliance function: analyst hours in the onboarding queue.

What pre-deal clearance actually is

Pre-deal clearance is a pre-screen. It is run on the artifact and the claimed structure, not on a verified legal person. It is fast by design, because its output is binary in practical terms: engage further, or do not.

What it interrogates is internal coherence. Does the claimed mandate chain reconcile with the party purportedly issuing the allocation? Is the payment instrument sequence commercially possible as described, or does it invert the normal order of performance in a way that pushes issuance risk onto the buyer before anything is verifiable? Does the product specification, the volume, the stated loadport and the delivery window form a transaction that a real trading desk would structure this way? Is the intermediary structure a legitimate broker arrangement, or a layer cake of interposed entities whose only function is to obscure who actually controls the cargo and the proceeds?

OilFlow's stated product capability includes exactly this: a pre-deal read that returns a verdict in under thirty seconds on the deal artifact as presented. That is a capability claim about the tool, not a claim about outcomes, adoption or detection rates.

Two things pre-deal clearance is emphatically not.

It is not a compliance sign-off. It does not discharge any obligation under FATF Recommendation 10, the CDD Rule, or the sanctions screening duties that attach to a transacting relationship. No MLRO should accept a triage verdict as evidence of due diligence, and no originator should present it as one.

It is not an identity verification. A coherent-looking deal from a sanctioned party is still a prohibited transaction. Coherence and legality are orthogonal.

What the regulator-grade KYC dossier actually is

The full 7-step KYC dossier is the record that survives audit, supervisory examination and correspondent-bank review. It is built once, properly, on a real counterparty, for a live deal.

Its components track the public frameworks directly. Identification and verification of the legal entity. Identification of beneficial ownership, with the ownership threshold and control tests applied per the relevant regime. Understanding the nature and intended purpose of the business relationship. Screening against the OFAC SDN List, consolidated EU and UK lists, and any other applicable regime, with attention to ownership-based exposure where a designated party's interest is not named on the face of the documents. Assessment of politically exposed person status. Risk rating and the assignment of an ongoing monitoring cadence. Documented approval, retained in a form that reconstructs the decision.

In an oil context that dossier also has to carry sector-specific risk indicators that a generic onboarding template will miss: vessel and voyage plausibility, AIS behaviour consistent with dark fleet operating patterns, ship-to-ship transfer exposure, and the jurisdictional geography of the payment route.

This is expensive work. It should be. It is also work that should only ever begin once you have established that a counterparty and a transaction exist.

The cost of conflation runs in both directions

Direction one: everything goes to onboarding. The desk treats every inbound approach as a potential relationship and routes it into full CDD. The onboarding queue fills with traffic that was never a deal. Analyst hours that should be spent on beneficial ownership resolution for live counterparties are spent verifying entities behind approaches that would have failed a coherence test in seconds. The queue lengthens, real deals wait, and the MLRO's escalation capacity is consumed by noise.

Direction two: no triage at all. The desk skips inception-stage screening and the fabricated documents pass straight into a formal file. This is the more dangerous failure. A KYC file is an institutional artifact. Once an LOI, an alleged allocation letter and a mandate chain sit inside a numbered dossier with an analyst's name on it, they stop being unverified claims and start being file contents. Downstream reviewers, credit committees, and in some cases correspondent banks read the file as a body of established fact rather than as a set of assertions that were never independently tested at inception. The paperwork acquires credibility it did not earn, and it acquires it from the filing system itself.

That is the procedural typology worth naming. Not a narrative scam, a control-placement error. One control run where two are required, at the wrong point in the workflow.

Market context: arb windows raise approach volume

Brent settled at $84.48, up $0.93. WTI settled at $78.88, up $0.70. Dubai was assessed at $82.48, putting Brent-WTI at $5.60 per barrel and Brent-Dubai at $2.00 per barrel. MOPS assessments were unavailable, so no inference should be drawn about Singapore product margins.

Open arbitrage economics tend to increase inbound approach volume across origination desks, because a visible spread is the pretext that makes an unsolicited offer sound timely. That is a structural observation about how approaches are framed, not a measured effect. The operational point stands regardless: when approach volume rises, triage load rises with it, and the desk without an inception-stage filter pushes that entire increase into the onboarding queue.

What compliance teams should do

1. Write the two controls into the workflow as separate steps with separate owners. Pre-deal clearance sits at inception and is owned by the originator. Full CDD sits at onboarding and is owned by compliance. Document the handoff point explicitly.

1. Define the trigger for KYC initiation. Full dossier work begins when a counterparty is identified and a deal is live, not when an approach arrives. Anything else is capacity leakage.

1. Prohibit triage output from appearing in the KYC file as evidence. A clearance verdict is a routing decision. It carries no evidentiary weight under FATF Recommendation 10 or the CDD Rule, and it should be recorded separately so no reviewer mistakes it for a sign-off.

1. Screen against OFAC SDN and applicable lists only at the onboarding stage, and screen the full ownership chain. A clean name search on the face of an LOI proves nothing about who controls the entity behind it.

1. Instruct originators on what a triage verdict means. "Cleared for further discussion" means the artifact is coherent. It does not mean the counterparty is acceptable, and it never will.

1. Audit for the credibility-conferral failure. Sample closed files and ask whether any document entered the dossier without independent verification at inception. If unverified assertions are being read downstream as established fact, the filing process is doing work it was never designed to do.

OilFlow Intelligence builds both controls: the pre-deal read for inception, and the 7-step KYC dossier for onboarding. If you want to see how the two sit in sequence rather than in competition, request a walkthrough or subscribe to the fraud-intelligence briefing.

A fast verdict is a filter for your queue. It is never a substitute for your file.