Extract data from customs declarations
Unstract reads CBP 7501 entry summaries, ISF filings, export declarations and bills of entry, typed, scanned or faxed, and returns checked declaration data to your customs filing or ERP system.
line 2 HTS vs invoice desc? check w/ client — Dana
CBP FORM 7501 · PAGE 1 OF 2
{ "entry_number": "K7Q-0418362-5", "summary_date": "11/04/2026", "port_code": "2704", "country_of_origin": "VN", "bl_number": "MTL26HPH0291", "manufacturer_id": "VNSONLIN1472HAI", "entered_value_usd": 60800, "duty": 1392.4, "mpf": 210.61, "total_due": 1679.01}
Trusted by logistics and supply chain teams around the globe
No two entry packets look alike
Declarations reach the brokerage from shippers, forwarders, carriers and customs portals, and each one arrives in its own condition.
Export declarations signed on paper, faxed and rescanned
A 7501, an ISF and a bill of entry asking for the same facts
HTS numbers corrected in pen on the broker's worksheet
The 7501 scanned with the invoice, packing list and B/L
Parts spreadsheets with a tariff number on every row
Brokers retype every line into the filing system, and one transposed tariff number or value becomes a duty underpayment that CBP can penalise years after the goods were released.
Unstract reads each declaration in the packet, pulls the fields you name, checks values, origin and HTS codes against the invoice and your tariff table, and sends the result to your customs filing or ERP system.
Parse, extract and route every declaration
Three products that work alone or together: parsing, extraction and automation. Begin with the layer your brokerage needs today and add the others as entry volume grows.
Parse every customs declaration into text that keeps its boxes
A 7501 packs dozens of numbered boxes onto one page, and a bill of entry from Mumbai or Felixstowe lays the same facts out differently. LLMWhisperer reads each one with its grid intact, so a duty rate stays on the line with its HTS number and a manufacturer ID never drifts into the importer's address.
Pass the text to your own LLM, or use parsing as the opening step of a wider customs process.
Learn more about LLMWhispererTurn every customs declaration into one structured entry record
Name the declaration fields you need in a prompt, and every document comes back as JSON in a single schema: an entry summary, an ISF 10+2, an export declaration or a bill of entry. As a customs declaration data extractor it needs no template per country or filer. An HTS code that does not fit the invoice description, or a line value that disagrees with the commercial invoice, comes back flagged with the source named.
Deploy it as an API, as an ETL pipeline, or as one step inside an orchestrated customs process.
Learn more about Document StudioRun customs clearance from entry packet to a file-ready entry
Describe how your team prepares a customs declaration in plain English, and Flow's agents build the workflow: the invoice, packing list, B/L or air waybill and certificate of origin collected as they arrive, read, cross-checked line by line, and loaded into your customs filing or ERP system as a draft entry and ISF. Once you approve the workflow, every entry packet goes through the identical steps.
Choose where it stops: values or quantities that differ across the packet, an HTS code that is missing or does not match the description, a certificate of origin that never came. Those entries wait for a licensed customs broker with the reason beside the line. Filing stays with the broker.
Learn more about FlowExtract from your own declarations today. Automate clearance later.
Start for free to parse and extract your customs declarations now. Automating customs clearance starts with a consultation.
Import, export and transit declarations in one schema
Documents
- US Customs Entry Summary 7501
- Importer Security Filings
- Export declaration forms
- Bill of entry
- Transportation Entry
- Customs declarations from other countries
- Commercial invoices
- Packing lists
- Bills of lading
- Air waybills
- Certificates of origin
- Arrival notices
- Partner-agency forms
- Any other customs authority's declaration layout
Fields captured
Built for the people who clear the goods
Entry summaries drafted from the client's packet with every line already classified, so the licensed broker reviews and signs instead of retyping.
ISF data pulled from the shipper's invoice and booking before the vessel loads, so the 24-hour deadline stops being a late-night scramble.
Every filed 7501 and bill of entry read back into one record set, so post-entry audits and reconciliations start from the declared values.
Import and export declarations read for each client in their own format, so cleared goods reach the warehouse with the entry data already in place.
Fewer keyed lines, entries ready sooner
Declarations hold your trade secrets and your duty exposure
A customs declaration carries the importer of record number, the declared value of every line and the manufacturer that made the goods. Together they map your supplier relationships and your landed cost. A misread HTS code carries its own risk: it turns into underpaid duty and a penalty notice.
- Encrypted in transit and at rest.
- Customs documents are never used to train models.
- Access by role, branch and client, with every corrected tariff number and released exception logged against the entry number.
- Retention you set, matched to the five years customs record-keeping rules ask importers and brokers to keep entry records.
- Brokers that must keep client trade data inside their own network can run Unstract self-hosted.
What brokers and trade compliance teams ask first
Unstract, in three layers. LLMWhisperer reads each declaration with its layout kept, Document Studio uses LLMs to return the fields you named as JSON, and Flow's agents run the clearance steps around them. Used together they work as a customs clearance documents data extractor that hands a draft entry to your broker.
Parse the page first, then extract. LLMWhisperer keeps each invoice line on one row with its quantity, unit price and value, and Document Studio maps those lines to HTS numbers and entered values in your schema. The same run reads the 7501 so both can be compared.
Document Studio returns one schema across entry summaries, ISF filings, export declarations, bills of entry, invoices, packing lists and bills of lading. Each field is located by what it means rather than where it sits, so an unfamiliar supplier or country format works on the first file.
Point Flow at the inbox or portal where shipment documents land. Its agents collect each packet, extract the declaration fields, check them against the invoice and B/L, and stage the entry in your customs filing or ERP system. Your team handles only the flagged lines.
Yes. LLMWhisperer handles fax noise, skewed scans and phone photos, and reads pen corrections next to the typed values. A value the extraction step cannot read with confidence goes to a person with the page beside it, so a guessed tariff number never reaches a draft entry.
Often both. LLMWhisperer is the customs declaration parser: it turns the page into layout-kept text. Document Studio is the extractor that turns that text into named fields, and you can call either one by itself through an API.
Yes. Each HTS number is compared with your tariff table and the line description, and rates are matched against the duty shown. A code that is missing, outdated or a poor fit for the goods is flagged for a licensed broker to decide.
Yes. ISF data elements such as seller, buyer, manufacturer, ship-to party and container stuffing location come back in the same schema as a US entry summary, and so do UK, EU and Indian bills of entry, export declarations and transportation entries.
No. Filing stays with your licensed broker and your filing software. Unstract prepares checked data for the entry and ISF, and the broker reviews, decides on classification and files.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Declarations are encrypted, never used for training, and kept only as long as you choose. Brokers that need trade data on their own servers can self-host, and the Trust Center lists each control.
Most brokerages run live entries within days of a consultation, where we set the workflow around your clients' packets, your tariff checks and your filing system. To test extraction first, start for free and upload a 7501.
Bring a month of entry packets to the consultation
Entry summaries, ISF filings, export declarations and bills of entry, faxed and scanned copies too. You see each declaration read on screen, with every HTS line, value and origin checked against its invoice.