Skip to main content
Back to Investment Decisions: Data-Driven and Faster
Lesson 4 of 5

Stay Ahead of Compliance and Trust

~26 min readLast reviewed May 2026

Regulatory and Ethical AI in Finance

Part 1: When AI Gets It Wrong, and Who Pays the Price

2023

Historical Record

Goldman Sachs

In 2023, Goldman Sachs' Apple Card algorithm was found to offer significantly lower credit limits to women than to men with comparable financial profiles.

This case illustrated how AI systems can inherit and amplify historical biases at scale in financial services.

This case captures the central tension of AI in finance. The tools are genuinely powerful. They process credit applications in seconds, flag fraud before it clears, and surface investment opportunities that human analyzts would miss. But they also inherit the biases baked into historical data, operate in ways that even their creators struggle to explain, and make decisions at a scale and speed that makes human oversight extremely difficult. Goldman's compliance team wasn't negligent. Their legal team wasn't asleep. The problem was that no one had asked the model to show its work, and no regulatory framework at the time required them to.

That regulatory gap is closing fast. The EU AI Act, which began phasing in from 2024, classifies credit scoring and financial risk assessment as high-risk AI applications, subject to mandatory transparency requirements and human oversight rules. The U.S. Consumer Financial Protection Bureau issued guidance in 2023 stating that lenders cannot use "black box" AI models as the sole basis for adverse credit decisions, they must be able to explain the reasons to applicants. If you work in financial services, insurance, lending, investment advisory, or any adjacent field, these rules affect what tools you can use, how you can use them, and what you have to document when things go wrong.

The Regulatory Landscape Is Moving Quickly

Three frameworks currently shape AI use in finance: the EU AI Act (2024, phased enforcement through 2027), the CFPB's AI lending guidance (2023), and the SEC's evolving rules on AI-generated investment advice (proposed 2023, ongoing). If your firm operates internationally, all three may apply to you simultaneously. None of them require you to avoid AI, they require you to use it responsibly, with documentation and human review built into the process.

The Principle Behind the Story

The Goldman case illustrates a principle that runs through every AI ethics conversation in finance: AI models don't discriminate on purpose, but they can discriminate at scale. A human loan officer who harbored bias affected dozens of applicants a year. An AI model running the same bias affects millions of applications a month, silently, consistently, and with a veneer of mathematical objectivity that makes the bias harder to challenge. This is what regulators mean when they talk about "algorithmic accountability", the idea that the organizations deploying AI are responsible for its outcomes, not just its intentions. The model being the decision-maker is not a legal defense. It's a liability.

For non-technical professionals, this principle has a very practical implication. You don't need to understand how a neural network weights its inputs. But you do need to understand what your AI tool is being asked to decide, what data it's drawing on, and whether a human with relevant expertise is reviewing outcomes before they affect real people or real money. These are management and governance questions, not engineering questions. The compliance officer, the HR director approving AI-assisted hiring in financial services, the marketing manager using AI to segment loan product audiences, all of these people are inside the regulatory perimeter now.

How Bias Travels from Data to Decision

Think about how a credit-scoring AI gets built. A team feeds it millions of past loan records: who applied, who was approved, who repaid, who defaulted. The model finds patterns. If historically certain zip codes had higher default rates, zip codes that, due to decades of redlining, correlate with race, the model learns to penalize applicants from those areas. It never sees race directly. It doesn't need to. Zip code, purchasing patterns, the type of phone used to apply, these become proxies. The model isn't racist in any intentional sense. It's a very accurate mirror of a racist history, and accuracy is exactly the problem.

This is called proxy discrimination, and it's one of the most common ways AI produces biased outcomes in finance. The same dynamic plays out in insurance pricing, fraud detection, and investment product recommendations. An insurance AI trained on claims data might charge higher premiums to people who buy their policies online rather than through a broker, not because online buyers are riskier, but because the historical data reflects that lower-income customers disproportionately used online channels, and lower-income customers had more claims. The pattern is real. The causal story is wrong. And the AI doesn't know the difference.

When you use an AI tool to assist with financial decisions, even something as simple as asking ChatGPT or Microsoft Copilot to help draft a client risk profile, or using a vendor's AI scoring tool for SME loan applications, you are touching this territory. The question you need to ask isn't just "Is this output accurate?" It's "What assumptions are baked into this output, and could those assumptions disadvantage a protected class of people?" That question doesn't require a data science degree. It requires professional judgment, which is exactly why regulators are insisting that humans stay in the loop.

Asking an AI to Flag Potential Bias in a Credit Decision Process

Prompt

I manage a small business lending team at a regional bank. We've started using an AI-assisted scoring tool that ranks loan applicants. I want to make sure we're not inadvertently discriminating against applicants. Can you help me write a checklist of questions I should be asking our vendor and reviewing with my team each quarter to stay on the right side of fair lending laws?

AI Response

