Briefings Blog

Compliance teams at Statutory Boards & Agencies responsible for payments infrastructure exposure to the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to draft formal regulatory submissions to central banks or supranational bodies, generate board papers on payments infrastructure benchmarks, and prepare gap-analysis documents against peer adoption rates. The same tools validate citation accuracy in finance-ministry-facing briefings.

Two frontier AI models tested by the RLB Specialist Panel on the workflows statutory-agency compliance officers 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 statutory-agency compliance officers use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.

For Compliance teams at Statutory Boards & Agencies, each hallucination has a direct operational consequence in the regulatory submission, gap-analysis document, or finance-ministry briefing. 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 a credibility-damaging factual discrepancy in a formal submission, a forced retraction or amended filing, and a misstated baseline for gap analysis presented to the governing board.

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 compliance teams at statutory boards & agencies, 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.

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.

Operations teams at Retail Banking firms running cross-border payments programmes under the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to build internal business cases for harmonisation investment, generate operational metrics for COO challenge sessions, and configure Fedwire payment-message templates. The same tools draft vendor due-diligence questionnaires on cross-border payment readiness.

Two frontier AI models tested by the RLB Specialist Panel on the workflows retail-banking operations 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 two distinct failure classes, False-Negative Retrieval and Schema Over-Specification across the set. Questions were prepared by the Specialist Panel based on real practical AI usage in the workflows retail-banking operations teams use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.

For Operations teams at Retail Banking firms, each hallucination has a direct operational consequence in the operations business case, COO challenge pack, or payment-message specification. The Panel's testing surfaces missing inquiry-rate and resolution-time benchmarks, and Fedwire hybrid postal address schema over-specification. Where these errors flow into a deliverable, the exposure is live STP failures, manual repair queues, and a re-run of UAT cycles mid-programme.

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-Q007-Sonnet46 (Claude Sonnet 4.6 (web search on), False-Negative Retrieval); 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 operations 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.

Operations teams at Payment Institutions running USD cross-border flows under the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to configure ISO 20022 address-field handling, draft mapper working notes, and generate QA test scripts for correspondent banking. The same tools build correspondent-bank onboarding checklists.

Two frontier AI models tested by the RLB Specialist Panel on the workflows payment-institution operations 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 two distinct failure classes, False-Negative Retrieval and Schema Over-Specification across the set. Questions were prepared by the Specialist Panel based on real practical AI usage in the workflows payment-institution operations teams use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.

For Operations teams at Payment Institutions, each hallucination has a direct operational consequence in the mapper working notes, QA test script, or onboarding checklist. The Panel's testing surfaces missing inquiry-rate and resolution-time benchmarks, and Fedwire hybrid postal address schema over-specification. Where these errors flow into a deliverable, the exposure is STP failures and systematic manual intervention in address-field processing at the transaction volumes the harmonisation programme is designed to reduce.

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-Q007-Sonnet46 (Claude Sonnet 4.6 (web search on), False-Negative Retrieval); 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 operations teams at payment institutions, 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.

Treasury teams at Corporate Banking firms steering cross-border liquidity under the CPMI Harmonised ISO 20022 Data Requirements (Updated Report) are increasingly using AI to review origination-system configurations against Fedwire format requirements, generate investment-case sections for migration projects, and validate vendor connectivity specifications. The same tools draft board briefings on the operational ROI of harmonisation.

Two frontier AI models tested by the RLB Specialist Panel on the workflows corporate-banking treasury 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 two distinct failure classes, False-Negative Retrieval and Schema Over-Specification across the set. Questions were prepared by the Specialist Panel based on real practical AI usage in the workflows corporate-banking treasury teams use AI for, and each finding is bound to verbatim regulator-issued source text held as primary substrate.

For Treasury teams at Corporate Banking firms, each hallucination has a direct operational consequence in the investment case, board briefing, or vendor connectivity specification. The Panel's testing surfaces missing inquiry-rate and resolution-time benchmarks, and Fedwire hybrid postal address schema over-specification. Where these errors flow into a deliverable, the exposure is validation failures at the Fedwire interface, addressable-data exceptions requiring manual resolution, and a weakened business case for migration spend.

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-Q007-Sonnet46 (Claude Sonnet 4.6 (web search on), False-Negative Retrieval); 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 treasury teams at corporate 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.