What a 235-Jurisdiction Trade-Tradability Matrix Actually Checks

Whether a physical-commodity trade can legally move looks like one question and is really four. Before a barrel or a parcel changes hands, a desk needs to know: can this product trade out of its origin and into its destination at all, are the payment terms permitted, does anyone in the chain need a license, and does the routing touch a sanctions nexus. Getting a clean answer means evaluating all four against the rules of the jurisdictions involved, on both sides of the trade.

A tradability matrix is the structure that holds those rules. This is a walk through what it checks, why each dimension matters, and why running it up front is cheaper than discovering a hard block after the deal is built.

Four dimensions, two sides

The mistake is treating tradability as a single yes or no. It is a grid. Four rule families, each evaluated for the origin country and again for the destination country, because a trade can be perfectly legal to sell and illegal to land.

1. Product tradability. Can this specific product move on this corridor? Some products are restricted out of certain origins or into certain destinations regardless of who the counterparties are. Crude, refined products, and gas each carry different treatment, and the treatment changes with the destination. A product that moves freely on one corridor can be barred on another.

2. Payment-term constraints. Even where the product can move, the permitted payment structure may be constrained. Some corridors limit or prohibit particular settlement mechanisms, financing arrangements, or terms. A deal can clear on product and still be unworkable on how it is paid for.

3. License requirements. Does the trade require a license, registration, or authorisation that a party in the chain does not hold? In many jurisdictions the seller, the buyer, or an intermediary must be registered with a national regulator to handle the product at all. Missing that is a hard stop that has nothing to do with sanctions.

4. Sanctions-aware routing. Does the corridor, the vessel, the flag, or any party touch a sanctions regime? This is where origin and destination interact with the counterparty screen. A clean product on a clean corridor can still be blocked if the routing runs through a restricted nexus or a designated party sits in the chain.

The reason the matrix spans 235 jurisdictions is that all four dimensions are jurisdiction-specific, and a single trade routinely involves an origin, a destination, an intermediary domicile, and a financing jurisdiction. Each one carries its own rules.

Why this belongs before the deal

In most desks, the regulatory question gets asked late, after a counterparty is chosen and terms are roughed out. The structuring effort goes in first and the tradability check comes last, the same backwards order that makes compliance-killed deals so expensive.

The dimensions above are not judgment calls that need a committee. They are lookups against a structured rule set. Product tradability for a corridor, the payment constraints on it, the license a party needs, the sanctions exposure of the routing: each is knowable from the counterparty name, the product, and the origin and destination, before anything is structured. Running the matrix first turns a four-to-six-week surprise into a thirty-second answer.

How it differs from a sanctions screen

A sanctions screen answers "is this party on a list." A tradability matrix answers "can this trade legally happen on this corridor." They are complementary and neither replaces the other.

A counterparty can pass every sanctions list and the trade can still be barred because the product cannot move that corridor, or because the payment term is not permitted, or because the seller lacks the required license. Conversely, a corridor can be wide open while a party in the chain is designated. A complete pre-deal read runs both: the eight-list sanctions and PEP screen on the parties, and the tradability matrix on the corridor.

Using it as an API

OilFlow exposes the matrix as the Regulatory Matrix API: send a product, an origin, and a destination, and get the tradability, payment-term, license, and sanctions-routing read back as structured data you can gate a workflow on. It is built to sit at the front of an origination or compliance flow rather than at the end of one.

If you want to see the rules applied to a real proposed trade rather than read about them, paste a deal for a free pre-deal clearance read at /predeal, or browse the public regulatory surface. To build against the matrix directly, the API documentation and a free sandbox key are the place to start, no card required.