Absolutely, here's a quarterly fair lending review checklist you can use with your vendor and your team: **Vendor Accountability Questions** 1. What data variables does the model use to generate scores? Ask for a full variable list in plain English, not technical documentation. 2. Has the model been tested for disparate impact across race, gender, national origin, and age? Ask for the most recent fairness audit report and the date it was conducted. 3. If an applicant is declined, can the model produce a plain-language explanation of the top reasons? This is now required under CFPB guidance for adverse action notices. 4. How often is the model retrained, and on what data? Models trained on pre-2010 data may reflect lending patterns from before the Fair Housing Act's modern enforcement era. **Internal Team Review Questions** 5. Are we reviewing approval and denial rates by demographic group at least quarterly? You don't need sophisticated software, a spreadsheet comparison is a starting point. 6. Is a human loan officer reviewing every AI-flagged denial before it becomes a final decision? Document this review in the loan file. 7. Have our loan officers received training on how to interpret and, when appropriate, override AI scores? 8. Do we have a documented process for applicants to request reconsideration if they believe the AI score was incorrect? **Red Flags to Watch** - Approval rates that differ by more than 10–15 percentage points between demographic groups with similar financial profiles. - Vendor inability or unwillingness to explain model variables. - No audit trail showing human review of AI-flagged decisions. Review this checklist with your compliance officer before your next vendor contract renewal.

A Different Industry, the Same Problem: Insurance in the UK

Admiral Insurance, one of the UK's largest car insurers, made headlines in 2016 when it announced a product called FirstRate, an AI tool that would analyze Facebook posts to assess the personality traits of young drivers and adjust their premiums accordingly. Careful, organized writers would get lower rates. Impulsive, overconfident social media behavior would cost more. The UK's Information Commissioner's Office stepped in before the product launched, ruling that Facebook's terms of service didn't allow personal data to be used this way without explicit consent. Admiral pulled the product. But the underlying idea, using AI to find unconventional data signals for financial risk assessment, didn't go away. It went underground, into less visible product features and vendor tools that aren't publicly announced.

The Admiral case shows that the ethical and regulatory risks of AI in finance aren't limited to lending. Insurance pricing, fraud scoring, investment suitability assessments, any time an AI model is making or heavily influencing a financial decision about a person, the same questions apply: What data is it using? Has that data been consented to? Could it produce outcomes that are unfair to protected groups? And critically: does the person affected have any way to understand or challenge the decision? For professionals in these fields, the practical takeaway isn't to avoid AI tools. It's to ask these questions of every vendor you work with, every tool your firm deploys, and every workflow where AI output influences a consequential decision.

AI Use CaseRegulatory Risk LevelKey RegulationHuman Review Required?Explainability Required?
Credit scoring / loan decisionsHighCFPB AI Guidance (US), EU AI ActYes, before adverse actionYes, plain-language reasons
Insurance pricing modelsHighFCA (UK), state insurance regulators (US)Yes, for rate exceptionsYes, on request
Investment product recommendationsHighSEC Reg BI, MiFID II (EU)Yes, suitability reviewYes, must document rationale
Fraud detection / transaction flaggingMediumGDPR, FCRAYes, before account actionPartial, reason codes required
Customer segmentation for marketingMediumGDPR, CCPA, FTC guidanceRecommendedNot mandated but best practice
Internal financial reporting / analyzisLowStandard audit requirementsStandard approval workflowNot mandated
Meeting summaries / email draftingLowData privacy policiesStandard editorial reviewNot applicable
AI use cases in finance ranked by regulatory risk level. 'Human Review Required' refers to regulatory expectation, not just best practice. Check with your compliance team for jurisdiction-specific rules.

The Compliance Officer's Dilemma: A Story from Asset Management

A compliance officer at a mid-sized asset management firm in Chicago, let's call her Sarah, faced a practical version of this problem in late 2023. Her firm's portfolio managers had started using ChatGPT Plus to help draft client investment commentary: the quarterly letters that go out to high-net-worth clients explaining portfolio performance and outlook. The quality improved noticeably. The letters were clearer, better structured, and took a fraction of the time to produce. Then Sarah's phone rang. A client's attorney was asking whether the investment commentary their client received constituted regulated investment advice, and if so, whether it had been produced by a system that met the SEC's recordkeeping requirements for electronic communications. Sarah didn't have a clean answer.

The SEC's recordkeeping rules require that all business-related electronic communications at registered investment advisers be archived and available for examination. ChatGPT conversations, unless routed through a compliant enterprise system, typically don't meet that standard. Sarah's firm hadn't broken any rules yet, no enforcement action was taken, but the conversation forced a policy decision. They moved to Microsoft Copilot for Microsoft 365, which integrates with their existing compliance archiving system, and established a formal policy: AI can draft, a human portfolio manager must review and approve, and the final approved text is what gets archived. The AI's draft is a working document, not a business record. This kind of policy, specific, documented, auditable, is exactly what regulators are asking for.

The Archiving Question Is the First Question

Before your team uses any AI tool for client-facing financial communications, ask your IT or compliance team one question: 'Does this tool integrate with our approved archiving system?' For firms using Microsoft 365, Copilot generally does. For standalone tools like ChatGPT or Claude accessed through a browser, the answer is usually no, unless you're on an enterprise plan with specific data retention agreements. Using the wrong tool for a regulated communication isn't just a compliance risk. It's an audit finding waiting to happen.

