ENTRY № 20 · STATUTORY READING · MAS FEAT + AIRM
PUBLISHED 2026-05-09 · ~12-MIN READ · WARRANT COMPLIANCE

MAS FEAT principles + AIRM, line by line.

The Monetary Authority of Singapore published the FEAT principles on 12 November 2018: fourteen sub-principles across Fairness, Ethics, Accountability, and Transparency, addressed to financial institutions using AI and data analytics. Six years later, the AI Model Risk Management Information Paper of December 2024 — Observations from a Thematic Review — operationalised those principles into governance, risk-management, and development-and-deployment expectations. Read together, the two documents set out what an MAS examination team will ask a Singapore FI about its production AI agents.

Warrant is regulator-grade evidence infrastructure for AI agents in regulated industries: drop an agent's execution trace, get a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.

PRINCIPLES
F · E · A · T
Fourteen sub-principles, published 12 November 2018. Applicable to all MAS-regulated FIs using AI and data analytics.
AIRM PAPER
Dec 2024· §§ 1–8
Information Paper, not a consultation. Eight sections covering oversight, risk-management systems, development and deployment, GenAI, and third-party AI.
TOOLKIT
Veritasv 2.0
MAS-led industry consortium since November 2019. Toolkit v2.0 released 26 June 2023, open source under Apache 2.0.
01 · § 1 · THE FOUR PRINCIPLES

The four principles in one paragraph.

On 12 November 2018, the Monetary Authority of Singapore released a set of generally accepted principles to promote fairness, ethics, accountability and transparency (FEAT) in the use of artificial intelligence and data analytics (AIDA) in Singapore's Financial Sector. MAS · FEAT principles · 12 November 2018 · as recorded in the PwC commentary of December 2018

The publication is short. The headline document presents fourteen numbered sub-principles, grouped under four headings, set against a one-page introduction. There is no Annex of definitions, no enforcement schedule, no penalty regime. There is the four-letter acronym. There is the addressee — financial institutions in Singapore using AI and data analytics. There is the verb the principles use throughout: should consider.

That verb is the load-bearing one. FEAT is not a Notice under section 55 of the Monetary Authority of Singapore Act. It is not a Guideline under section 27D. It is a set of generally accepted principles, addressed at the firm's internal governance framework. The MAS expectation, as set out by the PwC commentary published one month later, is that firms calibrate actions and requirements under their internal governance framework based on the materiality of the AIDA-driven decisions.

"FEAT does not bind. It calibrates. The supervisory expectation is that the firm's internal framework visibly answers each of the fourteen sub-principles, by document, by control, by audit trail."Warrant Compliance · 2026-05-09

The four principle headings, in MAS order, with the count of sub-principles under each:

F
Fairness — four sub-principles, organised as Justifiability (1 to 2) and Accuracy and Bias (3 to 4). SCOPE · individuals or groups disadvantaged by AIDA-driven decisions; data and model accuracy and bias.
E
Ethics — two sub-principles (5 to 6). SCOPE · alignment with the firm's ethical standards; equivalence with human-driven ethical baselines.
A
Accountability — five sub-principles, organised as Internal Accountability (7 to 9) and External Accountability (10 to 11). SCOPE · MAS uses the term Accountability. Not Accountability and Auditability. Auditability falls under the AIRM paper.
T
Transparency — three sub-principles (12 to 14). SCOPE · proactive disclosure to data subjects; clear explanations on data use and on consequences of AIDA-driven decisions.
02 · F · FAIRNESS

Fairness · sub-principles 1 to 4.

MAS organises the four Fairness sub-principles into two pairs. The first pair, Justifiability, addresses whether a decision can be defended after the fact. The second pair, Accuracy and Bias, addresses whether the system that produced the decision was sound at the time it produced it. The pairing matters. A decision that was sound when made can become unjustified six months later if the model has drifted or the population has shifted.

