The boundary

Commercial confidentiality. Compliance transparency.

The two are not in conflict. Commercial pricing and counterparty relationships are protected to preserve trust between sides; origin, documentation, banking, customs, inspection and contractual compliance remain fully transparent to required parties at every stage.

"Estal separates commercial confidentiality from compliance transparency. Commercial pricing and counterparty relationships are protected; origin, documentation, banking, customs, inspection and contractual compliance remain fully transparent to required parties."

Pillar 1

Origin transparency

Origin certificate and supporting documentation always available to required parties — banks, customs, surveyors, counterparties.

Pillar 2

Vessel and shipping compliance

IMO and sanctions screening on every nominated vessel. AIS history reviewed. P&I, class and flag verification.

Pillar 3

Banking and LC compliance

KYC, AML and beneficial-owner disclosure to opening banks. LC structure aligned to applicable banking and FX administration rules.

Pillar 4

Customs and inspection documentation

Full chain of customs and inspection documentation, transparent to receiving customs authority and surveyors.

Pillar 5

Contractual discipline

Back-to-back contractual integrity. Spec, term and quantity discipline maintained across both sides of the chain.

Pillar 6

Counterparty screening

Pre-engagement KYC, sanctions screening (OFAC, EU, UK, UN) and PEP screening on every counterparty.

What confidentiality covers

Commercial information, not compliance information.

Counterparty names, pricing, margins and bilateral commercial terms are not disclosed publicly. This is to preserve commercial trust between sides — a producer expects discretion about their pricing; a refinery expects discretion about their procurement profile. None of this affects compliance disclosure to banks, customs, surveyors, or contractual parties, which remains complete.

Banking · customs · inspection · counterparty

Compliance documentation discussion is welcome.