Putting It Into Practice: What Governance Actually Looks Like

The stories above. Goldman, Admiral, Sarah's asset management firm, aren't cautionary tales about avoiding AI. They're blueprints for what to build around AI use. In each case, the problem wasn't the tool. It was the absence of a governance structure: documented policies about what the tool can be used for, who reviews its outputs, how decisions get recorded, and what happens when something goes wrong. Building that structure doesn't require a technology team. It requires the people who actually use the tools, compliance officers, team managers, department heads, to ask a set of deliberate questions before a new AI workflow goes live.

Start with the decision. Ask: what is this AI tool actually deciding, or heavily influencing? If the answer involves a financial outcome for a client or customer, a rate, a limit, a recommendation, a denial, you're in regulated territory. Document that. Then ask: who is reviewing the AI's output before it becomes final? That reviewer needs to have the expertise to catch errors and the authority to override the AI. "The AI said so" is not an adequate compliance record. The reviewer's name, their assessment, and the date of their review should be in the file.

Finally, ask: what happens when we get it wrong? AI systems make errors. Models drift over time as the world changes but the training data doesn't. A fraud detection model trained in 2020 may perform poorly on 2024 transaction patterns. Your governance structure needs a feedback loop: a regular review of AI-assisted decisions to check for patterns of error, a process for clients or customers to flag incorrect outcomes, and a clear escalation path when the AI produces something that doesn't pass the smell test. None of this is exotic compliance infrastructure. It's the same discipline you'd apply to any high-stakes business process, with the added urgency that AI operates at a scale and speed where errors compound quickly.

Build a One-Page AI Governance Snapshot for Your Team

Goal: Produce a one-page AI governance snapshot that documents your team's current AI tool use, assigns risk levels to each use, identifies responsible reviewers, and flags gaps that need to be addressed. This document becomes the foundation of your team's AI compliance posture.

1. Open a blank document in Word, Google Docs, or Notion. Title it 'AI Use Policy, [Your Team Name], [Date]'. 2. List every AI tool your team currently uses, include ChatGPT, Copilot, Gemini, Grammarly AI, any vendor-supplied AI scoring or analytics tools. Be specific about which version (e.g., ChatGPT Plus, Microsoft Copilot for Microsoft 365). 3. For each tool, write one sentence describing what your team uses it for. Example: 'ChatGPT Plus, drafting first versions of client quarterly reports.' 4. Next to each use, classify it using the table from this lesson: High Risk, Medium Risk, or Low Risk based on whether it influences a financial decision affecting clients or customers. 5. For any tool classified as High or Medium Risk, write the name of the person responsible for reviewing AI outputs before they become final. If no one is currently assigned, write 'TBD, assign by [date].' 6. Write two sentences describing where the final approved output gets stored and whether that storage meets your firm's archiving requirements. If you're unsure, note that you need to check with IT or compliance. 7. Add a 'Known Gaps' section. List any AI uses where you don't currently have a clear review process, an assigned reviewer, or compliant storage. These are your action items. 8. Share the document with your manager or compliance contact and ask for a 30-minute review meeting within the next two weeks. 9. Set a calendar reminder to update this document every six months, or whenever your team adopts a new AI tool.

Key Lessons from Part 1

  1. AI bias in finance is usually not intentional, it's inherited from historical data that reflected past discrimination. The model doesn't need to 'see' race or gender to discriminate by proxy.
  2. Regulatory frameworks are now treating credit scoring, insurance pricing, and investment recommendations as high-risk AI applications, with mandatory transparency and human oversight requirements.
  3. The CFPB requires lenders to provide plain-language explanations for AI-assisted adverse decisions. 'The model said no' is not a legally adequate reason.
  4. The EU AI Act, phasing in through 2027, creates a compliance obligation for any firm operating in European markets, regardless of where the AI tool was built.
  5. Archiving and recordkeeping requirements apply to AI-assisted client communications at regulated firms. Not all AI tools meet these requirements by default.
  6. Governance isn't a technology problem, it's a management problem. The key questions (what is it deciding, who reviews it, what gets documented) are answered by business professionals, not engineers.
  7. AI errors compound at scale. A human making a biased decision affects a handful of people. An AI model running the same bias affects millions, silently and consistently.

When Algorithms Make Lending Decisions: The Bias Problem in Plain Sight

In 2019, Apple launched the Apple Card with Goldman Sachs as its banking partner. Within days, Twitter lit up with complaints. Tech entrepreneur David Heinemeier Hansson posted that his wife received a credit limit twenty times lower than his, despite having a higher credit score. Apple co-founder Steve Wozniak reported the same pattern with his wife. Goldman Sachs insisted the algorithm treated everyone equally and used no gender data. But "no gender data" is not the same as "no gender bias." The algorithm had been trained on historical credit data, data generated in a world where women historically had less access to credit, lower incomes on average, and different borrowing patterns. The bias was baked into the training data before a single line of code was written.

