This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Evidence must explain the decision
A green icon can show that software returned no configured match. It rarely shows the lists, data, thresholds, ownership, cargo, services, jurisdiction, reviewer or unresolved facts behind approval.
Recordkeeping duties are jurisdiction-specific
Sanctions, export-control and licensing regimes can prescribe retention, reports and production to authorities. Identify the rules applicable to each entity and transaction.
Start with an immutable deal identifier
Link fixture, voyage, vessel, cargo, payment and compliance records through a consistent reference. Names and invoice numbers change.
Preserve the list source
Record authority, list, download or query time, version and whether ownership rules beyond named entries were assessed.
Preserve exact search terms
Keep legal names, aliases, native script, registration numbers, dates, addresses, IMO number, MMSI and fuzzy settings.
Keep candidate matches
A dismissed near match is part of the audit trail. Record identifiers compared and the reason for resolution.
A no-match result needs limitations
State data age, jurisdictions covered, ownership gaps and any source unavailable. Silence is not proof of universal clearance.
Ownership needs arithmetic
Save the dated corporate chart, sources, percentages, aggregation and control analysis. A final beneficial owner label is not reproducible.
Distinguish source types
Mark registry evidence, counterparty declarations, vendor data, public reporting and analyst inference. They carry different weight.
Preserve former vessel identities
Connect names, flags, call signs, MMSIs, owners and managers through the IMO number and effective dates.
Cargo evidence needs a chain
Keep bills, invoices, certificates, terminal records, samples, quantities, tank movements and transfer history relevant to origin.
Payment evidence needs message state
Preserve instructions, remitter, beneficiary, currency, correspondents, bank queries, holds, rejections, freezes, returns and settlement.
Licences need the complete text
Save the operative version, conditions, parties, dates, reports and legal analysis. A licence number without scope is weak evidence.
General licences also need versioning
Authorities can amend or replace them. Record the text relied upon at each act, not the current webpage years later.
Legal advice needs factual inputs
Retain the facts sent to counsel and identify later changes. Advice based on a clean owner cannot decide a voyage after ownership changes.
Separate fact logs from privileged advice
Maintain operational evidence and decision records without unnecessarily copying legal communications. Privilege depends on law and substance.
Exceptions need expiry
An approved alias, supplier or route exception should be limited to verified identifiers and reviewed when facts change.
Continuous monitoring needs snapshots
If a platform updates results automatically, preserve status at fixture, nomination, loading, payment and discharge.
Event-based checks remain essential
Re-screen after designation, ownership, flag, manager, cargo, route, bank or consignee change.
Time must be normalized
Keep original timestamps and zones, then add normalized UTC separately. Do not overwrite source data.
Emails need headers
Forwarded messages and screenshots can lose sender, routing and time evidence. Preserve originals under authorized retention.
Messaging apps need controlled export
Capture relevant messages, edits, attachments, participants and time while respecting privacy and local law.
Voice decisions need confirmation
Document material telephone approvals and facts in a contemporaneous record. State who participated and what remained conditional.
Ship records need focused collection
Obtain relevant logs, AIS status, cargo and port documents without burdening the master with legal conclusions.
Vendor evidence needs provenance
Record provider, dataset, query and confidence. A commercial database can change historical relationships after reprocessing.
Web evidence needs capture context
Save URL, access time and page or document edition. A bookmark can later point to revised content.
Translations need control
Keep original language, translator, method and qualifications where material. Machine translation can support triage but not silently replace the source.
Data integrity needs access controls
Limit editing, log changes, back up records and preserve originals. A shared spreadsheet without history is vulnerable.
Retention should stop routine deletion
Legal holds and regulatory retention must cover mail, chats, screening exports, contracts and ship records across systems.
Over-retention creates other risk
Privacy, confidentiality and data-localization rules still apply. Keep necessary evidence with defined access and disposal.
Voluntary disclosure needs root-cause evidence
Collect chronology, persons, transactions, controls, failure, remediation and affected records. Avoid rewriting history to sound cleaner.
Training records prove capability imperfectly
Attendance shows exposure to training, not correct execution. Link lessons to procedures, testing and actual decisions.
Testing should sample real files
Check whether approvals contain identity, ownership, cargo, payment, licence and review evidence, not merely whether a field is populated.
Metrics need meaning
Alert volume, clearance speed and overdue cases can reveal strain. They should not reward analysts for closing difficult matches quickly.
Automated models need version evidence
If software scores ownership, routes or AIS behavior, preserve the model version, configured thresholds, input data and human review. A later upgrade may produce a different result from the same transaction. Compliance must be able to explain the decision actually made, not the decision today's model would make.
Production must remain usable under deadline
Authorities, banks or courts may request records quickly. Index documents by deal, vessel, party, event and authorization; preserve native files and readable exports; test retrieval; and identify withheld privileged or personal data through a controlled process. A theoretically retained archive that cannot be searched or authenticated is weak evidence.
Owners need voyage dossiers
Combine vessel, charterer, cargo, route, services, banks, approvals and changes in one indexed file.
Charterers need supply-chain dossiers
Trace seller, buyer, origin, end user, payment and transport while sharing necessary evidence with carriers.
Brokers need transmission evidence
Keep what was requested, received and forwarded with caveats. Do not alter documents into informal summaries.
Insurers need decision separation
Record underwriting, sanctions and claims decisions independently, including facts and authority relied upon.
Hypothetical: the vanished list
A vessel was cleared against a commercial dataset that later changes. The saved list version, query and identifiers allow reconstruction.
Hypothetical: the unexplained override
An analyst cleared an ownership alert with no note. Later review cannot determine whether evidence existed, turning a correct outcome into an indefensible process.
Hypothetical: the revised licence
A general licence is narrowed after loading. Versioned records prove which authorization applied to each earlier act and identify later steps needing new review.
Forecast
Compliance systems will generate stronger machine-readable audit trails, while synthetic documents and changing datasets complicate provenance. Evidence lineage will become as important as screening logic.
ZeaClub view
Build the file so an independent reviewer can reproduce the decision using information available at the time. Preserve identity, lists, ownership, cargo, services, payment, licences, uncertainty and authority. A screenshot records a screen; a defensible dossier records compliance.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- U.S. Treasury OFAC, A Framework for OFAC Compliance CommitmentsAccessed 2026-11-19
- U.S. Treasury OFAC, Economic Sanctions Enforcement GuidelinesAccessed 2026-11-19
- U.S. Department of Commerce BIS, Export Compliance GuidelinesAccessed 2026-11-19
- UK Government, OFSI general guidanceAccessed 2026-11-19
- Council of the European Union, EU Best Practices for restrictive measuresAccessed 2026-11-19