1
Individuals or groups of individuals are not systematically disadvantaged through AIDA-driven decisions, unless these decisions can be justified. IMPLICATION · the firm's internal framework must define what counts as justified. MAS does not.
2
Use of personal attributes as input factors for AIDA-driven decisions is justified. IMPLICATION · per-feature justification, not per-model. The audit trail names which attributes were used and why.
3
Data and models used for AIDA-driven decisions are regularly reviewed and validated for accuracy and relevance, and to minimise unintentional bias. IMPLICATION · review cadence and validation methodology must be documented. Regularly is the firm's call, calibrated to materiality.
4
AIDA-driven decisions are regularly reviewed so that models behave as designed and intended. IMPLICATION · this is the live-monitoring obligation. Every production model has an owner, a review schedule, and an artefact recording the last review.

The drafting choice in sub-principle 1 — unless these decisions can be justified — is the operative escape valve. Differentiation between client segments is not, in itself, prohibited. What is prohibited is unjustified systematic disadvantage. The firm's burden is the justification, recorded contemporaneously.

03 · E · ETHICS

Ethics · sub-principles 5 to 6.

The Ethics principle is two sub-principles long. It is the shortest of the four sections in the FEAT publication. The drafting takes a deliberate position: in the absence of a globally recognised ethics framework for AI, MAS pegs AI ethics to the firm's own existing ethics architecture.

5
Use of AIDA is aligned with the firm's ethical standards, values and codes of conduct. IMPLICATION · the firm cannot adopt a separate, weaker ethics standard for its AI systems. The board's existing code of conduct attaches.
6
AIDA-driven decisions are held to at least the same ethical standards as human-driven decisions. IMPLICATION · the equivalence rule. If a human relationship manager could not make a particular decision under the firm's code, an AI system cannot make it either.

Sub-principle 6 is the more enforceable of the two. It produces a concrete test the supervisor can apply: take an AIDA-driven decision the firm has made; ask whether a human, making the same decision under the same circumstances, would face disciplinary action under the firm's existing code; if yes, the AIDA-driven decision is also out of bounds. The asymmetry MAS is closing is the one where firms quietly let AI do what they would not let employees do.

04 · A · ACCOUNTABILITY

Accountability · sub-principles 7 to 11.

Accountability is the longest of the four sections by sub-principle count. MAS splits it into two halves. The first half, Internal Accountability (sub-principles 7 to 9), addresses how the firm holds itself responsible inside its own governance perimeter. The second half, External Accountability (sub-principles 10 to 11), addresses how the firm holds itself responsible to data subjects affected by its AIDA-driven decisions.

One drafting note worth flagging at the top. MAS uses the heading Accountability, not Accountability and Auditability. Some downstream commentary conflates the two. Auditability is addressed in the December 2024 AIRM paper, in Section 6.1 on standards and processes for development. The 2018 FEAT publication keeps Accountability as the standalone heading.

7
Use of AIDA in AIDA-driven decision-making is approved by the appropriate internal authority. IMPLICATION · per-use-case approval, mapped to a named approver inside the firm.
8
Firms using AIDA are accountable for both internally developed and externally sourced AIDA models. IMPLICATION · the third-party AI exception does not exist. A vendor model in production is the firm's responsibility, not the vendor's.
9
Firms using AIDA proactively raise management and Board awareness of their use of AIDA. IMPLICATION · board-level reporting on AIDA usage is expected, not optional.
10
Data subjects are provided with channels to enquire about, submit appeals for and request reviews of AIDA-driven decisions that affect them. IMPLICATION · adverse-action recourse must exist. MAS does not specify the channel.
11
Verified and relevant supplementary data provided by data subjects are taken into account when performing a review of AIDA-driven decisions. IMPLICATION · the appeal cannot be theatre. New verified evidence must be integrated into the re-review.

Sub-principle 8 is where the Singapore SaaS angle starts to bite. A Singapore-licensed bank using a foundation model from a US vendor is accountable for that model's behaviour to the same standard as if the bank had trained the model in-house. The vendor contract is a private-law artefact between two parties; the supervisory accountability runs from the bank to MAS, regardless.

05 · T · TRANSPARENCY

