FTZ Type 06 CAPE Rejection: Why & How to Fix It

Why are FTZ Type 06 entries getting rejected in CAPE Phase 1?

FTZ Type 06 entries are being rejected in CAPE Phase 1 because the 9903.01 and 9903.02 IEEPA Chapter 99 lines on the original entry summary are not sequenced correctly against the underlying Chapter 1-97 base HTS line. The CAPE validator reads the entry summary line-by-line and rejects any FTZ Type 06 CAPE declaration where the HTS relationship between the base classification and the IEEPA Chapter 99 line cannot be reconciled.

How do I fix an FTZ Type 06 CAPE rejection for HTS sequence mismatch?

You fix an FTZ Type 06 CAPE rejection by pulling the original entry summary, re-sequencing the HTS lines so the IEEPA Chapter 99 codes follow the base HTS line in CBP's required order, and refiling the CAPE declaration. If the entry has already liquidated and is past the 80-day CAPE Phase 1 window, the path shifts to a 1514 protest or, past 180 days, to a CIT complaint.

TL;DR

If you used FTZ Type 06 entries to consume goods out of a foreign trade zone during the February 2025 to February 2026 IEEPA window, your CAPE Phase 1 declarations are probably getting rejected with HTS relationship or sequence mismatch errors. The fix is mechanical: re-sequence the IEEPA Chapter 99 lines against the base HTS line in the order CBP's CAPE validator expects, then refile. GingerControl built this guide because FTZ Type 06 rejections are now the single most common CAPE Phase 1 error we are seeing, and the 80-day window does not pause while you troubleshoot.

Last updated: May 2026

---

What an FTZ Type 06 entry actually is

A Foreign Trade Zone Type 06 entry is the Consumption Entry filed when goods are withdrawn from an FTZ into U.S. commerce. It is the moment duty becomes payable on FTZ inventory, and it is the entry type that carries the Chapter 99 trade remedy lines, including the IEEPA codes that are now refundable.

The key contrast for refund purposes:

Entry type	What it covers	When duty is paid	IEEPA exposure
Type 01	Standard consumption entry, goods cleared directly from port	At entry	Direct, single HTS sequence
Type 06	FTZ withdrawal for consumption	At withdrawal from zone	Direct, but layered against FTZ admission status
Type 03	Antidumping/countervailing duty entry	At entry	Possible, depends on entry
Type 11	Informal entry	At entry	Limited

The crucial point: under 19 CFR Part 146, goods admitted to an FTZ are not entered for consumption at the time of admission. They sit in the zone under either Privileged Foreign (PF) or Non-Privileged Foreign (NPF) status. The Type 06 entry, typically filed as a Weekly Entry under 19 CFR 146.63, is when the IEEPA Chapter 99 codes attached, and is therefore the entry that needs CAPE treatment now.

Why IEEPA hit Type 06 entries the way it did

The IEEPA tariffs imposed from February 4, 2025 through early February 2026 applied via Chapter 99 codes 9903.01 and 9903.02. For FTZ goods, the timing rule is what makes Type 06 entries vulnerable.

Goods admitted to an FTZ in Privileged Foreign (PF) status lock in their HTS classification and duty rate at admission, but the trade remedy duty rate is generally the rate in effect at withdrawal. Goods admitted in Non-Privileged Foreign (NPF) status are classified and dutied at withdrawal in their condition at that time. In both cases, withdrawals during the IEEPA window picked up the 9903.01 or 9903.02 line on the Type 06 entry summary.

That is why FTZ operators who thought they were insulated by zone status still ended up paying IEEPA duties on Type 06 withdrawals. And that is why those same entries are now eligible for refund through CAPE, if the declaration can pass validation.

GingerControl is AI global trade compliance infrastructure that helps importers, exporters, and customs brokers classify products, engineer optimal tariff positions, calculate duties, and track policy changes. For the IEEPA refund work specifically, we focus on the entry-by-entry quantification and the pre-CAPE audit that determines whether a declaration will validate or reject.

What "HTS relationship or sequence mismatch" actually means

CAPE Phase 1 validates each entry summary line as a structured record. The validator checks three things for FTZ Type 06 entries:

1. The base HTS line (Chapters 1-97) is present and properly classified
2. The IEEPA Chapter 99 line (9903.01 or 9903.02) is present, sequenced correctly relative to the base line, and references the right tariff treatment
3. The FTZ admission status on the original entry summary aligns with the duty calculation that produced the IEEPA charge

