Caterpillar’s $392 Million Tariff Refund Shows Why Duty Data Needs an Audit Trail

A tariff reversal can look like a windfall on an earnings statement. Inside an importer’s operations, however, it creates a demanding reconstruction exercise: identify the affected entries, prove which duties were paid, connect them to products and shipments, determine the recoverable amount, and restate costs without erasing the original transaction history.

Caterpillar’s latest results put the scale of that work into focus. The manufacturer recognized $392 million in overturned tariffs during the second quarter, according to Supply Chain Dive. The company also said tariff costs were more than 40% below its previous estimate. Yet Caterpillar still expected roughly $2.2 billion in tariff costs for 2026.

The lesson for logistics teams is not that tariffs have disappeared. It is that duty liabilities can change after goods move, making historical data quality a material financial control.

A refund is a data-reconciliation event

Tariffs enter the business through customs entries, but their effects spread much further. Duties may be allocated to purchase orders, inventory, customer orders, shipments, business units, and product margins. A refund therefore cannot be handled as a single credit posted to a general ledger account.

For Caterpillar, the $392 million recovery equals nearly 18% of its remaining $2.2 billion annual tariff estimate. At that magnitude, a weak allocation method could materially distort product profitability or regional performance. Even for a smaller importer, applying a refund at an aggregate level can leave the wrong inventory, customer, or cost center carrying the original duty expense.

The reconciliation must answer several questions:

• Which customs entries were covered by the overturned measure?
• What tariff rate and classification were used when each entry was filed?
• Which shipment, purchase order, SKU, and supplier correspond to each entry line?
• Was the duty capitalized into inventory, expensed, or passed through to a customer?
• Has the merchandise been sold, transferred, or remained in stock?
• What amount was actually received, and how does it differ from the amount claimed?

Those connections rarely live in one system. Brokers hold entry records, transportation systems hold movement data, ERP platforms hold purchasing and inventory costs, and finance systems hold accounting treatment. The audit trail must bridge them.

Preserve the original duty state

One of the most dangerous shortcuts is overwriting the original duty amount after a refund becomes probable. That makes current reports appear clean but destroys evidence of what the company knew and paid at the time of import.

A stronger model treats each change as a new event. The shipment record retains the originally assessed duty, while separate fields or transactions capture the refund claim, approval status, expected recovery, cash receipt, and final adjustment. Each event should carry a timestamp, source document, user or system identity, and reason code.

This event-based approach matters because the operational and accounting dates differ. Goods may arrive in one quarter, a court or agency decision may occur in another, and cash may be received later. Preserving each state allows finance to apply its recognition policy while logistics continues to see the true historical landed cost.

Build an evidence chain at entry-line level

Refund eligibility often depends on details below the shipment header. Importers should retain the entry number, line number, Harmonized Tariff Schedule classification, country of origin, entered value, duty rate, duty amount, filing date, liquidation status, and broker reference. Commercial invoices, packing lists, bills of lading, origin documents, and payment confirmations should be linked rather than stored in disconnected folders.

The shipment is the useful joining point. A transportation management system can associate the carrier movement and freight charges with the purchase order and customs entry. That relationship lets analysts calculate both the original landed cost and the revised cost after recovery—without confusing a customs refund with a reduction in transportation spend.

Data controls should also prevent silent changes. If a broker sends a revised entry file, the integration should version it, flag changed classifications or amounts, and route exceptions for review. A hash or immutable document ID can show that supporting evidence has not been substituted after approval.

Reconcile across operations and finance

The operational workflow should begin with a population of potentially eligible entry lines, not with an assumed lump-sum receivable. Teams can then match the claim population to broker data and customs notices, calculate expected recovery, and record differences between claimed, approved, and received amounts.

Finance needs the same identifiers used by trade compliance. A shared reference—combining entry, line, SKU, and shipment—allows the refund to flow to the correct inventory layer or cost object. When merchandise has already been sold, the adjustment may affect cost of goods sold; when it remains in stock, it may alter inventory value. The proper accounting treatment belongs with the company’s finance policy, but logistics data determines whether that treatment can be applied precisely.

Dashboards should separate at least four figures: original duty paid, amount under review, approved recovery, and cash received. Combining them creates false certainty and can make working-capital forecasts unreliable.

Controls worth implementing now

Importers do not need to wait for another tariff ruling. They can strengthen readiness by requiring shipment-level customs references, validating entry totals against broker statements, retaining rate and classification history, and prohibiting destructive updates to duty fields. Exception queues should highlight missing documents, unmatched entries, duplicate claims, and differences between expected and received refunds.

Periodic sampling is equally important. Select entries from high-duty lanes and confirm that a reviewer can trace them from customs declaration through transportation record, inventory posting, and general ledger treatment. If that chain takes days of spreadsheets and email, the process is not ready for a large-scale reversal.

Caterpillar’s recovery shows that tariff volatility is not only a sourcing or policy issue. It is a test of whether logistics, customs, and finance share a reliable transaction history. Companies that preserve the original state and connect every adjustment to evidence can recover money faster, restate landed costs accurately, and defend the result later.

Want shipment, cost, and trade-compliance data connected in one operational workflow? Request a CXTMS demo to see how stronger logistics data supports faster reconciliation and better landed-cost decisions.