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.