A technology architect asked what specific changes the updated CPMI ISO 20022 data requirements document (d230) made relative to the 2023 original. The response incorrectly stated d230 was published April 2026 (actual: February 2026) and fabricated specific data entity breakdowns for the technical annex, with the date error self-retracted when the AI was challenged to verify its sources.
The model placed the publication date two months late and fabricated a cited URL to support its claim, self-correcting only when challenged. The date error suggests the model reconstructed the publication details from partial training signals rather than a clean retrieval of the February 2026 document. The fabricated citation was generated to satisfy the appearance of sourcing — the model produced a URL it could not have retrieved because the URL does not exist.
The two-month date error (April vs. February 2026) that self-retracts under challenge is a reconstruction-under-uncertainty pattern: the model had insufficient training signal on the exact publication date and generated a plausible date, then supported it with a fabricated URL. The self-retraction under challenge confirms the model was not retrieving a clean date record — it was confabulating with enough confidence to pass initial scrutiny. The citation-generation step produced a fabricated URL to fill the source slot, consistent with the broader citation-pipeline gap observed in the Opus 4.7 findings.
AI assistants we tested cited an incorrect publication date for the February 2026 ISO 20022 data requirements update, sourcing an April 2026 third-party aggregator date rather than the primary BIS record, and simultaneously fabricated specific data entity breakdowns for the technical annex. A technical briefing or engineering roadmap item that carries the wrong version date misanchors the implementation timeline — teams may treat the wrong month as the operative date for when updated requirements apply, and may scope to annex-level entity obligations that the document does not actually contain.
For a Software & SaaS firm whose product touches ISO 20022 message flows, version attribution errors in internal technical documentation propagate into engineering specifications before the discrepancy surfaces.
Each finding has a stable Citation ID (RLB-F-… for aggregated case-study findings, RLB-H-… for raw per-model hallucinations) — like a DOI, the ID always resolves to the canonical finding even if URLs change.
RegLeg Specialist Panel (2026). "Finding#2 — Misstated ISO 20022 update version and fabricated annex content — Software Saas × Technology Data — International / Multilateral." Citation ID: RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q009. RegLegBrief AI Hallucination Research, published 2026-06-04. https://reglegbrief.com/regulators/j1/int/bis-cpmi/cpmi-api-harmonisation-cross-border-2024/sectors/software_saas/technology_data/finding/INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-009/
RegLeg Specialist Panel. (2026). Finding#2 — Misstated ISO 20022 update version and fabricated annex content [Hallucination finding RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q009]. RegLegBrief AI Hallucination Research. https://reglegbrief.com/regulators/j1/int/bis-cpmi/cpmi-api-harmonisation-cross-border-2024/sectors/software_saas/technology_data/finding/INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-009/
RegLeg Specialist Panel, Finding#2 — Misstated ISO 20022 update version and fabricated annex content [RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q009], RegLegBrief AI Hallucination Research (June 04, 2026), https://reglegbrief.com/regulators/j1/int/bis-cpmi/cpmi-api-harmonisation-cross-border-2024/sectors/software_saas/technology_data/finding/INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-009/.
@misc{reglegbrief_RLB_F_INT_BIS_CPMI_API_HARMONISATION_CROSS_BORDER_2024_Q009,
author = {RegLeg Specialist Panel},
title = {Finding#2 — Misstated ISO 20022 update version and fabricated annex content},
year = {2026},
publisher = {RegLegBrief AI Hallucination Research},
note = {Hallucination finding Citation ID: RLB-F-INT-BIS-CPMI-API-HARMONISATION-CROSS-BORDER-2024-Q009},
url = {https://reglegbrief.com/regulators/j1/int/bis-cpmi/cpmi-api-harmonisation-cross-border-2024/sectors/software_saas/technology_data/finding/INT-BIS-CPMI-INT-001-CPMI-API-HARMONISATION-CROSS-BORDER-2024-v1-009/}
}