Transparency · sub-principles 12 to 14.

Transparency is the shortest of the four sections by word count, but the most procedurally demanding. MAS asks for three layers of disclosure: a proactive baseline disclosure to all data subjects, an on-request explanation of the data used, and an on-request explanation of the consequences. The third is the one most firms underbuild.

12
To increase public confidence, use of AIDA is proactively disclosed to data subjects as part of general communication. IMPLICATION · the firm tells the customer that AIDA is in the loop, before being asked.
13
Data subjects are provided, upon request, clear explanations on what data is used to make AIDA-driven decisions about the data subject and how the data affects the decision. IMPLICATION · per-decision explainability, in non-technical language. Counterfactual explanations are an emerging operative pattern.
14
Data subjects are provided, upon request, clear explanations on the consequences that AIDA-driven decisions may have on them. IMPLICATION · downstream consequences, not just the decision itself. A declined credit application has a credit-bureau consequence.

The PwC commentary of December 2018 noted that data subjects have similar transparency rights under EU GDPR Article 13 and Article 22. The overlap is not accidental. MAS Transparency sub-principles 13 and 14 read like a financial-sector specialisation of the GDPR right to explanation. A firm that has built its GDPR Article 13 disclosure stack already has most of FEAT 12 to 14 in place. The work is in the financial-sector specifics — the consequences disclosure under sub-principle 14, particularly.

06 · VERITAS

The Veritas consortium.

The 2018 FEAT principles defined the language. The Veritas Initiative, launched by MAS in November 2019, set out to operationalise it. The structure is an MAS-led industry consortium of, at peak, thirty-one industry players. Accenture and Bank of China were named as lead developers of the open-source Toolkit. Pilot testing was carried out by BNY Mellon, DBS Bank, OCBC Bank, and United Overseas Bank.

The Toolkit ships in two versions, both under the Apache License 2.0. Version 1.0 was released in February 2022 and covered fairness assessment only. Version 2.0 was released on 26 June 2023 and added assessment methodologies for ethics, accountability, and transparency. The toolkit is hosted on GitHub at github.com/mas-veritas2/veritastool.

What the Toolkit produces, mechanically, is per-use-case assessment notebooks — credit scoring, customer marketing, insurance underwriting — each walking an FI through the FEAT methodology and surfacing the artefacts the firm would otherwise assemble by hand. Adopting Veritas does not, in itself, satisfy FEAT. The Toolkit is an aid, not a certification. But the artefacts it produces are the closest thing to a standard format MAS has put forward.

A successor effort, Project MindForge, was established under the Veritas Initiative to address Generative AI. The first phase released a GenAI risk framework in November 2023, supported by a consortium of banks. The AIRM paper of December 2024 references both Veritas and MindForge as the operative industry-consortium efforts.

07 · AIRM

The AIRM Information Paper.

This information paper sets out good practices relating to Artificial Intelligence (AI) (including Generative AI) model risk management (MRM) that were observed during a recent thematic review of selected banks. The information paper focuses on the following key areas: AI governance and oversight; AI identification, inventorisation and risk materiality assessment; as well as AI development, validation, deployment, monitoring and change management. MAS · Artificial Intelligence Model Risk Management — Observations from a Thematic Review · § 1.1 · December 2024

The exact title is Artificial Intelligence Model Risk Management — Observations from a Thematic Review. It is dated December 2024 in the document header, and was published as an Information Paper, not a Consultation Paper. The thematic review on which it draws was conducted by MAS on selected banks in mid-2024. Section 1.2 then extends the relevance: the good practices highlighted should generally apply to other FIs, which should take reference from these when developing and deploying AI.

The structure is three thematic focus areas, each occupying its own section, with two cross-cutting Other Key Areas appended:

