Technology & Data teams at Retail Banking firms implementing the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to design message-schema validators, generate field-mapping logic for Fedwire and CHAPS rails, and draft API documentation for connected clients. The same tools build address-field parsing components for payment engines.
Two frontier AI models tested by the RLB Specialist Panel on the workflows retail-banking technology and data teams use to support advice on the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) produced one discrete hallucination bound to regulator-issued source text. The Panel records a single recurring failure class: Schema Over-Specification across the set. Questions were prepared by the Specialist Panel based on real practical AI usage in the workflows retail-banking technology and data teams use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.
For Technology & Data teams at Retail Banking firms, each hallucination has a direct operational consequence in the message-schema validator, field-mapping component, or API specification. The Panel's testing surfaces Fedwire hybrid postal address schema over-specification. Where these errors flow into a deliverable, the exposure is non-compliant Fedwire messages, rejected transactions at clearing, and a rework cycle spanning data-mapping and payment-engine logic. The pattern is uniform across the set: the AI returns a confident, sourced-looking answer that conflicts in a load-bearing specific with the regulator's verbatim text, and the error survives a first-pass review precisely because the surface form is plausible.
The Panel records each hallucination with the regulator's primary substrate held as the anchor, so the corrective text is available alongside the failure.
The Specialist Panel records the citation IDs as follows: RLB-H-INT-BIS-CPMI-ISO-20022-HARMONISATION-UPDATED-2026-Q010-Opus47 (Claude Opus 4.7 (web search on), Schema Over-Specification). Each citation links to the verbatim regulator-issued source text, the tested AI question, and the recorded AI response, so the Panel's assessment is traceable end to end. For technology & data teams at retail banking firms, the citation IDs operate as a reference index: when an AI answer in the working draft matches a known Panel finding, the cited regulator text is already available as the corrective anchor.
The full per-finding analysis cards, including the audience-specific impact statement, sit on the cell's detail surface for sign-off use.
This is the consolidated view of findings. Click the Citation IDs or 'see details →' on any item for the full details for each finding.
AI tools correctly identify the Fedwire ISO 20022 go-live date but misstate the postal address structure required for the hybrid/end-state approach: rather than the FRB-specified free-format optional lines of up to 70 characters alongside mandatory country code and town name, the AI describes optional structured sub-elements (Street Name, Building Number, Post Code) drawn from general CBPR+ address conventions.
A Technology & Data team at an international Retail Bank that builds Fedwire address-field validation or field-mapping logic to this AI specification will produce payment messages that fail Fedwire's format requirements, resulting in rejected transactions, manual exception processing, and a rework cycle spanning data-mapping, payment-engine logic, and Fedwire sandbox re-validation.
Every finding on this page compares an AI subject's account of the rule against the regulator's verbatim text from the regulator's own portal. Both are linked. Each delta, its root causes, and impact analysis are documented and published with immutable Citation IDs.