Invoice Data Extraction Logo
Invoice Data Extraction
Start Extraction
Pricing
Extraction Guide
API
Sign inCreate account
Sign inCreate account
Start Extraction
Pricing
Extraction Guide
API
  1. Home
  2. Articles & Analysis
  3. Invoice Fundamentals
  4. Bill of Lading vs Commercial Invoice vs Packing List

Bill of Lading vs Commercial Invoice vs Packing List

Compare bills of lading, commercial invoices, and packing lists, see which fields should align, and resolve legitimate shipment-document differences.

Published
Aug 30, 2026
Updated
Aug 30, 2026
Reading Time
15 min
Author
David Harding
Topics:
Invoice FundamentalsLogisticsshipping documentscustoms documentationdocument reconciliation

On this page

In a bill of lading vs commercial invoice vs packing list comparison, the commercial invoice records the sale and customs value, the packing list records the physical pack-out, and the bill of lading records the carrier's receipt and carriage details.

The three documents should tell one coherent shipment story, but they do not need to repeat identical values in every field. The buyer may differ from the consignee, an invoice quantity may be expressed in units while the packing list uses cartons, and a carrier may record pallets as handling units. The useful test is whether each value agrees with the role and level that document describes.

QuestionCommercial invoicePacking listBill of lading
Who usually issues it?Seller or exporterSeller, exporter, or packing partyCarrier, or its agent, based on shipper-provided details
What is its primary purpose?Records the sale, amount due, currency, and declared transaction detailsDescribes what is physically packed and howEvidences carrier receipt and records the agreed carriage details
Does it show financial values?Yes, including prices, currency, and total valueNormally no sales prices or amount dueNot a sales invoice; freight charges may appear depending on the form and arrangement
What physical detail does it carry?Goods and invoice quantitiesItem, carton or package, weight, and dimension detailCarrier-facing package or handling-unit counts, weights, and goods description
How is it used for customs?Supports valuation and other declaration dataSupports examination of package contentsSupports transport, arrival, and carrier-receipt evidence
Can it affect cargo release or title handling?Not as a transport title documentNoYes, depending on whether it is a straight bill, order bill, or non-negotiable sea waybill

This division is reflected in UK government guidance on international trade documents: the commercial invoice helps customs determine controls, duties, and taxes; the packing list shows what should be in each carton; and the bill of lading provides evidence that the carrier received the goods. It is a practical illustration of the document roles, not a universal statement of what every country or transport mode requires.

What each document governs, and what it does not

The commercial invoice is the seller's transaction record and request for payment. It identifies the parties to the sale, describes the goods, states quantities and prices, names the currency, and calculates the amount due. Customs authorities also use its declared transaction information when assessing value, duties, taxes, controls, and admissibility under the rules that apply to the shipment.

The packing list describes the physical pack-out rather than the debt. It can show which items sit in each carton, how many cartons or packages make up the shipment, and the net and gross weights and dimensions. It should not be used as a substitute for the commercial invoice because it normally carries neither line prices nor an amount due. A fuller two-document treatment is available in packing list and commercial invoice differences.

The bill of lading belongs to the carriage record. It evidences the carrier's receipt of the goods and records details such as the shipper, consignee, ports or places of receipt and delivery, goods description, packages or handling units, weight, and routing. It may also embody the carrier's contract of carriage or provide evidence of its terms, depending on the transport arrangement and governing law. It does not prove the supplier's price or establish what AP owes.

The form of the bill matters when cargo is released:

  • A straight bill of lading names a consignee and is non-negotiable. Release procedures still depend on the carrier, applicable law, and whether originals or other evidence are required.
  • An order bill of lading is negotiable and can transfer rights through endorsement and delivery. Its possession and endorsement therefore require tighter control.
  • A sea waybill is non-negotiable and supports release to the named consignee without presentation of an original negotiable bill. It is evidence of receipt and carriage, but not a document of title.

Calling every bill of lading a negotiable title document is therefore wrong. The reviewer must identify the actual form before deciding what it means for release or document control.

