CAPE Error Decoder: Every Error Message and How to Fix It

What is the CAPE Error Decoder?

The CAPE Error Decoder is a comprehensive reference for every error message and rejection code returned by CBP's Consolidated Administration and Processing of Entries (CAPE) Phase 1 process during IEEPA refund validation. Each error has a specific cause and a specific fix. This pillar covers the GOODS VALUE AMOUNT validation errors, HTS sequence and Chapter 1-97 relationship errors, FTZ Type 06 mismatch errors, reconciliation conflict errors, IOR validation errors, line-level filter exclusions, and the system-level rejections that block CAPE filing entirely. Each error references the right downstream action: PSC, Form 19 protest, CIT complaint, or no further action.

How do I know which CAPE error code I received?

CAPE error codes appear on REV-615 (the Trade CAPE Detail Refund Report) and on inline ACE error responses during CAPE Declaration submission. REV-615 ties each excluded entry to the specific reason code. ACE inline responses appear during filing if the Declaration is rejected before processing. Both sources are needed for complete error decoding: REV-615 for post-processing exclusions, ACE inline for pre-processing rejections. Decoded together, they explain every line that did not make it through CAPE Phase 1.

---

TL;DR: CBP's CAPE Phase 1 has been processing IEEPA refunds since April 20, 2026, with approximately $166 billion in IEEPA duties across 53 million entries from 330,000 importers flowing through the system. Every CAPE Declaration validates against multiple checks, and rejections happen at three layers: pre-processing (ACE inline errors), processing (Declaration-level rejections), and post-processing (line-level exclusions on REV-615). Each error code has a specific cause and a specific fix. This pillar consolidates the error decoding work scattered across our individual CAPE error posts (CAPE Declaration rejected error codes, FTZ Type 06 CAPE rejection HTS mismatch, CAPE refund came short on REV-603) into a single comprehensive reference. GingerControl's IEEPA refund service handles error decoding and remediation as part of the CAPE workflow, including REV-615 review, inline ACE error response analysis, and routing of excluded entries to PSC, Protest, or CIT channels.

Last updated: May 2026

---

How CAPE Errors Are Surfaced

CAPE errors appear in three places, each requiring different decoding:

1. ACE inline error responses during Declaration submission. When a CAPE Declaration is submitted, ACE validates the Declaration format and high-level eligibility before accepting it for processing. Format errors (malformed CSV, missing required fields, IOR mismatch) trigger inline rejections with error codes returned immediately.

2. CAPE Declaration-level rejection notices. After acceptance but before line-level processing, CBP may reject the Declaration as a whole for system-level reasons (filer authorization, batch size limits, processing errors). These appear as Declaration-level notices in ACE.

3. REV-615 line-level exclusions. After line-by-line processing, REV-615 (the Trade CAPE Detail Refund Report) lists entries that were excluded from refund disbursement with a reason code. This is where most error decoding happens because most filed Declarations are accepted at the Declaration level but contain some lines that get filtered during line-level processing.

For each error decoded below, the source (inline / Declaration-level / REV-615) is noted.

Pre-Processing Errors: ACE Inline Rejections

These errors appear during CAPE Declaration submission and block acceptance entirely. The Declaration cannot be processed until the underlying issue is fixed.

Error: Filer Authorization Missing or Invalid

Cause: The filer submitting the CAPE Declaration is not authorized to file on behalf of the IOR(s) listed. Common when a new filer/broker relationship has not been fully established in ACE, or when the Power of Attorney (POA) on file with CBP is outdated.

Fix: Verify the filer has an active POA on file for the IOR. Update Form 4811 if Notify Party or sub-account configurations need adjustment. Reach out to CBP Revenue Division if the POA appears current but the system shows otherwise.

Error: Batch Size Limit Exceeded

Cause: The CAPE Declaration includes more entries than the per-Declaration batch size limit allows.

Fix: Split the Declaration into multiple submissions, each within the batch size limit. CBP guidance specifies the current batch size; check the CAPE Trade Information Notice for current limits.

