What Does a Pre-Deal Clearance Check Actually Test? The Five Fields Every Originator Submits

A pre-deal clearance check tests four originator-supplied fields against four distinct failure modes: the counterparty against first-party fraud and registration inconsistency (the risk-based diligence logic of FATF Recommendation 10), the product against the counterparty's plausible trade profile, the corridor against sanctions exposure under the OFAC SDN List and the EU and UK regimes, and the payment structure against the deal's stated economics. Each field is a probe, not a formality. When an originator understands what each input defends against, the paste itself becomes a first line of defense rather than a box-ticking exercise.

With Brent at $76.29, WTI at $72.11, and Dubai at $74.29, the Brent-Dubai EFS sitting near $2.00 keeps Atlantic barrels marginally competitive into Asia. That single spread is why the corridor field is not decorative. A routing that ignores the prevailing arb is a routing worth questioning, and the check knows it before the deal does.

Why the Paste Is the Point

Most originators treat a clearance read as a gate they walk through. It is more accurate to treat it as a diagnostic that only performs as well as what you feed it. OilFlow's clearance mechanism reads the fields an originator submits and tests each against the failure mode it is designed to surface. A thin or evasive paste produces a thin read. A precise paste produces a sharp one.

The order matters too. Originators tend to supply the fields in a natural sequence: who they are dealing with, what is being traded, where it moves, and how it settles. Walking that sequence is the fastest way to understand what the check is doing at each step, and where a deal is most likely to break.

Field One: Counterparty, Tested Against First-Party Fraud and Registration Consistency

The counterparty field is the first thing an originator pastes and the first thing the read stresses. Here the test is identity and registration coherence, the operational core of FATF Recommendation 10 customer due diligence. Rec 10 requires firms to identify the customer, verify that identity using reliable and independent source data, and understand the nature of the business relationship. A pre-deal check applies that logic before the relationship is formalized.

The specific failure mode is first-party fraud, where the entity presenting the deal is misrepresenting itself rather than being impersonated by a third party. This shows up as registration inconsistency: a company number that does not match the trading name, a formation date that postdates the claimed trading history, a registered address that resolves to a mass-registration shell, or a mandate chain that cannot be reconciled to any beneficial owner with standing to sell the cargo.

What to paste: the legal entity name exactly as registered, the registration number, the jurisdiction of incorporation, and the role the counterparty claims (principal, mandate, or intermediary). If the counterparty is presenting under a mandate, name the principal. A mandate chain that cannot be walked to a real principal is the classic tell, and it is the counterparty field that surfaces it.

Field Two: Product, Tested Against the Counterparty's Plausible Trade Profile

The product field is tested for coherence, not existence. EN590 diesel exists. The question the check asks is whether this counterparty plausibly trades it, in the volume claimed, on the terms offered. A newly formed entity with no verifiable trade history offering multiple cargoes of EN590 at a steep discount to the prevailing curve is not describing a deal. It is describing bait.

The probe here is the fit between the named product and the counterparty profile established in field one. Product coherence catches the deals where the specification is technically real but commercially impossible for the entity presenting it. Discount depth is a component of this test: a price that sits well below the market for the corridor and grade is not a bargain, it is a flag, because legitimate sellers do not systematically leave money on the table.

What to paste: the exact grade and specification (EN590 10ppm, Jet A-1, or the relevant standard), the volume, the offered price or the basis and differential, and the delivery basis (FOB, CIF, or the applicable Incoterm). The read tests whether that bundle is internally consistent and consistent with what the counterparty could credibly source and move.

Field Three: Corridor, Tested Against Sanctions Exposure and Jurisdictional Risk

The corridor field, meaning the load port, the discharge port, and the route between them, is tested against public sanctions frameworks and jurisdictional risk. The named regimes are the OFAC SDN List and OFAC sectoral programs, the EU restrictive measures, and the UK sanctions regime administered by OFSI. A corridor that touches a sanctioned load point, a designated port, or a jurisdiction under a relevant program is the failure this field is built to catch.

The corridor test also probes for routing plausibility, and this is where today's tape earns its place in the read. With the Brent-Dubai EFS near $2.00, Atlantic barrels are only marginally competitive into Asia. A stated routing that makes no economic sense against the prevailing arb, or a discharge declaration that contradicts the load port and grade, is the signature of a layer cake structure built to obscure the true origin or destination of the cargo. Dark fleet activity, where vessels disable transponders or spoof positions to move sanctioned barrels, lives in exactly this gap between the declared corridor and the plausible one.

What to paste: the load port, the discharge port, the vessel or vessel-to-be-nominated status, and any transshipment points. Naming the corridor precisely lets the read test it against the SDN List, the EU and UK regimes, and the arb math that governs whether the route is even rational.

Field Four: Payment Structure, Tested Against the Deal's Stated Economics

The payment structure field tests whether the instrument matches the money the deal claims to move. A documentary letter of credit issued by MT700, a documentary letter of credit, an SBLC, or an advance-payment arrangement each carries its own economic logic. The failure mode is mismatch: an instrument that does not fit the size, tenor, or risk profile the rest of the paste describes.

Common tells surface here. A demand for a large advance payment before any performance instrument is posted inverts the normal risk allocation of a physical trade. A DLC structure that routes through an issuing bank inconsistent with the counterparty's stated jurisdiction, or a payment chain that adds intermediary hops with no commercial purpose, is a layer cake in the settlement leg. The instrument should follow the economics. When it leads them, or contradicts them, the deal is being engineered around the money rather than the cargo.

What to paste: the proposed instrument type (MT700 DLC, SBLC, or the specific arrangement), the issuing and confirming banks where known, the tenor, and the sequence of payment against documents or performance. The read tests that sequence against the volume, price, and corridor already supplied, and flags where the settlement structure does not reconcile to the trade it claims to fund.

The Fifth Field: Supporting Documents That Anchor the Other Four

Beyond the four core inputs, originators supply the documents that tie the deal together: the LOI, the ICPO, the corporate offer, and any proof of product or proof of funds. These are not a separate test so much as the connective tissue that lets the read cross-check the other four fields against each other. An ICPO that names a volume the counterparty could not credibly finance, or an LOI whose delivery terms contradict the corridor, is where inconsistency becomes visible.

The documents are also where recycled fraud paper is caught. Templates that circulate across unrelated deals, banking coordinates that reappear under different counterparty names, and specifications lifted verbatim from prior offers are all patterns a clearance read can flag when the supporting paste is complete.

What Compliance Teams Should Do

• Standardize the paste. Require originators to submit all four core fields plus supporting documents in a consistent format. Incomplete fields produce weak reads, and the gap is where fraud hides.
• Train the front office on what each field defends against. An RM who knows the counterparty field tests the mandate chain will pre-empt the failure rather than discover it late.
• Treat the corridor field as a live economic test, not a static one. Update routing-plausibility expectations against the prevailing EFS and arb, so implausible routings are caught in context.
• Reconcile the payment structure to the trade before it clears. Ensure the MRLO or MLRO function reviews any deal where the instrument leads the economics rather than following them.
• Anchor every read in the named frameworks. FATF Recommendation 10 for diligence logic, and the OFAC SDN List, EU, and UK regimes for sanctions exposure. Document which framework each flag maps to.

A clearance check is only as good as the paste that feeds it. When originators understand that each field is a test against a specific failure mode, they stop treating the check as a rubber stamp and start using it as the diagnostic it was built to be.

See how OilFlow's pre-deal clearance reads these fields in practice. Request a demo, or subscribe to Forensics Friday for weekly trade-document typologies.