Common CAPE Filing Mistakes That Delay Your IEEPA Tariff Refund

The CAPE portal is unforgiving of format errors — a malformed CSV gets rejected, not corrected, and the 60-to-90-day processing clock doesn’t start until a clean submission is accepted. Here are the most common mistakes to avoid before you file.

1. CSV Header Row Doesn’t Match CBP’s Exact Template

The CAPE portal validates the header row of your CSV against CBP’s published column names. Even minor variations — an extra space, different capitalization, an abbreviated column name — will cause an immediate format rejection.

Fix: Download CBP’s official CAPE CSV template from the CBP CAPE documentation page and use it as your starting point. Do not create your own header row from memory.

2. Including Section 301 Duty Amounts in the IEEPA Duty Field

Section 301 tariffs (9903.88.xx codes) and IEEPA tariffs (9903.01.xx codes) are separate. The IEEPA duty amount field in the CAPE CSV must contain only the duty amount attributable to the IEEPA code — not the total duty amount.

Example of the mistake: An entry paid $5,000 in Section 301 duties and $8,500 in IEEPA duties ($13,500 total). Listing $13,500 in the IEEPA duty field overstates the claim and will be caught during CBP’s recalculation step, resulting in partial rejection or delay.

Fix: Separate your IEEPA duty amounts by code. Your customs broker can help identify which amounts correspond to which Chapter 99 code.

3. Trailing Whitespace and Encoding Issues in CSV

Many importers prepare their CAPE CSV in Excel. Excel sometimes adds trailing whitespace characters at the end of field values or saves files with a BOM (byte order mark) character at the beginning. CBP’s validation system rejects files with these formatting artifacts.

Fix: After preparing your CSV in Excel, save it as “CSV UTF-8 (Comma delimited)” — not “CSV (MS-DOS)” or “CSV (Macintosh).” Then open the file in a plain text editor (Notepad on Windows, TextEdit in plain text mode on Mac) to verify there are no invisible characters before the first row or after the last row.

4. No ACH Banking Profile (or Unverified ACH)

Submitting a CAPE claim without a verified ACH banking profile in your ACE account does not result in rejection — it results in something worse: your approved refund sits in a disbursement queue until ACH is resolved. Meanwhile, interest calculation continues, but you’re not receiving funds.

Fix: Verify your ACH profile is confirmed in ACE before submitting your CAPE declaration. Allow 3-5 business days for CBP to validate new ACH profiles after they’re added.

5. Duplicate Entry Lines Across Multiple Declarations

If you’re splitting a large filing across multiple CAPE declarations (due to the 9,999-line limit), ensure there is no overlap between declarations. Duplicate entry lines across declarations create a processing error during CBP’s recalculation step.

Fix: Use a spreadsheet to track which entry lines have been included in which declaration. Sort by entry number before splitting, and verify there are no duplicates using a “Count if” or deduplication function before preparing each CSV.

6. Wrong Entry Number Format

CBP entry numbers have a specific format: a 3-digit filer code, a 7-digit sequence number, and a 1-digit check digit (e.g., 123-4567890-0). The CAPE CSV requires this format exactly. Omitting the dashes, adding extra characters, or transposing digits will cause line-level rejection.

Fix: Copy entry numbers directly from your CBP Form 7501 or ACE entry records rather than typing them manually.

7. Filing for Entries Where You Were Not the IOR

The CAPE system cross-references each entry line against CBP’s records. If the IOR number in your ACE account doesn’t match the IOR on the entry, the line will be rejected during recalculation.

Fix: Before filing, confirm that the IOR number in your ACE account matches Box 26 of Form 7501 for every entry line you’re claiming. Lines filed under the wrong IOR will be rejected at the recalculation stage — after you’ve waited 4-8 weeks for CBP to get to your claim.

8. Including Liquidated Entries Outside Phase 1’s Window

Phase 1 covers unliquidated entries and entries liquidated within the past 80 days. Including entries liquidated more than 80 days ago in your CAPE Phase 1 declaration will cause those lines to be rejected during review.

Fix: Pull the liquidation date (not the entry date) for each entry from your ACE records. Exclude any entry where the liquidation date is more than 80 days before your planned filing date. Set those aside for Phase 2.

9. Mixing Eligible and Ineligible Tariff Codes

CAPE accepts only IEEPA codes (9903.01.xx). Do not include lines with Section 232 steel/aluminum codes (9903.80.xx) or Section 301 codes (9903.88.xx). Including ineligible codes generates a line-level rejection that can create delays for the eligible lines in the same declaration.

Fix: Filter your entry data to include only lines with 9903.01.xx Chapter 99 codes before preparing your CAPE CSV.

10. Not Saving Your Confirmation Number

After submitting your CAPE declaration, the portal generates a confirmation number. This is your primary reference for tracking your claim’s status and for any correspondence with CBP about your filing.

Fix: Screenshot and save the confirmation number immediately after submission. Store it in a place your entire team can access (not just one person’s email).

Related Resources

• CAPE Portal Explained — Full filing walkthrough
• ACE Portal Setup for CAPE — Pre-filing configuration
• DIY vs. Expert Help — When to get professional help to avoid these mistakes
• Check Your Eligibility