WHAT IS A CARGO MANIFEST? HOW DO MANIFEST ERRORS AFFECT CARGO PICKUP?
“Manifest” is an operational umbrella term for data within a conveyance customs dossier. Vietnamese rules separately identify the cargo declaration and master/house bill information, filed or supplied by the carrier, authorised declarant or house-bill issuer under different sea and air mechanisms. A single error in the bill number, consignee, container, seal, package count, weight or port can cause the manifest to conflict with the B/L, import declaration, delivery order and terminal data. The result is not always a customs-clearance rejection, but the importer may be unable to retrieve the bill, obtain the D/O, complete system matching or move the cargo out of the customs-supervised area until the filing is corrected. This article explains the master–house structure, the fields that directly affect delivery and the correction workflow needed before storage costs escalate. Updated 20 July 2026.
QUICK FACTS
The carrier/agent/NVOCC files transport and cargo data; the importer or its authorised declarant registers the import customs declaration.
An accurate draft B/L is not enough. The master and house data must also be transmitted correctly.
They may affect bill retrieval, declaration preparation, D/O issuance, terminal matching and customs-supervision release.
Obtain confirmation that the filing party transmitted the amendment and that the system accepted it.
SCOPE
This article focuses on commercial imports by sea and air, including FCL, LCL, consolidated cargo and shipments using MBL/HBL or MAWB/HAWB. It is intended for importers, documentation teams, procurement, forwarders, NVOCCs and customs brokers.
- “Manifest” is not used here as a synonym for the importer’s customs declaration.
- Filing and amendment deadlines vary by transport mode, voyage, arrival status and applicable rules.
- Manifest or B/L amendment charges are commercial carrier/forwarder fees; there is no universal rate.
- Dangerous goods, scrap, controlled goods and physical discrepancies require additional regulatory review.
TERMS
| Term | Operational meaning | Role in cargo pickup | Key checks |
|---|---|---|---|
| Cargo Manifest Operational term | An umbrella term for advance cargo and bill data. Current rules treat the cargo declaration and master/house bill information as separate dossier components. | Identifies the shipment for risk management and matching with the customs declaration and storage operator. | Bill, parties, cargo, packages, weight and route; container/seal only where relevant to the mode and data set. |
| MBL / MAWB Master bill | Carrier- or airline-level transport document, often covering the carrier–NVOCC or direct shipper relationship. | Links the voyage/flight to the master shipment. | Carrier code, master number, voyage/flight and destination port/airport. |
| HBL / HAWB House bill | A secondary bill issued by an NVOCC or forwarder to the cargo owner in a consolidated shipment. | Identifies the actual consignee and individual shipment under the master. | Master–house link, consignee, package count and gross weight. |
| Manifest Amendment | The declarant submits corrected/supplemented data with explanatory evidence through the National Single Window. | Resolves discrepancies within mode-specific conditions; sea and air do not share one universal deadline. | Old/new values, declarant, submission time, receipt/processing response and commercial charges, if any. |
| D/O or eDO Delivery Order | Carrier/agent authority for the terminal, warehouse or CFS to deliver cargo to the entitled party. | Commercial delivery document; it does not replace customs clearance or supervision release. | Consignee, B/L, surrender/original status, fees and authorisation. |
HOW THE DATA FLOW WORKS
The manifest is a pre-arrival transport data layer, not one legally uniform document for every mode. Information normally starts from the Shipping Instruction, Invoice, Packing List and booking; it then appears on the draft B/L/AWB, is filed at master or house level and is received through the National Single Window. The importer later uses bill and transport data for its customs declaration, D/O and terminal procedures.
A PDF transport document can therefore be correct while the system manifest remains wrong or outdated. Conversely, correcting the manifest does not automatically amend an import declaration already registered. Each data layer must be corrected by the responsible party under the applicable process.
- Shipper freezes the Shipping Instruction: legal names, cargo, packages, weight, route and consignee.
- Carrier/NVOCC issues the draft bill: the importer reviews both master and house levels where applicable.
- House data follow mode-specific filing rules: for air cargo, the HAWB issuer supplies complete house data to the airline for filing; for sea cargo, if the vessel declarant lacks HBL data, it provides the vessel-dossier receipt number so the HBL issuer can file the house information through the National Single Window.
- Importer declares and obtains the D/O: bill, conveyance and location data must identify the stored cargo.
- Terminal and customs systems match the shipment: declaration, D/O, container/seal and supervision status must align before delivery.
| Mode | Inbound filing deadline | Amendment condition | House-data responsibility and system response |
|---|---|---|---|
| Air | Cargo declaration and master/house bill information: no later than 3 hours before ETA for flights longer than 3 hours; no later than 30 minutes before ETA for flights shorter than 3 hours. | Before customs procedures for the goods are completed and while the goods have not left customs supervision. | The HAWB issuer supplies house data to the airline for filing. The Single Window responds to a complete and valid amendment request within 30 minutes. |
| Sea | Cargo declaration, MBL/HBL and dangerous-goods declaration: no later than 12 hours before ETA for voyages under 5 days; no later than 24 hours for other voyages. | Before the cargo is removed from the customs-supervised area. | If the vessel declarant lacks HBL data, it provides the dossier receipt number to the HBL issuer for filing. The Single Window responds to a complete and valid amendment request within 1 hour. |
MANIFEST VS B/L, ARRIVAL NOTICE, CUSTOMS DECLARATION AND D/O
| Document/data | Issuer or declarant | Main purpose | Replaces manifest? | Impact if wrong |
|---|---|---|---|---|
| Manifest | Carrier, agent, airline or house-bill issuer within its responsibility | Declare conveyance, cargo and bill data to the authority | — | Shipment cannot be identified or matched correctly |
| B/L or AWB | Carrier/NVOCC/forwarder/airline | Transport document and evidence of receipt for carriage | No | Source data may require both document and manifest correction |
| Arrival Notice | Destination agent | Notify arrival, ETA, location and charges | No | Planning may be wrong; it does not amend customs data |
| Import customs declaration | Importer or authorised declarant | Declare goods, HS, customs value, tax and policy | No | Requires its own amendment/cancellation process |
| D/O or eDO | Carrier/agent/NVOCC | Authorise commercial release by terminal/warehouse | No | Cargo cannot be picked up even if customs clearance is completed |
HOW MANIFEST ERRORS AFFECT DELIVERY
| Incorrect field | Operational symptom | Potential impact | Priority | Post-correction confirmation |
|---|---|---|---|---|
| MBL/HBL or MAWB/HAWB number | Bill cannot be retrieved or master–house link fails | Declaration, D/O or system matching may be delayed | Very high | Bill number matches manifest, declaration, D/O and terminal |
| Consignee or notify party | The consignee is not the entitled legal receiver, or the notify party has incorrect contact data | A wrong consignee may stop the D/O or require endorsement/authorisation. A wrong notify party normally affects notices only, unless the contract/carrier system imposes an additional condition. | Very high for consignee; medium for notify | Separate entitlement from notification and confirm the legal consignee |
| Container or seal (containerised cargo, where declared) | Physical unit differs from transport, terminal or supervision data | Supervision exit may not be confirmed until reconciled; this should not be applied mechanically to air cargo or non-containerised shipments | Very high for containerised cargo | Container, seal and storage location align across relevant systems |
| Packages or gross weight | Manifest differs from packing or physical cargo | Explanation, amendment, inspection or discrepancy handling | High | Final data supported by evidence across the file |
| Cargo description | Description is vague or inconsistent with actual goods | Higher risk alerts, policy or dangerous-goods concerns | High | Specific commercial description consistent with declaration |
| Discharge port, CFS, voyage/flight | Shipment assigned to the wrong route or location | Wrong declaration office, warehouse or delivery planning | High | Correct conveyance, POD and location code |
| Master–house relationship | House data missing or attached to wrong master | Consolidated cargo cannot be split for the consignee | Very high | House accepted under the correct master |
A manifest error does not automatically mean that customs will reject or confiscate the cargo. The outcome depends on the field, timing, declaration status, storage location and supporting evidence. However, identity and supervision mismatches normally have to be resolved before final pickup.
DOCUMENTS AND DATA TO REVIEW
| Document/data | Source | Use | Fields to reconcile | Evidence to retain |
|---|---|---|---|---|
| Shipping Instruction and booking | Shipper/booking party/carrier | Before bill issuance and filing | Parties, route, cargo, packages and weight | Approved SI email and booking confirmation |
| Draft/final MBL/HBL or MAWB/HAWB | Carrier/NVOCC/forwarder/airline | Before and after filing cut-off | Bill number, master–house, parties and cargo | Approved draft, final and amendment history |
| Invoice and Packing List | Seller/exporter | Cargo reconciliation and customs declaration | Description, quantity, packages, gross/net weight | Final shipment versions |
| Arrival Notice and D/O/eDO | Destination agent | Delivery planning and release | Bill, consignee, ETA, location and container | Arrival notice, payment and D/O |
| Manifest amendment confirmation | Filing party/carrier/NVOCC | After error identification | Old/new values, bill, shipment and time | Reference, acceptance response and explanation |
| Customs declaration and supervision data | Importer/broker/customs system | Clearance and exit from supervision | Bill, conveyance, container, location and quantity | Declaration, clearance and supervision exit status |
CORRECTION WORKFLOW
- Identify the incorrect layer: manifest, B/L/AWB, Arrival Notice, D/O, customs declaration or terminal data.
- Stop the next transmission where possible: keep the bill/declaration in draft to avoid creating another inconsistency.
- Prepare an old–new schedule: list each field, correct value and supporting SI, Invoice, Packing List or shipper instruction.
- Send the request to the actual filer: carrier/agent for master; NVOCC/forwarder for house; airline/air agent for MAWB/HAWB.
- Track acceptance: retain the system reference or accepted status; “request received” is not proof of amendment.
- Review any registered customs declaration: handle its amendment or other procedure separately where affected.
- Recheck D/O and supervision: confirm bill, consignee, container/seal, location and cargo status before dispatching a truck.
- Close the audit file: retain pre/post amendment bills, charges, explanations and final system confirmation.
RESPONSIBILITY MATRIX
| Party | Main responsibility | Data controlled | Handover point | Risk if missed |
|---|---|---|---|---|
| Shipper/Seller | Provide accurate SI and commercial documents | Parties, cargo, packages, weight and route | Before SI cut-off | Error originates at source |
| Carrier/agent | Issue master bill and file carrier-level data | MBL/MAWB, conveyance, voyage/flight, container | Manifest filing and D/O | Master cannot be matched to cargo |
| NVOCC/Forwarder | Issue the house bill and handle house data under mode-specific rules: supply HAWB data to the airline or file sea HBL data using the vessel-dossier receipt where applicable | HBL/HAWB, consignee, master–house link | Pre-alert, filing and amendment | House missing or linked to the wrong master; consol cannot be split |
| Importer | Approve drafts and control legal entity data before ETA | Name/tax ID, bill and entitlement documents | Bill approval and declaration | Error found too late |
| Customs broker | Reconcile bill/manifest with declaration data | Bill, conveyance, location, container and quantity | Before official transmission | Declaration creates a second mismatch |
| Terminal/Warehouse/CFS | Hold and deliver cargo under valid status | Container, seal, bill, D/O and supervision status | Gate-out/delivery | Cargo cannot leave storage |
RISKS AND COMMON ERRORS
| Management error | Cause | Impact | Control |
|---|---|---|---|
| Reviewing only the final B/L | Assuming document accuracy proves system accuracy | Manifest remains wrong or house data is missing | Obtain filing confirmation/reference |
| Registering declaration before bill freeze | Schedule pressure while draft still changes | Wrong bill, conveyance, port or container | Use a document gate before transmission |
| Using abbreviated consignee name | Legal master data not controlled | D/O or entitlement problems | Use approved legal entity data |
| Ignoring master–house linkage | Only HBL received from forwarder | House attached to wrong master | Require pre-alert showing both bill levels |
| Dispatching truck before acceptance | Treating “request sent” as “system updated” | Truck waiting, storage or failed gate-out | Check final carrier/terminal/customs status |
| Amending manifest but not declaration | Teams work in silos | Data remain inconsistent | Maintain one shipment change log |
| No amendment record | Instructions handled by chat or phone | Difficult cost, liability and audit explanation | Retain old–new, email, reference and finals |
LEGAL BASIS AND OFFICIAL SOURCES
Vietnamese law uses the terms cargo declaration and bill-of-lading information. “Manifest” is the common operational term. Requirements must be checked for the relevant transport mode and current legal version.
| Source | Authority/effect | Relevant content | Application |
|---|---|---|---|
| Customs Law 54/2014/QH13, as amended by Law 90/2025/QH15 | National Assembly; Law 90 effective 1 Jul 2025 | General framework for declarations, records, supervision and responsibility for declared information. | General basis; it does not set the detailed manifest filing deadlines. |
| Decree 08/2015/ND-CP, directly amended by Decree 167/2025/ND-CP | Government | Framework for customs procedures concerning conveyances. Decree 59/2018/ND-CP was repealed by Decree 167 from 15 Aug 2025. | Do not cite Decree 59 as a standalone current basis. |
| Decree 167/2025/ND-CP | Government; effective 15 Aug 2025 | Articles 61 and 65 separately regulate air and sea dossiers, filing deadlines and amendment conditions; Articles 63 and 67 regulate filing responsibility, evidence and Single Window responses. | Current direct basis for both air and sea manifests. |
| Circular 50/2018/TT-BTC | Ministry of Finance; effective 5 Jun 2018 | Information indicators and declaration forms for conveyances at air, sea, rail, road and river borders. | Field-level manifest reference. |
| Circular 121/2025/TT-BTC | Ministry of Finance; effective 1 Feb 2026 | Amends cargo customs-declaration and supervision procedures. | Supplementary where a manifest error affects the import declaration or supervision; not the source of air/sea manifest deadlines. |
| Vietnam Customs – vessel procedure | Customs authority | Procedure, dossier and National Single Window method. | Operational reference at the time of filing. |
English translations in this article are for operational reference only and are not official legal translations.
FAQ
Does the importer file the manifest?
Normally, no. The carrier, agent or secondary-bill issuer files the data within its responsibility. The importer supplies and approves accurate data and files a separate import declaration.
If the B/L is amended, must the manifest also be amended?
Possibly yes. Once data have been filed, changing the B/L document does not automatically update the system. Confirm whether an amendment was required and accepted.
Will a package or weight discrepancy always prevent pickup?
Not always. The effect depends on the size of discrepancy, actual cargo, goods type and supervision status, but the data may still require explanation and reconciliation.
If customs clearance is completed, can cargo be picked up despite a manifest error?
Not necessarily. The D/O, terminal data, container/seal and customs-supervision exit must still be valid and aligned.
Who pays the manifest amendment fee?
It depends on who caused the error, the transport contract, booking terms and carrier/forwarder tariff. Separate B/L amendment, manifest amendment, re-issuance and storage costs.
Can the manifest be amended after arrival?
Yes, where the legal conditions remain open and supporting evidence is submitted. For inbound sea cargo, the cargo declaration and MBL/HBL must be amended before the cargo leaves customs supervision. For inbound air cargo, the cargo declaration and bill information must be amended before customs procedures for the goods are completed and while the goods remain inside the supervised area.
How early should the manifest be reviewed?
There is no universal internal deadline. Freeze the draft before the carrier cut-off and complete the pre-alert review early enough to allow amendment before arrival.
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.
Import procedure for cream-filled wafers: HS code, tax, food safety, C/O and E2E workflow
Gate Valve Export Guide: Markets, HS, Origin, Documents and Process
Industrial Router Export Guide: Markets, HS, Licensing, Origin and E2E Workflow
Exporting Butterfly Valves from Vietnam: Markets, HS 8481, Origin, Pressure Compliance and Transport
Laser Cutting Machine Export Procedure: HS, Dual-Use Screening, Origin and Shipping
Blade server export procedure: markets, HS, origin, dual-use screening and logistics
Exporting Gateways from Vietnam: Markets, HS 8517.62.21, Origin and Compliance
Mini PC export procedure: markets, HS, origin, dual-use, FCC/IMDA/OFCA and logistics
Exporting Industrial PCs from Vietnam: Markets, HS, Origin, Compliance and Transport
SERVER RACK EXPORT GUIDE: MARKETS, HS, ORIGIN, COMPLIANCE AND SHIPPING
Exporting Tower Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting PoE Switches from Vietnam: Markets, HS, Origin, Compliance and Transport
Desktop PC export guide: markets, HS code, origin and shipping
Exporting Edge Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting Load Balancers from Vietnam: Markets, HS, Origin, Compliance and E2E Workflow