How duty calculation is usually set up in finance and ERP systems

Most companies calculate duty by combining item master data, purchase order details and a tariff rate table, either in the ERP's trade module or in a connected trade compliance tool. That estimate feeds landed cost. The customs broker's filed entry later confirms the figure or corrects it, and finance reconciles the two.

Where the data lives

Duty depends on a handful of facts about the goods, and each one tends to sit in a different place.

Tariff classification is usually held on the material or item master, often per destination country, because the same product can carry different codes in different markets. Someone in trade compliance owns these codes. In practice, buyers or engineers sometimes set them when a new item is created, and nobody reviews them afterwards.

Country of origin may be stored on the item, on the supplier record or on the purchasing info record. Origin drives whether a preferential rate under a trade agreement can be claimed. Those claims also need supporting supplier declarations, which are often tracked in a separate document store with their own expiry dates.

The rate tables themselves are typically loaded from a content provider and refreshed on a schedule. Some smaller setups maintain rates by hand in a condition table, which works until a tariff change is missed.

How the estimate gets built

When a purchase order or inbound delivery is created, the system works out a customs value. That starts from the item price and is then adjusted according to the Incoterms on the order. Freight, insurance, assists and royalties may need to be added, depending on the destination's valuation rules. The ERP often cannot see all of these at order time, so the first number is an approximation.

The applicable rate is applied to that value. Specific duties based on weight or quantity need unit conversions that are set up correctly. Anti-dumping or countervailing duties sit on top and are frequently handled as manual exceptions.

The result usually lands as a planned delivery cost or condition on the order. At goods receipt it is posted as an accrual, so inventory carries an estimated landed cost before any invoice arrives.

When the real figure arrives

The broker files the entry and pays or defers the duty. The broker then invoices the importer, or the customs authority debits a deferment account directly. Either way, a document arrives showing what was actually assessed, line by line.

This is where duty calculation meets accounts payable. The broker's invoice is matched to the original order and to the receipt, much as any commercial invoice would be. Lines that fail the match are held. Common reasons are a different classification, a revised value or a rate the system did not expect. Someone has to decide whether the broker was wrong, the master data was wrong, or the estimate was simply incomplete. Each answer leads to a different fix.

Variances between accrued and assessed duty are posted to a price difference account, or back to inventory if the goods are still on hand. Where many shipments are consolidated on one broker statement, this matching becomes the heaviest part of the job.

Accounting treatment

Duty normally forms part of inventory cost and flows to cost of goods sold as stock is consumed. Duty on items that are not stocked, such as spare parts charged straight to a cost centre, goes to expense instead. Import VAT is often collected in the same customs payment but is recoverable, so it must be split out to a tax account and kept away from cost.

Companies running bonded warehouses, inward processing or drawback schemes need extra setup. Duty may be suspended, paid later or reclaimed after export. Those regimes demand traceability from import to final disposal, and most standard ERP configurations do not provide it without a dedicated trade module.

Where setups usually break

Classification codes go stale when products change but the item master does not. Origin is recorded at supplier level when it really varies by item or by shipment. Incoterms on the order disagree with what the logistics team actually negotiated. Preferential rates get applied without valid certificates behind them, which creates exposure at audit.

Another frequent gap is ownership. Trade compliance owns the codes and logistics owns the broker, while finance owns the accrual. Each assumes one of the others is checking the variance report.

Questions to ask the people who run it

Ask who sets the tariff code on a new item, and whether anyone checks it before the first shipment.

Ask how origin is decided when a supplier ships the same part from more than one plant.

Ask the accounts payable team what happens when a broker invoice does not match. Find out whether they chase the broker, adjust the accrual themselves or simply approve it.

Ask whether anyone compares the duty actually paid against what was estimated, and what they do with the differences they find.

Ask how rate changes reach the system, and who would notice if an update failed.

Ask which shipments are handled outside the system altogether. Samples, returns and urgent air freight are common examples.

Ask where preferential origin certificates are kept, and how someone would produce one if customs asked tomorrow.

The answers will show which parts of the documented design are followed and which have quietly been replaced by spreadsheets and habit.

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.