§4
OVERSIGHT & GOVERNANCE
Cross-functional oversight forums, updated policies and procedures, fair-ethical-accountable-transparent statements, capability building. Sets the tone.
§5
RISK-MANAGEMENT SYSTEMS
Identification (5.1), Inventory (5.2), Risk Materiality Assessment (5.3). The trio that lets the firm see what it has and what it depends on.
§6
DEVELOPMENT & DEPLOYMENT
Standards (6.1), Data Management (6.2), Development (6.3), Validation (6.4), Deployment-Monitoring-Change (6.5). The lifecycle, end to end.
§7
OTHER KEY AREAS
Generative AI (7.1) and Third-Party AI (7.2). Separate sections because the risk profile differs, not because the principles differ.

Section 6.1 is the section that introduces auditability as a development standard. The paper enumerates: data management, robustness and stability, explainability and fairness, reproducibility and auditability. Reproducibility and auditability are paired, deliberately. A model whose runs cannot be reproduced cannot be audited; a model that cannot be audited cannot be defended in front of an examination team. This is the section where Warrant's per-action evidence package maps cleanly onto MAS supervisory expectations.

Section 6.4 — Validation — distinguishes between independent validation and peer review, applied based on risk materiality. Section 6.5 — Deployment, Monitoring and Change Management — sets out pre-deployment checks and post-deployment monitoring; model updates must follow the same standards as initial deployment. A retraining cycle is not a free pass.

Section 7.1 on Generative AI flags the risk amplifications: hallucinations, opaque training-data provenance, evaluation difficulties for output bias. The paper asks FIs to extend the AIRM controls to GenAI rather than treating it as a separate regime. Section 7.2 on Third-Party AI carries the same logic — the FI's accountability does not transfer to the vendor, regardless of contract.

08 · SUPERVISORY TIER

The supervisory expectation tier.

Neither FEAT nor AIRM carries a standalone penalty regime for AI-specific failures. MAS does not, as of May 2026, have an AI-specific Notice analogous to the EU AI Act's Article 99 fine ceilings. What it has is a supervisory expectation set, enforceable through the existing examination architecture.

Three transmission mechanisms are operative. First, FEAT and AIRM expectations are read into existing risk-governance examinations. A bank's AI use is a topic an examination team can ask about, against the published principles. Second, the existing MAS Notices on outsourcing risk management, technology risk management, and individual accountability and conduct continue to apply; AIRM Section 7.2 on Third-Party AI explicitly threads through the outsourcing risk management framework. Third, MAS retains the general supervisory tools — directions, examination findings, conditions on licence — that apply to any regulated activity.

The practical posture is that an MAS-regulated FI cannot point to FEAT and say it does not bind. It binds through the supervisory channel. An examination outcome letter that flags weakness in the firm's AIDA governance, calibrated against FEAT and AIRM, is a finding the firm must remediate.

09 · FIELD MAPPING

Where Warrant maps FEAT and AIRM.

F-1, F-3
Justifiability and accuracy/bias review of AIDA-driven decisions. FIELD · trace.actions[*].justification with a per-action authorization assessment; classification.bias_indicators carried forward into the per-trace evidence rollup.
E-6
AIDA decisions held to at least the same ethical standards as human-driven decisions. FIELD · trace.actions[*].within_purpose plus the human-equivalence test recorded in the justification field.
A-7, A-8
Approval by appropriate internal authority; accountability for vendor models. FIELD · per-trace approver_id; trace.actions[*].model_provenance (internal vs. vendor; foundation model id; version pin).
A-10, A-11
External accountability — channels for review and supplementary-data ingestion. FIELD · trace.actions[*].review_record (channel, supplementary_data_received, re-review_outcome).
T-13, T-14
Explanations of data used and consequences of AIDA-driven decisions. FIELD · trace.actions[*].inputs (what data); trace.actions[*].outputs (what decision); per-trace consequence rollup for the disclosure layer.
AIRM 6.1
Reproducibility and auditability as development standards. FIELD · per-action input/output records, each a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.
AIRM 6.5
Pre-deployment checks and post-deployment monitoring. FIELD · per-trace deployment_id; evidence packages addressable by deployment, model version, and time window, independently verifiable without contacting Warrant.
AIRM 7.2
Third-Party AI accountability — vendor-sourced model still the FI's responsibility. FIELD · per-trace vendor_chain (foundation model provider, hosting jurisdiction, contract reference) carried into the FI's evidence package.
W
Sample MAS evidence package · Warrant registerINDEPENDENTLY VERIFIABLE WITHOUT CONTACTING WARRANT
→ /v/8a93cdde2a4b1f6c
10 · APAC PEERS

