Published 2026-04-18 · Hoobang Software
Import and export documents are the "passport" of foreign trade business. From inquiry to FX collection, every order is backed by a tightly interlocked set of documents. A single error or a mismatch between documents can mean delayed clearance and extra demurrage at best, or blocked FX collection and stalled tax rebates at worst. This article chains the core import/export documents in the order business actually happens, flagging the key validation point at each stage, to help merchandisers and document clerks prepare paperwork both quickly and accurately.
Around the moment a deal is confirmed, the first documents to appear are the Proforma Invoice (PI) and the Sales Contract (SC). The PI is the seller's formal statement of price and trading terms to the buyer — product description, quantity, unit price, Incoterms (FOB/CIF, etc.), payment terms and validity — often used by the buyer to apply for an import license or open a letter of credit. The SC is the legal record of both parties' rights and obligations. The product names, quantities, amounts and shipping marks on these two documents must stay consistent with every downstream document; they are the "source data" of the entire documentation chain. With a mature export business system, the PI and contract can be auto-populated from product records and quotes, eliminating inconsistencies at the source.
When goods are ready to ship, you prepare the Commercial Invoice (CI) and the Packing List (PL). The CI is the core document for settlement and customs valuation, and its amount must match the contract and the customs declaration; the PL details the piece count, gross/net weight, volume and marks of each carton, serving as the basis for the carrier's stowage, customs inspection and the buyer's receiving check. Common pitfalls include:
Generating these documents uniformly through the documentation business module ensures each field is entered once and reused across many documents, eliminating manual transcription errors at the root.
Once goods are handed to the carrier, the shipping line or forwarder issues the bill of lading (B/L), which is both a contract of carriage and a document of title. At the same time, an export customs declaration must be filed, with declaration data corresponding line by line to the invoice and packing list. If the buyer's country enjoys tariff preferences, a certificate of origin (C/O or various regional preferential CO) is also required. This stage involves many documents under tight timing; if shipping instructions (SI) and declaration data can be pushed automatically from the same order data, you can substantially compress document-preparation time and lower amendment costs.
After the goods ship and documents are submitted, the process moves to FX collection and tax rebate. Exporters use the customs declaration, invoice and other documents to handle FX write-off, and aggregate the VAT special invoices and customs declarations to file for export tax rebate. Tax-rebate filing demands extreme completeness and consistency of documents: the product code, quantity and amount on the customs declaration must cross-reconcile with the invoice and the FX receipt advice. Once sales, export, procurement and financial settlement are connected, tax-rebate data can be aggregated automatically and progress tracked, ensuring every eligible rebate is claimed without omission or error.
The core logic of import/export documentation comes down to one sentence: when the source data is consistent, downstream documents are naturally consistent. Manage everything from PI/SC/CI/PL through the bill of lading, customs declaration, certificate of origin and FX/tax-rebate materials on a single data foundation, so documents cross-validate and auto-populate — only then do both efficiency and accuracy rise together.
Enter document data once, reuse it across the whole chain — Hoobang Foreign Trade ERP keeps your paperwork error-free.