Resource

Where duty and tariff costs hide in COGS.

For many import-heavy companies, duty and tariff cost is not visible as a clean management line item. It is often buried inside inventory cost, landed-cost logic, purchase-price variance, freight allocation, broker statements, or manual accounting entries. That makes the first trade-margin question simple but hard to answer: how much duty cost is actually inside the margin base?

Start with landed cost, not the refund idea.

Duty and tariff cost usually enters the business through the import process, but finance may experience it later as inventory value or cost of goods sold. The customs entry, broker invoice, cash disbursement, and ERP landed cost may all describe the same economic burden from different angles. A serious review starts by tracing those angles before anyone discusses recovery, drawback, or claim-facing questions.

The most useful first view is a duty-cost bridge. It should show the import entry or broker record, the duty or additional tariff line, the product or SKU involved, the inventory receipt, and the accounting path into COGS. If those pieces cannot be connected, a modeled recovery number may look impressive while resting on weak records. Trade Recovery Data treats that as a stop condition, not a sales opportunity.

Common hiding places.

The first hiding place is the broker packet. Duties, merchandise processing fees, harbor maintenance fees, and additional trade-remedy tariffs may be visible in entry summaries, ACE exports, or broker reports, but not in the same system that finance uses to review margin. The second hiding place is the ERP landed-cost module. Some companies allocate duties across inventory receipts, while others post totals to a clearing account or bury the cost in purchase price. The third hiding place is freight and logistics allocation. Import-related charges are sometimes bundled into landed cost even when the business needs to separate duty from freight, brokerage, demurrage, and other charges.

A fourth hiding place is product hierarchy. The customs record may use HTS classification and entry-line descriptions, while finance uses SKU, item master, product family, customer, or business unit. Without a bridge, a CFO can know total duty paid but still not know which margin pools carry the cost. A fifth hiding place is timing. Goods imported in one period may be sold, exported, replaced, rejected, or destroyed in another period. That timing mismatch can make a simple annual total misleading.

What a clean COGS view should answer.

A useful COGS review should answer five questions. First, what duty and tariff cost was paid during the period? Second, where did that cost land in the accounting records? Third, which products, SKUs, invoices, shipments, or lots carried the cost? Fourth, which downstream activity could matter for a specialist review? Fifth, what records are missing or unreliable enough to stop the review?

This is not legal advice, tax advice, customs brokerage, HTS classification, or eligibility work. It is business analysis. The point is to know whether the company has a credible record path and whether the cost exposure is material enough to justify a licensed specialist conversation. A good screen narrows the conversation. It does not make the claim.

Why the 2025-26 environment matters.

Recent tariff expansions and trade-remedy changes have made duty exposure more visible to leadership, but not necessarily easier to measure. CBP maintains trade-remedy resources, Section 301 guidance, and IEEPA tariff FAQ material that show how product, country, entry type, and special tariff provisions can affect treatment. Those details belong with qualified trade professionals. The operational question before that is whether the company can assemble the record base those professionals would need.

Companies that wait until a refund idea appears often discover that the evidence path is weaker than the cost exposure. Companies that start with COGS, source systems, and matching keys get a cleaner answer. Sometimes the answer is proceed. Sometimes it is improve records first. Sometimes it is stop. All three are useful if they prevent wasted time and vague expectations.

Practical first step.

Pull one recent period and ask finance, logistics, and trade compliance to identify the duty-paid record, accounting treatment, product key, shipment key, and downstream activity record. Do not move confidential files yet. Just determine whether the bridge exists. If the bridge is visible, a focused screen may be worth the fee. If the bridge depends on manual guessing, the better first move is record cleanup.

Trade Recovery Data helps with that first screen. The output is not a refund promise. It is a practical record map, materiality view, and stop/go packet for management and any licensed specialist who may review the matter later.