Proving an AI-Assisted Determination to an Auditor
An AI-assisted customs determination is defensible only if the file shows the rule, the evidence and the human review. Six artefacts an audit file must carry.
The Audit Question Is Not "Was It Right"
An audit conducted two or three years after a shipment does not test whether a system was accurate. It tests what the file shows — and a determination that was correct but undocumented is, for audit purposes, indistinguishable from one that was guessed. This is the gap most machine-assisted compliance programmes discover late, because the tooling was bought to produce answers and the audit asks for the reasoning behind them.
The problem is sharper with automated preparation than with manual work, for a reason worth naming. When a person performs a check, the artefacts of that work — annotated documents, an email chain, a note on a print-out — accumulate as a by-product. When a system performs the same check, nothing accumulates unless it was designed to. The output appears; the reasoning evaporates. Speed removes the incidental paper trail that manual process generated by accident.
What follows is the file an AI-assisted determination has to leave behind if it is to be defensible later, drawn from what auditors actually ask for and from what the EU AI Act now requires deployers to retain.
The Six Artefacts
A defensible file contains six things, and the absence of any one of them shifts the burden back onto memory. They are not exotic; the difficulty is that they must be captured at the moment of the determination, because none of them can be reconstructed honestly afterwards.
1. The rule as it stood on the transaction date. Not the current text — the text in force when the shipment moved. A determination made correctly under an instrument that has since been amended is defensible; the same determination assessed against today's wording looks wrong. Rate volatility makes this acute: where a rate has been cut and restored within a quarter, the only defence is a record of which instrument governed that consignment.
2. The source documents the determination rested on. The specific invoice, packing list, transport document and certificate — as received, not as summarised.
3. The reconciliation. Which fields were compared against which, and what the comparison found. This is the artefact that converts an assertion into a demonstration.
4. The machine output, as produced. Including its stated confidence and, critically, anything it could not resolve.
5. The human review, including overrides. Who reviewed, when, what they changed, and why.
6. A record fixing what was signed. Something that establishes the reviewed set has not changed since review — otherwise the sign-off attaches to nothing in particular.
What the EU AI Act Now Requires of Deployers
For systems in scope, retention has moved from good practice to obligation, and the obligation sits partly on the deploying business rather than only on the vendor. Article 12(1) of the AI Act requires that high-risk AI systems technically allow for the automatic recording of events over the lifetime of the system. That is a design duty on the provider, but it has a direct procurement consequence: a system that cannot produce logs cannot be made compliant by the buyer's process.
Article 26 then binds the deployer. Under 26(1) and 26(2), deployers must take appropriate technical and organisational measures to use the system in accordance with its instructions, and must assign human oversight to natural persons who have the necessary competence, training and authority. Under Article 26(6), deployers must keep the logs the system generates for a period appropriate to the intended purpose and in any case at least six months, unless other law provides otherwise.
Two practical implications follow. First, "the compliance team reviewed it" is not an answer to 26(2) — the file has to identify a person with named competence and authority. Second, six months is a floor set by AI regulation, not by customs law; trade retention periods are considerably longer, and the longer period governs. Aligning log retention to the customs and tax retention schedule rather than to the AI Act minimum is the conservative and correct choice.
Why Override Records Cut Both Ways
The override log is the artefact most often omitted and the one an experienced auditor reads first, because it is the only direct evidence about the quality of the review itself. A reviewer who overrode the system regularly, with reasons, demonstrates that oversight was substantive. A reviewer who approved everything, across a period when the inputs were demonstrably imperfect, demonstrates the opposite — and the second pattern is exactly the automation bias that Article 14(4)(b) of the AI Act requires oversight design to work against.
This is why override capture should never be optional or free-text-only. The reviewer's disagreement with the machine is a first-class record, and its absence is not neutral evidence. A file showing a hundred determinations and zero corrections invites the question of whether review occurred at all — and that question, once asked, is answered from the same empty file.
Building the File Before It Is Needed
Under section 99A of the Customs Act, 1962, the proper officer may audit an assessment or an auditee at the department's office or at the auditee's premises. The audit arrives on the department's schedule, not on a schedule the business chooses, and by then the determination is years old and the people who made it may have moved on.
The operational conclusion is unglamorous: the file has to be assembled continuously, as a by-product of doing the work, because assembling it on demand is expensive and produces a weaker result. For a customs broker the same file is what evidences the Regulation 10(e) duty to have exercised due diligence — a conduct standard that can only be proven by contemporaneous record.
TradeWatch produces these six artefacts as the ordinary output of preparing a shipment rather than as a separate compliance exercise: the governing rule cited at the version in force, the source documents retained, the reconciliation recorded, unresolved items surfaced rather than defaulted, and a reviewer-of-record signing a fixed set. Kanan Labs prepares a readiness packet. It does not file Shipping Bills and holds no customs credentials — your licensed CHA files. Final HS classification requires human review.