How export and import control is set up in finance and ERP systems

Export and import control usually sits in a trade compliance module attached to the ERP, or in a separate trade system connected to it. That layer checks products and trading partners against the rules for each destination. It holds documents that fail. It also passes customs and duty data into the finance postings.

Where the controls live

The ERP owns the commercial documents: sales orders, purchase orders, deliveries and invoices. The trade layer reads those documents at set points and returns a decision. Sometimes the decision is a simple pass. Sometimes it places a block that only a compliance user can release.

Some businesses run all of this inside the ERP. Others keep a dedicated trade platform and pass data back and forth. The second setup is common where several ERPs feed one compliance team. It often leaves gaps at the interface, so the integration deserves as much attention as the rules themselves.

Master data carries most of the load

Almost every check depends on data maintained well before an order exists.

Each product needs a tariff classification for import and, where relevant, an export control classification. Country of origin belongs on the item or the batch. Valuation rules may also be stored there. When classification is missing, the system either blocks the order or quietly lets it through. Which of those happens is a design choice that someone made, and it is worth finding out.

Business partners are screened against restricted party lists. Screening runs when a customer, supplier or ship-to address is created. It runs again whenever the lists are updated. Near matches go to a review queue. A person then confirms a true hit or clears a false one, and that decision is stored with a reason.

Country and embargo settings decide which destinations need a licence and which are closed entirely. Licences are usually recorded as their own objects in the system, with limits on quantity or value. Each shipment draws down against them.

Blocks on documents

The usual pattern is to check at order entry and check again at delivery. The second check matters because lists and licences change in the gap between the two. A document that fails is held, and nothing downstream can proceed until the block is released. That means no picking, no goods issue and no billing.

Release rights belong with compliance staff, kept apart from sales and logistics users. A release with no recorded reason is one of the first things an auditor will ask about.

Customs filing and brokers

Export declarations and import entries are built from delivery and invoice data. Some companies file directly with customs. Many send the data to a broker, who files and then returns an entry number along with the duty assessed. The return message is the part that most often breaks. When it fails, finance is left with a broker invoice and nothing in the system to match it to.

Special regimes add more configuration. Bonded warehouses, inward processing, duty drawback and preferential origin all need extra tracking. For each one, the system has to prove later where goods went and what they were made from.

How duties and import tax reach the ledger

On the import side, duty is generally treated as part of inventory cost. It is often estimated at receipt as a planned delivery cost and posted to an accrual. When the broker or customs invoice arrives, it clears that accrual, and any difference goes to a variance account or back to stock.

Import VAT or similar taxes are handled separately from duty because they are normally recoverable. They post to a tax receivable through a clearing account. Deferment schemes and customs guarantees may also need their own accounts and a monthly reconciliation against customs statements.

Export sales carry fewer postings. They still need the correct tax treatment, and the proof of export has to be kept to support a zero rate.

Evidence for auditors

Internal control reviews look for a short list of artefacts. These include screening logs, block and release history, licence drawdowns and the link between each declaration and the matching invoice. Cycle memos describe where each check happens and who owns it. Auditors then ask for samples, so the system should be able to pull a declaration together with its supporting documents without a manual search. Findings usually turn into changes to release rights, to screening settings, or to how often data is reviewed.

Questions to ask the people who run it

The documented design and daily practice drift apart here more than in most finance processes. These questions tend to surface the difference.

• When a product has no classification, what actually happens to the order?
• Who clears screening matches, and does anyone check their decisions afterwards?
• Are blocks ever released in bulk, for example at month end or before a large shipment?
• How often does broker data fail to come back, and what does the team do when it does?
• Which spreadsheets sit alongside the system, and what do they track that the system does not?
• How are duty variances investigated, or do they simply get written off?
• If customs asked for the file behind a shipment from last year, who would assemble it, and from where?
• Which shipments bypass the standard flow, such as samples, returns, repairs or intercompany moves?

The answers to the last question often reveal the largest exposure. Those flows tend to be set up outside the normal order types, and the checks were never extended to cover them.

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.