Post-shipment file review checklist: 8 data groups businesses should reconcile

CUSTOMS PROCEDURES

Post-shipment file review checklist: 8 data groups businesses should reconcile

Customs clearance and warehouse delivery do not automatically mean that a shipment file is closed. Customs, commercial, transport, warehouse, payment and cost documents are issued by different parties at different times. Without a final reconciliation, a minor inconsistency may later develop into a supplementary declaration, post-clearance audit issue, tax reconciliation problem, freight dispute or customer claim. This guide provides a structured post-shipment review process to identify missing documents, inconsistent data, accountable owners and the conditions required to formally close a shipment file.

Prepared by: TGIMEXUpdated: 20 July 2026Scope: B2B logistics and post-clearance compliance

QUICK FACTS

One shipment – one master file

Keep all records under the same shipment ID or customs declaration number instead of scattering them across personal inboxes.

Close all three layers

A shipment should be marked complete only after customs, operational delivery and finance/accounting layers are closed.

Reconcile data, not merely file counts

Product, quantity, value, HS code, origin, Incoterms, container details and tax must be logically consistent.

Every discrepancy needs a conclusion

Classify each issue as a presentation error, missing evidence, declaration error, cost variance or claim requiring escalation.

SCOPE OF APPLICATION

This framework is suitable for commercial imports and exports by sea, air, road or rail after customs clearance, final delivery or receipt of sufficient final data to close logistics costs.

Export processing enterprises, processing trade, export production, temporary import/re-export, duty-exempt projects, highly regulated products or shipments under claim require additional records such as inventory ledgers, norms, reconciliation reports, permits and case-specific evidence.

Limitation: This is an internal control framework. Whether a supplementary declaration, additional tax payment, explanation or another customs procedure is required depends on the actual file and the rules in force.

KEY TERMS

Term Meaning Role in file closure
Shipment file The complete set of customs, commercial, transport, delivery and financial records for one shipment. The central evidence package for audits, reconciliation and disputes.
Audit trail A trace showing who created, changed, approved and used a record or data point. Supports the basis of a declaration and the handling of later discrepancies.
Post-clearance compliance Obligations after customs clearance, including record retention, declaration review, tax and explanation capability. Confirms that the declarant’s responsibility does not end at clearance.
POD Proof of Delivery. Confirms delivery location, time and recorded condition.
EIR Equipment Interchange Receipt. Evidence of container/equipment pick-up, return and condition for demurrage, detention or repair review.
Landed Cost The total cost of bringing goods to the destination or point of use. Connects goods value, duty, freight, insurance, local charges and inland costs.

HOW THE CONTROL MECHANISM WORKS

A shipment file is complete only when it can answer four questions without gaps: what was bought or sold; how it was declared to Customs; how the goods were transported and delivered; and how payments, costs and taxes were recorded.

Three layers must close together

1. Customs layer

Declaration, supporting documents, channel result, physical inspection, taxes, permits, specialized inspection and amendments or supplementary declarations.

2. Operational layer

Booking, bill of lading, manifest, delivery order, port-to-warehouse delivery, POD, EIR, empty return, shortage, damage and equipment time charges.

3. Financial layer

Commercial invoice, payment evidence, paid taxes, logistics invoices, accounts payable/receivable, credit notes and cost allocation.

Final data normally stabilizes only after delivery, issuance of final transport documents, service invoices and accounting entries. A post-shipment review should therefore be an independent control point, rather than a self-certification by the same person who prepared the declaration.

SHIPMENT FILE CLOSURE MATRIX

Review group Objective Key data to reconcile Expected output Typical owner
01 Shipment identity Prevent mixing records from different shipments or declarations. Shipment ID, PO/contract, invoice, declaration, transport document and container. Shipment cover sheet or index. Logistics/Trade compliance.
02 Commercial Evidence of the transaction and sales terms. Seller/buyer, product, quantity, unit price, currency and Incoterms. Consistent contract–PO–invoice–packing list set. Purchasing/Sales.
03 Customs and tax Support declaration basis and tax obligations. Procedure code, HS code, customs value, origin, rates, tax and permits. Final declaration and supporting rationale. Customs/Tax accounting.
04 Transport Evidence of route, conveyance and cargo unit. B/L or AWB, voyage/flight, container, seal, weight and ports. Final transport document, arrival notice and release/D/O. Logistics/Forwarder.
05 Delivery and warehouse Confirm actual receipt, delivery and equipment status. Packages, weight, delivery date, truck, container, seal and variances. POD, warehouse receipt/issue, EIR and incident report. Warehouse/Trucking/Logistics.
06 Cost and payment Close liabilities and landed cost under the correct scope. Duty, freight, surcharges, exchange rate, VAT, pass-through charges and credit notes. Cost reconciliation and complete invoice/payment file. Finance/Logistics.
07 Exceptions and claims Ensure no unresolved issue is hidden by “delivery complete”. Shortage, damage, delay, DEM/DET, reassessment, penalties and claims. Survey report, reservation notice, claim file or final decision. Logistics/Legal/Insurance.
08 Retention and retrieval Keep the file readable and retrievable throughout the retention period. File name, version, date, approver, format and storage location. Locked, access-controlled and backed-up folder. File owner/IT/Finance.

