What is the Octo CAPE-Filing Sequence?
The Sequence is the ordered checklist Octo treats as the difference between a clean acceptance and an indefinite stall. Five steps. Skip one and the refund either rejects, blocks, or sits unprocessed.
| # | Step | What it tests | Where you do it |
|---|---|---|---|
| 1 | Confirm 9903.01.xx / 9903.02.xx HTS codes | Only IEEPA-coded entries are eligible. Section 301 codes are not. | ACE entry-summary line review |
| 2 | Pull ES-003 with Liquidation columns | Verifies the entry is in scope and shows current Liquidation Status / Date | ACE Portal → ES-003 Entry Summary Line Tariff Details |
| 3 | Confirm ACH is set up in ACE | If ACH is missing, CBP issues the refund and it bounces back rejected | ACE Account Management → ACH banking |
| 4 | Submit CAPE Declaration | The refund request itself; once accepted, the entry's correction window closes | CAPE portal inside ACE |
| 5 | Re-pull ES-003 within 5 days | Confirms the 9903 lines are removed (the acceptance signal) and the entry is queued for refund | ACE Portal → ES-003 |
CBP's published timing estimate is 60–90 days. Reddit filers report faster anecdotal clears in the rollout window. Octo treats the gap between the two as a function of whether the Sequence cleared on the first submission, not on the third.
Why does this matter right now?
Per CBP's IEEPA Duty Refunds program page, CAPE — the Consolidated Administration and Processing of Entries functionality inside the Automated Commercial Environment (ACE) — launched its first phase on April 20, 2026 to process refund requests for IEEPA tariffs paid between February 2025 and February 2026. Importers who paid those duties have a finite window to file. After CBP accepts a CAPE Declaration, the correction window for that entry closes — meaning errors detected after submission cannot be amended.
The Reddit pattern that triggered this guide came from r/FulfillmentByAmazon: filers who pulled the wrong ACE report saw zero confirmation of their filing for weeks. Reddit filers in the anchor thread describe TR-011 as having stopped returning useful IEEPA-line data in February 2026 — treat that as a seller-reported caution, not an officially confirmed deprecation, and verify with your broker before relying on TR-011. The fix Reddit filers converge on: pull ES-003, not TR-011.
Step 1 — Confirm 9903.01.xx and 9903.02.xx codes only
Per CBP's IEEPA Duty Refunds page, only entries flagged with HTS Chapter 99 IEEPA codes — 9903.01.xx and 9903.02.xx — qualify for CAPE refunds. Section 301 tariffs on Chinese goods are not included. This is the most common eligibility error in seller reports: importers see "additional tariffs paid on Chinese imports" on their ledger and assume the whole amount is in scope. Per CBP's own guidance, it is not. Section 301 has its own refund track and does not flow through CAPE.
If your entry-summary lines show 9903.81.xx (Section 301), 9903.88.xx, or any code that is not 9903.01.xx or 9903.02.xx, it is not eligible for CAPE. Pull the ES-003 first to confirm the codes before you submit anything.
Step 2 — Pull ES-003, not TR-011
The right report is the ES-003 Entry Summary Line Tariff Details report inside ACE. Per the Liberty Justice Center walk-through, ES-003 shows entry-summary line details including the Chapter 99 IEEPA HTS codes that should be removed once CBP accepts and processes the CAPE Declaration. That removal is the acceptance signal.
Two configuration details that catch first-time filers, per Reddit threads in this Pulse sample:
- Liquidation Status and Liquidation Date columns are not in the default ES-003 export. Add them in the report builder before you run.
- Reddit filers report that TR-011 stopped returning useful IEEPA-line data in February 2026. If you pull TR-011 and see no rows, treat that as ambiguous — confirm with your broker whether TR-011 is reliable for your workflow before assuming "no entries to refund."
Step 3 — Confirm ACH is set up in ACE
This is the silent killer in Reddit reports. If ACH banking details are not configured inside ACE before CBP processes the refund, the refund issues and bounces back rejected. The importer does eventually get the money, but only after CBP re-issues — adding weeks to what should be a faster clear.
Check ACE Account Management before you file the CAPE Declaration. Reddit filers describe the ACH setup itself as taking 3–5 business days inside CBP's onboarding workflow, so build that lead time into your timeline.
Step 4 — Submit the CAPE Declaration
The CAPE Declaration is the actual refund request, filed inside the ACE portal. Per CBP's refund instructions, once the Declaration is accepted, the entry's correction window closes and certain errors cannot be amended after the fact. The legal commentary from Norton Rose Fulbright on CBP's CAPE process reinforces the same warning: review every line of the entry and the requested refund amount before submission.
The first fraud window for tariff refunds is not at the deposit. It is at the filing — because the correction window closes on submission.
Step 5 — Re-pull ES-003 within 5 days
After submission, re-pull ES-003 within 5 days. The 9903 lines should be removed from the entry-summary detail. If they are still there, the CAPE Declaration has not yet been processed. If they are gone, the entry is in the refund queue and ACH should clear within the 60–90 day CBP estimate. First-filer Reddit reports describe faster anecdotal clears in the rollout window, but plan against the 60–90 day published estimate, not the anecdote.
What 4 patterns kill a CAPE filing?
- Section 301 entries submitted as IEEPA. Per CBP, codes 9903.81.xx and 9903.88.xx will reject. Only 9903.01.xx / 9903.02.xx are in scope for CAPE.
- TR-011 used instead of ES-003. Reddit filers report TR-011 has stopped returning useful IEEPA-line data in February 2026. Treat as unreliable; pull ES-003 with Liquidation columns enabled and confirm with your broker.
- ACH not configured in ACE. Per Reddit reports, refund issues and rejects on bank-routing failure, requiring CBP re-issue. Adds weeks.
- Filing before the entry is fully reviewed. Per CBP, once CAPE accepts, the correction window closes. Errors cannot be amended.
The 15-day clears reported by early Reddit filers appear to come from filings that passed all five Sequence steps on first submission. CBP's official refund-timing estimate remains 60–90 days after acceptance — Octo treats the 15-day reports as best-case rollout anecdotes, not as the typical timeline.
How does CAPE compare to a customs broker handling the refund?
| Approach | Cost | Time | Best for |
|---|---|---|---|
| DIY in ACE | $0 in fees + your time | 60–90 days per CBP estimate | Importers with ACE accounts, ACH set up, and patience for the report-pull workflow |
| Customs broker | Typically a flat fee or % of refund | 60–90 days | Importers with multiple entries or no ACE access; broker takes liability for filing accuracy |
| Trade-law firm | Hourly rate + retainer | 30–90 days | Edge cases — entries straddling 9903 codes, contested liquidations, audit risk |
| Octo Periscope | Continuous monitoring fee | Surfaces deadline + code change | Importers who need a regulatory pipeline that flags eligibility shifts before they expire |
Periscope is not a customs broker. It is the monitoring layer Octo treats as the early-warning system for the next CAPE-equivalent program — which matters because IEEPA refund timelines are time-bounded and the next refund track for Section 301 has not yet opened a CAPE-style portal.
How does Octo Periscope monitor CBP for clients?
Octo Periscope tracks CBP's IEEPA Duty Refunds page, the Federal Register for new tariff rulings, and customs-broker industry publications for filing-window changes. The monitoring rate is configurable: daily for active windows like CAPE, weekly for broader trade-remedy signals.
CAPE filing windows don't reopen. Neither will Section 301's. Octo Periscope monitors CBP, USTR, and trade-remedy publications — and surfaces the eligibility, deadline, and form codes for your category before the window closes. See how Periscope flags regulatory windows →