Lloyds Banking Group has launched Export Assist, an AI-supported document-checking tool for UK exporters using letters of credit. Powered by Complidata’s TradeSpeed platform, it examines documentation before submission and flags potential errors that could trigger discrepancy fees, rejection or delayed payment. Lloyds says the service is available to UK exporters whether or not they bank with the group.

The bank estimates that 65 to 80 per cent of letters of credit contain errors or discrepancies and says the resulting corrections cost UK exporters up to 500,000 days each year. Those figures are company-provided and should be treated as estimates rather than independently verified sector totals. A Scottish exporter, Halspan, is quoted as saying the platform identified issues that might otherwise have been overlooked.

The use case is deliberately narrow. The tool is not described as deciding whether a transaction should be financed or paid. It applies AI to document quality before the formal trade-finance process reaches the bank and counterparties. That boundary is important: errors can be caught earlier while responsibility for the underlying transaction, sanctions checks, credit decision and payment remains within established controls.


Execution Level Governance- What audit-ready agent governance actually looks like
David Girvin, founder and CEO of Assury argues that model-in-the-loop review, AI governing AI, is fundamentally unreliable for regulated environments: even the best-performing models miss a meaningful share of violations, the reviewing model is typically provided by the same vendor being reviewed, and prompt injection or context poisoning can compromise both the acting agent and its supposed overseer simultaneously. He makes the case for deterministic, architecturally enforced controls instead, walking through Assury's approach of autonomy zones, session risk accumulation, and credential starvation, which lets a compromised agent be cut off from its tools instantly rather than relying on time-boxed access. The conversation touches on why David is sceptical of just-in-time credentialing as a solution for agent security more broadly, since agent sessions don't run on predictable human timescales, along with the current gap between how identity and security vendors are pitching agent protection and what he sees happening at the execution layer in practice. He also discusses the compliance and audit implications of probabilistic decision-making, arguing that regulated industries will increasingly need tamper-evident, hash-chained audit trails that can withstand scrutiny from auditors and regulators who are only beginning to understand agentic risk, and reflects on a named frontier lab's own published framework as an example of the gap between research and practitioner reality. Elsewhere, David reflects candidly on building a bootstrapped security company in an increasingly crowded market, why he turned down aggressive VC funding to stay in control of the product, and what a credible third-party assessment of his own gateway would need to look like given that Assury sits directly in the execution path for every customer's agents.
Share this post
The link has been copied!