Key takeaways
- Define the relevant endpoint from the actual agreement.
- Distinguish cargo completion, later documentation and departure events.
- Preserve the meaning and qualifications of each source entry.
- Assess conflicting endpoints as explicit alternatives while seeking clarification.
- Keep the resulting arithmetic separate from entitlement to payment.
Begin with the event the account needs
Skuld's statement of facts guidance highlights the evidential importance of contemporaneous port-call records. Their value depends on what they actually establish. Check the current text of the charter and obtain advice on the endpoint relevant to the despatch method being applied.
The reviewer should state that endpoint in a way the operational source can understand. A vague request for “completion time” may produce a record of a different milestone from the one needed for the account. Ask which activity ended and what the source means by its label.
This is especially important when the port file contains several completion-related entries. They may all be accurate but refer to different activities. A disagreement between times is not necessarily a contradiction until the event definitions have been compared.
The commercial team should resist selecting a convenient entry first and then interpreting the contract around it. Establish the required input, assess the evidence and apply the reviewed method in that order.
Separate the operational milestones
A cargo-operation completion entry, a later document-release entry and a departure entry can describe distinct stages. The relevant source should explain their meaning and relationship. The account reviewer should not collapse them into a single “finished” status.
If a report uses shorthand, obtain clarification from its issuer or the responsible personnel. Preserve the original wording alongside the explanation. A desk paraphrase should not become the only surviving account of what the source recorded.
Also distinguish an event time from the time it was reported. A message sent later may state that the operation ended earlier. The transmission record helps establish the communication history, but it is not automatically the operational endpoint.
Where the source qualifies the time as approximate, retain that qualification. An account can calculate a precise amount from an approximate input, but the presentation should not imply that the underlying event was established more exactly than the evidence allows.
Link the endpoint to the rest of the account
The endpoint cannot be reviewed entirely in isolation. The counted-time method leading to it, the allowance and any relevant exclusions also affect the result. Confirm that the disputed entry changes the intended input rather than another field with a similar name.
If the account preparer changes the endpoint, it should explain which counted period changes and why. A later time may affect the result differently under different counting assumptions. Do not assume a simple straight-line adjustment where the actual method contains qualifications.
The worked example below deliberately removes those complications. It illustrates the effect of alternative supported endpoints under an expressly assumed simple method. A real fixture requires the actual terms and evidence before the same arithmetic structure can be adopted.
Worked fictional endpoint comparison
This ILLUSTRATIVE example assumes an allowance of 48 hours and a simple agreed method that subtracts counted time from that allowance. Candidate endpoint A produces 30 counted hours; candidate endpoint B produces 32 counted hours. The assumed despatch rate is USD 12,000 per day, applied pro rata using 24 hours per day, with no additional modifiers.
| Candidate evidence position | Time saved | Calculation | Amount |
|---|---|---|---|
| Endpoint A | 48 − 30 = 18 hours | 18 ÷ 24 × USD 12,000 | USD 9,000 |
| Endpoint B | 48 − 32 = 16 hours | 16 ÷ 24 × USD 12,000 | USD 8,000 |
| Difference | 2 hours | USD 9,000 − USD 8,000 | USD 1,000 |
The difference shows why endpoint evidence can matter commercially. It does not authorise choosing the larger amount. The appropriate endpoint must follow the actual agreement and facts, and the example makes no finding that either amount is payable.
A principal receiving this comparison should also see why the evidence positions differ. Without that explanation, the numbers describe exposure but do not help assess the merits of the proposed account.
Use an evidence matrix for the completion question
| Evidence item | What to establish | Limit to preserve |
|---|---|---|
| Statement of facts entry | Which activity the completion label describes | Qualifications and agreement status |
| Vessel or terminal record | The source's observed event and time basis | Scope of observation |
| Later reporting message | Whether it reports an earlier event | Reporting time versus event time |
| Document-release record | What was issued or released | It may concern a different milestone |
| Departure record | What movement occurred | It does not independently define the contractual endpoint |
| Clarification | How the source explains an ambiguity | Distinguish later explanation from original record |
The matrix should identify the actual records used in the account. It should not imply that every listed item is mandatory in every fixture. The evidence required depends on the disputed proposition and the agreed method.
Where sources conflict, ask whether they describe different events before treating one as wrong. If they truly disagree about the same event, preserve the competing accounts and seek focused clarification. Do not average the times merely to produce a convenient compromise input.
Close the evidence question without overstating agreement
A source clarification may resolve the factual endpoint while leaving the contractual treatment disputed. State that distinction in the account. Agreement on what happened does not necessarily settle how the time-saved method applies to it.
If the factual question remains open, an authorised provisional comparison can identify its commercial significance. Label the alternatives and their supporting evidence. The account should not conceal uncertainty behind a single selected value described as final.
Once the position is resolved, update the calculation, narrative and any earlier estimate used by the commercial team. A corrected endpoint should not coexist with an outdated despatch expectation in the settlement brief.
Retain the explanation of the resolution. A future reviewer should understand why a particular event was used, especially if the file contains later milestones that might otherwise appear more definitive. The purpose is a supported commercial decision, not simply a tidy chronology.
Common mistakes
The main error is using the final timestamp in the file without checking what it represents. Another is choosing an earlier milestone because it produces more time saved. The endpoint must follow the agreement and evidence.
Do not confuse reporting time with event time or remove an approximation qualification. Avoid treating different operational milestones as contradictory records. Finally, keep factual resolution separate from contractual treatment so the account does not overstate what the parties have actually agreed.
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 departure time the default endpoint for despatch?
Do not assume that. Review the actual calculation basis and identify the required event. A departure record may describe a different stage from the endpoint relevant to the agreed method.
What if two documents show different completion times?
First establish whether they describe the same activity and use the same time basis. Seek clarification from the responsible sources. Preserve a genuine conflict rather than selecting the more favourable figure without explanation.
Can a later email prove an earlier completion event?
It can form part of the evidence, depending on its source and content. Distinguish the reported event time from the message time and retain any qualification or supporting record.
Does an agreed endpoint settle the despatch amount?
Not necessarily. The allowance, time-saved method, rate and other relevant terms also require review. A confirmed endpoint resolves one input rather than every element of the payment question.