Customs & trade documents
Agent: the documentation agent (documentation in ExecuteLoop), with the
customs cards and the CUSTOMS_MANIFEST_EXCEPTION evidence document.
What it does
It reads your shipping and customs records, finds what is holding a shipment up or doesn’t match, and drafts the next document or step for your trade team. Its jobs:
- Customs holds. Finds entries that are held, which release documents are still missing, and the charges that have built up so far.
- Document cross-checks. Compares the bill of lading, commercial invoice and packing list for one shipment, and names where they disagree.
- Weight against manifest. When the weighbridge and the manifest differ by more than 5 %, drafts a manifest amendment.
- Draft trade documents. When an order is ready for dispatch, drafts the bill of lading, commercial invoice, packing list and customs declaration from your ERP records, with the HS classification and Incoterm for review.
What it reads
Customs entry records, manifests, bills of lading, commercial invoices, packing lists, weighbridge events, ERP order and shipping records, regulatory tables you provide, and the rules Rules Recon found in your data. It can run read-only queries against the connection a run was started with.
What it produces
- Customs cards with a priority and a proposed next action, such as “request the certificate of origin from the supplier”. A customs manifest exception waits on Actionable Twins under the disruptions play.
- The
CUSTOMS_MANIFEST_EXCEPTIONevidence document, with each figure cited. See Evidence documents. - Draft document payloads (bill of lading, commercial invoice, packing list, customs declaration), an HS classification and the Incoterm, for a person to check.
Human oversight
- The customs or trade lead approves every next step and every document before it is sent or filed.
- The agent never files a declaration, submits a document to an authority or amends a manifest on its own.
- HS classifications are proposals. The declarant remains responsible for them.
Model
The deployment’s general reasoning tier.
The customs exception document is fixed arithmetic over cited records. No model computes its figures.
Where it runs and data handling
On the deployment’s own model plane: Runink’s shared machines on a Trial, your own cloud on Cloud and your own servers on On-premises. No outside AI service is called on any plan. See Facts shared by every card.
Guardrails
- Refuses to falsify or fabricate HS codes, commercial invoices, packing lists or Incoterms to avoid a tariff or a check.
- Never invents a figure. A document or value that isn’t on file is named as missing.
- Duty is kept out of avoidable port charges, so a delay’s cost isn’t inflated.
How to read its results
- It gives no legal or customs advice. A computed date or limit is an input for the person deciding.
- A draft document is only as complete as the ERP record behind it. Missing fields stay empty and are named, never filled with a plausible value.
- It doesn’t establish who caused a hold. It reports what the entry record says.