Skip to content
Start free
Documents
Bills of lading · Freight invoices · Rate confirmations · Packing lists · Delivery receipts
Typical fields
bol_number · shipper · consignee · gross_weight_lb
Output
JSON · Excel · CSV
Plans
$0 · $9.90 · $100 · Custom

Load paperwork in.
Shipment fields out.

Bills of lading, delivery receipts, packing lists and carrier invoices usually come in the layout of whoever issued them. The fields you define are read from every one and returned to your TMS or ERP.

Book a demoTry it on one file

30 minutes · no commitment

SampleRESULT · bill-of-lading.pdfJSON
{  "extracted_data": [    {      "bol_number": "BOL-552190",      "shipper": "Acme Supplies Inc.",      "consignee": "Orion Ltd.",      "carrier": "Sample Haulage Co.",      "pickup_date": "2026-05-12",      "items": [        { "item": "Cartons", "pieces": 18, "weight_lb": 1400 },        { "item": "Pallets", "pieces": 6, "weight_lb": 900 }      ],      "piece_count": 24,      "gross_weight_lb": 2300    }  ]}

Fictional bill of lading; values are illustrative. Only the extracted_data of a result is shown.

What changes between pickup and payment.

01
Process
How the work changes

Done by hand

  • Bills of lading, delivery receipts and carrier invoices are opened one at a time and keyed into the TMS or a spreadsheet.
  • One load carries several reference numbers (BOL, PRO, PO) and each document often shows a different one, so the documents are matched by hand.
  • A carrier invoice is usually checked against its rate confirmation, charge by charge, before it is approved.

With Parser

  • A bill of lading, a delivery receipt or a carrier invoice arrives by upload, e-mail or API, and the fields of that document type's template are read from it.
  • Each reference number comes back as a field of its own, so your system can match an invoice to its bill of lading and rate confirmation.
  • A validation rule can hold the charges on an invoice to their total. The result reaches your TMS or ERP by webhook or API, or as JSON, Excel or CSV.
02
Documents
Typical documents and fields

The documents, and the fields each one carries.

A load usually leaves these five documents behind. Under each are the fields it typically carries; the template you write decides which ones come back.

  • 2.1

    Bills of lading

    Fields bol_number shipper consignee piece_count gross_weight_lb

  • 2.2

    Freight invoices

    Fields invoice_number carrier pro_number accessorials total_due

  • 2.3

    Rate confirmations

    Fields load_id carrier linehaul_rate fuel_surcharge detention_terms

  • 2.4

    Packing lists

    Fields po_number ship_to line_items piece_count net_weight_lb

  • 2.5

    Delivery receipts

    Fields bol_number delivered_at received_by piece_count exceptions

Field names are set in the template and come back as the keys of the result. Define your own fields in the API guide.

03
Solutions
Where to look next

Related solutions.

  • 3.1

    Invoice processing

    Vendor, tax ID, line items, taxes and due date from invoices and bills.

    Fields vendor tax_id line_items total

    Invoice processing, see use case
  • 3.2

    Contract extraction

    Parties, dates, amounts and the clauses you name, read at intake.

    Fields parties effective_date term contract_value

    Contract extraction, see use case
  • 3.3

    Insurance

    Claim forms, policy schedules, certificates of insurance and repair estimates, read into claim and coverage fields.

    Fields claim_number policy_number loss_date claimed_amount

    Insurance, see industry

Your documents are different? Book a demo.

Bring a real bill of lading.

In the demo we process your documents live — no slides, no fluff.

Book a demoTry it on one file

30 minutes · no commitment

  • Self-serve

    Free, Starter ($9.90/month) and Pro ($100/month) start when you sign up. No card required for Free.

  • Enterprise

    By contract · your own model key · an engineer for your team · setup done for you if you want it · POC on your documents.