Freight document intake

One job record built from the invoice, the packing list and the bill of lading, before cutoff

• Domain: Supply Chain & Logistics
• Moment: Before the work starts
• Customer: A chemical-industry logistics operator

Build one reliable job record from every shipment document.

The situation

A logistics operator moving chemical freight receives, for every shipment, a commercial invoice, a packing list and a bill of lading. They come from three parties, in three layouts, as scans, phone photographs and PDFs buried inside email threads.

Job creation is manual and the cutoff is fixed. Customs submission, carrier booking, and port deadlines often arrive soon after the documents.

So the operator types. The checking that should happen between three documents written by three parties about one shipment does not happen.

What breaks today

The three documents disagree and nothing reconciles them. Gross weight appears on the packing list, on the bill of lading and sometimes on the invoice. Package counts, container numbers and marks appear on two of the three. Whichever document is open when the job is created becomes the truth downstream.

Scans are photographs of paper. Rotated, skewed, stamped across the figures, signed over the total, rescanned until a decimal point is a smudge. One attachment routinely holds an invoice and its packing list together, and a bill of lading spans several pages.

Party matching depends on names. Shipper, consignee, and notify party arrive as free text with branch suffixes, abbreviations, and inconsistent spelling. Matching them to a customer or agent often depends on individual memory.

Chemical freight carries a second document set. Hazard class, UN number, packing group, the dangerous goods declaration. When that is not on the face of the documents somebody has to find it, and the cost of being wrong is not a rekey. It is a rejected declaration or a refused container.

Cutoff converts checking into typing. Late documents mean the job is built from what was legible and repaired afterwards. The repair lands after the booking is made and after the declaration is filed, and by then the cost is an amendment, a re-manifested container or a demurrage conversation.

What Manuel does

Intake from the channels the documents actually use. The shared mailbox, forwarded threads, portal downloads and folders. Where the job system sits behind the firewall, a runtime agent runs on-premise and the cloud never reaches inside.

Classification by document. Each attachment is separated into its invoice, packing list, bill of lading, certificate, or declaration. A multi-page document stays together, while a file holding several documents is split.

Extraction across all three types. Manuel reads booking and bill of lading references, container and seal numbers, package details, weight, volume, commodity and tariff codes, incoterms, ports, and required dangerous goods fields. A new shipper layout is added to the existing intake process.

Assembly into one job record. The record is keyed on the shipment, so a late document attaches to the open job.

Cross-document validation, which is the actual control. Package count on the packing list against the bill of lading. Gross weight across every document that states it, inside a defined tolerance. Container numbers against their check digit. Consignee and shipper resolved against the customer and agent masters. Dangerous goods fields present and consistent whenever the commodity requires them.

Completeness against the job type, before cutoff. Rules define which documents and fields are required and which values must agree. A held shipment names the missing document.

Only exceptions reach a person. Each case states the mismatch and its location, such as conflicting gross weights, a failed container check digit, or an unresolved consignee. The source documents appear beside the decision.

What the customer gets

The first action of the day changes shape. It used to be typing against a clock. It becomes deciding on a short list of shipments where the documents conflict, with both values and both source documents on screen.

The disagreement is found before the declaration and before the booking, which is the only point at which it is cheap to fix.

This one is delivered and running, and the customer's operating figures are theirs. What we baseline in discovery: shipments a month, documents per shipment, minutes from arrival to job created, the share of jobs amended afterwards, and how often the three documents disagree.

What stays with your existing systems

The job system stays the system of record. Manuel does not make the booking, file the declaration or speak to the carrier. The customs broker relationship stays where it is.

Email stays where it is. Nobody moves to a new inbox and no mailbox is handed over: access is by delegated user permission, scoped to the addresses the documents arrive at.

What a first scope looks like

One trade lane or one customer, and a historical set of document packs you have already processed. Files first, read-only, nothing in the path of a live cutoff.

Manuel builds the canonical job record and we compare it against the jobs your team created, field by field. You see where it agrees, where it disagrees, and what it would have caught.

Related: Job margin protection / AP invoice control / Enterprise data intake