CAPE Declaration Rejected? Error Codes & How to Fix

What changed: Error names and fixes brought up to date with CBP's current CAPE error list (the June 25, 2026 split of the HTS sequence error), the PSC and ACH rules, Phase 3 and the court route, and our service wording corrected: we prepare the refund file and our licensed refund partner files it.

The short answer

A CAPE declaration is rejected when ACE cannot validate the file, or an entry on it, against CBP's CAPE rules. CBP told the Court of International Trade on October 6, 2026 that whole declarations fail mainly on importer or filer mismatches, bad entry numbers and CSV files that do not match CBP's template, and that single entries fail mainly for being too long past liquidation, carrying no IEEPA Chapter 99 line, or already sitting on an earlier declaration (Lord declaration, ECF 58). Each rejection points to a different fix: re-file CAPE, correct the entry with a Post Summary Correction and resubmit, file a 19 USC 1514 protest, or ask CBP directly.

Next step:Check every deadline on one entry

In this post
  1. How do I tell which fix applies to a rejected CAPE entry?
  2. TL;DR
  3. The two layers of CAPE rejection
  4. The nine rejection patterns I keep seeing
  5. Comparison: which rejection routes to which fix
  6. How GingerControl maps a rejected CAPE batch
  7. What to do this week if you have a rejected declaration
  8. FAQ
  9. If your team is staring at a rejected CAPE declaration
  10. References

How do I tell which fix applies to a rejected CAPE entry?

Read the Validation Result File first. File-level errors (format, header, authorization) kill the whole declaration and you re-file once corrected. Entry-level errors reject only the affected lines, and the right next step depends on the liquidation clock: still inside Phase 1 scope means re-file CAPE, past 80 days but inside 180 means 19 USC 1514 protest, past 180 means CIT.

TL;DR

If your CAPE declaration came back rejected, the worst thing you can do is resubmit the same file. CBP's CAPE Declarations and Error Definitions guide splits errors into file-level (full declaration rejected) and entry-level (only specific lines rejected), and each error has a defined route back to a refund: re-file CAPE, correct the entry with a Post Summary Correction and resubmit, file a protest under 19 USC 1514, or ask IEEPARefunds@cbp.dhs.gov. GingerControl built the IEEPA refund service because the difference between a fast refund and a forfeited claim is usually one routing decision made within a 180-day window.

Match a rejected declaration to the CAPE error messages and fixes before resubmitting the same file.

Last updated: October 10, 2026


The two layers of CAPE rejection

CAPE runs validation in two passes, and the layer that fails determines how much of your work you lose.

File-level validation checks the CSV itself: format, header row, entry number format, and submitter authorization (the filer code, or the importer of record number, must match the entries). A failure here rejects the entire declaration. Nothing inside the file is preserved, and you upload a corrected version once the underlying issue is fixed.

Entry-level validation checks each entry number against ACE's record of that entry: does it exist, does it carry a dutiable 9903.01 or 9903.02 line, is the entry within 80 days of liquidation, is its entry type allowed, is it free of an open protest, a drawback claim or a filed reconciliation, and was it already included in a prior declaration. Failures here only knock out the affected entries. Accepted entries continue processing.

The Validation Result File is the source of truth for file-level errors: select the File Upload Job # in the File Uploads subtab of the CAPE tab and download it. Entry-level results sit under the claim number in the Claim Status subtab. Open the results alongside your original CSV and match each rejected entry to its error code before doing anything else. As CBP puts it in its CAPE trade information notice, "If a submission fails any part of the file validation series, ACE rejects the CAPE declaration," while an entry that fails an entry check is dropped and "ACE rejects that entry summary from the CAPE Declaration and continues processing the remaining entry summaries."

The nine rejection patterns I keep seeing

Since Phase 1 opened on April 20, 2026, the rejected entries fall into a finite set of patterns, and CBP's error list puts a name on each one. Each one has a specific diagnosis path and a specific fix.

