Calculate duty: where the process breaks and how to spot it

Duty calculation usually breaks where data passes between owners. Common examples are the item master and the customs broker, the purchase order and the declared value, and the broker statement and the ledger. The errors surface late, as amended entries, unexplained duty variances and accruals that never clear.

The broker handoff

Most importers do not file their own entries. A broker classifies, values and declares goods using whatever the shipper and the importer sent. When the commercial invoice is thin, the broker fills the gaps from past shipments or from guesswork. Nobody inside the business sees that choice until the duty bill arrives.

The signs are easy to find once someone looks. Brokers send repeated emails asking for product descriptions. Entry lines carry codes that do not appear in the item master. One part number gets declared under different tariff codes on different shipments.

Classification living in two places

Tariff codes often sit in the ERP item master and again in the broker's own database. Each copy gets updated by different people for different reasons. Over time they drift apart. Engineering changes a component and nobody tells trade compliance. A new supplier ships a near identical product under a new part number with no code at all.

To detect this, compare declared codes against master data for a sample of recent entries. Items with blank or placeholder codes are a strong clue. So is a classification field that only one person is allowed to edit and that person is always behind.

Valuation that misses what was actually paid

Customs value is not always the invoice price. Freight, insurance, royalties, tooling the buyer supplied and later price adjustments can all change it. Purchasing negotiates these terms. Trade compliance rarely hears about them. Accounts payable sees the true cost but has no reason to flag it.

Suspect a gap here when supplier rebates or retroactive price changes are booked without any matching customs amendment. Another sign is moulds or dies shipped to an overseas supplier with no record of how their value reached the entry. Disagreement over which Incoterms apply to a lane is a further warning.

Origin claims without proof

Preferential trade agreements cut duty, but only with valid origin evidence. Teams sometimes claim the preference because the supplier said the goods qualify, and the supplier declaration is never filed or has expired. The saving looks real right up until an audit request reverses it.

Watch for preference claims on goods sourced through distributors, where nobody knows the true origin. Declarations kept in personal inboxes are another clue. So is a renewal process that depends on one person remembering.

Exchange rates and timing

Duty is assessed at the official rate on the date set by the customs authority. Finance often books the accrual at the company rate on receipt. The two figures will never match exactly. If no one owns the difference, it sits in a variance account and grows.

An exchange variance that is cleared by journal at period end without explanation points to this problem. The same is true when the accrual method was set up years ago and nobody can say why.

Matching the broker invoice

The broker bills duty, taxes, fees and disbursements together, often weeks after goods are received. Payables must match that bill to the entry, the receipt and the accrual. When the match fails, the invoice is held. A held broker invoice can stall the next shipment if the broker extends no further credit.

Trouble shows up as a large pile of unmatched broker invoices and receipts with duty accrued but never relieved. Payment adjustments for refunds and amended entries often land in the wrong cost centre, which is another symptom.

Exceptions handled off system

Samples, returns, repairs and temporary imports rarely follow the standard flow. People handle them by email and spreadsheet. Drawback claims and duty refunds get the same treatment. These workarounds keep goods moving but leave no trail, so recovery is missed and the same mistakes repeat.

Tell tale evidence includes a shared spreadsheet that is plainly more current than the system. Refunds that arrive with nobody expecting them belong in the same category. So do returned goods that were charged duty twice.

Questions to ask the people who run it

What documented procedures say and what happens on a busy day are often different. These questions tend to surface the gap:

• When the broker asks for a tariff code that is missing, who answers, and where does the answer get recorded?
• Which spreadsheet would cause the most damage if it disappeared tomorrow?
• How does trade compliance learn about price changes, rebates or tooling agreed by purchasing?
• Who checks that a supplier origin declaration is still valid before a preference is claimed?
• What happens to a broker invoice that does not match? Who releases the hold, and on what evidence?
• Where does the difference between accrued duty and paid duty go, and who explains it?
• How are samples, repairs and returns entered, and does anyone review them afterwards?
• When customs amends an entry, how does that change reach the ledger and the product cost?
• Which steps get skipped when a shipment is urgent?

Answers that point to a named individual, a personal inbox or "it depends" mark the places where the process relies on memory. Those are the first places to redesign.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.