When any one of those three checks fails, the CAPE declaration rejects with an HTS relationship or HTS sequence mismatch error. The most common triggers I am seeing:

• Sequence flip: The 9903 line was placed before the base Chapter 1-97 line on the original entry summary. CAPE expects base-first, Chapter-99-follows.
• Missing relationship link: The Chapter 99 line was filed as a standalone line item rather than as a related line to the base HTS. CAPE cannot tell which base line to strip the IEEPA charge from.
• PF vs NPF mismatch: The original entry summary recorded the FTZ admission status one way (for example PF), but the duty calculation reflects the other (for example duty rate at withdrawal, suggesting NPF). CAPE cannot reconcile.
• Wrong Chapter 99 code: The entry used 9903.02 when the goods and date should have triggered 9903.01, or vice versa. CAPE expects the code to match the entry date and origin.

This is mechanical. The original entry summary almost always has all the data CAPE needs, it is just not arranged the way the CAPE validator expects.

How to diagnose the rejection from the ACE response

When CAPE rejects, the ACE response includes an error code and a line reference. The diagnostic workflow:

1. Pull the original entry summary (CBP Form 7501) and the FTZ Weekly Entry summary. Confirm the actual sequence of HTS lines as filed.
2. Match the rejection line reference to the entry line. ACE returns the entry summary line number that failed validation.
3. Read the error code. Common codes for FTZ Type 06 rejections fall into the HTS validation family. CBP publishes the CAPE filer guidance with the active error list. Cross-reference your code there.
4. Check the FTZ admission documentation (e214). The CBP Form e214 is the admission record into the zone, and it shows the PF or NPF status. If the entry summary status does not match the e214, you have a documentation reconciliation issue, not just a sequence issue.
5. Confirm the IEEPA Chapter 99 code matches the entry date. 9903.01 and 9903.02 covered different windows during the IEEPA period. The wrong code at the wrong date will reject regardless of sequence.

If the rejection is purely sequence, the fix is a refile with the lines in the correct order. If it touches PF/NPF status or documentation reconciliation, the fix involves your FTZ Operator and possibly the Grantee.

Fix paths by entry status

Situation	Path	Timeline	Effort
Type 06 entry unliquidated, CAPE rejected for sequence only	Re-sequence HTS lines, refile CAPE	60-90 days post acceptance	Low
Type 06 entry unliquidated, CAPE rejected for PF/NPF mismatch	Reconcile e214 with entry summary, refile	60-90 days post reconciliation	Medium, FTZ Operator engagement
Type 06 entry liquidated within 80 days, CAPE rejected	Refile CAPE Phase 1 with corrections	60-90 days post acceptance	Low to medium
Type 06 entry liquidated past 80 days, within 180 days	File protest under 19 USC 1514	6-18 months for CBP decision	Medium
Type 06 entry liquidated past 180 days	CIT complaint	12-24+ months	High

Bottom line: Most FTZ Type 06 CAPE rejections are mechanical sequence problems that can be fixed by refiling. Documentation reconciliation issues take longer because they require pulling the e214 admission record and aligning it with the entry summary, and that work routes through your FTZ Operator.

What documentation you need to assemble

For a clean refile on an FTZ Type 06 CAPE rejection, you need five documents per entry:

1. CBP Form e214 admission record. Confirms PF or NPF status at admission and the HTS classification locked in (for PF status).
2. FTZ Weekly Entry estimate. Filed by the operator under 19 CFR 146.63, this is the underlying entry record for the consumption withdrawals during the week.
3. Type 06 entry summary (CBP Form 7501). The line-by-line record CAPE validates against.
4. Commercial invoice and packing list. For the consumed merchandise, confirming value and quantity used in the IEEPA duty calculation.
5. The CAPE rejection response from ACE. Includes the error code and line reference that point you at the specific validation failure.

The NAFTZ FTZ Operator Manual is the practitioner reference for the operator-side workflow. The CBP FTZ Manual is the regulatory reference.

GingerControl's Tariff Calculator covers the full U.S. tariff stack: base duty, Section 232, Section 301, Chapter 99, and Section 122 reciprocal tariffs across 200+ countries. For the FTZ Type 06 refund workflow specifically, the Calculator is what we use to re-derive the correct IEEPA duty for each Weekly Entry line and verify whether the original entry's IEEPA charge matches what CAPE will accept on refile.

