Upload a CBP Form 7501
Drop a filed US CBP Form 7501 into the audit engine. The deterministic parser extracts every line and the engine re-computes the duty and fee stack.
Upload a CBP Form 7501
A US CBP Form 7501 is the Entry Summary that documents duty and fee owed on a formal entry into the United States. LandedFees ships a deterministic 7501 parser (LFQG-144) that reads the standard 7501 field layout without OCR guesswork on the critical fields (HTS number, entered value, statutory duty). Drop the form in and the engine tells you what the duty stack should have been.
Deterministic means the parser locks onto the printed field positions rather than doing free-form OCR. It handles single-page and multi-page 7501s, ACE-generated PDFs, and scanned copies.
How to upload a CBP 7501
- Open the audit page.
- Drag your 7501 PDF (or PDF export from ACE) into the dropzone.
- The parser extracts entry number, port, importer of record, and every 7501 line: HTS number, entered value, duty rate, and duty amount.
- Review the extracted lines. Any low-confidence field is flagged with a yellow badge. Click to edit.
- Add any missing overlay data. The 7501 line format sometimes hides Chapter 99 overlays in the same HTS cell; the parser flags this and asks you to confirm.
- Click Audit. The engine re-computes duty and fees per line and returns findings.
Multi-page 7501s are supported. Line items are pulled from every page and reassembled in the input order.
What the parser reads
Header block: entry number, entry date, entry type, importer of record and consignee, port of unlading, mode of transport. Line block: line number, HTSUS number, description, entered value, duty rate, duty amount, MPF and HMF. Trailer block: total entered value, total duty, total fees.
If the 7501 was filed through ACE and includes the ACE reference number, the parser captures it so the finding memo carries the exact reference your broker will use to file a correction.
Common upload issues
Scanned 7501s that were faxed and re-scanned can drop below the deterministic parser's confidence threshold. In that case the OCR fallback kicks in and you see a yellow badge on every extracted field. Confirm each field before running the audit.
If your 7501 is a Type 06 warehouse withdrawal or Type 23 TIB, the parser handles the header but flags that duty computation for these types differs from a standard Type 01 or Type 11. Review the guidance in the findings panel.
Frequently asked questions
Do you support ACE data exports besides the 7501 PDF
Not yet. Today, upload the 7501 as PDF. ACE JSON export support is on the roadmap.
What if my 7501 has a supplement or PSC already filed
Upload both the original 7501 and any PSC as separate files. The engine reconciles them and audits against the latest state.
How long does the audit run
Most entries finish in under thirty seconds. Very large multi-line entries (fifty lines or more) can take up to two minutes.
Does the parser send my 7501 outside my region
Storage is in EU (Frankfurt, eu-central-1) at rest. The deterministic parser runs in the same region. See /trust for the full data-handling posture.
Related
Audit
Upload an EU Single Administrative Document
Drop an EU SAD (import declaration) into the audit engine. The parser reads Box 33 HS codes, Box 42 statistical value, and every duty line.
Audit
Upload a UK CDS declaration
Drop a UK Customs Declaration Service (CDS) export or the PDF into the audit engine. Refund path is C285 to the National Duty Repayment Centre.
Audit
Reading audit findings and picking an amendment lane
Every audit finding routes to one of four US amendment lanes: PSC (300 days), 1520(d) reconciliation (1 year), 19 CFR 174 protest (180 days post-liquidation), or duty drawback (5 years). Here is how to choose.
Still stuck
Paid tiers can open a ticket from the in-app support inbox. Free users can email operator support at info@growyourbrand.io.
Open a ticket