This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Key takeaways
- Organise records around the question they prove, not merely their file format.
- Keep forecasts, verified information, purchases and commercial allocations distinguishable.
- Preserve corrections without erasing the earlier decision basis.
- Set retention and access rules through the applicable legal and organisational review.
This article proposes an original commercial evidence architecture. It does not prescribe a universal retention period or replace statutory reporting records. Check the current text, applicable requirements, contractual obligations and any relevant preservation instruction before setting a retention or deletion schedule.
Decide what a future reviewer must reconstruct
Start with the questions likely to arise. Which activity did the estimate cover? Which inputs were available when the decision was made? What quantity and price basis were used? What was actually purchased, transferred, requested or settled?
These questions require related but different records. A final invoice may show the amount requested without explaining the source of the quantity. A verified emissions record may support reporting without establishing the commercial price basis.
Design the archive to connect those records while retaining their different meanings. The aim is not to create one document that appears to prove everything.
Also preserve the intended purpose of a model. A forecast prepared for voyage comparison should not later be presented as though it were the final basis for a contractual settlement.
Keep ship evidence and company reporting connected
The Commission's MRV guidance distinguishes ship emissions reports from aggregated company-level data for ships within ETS scope. Commission maritime MRV FAQ.
For this proposed archive, retain references that allow the responsible reviewer to connect the relevant ship and period with the company-level process. Do not assume that a company summary contains every detail required to understand a specific commercial voyage calculation.
The archive should also identify who supplied or approved the relevant evidence. A filename containing final does not establish verification, submission or acceptance status.
Where the commercial team holds only a reference to a controlled compliance record, preserve a reliable retrieval route and the responsible custodian. Uncontrolled copies can become outdated; inaccessible references can leave the reviewer unable to test the calculation.
Build an evidence map by function
The following table proposes an original structure. The responsible functions should determine the exact records and access restrictions for the actual business.
| Evidence group | Question it supports | Link to preserve |
|---|---|---|
| Activity and identity | Which ship, voyage, port activity and period are involved? | Transaction and reporting references |
| Scope assessment | What treatment was used and why? | Applicable review and supporting source |
| Emissions information | What quantity evidence was available? | Method, status and relevant record version |
| Calculation | How were inputs transformed into the estimate? | Formula, units, assumptions and output |
| Allowance activity | What purchase or transfer actually occurred? | Transaction confirmation and reconciliation |
| Commercial allocation | Why was an amount assigned or requested? | Actual terms, decision and supporting calculation |
| Correction history | What changed after the earlier decision? | Earlier record, reason and revised result |
Use the map to test completeness. A folder can contain many documents while still lacking the connection between the quantity used and the transaction being charged.
Preserve the calculation as well as the result
Keep the input values, units, formulas and material assumptions used for the decision. A saved total without its calculation basis is difficult to review, especially after the original author has moved on.
Where a model draws information from another system, preserve the relevant input snapshot or an authorised reproducible reference. A live link that now returns updated data may not reproduce the earlier result.
Explain manual adjustments. A reviewer should be able to tell whether an adjustment corrected an error, represented an agreed commercial treatment or introduced a planning assumption.
Do not make the archive depend entirely on a particular person's memory or private mailbox. The evidence should remain retrievable through the approved business process and access controls.
Fictional case: the invoice survives but the basis disappears
Imagine a fictional desk receiving a question about an earlier ETS-related commercial adjustment. The invoice and payment record are available, but the spreadsheet now contains updated operational inputs and a different price assumption.
The desk can show what was requested and paid, but cannot reconstruct the basis presented when the amount was approved. The latest spreadsheet is not reliable evidence of the earlier calculation merely because it uses the same filename.
The improved archive retains a decision snapshot with its inputs, formulas, supporting references and status. Later corrections are stored as revisions linked to the original rather than replacing it silently.
When a similar question arises, the reviewer can distinguish the original estimate, the reason for the correction and the resulting commercial action. That does not resolve every possible dispute, but it makes the factual basis available for the authorised assessment.
The lesson is specific: proof of payment and proof of the calculation answer different questions. Both may be needed, and neither should be assumed to contain the other.
Handle corrections without preserving confusion
Retaining history does not mean treating every version as equally current. Mark which record is operative for the present purpose and explain how it relates to earlier versions.
If a correction affects a downstream calculation or request, retain the link to that consequence. Otherwise the archive may show a corrected source while leaving an earlier commercial amount unexplained.
Where the correction is limited, preserve that limit. Updating a voyage input does not necessarily change an executed allowance purchase or an already reviewed contractual price basis.
The archive should therefore support both historical reconstruction and current use. Clear status labels help prevent an obsolete file from being reused as though it were the approved present position.
Set retention periods through an explicit assessment
Different record categories may serve regulatory, contractual, accounting or dispute-related purposes. The responsible legal and records functions should determine the applicable retention requirements and any restrictions on deletion.
Do not apply an arbitrary period to the entire ETS folder simply because it is convenient. Identify the category, relevant trigger, required duration and authorised disposal process under the applicable requirements.
Where a preservation instruction applies, ensure that routine deletion does not remove the affected evidence. The exact scope should be determined by the responsible function rather than inferred casually by the commercial desk.
Review the schedule when the business process, applicable requirements or storage arrangement changes. A retention policy that no longer matches the actual evidence flow can create gaps despite apparently orderly filing.
Test retrieval and controlled access
Select an archived decision and ask an authorised reviewer to reconstruct its basis without help from the original preparer. This reveals missing links and inaccessible records more effectively than counting files.
Check that the reviewer can distinguish the forecast, reported information, verified evidence and actual transaction records. If the statuses are unclear, improve the index and naming conventions.
Access should match the person's responsibility and the information's sensitivity. Broad circulation of the full archive is not necessary when a reviewer needs only a defined evidence package.
Record retrieval failures and fix the underlying cause. A broken source reference, departed custodian or inaccessible export format can undermine an otherwise complete retention policy.
Common mistakes
Keeping only the final invoice. Preserve the quantity, price and allocation evidence behind it.
Using live inputs to reconstruct an old decision. Retain the relevant historical snapshot or reproducible reference.
Erasing the earlier basis when correcting a model. Link the correction to the original and its consequences.
Choosing a universal retention period without review. Assess the applicable requirements for each record category.
Where Zeaclub fits
Zeaclub offers digitalised procedures across the voyage workflow.
Zeaclub provides 24/7 operating systems and worldwide coverage.
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 the final spreadsheet sufficient?
Only if it preserves the necessary inputs, method, evidence links and status for the decision. A current workbook may no longer reproduce an earlier calculation.
Should every old version remain usable?
No. Preserve required history while clearly identifying the operative record for the present purpose and preventing obsolete versions from appearing current.
Who should decide retention duration?
The responsible legal and records functions, using the applicable regulatory, contractual and other requirements. This framework supplies no universal duration.
Why keep purchase evidence separately?
An actual allowance transaction and a commercial allocation answer different questions. Their relationship should be documented rather than assumed.
How can the desk test its archive?
Ask an authorised reviewer to reconstruct a selected decision from the retained evidence. Record missing links, unclear statuses and retrieval failures, then correct them.