A packing slip is usually a fulfillment or receiving document placed with goods, especially in domestic trade. An export packing list is the more formal package-level record shared among the exporter, forwarder, broker, carrier, and consignee for an international shipment. The labels are sometimes used loosely, so the fields and intended use matter more than the filename.

A delivery note sits later in the physical flow. It accompanies or records delivery and can capture what the recipient accepted, rejected, or received short. By contrast, the bill of lading records carrier receipt and carriage. Teams resolving proof-of-receipt questions should look at how a delivery note supports receiving, not expect the bill of lading to confirm the final warehouse count.


Field-by-field authority and exception matrix

No document universally overrides the other two. The better question is which document is the primary evidence for the decision being made: the invoice for the sale and declared value, the packing list for the physical pack-out, or the bill of lading for carrier receipt and carriage.

Field familyWhere it commonly appearsExpected relationshipA legitimate differencePrimary decision evidenceWhat to check next
Seller, shipper, buyer, importer, consignee, notify partyParty fields appear across all three, but not every role appears on eachNames, addresses, and roles should fit the trade and transport arrangementThe seller may use a separate shipper; the buyer may not be the importer or consignee; a broker or local agent may be the notify partyCommercial invoice for buyer and seller; bill of lading for shipper, consignee, and notify partyConfirm the contract, purchase order, importer instructions, and party-role mapping before treating a name difference as an error
Invoice, PO, booking, and bill of lading referencesInvoice and PO on the commercial invoice; PO may appear on the packing list; booking and BOL number on the transport recordThe references should create an unbroken path between the order, sale, pack-out, and carriageNo single identifier may be printed on all three documentsEach originating document governs its own numberUse booking, container, shipment, or supplier references to establish the missing crosswalk
Goods descriptionAll three, usually at different levels of detailDescriptions should refer to the same goods without a material contradictionThe invoice may carry SKU-level detail while the bill uses a broader carrier-facing descriptionCommercial invoice and packing list for item identity; bill of lading for the description accepted into the carriage recordCompare model, SKU, material, use, marks, and package breakdown rather than exact wording alone
Commodity or HTS code and originCommonly on the commercial invoice; sometimes on a packing list or other customs document; not reliably present on every BOLWhere repeated, the code and origin should be consistent with the declared goodsA carrier document may omit the code or use a broader descriptionCustoms declaration and its supporting commercial recordsResolve unexplained code or origin changes with the exporter and broker before filing or payment where they affect duty or admissibility
Item and invoice quantitiesCommercial invoice and packing listThe shipped invoice units should reconcile to the packed item units for the shipment portionA partial or split shipment may cover only part of an invoice or POCommercial invoice for billed units; packing list for packed item unitsReconcile by line, shipment, and receipt rather than comparing only document totals
Cartons, packages, pallets, and handling unitsPacking list and bill of ladingThe packaging hierarchy should be mathematically explainableTen cartons on one pallet can appear as ten packages on the packing list and one handling unit on the BOLPacking list for carton contents; bill of lading for units tendered to the carrierRecord the relationship among items, cartons, pallets, and carrier units
Net and gross weightUsually packing list and bill of lading; sometimes commercial invoiceValues should use the same unit of measure and a compatible scopeGross weight includes packaging; carrier weight may cover a consolidated handling unit; rounding or later measurement may differPacking list for item and package weights; bill of lading for carrier-recorded shipment weightCheck units, net versus gross basis, scope, consolidation, and measurement source
Currency and declared valueCommercial invoice and customs records, not normally the packing list or BOLCurrency, line extensions, and total should agree within the transaction and declaration recordsFreight, insurance, assists, discounts, or customs valuation adjustments may cause a declaration basis to differ from the invoice totalCommercial invoice for the sale; customs entry for the declared customs basisRecalculate the invoice and document any valuation adjustment instead of forcing a three-document match
DatesInvoice, packing list, and bill of ladingDates should follow a plausible sequence for sale, packing, carrier receipt, departure, and issueDocuments can be issued on different days; split shipments can produce several transport dates for one invoiceEach document for its own event dateCheck whether the date names the event it appears to record, not merely whether all dates are equal
IncotermsCommercial invoice and contract records; sometimes repeated elsewhereThe named rule and place should agree with the sale termsA carrier route does not itself redefine the buyer's and seller's cost or risk allocationSales contract, purchase order, and commercial invoiceConfirm the term and named place using how Incoterms appear on commercial invoices rather than inferring them from freight movement
Container and seal numbersBill of lading and packing or loading records where containers are usedIdentifiers should link the packed goods to the transported containerA shipment can use multiple containers or receive a replacement seal that is documented laterBill of lading and carrier or terminal record for carriage; loading record for pack-outInvestigate transposed, missing, substituted, or unexplained identifiers before accepting the chain of custody

