This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Key takeaways
- Distinguish seller, intermediary, physical supplier and invoice issuer where relevant.
- Match records using legal identity rather than appearance alone.
- Keep identity checks separate from credit assessment and payment authority.
- Escalate changes through the organisation's approved verification process.
Use the relevant Greek identity reference carefully
Greece's GEMI company-search guidance describes searches by registry number, VAT number and company name.
For a Piraeus purchase involving a Greek-registered entity, that public reference can support the identity enquiry. It does not establish that the entity is the contracting seller in the particular transaction, that its credit is acceptable or that a payment instruction is authentic.
If the contracting entity is registered elsewhere, use the appropriate authoritative identity source. Do not assume a Piraeus delivery means every participant is a Greek company.
Map the parties before reviewing payment
Identify the buyer's contractual counterparty and the roles of any intermediary or physical supplier. Use the actual accepted documents and obtain clarification where the relationships are unclear.
A company appearing in delivery correspondence may perform a different role from the invoice issuer. That difference may be legitimate, but the finance reviewer needs an explained relationship rather than an assumption based on similar names.
Keep the vessel, call and supply references attached to the party map. A correctly identified company can still issue a document that relates to another transaction or an earlier delivery.
Review the payment evidence chain
| Review item | Evidence to obtain | Question it answers |
|---|---|---|
| Contracting identity | Accepted commercial document and authoritative identity reference | Which legal entity is involved? |
| Transaction link | Vessel, call and supply references | Which purchase does the amount concern? |
| Invoice basis | Billed components and supporting records | What is being requested for payment? |
| Recipient instruction | Verified instruction through the approved process | Who is authorised to receive the payment? |
| Credit decision | Actual finance approval and conditions | What commercial exposure has been accepted? |
| Release authority | Current internal authorisation | Who may approve the specific action? |
This is an original evidence checklist. It does not certify a supplier, provide a credit rating or establish a universal legal payment test.
Maintain a scoped review status
Authorised payment-review status: not provided; obtain current verified information. For a current transaction, .
The field should record completion and open questions without publishing private account details. Where a required confirmation is unavailable, show that the relevant decision remains pending.
Keep identity, invoice and payment-instruction checks separate in the record. Completing one does not imply that the others have been satisfied.
Fictional case: a familiar brand masks a different invoice entity
A fictional buyer receives a bunker invoice after a Piraeus call. The document uses a familiar trading style, but its legal issuer differs from the entity named in the accepted commercial record.
The preparer initially assumes the difference is merely presentation. The finance reviewer asks for the relationship between the entities and checks the transaction references before assessing the proposed payment.
The buyer obtains clarification through its approved contact process and records the actual basis for the invoice. If a payment recipient also differs, that instruction is reviewed separately rather than accepted as a consequence of the identity explanation.
The case shows why recognition of a brand is not the same as understanding the legal and commercial chain. It alleges nothing about any real Piraeus business.
Treat changed instructions as a new review question
If payment details or the claimed recipient changes, follow the organisation's established verification and escalation process. The reviewer should understand what changed, who requested it and what evidence supports the new instruction.
Do not allow operational urgency to erase the distinction between a supply issue and a payment-authority issue. Both may need prompt attention, but they require the appropriate decision-makers.
Preserve the original and revised communications according to the record policy. A clear change history helps authorised reviewers assess the request without relying on a reconstructed account.
Keep credit and payment approval distinct
An approved credit relationship does not automatically approve every invoice or recipient instruction. Likewise, a verified invoice does not determine whether a new credit request should be accepted.
Give finance the actual amount, scope, terms and unresolved questions needed for its decision. Do not present public registry information as a financial assurance or a prediction of performance.
If contractual responsibility is disputed, provide the agreement and evidence to the appropriate adviser. Check the current text and actual incorporated terms before making a legal assertion about who must pay.
Transfer the decision accurately
Record the action authorised, its conditions and the person responsible for implementation. An approval to investigate or prepare payment should not be restated as approval to release it.
At handover, identify any pending clarification and who will assess the reply. Keep the review open until its defined requirements are satisfied through the accepted process.
Common mistakes
Avoid using a trading name as the whole identity check, treating registry information as credit approval or assuming that a delivery participant is automatically the payment recipient. Do not merge separate review states into a vague cleared label.
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
Does a GEMI search prove a payment instruction is authentic?
No. It supports an identity enquiry within its scope. Payment instructions require the organisation's separate authorised verification process.
Must every Piraeus supplier be Greek-registered?
Do not assume that. Identify the actual contracting entity and use the relevant authoritative source for its jurisdiction.
Can different seller and invoice names be legitimate?
The relationship requires explanation from the actual records and responsible parties. Do not accept or reject it solely from the difference in names.
Does credit approval authorise invoice payment?
Follow the actual internal authority arrangements. Credit exposure, invoice validity and release of a particular payment are distinct review questions.