The periodic revision of the harmonised nomenclature takes effect this year, and as usual a proportion of the changes are consequential rather than cosmetic. Codes are being split, merged and renumbered, and a code that has been correct for a decade may simply cease to exist.
Importers with a long product master and no review process are the ones most exposed, because the failure surfaces as a rejected declaration on a consignment that is already at the port.
What changes
Three kinds of change matter. Codes that disappear entirely are the easiest to catch, because the declaration fails validation. Codes that survive but change scope are harder: the declaration passes, the duty rate may differ, and nothing tells you the classification is now wrong. Codes that are newly created for goods previously classified elsewhere fall into the same category.
What to do now
- Extract every commodity code used in the last two years, not only the ones in the current product master. Discontinued lines still get returned and re-imported.
- Map each against the correlation tables and mark anything that changed scope for a full re-review rather than a mechanical substitution.
- Check whether any preferential origin claim depended on a code that has moved, because a change of heading can affect whether a product-specific rule is satisfied.
- Review any binding ruling you hold. Rulings do not survive a nomenclature change automatically, and one that lapses without being replaced leaves the classification unsupported.
Timing
Do this before the change takes effect rather than after. Amending a declaration filed under a defunct code costs more than filing it correctly, and where duty was underpaid the correction carries interest. We are running the mapping exercise for retained clients through the first quarter and can take it on for others on a project basis.