Free AI Commercial Invoice Parser
Upload a commercial invoice, the export document that clears customs, and get structured trade data back in seconds: exporter and importer, line items with HS codes, Incoterms, country of origin, and total declared value, exported as JSON, CSV, or Excel.
One commercial invoice, every field returned.
An actual extraction result from a customs invoice: exporter and importer, a full line-item table with HS codes, and the trade terms customs checks first. Switch to JSON to see the exact shape your systems receive.
| Description | HS code | Qty | Unit price | Amount |
|---|---|---|---|---|
| Cotton bath towels, 500gsm | 6302.60 | 1,200 | $3.80 | $4,560.00 |
| Woven cotton bathrobes | 6208.91 | 400 | $9.50 | $3,800.00 |
| Bamboo hand towels | 6302.60 | 800 | $2.15 | $1,720.00 |
| Tufted cotton floor mats | 5702.42 | 300 | $6.40 | $1,920.00 |
{ "invoice_number": "CI-40817", "invoice_date": "2026-07-09", "exporter": { "name": "Mekong Textiles Co., Ltd", "country": "VN" }, "importer": { "name": "Atlas Home Goods LLC", "country": "US" }, "incoterms": "CIF Los Angeles", "country_of_origin": "VN", "currency": "USD", "line_items": [ { "description": "Cotton bath towels, 500gsm", "hs_code": "6302.60", "qty": 1200, "unit_price": 3.80, "amount": 4560.00 }, { "description": "Woven cotton bathrobes", "hs_code": "6208.91", "qty": 400, "unit_price": 9.50, "amount": 3800.00 }, { "description": "Bamboo hand towels", "hs_code": "6302.60", "qty": 800, "unit_price": 2.15, "amount": 1720.00 }, { "description": "Tufted cotton floor mats", "hs_code": "5702.42", "qty": 300, "unit_price": 6.40, "amount": 1920.00 } ], "goods_subtotal": 12000.00, "freight_insurance": 480.00, "total_declared_value": 12480.00 }
Specimen data shown. This is a customs export document, not a domestic sales invoice: it carries HS codes, Incoterms, and country of origin so customs can assess duties.
The commercial invoice is how a shipment clears customs.
It travels with the goods from exporter to importer. Customs reads it to classify the goods by HS code, verify origin and Incoterms, and assess duties and tariffs before the shipment is released.
Exporter
The seller ships the goods and issues the commercial invoice for the shipment.
Commercial invoice
Declares parties, goods, HS codes, Incoterms, origin, and value.
Customs clearance
Goods classified by HS code, value and origin verified.
Duties & tariffs assessedImporter
The shipment is released and delivered to the buyer of record.
Every field customs needs, as structured data.
The parser reads the whole commercial invoice and returns labeled fields rather than a wall of text. Here is exactly what comes back.
Parties & invoice details
The exporter of record, the importer of record, the invoice number, and the invoice date, normalized so they match your customs entry every time.
Line items & HS codes
Every line on the invoice as its own row: description, quantity, and unit price, plus the extended amount and the HS or HTS code used for tariff classification.
Trade terms
The Incoterms rule, country of origin, invoice currency, and total declared value: the fields customs brokers and freight systems check first.
Logistics & weights
Freight and insurance charges, gross and net weight, and the ports of loading and discharge, captured for customs valuation and cargo handling.
Commercial invoice to customs-ready data in three steps.
Upload the commercial invoice
Drag in a PDF, or a photo or scan (JPG, PNG, WebP, HEIC) of the invoice from your supplier or freight forwarder.
AI reads the document
The model identifies exporter, importer, line items, HS codes, Incoterms, and totals the way a customs broker would, regardless of layout.
Export the data
Download the structured result as JSON, CSV, or Excel, or send it onward to your customs or ERP system with a ParserBee account.
What is commercial invoice parsing?
Commercial invoice parsing is the automated conversion of an export document, the paperwork that travels with an international shipment, into structured data a system can use: named fields such as exporter, HS code, Incoterms, and declared value. It is a form of commercial invoice OCR that goes beyond reading text: it identifies what each piece of text means and returns it as a field a customs entry, ERP, or trade compliance system can consume directly. When a broker talks about extracting data from a commercial invoice, this is what they mean.
A commercial invoice is not the same document as a regular sales invoice. A domestic invoice is a bill for payment; a commercial invoice is the primary customs document for a cross-border shipment. Customs authorities use it to assess duties and tariffs, verify the HS or HTS classification of the goods, confirm the country of origin, and check the declared value against the Incoterms rule that determines who pays for freight and insurance. Getting these fields wrong can hold a shipment at the border, not just create an accounting error.
Why commercial invoices are hard to parse
Commercial invoices are especially difficult for customs invoice data extraction, for reasons every trade compliance team has run into:
- Every exporter uses a different template. A supplier in Vietnam, a freight forwarder in Rotterdam, and a factory in Ohio each format their commercial invoice differently, so a parser built for one layout breaks on the next.
- Line items bury the codes that matter. HS/HTS codes, quantities, unit prices, and descriptions are packed into dense tables, sometimes with multiple codes per shipment, and a single missed digit misclassifies the goods.
- Trade terms are abbreviated and easy to confuse. FOB, CIF, DDP, and EXW look similar but shift who is responsible for freight, insurance, and duties. Currency codes vary by exporter, too.
- Files arrive as scans and phone photos. A commercial invoice faxed from a supplier or photographed at a warehouse defeats any parser without built-in OCR.
This is why customs software built on fixed templates so often needs manual correction: a value lands in the wrong currency, an HS code truncates, or a scanned invoice imports as an empty record. Each error becomes a person's job to catch before a customs entry is filed.
How AI parsing differs from rule-based, template OCR
Template-based customs OCR works by matching a known layout: find the box labeled "Total", read the number below it, stop at the next known label. It is fast on templates it was built for, and brittle on everything else, because a new exporter's invoice matches no template on file. ParserBee's approach reads the document the way a customs broker does, using what the content says and where it sits in context, not a fixed position on the page. An HS code is recognized as an HS code by its format and its place next to a description and quantity, so invoices from a new supplier parse correctly the first time, with no template setup, and scanned invoices are read through OCR then interpreted with the same logic as a digital PDF.
Who uses this tool
Customs brokers & trade compliance teams
Turn each shipment's commercial invoice into a structured record ready for a customs entry: HS codes, country of origin, Incoterms, and declared value pulled out and ready to check against classification rules, without retyping a single field from a PDF.
Import/export teams & freight forwarders
Build a shipment record from the commercial invoice, and cross-check it against the bill of lading, in minutes instead of an afternoon. Track Incoterms and declared value across every consignment, and catch a mismatch before a shipment is held at the border.
ERP & trade compliance developers
The same extraction is available programmatically through ParserBee's API: send a file over REST, receive structured JSON. It is the fastest way to add commercial invoice ingestion to a customs management system or an internal ERP tool, with results ready to export to Excel, CSV, or Google Sheets for the rest of the team.
From single invoices to a pipeline
The free tool above parses one commercial invoice at a time, which is the right way to evaluate quality on your own documents. Shipments do not arrive one at a time, though. With a ParserBee account, the same parser becomes a pipeline: commercial invoices are processed in volume, and every result is delivered wherever your customs workflow lives, a Google Sheet, your customs or ERP system through Zapier or the API, or your own system through webhooks. Set the destination once, and every future invoice follows it.
From one invoice to an automated customs pipeline.
A free ParserBee account turns this tool into an automated flow: commercial invoices go in, customs-ready records come out, delivered to the systems you already use.
Invoices arrive
Batch upload, or send straight from your freight forwarder's inbox.
ParserBee extracts
Every invoice becomes the same structured trade record, automatically.
Clearance runs
Google Sheets natively, your customs/ERP system via Zapier or the API, or REST.
Frequently asked questions.
Is the commercial invoice parser really free?
What's the difference between a commercial invoice and a regular invoice?
What's the difference between a commercial invoice and a proforma invoice?
Which file formats does it support?
Are uploaded commercial invoices stored?
How accurate is the extraction, especially HS codes and values?
Can I parse commercial invoices in bulk and export to Excel, or send them to my customs or ERP system?
Clear customs faster, without the retyping.
Parse your next commercial invoice free above. When shipments pick up, a free ParserBee account turns the same parser into an automated pipeline to your customs system or ERP.