Customs Valuation for Import and Export: The ERP Data Requirements

The invoice is the starting point, not the answer

Customs value is the figure on which duty and import VAT are assessed. Almost everyone's first instinct is that it equals the invoice total, and almost everyone's first customs query proves otherwise. The internationally accepted primary basis is transaction value — the price actually paid or payable for the goods when sold for export to the country of import — but that price is then adjusted. Some elements are added because they are part of what the buyer gave up; some are deductible because they are not part of the goods' value. The adjusted figure, not the invoice figure, is the dutiable value.

The reason this belongs in an ERP discussion rather than a customs broker's, is that the adjustments draw on data that lives in different modules. Freight and insurance sit in logistics and finance. Commissions sit in sales agreements. Royalties sit in licensing contracts that finance may never see. Assists — free or reduced-cost materials, tooling, engineering supplied to the seller — sit in procurement or nowhere at all. A customs declaration that ignores these is not necessarily wrong, but it is unverified, and the liability for an incorrect declaration rests with the importer, not the broker who filled in the form.

The valuation methods, in order

The WTO Customs Valuation Agreement sets out six methods that must be applied sequentially: you use the first that can be applied, and you may not jump ahead because a later method gives a more convenient answer. Understanding the sequence matters because a company that cannot support transaction value falls to the next method, and the next method usually produces a higher value.

• Method 1 — Transaction value: the price actually paid or payable, adjusted for specified additions and deductions.
• Method 2 — Transaction value of identical goods: the value of comparable goods exported at or about the same time.
• Method 3 — Transaction value of similar goods: comparable but not identical goods, applied with adjustments for differences.
• Method 4 — Deductive value: derived from the resale price in the importing country, with deductions for costs incurred after import.
• Method 5 — Computed value: built up from production cost, profit and general expenses, as reflected in the seller's records.
• Method 6 — Fallback: a flexible application of the earlier methods, applied reasonably and consistently with the agreement.

The practical implication is that documentation supporting Method 1 is an asset. An importer who can demonstrate the price paid, the adjustments made and the basis for each is not asked to move to Method 2 — which would require finding identical goods and arguing comparability, a process that consumes weeks and rarely produces a lower number.

Additions: the expensive ones

The elements added to the price are where most valuation errors originate, because they are frequently paid to someone other than the seller and therefore do not appear on the commercial invoice. The classics are commissions and brokerage (buying commissions are treated differently from selling commissions), the cost of containers and packing, and the value of goods and services supplied free or at reduced cost by the buyer for use in production — the assists.

Assists are the category most consistently missed. If you supply tooling, moulds, dies, design work or engineering to your supplier so they can manufacture your order, that contribution is normally part of the customs value of the imported goods even though no payment flows for it on the invoice. Tooling amortisation is particularly awkward: the mould may produce goods across several years and several orders, so the value must be apportioned, and the apportionment must be documented. A company that supplied a mould and neither recorded its value nor allocated it across shipments has an underdeclaration, whether or not it intended one.

Royalties and licence fees are the other significant trap, and the test is relational rather than mechanical: a royalty related to the imported goods that the buyer must pay, as a condition of sale of the goods, is normally added to the customs value. The difficult case is a royalty paid for the right to use a trademark or technology that is also embedded in locally produced goods — the portion attributable to the imported goods must be identified and added, which requires a defensible allocation method rather than a reasonable guess.

Deductions: fewer, and strictly conditional

Deductions are a shorter list and the conditions are tighter, which is why they are argued about more. Costs of transport after import, duties and taxes in the importing country, and certain costs of construction or assembly after import may be deductible if they are separately identified in the price. The word separately does decisive work: a single landed price that includes installation, with no line-item breakdown, generally cannot be reduced by the installation cost, because you cannot demonstrate the amount.

The operational lesson is that the data must exist at the time the price is agreed. A contract that quotes one number covering goods and post-import services is a contract that has made a valuation decision by omission. If you want to deduct, structure the price with separate line items from the beginning — and make sure the ERP preserves that separation through to the order line rather than collapsing everything into a single amount.

Import and export valuation are not symmetrical

Exporting companies often assume the logic mirrors the import side. It does not, and the difference matters for anyone who has built a model on one side and expects it to serve the other. On import, the value generally includes transport costs up to the place of importation, so freight and insurance are typically part of dutiable value. On export, the declared value for export purposes is usually the transaction value on the export sale, and the treatment of freight depends on the terms and on what the export declaration is being used for — rebate computation, for example, generally rests on the FOB value.

That asymmetry has a direct systems consequence: the ERP needs more than one stored value per shipment line, with the derivation of each from the order terms and freight data explicit. A system that stores one 'shipment value' and reuses it for the export declaration, the rebate computation, the commercial invoice and the internal margin report will be wrong for at least one of them. The rebate side of this is covered in export tax rebate ERP software for China, and the trade-term cost allocation in FOB and CIF pricing in ERP.

Related-party purchases and the arm's length question

Where the seller and buyer are related — a Chinese subsidiary buying from its overseas parent, or the reverse — transaction value is still the primary basis, but it is accepted only if the relationship has not influenced the price. That turns a customs question into a transfer pricing question, and the two do not always pull in the same direction: a pricing policy designed to move profit to a low-tax jurisdiction may produce a customs value that looks low by comparison with identical goods, which is exactly the pattern a valuation review looks for.

