Counterparty verification before a shipping commitment

Overview

A useful file lets the principal distinguish a known business from an acceptable transaction. An established relationship may support confidence in a contact while leaving a new subsidiary, unfamiliar service or different payment structure untested. This guide offers an original commercial review framework; questions about legal capacity, enforceable authority or regulatory applicability require the appropriate specialist and current governing text.

Key takeaways

• Identify the contracting entity independently of its trading brand and group reputation.
• Describe the actual obligation and exposure before deciding what information is relevant.
• Separate identity, authority, credit, performance and compliance conclusions.
• Resolve conflicting evidence by examining its purpose and provenance, rather than counting documents.
• Give any acceptance a defined scope, conditions and owner for outstanding questions.

Start with the proposed commitment

The first question is what the principal is considering doing. A freight booking, an advance payment, a long charter and an agency appointment create different practical dependencies. A standard onboarding questionnaire may gather useful background, but it cannot determine the depth of review without this transaction context.

Write a short exposure statement. Name the proposed contracting party, the service or cargo movement, the party expected to pay, and the circumstances in which the principal would depend on future performance. Identify whether the principal must commit resources before receiving payment or whether the counterparty will hold documents or funds. This is a commercial description, not a conclusion about liability.

Next describe the decision deadline and the consequence of delay. Some information can be obtained before a preliminary discussion; other evidence must precede an actual commitment. Treating every stage as a final approval creates needless friction. Treating an initial introduction as authority for the whole transaction creates a much more serious ambiguity.

Ask the person sponsoring the transaction to explain why this entity is involved. “It belongs to a familiar group” is background. “It will charter the vessel and receive the freight invoices under the proposed agreement” describes a role that can be tested against the documents.

Build an entity identity that survives name changes

Collect the legal name, jurisdiction, relevant registration identifier, registered address and any trading names used in the correspondence. Associate each identifier with its issuing source. An internal account number is useful for filing but should not be mistaken for a public registration identifier.

Where available, an LEI provides another reference point. GLEIF explains that its Level 1 data identifies entities, while Level 2 data concerns direct and ultimate accounting consolidating parents. Keep that specific relationship definition intact when using the information; do not silently relabel it as a complete answer to every ownership question.

Compare the entity named in the offer, draft contract, invoice instructions and supporting records. A difference may have an innocent explanation, such as a branch description or a disclosed agency arrangement. The task is to obtain the explanation and establish which document should govern the proposed role, rather than automatically rejecting every formatting variation.

Preserve original spelling alongside any normalized search name. Search aids can remove punctuation or translate text for convenience, but the execution documents need a reliable connection to the identified entity. When a translation changes the apparent legal form or obscures a suffix, refer the uncertainty for competent review.

Treat authority as a separate question

A real company can be represented by someone whose authority is insufficient for the proposed act. Conversely, a legitimate intermediary may be communicating without becoming the contracting party. The file should describe both the entity relationship and the person's role.

Request evidence proportionate to the act: who is negotiating, who is expected to execute, and who may issue operational or payment instructions afterward. Have the responsible reviewer decide whether the supplied authority evidence is adequate under the relevant arrangement. A familiar email signature should not be the sole explanation for authority to make an unusual commitment.

Distinguish receiving a document from accepting its legal effect. A coordinator may obtain a mandate or corporate authorization and record its stated scope. Determining whether it binds the principal is a different task. If the scope excludes the act now requested, route that discrepancy before the act takes place.

Communication verification also deserves its own entry. A person may have the right title while a particular message is unauthenticated or unexpected. Use an independently established contact route to resolve material inconsistencies. Record the question actually confirmed: identity of the sender, content of an instruction, and authority to issue it are related but separate matters.

Assess the ability to perform the proposed role

Credit review asks whether the principal is comfortable with the financial exposure. Operational review asks whether the counterparty can deliver the promised service. A financially substantial business may have little experience with the particular cargo, while a capable operator may propose payment terms outside the principal's appetite.

For financial review, assemble the evidence requested by the authorized credit function and explain its relationship to the actual obligor. Group accounts, a reference for an affiliate and a recent payment from another entity should be labelled accordingly. Do not convert group familiarity into an assumption that another company will meet the obligation.

