Parse Bills of Lading, Customs Forms, and Carrier Invoices Automatically

EezyAutomation reads shipping documents from any carrier or broker, extracts structured logistics data, and feeds your TMS or ERP — for $2 per document.

Logistics Paperwork Is Slowing Your Supply Chain

Bill of Lading Variations

Every carrier, freight forwarder, and steamship line uses a different BOL format. Your logistics team adapts to each layout manually, extracting shipper, consignee, commodity, and weight data from documents that look different every time.

Customs Form Complexity

Import and export documentation — commercial invoices, packing lists, certificates of origin, customs declarations — requires precise data extraction. Errors cause delays at the border, storage charges, and compliance penalties.

Shipping Manifest Data Entry

Manifests list every item in a shipment with quantities, weights, dimensions, and HS codes. Manual entry from multi-page manifests is tedious, error-prone, and creates a bottleneck between document receipt and shipment processing.

Carrier Invoice Matching

Carrier invoices must be matched against contracted rates, BOL details, and actual shipment records. Without structured data from all three document types, reconciliation is a manual comparison exercise that misses overcharges.

The Logistics Document Stack

EezyAutomation
Core logistics document parser. Reads BOLs, customs forms, manifests, and carrier invoices from any format, extracting structured shipment and cargo data.
EezyFleet
Fleet and shipment integration. Parsed BOL and manifest data feeds EezyFleet for shipment tracking, vehicle assignment, and delivery confirmation.
EezyBooks
Carrier invoice AP. Parsed carrier invoices match against contracted rates and flow into accounts payable for payment processing.

Bill of Lading Parsing Across Carriers

