If you’ve been following the IEEPA tariff refund story, you’ve probably seen “CAPE” mentioned everywhere — in court filings, trade publications, and probably your customs broker’s emails. But most of the coverage assumes you already know what it is. You don’t. And that’s fine, because until recently, CAPE didn’t exist.
CAPE is the system CBP is building right now — from scratch — to process IEEPA tariff refunds for 330,000+ importers who overpaid duties between February 4, 2025, and February 24, 2026. It’s the government’s answer to the logistical nightmare created by the Supreme Court’s ruling in Learning Resources, Inc. v. Trump, which invalidated all IEEPA tariffs and left CBP holding billions in duties it now has to give back.
Here’s everything you need to know about CAPE: what it stands for, what it does, where it stands right now, and what it means for your refund.
What CAPE actually stands for
CAPE stands for Claims Adjudication and Processing Engine. It’s a new software module being built inside CBP’s existing Automated Commercial Environment (ACE) system. Think of ACE as the massive database where all U.S. import data lives — every entry, every tariff classification, every duty payment. CAPE is a specialized layer on top of ACE designed to handle one specific job: processing IEEPA refund claims at scale.
CBP didn’t have a system like this before because they’ve never had to process refunds at this scale before. Previous tariff adjustments — even large ones like certain Section 201 safeguard modifications — involved thousands of entries, not 53 million entry lines. The existing ACE infrastructure can handle individual post-summary corrections and protests, but it was never designed for mass automated refund processing across hundreds of thousands of importers simultaneously.
So CBP had to build something new. And they had to build it fast, because the CIT’s March 4 order set clear expectations for when refunds should begin flowing.
The name itself tells you the design philosophy: this is meant to be an adjudication engine, not just a payment processor. CAPE doesn’t just cut checks — it validates claims, cross-references entry data, flags discrepancies, and routes problematic entries for manual review. That’s both good news (automated processing means faster refunds for clean claims) and bad news (the review process creates bottlenecks that could delay your refund by months).
The four components of CAPE
Based on CBP’s court-filed status declarations, CAPE has four distinct components. Understanding each one helps you see where your claim will flow and where delays might occur.
1. Claim Portal
This is the front door. The Claim Portal is where importers (or their brokers and representatives) will submit refund declarations. It’s a web-based interface within the ACE system that accepts claim data, validates it against existing entry records, and feeds validated claims into the processing pipeline.
As of the most recent CBP status update filed with the Court of International Trade, the Claim Portal was approximately 73% complete. The remaining work involves user interface testing, security certification, and integration with ACE’s authentication system.
The portal will require specific data for each claim: entry summary numbers, HTS codes under headings 9903.01 and 9903.02, duty amounts paid, and importer of record information. If you’ve already pulled your ES-003 Entry Summary Details report from ACE, you have most of what you’ll need.
2. Mass Processing Engine
This is the heart of CAPE. Once claims enter the system through the portal, the Mass Processing Engine handles automated validation and adjudication. It cross-references your claimed duty amounts against CBP’s own records in ACE, verifies HTS code eligibility, calculates refund amounts including statutory interest under 19 U.S.C. Section 1505(c), and batches approved claims for payment.
This component was approximately 45% complete as of the last court filing — the least finished of the four. That’s significant because it’s the component that determines how fast claims actually move through the system. If the Mass Processing Engine can handle high volumes with minimal manual intervention, refunds will flow relatively quickly. If it chokes on data quality issues and routes a large percentage of claims to manual review, the entire timeline stretches.
The engine is designed to handle “clean” claims — those with complete data that matches CBP’s records — without human intervention. The question is what percentage of claims will be clean enough for automated processing. CBP hasn’t published an estimate.
3. Review and Liquidation Module
When the Mass Processing Engine flags a claim for discrepancies — mismatched duty amounts, HTS codes that don’t align with CBP records, entries with pending compliance actions — the claim routes to the Review and Liquidation Module. This is where CBP staff manually examine the claim, resolve discrepancies, and either approve or deny specific line items.
This module was approximately 80% complete, making it the most finished component. That makes sense — it’s built on existing ACE liquidation workflows that CBP staff already use daily. The challenge isn’t the software; it’s the staffing. CBP has roughly 2,500 staff available for IEEPA processing across all ports. When you divide 53 million entry lines by 2,500 staff, you get a ratio of 21,200 entry lines per person. Even if only 10% of claims require manual review, that’s still 5.3 million lines flowing through a manual process.
If your data is clean, you want to avoid this module entirely. Every claim that hits manual review adds weeks or months to your timeline. That’s why data preparation before the portal opens matters so much.
4. Refund Disbursement
The final component handles the actual payment. Once a claim is approved — either through automated processing or manual review — the Refund Disbursement module calculates the final amount (including accrued statutory interest), generates the payment instruction, and sends it to Treasury for ACH disbursement.
This module was approximately 63% complete. It requires ACH enrollment — if you’re not enrolled in CBP’s ACH system, you’ll need to set that up before you can receive any refund, regardless of how quickly your claim is processed. Your customs broker can help with ACH enrollment if you haven’t done it already.
Get your free Impact Assessment —>
How CAPE integrates with ACE
CAPE isn’t a standalone system. It’s built as a module within ACE, which means it has direct access to all of your existing entry data. When you submit a claim through the CAPE portal, the system can immediately pull up your original entry summary, verify the HTS codes you’re claiming, confirm the duty amounts you paid, and check the liquidation status of each entry.
This integration is actually one of CAPE’s biggest advantages. In a traditional protest or post-summary correction process, CBP staff have to manually pull up entry records, cross-reference documents, and verify data points one at a time. CAPE automates that cross-referencing, which is why CBP believes it can process the majority of straightforward claims without manual review.
But the integration also means that your ACE data quality directly affects your CAPE experience. If your original entry summaries have errors — wrong HTS codes, missing tariff ordinal numbers, duty amounts that don’t match — CAPE will flag those discrepancies automatically and route your claim to manual review. You won’t get a chance to fix the data during processing; you’ll just wait in the review queue while a CBP officer investigates.
That’s why pulling and reviewing your ACE data now — before the portal opens — is the single most important thing you can do to accelerate your refund. If you find discrepancies between your records and what ACE shows, you have time to resolve them with your broker before CAPE goes live.
Current completion status and expected timeline
Here’s where things stand as of the most recent CBP court filing:
| CAPE Component | Completion | Status |
|---|---|---|
| Claim Portal | 73% | UI testing, security certification remaining |
| Mass Processing Engine | 45% | Core logic under development |
| Review & Liquidation | 80% | Built on existing ACE workflows |
| Refund Disbursement | 63% | ACH integration in progress |
CBP has indicated a target launch of mid-April 2026 for initial portal access, though they’ve been careful to qualify this as a target rather than a commitment. Given that the Mass Processing Engine is still less than half complete, some slippage is plausible.
The CIT has scheduled follow-up status conferences to track CBP’s progress. If CBP misses its targets, the court has the authority to impose deadlines — though how enforceable those deadlines would be in practice is debatable. Courts can order agencies to act, but they can’t write software faster.
Capacity constraints: the 2,500-staff reality
Even when CAPE is fully operational, CBP faces a fundamental capacity constraint that no amount of automation can fully solve. The agency has approximately 2,500 staff available for IEEPA refund processing. These aren’t dedicated IEEPA staff — they’re existing CBP personnel who also handle ongoing import compliance, trade enforcement, and other duties.
For context, here’s the math:
- 330,000+ importers with potential IEEPA claims
- 53 million entry lines affected
- 2,500 CBP staff available
- That’s a ratio of 132 importers per CBP staff member or 21,200 entry lines per person
CAPE’s automation is designed to reduce the manual workload, but every claim that can’t be processed automatically becomes a manual task for an already-stretched workforce. CBP’s own court filings acknowledge this constraint, which is why they’ve been careful not to promise specific processing timelines.
The practical implication is that even after CAPE launches, your place in the processing queue matters enormously. Early filers with clean data will move through the automated pipeline quickly. Late filers, or those with data quality issues, will end up in manual review queues that could stretch 18-36 months.
What the court expects from CBP
The CIT hasn’t simply asked CBP to build CAPE and trusted them to figure out the timeline. The court has established an active oversight process with regularly scheduled status conferences where CBP must report progress on each CAPE component.
This judicial oversight matters for two reasons. First, it creates accountability. CBP can’t quietly push back deadlines without explaining why to a federal judge. Second, it creates a public record of CAPE’s development that importers and their advisors can track. Every status declaration CBP files becomes part of the court record, which is how we know the completion percentages and staffing figures cited throughout this article.
The court has also retained jurisdiction over the implementation proceedings, which means it can issue additional orders if CBP falls behind. In theory, the CIT could set hard deadlines for CAPE milestones or even appoint a special master to oversee the refund process. In practice, courts are reluctant to micromanage agency IT projects, but the threat of judicial intervention gives CBP strong incentive to stay on track.
For importers, the court oversight is reassuring but shouldn’t create complacency. The court can require CBP to act, but it can’t make software development go faster. Your best protection against CAPE delays is being prepared to file the moment the portal opens and having backup strategies — protests, claim assignment — in place for entries that can’t wait.
Common misconceptions about CAPE
Several myths about CAPE have spread through the importer community. Let’s clear them up.
Myth: “CAPE will automatically refund everyone.” CAPE doesn’t process refunds automatically for all importers. You have to file a claim. If you don’t file, you don’t get a refund — CBP isn’t going to proactively send checks to 330,000 importers.
Myth: “My broker will handle everything.” Your broker can file on your behalf, but they need your direction and approval. Many brokers are waiting for their clients to initiate the conversation. If you haven’t talked to your broker about IEEPA refunds yet, start today.
Myth: “I can file through CAPE and also file a protest on the same entry.” You can, and in many cases you should. Filing a protective protest on a liquidated entry preserves your rights regardless of what happens with CAPE. The two filings aren’t mutually exclusive — they’re complementary.
Myth: “CAPE will be faster than filing protests.” For clean claims from early filers, probably yes. But if your claim hits manual review, the protest path might actually resolve faster depending on your port’s processing speed. That’s why a hybrid strategy often makes sense.
Myth: “I should wait for CAPE before doing anything.” This is the most dangerous misconception. Waiting for CAPE means losing queue position, potentially missing protest deadlines, and forfeiting months of preparation time. Start pulling your ACE data and validating your entries now.
What this means for your refund strategy
Understanding CAPE’s architecture gives you a strategic advantage. Here’s what to do with that knowledge:
Prepare your data now. Don’t wait for the portal to open. Pull your ES-003 report from ACE, verify every entry against HTS headings 9903.01 and 9903.02, reconcile duty amounts, and resolve any discrepancies with your broker. Clean data means automated processing. Dirty data means manual review and months of delay.
Enroll in ACH. If you’re not enrolled in CBP’s ACH disbursement system, start that process immediately. No ACH enrollment means no refund disbursement, regardless of when your claim is approved.
File protective protests on liquidated entries. CAPE is designed for forward-looking claims processing, but it doesn’t replace the 180-day protest window on entries that have already liquidated. If you have entries approaching their protest deadline, file those protests now — don’t wait for CAPE.
Consider your four recovery paths. CAPE is the government processing channel, but it’s not the only option. For importers who can’t wait 18-36 months for government processing, claim assignment through institutional buyers provides immediate capital. Many importers use a hybrid approach: file clean claims through CAPE while assigning complex or high-value claims for immediate payment.
Get an Impact Assessment. An assessment validates your data, calculates your estimated refund including statutory interest, maps each entry’s liquidation status, and identifies any data quality issues that would delay CAPE processing. It’s the preparation step that positions you for day-one filing.
The bottom line
CAPE represents the largest automated claims processing effort in CBP history. It’s an ambitious system designed to solve an unprecedented problem — returning billions in wrongfully collected duties to hundreds of thousands of importers. But ambition doesn’t guarantee speed. The system is still being built, the staff are stretched thin, and the volume of claims will test even the most optimized processing engine.
Your job isn’t to wait for CAPE. It’s to be ready when CAPE is ready for you.
