Importer of Record & Tariff Responsibility in Contracts

What “Importer of Record” Means in the U.S. (And Why It’s Not Just a Label)

In plain English, the Importer of Record is the party that U.S. Customs and Border Protection (CBP) treats as responsible for
making entry and meeting the legal requirements tied to importing. That includes providing accurate entry data, exercising
“reasonable care,” and paying duties, taxes, and certain fees.

Legal responsibility vs. business reality

Here’s the part that surprises people: the contract can say “Seller pays all duties,” but CBP still looks to the party acting as the
importer of record for compliance and payment liability. In other words, you can shift cost by contract, but you can’t fully outsource
legal accountability.

Who can be the IOR?

In many transactions, the buyer becomes the IOR by default. But not always. Depending on the structure, the IOR might be:

• The U.S. buyer/importing entity
• A U.S. subsidiary or affiliate of the seller
• A U.S. consignee with authority to enter goods
• An authorized agent arrangement where the entry is filed on behalf of the IOR (often through a customs broker)

The key is that the IOR must be eligible to make entry, and the paperwork and power-of-attorney chain must match realitynot just
what the sales team wrote in a hurry at 11:58 p.m.

Tariff & Duty Responsibility: The Rule CBP Cares About (and the Clause Your CFO Cares About)

“Tariffs” is often used as a catch-all, but your landed-cost bill usually includes a family of charges:

• Customs duties based on HTS (Harmonized Tariff Schedule) classification
• Additional duties (e.g., trade remedy duties like Section 301/232, anti-dumping/countervailing duties)
• Fees such as Merchandise Processing Fee (MPF) and Harbor Maintenance Fee (HMF), when applicable
• Other agency fees/requirements when partner government agencies regulate the product (FDA, EPA, etc.)

The legal anchor: duties attach to the importer

U.S. regulations treat duty liability as a personal debt of the importer, and paying money to a broker doesn’t automatically wipe out
that liability if the broker fails to transmit payment. That’s why “Our broker handled it” is not a winning defense strategy.

So what can a contract do?

A contract can allocate who ultimately bears the cost of tariffs and duties (economically), even though the IOR remains on the hook
legally at the border. Think of the contract as the “who reimburses whom” rulebookplus a set of guardrails to prevent avoidable
mistakes.

Incoterms Are Helpful… But They Don’t Magically Rewrite U.S. Customs Law

Incoterms (like DDP, DAP, FCA, etc.) are widely used to define delivery obligations and risk transfer.
They are incredibly useful shorthanduntil people treat them like a complete customs strategy.

Why DDP gets everyone’s attention

Under DDP (Delivered Duty Paid), the seller generally takes responsibility for import clearance and paying import duties and taxes.
That sounds clean on paper. In practice, it can get messy fast in the U.S. if the seller is not set up to act as IOR or doesn’t have a
compliant structure to handle entry, bonding, and recordkeeping.

DAP and the “surprise bill” problem

Under DAP (Delivered at Place), the seller delivers to a named place, but the buyer typically handles import clearance and import
duties. That’s often fineuntil the buyer assumed “shipping included” also meant “tariffs included.” (It did not.)

Best practice: treat Incoterms as the starting point, not the finish line

A good contract takes the Incoterm and then adds specific clauses that spell out:

• Who will be the IOR for U.S. entry
• Who chooses and manages the customs broker
• Who provides classification, valuation, and origin dataand who stands behind it
• Who bears tariff changes after contract signing
• What happens with refunds, duty drawback, and post-entry audits

The “Reasonable Care” Standard: Your Contract Should Support Compliance, Not Sabotage It

U.S. law expects the importer of record to exercise reasonable care when making entrymeaning the importer should take
practical steps to ensure the classification, value, quantity, and origin information are correct (and that the goods are admissible).
“We guessed” is not a compliance program.

What “reasonable care” looks like in the real world

• Using correct HTS classification supported by product specs and, when needed, expert review
• Confirming country of origin rules (especially when multiple countries touch the supply chain)
• Documenting valuation methodology (assists, royalties, related-party pricing, etc.)
• Maintaining records for the required period (often five years from the date of entry)
• Escalating red-flag scenarios (trade remedies, forced labor concerns, restricted goods)

