You paid the duty. Then you looked closer and realized the assessment was wrong. Maybe the entry cleared under a code that never fit the product. Maybe an exclusion you qualified for got missed at entry. Maybe the rate applied does not match what the schedule actually says. Whatever the trigger, the money already left, and now you want it back.
The good news is that the system has a defined path for this. The harder part is that the path runs on strict deadlines and specific forms, and missing either one closes the door regardless of how right you are. Knowing how the process moves is what separates a recovered overpayment from a write-off.
Start by naming the actual error
Before you file anything, get precise about what went wrong. A dispute built on a vague sense that the duty felt high goes nowhere. CBP wants to know the specific basis.
Most tariff disputes fall into a few buckets:
- A classification error, where the entry used the wrong HTS code and pulled a higher rate than the correct code would
- A valuation issue, where the declared value overstated the dutiable amount
- A missed exclusion or program eligibility that should have lowered or removed the duty
- A straightforward CBP or data error at entry
Pin the claim to one of these before you move. The documentation you need and the form you file both depend on which one you are arguing.
Know which clock you are on
Timing is where most importers lose. The procedure splits depending on whether the entry has liquidated yet, so the first practical step is checking liquidation status in ACE.
If the entry has not liquidated, you generally fix it through a Post Summary Correction. That path is cleaner because the entry is still open and you are amending it before it finalizes.
Once the entry liquidates, the correction route closes and you move to a formal protest. The protest window runs on a fixed statutory clock that starts at liquidation, and it does not stretch for a good story or a busy quarter. Mark the deadline the day you spot the issue, because there is no recovering a claim you filed late.
Build the packet before you file
A protest with thin documentation invites a denial. The reviewer needs to reconstruct your argument without chasing you for missing pieces, so assemble everything before submission.
A complete packet usually includes the entry summary, the commercial invoices, proof that the duties were actually paid, and the evidence specific to your claim. For a classification dispute, that means a clear analysis of why the correct code applies and why the entered code does not. For an exclusion claim, it means the notice showing your product qualifies. The more the packet answers questions before they get asked, the faster it clears.
Importers who audit their own entries have an edge here. When you already run a tariff audit platform for importers across your history, you are not starting the protest from scratch. You have already flagged the questionable entries, gathered the supporting data, and can point to the pattern instead of hunting for one invoice at a time.
File through the right channel and track it
Formal protests go in through the ACE protest module using the correct form. Submit the full packet, note the entry number, and keep your own copy of everything.
Then wait, but wait actively. Review takes time, and complex claims with novel arguments take longer. Watch the case status and respond fast if CBP asks for more. A request that sits in someone’s inbox for three weeks is a request that stalls your refund.
If the volume of disputes is large, doing this entry by entry gets painful quickly. Teams handling recurring overpayments lean on import duty audit automation to spot the eligible entries at scale, group them by claim type, and keep the deadlines visible instead of tracking them in a spreadsheet nobody updates on a busy week.
When the protest gets denied
A denial is not always the end. If CBP rejects the protest or lets the review period lapse without acting, you can escalate to the Court of International Trade to preserve the claim. That path is more formal and usually worth a customs attorney’s involvement, but it exists precisely so a denial at the agency level is not automatically final.
Most disputes never reach that stage. They get resolved because the importer named the error clearly, filed on time, and handed over a packet that made the reviewer’s job easy.
The quieter lesson
Every recovered overpayment tells you something about the entries you did not check. If one classification error cost you real duty, the odds are decent that others sitting in your history did too. The importers who treat protests as a routine part of compliance, rather than a rare fire drill, are usually the ones who catch the pattern early and stop overpaying in the first place.
The dispute process works. It just rewards the teams who keep their entries organized enough to use it.