New York's Department of Financial Services launched an investigation. Goldman Sachs faced intense public scrutiny. The episode crystallized something that compliance officers, risk managers, and product leaders in financial services now have to grapple with directly: AI systems can discriminate without anyone intending discrimination. The Equal Credit Opportunity Act (ECOA) prohibits lending decisions based on sex, race, national origin, and several other protected characteristics. But ECOA was written for human decision-makers. When an algorithm makes ten million credit decisions a day, auditing for compliance becomes a fundamentally different challenge, and "the algorithm decided" is not a legal defense.

The principle the Apple Card episode forces into focus is this: AI in finance inherits the inequities of the past unless someone actively works to prevent it. The data that trains these models reflects decades of human decisions, some discriminatory, some structurally unfair, some just shaped by unequal access to opportunity. If you feed that data into a model uncritically, the model learns those patterns and reproduces them at scale. For finance professionals using AI tools, whether for credit analyzis, hiring, fraud detection, or customer segmentation, understanding this inheritance is not optional. It is a core competency.

What "Disparate Impact" Means for AI Tools

Under U.S. fair lending law, a practice is illegal if it produces a disparate impact on a protected class, even without any discriminatory intent. This doctrine applies to AI-driven decisions. If your AI tool approves loans at significantly different rates for different racial groups, that gap itself triggers legal scrutiny, regardless of whether race was an input variable. The Consumer Financial Protection Bureau (CFPB) has explicitly stated that ECOA applies to algorithmic credit decisions. Finance teams using AI for any customer-facing decision need to understand this framework before deployment.

The Explainability Problem: Why "The Model Said So" Isn't Enough

Imagine you're a loan officer at a regional bank. A small business owner applies for a $250,000 expansion loan. Your AI-assisted underwriting tool flags the application as high risk and recommends denial. The business owner asks why. You open the tool's interface and see a risk score of 67 out of 100, but no breakdown of which factors drove that score. You cannot explain the decision to the applicant. More importantly, under the Fair Credit Reporting Act and Regulation B, you are legally required to provide adverse action notices that give specific, intelligible reasons for credit denial. "The algorithm gave a low score" does not satisfy that requirement.

This is the explainability problem, and it sits at the intersection of ethics, law, and practical business operations. Many of the most powerful AI models used in finance, particularly deep learning models, operate as what researchers call "black boxes." They produce accurate predictions, but the internal reasoning is opaque even to their creators. Regulators in the EU have taken the hardest line on this: the AI Act classifies credit scoring as a high-risk AI application, requiring providers to ensure transparency, human oversight, and the ability to explain outputs. The UK's Financial Conduct Authority has issued similar guidance. In the U.S., the CFPB has signaled that explainability is a live compliance issue, not a future concern.

For finance professionals, the practical takeaway is not to avoid AI tools but to demand explainability as a procurement criterion. When your organization evaluates an AI underwriting tool, fraud detection system, or investment screening platform, explainability should be a non-negotiable feature, not an upgrade tier. Ask vendors specifically: Can this system produce human-readable explanations for individual decisions? Can those explanations hold up to regulatory review? If a vendor cannot answer those questions clearly, that is a significant red flag. The tools that will survive regulatory scrutiny are the ones built with explainability as a design principle, not an afterthought.

Compliance Manager. Drafting an AI Vendor Assessment Question Set

Prompt

I'm a compliance manager at a mid-sized bank. We're evaluating an AI-powered loan underwriting system from a third-party vendor. I need to create a list of due diligence questions focused on regulatory compliance, explainability, and bias risk. The questions should be things I can ask in a vendor meeting, not technical deep dives, but substantive enough to reveal whether the vendor takes these issues seriously. We operate under ECOA, the Fair Credit Reporting Act, and are watching the CFPB's AI guidance closely.

AI Response

Here are twelve due diligence questions for your vendor evaluation meeting: **Explainability and Adverse Action** 1. Can your system generate specific, reason-code-based explanations for each individual credit decision, explanations that meet Regulation B adverse action notice requirements? 2. Have those explanations been reviewed by legal counsel for FCRA and ECOA compliance? 3. Can your system produce explanations that a loan officer with no data science background can read and communicate to an applicant? **Bias Testing and Fair Lending** 4. What disparate impact testing do you conduct before deploying a model, and how often is it repeated after deployment? 5. Which protected classes do you test for under ECOA (sex, race, national origin, religion, marital status, age, receipt of public assistance)? 6. If testing reveals a disparate impact, what is your process for remediation? **Model Governance** 7. How frequently are your models retrained, and who approves model updates? 8. Do you maintain model cards or documentation that describes training data sources, known limitations, and intended use cases? 9. What is your process for detecting model drift, when the model's real-world performance diverges from its training performance? **Oversight and Human Review** 10. Is there a mechanism for human review to override the system's recommendation on any individual application? 11. What audit logs does the system maintain, and how long are they retained? 12. Have your models been reviewed or approved by any banking regulator, or have you received any regulatory feedback on their use?

Healthcare Finance Shows What Biased Training Data Costs in Practice

