Differences in quantity, weight or package count are often treated as minor clerical issues, yet they can cause the declaration to conflict with the commercial invoice, packing list, transport document, cargo manifest, licence or the physical goods. The difficulty is that the three data sets describe different things: quantity identifies the goods and their unit of measure; weight describes mass, normally distinguishing gross and net weight; package count describes the outer transport packages. Declaring cartons as product quantity, entering net weight as gross weight, or converting PCS–SET–KG without evidence may distort unit value, tax, inspection and customs-supervision data. This article provides a pre-filing reconciliation process for machinery, components and consumer goods packed in cartons or pallets.

Updated: 20 July 2026 | Primary scope: machinery, components and consumer goods packed in cartons/pallets

QUICK FACTS

Three different data concepts

Quantity describes goods; packages describe transport packing; weight describes mass.

Lock the UOM first

PCS, SET, KG, MTR and supplementary units require an item/HS mapping.

Gross is not net

Gross includes goods and packaging; net excludes transport packaging.

Do not double-count packages

Pallets and inner cartons are not both added when the manifest only declares pallets.

Stop filing when unreconciled

Differences among PL, B/L/AWB, manifest, scale record and physical cargo must be closed first.

Illustration for How to Review Quantity, Weight and Package Count Before a Customs Declaration — Illustration of the logistics topic, document or operation discussed in the article.

SCOPE OF APPLICATION

This article covers commercial imports and exports of machinery, components, spare parts and consumer goods packed in cartons, pallets, crates or similar units, including FCL, LCL, air cargo and road shipments.

It should not be applied mechanically to bulk cargo, liquids, gas, draft-survey cargo, live animals or goods subject to specific metrology rules. Those require the relevant weighing, measurement, survey or specialised-control documents.

TERMS AND DEFINITIONS

Term	Meaning	Operational role
Commercial quantity	Quantity stated in the invoice/PO, e.g. PCS, SET, ROLL or MTR.	Payment and line-by-line reconciliation.
Customs quantity	Quantity and unit required by the applicable customs/tariff data field.	Statistics, tax and regulatory control.
Package count	Number of outer shipping packages such as cartons, pallets, crates or drums.	Reconciliation with B/L, AWB, manifest and terminal/CFS records.
Gross Weight – G.W.	Weight of the goods plus transport packaging.	Normally the shipment-level weight used in transport and declaration data.
Net Weight – N.W.	Weight of the goods excluding transport packaging.	Packing list, product content, certain licences/C/O and allocation.
Tare Weight	Weight of pallets, crates, cartons and dunnage.	Logic check between gross and net weight.
UOM	Unit of Measure.	Controls PCS/SET/KG/MTR conversion and unit value.

OPERATING MECHANISM

The three data groups originate from different processes. Quantity comes from the transaction and item identity; package count comes from packing and transport data; weight comes from the goods, packaging and weighing. The control objective is therefore not to make the figures equal, but to demonstrate the relationship among them.

At declaration-line level, quantity must match the model, HS classification and UOM. At shipment level, package count and gross weight must reconcile with the final B/L/AWB or accepted manifest data. The packing list is the bridge, showing contents per package, N.W./G.W. and pallet/crate consolidation.

FILING PRINCIPLE: Each line quantity must use the UOM applicable to the declaration field and HS line. Where the invoice UOM differs, keep a documented conversion; never convert PCS–SET–KG merely to make documents appear equal.

STOP POINT: Do not transmit when the file cannot explain units per package, the outer package declared in the manifest, or the gross-to-net difference.

Data group	Priority source	Scope	Control point
Line-item quantity	Invoice, PO, contract, warehouse issue record, model list.	Per SKU/HS line; primary and supplementary units may apply.	File in the UOM applicable to the HS line. Where the invoice uses another UOM, retain an evidenced conversion; use a supplementary unit only when the field or tariff requires it.
Total gross weight	Packing list, weighing record, B/L/AWB or equivalent transport document.	Shipment or transport-document level, matching the scope of the transport record.	Reconcile gross weight at shipment/B/L level; do not invent line-level gross weights where the declaration form has no such field.
Net weight	Detailed packing list, production weight record, technical data.	Per SKU/package when available; not a universal total field for every declaration.	Net must not exceed gross for the same cargo scope and weighing time; the difference must trace to pallets, packaging or dunnage.
Package count	Final packing list and B/L/AWB/manifest.	Outer-package unit determined by field instructions and final transport data.	Do not add pallets and inner cartons together; record package type and count at the correct data layer.
Packing configuration	Packing instruction, marks & numbers and loading photographs.	Connects quantity, packages and weight.	Can explain units per package and packages per shipment.

DATA-SOURCE PRIORITY

Do not select the figure that appears most often. Trace each difference to its source and confirm which document is final.

