What to clarify before automating customs and export paperwork

Automated customs and export paperwork is one of the most rewarding applications in international trade, and one of the few where a mistake is not a problem with your customer but a problem with a government authority. A commercial invoice, an export declaration and a statistical trade report are statements made to the state. Whoever files them is liable for them, and that remains the declarant, not the software and not the supplier who built it.

That is not an argument against automating. This is precisely the area where automation removes a great deal of work. It is an argument for settling three things before you place the order, because they decide whether the process lowers your risk or multiplies it.

Your master data is the real precondition

In most ERP systems the commodity code and the country of origin are optional fields on the item record. Optional means, in practice, that they were filled in at some point, often when the item was created, often by somebody who wanted the question dealt with quickly.

While a person writes the export declaration this stays manageable, because in case of doubt they ask. A process does not ask. It takes whatever the field contains and writes it into a document that reaches the customs authority. An unverified entry on an item record thereby becomes a verified declaration, and a typing error becomes a false filing that surfaces during an audit years later.

Every automation project in this area therefore starts with an uncomfortable count. For how many of your active items are the commodity code and the country of origin filled in, and when were they last touched? If the rate is low, master data maintenance is the project and automation is the second step. That is the most common honest answer in this field, and it saves you an expensive false start.

Two fields that are wrong on a regular basis

Commodity codes move. The nomenclature is revised every year, headings are withdrawn, others are split. An item master that was maintained once and left alone since then contains codes that no longer exist. A process that passes such codes on unchecked produces filings that are rejected, or worse, filings that go through and pull a wrong duty rate behind them.

The country of origin is the second recurring error. It is not the country of the supplier and not the country the goods were shipped from. It is the country where the goods were produced or last substantially processed. In many systems this field is populated from the supplier address at creation time, because the value is already there. For a dealer registered in the Netherlands with manufacturing in Asia, the entry is then simply wrong, and no warning appears anywhere.

What automation is particularly good at here

The benefit is not that a process finds the correct commodity code. It cannot, because classification is a specialist decision carrying liability.

The benefit is that a process checks completely, every single time, what a person under time pressure skips. It can determine whether the commodity code and the country of origin are populated at all, whether the code has a permissible number of digits, and whether it still exists in the current nomenclature. It can flag an item whose country of origin matches the supplier's country of registration, given that the two rarely coincide. It can build the commercial invoice, the export declaration and the statistical report from the same verified source, so that three documents do not carry three different values.

And it can stop. In this environment a process that halts on a missing or implausible value and hands the case to a named person is the only defensible construction. Ten minutes of clarification are cheaper than any correction filed with an authority.

Who maintains, and who decides

For this to hold, you need two decisions inside the company.

First, a person or role who owns the classification of a new item before it may be sold. Without that, even the best checking only produces a growing pile of parked transactions.

Second, a rule on how often the nomenclature is reconciled. Once a year at the turn of the year is enough in most cases, and that reconciliation can be automated too. What matters is that it happens and that somebody works through the hits.

Sophera Consulting first looks at the state of your item master, records responsibility and checking rules in writing, and then builds the process for a fixed price, with no subscription and with documentation at handover. The entry point is the free Automation Check.

The recommendation

In this area, do not commission a process that produces documents. Commission one that checks first and produces afterwards. The difference costs a few extra days and decides whether automation multiplies your errors faster or catches them systematically.

And count beforehand how completely the commodity code and country of origin are maintained in your item master. If the rate is high, the project is contained and the benefit is immediate. If it is low, you have found the first piece of work, and you found it before paying for it.