Key takeaways
- Map document names to specific commercial and delivery roles.
- Connect the seller's invoice to the accepted purchase and actual supply.
- Read a signature within the stated purpose of the signed record.
- Do not treat a local technical document as the sale agreement.
Separate local service documentation from the purchase
APBA's alternative-fuel programme identifies an LNG supply technical instruction within its local development framework. APBA programme information
A technical or local service document has its own purpose. It does not automatically identify the buyer's contracting seller, settle price terms or establish the scope of payment obligations. Check the current applicable texts where those questions matter.
For a current transaction, the transaction-party map is not provided; obtain current verified information. Record the contracting parties, physical-supply references and invoice connection, with any unresolved role or authority question identified.
Establish the seller from the accepted transaction
Start with the purchase the buyer actually agreed. Identify the legal counterparty and the accepted order reference rather than selecting the most prominent name on the delivery attachments.
If the seller arranges physical supply through another entity, ask for the supported connection to the buyer's order. The desk should understand why that entity's delivery record appears in the pack.
Do not assume that the physical supplier is also the invoice issuer, or that the invoice issuer was necessarily the party named on every operational document. The actual arrangement determines the roles, and ambiguity should be resolved before approval.
Match the invoice to the agreed commercial chain
An invoice should be connected to the accepted seller, purchase scope and supporting supply evidence. Where it references an unfamiliar delivery number, seek the cross-reference instead of rejecting or approving it solely by name recognition.
A changed billing entity is a material question. Establish whether the change is supported by the agreement and authorised process; a new payment instruction alone does not explain why another party is entitled to invoice.
Where assignment, agency or competing payment rights are involved, obtain appropriate legal and finance review. Procurement should prepare the factual chain without presenting a legal conclusion it has not established.
Understand what a receipt signature confirms
A signed receipt may serve a defined delivery purpose. The reviewer should examine its actual scope rather than treating every signature as approval of all sale terms, prices and later invoice items.
Equally, do not dismiss a signed record merely because it was produced by the physical supplier instead of the contracting seller. Its evidential value depends on what it records and its connection to the supply.
If wording or authority is disputed, preserve the document and obtain the relevant review. Avoid paraphrasing it into a broader commercial acceptance in the internal summary.
A party-and-document map
| Role or record | Connection to establish | Unsupported shortcut to avoid |
|---|---|---|
| Contracting seller | Accepted purchase and legal entity | Selecting the best-known brand name |
| Physical supplier | Supply arranged for the order | Assuming it must issue the buyer's invoice |
| Delivery record | Actual event and relevant product | Matching only by vessel name |
| Receiving acknowledgment | Signatory and stated scope | Treating it as approval of every charge |
| Invoice issuer | Entitlement under the accepted arrangement | Accepting a new entity without explanation |
| Payment beneficiary | Verified authorised settlement instruction | Treating an attachment change as sufficient authority |
| Local service record | Specific procedural or permission purpose | Using it as a substitute sale contract |
Fictional case: the unfamiliar name is the physical supplier
A fictional Algeciras purchase is agreed with a seller that arranges delivery through another entity. The completed supply pack carries the physical supplier's name, while the invoice arrives from the accepted seller.
Accounts initially sees a mismatch and considers the invoice unsupported. The procurement reviewer provides the order-to-delivery connection and identifies the distinct roles, allowing the legitimate comparison to proceed.
During that review, a separate attachment proposes payment to another entity without an adequate explanation. The team does not extend the verified physical-supply relationship to cover the payment change. It holds that specific question for the authorised review process while preserving the accepted delivery evidence.
Keep product evidence linked across the chain
Quality or specification evidence can carry another reference, such as a batch or parcel identifier. The commercial file should show how that evidence connects to the product supplied under the order.
The relevant technical reviewer assesses its substance. Procurement's task is to avoid sending evidence for a different parcel or presenting a general certificate as transaction-specific support.
If an intermediary forwards a document, preserve the identifiable source and relevant reference.
Close the file with a concise explanation
A useful close-out note states which party sold the fuel, which supplied it, what evidence supports the delivery and why the invoice matches the agreement. Outstanding issues should remain scoped to their actual question.
This is more helpful than a folder in which every document exists but no one can explain how the names and references relate.
Common mistakes
Avoid assuming all documents must bear one name, approving a new invoice entity without support or stretching a receipt signature beyond its stated purpose. Another mistake is using a local technical document to settle sale terms. Verify the connections that matter while keeping each record's purpose intact.
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
Must the physical supplier and seller be the same entity?
Do not assume either arrangement. Establish the actual roles and supported connection for the purchase.
Does a delivery signature approve every invoice charge?
Its scope must be assessed from the document and relevant agreement, not presumed.
Is an unfamiliar delivery reference automatically invalid?
No. Request the documented connection to the accepted purchase and supply.
What belongs in the party-map slot?
Record the seller, physical-supply connection, invoice basis and unresolved authority or settlement questions.