Source	Evidence value	How to use
Physical goods/controlled weighing record	Physical evidence at factory, warehouse, CFS or handover.	Priority when a discrepancy is found; identify time, scope and weighing equipment.
Final packing list	Quantity per package, N.W./G.W., dimensions and marks.	Primary reconciliation document; do not use an obsolete draft.
B/L, AWB and manifest data	Package count/type, transport gross weight, document/container numbers.	Controls supervision data; amendment must be completed separately.
Commercial invoice/PO	Commercial line quantity, UOM and unit price.	Does not necessarily show package count or gross weight.
ERP/internal warehouse data	Item code, UOM conversion, lot/serial.	Use only after mapping to confirmed commercial documents.
Uncontrolled email/chat	Temporary information.	Not a final source until formalised in a confirmed document or data sheet.

INTEGRATED RECONCILIATION EXAMPLE

The figures below differ but remain logically consistent through the packing configuration. This is an operational illustration, not a fixed declaration template.

Data source	Goods quantity	Detailed packing	Outer package	Net Weight	Gross Weight
Physical cargo	1,000 component sets	100 cartons × 10 sets	2 pallets	1,200 kg	1,320 kg
Invoice	1,000 SET	Not required	Not required	Not required	Not required
Packing List	1,000 SET	100 CTNS	2 PLTS	1,200 kg	1,320 kg
B/L/Manifest	May only describe cargo	May omit inner cartons	2 PALLETS	—	1,320 KGS
Draft declaration	1,000 SET by line	Detail/remark where relevant	2 PLTS if transport data is declared that way	For internal control or licence reconciliation where needed	1,320 KGM in the applicable total-weight field; no line allocation unless specifically required

Control logic: 100 cartons × 10 sets = 1,000 sets; 2 pallets contain 100 cartons; 1,320 kg Gross − 1,200 kg Net = 120 kg of pallets/packaging/dunnage.

DOCUMENTS AND DATA TO CHECK

Document	Data required	Typical owner	Common error	Control action
Invoice/PO	Line quantity, UOM, price and model.	Purchasing/supplier.	PCS and SET mixed; free-of-charge line omitted.	Create item–UOM–HS mapping and reconcile quantity with value.
Packing List	Cartons/pallets/crates; units per package; N.W./G.W.; marks.	Shipper/packing warehouse.	Summary only; pallet and carton double-counted.	Require a package-level final version.
B/L/AWB/Manifest	Package count/type, gross weight, transport document/container.	Carrier/forwarder.	Draft used; amendment not updated in the system.	Confirm final document and acceptance of amendment.
Weighing/handover record	Actual weight, weighing time and scope.	Warehouse, CFS, carrier.	Unclear whether pallet is included; no irregularity report.	State gross/net, scope and responsible signatory.
Catalogue/BOM/UOM master	Set composition, pieces per set and unit weight.	Technical/ERP team.	Kits supplied loose; inconsistent conversion.	Approve conversion formula and retain calculation.
Licence/C/O/specialised file	Quantity, weight, quota/balance and UOM.	Compliance/supplier.	UOM differs from declaration; balance exceeded.	Match model, UOM, quantity and remaining balance before filing.

PRE-FILING REVIEW PROCESS

Step	Input	Action	Output
1. Freeze document versions	Invoice, packing list and draft/final B/L or AWB.	Mark version and approver; remove obsolete files.	One controlled source set.
2. Standardise item master	Model, expected HS, commercial and customs UOM.	Prepare PCS/SET/KG/MTR mapping.	Item master per declaration line.
3. Reconcile quantity	Invoice–PO–packing list–ERP.	Check every line, FOC items, accessories and serial/lot where relevant.	Quantity variance by SKU.
4. Reconcile packages	Packing list–B/L/AWB–manifest.	Identify outer versus inner packages and prevent double counting.	Locked package count/type.
5. Reconcile weight	Packing list–weighing record–transport document.	Check G.W., N.W., tare and weighing scope.	Evidence-based gross/net values.
6. Build reconciliation sheet	Reviewed quantity, package and weight data.	Connect quantity ↔ packages ↔ weight and separate official filing fields from internal analytics. Do not manufacture gross weight by HS line.	A reconciliation file showing source, formula and which values are actually transmitted.
7. Close discrepancies	Variance list.	Correct document/manifest or obtain confirmation; never average figures without basis.	Evidence of closure for each issue.
8. Independent approval	Draft declaration and reconciliation.	Second reviewer approves and freezes subsequent changes.	Data ready for transmission.

Four-eyes principle: the reconciliation preparer and declaration approver should be separate roles. Any post-approval change to PL, B/L/AWB or container data reopens the relevant review step.

RISKS AND COMMON ERRORS

