Chain of custody for trade documents
The shipment closed in 2019. The question arrives in 2031.
Lumenpath keeps a sealed, readable record of who held each document, what they did to it and what it looked like at the time. When someone asks years later, the answer is already written down.
- Six
- document types covered out of the box
- Ten years
- default retention, longer on request
- Seven
- checks behind every readiness score
- No account
- needed to verify a handover packet
Signing a document is now easy. Proving what happened to it afterwards is not.
A document passes through six organisations and four systems before it is filed. Each one keeps its own copy, its own log and its own idea of what the final version was. None of them kept the part a reviewer will ask for.
The trail is reconstructed, not kept
Someone digs through mailboxes and shared drives to rebuild a sequence that was obvious at the time.
Every reviewer starts over
The bank, the insurer and the auditor each do the same work, and each reaches a slightly different answer.
The evidence expires quietly
Certificates lapse, formats age out, staff leave. Nothing fails loudly until the file is needed.
What a sealed record looks like, from issue to review
The same entry that a forwarder writes today is the entry an auditor reads a decade later. Nothing is rewritten in between.
- 01
Issued
Exporter issues the document and seals it on entry
- 02
Endorsed
Freight forwarder adds an endorsement, trail continues
- 03
Presented
Bank receives a handover packet under a letter of credit
- 04
Cleared
Customs broker opens a scoped access window
- 05
Shelved
Record moves to retention with a ten-year rule
- 06
Reviewed
Auditor verifies the seal in 2034 without calling anyone
Six parts. Turn on the ones your documents need.
Most teams start with the custody trail and the seal, then add handover packets once a bank or a broker asks for one.
Who held the record
Custody Trail
Every handover is written down as it happens: who sent the document, who received it, on which system, at what time. The trail is append-only, so a correction shows up as a new entry rather than a quiet edit.
- Append-only entries with the previous entry referenced by hash
- Handover recorded on both sides, not only by the sender
- Corrections logged as amendments with a reason field
Six documents, and the way each one usually fails a review
| Document | Passes through | Where the evidence breaks |
|---|---|---|
| Bill of lading | Exporter, carrier, bank, consignee | Endorsement chains get rebuilt from email threads when the original is questioned. |
| Certificate of origin | Chamber of commerce, exporter, customs | The issuing body changes its stamp format and the old version cannot be validated. |
| Inspection report | Surveyor, buyer, insurer | Photos and the report itself are stored in different systems with different retention. |
| Customs declaration | Broker, authority, importer | Amendments overwrite the earlier filing, so the reason for the change disappears. |
| Letter of credit set | Issuing bank, advising bank, exporter | Discrepancy notices are decided in days and defended years later from memory. |
| Warehouse receipt | Operator, financier, trader | The same goods get pledged twice because nobody can see the current holder. |
Three rules we do not bend
Sit beside the systems, not on top of them
Your TMS, your bank portal and your document management system stay where they are. Lumenpath records what moves between them.
A record nobody can read is not evidence
Plain summaries next to the cryptography. If a reviewer needs us to explain a packet, the packet failed.
Say what is missing
Where the trail has a gap, we show the gap. A tidy report that hides a hole costs more than an honest one.
Bring one file that failed a review. We will walk it back to its origin.
Send a document that an auditor, a bank or a counterparty questioned. We will show what Lumenpath would have kept, and what nobody can reconstruct any more.