Exporting your ACE Entry Summary for CAPE

Why this matters

A CAPE filing is only as good as the entry data behind it. If your ACE export is missing the liquidation date on half the rows, the classifier can't tell which entries are still on the right side of the 80-day cliff, and those entries silently drop out of the filing. Getting the export right once — with every column the classifier needs — is what separates a two-hour filing from a two-week scramble.

CBP's IEEPA Duty Refunds program page has the canonical list of what CAPE expects. This guide translates that into specific ACE Portal clicks.

Step by step

1. Sign in to the ACE Portal. Navigate to the ACE Secure Data Portal. Use the account linked to your IOR. Brokers signing in on behalf of an importer need delegated access to that IOR.
2. Open Reports → Entry Summary. In the top navigation, select Reports, then Entry Summary. The default view lists entries for the last 12 months; you will widen this shortly.
3. Set the date range to the IEEPA window. Filter for entry filing date between Feb 1, 2025 and Feb 7, 2026. This bounds the universe to the IEEPA window. Entries outside the window are not CAPE-eligible.
4. Include the liquidation status and date. In the column picker, add the Liquidation Date and Liquidation Status columns. These drive the 80-day cliff computation. Without them the classifier cannot determine eligibility.
5. Include the paid duty breakdown. Add the Paid Duty Breakdown columns (IEEPA, Section 232, Section 301, MPF, HMF). The classifier needs these to separate IEEPA principal from stacked Section 232/301 duty that stays with CBP.
6. Export to CSV. Click Export → CSV. ACE produces a UTF-8 CSV with a header row, one line per entry. Save it locally and verify the file has the expected columns before proceeding.

The column list

Minimum columns the classifier needs:

• Entry Number (14 digits)
• Entry Filing Date
• Liquidation Date
• Liquidation Status (Liquidated / Unliquidated)
• HTS Subheading (per line)
• Paid Duty — IEEPA portion
• Paid Duty — Section 232 portion (if any)
• Paid Duty — Section 301 portion (if any)
• Country of Origin (for USMCA exclusion screening)
• IOR Number
• Filer Code

Missing any of the first five columns materially degrades the classifier's output. Missing any of the paid-duty columns degrades principal accuracy but not eligibility.

Troubleshooting

Export rows don't match my records

Compare row count to ACE's filter totals. A mismatch usually means you hit the 50,000-row cap and the export truncated. Split the window into quarters and concatenate.

CSV encoding looks wrong when I open it

ACE produces UTF-8. Some spreadsheet tools open CSVs as Windows-1252 by default and mangle accented characters (common in country-of-origin fields). Either import explicitly as UTF-8 or use a tool that respects the BOM.

My broker did the filing — can I still export?

Yes — the importer of record always has ACE read access to their own entries. If your ACE account does not show them, your account may not be linked to your IOR. Ask the broker for the IOR-CBP registration letter and contact ACE support to bind the IOR to your account.

Privacy

un-tariff processes ACE exports entirely on the server side. No entry data is logged to third parties or shared outside the classification pipeline. See the privacy policy and the DPA for the specifics.

Common questions