Pre-Deal Clearance vs. Regulatory KYC: What's the Difference and When Do You Use Each?

A pre-deal clearance read is a fast pre-screen at the moment of inception that tells an originator whether a counterparty is worth another minute of effort. A regulatory KYC dossier is the multi-step, documented record of decision that satisfies FATF Recommendation 10 customer due diligence expectations and screens against lists like the OFAC Specially Designated Nationals (SDN) file. They answer different questions at different points in the deal lifecycle, and treating one as a substitute for the other is the actual failure mode.

The workflow moment that starts everything

An originator opens the inbox to an LOI or an ICPO. A name is attached to a cargo of EN590 moving USGC to NW Europe. With Brent at $72.13 and the Brent-WTI arb near $3.35/bbl keeping barrels flowing across the Atlantic, origination tempo is high. The desk has more inbound than it can work. The first question is not "can we defend this relationship to a regulator" but something far narrower and far more immediate: "should I spend another minute on this counterparty, or bin it and move to the next name?"

That question has an owner. It is the originator, not compliance. And it has a moment. It sits at inception, before any documentary chain has been requested, before a DLC or MT700 is discussed, before the file exists at all. The tool that answers it must return a verdict in the time it takes to read the email, or it is not fit for that moment.

This is where teams blur two distinct functions and pay for it in one of two ways. Either they run the full compliance process on every unqualified inbound name, drowning the desk and burning analyst hours on deals that were never real. Or they skip the pre-screen, chase the deal on instinct, and arrive at onboarding with a thin file that will not survive a regulator's review. Sequence solves this. Substitution breaks it.

What a pre-deal clearance read actually is

A pre-deal clearance read is a pre-screen. It exists to protect originator time. It takes a counterparty name at the point of first contact and returns a fast go/no-go signal so the desk can decide whether the opportunity clears the bar for real work.

What it is not, and this matters, is a compliance record. It does not stand as the institution's documented decision. It does not replace list screening against the OFAC SDN file, the EU consolidated sanctions list, or the UK OFSI regime. It does not satisfy the customer due diligence obligations set out in FATF Recommendation 10, which expect a firm to identify the customer, verify identity from reliable independent sources, understand the beneficial ownership, and understand the purpose of the business relationship. A pre-deal read touches none of that at the depth a regulator requires, and it is not designed to.

OilFlow's pre-deal clearance read is built for this narrow job: a fast verdict at inception. Its value is precisely that it is fast and disposable. It tells the originator whether to open the next door. If the read comes back adverse, the originator saves the hours that would have gone into a dead file. If it comes back clean enough to proceed, the deal graduates to the process that does produce a defensible record.

The discipline here is honesty about scope. A pre-screen that pretends to be a compliance record is dangerous, because it invites the desk to onboard on the strength of a signal that was never meant to carry that weight.

What a regulatory KYC dossier actually is

The KYC dossier is the record of decision. It is the multi-step, documented, defensible file that answers the second question: can we defend this relationship to a regulator, an auditor, or a court.

This is the artefact that FATF Recommendation 10 contemplates. It carries identity verification from independent sources, beneficial ownership mapped through the mandate chain, screening results against OFAC SDN, EU, and UK OFSI designations, an assessment of the counterparty's risk profile, and the reasoning that supports the decision to onboard. Where the counterparty sits near the edges of the compliant trade, near vessels associated with the dark fleet, or presents a layered ownership structure that resembles a layer cake designed to obscure ultimate control, the dossier is where those findings are recorded and either cleared or escalated.

OilFlow's KYC dossier is a multi-step build, not a single verdict. That structure is the point. Each step contributes evidence to a file that has to withstand review long after the deal has closed. The dossier is owned by compliance, produced deliberately, and retained. It is the thing an MLRO points to when asked why the institution took on a given counterparty. A verdict cannot do that job. Only a documented file can.

Building this dossier costs time and effort. That is exactly why you do not want to build one for every unqualified name that lands in the originator's inbox. The dossier is expensive by design because it is defensible by design.

Where each tool sits in sequence, and who owns it

Place them on a timeline and the confusion dissolves.

At inception, the originator holds a raw name. The pre-deal clearance read runs here. Owner: origination. Purpose: protect desk time. Output: go/no-go. This step decides whether the deal is worth pursuing at all.

Once the deal is worth pursuing, ownership passes to compliance. The KYC dossier is built here. Owner: compliance, accountable to the MLRO. Purpose: protect the institution. Output: the regulator-grade record of decision. This step decides whether the institution can defend the relationship.

The pre-deal verdict never replaces the dossier. It decides whether the dossier is worth building. Read in that order, the two tools reinforce each other. The pre-screen filters the funnel so that compliance spends its expensive, documented process only on names that have already cleared a first look. The dossier then does the deep work the pre-screen was never built to do.

Conflate them and you get one of the two failure modes named at the top. Run the dossier process on every inbound and the desk slows to a crawl while analysts build files for deals that evaporate. Treat the pre-screen as the record and the compliance file arrives thin, unable to answer the Recommendation 10 questions or evidence the sanctions screening that OFAC, the EU, and the UK OFSI regime expect.

Why the distinction protects the desk and the institution

Speed and depth look like a trade-off only when both are forced into the same moment. Separate the moments and the trade-off disappears. The originator gets speed at inception. The institution gets depth at onboarding. Neither tool is asked to do the other's job, so neither is compromised.

This is also the answer to a question that comes up in every desk that runs high origination tempo: how do we move fast without cutting the compliance record thin. You do not solve it by making the dossier faster or the pre-screen deeper. You solve it by sequencing. Fast first, deep second. Filter, then document.

What compliance teams should do

• Map the two moments explicitly. Draw the line between inception and onboarding, and assign each tool to its moment. The pre-deal read at inception, owned by origination. The KYC dossier at onboarding, owned by compliance and accountable to the MLRO.
• Stop treating the pre-screen as a record. Write it into policy that a pre-deal clearance read is not customer due diligence and does not satisfy FATF Recommendation 10. It gates the process. It is not the process.
• Reserve the dossier for names that clear the pre-screen. Protect analyst hours by not building expensive, documented files for unqualified inbound. Let the pre-screen filter the funnel first.
• Screen the dossier against live designations. Confirm every onboarded counterparty against the OFAC SDN file, the EU consolidated list, and the UK OFSI regime, and record the result in the file. Map beneficial ownership through the mandate chain and flag layer-cake structures for escalation.
• Audit for the failure modes. Periodically check that the desk is not skipping the pre-screen and running on instinct, and that compliance is not running the full dossier on names that never cleared inception. Both are symptoms of conflation.

Sequence, don't substitute. The verdict decides whether the file is worth building. The file is what defends the institution when a regulator asks.

---

To see how a pre-deal clearance read and a multi-step KYC dossier sit side by side in one workflow, request a walkthrough or subscribe to the OilFlow Intelligence newsletter for further typology explainers.