IEEPA Tariff Class Action: Build the Entry-Level Evidence File Before Refund Claims Open

A federal court's decision to allow an IEEPA tariff class action to proceed does not guarantee that every importer will receive a refund. It does make one operational lesson urgent: a potential claim is only as usable as the entry-level evidence behind it.

Importers should not wait for the litigation to settle before connecting customs entries, duty payments, products, shipments, and accounting records. Building that file now reduces the risk of missed entries, duplicate claims, unsupported amounts, and months of reconciliation later.

Understand what changed—and what did not

Supply Chain Dive reported that the U.S. Court of International Trade cleared the way for a class-action suit involving importers that paid tariffs imposed under the International Emergency Economic Powers Act. The court estimated that, without the class mechanism, approximately $30 billion in IEEPA tariffs could remain with the government.

That procedural development matters because many importers may not have filed individual lawsuits. But it is not a final payment instruction, and businesses should not book an assumed recovery based on a headline. Eligibility, covered entries, deadlines, final liquidation status, appeals, and the treatment of particular claims can still affect the outcome. Customs counsel should interpret the orders; operations should make sure counsel receives complete records.

The scale explains why informal spreadsheets are risky. Reuters reported that more than 330,000 importers paid IEEPA tariffs across 53 million shipments, according to court documents. Reuters also reported that CBP said payments could take up to 45 days as its refund system progressed. At that volume, exceptions will be normal rather than rare.

Build one record for every customs entry

Create a controlled evidence record keyed to the customs entry number. At minimum, it should include:

• importer of record number and legal entity;
• entry number, entry type, port, filing date, entry date, and liquidation status;
• HTS classification, country of origin, entered value, quantity, and IEEPA duty rate;
• duty amount deposited and proof of payment;
• entry summary, commercial invoice, packing list, broker transmission, and relevant CBP notices;
• protests, post-summary corrections, reconciliation entries, drawback activity, reliquidation, or amendments;
• purchase order, SKU, shipment, container or air waybill, and general-ledger references; and
• refund status, amount expected, amount received, interest, variance, and final disposition.

Preserve versions rather than overwriting them. An original entry and a later correction tell an important story about classification, value, and the amount actually paid. The evidence file should show who changed a field, when it changed, why, and which supporting document authorized the change.

Treat HTS codes as evidence, not merely lookup data. A shipment can contain multiple tariff lines, and one invoice can span products with different rates or countries of origin. Recording only a total duty payment makes it difficult to prove which amount belongs to the affected measure or to allocate a recovery back to product cost.

Reconcile customs data to finance and landed cost

Customs and finance often view the same import differently. The customs team sees entries and tariff lines; accounts payable sees broker statements and Automated Clearing House withdrawals; merchandising or manufacturing sees SKUs and purchase orders; logistics sees shipments and containers.

Build a bridge among those views. For each entry, reconcile the duty deposit to payment evidence and the general ledger. Then allocate the affected duty to products using the same defensible method used in landed-cost accounting. Flag differences instead of forcing a match.

Typical exceptions include a broker payment covering several entries, an amended value, a split shipment, an entry tied to multiple purchase orders, an importer-of-record mismatch, a duty charge passed through by a vendor, or a refund already received through another process. Each exception needs an owner and resolution note.

Refund activity is already moving through different operational pathways. Supply Chain Dive separately reported that CBP began processing refunds for certain finally liquidated entries, while eligibility at that stage was limited to specified plaintiffs that had provided valid importer numbers by an earlier deadline. That distinction is a reminder to label each entry by procedural status rather than applying one assumption to the entire portfolio.

Assign ownership before a deadline appears

Use a simple responsibility model:

Customs compliance owns the entry population, tariff-line review, broker instructions, and communication with CBP. Finance validates cash paid, ledger treatment, receivable policy, and cash received. Brokers supply filing data, correction history, liquidation notices, and transmission records. Legal counsel determines claim strategy, scope, deadlines, and required preservation. Procurement and product teams validate SKU, supplier, origin, and purchase-order mappings.

Appoint one accountable program owner to manage the exception queue and sign-off. Set controls for duplicate entry numbers, missing documents, conflicting duty totals, and stale status. A weekly dashboard should show total entries reviewed, potentially covered value, evidence-complete value, open exceptions, refunds received, and unreconciled cash.

Do not send bulk instructions to brokers until counsel defines the action. Preserving and organizing evidence is prudent; filing protests, amendments, or claims is a legal and customs decision with deadlines and consequences.

Connect the evidence without disrupting clearance

The preparation effort should not slow current imports. Keep the live clearance process intact and create a linked evidence layer. In CXTMS, teams can associate the customs entry and tariff-line references with the purchase order, shipment, container, invoice, and delivery milestones already used in daily operations.

That connection makes gaps visible. A paid entry with no shipment reference can enter an exception queue. A shipment with several entries can retain each separately. When a refund arrives, finance can trace it from CBP or the broker to the entry, product allocation, and original landed cost without rebuilding the chain from email attachments.

The legal outcome remains outside an operator's control. Evidence readiness does not. A complete, entry-level record gives counsel a reliable population to assess, gives finance an auditable basis for reconciliation, and gives management a realistic view of exposure without treating a possible refund as certain cash.

Request a CXTMS demo to see how customs references, shipment records, documents, and financial exceptions can be connected in one transportation workflow.