AI Hallucination ResearchAudiencesSectorsSingaporeCorporate BankingTreasury › MAS Notice 637 (Amendment) 2025 - Risk Based Capital Adequacy Requirements for Banks Incorporated in Singapore
Corporate Banking × Treasury — Singapore · updated 2026-06-11 · methodology v2.3
Share / Print Twitter LinkedIn Email

AI Hallucination on MAS Notice 637 for Treasury teams at Corporate Banking firms in Singapore

Corporate Banking Treasury teams: documentation and reporting gaps possible from AI reading of MAS Notice 637

Treasury teams at Singapore corporate-banking divisions are increasingly using AI to draft capital-instrument issuance memoranda against MAS Notice 637, generate ALM working notes on the amendment effects, prepare due-diligence packages for senior and subordinated debt issuance, and update group-capital reporting templates for the consolidated Notice. 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 Treasury teams at Singapore corporate-banking divisions the operational consequence is concrete. Internal capital-structure memoranda that name a fabricated MAS notice would surface in due-diligence packages and ratings-agency dossiers, and would not resolve to any MAS register entry. Template updates that capture amendment annotation as substantive Notice text would generate reconciliation issues against the published Notice. Both errors trace 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.

<- Take me back to my Treasury x Corporate Banking (SG) overview

Executive Summary

Treasury functions at Singapore corporate banks issue capital instruments under MAS Notice 637, monitor capital adequacy ratios for the bank's funding and capital management activities, and engage with MAS on capital instrument eligibility. Across the two findings in this cell, an AI model fabricated a parallel holding-company notice and misrepresented the meaning of yellow highlighting in MAS amendment PDFs. For treasury, both failures translate into capital management positions captured against the wrong regulatory basis.

How AI gets this regulation wrong

Both findings are inference drift. The AI committed to specific answers on instrument identification and on amendment-convention reading, in cases where MAS's published text resolves the question.

AI's Failure ModeCountAffected findings
Exposed Fabrication2Finding#1 · Finding#2

What that means for your practice

For corporate banking treasury, both findings translate into capital management workstream exposure: capital instrument structuring, capital ratio monitoring, and capital management reporting that captures the wrong regulatory basis. The risk concentrates in the capital instrument issuance pipeline, where treasury produces the regulatory-basis documentation that feeds into legal opinions and disclosure.

Risk ImpactCountAffected findings
Regulatory enforcement / professional liability exposure2Finding#1 · Finding#2

When this affects Treasury teams at Corporate Banking firms

Treasury functions at corporate banks apply Notice 637 across capital instrument issuance (Tier 1 and Tier 2 instrument structuring, eligibility memoranda for MAS engagement), capital ratio monitoring, capital management reporting, and capital planning at the group level (particularly where the corporate bank operates under a Singapore financial holding company).

The two findings in this cell map onto questions a treasury team puts to an AI tool in this work. First, what MAS instrument governs capital adequacy obligations at the holding company level for the group's capital planning. The AI's fabricated parallel notice produces a citation for the planning memorandum that does not exist. Second, when reading the 2025 amendment for changes to capital instrument eligibility, how to interpret yellow highlighting. The AI's wrong reading causes treasury to capture annotation text as a live eligibility change, distorting the eligibility view that flows into the issuance pipeline.

The findings at a glance

The table below lists each finding from the AI testing on MAS Notice 637 in this cell, showing the topic, the AI's failure mode, and the citation identifier.

#Finding titleTypeCitation ID
1Fabricated 'Notice FHC-N637' for financial holding companiesHallucinationRLB-H-SG-MAS-NOTICE-637-CAPITAL-ADEQUACY-BANKS-2025-Q010-Opus47
2Misrepresented yellow-highlight meaning in MAS amendment PDFsHallucinationRLB-H-SG-MAS-NOTICE-637-CAPITAL-ADEQUACY-BANKS-2025-Q012-Opus47

Aggregate impact

Together, the two findings describe a failure mode in AI-assisted research that loads directly onto the treasury workstream. The model fabricates instruments and misreads conventions on question types that treasury research repeatedly handles in this practice. The compounding effect is in the issuance pipeline: a treasury memorandum capturing the wrong regulatory basis on instrument eligibility flows into the legal opinion, the offering document, and the regulatory engagement with MAS.

What your team should do

Treasury teams should treat AI tools as a research-prompt generator on Notice 637 work, with a mandatory verification step against MAS's published text before AI output enters an eligibility memorandum, capital plan, or regulatory submission.

Practical safeguards: (a) every MAS instrument citation in a treasury eligibility memo or capital plan must be verified against the MAS publications portal. (b) When reading the 2025 amendment for changes to capital instrument eligibility, pull paragraph 3 of the amendment for the reading convention before logging changes. (c) Anchor group-level capital planning regulatory basis on Notice 637 paragraph 11.2.2, not on AI-supplied parallel-instrument references. (d) Embed a verification gate in the issuance pipeline where regulatory-basis claims in the treasury memorandum are checked against source before legal review.

Where AI tools support treasury work in this practice: outlining eligibility memorandum structures, identifying which Parts of Notice 637 are relevant to a particular instrument's eligibility analysis, and producing first-pass summaries of amendment changes for verification against the source amendment.

How RLB Can Help

RegLeg's published Hallucination Research is available as a free pre-flight check for Singapore banking practitioners working across MAS-supervised entities. Before relying on AI-assisted output for regulatory interpretation, compliance advice, or capital-instrument structuring, practitioners can consult the research to identify where AI tools have demonstrably mis-stated the rules: invented instruments, misread editorial conventions, outdated paragraphs presented as current. The research covers specific MAS instruments and surfaces the exact questions where AI tools have failed, making it a practical reference rather than a general caution.

For firms where multiple teams are working the same regulatory portfolio, RegLeg offers bespoke deep-dives into individual MAS instruments. These engagements go beyond the published findings to examine the full pattern of AI failure modes relevant to the instrument: the question types, the failure mechanisms, and the risk implications for compliance, risk, treasury, legal, and reporting work. The output is designed to be shared across functions and used as a durable reference, reducing duplicated due-diligence effort and creating a consistent internal standard for AI-assisted regulatory work.

RegLeg also develops training and CPD-aligned content for Singapore banking teams. The material translates the failure-mode catalogue into practical guidance on the classes of error practitioners should watch for: confabulated cross-references, version confusion between superseded and current instruments, jurisdiction bleed between superficially similar regimes, and inference-driven elaboration that overstates what an instrument actually requires. Separately, RegLeg offers a confidential review of a firm's existing AI-use policy against the failure-mode catalogue, identifying gaps between the policy's assumptions and the documented evidence of how AI tools perform on Singapore prudential questions in practice.

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.