For operational review, identify the resources and dependencies relevant to the proposed role. An agent appointment may depend on local service arrangements and availability. A cargo commitment may depend on readiness, terminal acceptance and the ability to provide the required shipment information. Ask for evidence tied to those dependencies rather than a promotional description of general experience.

References are most useful when the context is visible. A reference about routine documentation does not answer a question about handling an unusual cargo. Ask what the referee actually observed, how recently, and for which entity. Record limitations without turning a qualified reference into a negative finding.

Use an evidence matrix with separate conclusions

The following matrix is an editorial tool for structuring a review. Its purpose is to prevent a strong answer in one area from concealing a missing answer elsewhere.

Avoid a single green indicator until its meaning is defined. It might mean that the questionnaire is complete, that the documents have been reviewed, or that an authorized principal has accepted the proposed transaction. Those states should not share an unexplained label.

Resolve discrepancies by asking what they change

Conflicting addresses, different entity names and unexpected payment parties are prompts for explanation. Their importance depends on the decision they affect. An old correspondence address may create an administrative correction; a different intended charterer may change the entire credit and contractual review.

Keep a discrepancy statement short: what conflicts, which source says each thing, and which proposed action depends on resolution. Ask for the missing relationship rather than requesting the whole onboarding pack again. Targeted requests reduce delay and make evasive or incomplete answers easier to recognize.

Do not erase the conflicting evidence once an explanation arrives. Preserve the original and link the resolution, including who accepted it and for what purpose. A later reviewer may need to understand why an apparently inconsistent document did not change the decision.

Where evidence remains unavailable, describe the resulting uncertainty in practical terms. “Cannot establish the intended obligor” is more useful than “documents pending.” The principal can then decide whether to change the proposed terms, seek additional assurance, defer the commitment or decline it through the appropriate process.

Fictional case: a familiar brand proposes a new charterer

Consider a fictional cargo desk that has worked with a trading group through its established operating company. A new freight inquiry uses the same brand and familiar contact, but the draft recap names a newly introduced affiliate. The contact says the group handles everything centrally and asks the desk to reuse the existing customer approval.

The coordinator identifies several distinct questions. The new affiliate's identity must be established. Its role as charterer must be clear. The contact's authority to negotiate for it needs review. The credit function must assess the exposure to that obligor, and the proposed payment arrangement needs to be understood. None of these questions is answered simply by recognizing the brand.

Further information confirms the intended entity and explains the shared contact team. However, the financial material supplied belongs to the established operating company. The desk records that mismatch instead of renaming the document as support for the affiliate. The principal then considers whether different terms or separately reviewed support would make the proposed arrangement acceptable.

The outcome is a scoped decision, not a declaration that the group is either safe or unsafe. The existing relationship remains useful evidence of experience, while the new commitment receives the review its actual structure requires. If the entity changes again before execution, the affected conclusions must be revisited.

Design the handover around usable conditions

The person preparing the file should give the decision maker a concise conclusion page backed by accessible evidence. Include the intended act, identified parties, reviewed questions, unresolved exceptions and the proposed conditions. Show which function has addressed each issue without implying that one reviewer has covered every discipline.

Conditions should attach to a concrete action. “Confirm the contracting entity before execution” is testable. “Continue monitoring” is incomplete unless someone knows what to monitor and which change requires a new decision. A condition that nobody owns is likely to survive in the file while disappearing from practice.

After a decision, provide the operations and accounts teams with the parts relevant to their tasks. They may need the correct entity name, authorized contact route, payment verification requirement and triggers for escalation. They do not necessarily need unrestricted access to every sensitive background document collected during the review.

Finally, distinguish reusing evidence from reusing a conclusion. Stable identity information may remain useful, subject to freshness checks. Acceptance of a previous exposure does not automatically answer a new transaction with different terms, counterparties or dependencies.

Common mistakes

The most common mistake is allowing a successful identity search to stand for the entire review. Identity evidence can be strong while authority, financial exposure or performance capability remains unresolved.

Another is collecting documents without explaining their purpose. A large folder makes review slower when the entity, period and question supported by each item are unclear. Label the evidence relationship and retain the limitation.

A further mistake is letting commercial urgency redefine an unresolved question as an administrative detail. If the missing information determines who will owe or perform something, the principal should see that consequence before deciding how to proceed.

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

Explore Zeaclub