Product & Business Development teams at Retail Banking firms shaping cross-border payment propositions under the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to build corridor strategy and partner-pitch decks, draft investor briefings on payments infrastructure positioning, and prepare product approval papers that cite peer-system adoption data. The same tools generate competitive-positioning claims in regulator-facing product narratives.
Two frontier AI models tested by the RLB Specialist Panel on the workflows retail-banking product and business-development teams use to support advice on the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) produced two discrete hallucinations bound to regulator-issued source text. The Panel records a single recurring failure class: Numeric Drift across the set. Questions were prepared by the Specialist Panel based on real practical AI usage in the workflows retail-banking product and business-development teams use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.
For Product & Business Development teams at Retail Banking firms, each hallucination has a direct operational consequence in the product approval paper, investor briefing, or competitive-positioning narrative. The Panel's testing surfaces ISO 20022 adoption rate conflation (RTGS vs faster payments), and ISO 20022 adoption rate conflation (RTGS vs faster payments). Where these errors flow into a deliverable, the exposure is investor-facing misstatement, product strategy built on a false market assumption, and credibility damage in partner conversations.
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-Q006-Opus47 (Claude Opus 4.7 (web search on), Numeric Drift); RLB-H-INT-BIS-CPMI-ISO-20022-HARMONISATION-UPDATED-2026-Q006-Sonnet46 (Claude Sonnet 4.6 (web search on), Numeric Drift). 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 product & business development 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 tested on this regulation collapsed two distinct CPMI adoption figures, faster payment systems at more than three-quarters, and RTGS systems at approaching half, into a single blended percentage applied uniformly to both. For a Product & Business Development team at a Retail Banking firm, this matters because the FPS/RTGS gap is strategically load-bearing: it drives infrastructure investment sequencing, correspondent banking readiness conversations, and competitive positioning claims in product approvals and investor materials.
A product strategy or regulatory mapping document that cites the AI's conflated figure misrepresents the state of the RTGS migration cycle, with the error traceable back to a verifiable primary source, directly undermining the firm's credibility with any regulator or auditor who checks the CPMI reference.
Claude Sonnet 4.6 with web search exhibited the same blended 79% adoption figure as the Opus 4.7 test on the matching question, collapsing the regulator's separately-stated faster-payment and RTGS rates into a single composite. The structural exposure for this audience is identical to the Opus variant: aI tools tested on this regulation collapsed two distinct CPMI adoption figures, faster payment systems at more than three-quarters, and RTGS systems at approaching half, into a single blended percentage applied uniformly to both.
For a Product & Business Development team at a Retail Banking firm, this matters because the FPS/RTGS gap is strategically load-bearing: it drives infrastructure investment sequencing, correspondent banking readiness conversations, and competitive positioning claims in product approvals and investor materials. A product strategy or regulatory mapping document that cites the AI's conflated figure misrepresents the state of the RTGS migration cycle, with the error traceable back to a verifiable primary source, directly undermining the firm's credibility with any regulator or auditor who checks the CPMI reference.
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.