The bias problem is not unique to consumer lending, it runs through any sector where AI makes high-stakes recommendations based on historical data. In 2019, researchers published a landmark study in Science exposing a widely used healthcare algorithm that systematically underestimated the medical needs of Black patients. The algorithm used healthcare spending as a proxy for health needs. Because systemic inequities meant Black patients had historically spent less on healthcare, not because they were healthier, but because they had less access, the algorithm concluded they needed less care. Optum, the company behind the algorithm, acknowledged the findings and committed to changes. The algorithm had been used by major insurers and hospital systems affecting tens of millions of patients.

The financial services parallel is direct. When AI tools use proxies, zip code, educational history, social connections, purchase patterns, they can encode racial or socioeconomic bias without ever asking for race or income directly. This is sometimes called "proxy discrimination." A credit model that penalizes applicants who shop at certain stores, live in certain neighborhoods, or have certain employment histories may be producing racially disparate outcomes through entirely race-neutral-looking inputs. For finance professionals, this means you cannot evaluate an AI tool's fairness simply by checking whether protected characteristics appear in the input data. You have to look at outcomes, and that requires testing, not just trust.

Comparing Regulatory Approaches: What Finance Teams Need to Know

JurisdictionKey Regulation/FrameworkScope for Finance AIExplainability RequirementEnforcement BodyStatus (2024)
European UnionEU AI ActCredit scoring classified as high-risk AIMandatory for high-risk applicationsNational market surveillance authoritiesIn force, phased implementation through 2027
United StatesECOA / Regulation B + CFPB GuidanceApplies to all algorithmic credit decisionsRequired via adverse action noticesCFPB, OCC, Federal ReserveExisting law; active enforcement; no comprehensive AI law yet
United StatesFair Housing ActAI-driven mortgage and rental decisionsDisparate impact standard appliesHUD, DOJExisting law; active litigation
United KingdomFCA AI Principles + ICO GuidanceConsumer credit, investment advice, insuranceStrongly recommended; guidance-basedFinancial Conduct Authority, ICOPrinciples-based; binding rules expected
CanadaArtificial Intelligence and Data Act (AIDA)High-impact AI systems including financial servicesRequired for high-impact systemsMinister of Innovation, Science and IndustryProposed; not yet enacted as of 2024
SingaporeMAS FEAT PrinciplesAll AI/ML used in financial servicesFairness, Ethics, Accountability, Transparency requiredMonetary Authority of SingaporeIn force, industry guidance
Regulatory landscape for AI in financial services across major jurisdictions, 2024. Finance teams operating internationally must map their AI tools against each relevant framework.

A Human Resources Director Learns That Hiring AI Has a Compliance Footprint Too

Consider the position of a Head of Talent Acquisition at a global investment bank. Her team processes over 40,000 job applications a year. In 2022, her firm piloted an AI resume screening tool to handle first-round filtering. Six months in, the firm's legal team flagged a problem: the tool had been trained on ten years of successful hires at the firm. The firm's historical hiring had skewed heavily toward candidates from a small set of elite universities, a pattern that, when mapped against demographic data, correlated strongly with race and socioeconomic background. The tool had learned to replicate that pattern. Amazon famously scrapped a similar tool in 2018 after discovering it systematically downranked resumes that included the word "women's", as in "women's chess club." The lesson repeated itself, at scale, across the industry.

The compliance implication for finance firms is significant. In the U.S., AI hiring tools fall under Title VII of the Civil Rights Act. The EEOC issued guidance in 2023 specifically addressing algorithmic discrimination in hiring, stating that employers remain liable for discriminatory outcomes even when those outcomes are produced by a vendor's tool. New York City's Local Law 144, which took effect in 2023, requires employers using AI hiring tools to conduct annual bias audits and publish the results. For finance professionals in HR, talent, or people operations roles, this is a live compliance obligation, not a hypothetical future risk. Auditing the AI tools your firm uses for hiring is now part of the job.

Monday Morning Action: Map Your AI Tools to Compliance Risk

Start a simple spreadsheet this week. List every AI tool your team currently uses that touches a decision about a person, a customer, a job applicant, a borrower, an investor. For each tool, note: (1) What decision does it inform? (2) Who is affected? (3) Can you explain its output in plain language? (4) Has anyone tested it for disparate impact? You don't need to be a data scientist to do this audit. You just need to ask the questions. Most compliance gaps in AI start with no one having asked these basic questions at all.

Turning Ethical Principles into Practical AI Policy

Ethics frameworks for AI, fairness, accountability, transparency, explainability, can sound abstract until you connect them to specific decisions your team makes every week. Take transparency. In practice, transparency means your team knows which AI tools are being used, what data they process, and what decisions they influence. It means customers know when an AI has assessed their creditworthiness. It means your board or audit committee can get a clear answer to "what AI are we using and how are we governing it?" Most firms that have faced regulatory action over AI were not operating in bad faith, they simply had no governance structure that made these questions answerable. Transparency starts with documentation, not philosophy.

Accountability is equally concrete. It means someone in your organization owns the answer to "what happens when this AI tool gets it wrong?" Not the vendor. Not "the algorithm." A named person or team who reviews exceptions, handles complaints, and has the authority to override the system. The EU AI Act calls this a "human oversight" requirement for high-risk applications. But even where it is not legally mandated, having a clear escalation path for AI-driven decisions is basic operational hygiene. For finance teams, this might mean designating a model risk officer, ensuring loan officers can flag and override AI recommendations, or establishing a formal review process for AI-generated investment signals before they reach clients.

