Home / How It Works
How It Works: One Shipment's Documents, Start to Finished
This page walks a single shipment's documents through the loop — from bill of lading to freight invoice. The example is an import shipment with customs paperwork in the middle, but the same five stages apply to any shipment that travels with documents.
Intake: arrival is a system event, not a favour
The bill of lading is issued at pickup, and a copy reaches the office by email the same afternoon. In a manual process it would sit in a shared inbox until someone claimed it. In the loop, arrival is intake: the document is captured the moment it lands, tied to the shipment, and queued for processing — and the same happens when the broker's customs paperwork and, later, the signed proof of delivery arrive.
Nothing is sorted by hand, and nothing waits on a person noticing it. From this point on, each document's location and status are always known.
Classification & extraction: the documents are read
Next, the processing engine — MaxxOwl™ SI on the MaxxLogix platform — reads each document. Classification comes first: is this the bill of lading, a customs form, a delivery receipt? The engine decides from the document's layout, language, and content — not from a file name or a folder somebody chose.
Extraction follows: shipment references, weights, piece counts, charges, and delivery details are lifted out as structured data. Skewed scans and multi-page attachments are handled as part of the read, and every extracted value carries a confidence level that the next stage puts to work.
Validation & matching: documents are checked against each other
Extracted data is only useful if it can be trusted, so the loop checks it first: the customs set for completeness. Then, when the carrier's freight invoice arrives after delivery, it is matched against the shipment order and the signed proof of delivery using N-Way Match™ — so a rate, weight, or accessorial charge that disagrees is caught here, not in a dispute weeks after payment.
Anything that fails a check becomes an exception: it leaves the straight-through path and is routed to a person together with the documents, the extracted data, and the specific reason it was flagged.
Workflow: work moves by rule, not by inbox
A matched set moves into workflow: the verified freight invoice proceeds toward payment, and the completed file supports billing the customer. Exceptions follow their own routes — by type, by desk, by value — and each is a task in a queue, not a thread in someone's email. Reviewers work in Outcome Workspace™, where the documents and their data sit side by side and a decision is a single action, recorded with a name and a timestamp.
If a step stalls — a proof of delivery still outstanding, an exception unanswered — the workflow knows. Reminders and escalations are part of the route itself, not a manager's memory.
Outcome: the finish is recorded, not assumed
When the last item lands, the loop closes. The shipment file holds the bill of lading, the customs paperwork, the signed proof of delivery, and the matched freight invoice — and the outcome, what got done with them, is written to the record: what was matched, what was excepted, and how long each stage took.
That record is the point. It is what Outcome Analytics™ reports on: volumes by document type, exception rates, match results, and the outcomes each process produces. Improvement stops being a guess, because the loop keeps its own evidence.
The other front door: forms and portals
Not everything arrives as a document. A request submitted through a form or a portal — MaxxLaunch™ on the MaxxLogix platform — arrives as structured data already, and joins the same workflow at the validation stage. From there the loop treats both doors identically: checked, routed, worked, and recorded. Documents and data, one loop.
Same loop, every shipment
Every shipment your operation runs can be walked through the same five stages. The documents, rules, and matches change from lane to lane; the loop doesn't. That consistency is what makes the outcomes comparable — and what makes a platform different from a pile of point tools.
← Back to the overview: intelligent logistics automation for freight documents
Put your shipment documents through the loop
The stages above run on MaxxLogix — Outcome Cloud™, MaxxOwl™ SI, Outcome Workspace™, and the rest of the platform, with capacity published in SI Units and no surprise overages. See it at maxxlogix.com.
Visit MaxxLogix