The bill of lading is the foundational document in freight logistics. It serves as a receipt of cargo, a contract of carriage, and a document of title. Despite its importance, there is no universal BOL format. Ocean carriers use FIATA-style documents. Trucking companies use straight or order BOLs with carrier-specific layouts. Freight forwarders issue house bills that aggregate multiple shipments. Each variant contains the same core information — shipper, consignee, origin, destination, commodity description, quantity, weight — but presents it differently. EezyAutomation parses BOLs from any carrier without requiring carrier-specific templates. The fuzzy-logic parser identifies BOL fields based on label proximity, field position patterns, and content validation (e.g., a field near 'Consignee' that contains an address pattern is the consignee address, regardless of which carrier's form it appears on). This approach handles the long tail of carrier formats that template-based systems cannot economically support. For LTL shipments with multiple commodity line items, the parser extracts each line: description, NMFC code, class, pieces, weight, and dimensions. This line-level detail is essential for rate verification — you cannot confirm that a carrier billed the correct class without knowing what was in each line item. The parser handles multi-page BOLs where commodity tables span pages, BOLs with handwritten entries (processed via OCR), and electronic BOLs received as PDF or image attachments. The parsed output feeds your TMS for shipment creation, your accounting system for freight cost accrual, and your audit process for carrier invoice matching. A single parse generates data for multiple downstream uses, eliminating the duplicate entry that occurs when shipping, accounting, and operations each extract data from the same BOL independently. At $2 per document, the ROI is immediate for any operation processing more than a handful of BOLs per day. A logistics coordinator spending 5 minutes per BOL at $22/hour costs $1.83 in labor alone — before accounting for errors, corrections, and the cost of delayed shipment processing.

Customs Form Automation for Import/Export

International trade documentation is where data extraction errors carry the highest consequences. An incorrect HS code on a customs declaration can result in duty overpayment, shipment seizure, or a compliance violation that affects your C-TPAT status. A missing field on a commercial invoice can delay clearance for days while your goods incur demurrage and storage charges at the port. EezyAutomation handles the full range of customs documentation. Commercial invoices are parsed for buyer, seller, terms of sale (Incoterms), currency, line-item descriptions, quantities, unit values, and total invoice value. Packing lists extract carton counts, dimensions, weights, and commodity descriptions. Certificates of origin capture the country of manufacture, harmonized codes, and certification authority details. For customs declarations (CBP Form 3461, 7501, and equivalents in other jurisdictions), the parser extracts entry type, importer of record, consignee, country of origin, HS codes, duty rates, and declared values. The engine validates extracted HS codes against the Harmonized Tariff Schedule to flag potential misclassifications before submission, giving your broker or compliance team the opportunity to correct errors at the extraction stage rather than at the border. The parser also handles the supporting documents that accompany customs entries: ISF (Importer Security Filing) data, anti-dumping and countervailing duty certificates, FDA prior notice filings, and FCC declarations of conformity. Each document type has its own extraction template, and all parsed data consolidates into a structured entry record that feeds your customs brokerage system. For importers and customs brokers processing high volumes, batch processing handles stacks of documents overnight. A broker receiving 200 entry packets per week — each containing 5-10 documents — can parse the entire week's intake in hours instead of dedicating staff days to manual data entry. The structured output feeds directly into ACE (Automated Commercial Environment) preparation workflows, reducing the cycle time from document receipt to customs entry filing.

Carrier Invoice Matching and Reconciliation

Freight audit studies consistently show that 3-5% of carrier invoices contain billing errors. For an operation spending $1 million annually on freight, that is $30,000-$50,000 in overcharges that go undetected without systematic invoice verification. The problem is that verifying a carrier invoice requires matching it against three separate data sources: the contracted rate, the bill of lading, and the actual shipment record. Doing this manually is so time-consuming that most companies audit only a sample of invoices, letting the majority pass without verification. EezyAutomation enables comprehensive carrier invoice matching by parsing all three document types into comparable structured data. The carrier invoice yields billed charges, accessorial fees, fuel surcharges, and reference numbers. The BOL yields commodity class, weight, dimensions, and origin-destination pair. The rate agreement yields the contracted rate for that lane and service level. With all three documents parsed, matching becomes a data comparison exercise rather than a document review exercise. The system flags invoices where the billed rate exceeds the contracted rate for the lane. It flags invoices where the billed weight exceeds the BOL weight. It flags accessorial charges that are not supported by BOL notations (detention, liftgate, inside delivery). And it flags duplicate invoices — the same shipment billed twice under different invoice numbers. For organizations with EezyBooks integration, verified carrier invoices flow directly into accounts payable. Invoices that pass all matching checks can enter the payment queue automatically. Invoices with discrepancies route to a dispute queue where the logistics team reviews them alongside the specific matching exceptions. The dispute is documented — billed $450, contracted rate for this lane and class is $380, BOL shows 2,400 lbs not the 3,100 lbs billed — giving your team a structured basis for the carrier dispute rather than an impressionistic sense that the bill looks high. The financial impact of automated matching extends beyond catching individual overcharges. When carriers know your invoices are systematically audited, billing accuracy improves preemptively. Industry data suggests that shippers who implement freight audit programs see error rates decline from 5% to under 2% within 12 months, as carriers tighten their own billing processes in response to consistent, documented disputes.

EezyAutomation vs. Logistics Document Solutions

Feature-by-feature comparison for shipping and customs document automation

Feature
EEZYVERSE
Flexport
Chain.io
Manual Broker Processing
Pricing model
$2/document, no subscription
Full-service freight forwarding fees
Platform subscription + per-transaction
$50-100/hour broker staff cost
Core function
Document parsing engine for logistics documents
Full-service digital freight forwarder
Supply chain data integration platform
Manual document processing
BOL parsing
Any carrier format, line-item commodity detail
Within Flexport shipments only
Data mapping, not document parsing
Manual extraction per document
Customs form parsing
Commercial invoice, packing list, CO, declarations
Handled within forwarding service
Data integration, limited parsing
Manual extraction and entry
Carrier invoice audit
Automated rate vs. billed comparison
Within Flexport invoices only
Data visibility, not audit
Sample-based manual audit
Multi-carrier support
Any carrier, any format, any mode
Flexport network carriers
Connected carrier partners
Depends on broker relationships
Output flexibility
JSON, CSV, API — feeds any TMS or ERP
Flexport platform
Platform integrations
Manual entry into target system
Implementation
Days — configure and start parsing
Onboarding as forwarding client
Weeks-months for integration
Immediate (manual process)
HS code validation
Extracted codes validated against HTS
Within forwarding service
Not a parsing tool
Depends on broker expertise
Seat fees
None — unlimited users
Platform access included in service
Per-user platform pricing
Per-hour labor cost

Real-World Use Cases

Third-Party Logistics (3PL)

Scenario: A 3PL handles 500 shipments per week across 40 carriers, each with different BOL formats and invoicing styles. Staff spends hours daily on manual document processing.
Outcome: EezyAutomation parses BOLs and carrier invoices from all 40 carriers into a unified data format. Shipment creation time drops by 70%, and carrier invoice matching catches $180K in annual overcharges.

Customs Brokerage

Scenario: A customs broker processes 200 entry packets per week, each containing commercial invoices, packing lists, certificates of origin, and customs declarations from different importers.
Outcome: Batch parsing processes entry packets overnight. Brokers start each day with pre-extracted data and focus on classification review and compliance rather than data entry. Entry filing time drops from 45 minutes to 10 minutes per shipment.

E-Commerce Fulfillment

Scenario: An e-commerce company ships 2,000 packages daily across FedEx, UPS, USPS, and regional carriers. Carrier invoices arrive weekly and must be reconciled against shipping records.
Outcome: Parsed carrier invoices match automatically against shipment records. Billing errors (wrong zone, wrong weight, wrong service level) are flagged immediately, recovering an average of 4% of total shipping spend.

Manufacturing Importer

Scenario: A manufacturer imports raw materials from 15 countries, generating 50+ customs entries per month with varying documentation requirements per country of origin.
Outcome: EezyAutomation parses all import documentation regardless of origin country format. HS code validation flags potential misclassifications before filing, avoiding duty reassessments and compliance penalties.

Per-Document Pricing for Logistics Documents

No TMS license required. No seat fees. No minimums.

Logistics Document Parsing
$2/document
  • ["Bills of lading (ocean, truck, air, rail)","Commercial invoices and packing lists","Customs declarations and certificates of origin","Carrier invoices and freight bills","Shipping manifests with line-item extraction","HS code validation","API output to any TMS or ERP","Unlimited users","No contract"]
Start Parsing Logistics Documents

Frequently Asked Questions

EezyAutomation parses BOLs from any carrier across all modes: ocean (MSC, Maersk, CMA CGM, etc.), trucking (any LTL or FTL carrier), air (any airline or freight forwarder), and rail. The fuzzy-logic parser adapts to each carrier's format without requiring template configuration. New carrier formats are handled on first encounter.

Stop Keying Shipping Documents. Start Parsing Them.

Upload a BOL, customs form, or carrier invoice and see structured output in seconds.

Try Logistics Parsing Free