Misstated recommendation count, fabricated consultation respondents, and scoping drift on the CPMI October 2024 final report on FPS interlinking governance. Two frontier AI models tested by the RegLeg Brief Specialist Panel produced confident, citable answers across six distinct questions on the October 2024 CPMI final report on linking fast payment systems across borders that the regulator's own primary text in publication d223 directly contradicts. The audit covers the count and scope of the report's oversight recommendations, the named list of public consultation respondents in Annex 1, and the distinction between the interim publication d219 and the final publication d223.
For Compliance teams at Payment Institutions working CPMI FPS interlinking governance matters, the failure pattern is operationally consequential. The audit tested six questions designed by the RLB Specialist Panel to mirror how legal, compliance, risk, operations, and board-secretariat teams at payment institutions, hub entities, and banks participating in fast payment system interlinking arrangements actually use AI on this practice area: compliance-monitoring frameworks for the d223 recommendations, internal control checklists keyed to each recommendation, regulator-engagement files on oversight expectations, and senior-management compliance reports on the FPS interlinking regime. Each question is bound to verbatim regulator-issued primary substrate.
Across the six findings the AI subjects committed, in board-style and analyst-style deliverables, to approximately ten oversight recommendations (against the seven set out in d223 Section 5.2), to consultation-respondent lists of fifteen to twenty named organisations (against the seven specific respondents recorded in d223 Annex 1), and to a scoping treatment that places the single access point gateway model inside the report's recommendations (against d223 Section 2.2, which records that the single access point is not the focus of the report).
The findings are operationally consequential for legal teams, compliance teams, risk teams, operations teams, and board secretariats at payment institutions, banks, hub entities, and FPS operators whose practice touches the October 2024 CPMI final report. A board-level briefing memo that records the report as setting out approximately ten recommendations conflates the interim d219's ten considerations with the final d223's seven recommendations and embeds that confusion into the board's understanding of the oversight regime. A legal opinion that scopes a single access point arrangement inside the d223 recommendation set creates a falsifiable regulatory-interpretation error in a partner-level deliverable.
An analyst report that lists fifteen to twenty named consultation respondents (including fabricated organisation names) attributes positions and counts to stakeholders that the regulator's Annex 1 does not record.
The audit's six findings are published with immutable RLB Citation IDs. Representative entries include RLB-H-INT-BIS-CPMI-CPMI-FPS-INTERLINKING-GOVERNANCE-2024-Q001-Opus47, RLB-H-INT-BIS-CPMI-CPMI-FPS-INTERLINKING-GOVERNANCE-2024-Q002-Sonnet46, RLB-H-INT-BIS-CPMI-CPMI-FPS-INTERLINKING-GOVERNANCE-2024-Q006-Opus47. The full audit is published at the CPMI FPS Interlinking Governance 2024 hub on RegLegBrief.com.
This is the consolidated view of findings. Click the Citation IDs or 'see details →' on any item for the full details for each finding.
For Payment Institution compliance officers on FPS interlinking governance, the AI's commitment to approximately ten oversight recommendations rather than the seven set out in CPMI d223 Section 5.2 lands directly in horizon-scanning entries, compliance committee briefings, control-plan updates, training material for first-line operations teams, and the firm's regulatory-change log. The wrong number anchors the team's planning on a fabricated compliance surface, drives over-implementation work against considerations carried over from the interim d219, and creates downstream inconsistencies between the team's d223 position and the recommendation set the regulator actually issued.
The risk concentrates in regulatory-change horizon scanning, control-plan updates, and compliance committee briefings on cross-border FPS developments, where the count is a verifiable fact that supervisors, counterparties, and internal QC reviewers will check against the source.
For Payment Institution compliance officers on FPS interlinking governance, the AI's commitment to approximately ten oversight recommendations rather than the seven set out in CPMI d223 Section 5.2 lands directly in horizon-scanning entries, compliance committee briefings, control-plan updates, training material for first-line operations teams, and the firm's regulatory-change log. The wrong number anchors the team's planning on a fabricated compliance surface, drives over-implementation work against considerations carried over from the interim d219, and creates downstream inconsistencies between the team's d223 position and the recommendation set the regulator actually issued.
The risk concentrates in regulatory-change horizon scanning, control-plan updates, and compliance committee briefings on cross-border FPS developments, where the count is a verifiable fact that supervisors, counterparties, and internal QC reviewers will check against the source.
For Payment Institution compliance officers on FPS interlinking governance, the AI's commitment to approximately ten oversight recommendations rather than the seven set out in CPMI d223 Section 5.2 lands directly in horizon-scanning entries, compliance committee briefings, control-plan updates, training material for first-line operations teams, and the firm's regulatory-change log. The wrong number anchors the team's planning on a fabricated compliance surface, drives over-implementation work against considerations carried over from the interim d219, and creates downstream inconsistencies between the team's d223 position and the recommendation set the regulator actually issued.
The risk concentrates in regulatory-change horizon scanning, control-plan updates, and compliance committee briefings on cross-border FPS developments, where the count is a verifiable fact that supervisors, counterparties, and internal QC reviewers will check against the source.
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.