Error: Malformed CSV / Format Validation Failure

Cause: The submitted Declaration file does not conform to the required CSV format. Common issues: missing required columns, incorrect column ordering, non-UTF-8 character encoding, or missing entry summary numbers.

Fix: Validate the file format against CBP's published CAPE Declaration specification before submission. Use a validation script or template that matches the current required format.

Error: IOR Mismatch Across Entries

Cause: Entries within a single Declaration belong to different IORs that are not properly grouped or authorized under a single filer relationship.

Fix: Group entries by IOR and submit separate Declarations per IOR. Verify filer authorization for each IOR.

Processing-Level Errors: Declaration Rejection

These errors appear after acceptance but before line-level processing. The Declaration was accepted in form but rejected in substance.

Error: System Processing Failure

Cause: A CBP system-side issue prevented the Declaration from completing processing. May appear during peak processing periods.

Fix: Resubmit the Declaration after a delay (typically 24-48 hours). If the error persists, contact CBP Revenue Division for case-specific guidance.

Error: Duplicate Declaration Identifier

Cause: A Declaration with the same identifier has already been submitted and accepted. Common when a filer resubmits without changing the identifier.

Fix: Generate a new unique Declaration identifier and resubmit. Check whether the original submission was actually accepted; if so, do not resubmit.

Post-Processing Errors: REV-615 Line-Level Exclusions

These are the most common CAPE errors. The Declaration was accepted and processed, but specific lines within the Declaration were excluded from refund disbursement. Each line-level error has a specific reason code on REV-615.

Error: GOODS VALUE AMOUNT Validation Failure

Cause: The goods value amount on the entry does not validate against CBP's records, typically because of value discrepancies between the original entry filing and the Declaration data.

Fix: Reconcile the goods value amount against the original entry summary (CBP Form 7501 or equivalent). Common issues: rounding differences, currency conversion discrepancies, or amendment history not reflected in the Declaration. Correct the value and resubmit, or route to PSC if the entry is unliquidated and the corrected value applies to the entry data itself.

Error: HTS Sequence / Chapter 1-97 Relationship Error

Cause: The Chapter 99 IEEPA line (9903.01 or 9903.02) is not in the correct sequence relative to the underlying Chapter 1-97 HTS line. Most common in FTZ Type 06 entries.

Fix: Reorder the Declaration lines so the Chapter 99 IEEPA line follows the correct Chapter 1-97 line. See our dedicated post on FTZ Type 06 CAPE rejection HTS mismatch for FTZ-specific patterns. Resubmit the corrected Declaration.

Error: Outside Phase 1 Scope (>80 Days Past Liquidation)

Cause: The entry liquidated more than 80 days before CAPE Declaration submission. CAPE Phase 1 only covers entries within 80 days of liquidation.

Fix: Route the entry to Form 19 protest under 19 U.S.C. 1514 within 180 days of liquidation. If past 180 days, route to CIT complaint within the 2-year CIT statute under 28 U.S.C. 2636. See our 180-day deadline post for the channel decision tree.

Error: No Duty Differential / $0 or FREE Lines Filtered

Cause: The IEEPA duty on the entry calculated to $0, or the underlying HTS line was already FREE. CAPE filters these because there is no refund to disburse.

Fix: No action required if the entry was genuinely $0 duty. Verify against ES-003 (entry summary line tariff detail report) to confirm the line calculated to $0.

Error: Reconciliation Status Conflict

Cause: The entry is flagged for reconciliation under 19 CFR Part 174 and is in a non-final ACE state. CAPE cannot process reconciliation-pending entries.

Fix: Resolve the reconciliation first, then file CAPE if still within Phase 1 window. If reconciliation will not resolve in time, route to Form 19 protest. See our CAPE for reconciliation flagged entries post for the workflow.

Error: Non-IEEPA Tariff Layer Filed Under Wrong Code

