Customs Documentation Automation, What Importers and Brokers Actually Need It to Do

Customs documentation automation is what happens to the customs declaration, the commercial invoice and the broker’s invoice after they arrive by email. Not reading them, that part is easy now. Tying them to the right import file in the ERP, checking them against it, and entering only what matches.

Most import offices still do this by hand. The broker emails the cleared declaration and the invoice for duties and fees. Someone opens the import file in the ERP, finds the shipment, checks the declared value against the commercial invoice, checks the duty against the HS codes, and types the costs into the landed cost record. Then the next shipment.

This page explains what customs documentation automation has to do, document by document, and where tools that only extract fields stop short. We wrote about automating commercial invoices for customs clearance separately, this is the whole file.

The documents in a customs file

The commercial invoice

The supplier’s invoice for the goods, the basis for the declared value. Its totals have to agree with the purchase order and with the declaration.

The packing list and the bill of lading

What was shipped, in how many packages and at what weight, and the carrier’s record of the shipment. Together with the commercial invoice they make up the import file that the declaration is built from.

The customs declaration

The entry filed by the broker, with HS codes, declared values, duties and taxes per line. It is the document the authorities hold you to, and the one most often filed in the ERP as a PDF nobody reads again.

The broker’s invoice

Duties, VAT, port fees, handling, the broker’s own fee. Several cost types on one invoice, each landing on a different account, often weeks after the goods arrived.

What automation has to do with them

Identify the sender and the shipment

Which broker, which forwarder, and which of your open import files this belongs to. Without that link, extracted fields are just numbers.

Check the declaration against the commercial invoice

Declared value per line against the invoice value, quantities against the packing list, currency and exchange rate against what was booked. A difference here is either a broker error or a future audit question.

Check the broker’s invoice against the declaration

The duty on the invoice should equal the duty on the declaration. The VAT should follow from the declared value. Fees should match the broker’s agreement. Each cost type goes to its own line in the landed cost.

Stop what does not agree, with a reason

A declared value that does not match the invoice, a duty amount that differs from the entry, a fee that is not in the agreement. Each stops for the import coordinator with the difference shown, instead of being entered and found at year end.

Enter only what matched

The cleared declaration, the costs and the references go into the import file in the ERP as normal records. The landed cost is complete when the goods are, not a month later.

Where extraction-only tools stop short

They read, they do not match

OCR or a template tool returns the fields. Somebody still has to find the import file, compare the values and decide. The typing moved, the checking did not.

A template per broker

Every broker and forwarder has its own declaration printout and invoice layout. Template tools need one each, and the layouts change.

One document at a time

The value of a customs file is in the relationships between its documents. A tool that handles each PDF alone cannot tell you that the duty on the invoice is not the duty on the declaration. This is why intelligent document processing for freight forwarders is a different problem from invoice OCR.

How it works with DOConvert

DOConvert is the AI layer for the ERP. It connects directly to Priority through the DOConvert Priority connector, which is bi-directional, and to Oracle Fusion Cloud ERP and Infor M3, with no middleware. Here is a customs file for one container.

The documents arrive by email

The forwarder sends the commercial invoice, packing list and bill of lading. Days later the broker sends the cleared declaration and its invoice. DOConvert identifies each sender and recognises each document for what it is. No template per broker or forwarder.

The import file is found in the ERP

From the purchase order number, the invoice reference or the container number, DOConvert finds the open import file and ties all five documents to it as one case.

The cross-check

Declaration values against the commercial invoice, package counts against the packing list and bill of lading, duty and VAT on the broker’s invoice against the declaration. Differences stop with a plain reason for the import coordinator.

The import file is completed

What matched and was confirmed is entered, the declaration details, the duties and fees as costs on the import file, the references. iDigital automated its customs records this way in Priority.

The same documents, from the forwarder’s side

A forwarder or broker handling the same file for many clients runs the same flow per client, and the document-by-document view is in freight document processing. Avi Rafalson, CEO of DOConvert, wrote about why checking matters more than extraction in Beyond Extraction.

Who it fits

Importers whose purchasing or finance team keys declarations and broker invoices into the import file.

Customs brokers and freight forwarders handling declarations for many clients a day.

Controllers who want landed cost complete and auditable without a month of catch-up.

Companies on Priority, Oracle Fusion or Infor M3 that import regularly, in the UK, the US or Israel.

Questions and answers

Does automation file the customs declaration?

No. The broker files it. Automation handles what comes back, the cleared declaration and the invoices, and gets them into the ERP checked.

What if the broker’s invoice arrives weeks after the goods?

It is tied to the same import file whenever it arrives, and checked against the declaration that is already there.

Do we need a template for each broker?

No. DOConvert understands what a declaration or an invoice is rather than where the fields sit, so a new broker works from the first document.

How long does implementation take?

A typical DOConvert implementation takes about 10 business days, in the cloud or on your own servers.

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

Process overview

DOConvert revolutionizes B2B communications with cutting-edge technology that automates data extraction – a platform that extracts relevant data from any document type and integrates the data into your digital records system, without human intervention.
Our advanced technology automatically maps, recognizes, parses and processes data from complex documents in mere seconds, enhancing operational speed, boosting efficiency, and drastically reducing your costs.

With DOConvert, you are “hands-free.” You no longer need to copy/paste, or retype critical information embedded in your documents. Data contained in emails, purchase orders, invoices, and much more can be extracted and entered into existing systems in seconds.
Gone is the cumbersome, time-consuming, error-prone, data entry, saving you and your company time and money.

DOConvert revolutionizes B2B communications with cutting-edge technology that automates data extraction – a platform that extracts relevant data from any document type and integrates the data into your digital records system, without human intervention.
Our advanced technology automatically maps, recognizes, parses and processes data from complex documents in mere seconds, enhancing operational speed, boosting efficiency, and drastically reducing your costs.

Additional case studies

Subscribe to receive tips and product updates

Get our updates to your inbox