accountants advising Singapore-incorporated banks and financial holding companies are increasingly using AI to draft regulatory-capital classification notes for client banks and FHCs, generate first-pass capital-adjustment walkthroughs against MAS Notice 637, prepare client-facing summaries of the 31 December 2025 amendment effects, and update group-level capital reporting templates from the amendment package.
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 accountants advising Singapore-incorporated banks and financial holding companies the operational consequence is concrete. A classification note that cites a fabricated MAS instrument would not resolve to any MAS register entry and would attract immediate review queries from the engagement partner or ACRA. A template update that captures amendment annotation as substantive Notice content would generate reconciliation differences when the regulator releases the published untracked Notice. Both errors trace directly to AI output that was not checked against the primary MAS 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.
Accountants advising Singapore-incorporated FHCs on group capital reporting need precise instrument references when classifying regulatory adjustments and capital deductions. Opus 4.7's fabricated "Notice FHC-N637" would produce a citation in a capital reporting workpaper that does not resolve to any MAS instrument, exposing the engagement to review queries from the engagement partner or ACRA. The correct framework is MAS's separate FHC notice issued under the Financial Holding Companies Act; accountants should source notice references directly from the MAS register before incorporating them into client deliverables.
Accountants reviewing the MAS Notice 637 amendment PDFs to update group capital reporting templates rely on knowing which text legally enters the consolidated Notice. Opus 4.7's reading of the yellow as visual emphasis would cause an accountant to over-include annotation text in reporting-template updates, generating reconciliation issues against the regulator's eventual untracked publication. The annotation convention is regulator-stated on the PDF cover; treating the yellow as substantive Notice content is a documentary error that compounds across templates.
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.