Durban Bunker Documents: Application or Licence?

Key takeaways

• An application form is not proof that its request was approved.
• Review the actual operator and proposed activity, not only the seller's name.
• Keep regulatory evidence separate from product and delivery evidence.
• Check current requirements and document status before relying on them.

Understand the document's purpose

TNPA's bunkering application form identifies the port and proposed method or activity. TNPA application form

That form structure helps organise a question; it does not establish that the applicant holds approval. A completed form, payment receipt or correspondence about processing should retain its actual status.

For a current transaction, the permission-evidence review is not provided; obtain current verified information. Record the proposed operator and activity, document type, relevant scope, verification basis and unresolved questions without publishing sensitive personal information.

Separate the contracting seller from the performing operator

A seller may arrange a physical service through another party. The buyer's review should identify who will perform the relevant activity and which evidence belongs to that entity.

Do not reject a document merely because its holder differs from the contracting seller without first understanding the proposed arrangement. Equally, do not accept a seller's unrelated permission as evidence for another operator's activity.

The commercial record should explain the roles and connect the proposed service to the relevant evidence. Where the legal or regulatory consequences of the arrangement are uncertain, check the current text and obtain appropriate advice or authority confirmation.

Examine scope rather than appearance

An official-looking document may concern another port, a different activity or a period that does not cover the planned service. The review should identify those fields explicitly instead of relying on logos, file names or a general statement that the company is licensed.

Check whether the document is an application, issued permission, amendment, renewal request or other communication. A later date alone does not make one category equivalent to another.

If the supplier provides only part of a document, ask for the relevant complete evidence or an appropriate verification route. A cropped page may omit conditions essential to understanding its scope.

A permission-evidence decision table

Fictional case: the attachment is only a request

A fictional Durban supplier sends a completed application form in response to the buyer's request for supporting service documentation. The attachment carries the proposed operator's name and identifies the port, so the procurement record initially marks the check complete.

A reviewer notices that the document describes an application rather than issued permission. The buyer requests the appropriate current evidence and clarification of the proposed performing entity.

The review remains open until the relevant status is established. This does not assume that the operator lacks permission; it recognises that the document supplied does not answer the question. The purchase decision can then rely on a supported position rather than an inference from a form's appearance.

Keep product evidence on a separate track

Permission evidence does not establish that the offered fuel meets the accepted specification, that the parcel quantity is correct or that a particular delivery window is available. Those questions need their own relevant confirmations.

Likewise, satisfactory product documents do not resolve an unanswered permission question. A complete procurement review should preserve the distinction rather than letting one strong document compensate for an unrelated gap.

This separation makes follow-up more efficient. The buyer can ask for the missing evidence precisely instead of requesting an undefined larger document pack that still fails to address the actual issue.

Resolve the result before representing the check as complete

The final review should state what was verified, by whom and for which proposed service. If an authority clarification is limited to a particular point, preserve that limit.

Where current public evidence is unavailable, use an authorised confirmation route and record the outstanding status honestly. Do not copy an old approval marker from a previous Durban purchase without confirming its relevance.

Avoid turning the procurement checklist into an independent legal determination. Its role is to gather and connect the evidence required by the applicable process, with qualified assessment where needed.

Common mistakes

Avoid treating applications as issued permissions, assuming seller and operator roles are identical and accepting a document without checking its scope. Other mistakes include using a payment receipt as approval evidence or treating a permission document as proof of fuel quality and service availability.

Where Zeaclub fits

Zeaclub supports agentic, AI-assisted operations with a human in control.

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Explore Zeaclub

Visit the Zeaclub website