What Is a Cargo Manifest? Its Role in the Import Cargo Release Process
An import shipment may have a bill of lading, an Arrival Notice and a vessel arrival, yet still be delayed when manifest data do not match. A wrong bill number, consignee name, container, package count or gross weight can disrupt customs declaration, delivery-order reconciliation and terminal supervision. A manifest is neither a bill of lading nor a delivery order. It is the cargo and transport data submitted electronically by the carrier, agent or freight forwarder to the relevant authorities under the applicable rules. This article explains master and house manifests, their relationship with MBLs and HBLs, their role in customs risk assessment and cargo pickup, the data importers should check, the amendment workflow and the errors that commonly create storage, amendment or delay costs.
QUICK FACTS
SCOPE
This article focuses on import cargo manifests, particularly ocean shipments with MBL/HBL structures, containers and Vietnam National Single Window procedures. The control logic is also relevant to air cargo, although datasets, names, deadlines and systems differ.
It is not a filing manual for a specific voyage. For an error, the importer must work with the party that transmitted the data and its Vietnam destination agent.
KEY TERMS
| Term | Meaning | Operational role |
|---|---|---|
| Cargo Manifest | Cargo and bill data declared for the means of transport. | Pre-arrival information, risk management, supervision and cargo identification. |
| Master Manifest | Carrier/agent data based on the MBL and voyage. | Represents the master transport layer. |
| Secondary bill data / house manifest | Data filed by an authorized party for each HBL under the related MBL; operationally this is often called a house manifest. | Identifies each underlying shipment in a consolidation. |
| MBL | Master bill issued by the carrier. | Primary source for master manifest data. |
| HBL | House bill issued by an NVOCC/forwarder. | Primary source for house-manifest and HBL-level pickup data. |
| Arrival Notice | Destination notification of cargo arrival and operational details. | Not a manifest and not proof that the filing is correct. |
| Delivery Order | Commercial release instruction issued at the carrier/forwarder layer. | Supports physical delivery after conditions are met; not the manifest. |
| E-Manifest | Electronic submission and processing of manifest data. | Creates standardized data for authorities and port systems. |
HOW IT WORKS
1. The manifest is the shipment’s regulatory data map
It links the voyage, ports, bills, parties, packages, gross weight, containers, seals and cargo descriptions. Authorities use the information before or upon arrival for identification, risk assessment and supervision.
2. Consolidation creates two layers
The carrier or agent files the MBL-level master manifest. When multiple HBLs sit under one MBL, the NVOCC/forwarder files each house bill. A master filing alone may therefore be insufficient for an importer whose release is organized by HBL.
3. It does not replace the transport or release documents
Bill-of-lading release conditions, originals/surrender status, fees and the carrier’s or forwarder’s D/O process remain separate. The customs declaration is also a separate filing that must reference the correct arrival data.
4. Its role spans the pickup workflow
- Supports customs risk assessment and cargo identification.
- Provides bill and cargo keys for the importer’s customs declaration.
- Supports terminal/warehouse supervision and container/package reconciliation.
- Must be amended by the filer or another system-authorized party when incorrect.
DOCUMENT COMPARISON
| Document/data | Prepared/issued by | Primary purpose | Direct cargo release? | Common confusion |
|---|---|---|---|---|
| Manifest | Carrier/agent/forwarder as filer | Regulatory declaration of voyage, bills and cargo. | No. It is background data for controls. | Confused with B/L or an internal packing list. |
| Bill of Lading | Carrier or NVOCC/forwarder | Transport document and evidence of contractual terms; functions vary by B/L. | Part of the release chain; a D/O is commonly still required. | Using MBL instead of HBL or vice versa. |
| Arrival Notice | Destination carrier/forwarder | Arrival schedule, location and estimated charges. | No. | Assuming it proves the manifest is correct. |
| Delivery Order | Carrier/agent/forwarder | Authorizes terminal/warehouse delivery subject to release conditions. | Yes, together with customs and supervision clearance. | Master and house D/O layers may both matter. |
| Customs Declaration | Importer/customs broker | Declares imported goods for customs procedures. | A key legal condition for release from customs supervision. | A manifest does not replace the declaration. |
DATA TO CHECK
| Data | Source | Why it matters | Typical error |
|---|---|---|---|
| MBL/HBL number | B/L, Arrival Notice, D/O draft | Primary system link. | Missing prefix, character error or wrong bill layer. |
| Shipper/Consignee/Notify | B/L and contract | Identifies shipment parties. | Legal name/address or tax ID mismatch. |
| Vessel/Voyage, POL/POD | Booking, B/L, Arrival Notice | Links cargo to the correct arrival. | Wrong voyage, transshipment port or terminal. |
| Container/Seal | B/L, packing list, EIR | Used for supervision and physical delivery. | One-character error or unreported seal/container change. |
| Packages/type | Packing List and bills | Reconciles cargo quantity and handling units. | Carton/pallet/package mismatch or house totals not reconciling to master. |
| Gross weight | Packing List and B/L; VGM is only a separate reasonableness check for total packed-container mass | Supports cargo identification and reconciliation; cargo gross weight is not the same as VGM because VGM also includes container tare. | Net/gross or kg/ton error. |
| Cargo description | Invoice, packing list, B/L | Identifies cargo and supports risk assessment. | Overly generic or inconsistent description. |
| DG/reefer remarks | DG declaration, booking and B/L | Controls special cargo attributes. | Missing UN/class, temperature or special requirement. |
IMPORT PICKUP PROCESS
- Receive the pre-alert: collect MBL, HBL, invoice, packing list and ETA.
- Identify the filer: carrier/agent for master; NVOCC/forwarder for house.
- Reconcile before arrival: bill number, consignee, container, seal, packages, weight and description.
- Raise discrepancies immediately: state the incorrect field, correct data and evidence.
- Obtain amendment confirmation: distinguish “request received” from “system filing updated/accepted.”
- Process Arrival Notice and D/O: confirm master/house release conditions, fees and pickup location.
- File customs entry: use the correct arrival bill information and resolve mismatches before dispatch.
- Complete supervision release: match container, seal, package count, terminal and statuses.
- Archive evidence: bills, amendment request/confirmation, D/O, customs entry and handover records.
COMMON RISKS
| Error | Cause | Impact | Control |
|---|---|---|---|
| Missing house manifest | Forwarder checked only the MBL or omitted an HBL. | HBL cannot be found or matched. | Maintain an MBL–HBL map and confirm each HBL status. |
| Wrong consignee | Old draft or trade name used instead of legal entity. | Release and party-identification issues. | Lock legal entity data before manifest cut-off. |
| MBL/HBL confusion in customs entry | Consolidation structure not understood. | Arrival data mismatch. | Mark master/house clearly in pre-alert and SOP. |
| Container/seal mismatch | Equipment or seal changed without synchronized updates. | Supervision hold or terminal verification. | Reconcile EIR, final B/L, manifest and packing list. |
| Late amendment | Review starts only after arrival or customs error. | Delay, storage and commercial amendment fees. | Review pre-alert before ETA with an internal deadline. |
| Calling amendment fee a customs penalty | Service fees and legal sanctions are mixed. | Cost disputes and wrong responsibility allocation. | Separate carrier/forwarder charges from legal enforcement. |
| Relying only on Arrival Notice | Assuming arrival notice equals correct manifest. | Error found only during customs or gate-out. | Check the critical data set against the B/L. |
LEGAL BASIS AND SOURCES
Sources reviewed on 21 July 2026. Filing and amendment requirements vary by mode, transport document, current regulation and system guidance.
| Source | Role | Application note |
|---|---|---|
| Decree 08/2015/ND-CP | Core customs procedure, inspection and supervision framework. | Read with amendments. |
| Decree 59/2018/ND-CP and Decree 167/2025/ND-CP | Amend Decree 08/2015. | Decree 167/2025 effective 15 August 2025. |
| Circular 38/2015/TT-BTC, Circular 39/2018/TT-BTC and Circular 121/2025/TT-BTC | Operational customs procedures and supervision; Circular 121/2025/TT-BTC has applied since 1 February 2026. | Circulars 38/2015 and 39/2018 are partially no longer effective; apply their remaining provisions together with current amendments. |
| Vietnam National Single Window manifest data notice | Illustrates standardized container and house-bill data requirements. | Use current system instructions. |
| IMO FAL Declarations and Certificates | Identifies Cargo Declaration as FAL 2 and electronic reporting. | International standard; national implementation controls the procedure. |
| IMO FAL Convention | International framework for ship reporting and single window. | Electronic exchange and maritime single-window requirements are current under FAL. |
FAQ
1. Is a manifest the same as a Packing List?
No. A Packing List is prepared by the seller/shipper; a manifest is regulatory transport data filed by the carrier or forwarder.
2. Can the importer amend the manifest directly?
Normally no. The request goes to the carrier, agent or forwarder that filed it.
3. Which bill number should be used when an HBL exists?
Confirm the master/house structure and current customs-entry instruction. Do not substitute the MBL for the HBL without a valid basis.
4. Does a correct manifest mean cargo can be picked up immediately?
No. B/L release, D/O, customs, charges and terminal supervision must still be completed.
5. Does every amendment create a customs penalty?
No general conclusion is possible. Commercial amendment fees may apply; administrative sanctions arise only in legally defined cases.
6. Why can MBL and HBL package presentation differ?
Packaging levels and consolidation can differ, but the master–house relationship must reconcile and comply with the system dataset.
7. When should manifest data be checked?
At draft/final B/L and pre-alert stage, before ETA and before customs filing.
Tiếng Việt
中文 (中国)
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.
When should businesses photograph or video container stuffing and opening?
When Can Cargo Insurers Reject or Reduce a Claim?
Risks of Failing to Inspect a Container Before Cargo Stuffing
Risks of Failing to Inspect a Container Before Cargo Stuffing
What Documents Are Required for a Cargo Insurance Claim?
What Information Should a Cargo Damage Survey Record Contain?
Total Loss vs Partial Loss in Cargo Insurance: What Is the Difference?
Cargo Dented, Wet or Missing Packages: What Should a Business Do?
Who Must Arrange Insurance under CIF and CIP?
Export Process: From Purchase Order to Final Document Set
How Is Cargo Insurance Value Determined?
How Do ICC-A, ICC-B and ICC-C Cargo Insurance Conditions Differ?
When Should a Business Buy Separate Cargo Insurance?
Can Carrier Liability Replace Cargo Insurance?
Forwarder, Carrier, NVOCC and Customs Broker: What Is the Difference?