How to Fix CAPE Upload Errors Before You Miss the Phase 1 Window

If ACE rejects your CAPE declaration, the first question is not whether your refund rights disappeared. The first question is what kind of error ACE is showing you.

CBP’s April 2026 ACE quick reference guide separates CAPE problems into two different buckets:

• File upload problems in the File Uploads work area
• Claim-level problems in the Claim Status work area

That distinction matters because the fix is different. Sometimes you need to rebuild and reupload the entire file. Other times you should correct only the rejected entries and file those entries on a new CAPE declaration.

Source: CBP, ACE Portal CAPE Declarations Quick Reference Guide, April 2026.

If you need the full step-by-step submission workflow before you troubleshoot, start with our ACE Portal CAPE filing guide.

Start With the Right ACE Screen

ACE uses two CAPE work areas for two different jobs:

• File Uploads shows the upload job itself, along with validation-result downloads for file and row-level errors.
• Claim Status shows what happened after ACE processed the declaration, including whether the claim was Rejected, Accepted with Error(s), or Accepted.

If you only look at one screen, you can easily fix the wrong problem.

Four Fast Checks Before You Rebuild Anything

Before you touch the file, confirm these basics:

1. You used the official CAPE template from the ACE tab.
2. The file is saved as CSV (Comma delimited).
3. The first column still uses the Entry Number header and each row contains one complete 11-digit entry number.
4. The file is under 1 MB and does not contain duplicate entries.

Source: CBP, ACE Portal CAPE Declarations Quick Reference Guide, April 2026.

What Failed Initial Validation Usually Means

Failed initial validation usually means ACE found a problem before it could treat the file as a clean CAPE submission.

CBP’s examples include:

• Entry numbers that are not 11 characters long
• Duplicate entry numbers
• A filer code mismatch

This is where the Validation Result File matters. ACE can generate a download that identifies the affected rows and the error description, including examples such as “not 11 characters long” and “filer code not matching.”

What To Do Next

If the issue is in this category, correct the file itself and reupload the full file.

Do not assume you should break out one row and keep moving. Initial-validation problems usually mean the upload package is wrong, not just one downstream claim outcome.

What Rejected by Batch Validation Usually Means

Rejected by batch validation usually means ACE could read the file, but one or more entries failed deeper system validation.

CBP’s examples include:

• The entry does not exist in ACE
• The importer of record does not match the current account context

In practice, this is also where other CAPE blockers can surface, such as entries that fail eligibility review or do not line up with the filing party’s data.

Where To Check the Details

Start with the Validation Result File in File Uploads. If the declaration moved far enough to create a claim, also open Claim Status and click the Claim Number to download the Claim Details file.

Together, those two files tell you whether the problem is still at the upload-validation stage or has become a claim-specific rejection.

What Accepted with Error(s) Actually Means

This is the CAPE status that can mislead filers the most.

Accepted with Error(s) does not mean the whole declaration is fine. It means ACE accepted at least some entries, while rejecting or flagging others.

That creates three immediate follow-up tasks:

1. Open Claim Status and confirm which entries were accepted.
2. Download Claim Details and isolate the rejected rows with their error descriptions.
3. Build a new, narrower CAPE declaration for the corrected rejected entries only.

If you skip that review, you can mistakenly think the job is complete when only part of the declaration made it through.

When To Reupload the Full File vs. Only Corrected Entries

CBP’s quick reference guide draws a clean line:

• If you are dealing with file upload errors, fix the file and reupload the full file.
• If you are dealing with claim errors, fix the affected entries and reupload only those corrected entries.

This is one of the most useful practical rules in the ACE quick reference guide because it prevents duplicate resubmissions and helps you keep your CAPE filing history clean.

A Practical Triage Sequence for Importers

If the Phase 1 window is closing and you need to move quickly, use this order:

1. Fix obvious file problems first: wrong file type, missing template structure, duplicate rows, bad entry length, or oversize file.
2. Download the validation-result output before changing anything so you preserve the original error record.
3. Separate true file errors from entry-specific claim errors.
4. Reupload the full file only if the file itself is defective.
5. Refile only the corrected rejected entries if the original declaration already accepted the clean rows.

If your rejected entries also involve protests, older liquidations, broker mismatches, or other non-routine facts, CAPE may not be the only path you should rely on.

Do Not Treat Every Rejection as a Purely Technical Problem

Some CAPE rejections look technical at first but point to a legal or procedural issue instead.

That is especially true when the rejected entries involve:

• liquidations outside the current Phase 1 lane
• open protests
• broker-of-record mismatches
• drawback or reconciliation conflicts

If that is your fact pattern, use the rejection as a signal to review the broader strategy, not just the CSV formatting.

For the full process context, see our Complete Guide to Filing IEEPA Refund Claims Through CAPE.

CBP’s Official CAPE Error Dictionary (CSMS #68401616)

When an on-screen error description is ambiguous, the canonical reference is CBP’s CAPE Error Dictionary, published in CSMS #68401616 (April 29, 2026 update). The dictionary defines 15 distinct CAPE error codes that span the entire pipeline:

• File-format errors — wrong file type, missing header row, oversize file, empty file
• Entry-format errors — entry length, duplicate entry numbers, invalid characters, filer-code mismatches
• Claim-validation errors — entry not found, IOR mismatch, ineligible category (drawback, reconciliation, AD/CVD pending liquidation), open protest conflict
• Post-acceptance errors — Entry Summary Is Cancelled/Rejected, Entry Summary Is In Trade Control

If the on-screen status does not give you enough to act on, look the specific error string up in CSMS #68401616 — it tells you whether the error is at the file, entry, or claim layer, which tells you whether to refile the whole file or only the corrected entries.

Source: CBP CSMS #68401616, CAPE Error Dictionary update, April 29, 2026.

Next Steps if You Are Still Stuck

1. Recheck your file against our CAPE CSV preparation guide.
2. Review whether your entries are even inside the current CAPE Phase 1 window.

We are not a law firm, customs broker, or government agency. We provide educational content and connect importers with vetted trade law professionals.