Cause: The line was filed under a non-IEEPA Chapter 99 code (Section 301 9903.88.xx, Section 232 9903.80/.81/.85.xx, or Section 122 9903.03.xx) that CAPE does not process. CAPE only refunds 9903.01 and 9903.02.

Fix: None via CAPE. Section 301, Section 232, and Section 122 duties are not CAPE-refundable. For Section 301 exclusion claims, file under the appropriate 9903.88.69 or 9903.88.70 exclusion line if eligible.

Error: Already-Refunded Line (Duplicate Claim)

Cause: The line was previously refunded through CAPE, PSC, or protest, and a duplicate claim was submitted.

Fix: Reconcile the importer's CAPE/PSC/protest history to identify the prior refund. Withdraw the duplicate from any pending submissions. If the prior refund was incomplete, route the unrefunded portion to the appropriate channel.

Error: Interest Calculation Validation Failure

Cause: The interest calculation on the Declaration does not match CBP's calculation using the IRS quarterly underpayment rate from deposit date to refund date.

Fix: Re-calculate interest using the IRS underpayment rate for each applicable quarter. Resubmit the corrected calculation.

Error: Bond Deposit Reconciliation Mismatch

Cause: The Declaration claims the refund against a cash deposit when the original duty was paid via bond, or vice versa.

Fix: Verify whether the original duty was paid via cash or against a bond. Reconcile the Declaration accordingly. For bond-paid entries, the refund flows back against the bond; for cash-paid entries, the refund flows directly to the importer.

Error: Account-Level Offset Applied

Cause: CBP deducted outstanding debts (liquidated damages, prior overpayments, Treasury federal debt offsets, TOP) from the refund. This is not technically a "rejection" but appears as a reduction in the disbursed amount.

Fix: See our IEEPA refund offsets post for offset validation and dispute paths.

Error Decoding Workflow

For importers receiving CAPE errors at scale, the decoding workflow:

Step 1: Pull REV-615 and inline error responses. For each Declaration, retrieve REV-615 (post-processing line-level exclusions) and any inline ACE error responses (pre-processing rejections).

Step 2: Categorize errors by code. Group errors by code to identify patterns. A Declaration with 100 line-level errors may have 80 of one type (e.g., outside Phase 1 scope) and 20 of another (e.g., HTS sequence error).

Step 3: Apply the fix per error category. For each error category, apply the fix above. Most errors fall into one of the categories listed; novel errors should be investigated specifically with CBP Revenue Division or specialized support.

Step 4: Resubmit or route to alternative channels. Lines that can be fixed and resubmitted to CAPE go back through Phase 1. Lines that fall outside CAPE Phase 1 route to PSC, Protest, or CIT.

Step 5: Document the resolution per line. For audit purposes, document the error encountered, the resolution applied, and the final disposition (refund received via CAPE, refund pending via protest, etc.).

Frequently Asked Questions

Where do CAPE error codes appear?

CAPE error codes appear in three places: ACE inline error responses during Declaration submission (pre-processing rejections), Declaration-level rejection notices in ACE (system-level rejections), and REV-615 line-level exclusions (post-processing). Most decoding work focuses on REV-615 because most filed Declarations are accepted at the Declaration level but contain some lines that get filtered during processing.

What does GOODS VALUE AMOUNT error mean?

The GOODS VALUE AMOUNT error indicates that the goods value on the entry does not validate against CBP's records. Common causes: rounding differences, currency conversion discrepancies, or amendment history not reflected in the Declaration. The fix is to reconcile the goods value against the original entry summary and resubmit.

What does CH 1-97 / HTS sequence error mean?

The CH 1-97 (or HTS sequence) error indicates that the Chapter 99 IEEPA line is not in the correct sequence relative to the underlying Chapter 1-97 HTS line in the Declaration. Most common in FTZ Type 06 entries. The fix is to reorder the Declaration lines so the Chapter 99 IEEPA line follows the correct Chapter 1-97 line.

Why are Section 301 and Section 232 duties filtered out of CAPE?

