To process packing lists automatically for goods receipt, the list has to be read when it arrives by email, matched to the purchase order in the ERP carton by carton and line by line, and posted as a receipt only when the quantities agree. A good setup also treats the packing list, the commercial invoice and the bill of lading of one import shipment as a single case, so the receipt and the landed cost come from the same checked data.

Here is what usually happens instead. The forwarder emails the packing list a week before the container lands. It sits in a folder. When the goods arrive, someone in the warehouse opens the PDF, counts cartons against it, and then types quantities, lot numbers and weights into the ERP by hand.

The packing list is the document that knows what is physically in the boxes. That is why it belongs next to the PO, and why it is one of the harder pieces of an import file.

Why packing lists slow the warehouse down

They describe cartons, the PO describes items

The PO says 1,200 units. The packing list says 48 cartons of 25. Someone multiplies, every time, for every line.

Lot numbers, weights and dimensions

Food, pharma, chemicals and electronics need the lot or batch per carton in the ERP. Typing them is slow and a wrong digit follows the product for its whole shelf life.

One shipment, several documents

The packing list, the commercial invoice and the bill of lading describe the same goods three ways. If they are keyed separately, they disagree, and the disagreement is found at month end.

Every supplier lays it out differently

Tables, free text, a scan of a stamped page. A template per supplier breaks the first time a supplier changes their form.

What the automation has to do

Read the list from the mailbox

As PDF, Excel or scan, without a template, including lists that run across several pages and cartons that hold more than one item.

Identify the supplier and find the PO

From the sender, the supplier name and the PO or order reference on the list.

Convert cartons to order units and compare

Each line is resolved to an item on the PO and the quantity is checked. Shortages, extras and unknown items stop with a reason. This is the same check the purchase order and packing list flow relies on.

Create the goods receipt with the detail the ERP needs

Quantities, lots, weights and expiry dates where they apply, linked to the PO so the supplier invoice has something to match against later.

How it works with DOConvert

DOConvert is the AI layer for the ERP. It reads the packing list, finds the PO, checks every line and only then posts the receipt. One container, step by step.

The documents arrive by email

The forwarder sends the packing list, the commercial invoice and the bill of lading in one or three emails. DOConvert groups them into one case for the shipment.

DOConvert identifies the supplier and the PO

From the sender and the documents. A supplier sending for the first time works without setup.

Cartons become order lines

48 cartons of 25 become 1,200 units against the PO line. Lot numbers and weights are read per carton.

Lines are checked against the PO and against each other

The packing list, the invoice and the bill of lading are cross-checked. One line shows 1,150 units on the packing list against 1,200 on the invoice. It stops, with the difference written next to it.

The goods receipt is created in the ERP

The matching lines are received with lots and weights. For Priority users this runs through the DOConvert Priority connector, which is bi-directional, so it reads the PO and writes the receipt back. The full import case for Priority is described in import file processing for Priority ERP. On Oracle Fusion Cloud ERP and Infor M3 the connection is direct too, no middleware.

Who it fits

• Importers and distributors that receive containers with long packing lists and lot numbers
• Warehouse and logistics managers who want receipts posted on arrival, not days later
• Controllers who need the receipt, the invoice and the bill of lading to agree before landed cost is calculated
• IT and IS managers on Priority ERP, Oracle Fusion Cloud ERP or Infor M3 who want the receipt created in the ERP, the way Kol Timber removed manual checks on import files

Questions and answers

Can it read a packing list where one carton holds several items?

Yes. Each carton line is split into its items and each item is matched to the PO. Mixed cartons are the normal case, not the exception.

What if the packing list and the commercial invoice disagree?

The case stops with the difference shown line by line. Someone decides, and the receipt is posted with the agreed quantity. How documents of one shipment are merged and checked is explained in DOConvert’s document merging and validation technology.

Does it work for local deliveries as well as imports?

Yes. A local supplier’s packing list is matched to the PO the same way. The import case just adds the invoice and the bill of lading.

Does the warehouse still count the cartons?

Yes. The physical count stays with the receiving team. The typing and the comparison to the PO do not.

How long does it take to set up?

A typical DOConvert implementation takes about 10 business days, in the cloud or on your own servers. Avi Rafalson explains why checking against the ERP matters more than reading the page in Beyond Extraction, the next frontier in intelligent document processing.

Want to see it on your own documents? Book a Demo or Get Started