← Back to Blog
Operations6 min read

ACE Data for Duty Refund Claims: What Importers Should Pull First

ACE data is often the fastest way to build a claim file. A disciplined export from your broker or ACE account can help teams confirm entry numbers, liquidation dates, duty amounts, and the source documents a refund workflow may require.

For most refund workflows, the first bottleneck is not legal analysis. It is data assembly. ACE reports and broker exports give import teams the entry-level record they need to understand where duties were paid, what has liquidated, and which shipments deserve immediate attention.

Start With a Clean Entry-Level Export

The first export should make it possible to sort and filter at the entry level. In practice, that means confirming:

Entry number

Entry date

Importer of record

Broker reference

Port of entry

HTS classification

Declared value

Duties, taxes, and fees paid

Liquidation date and status

Without that structure, every downstream question becomes manual. With it, teams can quickly isolate high-dollar entries, open protest windows, and claims that still need source documents.

Pair ACE Data With the Source Record

ACE-level reporting is powerful, but it is not the full claim file by itself. Once high-priority entries are identified, pull the source documents that explain the transaction:

Commercial invoices

Packing lists

Entry summaries

Rulings or exclusion support, if relevant

Prior correspondence with the broker

This pairing matters because refund opportunities usually turn on both the entry record and the evidence behind it.

Normalize Before You Analyze

Import data often comes from multiple brokers, ERP systems, and spreadsheets. Normalize the field names, date formats, and company names before anyone starts calculating recovery potential. Otherwise, the same importer may appear under several aliases and the same issue may look like several different problems.

What Good Intake Looks Like

The most effective intake process is simple:

1. Pull the entry data

2. Tag records by issue type and deadline sensitivity

3. Attach the source documents for the entries that matter most

4. Hand off a structured packet rather than a loose spreadsheet

That approach reduces delay, makes broker collaboration easier, and creates a cleaner record if the company decides to move from screening into an actual claim.

Ready to recover what's yours?

Contact us for a no-obligation assessment of your duty recovery potential.

Get in TouchMore Articles