The practical requirement is a defensible comparability position: evidence that the price is consistent with what unrelated parties pay for the same or similar goods, or a documented explanation of why the margin differs, drawn from the same intercompany policy that the transfer pricing file describes. Companies that maintain a transfer pricing study for tax purposes but never connect it to their customs declarations are holding two inconsistent explanations of the same price. When one authority reads the other's file, the inconsistency is not a detail — it is the finding.

Post-entry adjustments and voluntary correction

Prices change after import more often than most companies admit: rebates are settled at year end, volume discounts are credited retrospectively, warranty costs are recharged, and a transfer pricing policy is trued up annually. Each of these can change the customs value of goods that were declared months earlier. The obligation in most jurisdictions is to adjust the declaration, not to leave the original figure standing because the shipment has cleared.

This is an area where the ERP is either an asset or a liability. If retrospective credits and recharges are recorded only in the general ledger, linking them back to specific declarations is forensic work and usually does not happen. If the price adjustment carries a reference to the original transaction and the declaration, a post-entry adjustment becomes a reportable list rather than an archaeological exercise. The same data supports voluntary disclosure — usually treated far more favourably than a correction discovered during an audit, which is the practical argument for making the link before anyone asks.

It is worth being clear that voluntary correction is not a comfortable activity and no company should build a process around the assumption that disclosure is painless. The point is narrower: the decision of whether and how to correct should be a business decision made with information, rather than a decision forced by the absence of information. A system that cannot identify which declarations are affected has removed the choice.

Working with a broker without outsourcing the liability

A customs broker is a specialist in procedure, not a party to your commercial arrangements. It can classify goods, prepare declarations and manage the formalities at the port, but it cannot know that your engineering team supplied tooling at no charge, that a licence agreement includes a royalty tied to sales of the imported product, or that the price was set under an intercompany policy reviewed annually. Those facts live inside the business, and the declarations are only as accurate as what the business chose to disclose.

The workable arrangement is a standing valuation brief per product family or supplier, maintained by the business and given to the broker as reference, reviewed whenever a contract changes. It should state the valuation basis, the adjustments that apply, the ones explicitly considered and rejected with a reason, and the documents that support each. That brief turns the broker from a guesser into an applier of stated positions, and it turns a customs query from an argument about facts into a review of a documented methodology. The same brief is the natural companion to the transfer pricing file and to the audit pack described in preparing for a China export tax audit.

What the ERP must hold

The requirements are not exotic, but they are consistently absent in systems designed primarily for domestic trade.

• Trade term per order line, with the cost components (goods, freight, insurance, other) stored separately and the customs value derivable rather than typed.
• A freight and insurance record attributable to the shipment or line, so an adjustment can be computed and evidenced rather than estimated.
• A register of assists — tooling, moulds, engineering, free-issue materials — with value, date supplied, and an allocation schedule across the goods they support.
• Royalty and licence agreements recorded with the goods they relate to and the allocation basis, not merely the payment amounts.
• Commission type distinguished between buying and selling, because the valuation treatment differs.
• Versioned declaration records, so a valuation position taken at entry can be reconstructed if it is queried later.
• A reconciliation view showing declared customs value against the commercial invoice value and explaining every difference.

That last item is the one that turns a customs query into a short conversation. If the difference between invoice value and declared value is explained by a stored, itemised adjustment with a supporting document, the query is answered. If the difference is unexplained because the adjustment was applied by the broker from an email, the query becomes an audit.

There is a commercial argument alongside the compliance one. Consistent valuation positions make landed cost predictable, and landed cost is what a distributor or a project buyer actually compares when choosing between suppliers. An importer that discovers a duty assessment after the goods have been priced into a contract has already lost the margin it was counting on. Treating valuation as a cost input rather than a customs formality is how the better-run importers avoid that, and the data discipline is the same either way.

Why this is a governance issue, not a broker issue

For groups importing into several markets, the discipline should be identical across entities even where the local rules differ. A valuation brief that exists in one subsidiary and not another produces two positions on the same product, and the comparison is the first thing a group-level reviewer performs. Standardising the brief is cheap; reconciling divergent positions after the fact is not.

It is common for importers to treat valuation as entirely delegated to the customs broker, on the reasoning that the broker knows the rules. The broker knows the rules; the broker does not know your licensing agreement, your tooling contribution, or that the engineering team sent drawings to the supplier at no charge. The legal responsibility for the accuracy of the declaration sits with the importer, and the information asymmetry means the broker can only declare what it is told.

The fix is procedural and systems-shaped: a valuation data pack assembled per product or supplier, reviewed when a contract changes, and referenced at declaration. For groups with several importing entities, the same pack should be used consistently, because divergent valuation positions on identical goods across entities is exactly the pattern that attracts attention. Consolidation and multi-entity structure is covered in multi-entity consolidation for Chinese groups going overseas. Get the data pack right and valuation stops being a recurring argument with customs and becomes an ordinary master data discipline — which is what it always was underneath.