CAPE CSV format errors, fixed

The six errors we keep seeing from small-business importers, and the shortest fix for each.

1. 1. "Entry number must be 11 alphanumeric characters"

   CBP's validator expects exactly 11 alphanumeric characters per entry. A common cause is Excel chopping a leading zero when it thinks the value is a number — for example turning 0123456789A into 123456789A (10 chars).

   Fix: format the column as Text before pasting in Excel, or skip Excel entirely and paste numbers into this tool directly — it treats everything as text and preserves leading zeros.

2. 2. "Duplicate entry number"

   CAPE rejects the whole CSV if any entry number appears twice, including across different filers. The most common cause: a broker list that re-lists amended entries, or two brokers both giving you the same entry.

   Fix: paste everything into this tool — duplicates are automatically removed from the export, and you'll see exactly which rows were duplicates before the export.

3. 3. "Duplicate tax ID" error on submit

   This is a portal-side error, not a CSV error. It means CBP already has an ACE account tied to your EIN, usually because a broker set one up in your name years ago.

   Fix: call the CBP Client Representative desk for ACE accounts or reach out via the ACE help form. You'll likely need to get your broker to release the tie or consolidate.

4. 4. "File format not accepted"

   CAPE wants a plain CSV — UTF-8 is safest — with the first row being the literal header Entry Number. Some rejections trace back to Excel saving as CSV UTF-8 (with BOM) or Macintosh CSV.

   Fix: download your CSV from this tool. We write plain UTF-8 CSV with a single Entry Number column and a trailing newline, which is what the validator expects.

5. 5. "Exceeds maximum of 9,999 entries"

   CBP caps one CAPE Declaration CSV at 9,999 entries. Big importers hit this constantly.

   Fix: this tool auto-splits anything over that limit into part 1, part 2, etc. Upload them as separate CAPE Declarations.

6. 6. "System is currently experiencing high volume"

   Not a CSV problem — a portal load problem. Widely reported in the first days after launch.

   Fix: try early morning (before 7am ET) or late evening. Keep your CSV ready so you can submit the moment the portal responds.