public auditors of Singapore banks and financial holding companies are increasingly using AI to draft audit-planning memoranda for Singapore bank engagements, generate first-pass regulatory-capital walkthroughs against MAS Notice 637, prepare audit committee communication on the 31 December 2025 amendment effects, and reconcile FHC-level capital obligations into the engagement scoping note.
In Singapore-incorporated banks and financial holding companies the workflow shape is now consistent: a frontier AI assistant produces a clean first draft on MAS Notice 637 risk-based capital adequacy for Reporting Banks, and the reviewer is asked to spot-check the cited MAS instruments and drafting-convention claims against the regulator-issued source before the deliverable goes out. The two AI failures recorded by the RLB Specialist Panel sit precisely at that spot-check boundary.
Two frontier AI models tested by the RLB Specialist Panel on MAS Notice 637 (Amendment) 2025 produced FABRICATED_FACT errors against the regulator-issued source held as primary substrate. The first invented a sibling "Notice FHC-N637" for financial holding companies that does not appear on the MAS Notices and Directives register; the actual FHC capital framework is a separate MAS notice issued under the Financial Holding Companies Act.
The second misread the yellow-highlight convention in the MAS Notice 637 amendment PDF as visual emphasis, when the regulator's cover note states the yellow is annotation describing the change and will not appear in the published untracked Notice. Both findings sit in the same failure class: Source-Credit Fabrication, where the AI produces a confident, lawyer-shaped citation that does not exist or contradicts a regulator-stated convention. Neither AI subject hedged, flagged low confidence, or refused.
Both produced clean, deployable prose with the wrong substantive content, which is the version of AI failure that is hardest for a reviewer to catch on a fast-moving deliverable. Questions are prepared by the RLB Specialist Panel based on real practical AI usage in the workflows the respective audience uses AI for. The Panel binds each AI finding to verbatim regulator-issued source text held as primary substrate, and records the AI subject, the question class, and the operational consequence for each affected audience.
For public auditors of Singapore banks and financial holding companies the operational consequence is concrete. An audit-planning memo that routes capital testing through a fabricated MAS notice would not survive ACRA Practice Monitoring Programme review. A working paper that treats amendment annotation as substantive new Notice text would generate test designs that the engagement partner cannot defend on inspection. Both errors are direct workpaper risks tied to AI output that was not verified against the regulator's source.
The RLB Specialist Panel records each error against the underlying regulator-issued text and names the AI subject for audit transparency. The two findings carry Citation IDs RLB-H-SG-MAS-NOTICE-637-CAPITAL-ADEQUACY-BANKS-2025-Q010-Opus47 and RLB-H-SG-MAS-NOTICE-637-CAPITAL-ADEQUACY-BANKS-2025-Q012-Opus47; Claude Opus 4.7 is the AI subject in both events and the source-text excerpts are quoted verbatim in the briefing body that follows.
This is the consolidated view of findings. Click the Citation IDs or 'see details →' on any item for the full details for each finding.
Public auditors of Singapore banks and FHCs work to the actual Notice 637 framework when assessing regulatory-capital disclosures and audit committee reporting. The Opus 4.7 fabrication of a sibling "Notice FHC-N637" would, if relied on in audit planning or working papers, route capital testing through a non-existent instrument and produce a planning artefact that fails ACRA review. Auditors should treat every AI-asserted notice reference as a working-paper assertion that requires source verification against the MAS register. The audit-quality consequence of an unverified AI citation is direct and traceable in workpapers.
When public auditors review the amendment package for MAS Notice 637, the yellow-highlight convention determines which text actually becomes part of the consolidated Notice and is therefore in scope for the audit period. Opus 4.7's mischaracterisation, treating the annotation as visual emphasis, would distort the auditor's understanding of what changed, with downstream effects on test design and on the audit committee report. The regulator-stated annotation convention is on the face of the PDF and must be followed; auditors should default to the primary-source explanation, not the AI gloss.
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.