What To Do When CAPE Shows Accepted with Error(s)
Understand what Accepted with Error(s) means in ACE Claim Status, how to identify the rejected entries, and when to refile only the corrected rows.
Accepted with Error(s) is one of the most misleading statuses in the CAPE workflow.
It sounds close to success, but it is not the same thing as a clean acceptance.
In CBP’s ACE quick reference guide, Accepted with Error(s) means the claim moved forward for some entries, while other rows still failed or were flagged. If you treat that status like a full approval, you can stop too early and leave recoverable entries unresolved.
What This Status Actually Means
Think of Accepted with Error(s) as a split outcome.
ACE has already processed the declaration far enough to create the claim, but the result is mixed:
- some entries were accepted
- some entries were rejected
- some entries may show a specific error description in the claim details file
This is different from a pure file upload failure. At this stage, ACE has moved beyond the upload job and into claim-level review.
First Check the Right ACE Screen
Do not start in the wrong tab.
- File Uploads tells you about the upload job, file-level problems, and the Validation Result File.
- Claim Status tells you the processed declaration outcome, including
Rejected,Accepted with Error(s), andAccepted.
If you see Accepted with Error(s), your next move is in Claim Status, not just the original upload screen.
The Five-Step Response Sequence
When CAPE shows Accepted with Error(s), do this in order:
- Open Claim Status and locate the claim number.
- Download Claim Details.
- Separate the accepted entries from the rejected entries.
- Read the error description on the rejected rows before touching the original file.
- Rebuild a new declaration only for the corrected rejected entries.
That order matters because the accepted rows do not need to be resubmitted just because another row in the same claim failed.
What Claim Details Usually Tells You
CBP’s ACE quick reference guide shows that Claim Details can list each entry number with its status and error description.
Examples include:
Entry Summary UpdatedEntry Summary Is Cancelled/RejectedEntry Summary Is In Trade Control
Those descriptions help you decide whether the next problem is:
- a correctable entry issue,
- an account or control issue,
- or a sign that the entry may not fit the current CAPE lane at all.
When You Refile Only the Rejected Entries
CBP’s practical rule is straightforward:
- if the problem is a file upload error, fix the file and reupload the full file
- if the problem is a claim error, fix only the affected entries and refile those corrected entries on a new CAPE declaration
Accepted with Error(s) usually falls into the second bucket.
That is why the correct next move is usually not to resend the entire original file. Refile only the corrected rejected rows after you understand what actually failed.
Common Reasons a Claim Lands Here
The most common reasons are not all technical.
Some are operational:
- the entry data did not align with the filing account
- the row passed file upload but failed deeper validation
- the entry needs correction before it can be resubmitted cleanly
Some point to a larger posture issue:
- the entry is outside the clean Phase 1 timing lane
- the entry is blocked by protest posture
- the entry sits in a category CAPE is not handling in the current phase
So do not assume Accepted with Error(s) always means “fix the formatting and try again.”
When This Is Not Just a Refile Problem
Pause before you refile if the rejected entries involve:
- liquidations older than the current CAPE window
- open protests
- multiple brokers or filer mismatches
- drawback, reconciliation, or other category blockers
At that point, the real issue may be path selection, not claim cleanup.
If that sounds like your file, read our CAPE, Protest, or CIT path guide before you keep resubmitting rows.
The Practical Takeaway
Accepted with Error(s) means progress, but not closure.
The safe workflow is:
- preserve the accepted rows,
- isolate the rejected rows,
- use Claim Details to understand why those rows failed,
- then refile only the corrected rejected entries when the issue is truly a claim-level correction.
If you need the full operational flow, go back to our ACE Portal CAPE filing guide. If you need the broader upload-error framework, see our CAPE troubleshooting guide.
Not sure whether the failed rows belong in CAPE at all?
If your rejected entries involve protests, older liquidations, or multiple filing parties, get a case-specific review before you keep rebuilding declarations around the wrong path.
Sources
Source: CBP, ACE Portal CAPE Declarations Quick Reference Guide, April 2026.
Source: CBP April 2026 CAPE processing guidance and related ACE workflow releases.
We are not a law firm, customs broker, or government agency. This article is educational only.