The load that was "too late and damaged".
A haulier and a terminal share one logbook of deliveries. Three years later, a claim comes in.
The TMS forwards the delivery
Reference, container, registration plate, time, delivery note. Vidimus hashes, signs with the system key, encrypts the note in the vault. Five minutes later: the group is anchored and timestamped; for customer organisations, usually also qualified (eIDAS) within six hours.
The terminal confirms on the phone
Reception receives a share link and confirms: "received without reservation". Signed with a key on the terminal's own device. That confirmation is itself anchored — now it is in the file of both parties.
The claim — and the doubt
Claim from the recipient: too late, damaged. The carrier's planner has doubts: has that delivery in the TMS been changed in the meantime?
Open Proof
Eight checks, all green — content recomputed, place in the group, signature, Vidimus's signature, ledger, timestamp, qualified timestamp, Bitcoin. And the terminal's confirmation, with its time, is right next to it.
What the carrier can show
The carrier does not send "our word" but the bundle and the verification link. The counterparty's insurer can have its IT people recompute it: unchanged since anchoring, with the terminal's confirmation next to it.