AI Agents for Landed Cost and Customs Duty Verification
Duty is calculated on a classification somebody chose, a value somebody declared, and an origin somebody stated. Finance sees only the total.
- Duty depends on classification, declared value and origin, and errors in any of the three flow straight into inventory cost.
- Classification tends to be set once per product and then reused indefinitely, including after the product changes.
- Broker entries are rarely checked against the commercial documents they were built from.
- Landed cost that is estimated and never trued up distorts margin at the product level, which is where pricing decisions are made.
- ChatFin compares broker entries to source documents, flags inconsistencies, and trues up landed cost with the evidence attached.
Imported goods carry costs that arrive after the goods do: duty, freight, insurance, brokerage, port charges and any adjustment the broker makes later.
Most systems capitalise an estimate at receipt and reconcile the difference to a variance account, where it becomes invisible. The inputs behind the duty calculation are handled by a broker and rarely re examined by finance.
This page covers what actually drives duty, why classification drift is the quiet problem, and how a governed agent can verify the inputs and keep product level landed cost honest.
Three inputs, one total
Duty is a function of tariff classification, customs value and country of origin. Each is determined at the time of entry, and each can be wrong independently.
Finance receives a duty invoice showing a total, with no visibility into which classification was used or how the value was built.
Classification drift
A product gets classified when it is first imported. Then the specification changes, materials change, or the product is superseded by a similar one that inherits the same code.
Nobody revisits it, because there is no event that triggers a review. The code keeps being used and the duty keeps being paid at whatever rate it carries.
Periodic testing of classification against current product data is the only reliable way to catch this, and it can move duty in either direction, which is why it should be treated as an accuracy exercise rather than a savings hunt.
The broker's version and yours
The entry summary comes from the broker, the commercial invoice and packing list come from the supplier, and the purchase order sits in your ERP. Duty is calculated on the broker's version and finance reconciles only the total.
What the agent needs to see
Ledger detail from the ERP, plus commercial invoices and packing lists taken from the source they arrive in, read through the API surface your ERP already exposes rather than the database.
What it should be allowed to do
Prepare a landed cost adjustment and a broker query list and leave it for the cost accountant to approve. Reading widely and writing narrowly is the line that keeps this safe.
That division matters more than which model sits underneath. An agent that can read commercial invoices and packing lists, broker entry summaries and freight and duty invoices while posting only through the validated path a person uses gives you the coverage without handing over the ledger, and ChatFin works that way on every ERP it connects to.
What the agent verifies
The agent compares the broker entry to the commercial invoice, packing list and purchase order: quantities, values, product descriptions and stated origin.
Inconsistencies become a broker query list. Confirmed costs are allocated to the right receipts so landed cost reflects what was actually incurred.
Match entry to source
Compare the broker entry summary against the commercial documents it should have been built from.
Test classification consistency
Check that the same product is classified consistently and that descriptions match the code used.
Allocate actual costs
Apportion duty, freight and charges to the specific receipts rather than to a variance account.
Draft the adjustment
Prepare the landed cost true up and the broker query list with the documents attached.
Why this reaches pricing
Landed cost is the basis for product margin. When the estimate is stale, margin at the product level is wrong even though total cost of goods is right, because the error is distributed rather than absent.
That matters most for businesses with wide assortments, where pricing and assortment decisions are made product by product on numbers nobody has verified.
Accurate inventory cost
Actual duty and freight allocated to the receipts that incurred them, rather than absorbed into a variance.
Reliable product margin
Landed cost per item that reflects reality, which is what pricing and assortment decisions depend on.
Classification stays with a specialist
Tariff classification is a technical determination with legal consequences. ChatFin tests consistency and flags where product descriptions and codes no longer agree, and the classification itself stays with your broker or customs specialist.
The record kept against landed cost is deliberately plain: the commercial invoices and packing lists the agent read, the reasoning it applied, the draft it produced, what the cost accountant changed, and the moment it posted. That is the trail an auditor asks for, and it is assembled while the work happens rather than reconstructed afterwards.
The wider argument for that design sits in governed write-back and a controller's guide to reviewing AI generated entries.
A is prepared, reviewed and approved before it posts, and every step is logged from the source document to the entry. landed cost adjustment and a broker query list
How ChatFin verifies entries
Broker entries are compared against the commercial documents they should have been built from, line by line, and inconsistencies become a query list. Actual duty and freight are allocated to specific receipts so product level margin stops depending on a stale estimate.
It connects to the ERP, the customs broker's system and the freight forwarder portal through the interfaces those systems already expose, which keeps the security review short and the setup measured in days rather than quarters.
Match entry to source
Quantities, values, descriptions and stated origin compared against commercial documents.
Test classification consistency
The same product checked for consistent coding, with description and code mismatches flagged.
Allocate actual cost
Duty, freight and charges apportioned to the receipts that incurred them.
Draft true up and queries
Landed cost adjustment and the broker query list prepared with documents attached.
A first run is usually read only against a period you have already closed, so you can compare what the agent found against what your team found before anything is trusted with a landed cost adjustment and a broker query list.
Because the read and write paths are shared, extending into the next process on NetSuite, SAP Business One or Acumatica is a configuration decision rather than a project.
Duty is decided by three inputs. Finance usually sees only the total they produced.
ChatFinFrequently Asked Questions
Can it classify products for customs purposes?
It should not. Classification is a technical determination with legal consequences and belongs with a qualified specialist or your broker. What the agent does is test consistency and flag where descriptions and codes no longer agree, so the review is targeted.
Do we need our broker to cooperate?
Entry summaries are documents you are entitled to, and most brokers provide them routinely. The verification runs against those documents and your own commercial paperwork, so it does not depend on system access at the broker.
How does this affect inventory valuation?
Actual duty and freight are allocated to the receipts that incurred them rather than absorbed into a variance account, which makes product level cost and margin accurate. Adjustments are drafted for approval like any other entry.
This page is general information about finance operations and software, not legal, accounting, or tax advice. Confirm treatment for your own entity with your advisors.
Check every entry against the documents behind it.
ChatFin compares broker entries to commercial invoices, packing lists and purchase orders, flags inconsistencies, and allocates actual duty and freight to the right receipts.
Landed cost stops being an estimate that nobody trues up, and product margin becomes a number worth pricing against.
Book a DemoSee broker entries checked against your own documents.
Bring a set of entry summaries with the matching commercial invoices. We will show the comparison, the inconsistencies, and landed cost allocated to actual receipts.