Error	Cause	Impact	Control
Declaring cartons as product quantity	Quantity confused with package count.	Incorrect quantity, unit value, licence and physical inspection.	Use separate commercial quantity, customs quantity and package columns.
Entering net as gross	Wrong column selected from packing list.	Mismatch with transport/manifest and supervision data.	Cross-check G.W. against B/L/AWB and use correct weight UOM.
Double-counting pallet and cartons	PL shows 2 pallets/100 cartons while carrier declares 2 pallets.	Declaration shows 102 packages against 2 in manifest.	Use outer package from transport data; keep inner pack in detail.
PCS–SET conversion without BOM	Kit composition not controlled.	Incorrect HS quantity, licence use and inventory.	Approved BOM/UOM conversion.
Arbitrary gross-weight allocation	Assuming each HS line must carry gross weight even where only shipment total is required.	Creates unsupported data and weakens the audit trail during inspection.	Keep gross weight at shipment/B/L level. Analyse line weights only for internal, licensing or specialist-control needs using objective evidence; do not turn the allocation into a filing field unless required.
Ignoring small scale difference	Assumed to be harmless.	May conceal shortage, excess or damaged packaging.	Confirm identical weighing scope, time, UOM and scale accuracy. Document a non-filing variance; resolve any variance that changes the declaration, manifest or licence before transmission.
Packing list corrected but manifest unchanged	Only internal document was updated.	D/O, declaration and supervision still use old data.	Track amendment until carrier/agent confirms acceptance.

LEGAL BASIS AND SOURCES

Instrument/source	Authority	Status	Role
Customs Law No. 54/2014/QH13 and amendments	National Assembly	Effective 1 January 2015; Law 90/2025/QH15 amended selected provisions from 1 July 2025.	Completeness, accuracy and truthfulness of declarations and declarant responsibility.
Decree 08/2015/ND-CP as amended by Decree 167/2025/ND-CP	Government	Decree 167/2025 effective 15 August 2025.	Customs procedures, transport/manifest and supervision data.
Circular 38/2015/TT-BTC as amended by Circulars 39/2018 and 121/2025	Ministry of Finance	Circular 121/2025 effective 1 February 2026.	Articles 18–20 govern filing, registration and amendments. Appendix II covers Models 01/02 and Model 03, so declaration fields must be distinguished from invoice/transport data.
Current Appendix II	Ministry of Finance	Applied by flow, procedure type and system configuration.	Models 01/02 guide declaration data by import/export flow. Model 03 separately covers invoice and transport data; package count and gross weight are taken from the B/L or equivalent transport document.
Carrier/terminal transport rules	Carrier, port, warehouse/CFS	Route and system specific.	Package type, gross weight and amendment status; not a substitute for customs law.

Circular 121/2025/TT-BTC Decree 167/2025/ND-CP Circular 38/2015/TT-BTC

FAQ

The invoice states 1,000 PCS while the packing list states 100 cartons. Is that wrong?

No. They describe different data layers. The file must demonstrate 10 PCS per carton and 100 cartons = 1,000 PCS.

One pallet contains 50 cartons. Should package count be 1 or 50?

Check the specific field and the accepted transport data. Where the B/L/manifest records one pallet as the outer package, do not add 50 inner cartons to create 51 packages; keep the cartons in the packing-list or appropriate detail layer.

Must gross weight equal total net weight?

No. Gross includes packaging and pallets, so it normally exceeds net. The difference must be reasonable and traceable to packaging.

Can weight from the invoice be used?

Only where clearly stated and consistent with the final packing list and transport document. For shipment gross, prioritise final PL, weighing record and B/L/AWB.

Several HS lines share one B/L gross weight. What should be done?

Do not automatically allocate gross weight to each HS line. File the shipment/B/L gross weight in the applicable total field. Prepare line-level weight analytics only where a licence, specialist control, costing or internal system needs it, using actual or objective data and keeping the calculation separate from official fields.

Can a small weight difference be ignored?

There is no universal tolerance for every shipment. Check weighing scope, scale tolerance, moisture, packaging and transport data. A variance that does not change a filing field may be documented; one that changes the declaration, manifest or licence must be resolved before transmission.

After correcting the packing list, must the B/L/manifest be checked again?

Yes. A commercial-document correction does not automatically update transport data. Confirm that the amendment has been submitted and accepted.

APPLICATION NOTE: Specific data fields depend on import/export direction, procedure type, HS code, transport mode and system version. This is an operational control framework and does not replace the current Appendix II or a customs decision for a specific shipment. Vietnamese legal sources govern; this English version is not an official legal translation.

TGIMEX IMPLEMENTATION SUPPORT

TGIMEX helps businesses turn the article into a shipment-ready checklist, covering input-data review, dossier preparation, milestone control, and coordination with the relevant parties.

Convert guidance into checks

Assign an owner and deadline to every operational control point.

Reconcile shipment data

Compare booking, transport, commercial, customs, and delivery evidence.

Manage operational risk

Record discrepancies, actions, and decision evidence to prevent recurrence.

Discuss your shipment dossier

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE