The evidence is in five systems and an inbox
The invoice is in the carrier's portal. The gate events are in the terminal's system, which may or may not export history. The empty-return proof is on the trucker's EIR, which is a photo of a piece of paper. The free-time terms are in a PDF contract someone in procurement has. The argument so far is in email. D&D Pilot takes all of that as it is.
What it reads
| Source | Formats | What is extracted |
|---|---|---|
| Carrier / terminal invoices and statements | PDF (text or scanned), XLSX/CSV portal exports | Container, charge type, period, days, rate, amount, tier, currency |
| B/L, sea waybill, booking confirmation | PDF, EDI 301/310 | Container, type/size, POL/POD, Incoterm, haulage arrangement, shipper/consignee, free-time notes |
| Terminal and depot events | EDI 315/322, portal CSV, screenshots | Discharge, available, gate-out full, gate-in empty, holds, with timestamps and source |
| EIR | Photo, PDF | Gate-in/out timestamps, container and chassis numbers, condition |
| Customs and government notices | PDF, email | Hold placed / released |
| Tariffs and contracts | Free-time clauses by trade lane, container type, calendar basis; rate tiers; exclusions | |
| EML/MSG/pasted | Claims, concessions, evidence cited, open questions |
Provenance is kept
Every event on the timeline carries its source and the agent's confidence in it. An EDI event outranks a screenshot; the file says so when a weaker source is all there is.
What it never does
It does not log into carrier or terminal portals, does not pull data on its own schedule, and does not send anything to a carrier. Upload, forward or paste — and nothing leaves without a person pressing send.