History — the receipt for everything already done
Splitting and validation records, and how to read a full extraction: senders, bounding boxes, and charges that reconcile.
Two tabs, two stages
History separates the pipeline's two completions. Splitting covers documents broken apart and submitted to PPU; Validation covers orders checked against the TMS and passed to 3G. A document can appear in both, at different times, which is the point — the tabs are stages, not categories.
Opening a record
The row action menu offers View, Detailed View, and Download. Detailed View is the one that matters here: it opens the extraction record, which is the structured read KnowDoc produced from the page. The breadcrumb switches to Dashboard › Documents when it opens, because the record itself lives under Documents — expected, not a navigation bug.
What a record contains
Three layers, and the third is what makes the record defensible.
- Sender & metadata — Who sent it, when it arrived, which carrier profile read it.
- Bounding boxes — Where on the page each extracted value was found.
- Charge lines — The structured financial read — quantities, unit prices, totals.
Bounding boxes are the citation
Every extracted value carries the coordinates it came from. That turns "the system says the total is X" into "the system says the total is X, and here is the pixel region on page 2 it read it from." When a carrier disputes a figure, you are not defending a model's judgement — you are pointing at their own page.
The arithmetic that proves itself
The walkthrough closes on a document whose numbers reconcile three separate ways. The freight line's own quantity times unit price gives 2 × 419.19 = 838.38. The fuel surcharge line states 57.5%, and 57.5% of 838.38 is 482.07 — exactly the extracted FSC. Add the $50 accessorial and 838.38 + 482.07 + 50 = 1,370.45, exactly the total amount due. Every extracted figure is checkable against another extracted figure.
Proof-of-delivery flags
The record also carries POD flags read off the page — signature present, carrier stamp present, and so on, each answered independently. The filmed document has a signature but no carrier stamp. That granularity is what lets a rule say "auto-process if a signature is present" rather than the blunter "auto-process if a POD is attached."
Why nothing here needed a human
That is the argument the screen makes. A document that reconciles against itself, cites its own page coordinates, and satisfies its POD rule has already answered every question a reviewer would have asked. The reason to open History is not to re-check that work — it is to be able to show it, months later, to someone who wasn't there.
Ready to build your own?
Start free and ship your first app in minutes — or have us set it up with you.
More guides in Inbox & Documents
More resources