What Phase 2 may resolve automatically, and what it probably will not

Phase 1 of CAPE was deliberately scoped narrow: clean unliquidated entries and recently liquidated entries with straightforward HTS structures. CBP has signaled subsequent phases will expand to more complex entry types. As Thompson Hine has noted in their April 2026 alert, the phased rollout is intended to absorb operational complexity gradually.

It is reasonable to expect Phase 2 to handle some FTZ-specific validation differently, possibly relaxing the strict sequence check or adding a parallel validator that understands FTZ admission status. That said, two things are unlikely to change:

• The underlying entry summary still has to be internally consistent. A PF/NPF documentation mismatch on the original entry is a real reconciliation problem that no validator change will fix.
• The 80-day and 180-day windows are statutory. Waiting for Phase 2 on entries that liquidated in early 2026 is a clock-management problem, not a Phase 2 problem.

The right working assumption: refile what you can now, escalate the entries that need FTZ Operator reconciliation, and protect the protest clock on anything that has liquidated.

A quotable framing on FTZ Type 06 CAPE rejections

Most CAPE Phase 1 rejections on FTZ Type 06 entries are not substantive disputes about whether the IEEPA refund is owed. They are line-ordering problems on the original entry summary, where the IEEPA Chapter 99 code is present but not sequenced in the relationship structure the CAPE validator expects. The fix is a re-sequenced refile, not a legal escalation, as long as the underlying entry data and FTZ admission record reconcile.

How GingerControl fits in

For importers and FTZ operators working through FTZ Type 06 CAPE rejections, the work splits into three pieces:

• Quantification. Per Weekly Entry and per Type 06 withdrawal, calculate the IEEPA-only duty exposure that CAPE should remove. The Tariff Calculator handles this across the full tariff stack so the IEEPA component is isolated cleanly.
• Pre-refile audit. Compare the original entry summary line structure to the CAPE validator's expected structure, flag sequence and relationship mismatches before refiling, and confirm the e214 admission status reconciles. This is where we save importers the second rejection.
• Protest and CIT routing. For entries past the 80-day window, route to protest documentation under 19 USC 1514 or, past 180 days, to CIT complaint preparation. GingerControl supports the documentation work; the protest or complaint filing is done by your licensed customs broker or trade lawyer.

GingerControl does not file CAPE declarations on behalf of importers. That work goes through your customs broker or filer with ACE Portal access. What we do is quantify the refund per entry and audit the entry data so the CAPE declaration validates the first time.

FAQ

What does HTS sequence mismatch mean on a CAPE rejection? It means the IEEPA Chapter 99 line (9903.01 or 9903.02) on the original entry summary is not sequenced correctly relative to the base Chapter 1-97 HTS line, so the CAPE validator cannot match the IEEPA charge to a base classification line for removal. GingerControl's pre-refile audit flags this sequence problem before submission so the refile validates the first time.

Why are FTZ Type 06 entries getting rejected more often than Type 01 entries? Because Type 06 entries layer the IEEPA Chapter 99 line on top of an FTZ admission status (PF or NPF) that adds a second reconciliation point CAPE has to validate. Type 01 entries have a single classification path. GingerControl's Tariff Calculator handles both, but for Type 06 entries we specifically check the e214 admission record against the entry summary before refile.

Can I refile a CAPE declaration after a rejection? Yes. Once you correct the line sequence or the underlying data issue, you refile through the same ACE Portal CAPE channel. There is no per-declaration limit on refiles, only the 9,999-entry-per-declaration size limit. GingerControl's pre-refile audit is the step that prevents a third rejection.

What if my FTZ Type 06 entry already liquidated past the 80-day CAPE window? The path moves to a protest under 19 U.S.C. 1514 if the entry is within 180 days of liquidation, and to a CIT complaint if past 180 days. GingerControl supports the entry-by-entry quantification that the protest or complaint needs; the filing is done by your customs broker or trade lawyer.

Does Privileged Foreign status affect the IEEPA refund eligibility? PF status locks the HTS classification and base duty rate at admission, but the IEEPA Chapter 99 duty was generally applied at withdrawal regardless of PF or NPF status. So the IEEPA refund eligibility is the same in both cases. GingerControl's pre-refile audit verifies the PF or NPF status on the entry summary matches the e214 admission record.