Cross-reference · HKMA, BNM, BoT.

The MAS AIRM paper itself, in footnote 21 to Section 4.4, names two peer-jurisdiction publications operating in adjacent space. The Hong Kong Monetary Authority issued guiding principles for the use of big data analytics and AI in 2019, covering governance and accountability, fairness, transparency and disclosure, and data privacy and protection. De Nederlandsche Bank — outside APAC, but cited by MAS in the same footnote — issued the SAFEST principles in 2019: Soundness, Accountability, Fairness, Ethics, Skills, Transparency. The acronym overlap with FEAT is deliberate.

Closer to home, the picture is patchier. Bank Negara Malaysia has not, as of May 2026, published a counterpart to FEAT, though its Risk Management in Technology policy and its 2024 discussion paper on AI in financial services touch the same themes. The Bank of Thailand issued AI-related guidance in 2024 framed as ethics and risk management expectations for FIs, but without the Singapore-style consortium-toolkit pairing. Reserve Bank of India sits in a different lineage — the FREE-AI committee report of 2025 addresses India's regulatory architecture rather than borrowing the FEAT acronym. The practical observation is that a Singapore-headquartered FI working backwards from FEAT and AIRM will generally be over-compliant with the rest of APAC; Singapore is the regional reference floor.

11 · SAAS ANGLE

The Singapore-headquartered SaaS angle.

A practical observation, addressed to the AI-vendor side of the trade. A meaningful share of AI infrastructure SaaS — model-routing, observability, evaluation, agent platforms — is incorporated in or operationally routed through Singapore. The reasons are well known: tax, talent, capital-control regime, regional headquarters logic. The consequence is less well known. FEAT and AIRM increasingly function as procurement-gate requirements for these vendors.

The mechanism is AIRM Section 7.2 on Third-Party AI, read together with FEAT sub-principle 8 on accountability for externally sourced AIDA models. An MAS-regulated FI evaluating an AI vendor must satisfy itself that the vendor's product can be operated within the FI's FEAT and AIRM controls. The vendor that cannot show how its product enables the FI's reproducibility, auditability, and per-decision explainability obligations is the vendor that loses the procurement.

The shift over the last eighteen months is from does the vendor have a SOC 2 report to does the vendor's product produce evidence the FI's MAS examination team can read. A SOC 2 report covers the vendor's own controls. A per-action evidence package, addressable by deployment and model version and independently verifiable without contacting Warrant, covers the FI's controls — which is what AIRM Section 6.5 actually asks for. The EU AI Act's Article 12 logging obligation and the AIRM Section 6.1 reproducibility-and-auditability standard are not in conflict; an evidence architecture that satisfies one largely satisfies the other. The vendor that ships one product with one evidence layer covers both markets.

12 · FAQ

Questions a compliance officer asks first.

Are the FEAT principles legally binding on financial institutions in Singapore?

No. The FEAT principles are non-binding guidance. The 12 November 2018 publication describes a set of generally accepted principles that firms should consider when assessing or developing internal frameworks to govern the use of AI and data analytics. They do not carry the force of an MAS Notice. They do, however, sit inside the supervisory expectation set, and an examination team can ask how a firm's internal governance framework calibrates to them. A firm that ignores FEAT is not breaching a Notice; it is opening up an examination finding.

What does FEAT stand for and how many sub-principles are there?

FEAT stands for Fairness, Ethics, Accountability, and Transparency. There are fourteen sub-principles. Fairness has four, split into Justifiability (1 to 2) and Accuracy and Bias (3 to 4). Ethics has two (5 to 6). Accountability has five, split into Internal Accountability (7 to 9) and External Accountability (10 to 11). Transparency has three (12 to 14). MAS uses the terminology Accountability, not Accountability and Auditability — auditability is addressed separately in the December 2024 AIRM paper.