CAPE only refunds IEEPA Chapter 99 duties under 9903.01 and 9903.02. Section 301 (9903.88.xx), Section 232 (9903.80/.81/.85.xx), and Section 122 (9903.03.xx) are not CAPE-refundable. For Section 301 exclusion claims, file under the appropriate 9903.88.69 or 9903.88.70 exclusion line if eligible.

How do I fix a CAPE rejection on an FTZ Type 06 entry?

FTZ Type 06 entries commonly trigger the HTS sequence error because the Chapter 99 line placement differs from non-FTZ entries. See our dedicated post on FTZ Type 06 CAPE rejection HTS mismatch for the FTZ-specific fix.

What if my entry is rejected because it is past 80 days of liquidation?

Route the entry to Form 19 protest under 19 U.S.C. 1514 within 180 days of liquidation. If past 180 days, route to CIT complaint within the 2-year CIT statute. The protest path is the right channel for entries past CAPE Phase 1 window but within protest window.

How does GingerControl handle CAPE error decoding?

GingerControl's IEEPA refund service handles error decoding and remediation as part of the CAPE workflow. The service reviews REV-615, decodes each line-level exclusion, applies fixes where possible, and routes lines that fall outside CAPE Phase 1 to PSC, Protest, or CIT.

Can I resubmit a Declaration after fixing errors?

Yes. After fixing the underlying issues, the corrected Declaration can be resubmitted. Use a new Declaration identifier to avoid the duplicate identifier rejection. The fixed lines flow through Phase 1 processing again.

What if I receive an error code not listed here?

Novel or undocumented error codes should be investigated specifically with CBP Revenue Division or specialized support. The CAPE process is evolving; new error patterns may appear as CBP refines validation logic. Contact us if you encounter undocumented errors; we may have additional context.

---

Decode Your CAPE Errors and Recover the Refund

If your CAPE Declaration produced errors or REV-615 excluded some lines, the right decoding plus the right downstream action recovers the refund. Each error has a specific cause; most have a specific fix. Lines that cannot be fixed for CAPE typically route to PSC, Protest, or CIT.

Get a no-cost CAPE error review from GingerControl. The review decodes your REV-615 exclusions, applies fixes where possible, and routes remaining lines to the right recovery channel.

GingerControl is not just a tool. We work with importers, customs brokers, and trade compliance counsel on CAPE error decoding, REV-615 reconciliation, and parallel CAPE / PSC / Protest / CIT workstreams. Talk to our team about your CAPE error situation.

---

References

[REF 1] U.S. Customs and Border Protection, IEEPA Duty Refunds Data cited: CAPE Phase 1 framework, REV-615 reporting structure Source: CBP IEEPA Duty Refunds

[REF 2] CBP Trade Information Notice on CAPE Data cited: CAPE Phase 1 launch April 20, 2026; batch size limits Source: CBP Trade Information Notice CAPE Published: April 2026

[REF 3] CBP IEEPA Refunds and CAPE Webinar (April 2026) Data cited: 330,000 importers, $166 billion IEEPA duties, 53 million+ entries Source: CBP IEEPA Refunds CAPE Webinar Published: April 2026

[REF 4] 19 U.S.C. 1514, Protest of decisions of Customs Service Data cited: 180-day Protest deadline framework for entries outside CAPE Phase 1 Source: 19 U.S.C. 1514

[REF 5] 19 CFR Part 174, Protests Data cited: Protest framework and reconciliation interaction Source: 19 CFR Part 174

[REF 6] 28 U.S.C. 2636, Time for commencement of action at Court of International Trade Data cited: 2-year CIT statute for entries past 180-day protest window Source: 28 U.S.C. 2636

[REF 7] IRS Quarterly Interest Rates Data cited: IRS underpayment rate for interest calculation on IEEPA refunds Source: IRS Quarterly Interest Rates

[REF 8] CBP REV-603/REV-613 Quick Reference Card Data cited: REV-603 and REV-613 status code framework Source: CBP REV Reports QRC Published: April 2026