This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Key takeaways
- Identify whether the exception concerns identity, missing information or legal scope.
- Preserve the original search inputs and the returned result.
- Explain the specific action that depends on the assessment.
- Seek an authorised interim instruction while the question remains open.
- Record the reason and limits of the final decision.
Interpret the score as the tool describes it
OFAC explains that its search score measures name similarity, and it does not recommend a universal match threshold. These descriptions concern OFAC's tool; do not assume another product uses the same method or scale. Check the current text and the organisation's reviewed screening process.
For escalation, provide the actual score or result as evidence without translating it into a probability of wrongdoing. The reviewer needs the underlying entry and the transaction identity, not merely a coloured status or a statement that the score looks high.
Do not adjust settings solely to make an inconvenient alert disappear. If a search configuration may be inappropriate, treat that as a separate process question for the responsible owner. The current transaction still needs a defensible assessment on the available evidence.
A tool result can help prioritise attention, but it does not identify the complete legal consequence. The compliance decision-maker should determine the next step under the relevant rules and advice.
Classify the exception before forwarding it
An identity exception asks whether the searched party is the person or entity indicated by the result. An information exception concerns missing or inconsistent inputs. A legal-scope exception concerns how the applicable restrictions affect the proposed activity. These categories can overlap, but naming them helps focus the request.
For example, a company-name alert with an unresolved registration detail needs factual clarification. A known party involved in a newly proposed service may require a different legal analysis even if its identity is clear. Sending both as a generic screening problem obscures the decision needed.
The preparer should state what is known and what remains uncertain. Avoid presenting a tentative explanation as a completed finding. If a counterparty provides a clarification, identify its source and supporting evidence for review.
Classification is not clearance. It helps route the question to the appropriate person without allowing the operator to resolve matters beyond its authority.
Show the reviewer the transaction connection
An alert becomes actionable when the reviewer understands the party's role in the proposed activity. Identify whether the subject is the contracting entity, a payer, a service participant or another relevant party. Do not leave the relationship implicit in a forwarded email chain.
State the next action awaiting a decision. The principal may be considering a fixture commitment, an instruction to an agent or a payment. The reviewer needs the actual proposed act and timing to assess the request within its scope.
Preserve the commercial explanation without treating it as an argument for a predetermined outcome. A receiver's urgency or a vessel's schedule can help prioritise the work, but neither supplies missing identity evidence or changes a legal requirement.
If several actions depend on the same issue, identify them separately. A scoped answer about one action should not be extended automatically to the others.
Prepare an exception packet
| Packet component | What to include | Why it matters |
|---|---|---|
| Searched subject | Exact submitted name and identifiers | Shows what the result actually concerns |
| Source result | Relevant entry, source and search context | Allows assessment beyond the summary label |
| Identity evidence | Supporting records and discrepancies | Defines the factual question |
| Transaction role | How the party participates | Connects the alert to the proposed activity |
| Pending action | Specific decision and practical timing | Makes escalation actionable |
| Prior assessment | Relevant earlier conclusion and its scope | Avoids assuming it covers new facts |
| Requested instruction | The unresolved question for the reviewer | Prevents a vague request for reassurance |
This original packet is a commercial escalation aid, not a prescribed regulatory reporting form. The organisation's compliance process and applicable advice determine any required external action.
Keep the packet concise and link the supporting material. The reviewer should see the decisive uncertainty immediately rather than search through unrelated operational updates to find the issue.
Fictional case: a familiar name hides a new entity
In a fictional fixture, a screening alert resembles a name that the organisation previously reviewed and disqualified as a match. The operator assumes the new alert can be closed on the same basis because the trading name looks familiar.
The escalation packet reveals that the proposed transaction now names a different legal entity using a similar brand. The earlier assessment relied on identifiers that do not establish the new company's identity. The old conclusion is relevant history, but it is not a completed answer to the current question.
The reviewer requests the necessary clarification and assesses the actual subject. The principal receives a scoped decision for the current proposal. The operator records the reason rather than adding another unexplained entry to a list of previously cleared names.
The fictional case does not imply that the new entity is restricted. It shows why an earlier false-positive assessment should be linked to its evidence and scope, rather than reused through name familiarity alone.
Keep the interim operational instruction explicit
While the exception remains unresolved, the responsible principal should identify which dependent action awaits assessment and what work may continue within the applicable process. The operator should not create its own permission to proceed because a response is delayed.
Avoid ambiguous messages such as compliance is aware when the implementing team needs a decision. Awareness, active review and authorisation are different states. The receiving desk should know which one applies and who remains responsible for the next step.
Provide the reviewer with changes that affect urgency or substance. If the proposed payer, cargo or service changes during the review, identify the new fact rather than waiting for an answer to an obsolete question.
Any legal requirement to block, reject, report or seek authorisation must be determined through the applicable rules and advice. An internal escalation status should not be mistaken for the completion of a regulatory obligation.
Record the reason for resolution
The final record should explain what question was resolved, what evidence supported the decision and which action the conclusion addresses. A bare false positive or approved label does not give the next reviewer enough context if the same name appears later.
Where the decision is conditional, state the condition and the person responsible for confirming it. Do not allow a qualified conclusion to become unconditional when it is copied into an operational system.
If the issue cannot be resolved, identify the missing information and the resulting instruction under the organisation's process. An unresolved record is preferable to a manufactured explanation designed only to close the queue.
The principal should also know if the exception exposed a broader process problem, such as missing identifiers or an outdated party record. That improvement task can be handled separately from the decision on the current transaction.
Common mistakes
The main mistake is treating a similarity score as a legal conclusion. Another is reusing an earlier name-based dismissal without checking the current entity and supporting identifiers.
Avoid changing search settings to remove an alert, escalating without the transaction connection or reporting awareness as authorisation. Give the reviewer a defined question and preserve the scope of the answer.
Where Zeaclub fits
Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.
Zeaclub offers digitalised procedures across the voyage workflow.
Explore Zeaclub
Educational information only; not legal, financial or trading advice. Contract wording and applicable rules control. Verify current requirements and obtain qualified advice before acting.
Frequently asked questions
Is a high similarity score proof of a sanctions match?
It should be interpreted according to the tool's documented meaning and the organisation's review process. The responsible reviewer needs the underlying identity evidence and transaction context.
Can an earlier false-positive result be reused?
Check whether the same subject, identifiers and relevant circumstances are involved. An earlier conclusion should not be extended to a different entity or changed proposal through a familiar name alone.
What if the commercial action is urgent?
Explain the practical timing and seek a clear interim instruction through the authorised route. Urgency helps prioritise review but does not resolve the underlying evidence or legal question.
What should the resolution record contain?
State the question, evidence, reasoning, scope and any conditions of the decision. Keep the original alert separate from the reviewed conclusion so that later users can understand both.