How does GingerControl help with FTZ Type 06 CAPE rejections? GingerControl quantifies the IEEPA refund per Weekly Entry and per Type 06 withdrawal, audits the entry summary against the CAPE validator's expected line structure, and flags PF/NPF documentation reconciliation issues before refile. We do not file CAPE declarations; that goes through your customs broker with ACE Portal access.

Will CBP audit FTZ Type 06 refund claims more aggressively than Type 01 claims? CBP has signaled it may audit IEEPA refund claims generally, and FTZ entries have an extra documentation layer (e214 and Weekly Entry) that gives auditors more to review. The defense is clean reconciliation between the e214, the Weekly Entry, and the Type 06 entry summary. GingerControl's audit work produces the documentation that supports that defense.

What is the most common single fix for an FTZ Type 06 CAPE rejection? Re-sequencing the 9903.01 or 9903.02 line to follow the base Chapter 1-97 line in the order CAPE expects, then refiling. Most rejections we see are mechanical sequence errors, not substantive eligibility problems. GingerControl's pre-refile audit catches the sequence issue before the CAPE declaration is submitted.

If your FTZ Type 06 entries are rejecting in CAPE

If you are not sure how much of your FTZ Type 06 exposure is still recoverable, size it first. The IEEPA refund toolkit on this page has two free calculators that size the opportunity in minutes. The ES-003 drop-in calculator parses your ACE export entirely in the browser (nothing uploads), classifies every line by Chapter 99 prefix, buckets entries by liquidation status, and returns total IEEPA duties paid plus estimated recoverable amount. The quiz-style estimator is the faster path if you do not have your ES-003 yet, a handful of questions and you get a directional estimate.

If your team is watching FTZ Type 06 CAPE declarations come back with HTS relationship or sequence mismatch errors, GingerControl re-sequences the HTS lines on the underlying entry summaries, audits the e214 admission status against the entry record, and prepares the refile so it validates the first time. For entries past the 80-day window, we route to protest or CIT complaint documentation.

Talk to our team about FTZ Type 06 CAPE rejections and IEEPA refunds

Related reading

• The Importer's IEEPA Tariff Refund Guide
• How to Submit a CAPE Declaration for IEEPA Refunds
• Duty Drawback vs Foreign Trade Zone
• CAPE-Eligible Entries for IEEPA Refunds
• Pulling the ES-003 Report for IEEPA Refunds
• How to File a Customs Protest Under 19 USC 1514
• Court of International Trade Tariff Refund Path

References

[REF 1] U.S. Customs and Border Protection, IEEPA Duty Refunds and CAPE Filer Guidance Data cited: CAPE Phase 1 launch April 20, 2026; validation error structure; ACE Portal channel Source: CBP IEEPA Duty Refunds Published: 2026

[REF 2] 19 CFR Part 146, Foreign Trade Zones Data cited: FTZ admission, Privileged Foreign and Non-Privileged Foreign status, Weekly Entry under 19 CFR 146.63 Source: 19 CFR Part 146 Published: current

[REF 3] CBP Foreign Trade Zones Manual Data cited: e214 admission record, Type 06 Consumption Entry, operator and grantee responsibilities Source: CBP FTZ Manual Published: current edition

[REF 4] National Association of Foreign Trade Zones (NAFTZ) Data cited: Operator-side workflow practices for Weekly Entry and Type 06 filing Source: NAFTZ Published: current

[REF 5] Thompson Hine SmartTrade analysis Data cited: April 20, 2026 CAPE Phase 1 launch and phased rollout scope Source: CBP Confirms April 20 2026 Launch of CAPE Phase 1 Published: April 2026

[REF 6] BDO IEEPA Tariff Refunds FAQ Data cited: CBP audit risk on IEEPA refund claims, documentation expectations Source: BDO IEEPA Tariff Refunds FAQ Published: 2026

[REF 7] 19 U.S.C. 1514 protest provisions Data cited: 180-day protest deadline from liquidation Source: 19 USC 1514 Published: current

[REF 8] Foreign-Trade Zones Board (ftz.gov) Data cited: FTZ Board oversight, grantee structure Source: Foreign-Trade Zones Board Published: current