Trade finance is one of the last genuinely paper-shaped processes in banking. A documentary credit is issued, an exporter presents a set of documents — invoice, transport document, insurance certificate, certificates of origin and inspection, packing lists — and a checker in an operations centre compares that set against the terms of the credit and the applicable rules, within a fixed window, and decides whether the presentation complies.
The scale of the rework is the striking part. Surveys referenced during the drafting of UCP 600 indicated roughly 70% of presentations were rejected on first presentation, and later industry estimates have generally sat in the 65–80% range with substantial regional variation. Two decades of rule revision have not moved the number much, because the underlying cause is not the rules. It is that compliance is assessed on documents alone, and documents produced by half a dozen unrelated parties in different countries rarely agree with each other on first attempt.
That combination — written rules, document inputs, a decision that must be justified, and a deadline — describes an unusually good candidate for agent-assisted work. It also describes a process where the wrong automation design creates real exposure.
Why this workflow suits an agent, and where the line sits
Four properties make documentary examination tractable. The rules are written down: UCP 600 and the associated ICC practice materials define what constitutes a complying presentation with more precision than most enterprise processes achieve. The inputs are bounded — a presentation is a finite set of documents, not an open-ended research task. The output is structured: a finding per potential discrepancy, each traceable to a document and a credit term. And there is a clock, which makes preparation time genuinely valuable rather than merely convenient.
The line, however, should be drawn firmly. The bank’s determination that a presentation does or does not comply, and the single notice of refusal stating each discrepancy relied upon, are acts with legal consequence. An agent that drafts findings is an aid to a checker. An agent that issues the determination has been given a role the operating model cannot support, and it will be the first thing an examiner asks about. The design pattern is the one described in human approval steps in agentic workflows: the machine assembles the case, the qualified person decides it.
What makes it harder than document extraction
Teams that have automated invoice capture often assume this is the same problem at a different scale. It is not, for three reasons.
The check is relational, not per-document. Extracting a goods description from an invoice is straightforward. Determining whether it is consistent with the credit and not in conflict with the transport document and the certificate of origin is a cross-document reasoning task. Most discrepancies live in the disagreements between documents, not inside any one of them.
Presentation form carries meaning. Whether a document is an original or a copy, how it is signed, who issued it and whether it is dated in a permissible relationship to shipment can each be decisive. A pipeline that reduces every document to plain text loses the attributes the examination turns on.
The credit itself is the specification. Every presentation is examined against a different set of terms, including conditions that map to no document at all. The rule set cannot be static; it has to be built per credit from the credit’s own text — a retrieval and structuring problem before it is a checking problem.
An architecture that holds up under scrutiny
A workable design has five stages, each producing evidence rather than only passing data forward.
Ingest and normalise. Accept scanned images and electronic records, classify each document by type, and preserve page-level provenance so every later assertion can point back to a location in a source file. The ingestion discipline here is the same one required for any secure document ingestion pipeline.
Structure the credit. Parse the credit and any amendments into an explicit, reviewable list of requirements — documents required, data conditions, dates, tolerances, presentation period. This artefact is worth exposing to the checker directly; a mis-parsed credit term is a failure mode that is much cheaper to catch here than three stages later.
Extract with references. Pull the fields each requirement depends on, each carrying a citation to the document and location it came from. An extracted value with no reference cannot be reviewed at speed, and a finding a checker cannot verify in seconds is a finding that costs more than it saves.
Check and draft findings. Run the deterministic comparisons — dates, amounts, tolerances, party names, consistency of descriptions across documents — in code where they are deterministic, and reserve model judgement for the genuinely interpretive comparisons. Each candidate discrepancy is drafted with the requirement it relates to, the evidence, and a confidence signal.
Present for decision. The checker receives an ordered worklist with the strongest evidence first, confirms or dismisses each finding, and composes the notice. The platform records not just the outcome but the whole basis: which model version produced which finding, what the checker changed, and when. That record is the difference between a helpful tool and a defensible one — the same execution evidence any regulated agent workflow needs.
Governance the trade finance function will be asked about
Three areas draw immediate attention in any internal audit of this workflow.
Traceability of findings. Every discrepancy raised must be attributable to a specific requirement and a specific document location, and must be reproducible later. “The system flagged it” is not a position a bank can defend when a beneficiary disputes a refusal.
Model change control. Upgrading the extraction or reasoning model changes examination behaviour. That is a change to a control-relevant process, and it needs version pinning, a promotion decision and a record of which version was live on a given date — the discipline set out in model governance for local models.
Segregation and access. Presentation sets contain commercially sensitive counterparty data and sit adjacent to sanctions and financial crime screening. Retrieval and tool access have to be scoped so an agent supporting trade finance cannot reach beyond its own domain, which is the isolation model described in department-specific agents.
The digitisation trend does not remove the work
Electronic presentation is advancing. eUCP version 2.1 aligned the electronic presentation rules with the UNCITRAL Model Law on Electronic Transferable Records, and jurisdictions including the United Kingdom have recognised electronic trade documents in law. Structured electronic records reduce extraction error, but they do not reduce the examination burden, because the disagreements between documents remain — and a mixed estate of paper, scanned and electronic presentations will persist for years. A pipeline that accepts both and produces identical findings from either is the practical target.
Measuring whether it worked
Three measures matter more than throughput. Checker agreement rate — the proportion of drafted findings the checker accepts unchanged — tells you whether the agent is genuinely helping or generating review work. Escaped discrepancies — issues found later that the pipeline missed — is the safety metric, and needs a sampling process rather than a dashboard. Time to first decision is the business metric, because in trade finance the value is largely in returning a clean refusal or acceptance early enough for the beneficiary to correct and re-present within the credit’s validity.
Building the benefit case from those three, rather than from a documents-per-hour figure, is what makes the ROI calculation survive review.
How VDF AI supports document examination workflows
VDF AI runs the whole pipeline inside the bank’s own environment: ingestion, extraction, retrieval over the credit and internal practice guidance, deterministic checks as governed tools, and the drafting of findings by local models registered on the platform. No presentation document, extracted field or examination log leaves the boundary.
Approval steps are part of the workflow definition rather than an add-on, so a finding reaches a checker before anything is issued, and the checker’s confirmation or amendment is recorded alongside the model version and evidence that produced it. Tool access is scoped per agent, so the workflow reaches the systems it needs and no others. The result is a preparation layer that shortens the examination without moving the decision, and an evidence trail that answers what an auditor will actually ask: on what basis was this discrepancy raised, and who decided it.
Further reading
- How AI Agents Automate Financial Document Review: Loan Underwriting
- Document Extraction, Validation, and Routing with VDF AI
- How to Add a Human Approval Step to an Agentic Workflow
- AI Agents for Payment Investigation Workflows
- On-Premise AI for Financial Services
Sources
- ICC — eUCP Version 2.1, Uniform Customs and Practice for Documentary Credits for Electronic Presentation
- Trade Finance Global — Released: eUCP Version 2.1, aligning with MLETR
- DCW — Discrepancy Rates Under UCP 600
- UK Legislation — Electronic Trade Documents Act 2023
Examining documents against written rules at volume? See how VDF AI builds governed agent workflows inside your own environment, or book a demo.