Vidimus
Explainer videos NL Start free

VIDIMUS/CASE FILES/TRANSPORT, PORT & LOGISTICS

Delivered. "Never received — or damaged."

A load delivered, a container through the gate, a parcel signed for — and weeks later the dispute: too late, damaged, never arrived. Every link in the chain keeps its own history. This page shows how you create one shared proof layer where carrier, terminal and recipient see the same facts.

Gate-in 09:41 (UTC+2), container at the terminal. The recipient claims: arrived after the cut-off, extra costs. The terminal's history says 09:41 (UTC+2), the carrier's 09:38 (UTC+2), the recipient has an email from 10:15 (UTC+2). Three systems, three clocks — and the costs are split according to who shouts loudest.

01 / THE PROBLEM

Why this goes wrong so often.

A

Every party its own system, every party its own clock

TMS, terminal system, the recipient's ERP: all with their own time, all changeable by their own administrator.

B

The reservation comes too late or never

Under the CMR, whoever makes no reservation at delivery largely loses their position — but whoever does make one must also be able to prove it.

C

The chain is long, memory is short

In a claim months later, nobody can still reconstruct exactly what happened when. Whoever is best documented wins.

02 / TODAY

What you can already do now — even without Vidimus.

  • At delivery, make a dated reservation on the consignment note for visible damage; for damage that is not visible, in writing within 7 days (CMR Art. 30).
  • Record gate-in/gate-out and deliveries automatically and keep the raw events, not just daily summaries.
  • Agree in your contracts which record applies between the parties (evidence clause) and which time source.
  • Take photos at delivery — with the recipient's signature at the same moment.
03 / THE LAW

What the law says.

CMR Convention Art. 9 & 30

Until proven otherwise, the consignment note is proof of the contract and of receipt. Without a reservation at delivery, the goods are presumed to have been delivered as described; report visible damage immediately, hidden damage within 7 days. Even a suspected "too late" requires a written reservation within 21 days.

Art. 8.11 of the Belgian Civil Code

Between businesses, evidence is free: scans, system histories and photos are admissible and are weighed. A record in which none of the parties can change anything unnoticed is stronger.

General information, not legal advice. Vidimus supplies evidence; how much weight it carries is for the court to assess — and that weight is exactly what anchoring increases.

04 / ANCHORED

What changes.

  • Every gate scan, delivery or handover gets a fingerprint when it is created and is anchored within five minutes with an external timestamp; for customer organisations, each group also receives a qualified timestamp (eIDAS), usually within six hours — one clock for the whole chain, belonging to no one in particular.
  • Carrier, terminal and recipient look at the same ledger: no more "my history against yours".
  • In a physical handover, both parties sign on the phone (QR handover), with photos; anyone can verify the evidence bundle independently.
recordgate-in GI-88412
vehicleregistration plate + container no.
sourcegate system · automatically via api
moment09:41:03 (UTC+2) · anchored within 5 min.
anchoredmerkle root + timestamp + bitcoin anchor
THE MATHS

Eight disputed deliveries a year × 6 hours × €75, plus an average of €7,500 in shared costs per dispute ≈ €3,600 in hours and €60,000 in costs that you "absorb" for lack of proof. One shared proof layer makes most disputes unnecessary before they even start.

05 / DISSECTED

One gate scan, from start to proof.

Fictional example: driver Tom Peeters scans at 09:41:03 (UTC+2) at Kaai 1742. On the left what is created technically, on the right what it means in plain language. The fingerprint and the Merkle root really were calculated on this record.

01 · the scan

What you already have

Your gate system already records this today. The problem is not the record, but that it lives in one system that can be changed afterwards.

driver Tom Peeters · BADGE-4471 · 1-ABC-123 · MSKU 452 118-0 · gate-in GI-88412 · Kaai 1742 · 09:41:03 (UTC+2)
02 · the fingerprint (SHA-256)

Like a human fingerprint

Unique to exactly this record, and you cannot reconstruct the record from it. Change one character — 09:41:03 (UTC+2) becomes 09:41:04 (UTC+2) — and the whole fingerprint is different. That is how you see later whether anything was changed.

f7585ccf75a163b359933be611f97fe68ba39b5ca7e6ec1ece23972ee50203fc
03 · who: the signature (Ed25519)

A signature from whoever holds the key

Only whoever holds the key can sign like this; anyone can check that it was them. That establishes who submitted the scan.

CN=gate-01.terminal-x.be · signature 3045a1…e8f2 (64 bytes)
04 · when: the qualified timestamp

A postmark — from someone else

Not our clock and not yours. Within five minutes, an external timestamping service stamps it; for customer organisations, GLOBALTRUST, a qualified trust service provider on the EU trusted list, also puts a timestamp on the group, usually within six hours. Neither of them has anything to gain from it. Adjusting a time afterwards therefore stands out.

external timestamping service (third party) · stamped 09:46 (UTC+2) · qualified per group, for customer organisations · serial no. 0x5b3f…21
05 · anchored: Merkle → ledger

One anchor for a whole stack

All scans of those minutes are combined into one root fingerprint; it receives the timestamps of step 04 and goes into Bitcoin via OpenTimestamps, a public register in which a change stands out for anyone who checks, even if we were to try. Each individual scan can still be shown, through its place in the stack.

root b96f20a5…7ac7e363 · timestamp + Bitcoin anchor (OpenTimestamps)
06 · the original

A vault with a retention lock

Every original is stored encrypted, in storage that does not allow deletion or overwriting until the end of the retention period, not even at our request. If it has to go after that, or for privacy reasons, the content key is destroyed: the file is unreadable for good, while the fingerprint still proves that something was there.

GI-88412.json + gate-foto.jpg · AES-256-GCM · non-overwritable · 7 years
07 · the evidence bundle

A file any expert can check for themselves

The counterparty, the auditor or the court does not have to believe us: with standard software, they check that this scan existed at that moment, submitted by gate-01, and has not been changed since.

hash recomputed · path → root · root = tx · timestamp — everything matches

Person, company, registration plate and container number are made up. The SHA-256 and the Merkle root really were calculated on the record shown; signature, timestamp and tx id are illustrative values.

06 / QUESTIONS

FAQ.

Do all parties in the chain have to take part?

No. Anchoring only your own records already strengthens your position: your records are then the only ones for which it can be checked that they have been unchanged since anchoring. If partners take part, everyone looks at the same facts.

Does this work with our TMS/terminal system?

Yes — via API or webhook we forward a copy of every event; nothing in your system changes.

What about the e-CMR?

Anchoring complements the (e-)CMR: the consignment note remains the contractual document; we make the records around it — scans, times, photos, reservations — recomputable for every party.

How we start: your first logbook today, the first 100 records free.

You create your account in two minutes, no payment details needed. A director identifies your company once with the Belgian eID; then you create your first logbook in a few minutes. The first 100 records a month and the first measurement source are free. After that, you pay per record or per measurement source, with a minimum of €19 a month.