DOCUMENTS AND DATA TO REVIEW

The table can be used as an internal review sheet. Businesses should add three control fields in their own system: result, reviewer and completion date.

Review point What to reconcile Pass condition Action for a discrepancy
☐ File identity Shipment ID, PO/contract, invoice, declaration and transport document belong to one shipment. A single index and consistent naming rule exist. Separate mixed records and create a document-number mapping table.
☐ Transaction parties Names, addresses and tax IDs of buyer, seller, exporter, importer and authorized representative. Any difference is supported by contract, authorization or transaction structure. Do not silently alter issued records; request correction or written explanation from the issuer.
☐ Product and specification Description across contract, invoice, packing list, technical records, permits and declaration. The same goods can be identified and the description supports classification. Assess possible impact on HS code, product policy, tax and labeling.
☐ Quantity and units Packages, pieces, net/gross weight, commercial units and declared units. Conversions are supported by a formula and source evidence. Record the variance and distinguish document error, shortage/overage and declaration error.
☐ Value and currency Unit price, total, discounts, Incoterms, freight, insurance and adjustments. Customs value logic can be traced to contracts, invoices and cost evidence. Review tax impact and whether a supplementary declaration is required.
☐ HS code and tax Classification, declared description, duty rate, import duty, VAT and other applicable taxes. Technical documents, catalogue, composition/use or analysis support the position. Document the assessment and obtain specialist advice where needed.
☐ Origin and C/O Declared origin, origin criterion, C/O number/date, invoice, transport and preference conditions. Core data is consistent and the certificate remains readable and verifiable. Distinguish formal defects from defects affecting preference and tax treatment.
☐ Permits and specialized control Permit, inspection registration/result, exemption, declaration or certificate. Correct entity, product, quantity, validity and permitted shipment/use. Keep the file open until the final document or authority conclusion is obtained.
☐ Transport document and manifest Shipper, consignee, notify party, packages, weight, ports, voyage/flight, container and seal. The final version matches customs data and actual delivery. Retain amendment history and identify the final effective version.
☐ Delivery and warehouse POD, handover, weighbridge record, warehouse receipt/issue, seal photo and incident report. Actual receipt is reconciled to packing list and declaration. Open an exception file, preserve evidence and notify relevant parties under the contract.
☐ Container/equipment Pick-up/return EIR, timestamps, condition, container, seal and free time. Empty return and the final DEM/DET/repair position are evidenced. Do not close while estimated charges, date disputes or damage claims remain open.
☐ Duty and fees Payment record, tax debt status, adjustments and refund/non-collection where applicable. System and ledger amounts match the final declaration. Reconcile with bank, payment portal and Customs where necessary.
☐ Logistics invoices International freight, local charges, trucking, handling, storage, inspection support, pass-through charges and VAT. Correct legal entity, scope, shipment and service acceptance evidence. Request debit/credit note or invoice correction before final cost closure.
☐ Payment and balances Bank evidence, offsets, deposits, installments, bank fees and exchange differences. Balances match contract, invoice and vendor/customer sub-ledger. Flag unresolved amounts and avoid arbitrary allocation to another shipment.
☐ Version and approval Drafts, amendments, final versions, confirmation emails and approvers. One final version is clearly identified and material history is preserved. Restore the audit trail; do not delete a prior version that supported an earlier decision.
☐ Retrieval Files open correctly, scans are complete, naming is searchable, access is controlled and backups exist. The complete file can be retrieved by declaration or shipment ID within a reasonable period. Recover files, rescan, standardize formats and hand over to the designated records owner.

REVIEW AND CLOSURE PROCESS

Define the file scopeConfirm shipment ID, declaration, procedure, transport mode, contract/PO and involved parties. The output is a document list tailored to the shipment type.
Collect final recordsObtain final versions from customs, purchasing/sales, forwarder, carrier, warehouse, trucking and finance. Do not treat a nearly-final email attachment as an officially issued record.
Index records and lock versionsUse a consistent naming rule, for example year-month_shipment_document-number_version. Mark the final version while retaining material amendment history.
Reconcile key data fieldsCompare parties, goods, quantity, value, HS, origin, transport, delivery, duty and cost. A document count is not a substantive review.
Classify discrepanciesSeparate missing evidence, explainable differences, document errors, declaration errors affecting policy/tax, operational or financial variances and claims.
Resolve and retain the conclusionAssign an owner, action, supporting evidence and final status to each issue. Potential declaration errors must be assessed under the supplementary declaration rules applicable at that time.
Approve closure and retainThe file owner and relevant functions confirm that customs, operations and finance are closed. Lock, access-control, back up and assign retention periods.
Internal SLA: There is no single statutory deadline for completing an enterprise’s entire post-shipment internal review. Set an internal deadline based on receipt of final records and shipment risk.