Some fields cannot be matched across all three because they belong to only one or two records. A blank invoice value on a packing list is normal; a missing sales price on a bill of lading is not evidence of an incomplete transport document. Reconciliation should compare shared facts where they overlap and preserve the distinct facts each document contributes.

Legitimate differences versus reconciliation exceptions

A non-match is not automatically an error. It becomes an exception when the packet cannot explain why the values differ or how they relate to the same shipment.

Different party names can reflect different roles. A manufacturer may sell to a parent company, ship from a contract warehouse, name a local subsidiary as importer of record, deliver to a third-party distribution center, and list a customs broker as notify party. Those names should not be forced into equality. The reviewer should map each entity to its contractual, customs, transport, or receiving role and investigate only an unexplained substitution or incompatible address.

Quantities can describe different levels. An invoice may bill 1,000 units, a packing list may place them in 50 cartons, and a carrier may receive 5 palletized handling units. All three figures can be correct. The relationship fails when the hierarchy does not add up, the pack-out omits billed units, or the carrier record cannot be connected to the packages under review.

Net and gross weight are different measures. Net weight covers the goods; gross weight includes relevant packaging. Pallets, dunnage, consolidation, unit conversion, measurement method, and rounding can also affect the recorded number. There is no safe universal tolerance. Compare the same basis and scope first, then document why any remaining variance is acceptable for the particular commodity, mode, and control.

One commercial record can span several physical movements. A split shipment may generate several packing lists and bills of lading against one purchase order or invoice. A partial receipt may leave some billed units in transit, rejected, or back-ordered. Dates, quantities, packages, and transport references will differ, but the packet should reconcile each portion and prevent the same units from being received or paid twice.

When matching a bill of lading to an invoice and packing list, escalate a difference if it breaks the shipment story. Examples include an unknown consignee, an unexplained change in goods or origin, billed quantities with no packed or received counterpart, a declared value in the wrong currency, an incompatible route, a container or seal that cannot be traced, or identifiers that connect to another shipment.

The likely consequence still depends on where the shipment is, the transport mode, the contract, and the jurisdiction. A discrepancy can prompt a customs question, but no single mismatch guarantees a customs hold. The same difference might instead affect carrier release, warehouse receipt, or supplier payment.

What a mismatch can interrupt

The same discrepancy can matter to one workflow and be irrelevant to another. Routing it correctly requires identifying the decision at risk.

WorkflowDiscrepancies that matter mostPossible outcomeFirst owner to involve
Customs declaration or reviewDeclared value, currency, goods description, classification, origin, party roles, and supporting-document referencesQuery, request for evidence, amended declaration, or duty and tax reassessmentCustoms broker or trade-compliance owner, with the exporter for source corrections
Cargo releaseConsignee, bill type, endorsement, original-document status, release instruction, freight status, route, or carrier referenceRelease delay or refusal pending the required document or instructionCarrier or freight forwarder
Warehouse receivingPackage count, handling units, weight, marks, container, seal, item quantity, or visible shortage and damageReceiving exception, quarantine, shortage record, or claim evidenceReceiving team, warehouse, carrier, or packer according to the discrepancy
Supplier paymentInvoice and PO references, billed quantity, price, receipt evidence, shipment portion, and duplicate-document riskPayment hold, short-pay, debit note, or request for a corrected invoiceAP and procurement, with the supplier for invoice correction