A contract that assigns tariff costs but doesn’t require data cooperation is like buying a smoke alarm and removing the batteries
because the beeping is “annoying.”

Contract Drafting: Clauses That Prevent Tariff Fights (and Friendship-Ending Email Threads)

If you want fewer disputes, write the contract like you assume tariffs will change, a shipment will be delayed, and someone will ask,
“Waitwho is the importer?” five minutes before the vessel arrives. Because that will happen.

1) Name the Importer of Record explicitly

Don’t leave this implied. State the legal entity (not just “Buyer”) that will act as IOR for U.S. entry. If the seller will act as IOR,
require proof of capability (bonding, broker appointment process, recordkeeping plan).

2) Separate “IOR compliance responsibility” from “economic tariff responsibility”

Clarity hack: include two separate subsections:

• Customs Compliance Responsibilities: who files, who provides data, who signs, who retains records.
• Tariff & Duty Cost Allocation: who ultimately pays, reimburses, or credits duties and related charges.

3) Define what counts as “tariffs” and “import charges”

If you don’t define it, someone will argue “tariffs” means only base duty, while the other side insists it includes additional duties,
MPF, HMF, and the emotional damage of demurrage. Use a definition that includes:

• Base customs duties
• Additional duties (trade remedies)
• Government fees (e.g., MPF/HMF when applicable)
• Penalties and interest (and who bears them, if caused by whom)

4) Add a tariff change / “change in law” mechanism

Tariffs can change after your pricing is locked. Your contract should include a mechanism for:

• Price adjustments when new duties apply
• Renegotiation triggers for extreme changes
• Termination rights if costs exceed a defined threshold
• Notice requirements and documentation standards

5) Require data cooperation (classification, origin, valuation)

The IOR needs accurate product info. The supplier often controls it. So require the supplier to provide and warrant the accuracy of:

• Product descriptions and technical specs
• Materials breakdown / BOM where relevant
• Country of origin details and supporting records
• Pricing components that affect customs value

6) Include indemnities that match fault

A fair approach: if the buyer (as IOR) pays penalties because the seller provided incorrect origin data, the seller indemnifies. If the
buyer misclassified despite accurate specs and ignored advice, that’s on the buyer. Tie indemnity to the cause, not the invoice size.

7) Handle refunds, protests, and duty drawback

If duties are overpaid, who gets the refund benefit? If drawback is available, who files and who gets the proceeds? Your contract should
say:

• Whether the IOR will file protests or post-entry corrections
• How refunds/credits are allocated between parties
• Whether drawback claims will be pursued and how proceeds are shared

Practical Examples: How Contract Language Changes the Outcome

Example 1: “DDP to the U.S.” with a non-U.S. seller

A European supplier sells machines “DDP Chicago.” The buyer assumes the supplier will be the importer and pay duties.
The supplier assumes its forwarder can “handle customs” and invoices duties back later. The shipment arrives, and CBP requires an
eligible IOR with a bond and a proper broker appointmenton time.

If the contract doesn’t name the IOR and doesn’t require an operational plan, the shipment can sit while both sides debate whose
problem it is. A better contract would specify: “Seller shall act as IOR through its U.S. affiliate [Entity Name]” (or “Buyer shall be
IOR, seller reimburses duties”), plus a clear process and timeline.

Example 2: DAP with tariff volatility

A buyer agrees to DAP terms and is IOR. A tariff increase hits between order and arrival. Without a change-in-law clause, the buyer may
be stuck eating the cost. With a clause, the parties follow a pre-agreed playbook: notice, documentation, price adjustment formula,
and the option to pause or renegotiate.

Example 3: Broker error and the “but we paid them” defense

The importer wires money to its broker to cover estimated duties. The broker fails to transmit payment correctly.
The importer discovers a problem only after CBP notices. Contracts that spell out broker selection, controls, reconciliation, and proof
of payment reduce the chance of this “how did this happen” moment.

A Quick Checklist for Contracts Involving U.S. Imports