1. HTS relationship mismatch or invalid HTS (the old sequence-mismatch error, often FTZ Type 06)

What triggers it. ACE cannot validate the HTS lines on the entry. Until June 25, 2026 this came back as HTS RELATIONSHIP/SEQUENCE MISMATCH, which the trade bar reported hitting self-filing FTZ operators on weekly Type 06 entries from late April 2026. CBP then split it into two narrower errors: HTS RELATIONSHIP MISMATCH, when an add, replace or derived HTS code is on the entry without the corresponding HTS code it needs, and INVALID HTS, when the line date falls outside the begin and end dates of an HTS code on the entry (CSMS #69056483). A related message, UNABLE TO CALCULATE DUTY, means a duty computation code on the entry cannot be calculated.

Diagnose from ACE. Open the entry summary in ACE and check each Chapter 99 line against the HTS code it depends on, and each HTS code against its begin and end dates. A missing companion code points to a relationship mismatch; a code that was end-dated and replaced since you filed points to invalid HTS.

Fix. If the entry was rejected under the old sequence-mismatch message, resubmit it on a new CAPE declaration: CBP narrowed the check, and many of those entries now pass. If it comes back with HTS RELATIONSHIP MISMATCH, file a Post Summary Correction that adds the corresponding HTS code; if INVALID HTS, file a PSC that replaces the expired code with its replacement. Once the PSC has processed, resubmit the entry on a new declaration (CSMS #69056483). One exception: since August 21, 2026, ACE rejects any PSC that changes an IEEPA HTS line on an FTZ Type 06 entry (error F883, CSMS #69635410), so if the fix on a Type 06 entry touches the 9903.01 or 9903.02 line, ask your CBP client representative first. For UNABLE TO CALCULATE DUTY and other technical problems, email IEEPARefunds@cbp.dhs.gov. Interest keeps running meanwhile: refund interest is counted from the deposit date to the date the entry liquidates or reliquidates (19 U.S.C. 1505).

2. Entry has no IEEPA HTS line

What triggers it. ACE returns NO IEEPA HTS ON ENTRY: the entry carries no IEEPA Chapter 99 number, so there is no 9903.01 or 9903.02 line for CAPE to remove and nothing for it to refund. CBP named this as one of the main reasons entries fail.

Diagnose from ACE. Pull the ES-003 report for the entry with the IEEPA tariff indicator, which shows every line with assessed duties. If no line carries a 9903.01 or 9903.02 code, CAPE has nothing to refund on that entry.

Fix. Remove the entry from the declaration. If you believe IEEPA duty was paid anyway but reported without its Chapter 99 line, do not use a PSC to start the refund: CBP prohibits initiating an IEEPA refund request by filing a Post Summary Correction (CSMS #68340863). A liquidated entry can still be protested under 19 USC 1514 within 180 days of liquidation; for an unliquidated one, ask CBP at IEEPARefunds@cbp.dhs.gov or your counsel before you file anything.

3. 9903.01 or 9903.02 line shows $0 or FREE

What triggers it. The Chapter 99 line is on the entry but the duty amount is zero, either because a duty-free provision applied (de minimis, exclusion, FTA preference) or because the rate was coded FREE at the time of entry. CAPE checks for at least one dutiable IEEPA Chapter 99 code (CBP's CAPE notice), and it will not refund what was not paid.

Diagnose from ACE. ES-003 shows the duty amount per line. If the 9903.01/.02 row reads $0 or FREE, this entry has nothing to recover under CAPE.

Fix. No CAPE path, and a PSC cannot be used to start an IEEPA refund (see pattern 2). If you believe IEEPA duty was in fact paid on the entry, a liquidated entry can be protested within 180 days of liquidation; otherwise the entry simply does not belong on the declaration.

4. Entry outside Phase 1 scope (past 80 days liquidated)

What triggers it. Phase 1 accepts unliquidated entries and entries within 80 days of liquidation, and Phase 2 keeps the same limit. An entry that liquidated more than 80 days ago is out of scope, and ACE rejects it with ENTRY SUMMARY IS IN FINAL LIQUIDATION STATUS.

Diagnose from ACE. Check the entry's liquidation date on the entry summary. Add 80 days. If today is after that, CAPE Phase 1 is not your route.

Fix. Switch to a formal protest under 19 USC 1514 if you are still within 180 days of liquidation. The protest is filed on CBP Form 19 and keeps the liquidation from becoming final; CAPE does not take protested entries yet, and CBP lists them for a later phase. Walk through the 1514 protest process for the specific filing mechanics. If the entry liquidated more than 180 days ago with no protest, the remaining path is a suit in the Court of International Trade under 28 U.S.C. 1581(i), which must be filed within two years after the claim accrues (28 U.S.C. 2636(i)); no court has yet ruled when that is. Since October 6, 2026, CAPE Phase 3 takes finally liquidated entries, but only from plaintiffs whose entries the court has ordered reliquidated. On October 8, 2026 the court certified a class in Freestyle World v. CBP covering importers of record who paid IEEPA duties between February 1, 2025 and February 19, 2026, except those that sued separately, but it has not yet ordered relief for the class (ECF 61).

5. Missing ACH refund banking details

What triggers it. The IOR sub-account in ACE does not have ACH Refund Authorization configured. This one is not a rejection at all: CBP can accept the declaration, but it holds the refund until refund bank details are on file. As of October 2, 2026, 20,362 refunds worth about $1.1 billion were waiting on them.

Diagnose from ACE. Log into the ACE Portal, navigate to the Importer sub-account, and check the ACH Refund Authorization tab. As CBP's CAPE notice puts it, refund bank account information "is specific for refunds and is separate from any ACH information used to make payments to CBP." A blank ACH Refund tab is the issue, even if ACH Debit (for paying duties) is fully configured. The REV-613 report lists any refund rejected for missing ACH refund enrollment.

Fix. Submit ACH Refund Authorization through the Importer sub-account. Since October 10, 2026, adding or changing refund bank details needs a security token sent by email or text (CSMS #70162211). There is no paper check to fall back on: under CBP's Electronic Refunds rule (91 FR 21) refunds go by ACH apart from rare waivers, and CBP holds the money until the details are on file. You do not need to re-file the declaration.

6. Account mismatch: the importer of record number does not match

What triggers it. ACE rejects the whole upload with ACCOUNT MISMATCH when the importer of record number on an entry summary does not match the IOR number of the Importer account that uploaded it. It usually means some entries were filed under another IOR number or suffix, such as a subsidiary's. CAPE has no separate duplicate-EIN error; the IOR number is what it matches.

Diagnose from ACE. Download the Validation Result File and compare the IOR number on each flagged entry summary with the IOR number of the account you uploaded from.

Fix. Take those entries out, upload the rest again as a new file, and file the removed entries from the Importer sub-account for their own IOR number. If that IOR number has no Importer sub-account yet, add it through CBP's ACE Portal Account Application Web Form, which handles new sub-accounts and sub-account identifiers on an existing top account (CBP).

7. Wrong filer code (broker did not file the entry)

What triggers it. For Filer and Organizational Broker accounts, CAPE requires that the first three characters of each entry number match the filer code of the submitting account; the error reads FILER CODE NOT MATCHING. A broker filing CAPE on behalf of an IOR must be the broker that filed that entry, and the entry number's first three characters are that broker's filer code. If the broker now filing CAPE did not file the entry, ACE rejects the upload on filer-code mismatch.

Diagnose from ACE. Look at the first three characters of the rejected entry numbers in your CSV and compare to the filer code of the ACE account that submitted the declaration. Any mismatch is the cause.

Fix. Either the IOR files CAPE directly from its own Importer account (which sidesteps the filer code rule because an Importer account is matched on the IOR number, not the filer code), or the broker that filed the entries files. If the original broker has gone dark or the relationship has ended, IOR-direct submission is the path: a power of attorney does not let a new broker file for entries it did not file, because CBP allows only the IOR or the licensed broker that filed the entries (CBP). Our power of attorney guide covers the authorization side. Switching filer code on the historical entry itself is not realistic.

8. Entry already on a prior CAPE declaration or under active protest

What triggers it. Each entry may sit on only one accepted CAPE declaration, and an entry on an open or suspended protest is rejected with PROTEST ON ENTRY. If it was included on a prior accepted declaration, or a 1514 protest is already pending on the same liquidation, the new declaration line is rejected.

Diagnose from ACE. Cross-check the entry against your prior CAPE submissions (the ES-022 report links accepted declarations to their entries) and your protest log. The claim's results file gives the rejection reason for each entry.

Fix. For a duplicate CAPE submission there is nothing to fix: the entry is already processing on the first declaration, so drop it from the new one. For an entry already under protest, CBP says that if the protest was filed only for the IEEPA refund and the entry is within 80 days of liquidation, the importer may withdraw the protest and put the entry on a CAPE declaration for faster processing; a suspended protest needs its suspension lifted by the processing Center first (CSMS #68340863). Otherwise leave the entry off CAPE and let the protest run. Do not have both routes live on the same entry.

9. Entry date outside the IEEPA window

What triggers it. The entry date is before February 4, 2025, when the first IEEPA Chapter 99 codes took effect, or after February 23, 2026, the last day IEEPA duties were collected: collection stopped for goods entered on or after February 24, 2026 (CSMS #67834313), after the Supreme Court ruled the tariffs unlawful on February 20, 2026. There is no IEEPA duty to refund on entries outside that window.

Diagnose from ACE. Check the entry date on the entry summary. Confirm against the IEEPA effective dates.

Fix. Remove the entry from the declaration. If duty was paid on a Chapter 99 code that is not 9903.01 or 9903.02, it is likely Section 301 (9903.88), Section 232 (9903.80/.81/.85), or Section 122 (9903.03.01 to 9903.03.11, which applied to goods entered February 24 through July 23, 2026 and has expired), and those are not refundable through CAPE. Section 122 has its own refund path through liquidation monitoring and 1514 protest where applicable.

Comparison: which rejection routes to which fix

Rejection pattern Route back to refund Deadline that controls Typical timeline
HTS relationship mismatch or invalid HTS (old sequence mismatch, FTZ Type 06) Resubmit on a new declaration; if a new error appears, PSC first (never one that changes the IEEPA line on an FTZ Type 06 entry), then resubmit PSC within 300 days of entry and 15 days before scheduled liquidation 60-90 days after CAPE acceptance
No IEEPA HTS line, IEEPA never paid Remove from declaration N/A N/A
No IEEPA HTS line, but IEEPA duty was paid Liquidated: 19 USC 1514 protest; unliquidated: ask CBP (a PSC cannot start an IEEPA refund) 180 days from liquidation Not set; CBP lists protested entries for a later CAPE phase
9903.01/.02 line shows $0 or FREE Remove from declaration N/A N/A
Outside Phase 1 scope (past 80 days liquidated) 19 USC 1514 protest 180 days from liquidation Not set; CBP lists protested entries for a later CAPE phase
Past 180 days liquidated, no protest Suit at the CIT under 28 USC 1581(i); CAPE Phase 3 once the court orders reliquidation Two years after the claim accrues (28 USC 2636(i)); start date not yet decided Depends on the case
Missing ACH refund details Add ACH Refund Authorization; no re-file needed None, but CBP holds the refund until then Refund released once details are on file
Account mismatch (IOR number) Remove those entries, re-upload the rest, file them from the right Importer sub-account Same as underlying entry Procedural
Filer code not matching IOR files direct, or the broker that filed the entries files Same as underlying entry Procedural
Entry already on prior CAPE or protest Drop the duplicate; withdraw an IEEPA-only protest within 80 days of liquidation, or let it run Same as underlying entry Depends on chosen route
Entry date outside Feb 4, 2025 to Feb 23, 2026 Remove from declaration N/A N/A

Bottom line: Every rejected CAPE entry maps to exactly one of these routes. The cost of getting the routing wrong is not a re-submission, it is a forfeited refund, because the protest clock and the CIT clock both keep running while you re-file a CAPE that ACE will reject again.

How GingerControl maps a rejected CAPE batch

GingerControl's IEEPA refund service starts from your ES-003 report and sorts every entry by refund route and deadline: re-file CAPE, PSC then CAPE, protest, court route, or out of scope. We prepare the refund file, closest deadline first, and our licensed refund partner files it. Your broker or counsel handles any Court of International Trade case. We are not a customs broker, do not file your entries and do not promise a refund amount.

The reason this matters as a separate workflow: a 9,999-entry CAPE declaration that comes back with 1,800 rejected lines is not one problem, it is between four and nine problems, each with its own deadline. The diagnosis work is more analytically dense than the original filing.

What to do this week if you have a rejected declaration

A pragmatic sequence:

  1. Pull the Validation Result File and the claim results from the CAPE tab in ACE, and the ES-003 report for the same period.
  2. Tag every rejected entry with one of the nine patterns above.
  3. Sort the rejected entries by liquidation date and flag every entry that is within 30 days of its 180-day protest deadline. Those become the highest priority because the protest route closes irrevocably.
  4. For entries needing PSC, get the PSC drafted and filed before the entry liquidates. PSC is no longer available post-liquidation.
  5. For entries rejected under the old HTS RELATIONSHIP/SEQUENCE MISMATCH message (often FTZ Type 06), resubmit them on a new declaration and fix whatever still fails with a PSC, unless that PSC would change the IEEPA line on an FTZ Type 06 entry, which ACE now rejects.
  6. Confirm ACH Refund Authorization is active on the IOR sub-account before refiling anything.
  7. Re-file CAPE on the entries that are genuinely back in scope after the fixes.

FAQ

Why was my CAPE declaration rejected even though my entries paid IEEPA duties? A rejection does not mean the duties were not paid, it means ACE cannot validate one of the CAPE-specific requirements on the entry: HTS relationships, a dutiable IEEPA Chapter 99 line, the 80-day liquidation window, the filer code or importer of record match, the entry type, or an open protest. GingerControl's IEEPA refund service sorts each entry by refund route and deadline, so you do not re-submit the same rejection.

Can I just resubmit a rejected CAPE declaration? Only if you have fixed the underlying error. Resubmitting the same file produces the same rejection. The exception is an entry rejected under the old HTS RELATIONSHIP/SEQUENCE MISMATCH message: CBP narrowed that check on June 25, 2026 and asks filers to resubmit those entries on a new declaration (CSMS #69056483); if one now returns HTS RELATIONSHIP MISMATCH or INVALID HTS, fix it with a PSC first (on an FTZ Type 06 entry, ACE rejects a PSC that changes the IEEPA line). Corrected entries always go on a new declaration, because an accepted one cannot be amended.

What is the difference between a file-level and an entry-level CAPE rejection? File-level rejections (format, header row, entry number format, filer code or importer of record mismatch) kill the entire declaration and require a full resubmission once corrected. Entry-level rejections only knock out the affected lines, and accepted entries continue processing. Read file errors from the Validation Result File and entry errors from the claim's results file, then route each rejected entry to a CAPE re-file, a PSC, a 1514 protest, or the court route based on its own liquidation date.

How do I fix a CAPE rejection where the entry is past the 80-day liquidation window? CAPE will not accept that entry. The fix is a protest under 19 USC 1514 filed within 180 days of liquidation, which keeps the liquidation from becoming final; CAPE does not take protested entries yet, and CBP lists them for a later phase. Past 180 days with no protest, the path is a suit in the Court of International Trade, and since October 6, 2026 CAPE Phase 3 takes finally liquidated entries of plaintiffs whose entries the court has ordered reliquidated. GingerControl's IEEPA refund service sorts each entry by route and deadline and prepares the refund file; our licensed refund partner files it.

Can a customs broker re-file my rejected CAPE declaration if they were not the original broker of record? Not directly through their filer code, because CAPE requires the first three characters of the entry number to match the submitting filer code, and CBP allows only the importer of record or the licensed broker that filed the entries to file. The workaround is for the IOR to file CAPE from its own ACE Importer account, where matching is on the IOR number rather than the filer code.

Is interest still accruing on entries that have been rejected by CAPE? Yes. Under 19 U.S.C. 1505, interest on an IEEPA refund runs from the date you deposited the duty to the date the entry liquidates or reliquidates with the refund, and CBP pays it inside the same refund, not separately (CBP). A rejection does not stop that clock, but the refund windows keep running too: an entry more than 80 days past liquidation leaves CAPE, and after 180 days without a protest the liquidation is final. CBP built CAPE to carry out the Court of International Trade's March 4, 2026 order in Atmus Filtration, which directed it to liquidate or reliquidate entries without the IEEPA duties (CSMS #68340863).

What happens if I have an entry on a CAPE declaration and a 1514 protest at the same time? ACE rejects the entry with PROTEST ON ENTRY. You pick one path: if the protest was filed only for the IEEPA refund and the entry is within 80 days of liquidation, CBP lets you withdraw the protest and put the entry on a CAPE declaration; otherwise leave the entry off CAPE and let the protest run. GingerControl's IEEPA refund service sorts every entry by route and deadline before anything is filed.

If your team is staring at a rejected CAPE declaration

Before re-filing, get an honest read on the size of the refund still recoverable across your rejected entries. The ES-003 calculator on our IEEPA refund service page reads your ACE export entirely in the browser (nothing uploads), sorts every line by its Chapter 99 number, sorts entries by route and protest deadline, and returns total IEEPA duties paid plus an estimated refundable amount. If you do not have your ES-003 yet, the free IEEPA refund estimator gives a first-pass number from the country you import from and a rough value.

If you submitted a CAPE declaration and got a Validation Result File with hundreds or thousands of rejected lines, the routing decision per entry is the bottleneck, not the resubmission itself. GingerControl's IEEPA refund service sorts each entry by route and deadline and prepares the refund file, closest deadline first; our licensed refund partner files it, and your broker or counsel handles any Court of International Trade case. Refund amounts and CBP acceptance are never guaranteed.

Map your rejected CAPE declaration

Talk to our team about sorting your rejected entries by refund route and deadline.

References

  1. U.S. Customs and Border Protection, ACE Portal CAPE Declarations and Error Definitions
    Data cited: File-level vs entry-level validation, error message taxonomy, Validation Result File mechanics
    Source: CBP CAPE Declarations and Error Definitions
    Published: June 2026 (Publication No. 5612-0626)
  2. U.S. Customs and Border Protection, CAPE Trade Information Notice (Pub. 1009-1119)
    Data cited: file and entry validation series, where to read file and claim results, refund bank account separate from the payment ACH account, PSC prohibition
    Source: CBP CAPE Trade Information Notice
    Published: April 2026, last updated July 10, 2026
  3. U.S. Customs and Border Protection, IEEPA Duty Refunds program page
    Data cited: CAPE channel inside ACE, refund consolidation by Importer of Record, ACH refund setup requirement, error message definitions, who may file, interest under 19 U.S.C. 1505
    Source: CBP IEEPA Duty Refunds
    Published: 2026, last modified September 30, 2026
  4. U.S. Customs and Border Protection, CSMS #68340863, UPDATE, CAPE for IEEPA Refunds, April 20, 2026, Deployment
    Data cited: March 4, 2026 Atmus Filtration order, PSC prohibition, withdrawing an IEEPA-only protest for entries within 80 days of liquidation
    Source: CSMS #68340863
    Published: April 13, 2026
  5. Troutman Pepper Locke, CBP Issues Guidance on IEEPA Duty Refunds via New CAPE Process
    Data cited: Filer code matching rule, IOR vs broker authorization, ACE account preconditions
    Source: Troutman CBP Guidance on IEEPA Duty Refunds via CAPE
    Published: April 2026
  6. EisnerAmper, IEEPA Tariff Refunds CAPE System Now Live
    Data cited: ACH Refund Authorization tab separate from ACH Debit, banking setup as gating issue
    Source: EisnerAmper IEEPA Tariff Refunds CAPE System Live
    Published: April 2026
  7. White and Williams, IEEPA Tariff Refunds CBP Launches CAPE Process
    Data cited: CSV upload mechanics, 9,999-entry-per-declaration limit, Chapter 99 line removal mechanics
    Source: White and Williams IEEPA Tariff Refunds CAPE Process
    Published: 2026
  8. 19 U.S.C. 1514, Protest provisions
    Data cited: 180-day protest deadline from liquidation
    Source: 19 USC 1514
  9. U.S. Customs and Border Protection, CSMS #69056483, Update to Entry-Level Validations for CAPE Declarations
    Data cited: HTS RELATIONSHIP/SEQUENCE MISMATCH split into HTS RELATIONSHIP MISMATCH and INVALID HTS, resubmission and PSC guidance
    Source: CSMS #69056483
    Published: June 25, 2026
  10. Declaration of Brandon Lord, CBP, Freestyle World, Inc. v. CBP, CIT No. 26-01088, ECF 58
    Data cited: main reasons declarations and entries fail validation, refunds held for missing ACH details, CAPE Phase 3 deployment on October 6, 2026
    Source: Lord declaration
    Published: October 6, 2026 (data as of October 2, 2026)
  11. U.S. Customs and Border Protection, CSMS #67834313, Ending Collection of IEEPA Duties
    Data cited: IEEPA duties no longer collected on goods entered on or after February 24, 2026
    Source: CSMS #67834313
    Published: February 22, 2026
  12. U.S. Customs and Border Protection, CSMS #70162211, ACE Portal: Addition of Verification Step for ACH Refund Changes
    Data cited: security token required to add or change ACH refund information from October 10, 2026
    Source: CSMS #70162211
    Published: October 9, 2026
  13. U.S. Customs and Border Protection, CSMS #69635410, Update to ACE CATAIR Error Dictionary: New Error F883 PSC NOT ALLOWED TO MODIFY IEEPA HTS
    Data cited: ACE rejects a PSC on an FTZ Type 06 entry that modifies the IEEPA HTS, deployed August 21, 2026
    Source: CSMS #69635410
    Published: August 24, 2026
  14. U.S. Court of International Trade, Freestyle World, Inc. v. CBP, No. 26-01088, ECF 61, Opinion and Order
    Data cited: class of importers of record who paid IEEPA duties between February 1, 2025 and February 19, 2026, excluding those that sued separately, certified October 8, 2026
    Source: Opinion and Order
    Published: October 8, 2026
Your next step

Racing a refund or protest deadline?

Hand this to GingerOS.

Get your refund claim sized and filed Check every deadline on one entry

Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.

Reviewed by Michael Weick, LCB / CCS
Customs compliance manager with 42 years of experience (ex Subaru of America, Merck, and Motorola).

More in Trade Basics

Our Risk-Free Promise

Full refund.

If you’re not satisfied before MVP acceptance, get a full refund of your deposit.

Click Me!

See if you qualify