Bill of lading processing: the fields, the checks against the booking, invoice and packing list, and the TMS record

A bill of lading is a receipt for the goods, evidence of the contract of carriage and, when it is negotiable, a document of title. The Hague-Visby Rules say what it must show once the carrier has the goods and the shipper asks for it: the leading marks, "either the number of packages or pieces, or the quantity, or weight, as the case may be, as furnished in writing by the shipper", and the apparent order and condition of the goods (Article III(3)). The US Carriage of Goods by Sea Act has the same list in its section 3(3) (COGSA).

Two consequences shape the whole process. First, those particulars are the shipper's: the shipper "shall be deemed to have guaranteed to the carrier the accuracy" of the marks, number, quantity and weight it furnished (Article III(5)). The check that matters is therefore against the shipper's own documents, the commercial invoice and the packing list, not against the carrier. Second, the bill is prima facie evidence of what was received, and "proof to the contrary shall not be admissible when the bill of lading has been transferred to a third party acting in good faith" (Article III(4)). An error that reaches a buyer or a bank can no longer be corrected against them. That is why the draft, before issue, is where the checks belong.

The carrier need not state particulars it has "no reasonable means of checking" (proviso to Article III(3)): hence "said to contain" and "shipper's load and count" on a container it never opened, a practice US manifest rules also name (19 CFR 4.7a(c)(3)). The count is yours.

Under Hague-Visby, unless a value was declared, the carrier's liability is capped at 666.67 units of account per package or unit, or 2 per kilogramme of gross weight, whichever is higher (Article IV(5)(a)); the unit is the IMF's special drawing right (SDR). For a container, "the number of packages or units enumerated in the bill of lading as packed in such article of transport" counts; otherwise the container itself is the package (Article IV(5)(c)). The count on the bill is what the limit is computed on, not the count on your packing list.

Under US COGSA the limit is $500 per package unless a higher value is declared (section 4(5)); what counts as the package in a container is for the court, so the same check applies. Either way, this is a reason to check the count, not legal advice on a claim.

The shipment record holds four groups of data, each read once and checked before it is written:

• The document. Number, type, paper or electronic, originals, status (draft, approved, issued, surrendered), dates, and the source file or eBL reference attached to the record.
• The parties. Shipper, consignee or "to order", notify parties, each resolved to one existing organisation in the TMS. A party that matches none or several is held.
• The routing and equipment. Vessel, voyage, ports and places; each container with its size-type code and seals.
• The cargo and terms. Per container: marks, packages and kind, description, HS codes, gross weight and volume with units; freight terms and charges.

On a consolidation, house bills are written under their master and their packages and weights summed against it, container by container. Filings use the same data. In the US the carrier's cargo declaration must reach CBP 24 hours before loading at the foreign port, and a licensed or registered NVOCC with an international carrier bond can transmit its own house data directly (19 CFR 4.7(b)(2) and (b)(3)(i)). For the EU's ICS2, DCSA added more than 190 attributes to its shipping instructions in February 2025 (DCSA), and its model records who files the house bill: the house filer itself or the carrier on its behalf.

Write each record once: store the bill number with it, so that a retry after a timeout finds the record instead of creating a second shipment. How that works in CargoWise, through eAdaptor and its organisation codes, is in the guide to CargoWise data entry automation; for other systems, see TMS data entry automation.

Automated processing prepares each of these decisions with the evidence beside it. It does not take them.

• Approving the draft. Once a negotiable bill is with a third party in good faith, its particulars are conclusive against the carrier (Article III(4)), and the shipper has guaranteed them (III(5)). Approval is a person's act.
• Which document is right. When the bill, the invoice and the packing list disagree, which one to correct is a commercial question for the shipper, not a data question.
• Clauses and remarks. A remark on damaged goods or packaging, or a clause the buyer or bank may refuse.
• A type or a term that does not match the sale. A straight bill where the credit needs a negotiable one, collect freight on a C rule.
• New parties and new routings. A consignee or notify party not in the TMS, a port not in the booking.
• Delivery without the original bill. Always a person, and usually your management or insurer as well.

Four routes remove the reading and keying, and a desk usually ends up with two or three of them, by carrier and customer:

• Structured data from the carrier. A carrier on DCSA's API, or an eBL platform, sends the bill as fields. Nothing to read; the checks and the TMS write remain.
• Your TMS's own capture. Examine what it already reads before buying anything; for CargoWise, the guide linked above starts there.
• Template capture (OCR with a layout per carrier). Reads the layouts you set up and stops at a new one. See OCR vs LLM for document extraction.
• Document AI or an agent connected to the TMS. Reads any layout, then runs the comparisons and writes the record, holding what fails. This is what Mirage's bill of lading processing does.

Test any of them on a month of your own bills, bad scans and house bills included, in parallel with the desk, counting holds and errors after entry; the method is in the document automation pilot guide. The other documents of a shipment (invoices, packing lists, customs and proof of delivery) are covered in manual vs AI freight document processing.

• Most of your carriers already send data. If bills arrive through DCSA's API or an eBL platform, what remains is the checks and the TMS write: build those, not a reader.
• The volume is small. A few bills a week, checked without a backlog, leave little to remove.
• The booking data is not in the TMS. With nothing to compare against, automated reading only moves the typing elsewhere. Fix the booking record first.
• Nobody has written the checks down. A process cannot apply a tolerance that exists only in someone's head.
• The work is mostly bulk or charter party bills. Their quantities and clauses follow other practices, outside this guide.

The opposite case, many carriers, scanned bills, houses under masters and bookings in the TMS, is where automation pays: Transwin cut manual data entry on freight documents by 70% (case study).