Fairness in practice means building testing into your workflow, not just at deployment, but continuously. Models drift. The world changes. A model trained on pre-pandemic lending data may behave differently in a post-pandemic economy. A fraud detection model trained on one geography may perform poorly in another. Ongoing monitoring is not a technical nicety, it is what separates firms that catch problems early from firms that discover them in a regulatory examination or a news story. Finance professionals do not need to run the tests themselves, but they do need to ask their vendors and data teams: how often is this model's fairness performance reviewed, and who sees the results?

Conduct an AI Ethics Spot-Check for One Finance Tool Your Team Uses

Goal: By completing this task, you will have conducted a real compliance spot-check on an AI tool your organization already uses, produced a shareable summary of findings, and taken a concrete governance action, all without requiring any technical expertise.

1. Identify one AI tool your team currently uses that influences a financial or people-related decision, this could be a credit scoring tool, a customer risk classifier, a fraud alert system, a hiring screen, or an AI-generated investment report. 2. Open ChatGPT, Claude, or Microsoft Copilot and paste the following: 'I use [tool name] for [describe the decision it informs]. Help me draft five questions I should ask my vendor about bias risk, explainability, and regulatory compliance for this specific use case.' 3. Review the AI-generated questions. Edit or add any questions specific to your regulatory environment (e.g., ECOA if it is a credit tool, EEOC if it is a hiring tool). 4. Schedule a 30-minute meeting with either your vendor contact or your internal IT/data team and bring those questions. 5. During the meeting, take notes on which questions they could answer clearly, which they struggled with, and which they had never been asked before. 6. After the meeting, use an AI tool to help you draft a brief summary (one page maximum) of what you learned, noting any compliance gaps or areas needing follow-up. 7. Share that summary with one stakeholder: your manager, your compliance officer, or your team lead. 8. Based on the responses, identify one concrete next step, whether that is requesting a vendor audit report, escalating a concern to legal, or proposing a formal AI governance review. 9. Save all notes and outputs in a dedicated folder labeled 'AI Governance Audit', this becomes the foundation of your team's AI risk documentation.

Key Principles from Part 2

  1. AI systems inherit historical bias from their training data, even when protected characteristics are not explicit inputs. The Apple Card case shows that "no gender data" does not guarantee gender-neutral outcomes.
  2. Explainability is a legal requirement in financial services, not just an ethical preference. Adverse action notices under Regulation B require specific, intelligible reasons, "the model scored you low" does not comply.
  3. Proxy discrimination is real and common. AI tools that use zip code, purchase history, or educational pedigree as inputs can produce racially disparate outcomes through entirely race-neutral-looking variables.
  4. Regulatory frameworks vary significantly by jurisdiction. Finance teams operating internationally must map their AI tools against the EU AI Act, CFPB guidance, FCA principles, and MAS FEAT simultaneously.
  5. Hiring AI carries its own compliance footprint. Employers, not vendors, bear liability for discriminatory outcomes from AI hiring tools under U.S. law, and New York City now requires annual bias audits.
  6. Transparency means documentation and disclosure, not just intention. A firm that cannot answer 'what AI are we using and how are we governing it?' is already exposed to regulatory risk.
  7. Accountability requires a named human owner for AI-driven decisions, someone who can review exceptions, handle complaints, and override the system when needed.
  8. Continuous monitoring is not optional. Models drift over time, and a tool that was fair at deployment may produce biased or inaccurate outputs months later without anyone noticing.

When the Algorithm Gets It Wrong: Accountability in AI-Driven Finance

In 2023, the Dutch financial regulator AFM investigated a consumer lending platform that had quietly embedded an AI credit-scoring model into its approval pipeline. The model had been trained on historical loan data, data that reflected decades of lending bias. The result: applicants from certain postal codes were denied credit at nearly twice the rate of demographically similar applicants elsewhere. Nobody had programmed discrimination into the system. The bias emerged from patterns in old decisions, and the AI faithfully reproduced them at scale. By the time the regulator intervened, tens of thousands of applicants had been affected.

What made this case particularly instructive was the company's initial defense: the model was a third-party tool, and no human had made the discriminatory decisions. The regulator disagreed. Under EU financial services law, outsourcing a decision to an algorithm does not outsource the legal and ethical responsibility for that decision. The firm, not the vendor, was accountable. This is the core tension that every finance professional using AI tools must understand: AI can scale your capabilities, but it also scales your accountability.

The principle extracted from this case is straightforward and non-negotiable. When AI touches a consequential financial decision, a credit denial, a risk flag, a compliance report, a human professional remains responsible for the outcome. That is not a limitation of AI. It is a feature of a functioning financial system. Your job is not to be suspicious of AI tools, but to use them with the same professional judgment you would apply to any other input, whether that is a junior analyzt's spreadsheet or a consultant's recommendation.

The EU AI Act and High-Risk Financial Applications

