How trade documentation is usually set up in finance and ERP systems

Trade documentation usually runs as an output of the sales and shipping flow in the ERP. A delivery or shipment triggers commercial invoices, packing lists, origin statements and customs declarations, built from master data on products, partners and countries. A separate trade module or broker often handles filing and screening.

Where the documents come from

Most documents are not typed by hand. They are generated. The ERP holds a sales order, then a delivery, then a goods issue, and each of those events can fire an output. Output rules decide which document prints, in what language, for which ship-to country and through which channel. Common channels are paper, PDF by email and an electronic message to a broker or customs portal.

The commercial invoice for customs is often not the same as the billing invoice sent to the customer. It may show values the customer never sees, such as freight split out, assists or a transfer price between related entities. Many setups treat it as a pro forma document tied to the delivery. The real receivable lives elsewhere.

Imports mirror this on the purchasing side. A purchase order and an inbound delivery carry the data a broker needs. The broker files the entry, and the duty and tax figures come back to be posted against the landed cost of the goods.

The master data underneath

Document quality depends almost entirely on master data. Each product needs a tariff classification for every country it moves to or from. It also needs a country of origin, and sometimes a preferential origin status under a trade agreement. Export control classifications sit here too.

Business partners carry their own fields. Incoterms, importer of record, tax registration numbers and screening status all live on the customer or vendor record, or on the order itself when they vary.

In larger setups this data sits in a dedicated trade compliance module that the ERP calls during order processing. Smaller setups keep it in custom fields on the material master. Either way, someone owns it, and that ownership is frequently unclear.

Letters of credit and bank documents

Where trade is financed through documentary credits or collections, treasury gets involved. The letter of credit terms are recorded against the sales order. The shipping team must then produce a document set that matches those terms exactly, down to spelling and dates. Banks reject sets with discrepancies, and payment waits until they are fixed.

Some ERPs track the credit as an object with its own limits and expiry. Others leave it in a spreadsheet kept by treasury. The second arrangement is common and fragile.

Filing, storage and audit evidence

Customs authorities can ask for proof long after goods have moved. So the setup needs a retention rule and a place to store signed copies, carrier documents and broker confirmations, linked back to the delivery or entry number.

Internal control work leans on the same archive. Auditors ask for samples of shipments with full document trails. Control owners write cycle memos describing how classification is approved, who can release a blocked order and how duty postings are reconciled to broker statements. When findings come back, the adjustment is usually to master data or to a missing approval step.

Questions to ask the people who run it

The documented flow and the daily practice drift apart quickly here. Ask the shipping clerks and the trade team directly.

• When the system prints a document with a wrong value, who fixes it, and is the fix made in the system or on the paper?
• Which documents are still edited by hand before they go to the broker or the bank?
• Who decides a new product's tariff code, and what happens to orders placed before it is set?
• How do blocked orders from screening get released, and is the release recorded anywhere?
• Where do signed proofs of export end up, and could a specific one be found on request?
• Does the broker's entry data ever disagree with what the ERP sent, and who notices?
• How are letter of credit terms passed to the people preparing the document set?
• Which customers or countries have special handling that nobody wrote down?

The answers to the hand edits question usually reveal where master data is weakest.

Where changes tend to break things

Changing the order or delivery structure can silently stop outputs from firing, because output rules key off document types and shipping points. Test each lane, not just the main one.

Moving classification data into a new module needs a cutover plan for open orders. Otherwise shipments in flight pick up blank or stale codes.

Broker interfaces are often older than anything around them. Field mappings were tuned over years, and the logic behind them may exist only in the head of one integration analyst. Find that person early.

Finally, check how duty and tax postings flow into inventory valuation and the general ledger. A process change on the trade side can shift landed cost without anyone in finance seeing it until the period closes.

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.