Do not resolve a discrepancy by silently replacing the source value in a spreadsheet or document image. Preserve what each original record says, note who identified the exception, and establish which party owns the correction.

The supplier or exporter normally corrects its commercial invoice. The packer, origin warehouse, or exporter provides evidence about carton contents and pack-out. The carrier or freight forwarder corrects or explains bill of lading, booking, routing, and release records. A customs broker can explain jurisdiction-specific filing requirements, but should not be treated as the author of a supplier's commercial facts.

The packet should include the corrected document or a written explanation, the date received, and the disposition. If the original was used for a customs filing, cargo release, receipt, or payment decision, retain both versions and record whether a further amendment or operational action was required.


Build an audit-ready shipment packet

An audit-ready packet preserves the source records, the comparison, and the reason an exception was accepted or corrected. A workable method is:

  1. Retain the original files. Keep the commercial invoice, packing list, bill of lading, and any relevant purchase order, booking, customs, delivery, or payment record in their received form.
  2. Assign one packet or shipment ID. Use it to connect documents even when their own reference fields differ.
  3. Capture stable cross-references. Record the invoice and PO numbers, booking and bill of lading numbers, container and seal identifiers where present, package counts, and the source filename and page for each observed value.
  4. Compare by field family. Keep separate columns for the value stated on each document. Do not collapse them prematurely into one supposedly correct value.
  5. Log exceptions and ownership. Describe the variance, its operational risk, the responsible party, and the next action.
  6. Attach the resolution. Preserve a corrected document, written explanation, measurement record, or other evidence, then record the accepted value and why it was accepted.
  7. Record the outcome. Link the review to customs clearance or amendment, cargo release, warehouse receipt, and supplier-payment status as applicable.

At volume, PDF data extraction can turn mixed shipment packets into comparable rows while retaining source-file and page references. Extraction does not decide whether a mismatch is legitimate: party roles, packaging hierarchies, split shipments, and document corrections still require human review.

Teams processing the carriage record separately can use bill of lading extraction and matching as a focused continuation. The packet-level control remains the same: preserve each source value, connect it through stable identifiers, and document the resolution rather than erasing the exception.

Invoice Data Extraction

Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.

Try It Free
Continue Reading

Related Articles

Explore adjacent guides and reference articles on this topic.

Packing List vs Invoice: Key Differences Explained

Packing lists describe what is physically shipped; invoices record what is billed. Learn the key field, workflow, and customs differences and why mismatches matter.

Freight Document Extraction: Logistics Parser Guide

Freight document extraction turns invoices, BOLs, manifests, PODs, and customs forms into structured data for review, audit, and ERP/TMS handoff.

Commercial Invoice Data Extractor: Fields to Capture

Learn what a commercial invoice data extractor should capture, from seller and shipment details to HS codes, origin, values, charges, and line-item exports.

Back to Articles & Analysis

Invoice Data Extraction

The AI-native automation platform for high-accuracy invoice extraction

Platform

  • Start Extraction
  • Home
  • Pricing
  • API
  • Python SDK
  • Node.js SDK

Solutions

  • Invoice to Excel
  • Invoice OCR Software
  • Bank Statement Converter
  • Receipt OCR
  • Utility Bill Extraction
  • Payroll Data Extraction
  • PDF Data Extraction

Resources

  • Articles
  • Contact

Trust & Security

  • Security
  • Subprocessors
  • AI Data Use

Legal

  • Terms of Service
  • Data Processing Addendum
  • Privacy Policy
  • Refund Policy
  • US State Privacy Rights
  • EEA/UK Privacy Rights
English
Sign inCreate account

© 2026 Invoice Data Extraction — DEH Technologies LLC

Secure by Design. Your data is never used for AI training.