Does FEAT use the term "Accountability" or "Accountability and Auditability"?

MAS uses Accountability as the standalone heading in the 12 November 2018 FEAT publication. Sub-principles 7 to 11 fall under this single heading, split into Internal Accountability (7 to 9) and External Accountability (10 to 11). Auditability is addressed six years later, in the December 2024 AIRM Information Paper, where Section 6.1 enumerates the development standards as data management, robustness and stability, explainability and fairness, reproducibility and auditability. Reproducibility and auditability are paired in AIRM as a development obligation, not built into the FEAT acronym.

What is the AIRM Information Paper and when was it published?

The MAS Artificial Intelligence Model Risk Management Information Paper, subtitled Observations from a Thematic Review, was published in December 2024. The thematic review was conducted on selected banks in mid-2024. It is structured in eight sections plus two annexes. Sections 4 to 6 carry the substantive content, organised around three thematic focus areas: Oversight and Governance, Key Risk Management Systems and Processes, and Development and Deployment. Sections 7.1 and 7.2 add Generative AI and Third-Party AI as cross-cutting topics.

Does the AIRM paper apply only to banks?

The thematic review focused on selected banks, but Section 1.2 of the paper states that the good practices highlighted should generally apply to other financial institutions, which should take reference from these when developing and deploying AI. In practice, an MAS examination team reading the AIRM paper against an insurer or an asset manager will adjust for sector specifics but apply the same governance, identification, validation, and monitoring expectations.

What is the Veritas Initiative and what version of the Toolkit is current?

The Veritas Initiative is an MAS-led industry consortium launched in November 2019 to support FIs in operationalising the FEAT principles. The consortium has comprised, at peak, thirty-one industry players, with Accenture and Bank of China as lead developers and BNY Mellon, DBS, OCBC, and UOB among the pilot testers. The Veritas Toolkit version 1.0 was released in February 2022 covering fairness assessment. Version 2.0 was released on 26 June 2023 and added assessment methodologies for ethics, accountability, and transparency. The toolkit is open source under Apache License 2.0, hosted at github.com/mas-veritas2/veritastool. A successor effort, Project MindForge, addresses Generative AI specifically and released its first risk framework in November 2023.

How do FEAT and AIRM interact with the EU AI Act for a Singapore-headquartered SaaS vendor?

They sit alongside it. A Singapore-headquartered SaaS vendor selling into a regulated EU customer faces the EU AI Act through its customer's high-risk AI system perimeter. The same vendor selling into an MAS-regulated FI is read against FEAT and AIRM through the customer's third-party AI risk management. The two regimes are not in conflict. They overlap on transparency, accountability, validation, and monitoring. A vendor whose product produces per-action evidence that is independently verifiable without contacting Warrant satisfies the substantive requirements of both. A vendor whose product does not, fails both.

How does Warrant produce evidence mapped to FEAT and AIRM?

Drop the AI agent's execution trace at warrant.build/demo. Warrant produces a PDF mapping per-action evidence to FEAT sub-principles 1 to 14 and to AIRM sections 4 to 6, with cross-references where AIRM Section 7 applies. Each entry is a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant at warrant.build/verify.

· READ THE SOURCE

Read the source directly.

Authored by Warrant Compliance, the regulatory-analysis function at Warrant. [email protected]. Editorial commentary on regulatory text. Not legal advice. The verbatim quotation of FEAT sub-principles 1 to 14 reflects the published text as recorded in the PwC commentary of December 2018, which footnoted the original MAS press release of 12 November 2018. The verbatim quotation of AIRM Section 1.1 reflects the December 2024 MAS Information Paper PDF read directly. Where the mas.gov.sg primary URLs were intermittently in maintenance during drafting, the PwC December 2018 commentary and the AIRM PDF mirror at the Rajah & Tann AI Toolkit served as cross-checked sources.