RISKS AND COMMON ERRORS

Error Typical cause Impact Control
Keeping only the declaration and invoice Confusing the customs declaration with the complete shipment file. Weak evidence for HS, origin, value or delivery. Use a shipment-type document matrix.
Using a draft version No version control for invoice, packing list or transport document. Internal data differs from the document used for declaration. Use Draft/Issued/Final/Cancelled status and controlled approval.
Unresolved quantity variance Warehouse, trucking and trade teams use separate records. Inventory error, late claim or customs discrepancy. Create a variance report linked to the shipment ID.
Costs assigned to the wrong shipment Late or consolidated service invoices. Incorrect landed cost, balances and value analysis. Put the shipment ID on service orders, debit notes, invoices and entries.
Records held only by the forwarder No service close-out deliverable. Loss of retrieval capability when vendor or staff changes. Require a closing dossier and retain the enterprise’s own copy.
Deleting old emails and versions A “clean folder” is prioritized over audit trail. Loss of evidence explaining the declaration basis at the relevant time. Separate final documents while preserving material communication history.
Closing while a claim is open No conditional-closure or open-exception status. Missed claim deadlines and unrecovered costs. Separate delivery completion from unresolved exception closure.

LEGAL BASIS AND OFFICIAL SOURCES

Instrument/source Relevant content Use in this guide
Vietnam Customs Law, consolidated in Document 54/VBHN-VPQH dated 23 March 2026 Declarant obligations, customs dossier and post-clearance audit. Customs records for cleared goods must generally be retained for five years from declaration registration, unless otherwise provided by law. Basis for post-clearance retention and production of records upon request.
Circular 38/2015/TT-BTC, as amended Customs records, data and procedures for imports and exports. Identifies documents by procedure and shipment circumstances.
Circular 39/2018/TT-BTC Amends major provisions of Circular 38, including customs dossiers and customs value review. Must be read together with the original Circular 38.
Circular 121/2025/TT-BTC, effective 1 February 2026 Further amendments to customs procedures, supervision and tax administration for imports and exports. Use for procedures and records arising on or after 1 February 2026, subject to any applicable transitional provisions.
Decree 174/2016/ND-CP Accounting records may require minimum retention of five or ten years depending on record type and use; it also addresses electronic records. Separates customs-file retention from accounting and tax record retention.
Validity note: Circular 38/2015/TT-BTC and Circular 39/2018/TT-BTC are both partially expired. Apply only their provisions still in force together with Circular 121/2025/TT-BTC and other relevant amendments.
Translation note: English descriptions are for operational reference only and are not official legal translations.

FAQ

1. Is another review needed after clearance and full delivery?

Yes. Clearance confirms completion of customs formalities at that point, but responsibility for declaration accuracy, record retention, tax and explanation capability continues.

2. Are scanned copies sufficient?

It depends on the document and its legally valid form. Electronic records must remain complete, accessible and traceable to their source and time. Paper originals or records required for submission/presentation must be managed under the applicable rules.

3. Should a shipment file be retained for five or ten years?

Customs records generally follow the five-year period from declaration registration under the Customs Law. Accounting records may require five or ten years depending on type. Where one record falls under multiple regimes, apply the longer period and retain it while a case remains unresolved.

4. Who should approve file closure?

Assign one owner in trade compliance/logistics, with confirmations from purchasing/sales, warehouse, finance and legal or product compliance where relevant. Avoid a control design in which one person creates and approves all data without review.

5. Must every minor difference trigger a supplementary declaration?

No conclusion can be based on the word “minor”. Determine which record is incorrect, whether the declaration, product policy, HS code, origin, value or tax changes, and the current status of any customs review.

6. If the forwarder keeps the documents, must the importer/exporter keep another set?

Yes. The enterprise/declarant remains responsible for its records. Service contracts should specify the closing dossier, file format, delivery time and retrieval support.

7. Should folders be organized by date, customer or declaration?

A multi-level structure is useful, but use one unique retrieval key—normally year plus shipment ID and declaration number—so the file can be found from customer, customs and accounting perspectives.

APPLICATION NOTE: The required records vary by customs procedure, Incoterms, product control, payment method and service contract. Potential errors involving HS code, origin, value, quantity, permit or tax should be assessed from original evidence. Do not make internal data “match” by overwriting records without preserving the source and audit trail.
QUICK CONSULTATION

NEED TO REVIEW IMPORT PROCEDURES OR A SHIPPING PLAN?

Send us the product name, shipping route, current dossier, or implementation request in advance so we can suggest a suitable approach that is practical, focused, and aligned with your shipment.

CALL NOW
Zalo
HOTLINE 0963 856 664 / 0982 135 393
EMAIL info@tgimex.com
SUITABLE FOR International shipping · Customs procedures · Import licenses · B2B logistics

Leave a Reply

Discover more from TGIMEX VIETNAM JSC

Subscribe now to keep reading and get access to the full archive.

Continue reading