Your CAPE Declaration Was Rejected: The Line-Level Reasons and How to Fix Them

Where CAPE stands, as of July 2, 2026

CAPE is CBP's refund system for the IEEPA tariffs the Supreme Court struck down on February 20, 2026. It went live in ACE on April 20, 2026. Phase 1 covered unliquidated entries and entries liquidated within roughly 80 days of submission, which CBP estimated at about 63 percent of refund-due entries. Phase 2 opened June 29, 2026 and takes the entry types Phase 1 turned away, reconciliation, drawback-flagged, and AD/CVD entries among them. Only the importer of record or the original filing broker can file, in either phase, and finally-liquidated entries remain outside both phases while the Federal Circuit appeal runs.

The scale of the queue explains the strictness: roughly 330,000 importers paid an estimated $166 billion under the struck-down programs, and as of late May 2026 only about 157,402 CAPE declarations had been filed. Per press reporting of CBP figures, $89.6 billion in declarations had been accepted and $20.6 billion paid as of June 1, 2026. The machinery works. It just rejects ruthlessly on data quality. This article is part of The Manufacturer's Guide to Checking Your Tariff Bill.

The rejection rate, and why it is so high

Roughly 30 percent of CAPE declarations fail initial file validation, per Baker Tilly's May 26, 2026 analysis of the filing data. Three design choices in CAPE drive the number:

• Validation runs at two levels, file and entry, and a failure at either level stops the declaration.
• One ineligible entry can sink the whole declaration it travels in.
• An accepted declaration cannot be amended. What gets accepted is final, including its omissions.

Those rules reward filers who reconcile before submitting and punish everyone else with another trip through the queue.

The rolling timeline keeps minting new filers, too. Phase 1's roughly 80-day liquidation window is short against the normal liquidation cycle, where entries typically liquidate around 314 days after entry, so entries keep aging into and out of scope week by week; verify where your own entries sit with your broker. A declaration that was partly ineligible in May can be filed clean in July, and the reverse: waiting costs eligibility on entries that finally liquidate in the meantime.

The rejection classes, and the fix for each

File-level validation failures. The file itself fails: structure, format, required fields, internal consistency. The fix is mechanical. Rebuild the file from a clean export rather than hand-editing the rejected one, because hand edits fix the visible error and preserve the invisible ones.

Eligibility failures.An entry in the batch is a type the phase you filed under excludes. Since Phase 2 opened on June 29, 2026, the reconciliation, drawback-flagged, and AD/CVD entries Phase 1 turned away have a CAPE lane of their own; finally-liquidated entries remain outside both phases. The fix is routing, not correction: pull the ineligible entries out, resubmit the clean remainder, and file the Phase 2 types in their own batch. What no phase takes is a different pathway's problem, not a lost cause.

Duty-calculation mismatches.The "unable to calculate duty" class. Your file disagrees with CBP's current record on HTS, value, or quantity for a line. The most common root cause is a Post Summary Correction that changed the entry after your data snapshot was taken: you filed from what the entry used to say. The fix is to re-pull current entry data from ACE and diff it against your file, line by line, before resubmitting.

Filer eligibility. CAPE accepts the declaration only from the importer of record or the original filing broker. If a freight forwarder, a new broker, or a parent entity filed, the rejection has nothing to do with the data. Refile from the right identity.

Batch hygiene decides everything

Because one ineligible entry can sink a declaration and an accepted declaration cannot be amended, batch construction is the actual skill. Submit clean, verified entries in one batch, and quarantine anything doubtful into a second submission. Filing one giant declaration to save effort is how a 95-percent-clean filing becomes a 100 percent rejection, and filing a too-small clean batch costs nothing but a second upload.

The no-amendment rule cuts the other way as well: an accepted declaration that omitted eligible entries cannot be topped up by editing it. Keep a running ledger of which entries went into which declaration and which remain unfiled, because the question "did we already claim this entry?" gets expensive to answer from memory three submissions in.

Reconcile against the entry record before resubmitting

The manual pre-flight, line by line:

1. Pull fresh entry data from ACE today, not from the snapshot you filed from.
2. Diff your declaration file against the fresh pull on the three fields CAPE checks: HTS, value, quantity.
3. Where they disagree, the entry record wins. Update your file to match it, and note any line where a PSC changed the record since your snapshot.
4. Screen every entry against the eligibility rules of the phase you are filing under, Phase 2 since June 29, 2026, and route the ineligible ones out.
5. Confirm the filing identity is the importer of record or the original broker.
6. Resubmit the clean batch, and only the clean batch.

What CAPE structurally cannot fix

CAPE rules on the IEEPA refund math and nothing else. It cannot rule on classification, valuation, or origin, and it cannot reach finally-liquidated entries: CBP and DOJ deny authority to refund entries more than 180 days past liquidation without an importer-specific court judgment. The Court of International Trade ordered universal refunds, DOJ appealed to the Federal Circuit on June 2, 2026, and that question is pending as of July 2, 2026.

Money in those categories is not gone; it routes elsewhere. Classification, valuation, and origin issues travel by Post Summary Correction or protest, and the protest window runs 180 days from liquidation with no extensions; entries typically liquidate around 314 days after entry, so verify the dates on your own entries with your broker. The full routing table is in PSC, protest, CAPE, or drawback. And note what the IEEPA refund does not touch at all: the duties you are still paying today. Most importers checking IEEPA lines have never rechecked their Section 301, 232, or 122 lines, which is the line-by-line method's whole subject.

While the appeal runs: preserve the rights you have

You do not control when the Federal Circuit rules, but you control whether your entries are still actionable when it does. The preserving moves are mundane: get current liquidation dates from your broker, file protests inside the 180-day window on entries where CAPE cannot reach, and keep the per-entry ledger current, so your rights are intact however the appeal lands. Verify each date with your broker; the windows run per entry, not per importer.

The fast path

The pre-flight above is a per-line reconciliation job, and that is a reading problem at scale. Upload your entry summaries and ACE export at the tariff checkand the report rebuilds each line from the documents, prices what each line owed against what it paid, and flags what CAPE cannot refund along with the pathway that can. The declaration-file diff itself, your file against today's entry record on HTS, value, and quantity, runs from a fresh ACE pull using the pre-flight above.