<- View all workflow automations

Customs declarations and commercial invoices — extracted into compliance-ready data

Lido extracts HS/HTS codes, declared values, country of origin, duty amounts, importer and exporter details, and incoterms from customs declaration forms and supporting commercial invoices, producing compliance-ready structured data for your customs management system or broker. Clearance delays from keying errors stop here.

  • Reads declaration forms across customs authorities. US CBP entry summaries (CBP Form 7501), Canadian B3 forms, EU SAD forms, and commercial invoices used in customs filings, all extracted in the same pipeline without per-country template setup.
  • Extracts HS and HTS codes with declared value per line item. Multi-line commercial invoices with different HTS classifications per line are extracted as individual rows, each with its own HTS code, declared value, quantity, and country of origin.
  • Confidence scoring on every extracted field. Declared values, HTS codes, and country of origin are critical for duty calculation. Low-confidence extractions are flagged for broker review before the entry is filed, not discovered during a CBP inquiry.
Trusted by thousands of finance and operations teams

How customs declaration processing works in Lido

Customs clearance depends on accurate declared values, correct HTS classifications, and verified country of origin. Errors on any of these fields create delays, duty underpayments, and CBP holds. Manual extraction from multi-page commercial invoices and declaration forms introduces exactly the kinds of errors that trigger scrutiny. Lido extracts and structures the data before the entry is filed.

1. Customs documents arrive as PDFs from importers or freight forwarders

Commercial invoices, packing lists, certificates of origin, and draft customs entries arrive as PDF attachments from the importer, freight forwarder, or carrier. Lido picks them up from a watched inbox or broker portal and begins extraction. Multi-document shipment packages, invoice plus packing list plus certificate of origin, are processed as a linked set, with fields cross-referenced across documents.

2. Importer, exporter, and shipment header fields are extracted

From each customs document set: importer of record name and address, IRS/EIN number, importer bond number, exporter name and country, entry type, port of entry, mode of transport, vessel or flight number, country of export, estimated import date, and total declared value. These header fields populate the entry summary record in the customs management system.

3. Line-item HTS classifications and declared values are extracted

From the commercial invoice: each line item's description of goods, HTS/HS code, quantity, unit of measure, unit value, total line value, country of origin, and manufacturer or seller name. Multi-line invoices with 50 or more line items are fully extracted with one output row per line. Lines with different HTS codes for similar goods are preserved as distinct entries rather than aggregated.

4. Duty calculations are validated against extracted HTS codes and values

Extracted HTS codes are validated against the expected code format (10-digit for US HTS, 8-digit for HS). Declared values per line are summed and compared against the invoice total, discrepancies between line totals and the invoice grand total are flagged before the entry is filed. Anti-dumping and countervailing duty flags are identified for lines where the HTS code falls under an active ADD/CVD order.

5. Compliance-ready structured data is delivered for entry filing

The extraction output is structured as a line-item-level dataset with all fields required for customs entry preparation. HTS code, value, quantity, country of origin, manufacturer, and duty rate. The output maps directly to your customs management system's import format or your broker's ACE entry preparation template. Each line is traceable to the source invoice page and line number for audit support.

Try it free

See this workflow run on your documents

Upload a batch and get structured output in minutes.

Customs document types Lido extracts from

Commercial invoices for customs

Multi-line commercial invoices from foreign sellers with HTS codes, declared values, quantities, and country of origin. Any currency, any number of line items.

Certificates of origin (CO and GSP form A)

General certificates of origin, GSP Form A, NAFTA/USMCA certificates. Exporter, producer, tariff classification, and origin criteria extracted.

CBP Form 7501 (US entry summary)

US customs entry summary forms. All blocks extracted including entry type, HTS numbers, duty amounts, MPF, HMF, and importer of record fields.

Canadian B3 customs coding forms

Canadian customs entry forms for commercial importations. Tariff code, value for duty, origin, and applicable trade agreement codes extracted.

EU Single Administrative Document (SAD)

European customs declaration forms. All boxes extracted including HS code, customs value, statistical value, country of origin, and procedure code.

Customs invoices (Canadian CI1 and others)

Country-specific customs invoice formats required by Canada, Australia, and other authorities. All mandatory fields extracted in addition to standard commercial invoice fields.

Why manual customs data entry creates duty errors and clearance delays

Keying errors that trigger CBP holds

A customs broker receives a 35-line commercial invoice for an import shipment. The entry prep specialist reads each line, identifies the HTS code the importer has listed, types the declared value, and enters the country of origin. On line 22, a transposed digit in the HTS code shifts the classification from a duty-free subheading to one carrying a 7.5% Section 301 tariff, a $4,800 error on a $64,000 line item. The error is discovered during CBP review, not before filing. The hold costs more in demurrage than the original keying error would have taken to verify.

Lido extracts HTS codes and values with confidence flags that catch classification errors before filing

Lido extracts each line's HTS code, declared value, and country of origin with confidence scoring. Low-confidence HTS reads, where the invoice code is partially obscured or non-standard, are flagged for broker review before the entry is filed, not after CBP scrutiny. Your entry prep team reviews flagged exceptions and approves clean lines rather than manually re-keying a 35-line invoice from scratch.

Lido vs manual customs entry data preparation

FeatureLidoManual keying
Extract HTS codes and declared values from any commercial invoice format
Flag low-confidence HTS reads before entry is filed
Cross-reference line totals against invoice grand total automatically
Identify ADD/CVD-applicable HTS codes in the extracted data
Output line-item data formatted for your customs management system
Read each invoice line and re-key every field into the entry system by hand
Customs entry automation

A transposed HTS digit on line 22 of 35 is not caught by re-reading a PDF

Extract customs data with confidence scoring and catch classification errors before CBP does.

Common use cases

Customs Broker

Prepare ACE entry summaries from multi-line commercial invoices

A licensed customs broker files 80 formal entries per week for import clients. Each entry requires line-by-line extraction of HTS codes, declared values, and country of origin from commercial invoices averaging 20 lines. Lido processes each invoice set and delivers ACE-ready structured data, cutting entry prep time per shipment from 45 minutes to under 10.

Importer / Trader

Validate HTS classifications before submitting to your customs broker

An importer receiving 150 ocean shipments per year submits commercial invoices to their customs broker for entry preparation. Lido extracts the HTS codes and declared values the foreign seller has listed on each invoice, enabling the importer to spot classification errors before the documents reach the broker, reducing broker amendment fees and CBP inquiry risk.

Trade Compliance Team

Screen imported goods for ADD/CVD and Section 301 tariff exposure

A trade compliance team at a mid-size manufacturer reviews all import invoices for anti-dumping and Section 301 tariff exposure before goods are ordered. Lido extracts HTS codes from supplier invoices and quotations, enabling the compliance team to flag affected product lines and source alternatives before purchase orders are committed.

Freight Forwarder

Compile customs document packages for broker hand-off

A freight forwarder coordinates customs clearance for 60 client shipments per week. Each shipment requires a document package: commercial invoice, packing list, BOL, and certificate of origin. Lido extracts key fields from each document and generates a customs document summary for broker hand-off, including flagged discrepancies between invoice and packing list quantities.

Stop keying customs data line by line from commercial invoices

Try Lido free. Upload a commercial invoice or customs declaration and see HTS codes, declared values, and country of origin extracted into compliance-ready structured data in minutes.