The EU AI Act, which began phasing into enforcement in 2024, classifies AI systems used in credit scoring, insurance pricing, and investment decisions as 'high-risk.' High-risk systems require human oversight, documentation of training data, regular accuracy audits, and explainability, meaning the AI must be able to justify its outputs in terms a human can understand. This applies to tools you buy, not just tools you build.

The Explainability Problem, and Why It Matters for Your Monday Morning

Goldman Sachs faced a pointed public moment in 2019 when the Apple Card, issued through Goldman, was accused of offering significantly lower credit limits to women than to men, including in cases where spouses shared finances. Goldman's response was that the algorithm made the decisions based on creditworthiness factors, not gender. The problem was that nobody outside the firm could verify that claim. The model was a black box. Regulators and customers could see the outputs but not the reasoning. The New York Department of Financial Services opened a formal investigation.

This is the explainability problem. A model that cannot show its work is a liability in regulated industries, not because the model is necessarily wrong, but because you cannot defend what you cannot explain. When you use AI tools like ChatGPT or Claude to draft compliance summaries, flag risks in contracts, or analyze portfolio exposure, you face a smaller version of this same challenge. If a client or regulator asks why you flagged a particular risk, 'the AI said so' is not an answer. You need to be able to articulate the reasoning yourself.

The practical solution is to treat AI output as a first draft of your thinking, not a final answer. When Claude summarizes a regulatory document and highlights three compliance gaps, your job is to read those gaps, verify them against the source, and be able to explain them in your own words. This takes fifteen minutes instead of three hours. That is the genuine productivity gain. But skipping the verification step, treating the AI summary as the document itself, is where professionals create real professional and legal exposure.

Compliance Officer. Explaining an AI-Flagged Risk to a Client

Prompt

I used an AI tool to review this investment advisory agreement and it flagged a potential conflict of interest in Section 4.2 around fee disclosure. Help me write a plain-English explanation of why this clause could be problematic under SEC Rule 206(4)-7, suitable for sharing with a non-legal client.

AI Response

Here is a plain-English explanation you can share with your client: **What the clause says:** Section 4.2 allows the adviser to receive compensation from third-party fund managers whose products are recommended to clients. The clause discloses this arrangement, but only in general terms, it does not specify how much compensation the adviser may receive or how that amount could influence which products get recommended. **Why this matters under SEC rules:** SEC Rule 206(4)-7 (the Compliance Rule) requires registered investment advisers to maintain written policies that address conflicts of interest, including financial incentives that could affect the objectivity of their advice. A vague disclosure like this one does not meet the standard of 'full and fair disclosure' that the SEC expects. It tells clients that a conflict exists, but not enough for them to evaluate how significant it is. **The practical risk:** If the adviser recommends a fund partly because it pays them a referral fee, and the client later suffers losses, this clause would likely not protect the adviser from a regulatory complaint or civil claim. The client could reasonably argue they were not given enough information to make an informed decision. **What we recommend:** Request a revised clause that specifies the types of third-party compensation, the approximate range or calculation method, and an explicit statement of how the firm manages this conflict in its recommendation process. This is standard practice for compliant advisory agreements.

A Healthcare Parallel: What Finance Can Learn from Medicine's AI Mistakes

In 2019, a widely-used hospital algorithm in the United States was found to systematically underestimate the health needs of Black patients. The algorithm used healthcare spending as a proxy for health complexity, a reasonable-sounding shortcut that failed because, historically, less money had been spent on Black patients, not because they were healthier. The researchers who uncovered this estimated the bias affected millions of patients annually. The healthcare sector's response, mandatory bias audits, diverse training data requirements, explainability standards, mirrors exactly what financial regulators are now requiring for AI in credit and investment.

The parallel is direct and instructive for finance professionals. Any AI model trained on historical financial data inherits the biases embedded in that history. If your firm's past lending decisions, investment recommendations, or risk assessments reflected conscious or unconscious bias, an AI trained on that data will reproduce those patterns, efficiently and at scale. You do not need to be a data scientist to ask the right questions: Who was this model trained on? Has it been tested for demographic fairness? Can the vendor show you an independent audit?

AI Use Case in FinanceKey Regulatory ConcernRelevant FrameworkProfessional Action Required
Credit scoring and loan approvalDemographic bias in outcomesEU AI Act, Equal Credit Opportunity Act (US)Request bias audit from vendor; document human review
Automated investment advice (robo-advisors)Suitability and conflict of interestSEC Regulation Best Interest, MiFID IIVerify AI recommendations against client risk profile
AML and fraud detection flaggingFalse positives affecting customers unfairlyFATF guidelines, FinCEN requirementsEnsure human review before account action
AI-generated compliance reportsAccuracy and hallucination riskSOX, GDPR, local audit standardsVerify all figures against source documents
Earnings forecasts and market analyzisMarket manipulation, material non-public infoSEC Rule 10b-5, MAR (EU)Do not act on AI output derived from non-public data
Common AI applications in finance mapped to their primary regulatory risks and the professional actions required to manage them responsibly.

The Fund Manager Who Built Trust by Showing the Work

