CBP Expands IEEPA Tariff Processing in October: Build an Entry-Level Readiness Check

The next phase of IEEPA tariff refunds is not simply a finance event. It is an entry-data test.

U.S. Customs and Border Protection plans to expand its Consolidated Administration and Processing of Entries portal, or CAPE, on October 6. The new phase will allow eligible importers to seek refunds for certain finally liquidated entries that carried tariffs later invalidated by the Supreme Court. According to Supply Chain Dive, the initial process applies to businesses that submitted a valid importer-of-record number to CBP by the end of July. Entries submitted after July 30 will require additional instructions.

The scale explains why a static tariff memo will not be enough. Reuters reported that more than $175 billion in U.S. tariff collections could be subject to refunds, based on a Penn Wharton Budget Model estimate. Every potential recovery still depends on the underlying entry record, its legal status, and the evidence connecting a shipment to the duty paid.

Start with an entry-level eligibility record

Importers should resist managing the refund effort through a list of purchase orders or a single total from the general ledger. CBP works at the customs-entry level. The operational record therefore needs to connect each entry number to the importer of record, entry date, liquidation status, affected tariff line, amount deposited, broker filing, and supporting commercial documents.

Build a readiness table with one row per entry and, at minimum, these fields:

• Entry number, entry type, port, importer of record, and broker
• Entry and liquidation dates, including whether liquidation is final
• HTS classification and tariff treatment used at filing
• Country of origin and the evidence supporting that determination
• Customs value, duty base, IEEPA duty paid, and expected refund
• CAPE eligibility status and the date the importer number was submitted
• Protest, litigation, reliquidation, or other case references
• Document completeness, owner, next action, and due date

That structure separates entries ready for processing from entries needing legal, broker, or data review. It also prevents a portfolio-level refund estimate from being mistaken for cash that is already recoverable.

Recheck the five facts that drive treatment

A clean entry number is not proof of a clean entry. Before an entry moves into a refund workflow, compliance teams should validate five facts: classification, origin, value, effective date, and duty treatment.

First, compare the HTS code in the broker filing with the product master and the classification rationale in effect on the entry date. Second, confirm that country of origin is supported by supplier declarations, production records, or other applicable evidence—not inferred from the ship-from location. Third, reconcile customs value to the commercial invoice and identify assists, royalties, related-party adjustments, freight exclusions, or later value corrections.

Fourth, apply the tariff rule and court or agency instruction that was effective for that entry and liquidation date. Fifth, recalculate the expected duty treatment at the line level. A shipment may contain both affected and unaffected merchandise, so an entry-wide percentage can create false refund expectations.

This check should preserve both the original decision and the revised one. Overwriting the old duty treatment destroys the audit trail needed to explain why the landed cost changed.

Route ambiguity instead of holding the whole portfolio

The highest-risk cases should move into named exception queues. At least four queues are useful:

1. Classification or origin ambiguity: Product attributes or supplier evidence do not support a confident determination.
2. Liquidation-status conflict: Internal data, broker data, and CBP status do not agree, or the entry is subject to another proceeding.
3. Document mismatch: Invoice value, line quantity, importer identity, or duty amount differs across the entry packet.
4. Instruction pending: The entry falls outside the announced timing or population, including entries submitted after the stated July cutoff.

Each queue needs an owner, service level, and permitted next step. Customs compliance should own technical classification and origin questions. Finance should reconcile payment and refund amounts. Brokers should correct filing discrepancies. Counsel should handle protests, litigation, and final-liquidation questions where legal rights or deadlines are involved.

Do not let one ambiguous population freeze entries that already pass the control. Release clean records in governed batches, then reconcile acceptance, rejection, payment, and interest results back to the entry table.

Preserve the landed-cost decision after the refund

Refund processing changes historical landed cost. That can affect product margins, customer billing, inventory valuation, duty drawbacks, and supplier or customer agreements. Posting one aggregate credit may balance cash while leaving every operational decision based on the old cost.

A transportation management system should retain the shipment-to-entry relationship and record the sequence: original duty estimate, broker filing, payment, liquidation, eligibility decision, refund request, CBP response, and cash receipt. Every adjustment should include its source, timestamp, amount, and approving role.

The same record supports better controls going forward. Teams can compare estimated and filed duties, identify products that repeatedly generate classification exceptions, measure broker-document error rates, and update landed-cost projections without erasing history.

Track operational measures such as percentage of entries fully documented, value ready for submission, exception aging, expected-to-received variance, and days from eligibility to cash. These measures expose readiness and bottlenecks; a headline refund total does neither.

Turn the October change into a repeatable control

CBP's expansion creates a near-term deadline, but the durable capability is an entry-level compliance workflow. Classification, origin, value, dates, and duty treatment should be validated before filing, linked to shipment evidence, and retained through liquidation and any correction or refund.

CXTMS can connect freight movements, customs references, broker documents, landed-cost decisions, and exception ownership in a single operational record. That gives compliance and finance teams the same evidence without relying on disconnected spreadsheets.

Request a CXTMS demo to see how entry readiness, customs exceptions, and landed-cost changes can be managed alongside the shipment lifecycle.