Does Your Invoice Describe Both the Packs and the Equipment?
Yes. A commercial invoice for a UN 3481 shipment has to describe the lithium-ion battery packs and the equipment they power as separate line items, carry the UN number and the packing instruction reference against the battery line, declare country of origin per line, and state a value that is consistent with the transport document travelling in the same document pouch. On a lithium battery load the invoice is the second dangerous goods document, and it gets read that way.
It is Thursday, twenty past four, and I am standing at a stainless packing bench in a cross-dock about forty minutes from the plant. On the bench: a printed air waybill on the left, a commercial invoice on the right, and a highlighter I have not picked up yet. Behind me the trailer is loaded and sealed and the driver is in the cab with the engine off. On my phone is a scanned form from the entry filer, standard language, asking us to describe the merchandise and clarify quantities.
Not a classification dispute. A description problem. Somebody is holding our paperwork and cannot tell what is inside the boxes.
This is the moment I want you standing in, because everything I know about commercial invoices I learned by standing in it.
I read left to right. Transport document first, always. The handling information box on the waybill reads clean: UN3481, lithium ion batteries contained in equipment, class 9, PI 967. Twelve pieces. Gross weight. Whoever built that declaration knew exactly what they were doing.
The invoice says one line. "Battery packs with chargers, 1 lot." A value. No UN number, no piece count that matches anything on the waybill, no origin. It does not contradict the waybill. It just says nothing, and nobody can clear a shipment described as one lot.
That is the whole failure mode. The invoice gets written by someone in order entry who is thinking about the purchase order. The declaration gets built by someone in shipping who is thinking about the packing instruction. Nobody puts the two pages side by side until a trailer is sitting still.
Both means both, on separate lines
A line for the equipment and a line for the battery. Not a parenthetical, not "with batteries," not a note in the description field. A line, with its own quantity, its own origin, its own classification if it differs.
What it looks like when it is right, roughly:
| Line | Description | Qty | Dangerous goods reference | Origin |
|---|---|---|---|---|
| 1 | Lithium-ion battery pack, P/N BP-4820, 48 V 20 Ah, installed in equipment | 96 pcs | UN3481, lithium ion batteries contained in equipment, class 9, PI 967 | Assembly country |
| 2 | Charging cradle, P/N CR-48 | 96 pcs | Not applicable | Assembly country |
| 3 | Spare lithium-ion battery pack, P/N BP-4820, shipped loose | 8 pcs | UN3481, lithium ion batteries packed with equipment, class 9, PI 966 | Assembly country |
Row three is the one everybody forgets, and it is the one that gets opened at the dock. Spares in a foam cutout beside the unit are not "contained in equipment." They are packed with equipment. Both are UN 3481. They are not the same description, and they do not cite the same packing instruction.
Contained in versus packed with
Which wording applies is a physical question, not a paperwork preference. Is the pack inside the device, or in the same carton next to it? If the shipment is a mix, the invoice needs both descriptions and the declaration needs both descriptions. If the invoice says contained in equipment and the carton holds eight loose spares, the two documents now disagree on a fact any officer can verify by cutting the tape.
I also keep the wording identical between the two documents rather than paraphrasing. Elegance is not the goal. The officer is matching strings.
Three origins, sometimes four
I have never had a pack where the cells, the BMS, the pack assembly, and the finished equipment all came from one country. Cells from one place, the protection board from another, pack assembly in a third, the end device built here. Each is a separate origin declaration and origin is declared per line item, so a mixed shipment carries several.
The mistake I actually see is not a legal one, it is a data one. Someone fills the origin field on the battery line with the cell supplier's country because that is what the buyer's ERP has on the part record. The origin of the pack and the origin of the cells inside it are different determinations, and the one that belongs on the line is the one your trade compliance people have settled on for the pack. I do not make that call at the bench. My job is narrower: whatever was determined lands in the same field, spelled the same way, on the invoice, on the entry data, and on the carton marking.
Two classifications on one invoice
The pack and the charging cradle do not share a code, and a mixed shipment carrying more than one classification is normal. What is not normal is one code sitting in the invoice header with nothing on the lines. Put a code per line and the entry filer stops guessing. Guesswork at that stage comes back to you as a question, and questions come back as time.
Value, and what the Incoterms rule does to it
Declared value follows the transaction basis for the shipment. Depending on the Incoterms rule in force, freight and insurance may sit inside the invoice value or outside it. Either treatment can be made to work, as long as the invoice, the transport document's freight terms, and the entry data tell the same story. Where it breaks is when the invoice reads as delivered terms and the waybill reads freight collect. Now someone has to write an explanation, and the trailer is still parked.
The other one I push back on: a battery line valued at zero with a note that it is included with the equipment. If the pack has standalone value, and a spare pack almost always does, give it a number. A zero invites a question you did not want.
The package count is where it actually breaks
If you take one field out of this, take this one. The declaration says twelve pieces. The invoice says three pallets. The packing list says twelve cartons on three pallets. The dock has four pallets on it because one was added at close of business and nobody updated anything. A declaration and a commercial invoice that disagree on package count is the most common hold trigger I deal with, and it is the cheapest one to prevent.
Pick one unit, cartons or pallets, and use it on all three documents. Then walk to the dock door and count out loud against the paper before the seal goes on. It takes about ninety seconds.
When the pack builder ships straight to your customer
Drop shipments are where this gets structurally hard. The pack builder is the shipper of record, an invoice has to be issued, and the purchase order is silent about who prepares the invoice data. The default outcome is predictable: the pack builder invoices only the packs, because that is all they sold, and the equipment the packs are installed in goes undescribed. Or your team issues the invoice and never sees the packing list. Either way the invoice data has to come from the party holding the complete transport facts.
Fix it upstream in one sentence in the PO: the seller prepares commercial invoice data for the complete shipment, including buyer-supplied equipment, and reconciles it against the transport document before tender. I have watched that sentence save a week.
The order I read the pair in
Transport document first, then invoice, then packing list, and I write the invoice from the transport document, not from the purchase order. The PO tells you what you sold and for how much. It does not know how many pieces are on the truck.
Five fields, side by side, every time: UN number and proper shipping name wording, identical on both pages. Packing instruction reference, identical. Piece count and the unit it is counted in, identical. Origin per line, matching the entry and the carton marking. Value, consistent with the freight terms on the transport document.
Not every mismatch stops a load. Some get corrected with a phone call and a revised page. But correction takes days, and the trailer does not care how long it takes. That is why I read the two documents together before the seal goes on, and why I would rather argue about a line item at the bench than explain one through a windshield.