AI agent · Logistics & ports · Chase what is missing
Customs file assembly
A customs declaration rests on documents that come from different people at different times. The agent assembles the file for each shipment, checks the documents agree, and chases whatever is missing until the file is complete or a person must step in.
Typical volumes for this process, not a client figure.
Documents gathered from five places and assembled per shipment.
Assembled automatically; missing pieces chased from the source.
Where the time goes today
For each shipment, the customs file brings together the commercial invoice, the packing list, the transport document, a certificate of origin where preferential treatment is claimed, and any licences, permits or product certificates the goods require. These come from the supplier, the forwarder, the carrier, your own purchasing team and sometimes a laboratory or an issuing body. Someone in the trade or logistics team gathers them from emails, portals and shared folders, checks them, and passes the file to the broker or to whoever lodges the declaration.
Most of the time goes into chasing. A packing list arrives without the invoice, the certificate of origin is promised for next week, the forwarder sends a draft bill of lading and then a final one with a different weight. The person assembling the file keeps a mental list of what is outstanding for each shipment and writes follow-ups one by one. When the goods arrive before the file is complete, they wait, and storage or demurrage charges begin.
Inconsistencies are the other risk. A weight on the packing list that differs from the transport document, or an invoice value that differs from the order, can lead to a query or an amended declaration later.
How the agent works
- Open the shipment fileWhen a shipment is booked or an advance notice arrives, the agent opens a file and lists the documents it needs, based on the goods, origin, destination, transport mode and whether preference is claimed.
- Collect what arrivesIt watches the mailboxes, portals and folders where documents land, identifies each document, and attaches it to the right shipment using references, parties and dates.
- Check consistencyIt compares key facts across documents: parties, goods description, quantities, weights, values, currency, origin and references. Differences beyond your tolerances are recorded with both values.
- Chase what is missingFor each missing or inconsistent document, it writes to the party that issues it, stating exactly what is needed and why, then follows up on a schedule tied to the arrival date.
- Escalate or releaseA complete, consistent file goes to your broker or declaration team. A file still incomplete as arrival approaches is escalated to a person, with the history of every request.
What stays with a person
Tariff classification, customs valuation, claims to preferential origin and the declaration itself stay with your customs specialists or your broker. They carry legal responsibility, and the rules behind them often call for interpretation. The agent can show that the commodity code on an invoice differs from the one used last time for the same product, but it does not choose the code.
A person also takes over when chasing stops working: a supplier who does not answer, a certificate that cannot be issued in time, a discrepancy the forwarder disputes. At that point the decision is commercial, such as shipping without preference or holding the goods, and the agent's job is to have the full history ready.
What it reads, what it produces
| It reads | It produces |
|---|---|
| Commercial invoices and packing lists | A shipment file with every document attached and identified |
| Transport documents: bills of lading, air and road waybills | A checklist per shipment showing what is present, missing or inconsistent |
| Certificates of origin, licences and product certificates | Follow-up messages to forwarders, suppliers and carriers, with the history kept |
| Booking and advance notice data from forwarders and carriers | A handover pack for the broker or declaration team |
| Purchase orders and product data, including previous classifications | An escalation list of shipments at risk of arriving incomplete |
| Your document requirements by product, origin and destination |
Controls that come with it
- Document requirements come from rules your trade compliance team owns and versions.
- The agent never lodges a declaration or chooses a classification; it assembles and checks.
- Follow-ups use approved templates and go only to contacts already on record for that shipment.
- Escalation deadlines are set from arrival dates, so late files reach a person while there is still time to act.
- Every document received, check made and message sent is logged, and a misfiled document can be moved and the file re-checked.
How you know it works
- Share of files complete before the goods arrive
- Time spent per shipment on gathering and chasing
- Storage or demurrage charges linked to incomplete documents
- Inconsistencies caught before lodging against queries raised afterwards
Is your process ready?
- Written rules: which documents each product and trade lane needs is written down by your trade compliance team.
- Systems: the mailboxes, portals and folders where documents arrive can be read, and forwarder portals permit automated access under their terms.
- Cheap check: a completed file can be reviewed against its checklist in minutes, and the broker's acceptance confirms it.
- Volume: hundreds of shipments a week, each with several documents from several parties, repays the build.
- Consistent process: your team, your forwarders and your broker agree on what a complete file contains.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Documents attached to long email threads that mention several shipments, which makes filing them correctly harder than expected.
- Draft and final versions of the same document, where the agent must keep the final and record what changed.
- Chasing a party who does not actually issue the document, which wastes days.
- Requirement rules that miss product-specific certificates, so a file looks complete when it is not.
Questions we get
Does it prepare the customs declaration?
No. It assembles and checks the documents the declaration relies on, then hands them to whoever lodges it: your broker or your own declaration team. Classification, valuation and origin decisions carry legal responsibility and stay with them. If your broker accepts structured data, the agent can pass the extracted facts along with the documents to save re-keying.
How does it know which documents a shipment needs?
From rules your trade compliance team writes, by product, origin, destination and transport mode, and by whether preferential treatment is claimed. When a shipment falls outside those rules, such as a new product or a new trade lane, the agent flags it for a person to decide rather than assuming a standard set.
How often does it chase, and whom does it write to?
The schedule is yours, usually tied to the expected arrival date, with follow-ups closer together as arrival approaches. It writes only to contacts on record for that shipment and party, using templates you approve. Each message names the shipment, the document needed and the deadline, and replies are read and attached to the file.
What happens when documents disagree?
The agent records both values and the document each came from, and asks the party best placed to correct it: the supplier for an invoice value, the forwarder for a gross weight. A difference within your tolerance is noted and the file moves on. Anything unresolved by the escalation deadline goes to a person.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.