A boutique asset management firm in Singapore began using AI tools in 2022 to generate preliminary ESG risk summaries for prospective portfolio companies. Rather than presenting these summaries to clients as finished analyzis, the lead portfolio manager developed a practice of sharing both the AI-generated draft and her own annotated version, showing where she agreed, where she corrected the AI, and where the AI had flagged something she would have missed. Clients reported higher confidence in the firm's process, not lower. The visible human judgment made the AI output more credible, not less.

This is the accountability model that regulators and ethicists are pointing toward: AI as a transparent input into a human professional's reasoning, not a replacement for it. The portfolio manager's approach also created a practical audit trail, if a client or regulator ever questioned a recommendation, the documentation showed exactly how the AI output had been evaluated and what human judgment had been applied. That documentation is increasingly not optional. Under frameworks like the EU AI Act and the SEC's 2023 guidance on AI in investment advice, firms are expected to maintain records of how AI tools influenced consequential decisions.

Build Your Own Audit Trail. Starting Today

Any time you use AI to support a financial decision or client-facing output, save two things: the prompt you used and the AI's raw response. Add a brief note of what you verified, changed, or rejected. This takes two minutes and creates documentation that protects you professionally. Store it in the same place as your other work records, a shared drive, a client folder, or your firm's compliance system.

Putting It Into Practice: Your Ethical AI Checklist

The professionals who use AI most effectively in finance are not the ones who trust it most blindly, they are the ones who have developed a consistent, fast verification habit. Before any AI-assisted output leaves your desk, three questions should be automatic: Did I check the AI's claims against the source? Could I explain this reasoning to a regulator or client without referencing the AI? Does this output affect anyone's access to financial products or services? If the answer to any of these requires more work, do that work. The AI has already saved you time, use some of it on verification.

Data privacy is the second practical pillar. Financial data is among the most sensitive personal data that exists. When you paste client account details, loan applications, or investment portfolios into a public AI tool like the free version of ChatGPT, that data may be used to train future models, depending on the platform's current privacy settings. ChatGPT Plus and Claude Pro both offer options to turn off training on your inputs. Microsoft Copilot for Microsoft 365, deployed through an enterprise license, keeps your data within your organization's environment by default. Know which tool you are using and what its data handling terms actually say.

Finally, treat AI regulation as a living document, not a one-time briefing. The EU AI Act, SEC guidance, and CFPB positions on algorithmic decision-making are all evolving in 2024 and 2025. The professionals who stay ahead of this are reading the primary sources, not waiting for their compliance department to issue a memo eighteen months later. Set a quarterly reminder to check for updates from your relevant regulator's website. Thirty minutes a quarter keeps you current. That is a reasonable investment for tools that are now touching your most consequential professional outputs.

Build a Personal AI Ethics Checklist for Financial Work

Goal: Create a practical, one-page reference document that you can use every time AI tools contribute to a financial output, protecting you professionally and ensuring your work meets emerging regulatory standards.

1. Open a free AI tool. Claude (claude.ai) or ChatGPT (chat.openai.com), and a blank document in Word, Google Docs, or Notion. 2. In the AI tool, type: 'I work in [your role] in financial services. List 8 specific questions I should ask myself before using AI-generated content in a client report, compliance document, or investment recommendation. Make them practical and specific to regulated finance.' 3. Review the AI's list. Cross out any that don't apply to your role. Add any that are missing based on your own experience. 4. In your blank document, create a header: 'My AI Output Checklist, [Your Role]' with today's date. 5. Write your final checklist as a numbered list of 6-8 questions. Each question should be answerable with a yes/no and take under two minutes to check. 6. Add a second section titled 'Data Privacy Rules I Follow', list the specific AI tools you use and one sentence about each tool's data handling policy (check the tool's privacy settings page for this). 7. Add a third section titled 'My Verification Habit', write two sentences describing exactly how and where you will save your AI prompts and outputs for documentation purposes. 8. Share the document with one colleague or your manager and ask if they would add anything from a compliance perspective. 9. Save it somewhere you will actually find it, your desktop, a pinned note, or the top of your work drive folder.

  1. Accountability does not transfer to algorithms. When AI influences a financial decision, the human professional and their firm remain legally and ethically responsible for the outcome.
  2. Explainability is a professional requirement, not a technical nicety. If you cannot explain the reasoning behind an AI-assisted output in your own words, you are not ready to act on it.
  3. Historical data carries historical bias. Any AI model trained on past financial decisions may reproduce the inequities embedded in those decisions, at greater scale and speed.
  4. Transparency builds trust. Showing clients and colleagues how AI was used, and where human judgment was applied, increases confidence in your work rather than undermining it.
  5. Data privacy is your responsibility, not the tool's. Know which AI platforms you are using, read their data handling terms, and never paste sensitive client data into tools without enterprise-level privacy protections.
  6. Regulation is accelerating. The EU AI Act, SEC guidance, and CFPB algorithmic fairness standards are all active and evolving. Staying current is a professional obligation, not optional continuing education.

This lesson requires Pro+

Upgrade your plan to unlock this lesson and all other Pro+ content on the platform.

Upgrade to Pro+

You're currently on the Free plan.