• IOR named? Legal entity identified, with operational capability confirmed.
• Incoterm aligned? Incoterm chosen, and additional U.S.-specific customs obligations addressed.
• Tariff definition included? Covers base duty, additional duties, fees, and related costs.
• Change-in-law clause? Price adjustment or renegotiation mechanism for tariff changes.
• Data cooperation clause? Supplier provides accurate classification/origin/valuation inputs.
• Indemnities fair? Allocated based on fault and control of information.
• Refund/drawback handled? Who files, who benefits, what documentation is required.
• Recordkeeping addressed? Who keeps what records, where, and for how long.

Conclusion: Make Tariff Responsibility Boring (That’s the Goal)

The smartest import contracts don’t try to “win” tariffs. They try to prevent surprises. In the U.S., the importer of record is the party
CBP looks to for compliance and duty liability. Your contract can still allocate who ultimately bears the costbut only if you write the
deal with operational reality in mind: clear IOR designation, clear tariff definitions, data cooperation, and a plan for what happens when
the trade environment changes.

If your contract can answer “Who is the IOR?” and “Who pays tariffs if they change?” in one breath, you’re already ahead of most
panic-filled inboxes in international trade.

Real-World Experiences: 5 Lessons People Learn the Hard Way (So You Don’t Have To)

Below are field-tested experiences companies run into when “Importer of Record” and “tariff responsibility” are treated as an afterthought.
No names, no shamejust the kind of trade stories that make compliance teams laugh so they don’t cry.

1) The “DDP means you pay everything, right?” misunderstanding

One buyer ordered goods under DDP terms and assumed duties were handled. The supplier assumed it could simply “arrange delivery”
and bill the buyer later for any duties. The shipment landed, and the forwarder asked, “Who is the importer of record?”
The buyer said, “Not me.” The supplier said, “Not legally possible.” CBP said nothing (CBP doesn’t do group therapy), but the cargo
sat while both sides scrambled to appoint a broker and figure out bonding.

The fix was simplebut late: the revised contract named the buyer as IOR, required the supplier to provide classification/origin support,
and created a clean reimbursement process for duties that were priced into the deal. Same business outcome, fewer clearance delays.

2) The tariff increase that turned “profitable” into “we should’ve sold lemonade instead”

A mid-sized importer priced a long-term supply contract when duties were stable. Then additional duties applied to the product category
months later. Because the contract didn’t include a change-in-law clause, the importer ate the difference for multiple shipments.
They tried to renegotiate anyway, which is like trying to install a seatbelt after the crash.

Their next contract included a tariff-adjustment mechanism: if duty rates increased beyond a defined threshold, pricing adjusted by a
formula tied to documented duty amounts. It didn’t make tariffs “fun,” but it made the math predictableand predictability is basically
happiness in spreadsheets.

3) “Our broker handles compliance” (famous last words)

Another company relied heavily on a broker to file entries. The broker was competent, but the importer’s internal product data was
messydescriptions changed, SKUs were reused, and origin data lived in three different systems (none of which agreed with each other).
When CBP questions arose, the importer realized the broker could only file what they were given. “Reasonable care” still landed on the
importer’s desk, not the broker’s.

The company updated its contracts to require suppliers to provide stable technical specs and origin support, and it added an internal
“import data pack” process before purchase orders were issued. Not glamorous, but neither is a post-entry audit.

4) The refund fight: “Who gets the money back?”

Sometimes the drama arrives after the import. A business discovered it had overpaid duties due to misclassification and could pursue a
refund/protest. The supplier said, “We’ll cooperate… if we get the benefit.” The buyer said, “We’re the IOR, so it’s ours.”
The contract said nothing, which is the legal equivalent of a shrug emoji.

In later deals, they added a refunds/drawback clause: who files, who provides documents, how refunds are shared, and how long each
party must cooperate. Suddenly, the “who gets the refund” debate became a one-paragraph answer instead of a month-long email saga.

5) The best experience is the one where nothing exciting happens

The smoothest imports often come from boring discipline: the contract names the IOR; the Incoterm matches the logistics plan; product
data is consistent; tariff responsibility is defined; and there’s a written response plan for changes. Nobody puts that on a billboard,
but it’s the difference between “clearance in a day” and “why is this container still here?”