Financial AI

Financial AI failures — trading, underwriting, and compliance mistakes in finance agents

116 patterns

Financial AI failures — trading, underwriting, and compliance mistakes in finance agents. We've tracked 116 distinct Financial AI patterns across production AI agent deployments — most commonly in Mortgage Documents, Financial Services, Insurance systems. One recurring example: Agent Fabricates Plausible Tool Output When Risk-Engine Tool Call Times Out — When a Pre-Trade Risk-Check Tool Call Times Out or Returns a Transport-Level Error Instead of a Structured Response, the Agent's Next Reasoning Step Generates a Schema-Conforming R…

Each pattern below documents the specific failure mode, why it happens, and how teams have mitigated it in practice — use this page as a reference when building guardrails, writing evals, or debugging an agent that's already misbehaving in this way.

Context-Window Truncation Drops Early-Session Client Constraint

Frequency:Occasional

A Hard Constraint the Client States Early in a Long, Multi-Turn Advisory Session (e.g., "No Fossil-Fuel Holdings," "No Leveraged Products") Falls Outside the Model's Effective Context Window by the Time a Later-Turn Recommendation Is Generated, and the Agent Recommends a Security That Violates It Without Re-Checking Against the Original Constraint List

Cross-Client Parameter Bleed in Sequential Advisory Sessions

Frequency:Occasional

An Advisor-Facing Agent That Processes Multiple Clients Within a Single Continuous Session Carries a Computed Suitability Parameter (Risk Tolerance, Tax Bracket, Liquidity Need) From One Client Forward Into Its Reasoning for the Next Client, Without Any Literal Data From the First Client Appearing in the Second Client's Output

Post-Liquidation State Blindness in Margin Call Resolution

Frequency:Occasional

An Agent Resolving a Margin Call Through a Multi-Step Tool-Calling Sequence Continues Reasoning About Remaining Liquidation Needs Using the Account Equity and Margin-Usage Figures It Read Before Its Own Preceding Sell Order Executed, Rather Than Re-Fetching Current State After Its Own Action Changed It

Catastrophe Correlation Blindness

Frequency:Occasional
Category:Insurance

Catastrophe risk model assumes independent claims; hurricane hits coast, model hadn't provisioned for 10k simultaneous claims; reserve exhausted within days

Embedding-Retrieval Applies Wrong Occupation-Class Rate Precedent by Lexical Similarity

Frequency:Occasional
Category:Insurance

An Underwriting Agent's Retrieval Step, Used to Find a "Similar Prior Case" Precedent for Classifying an Applicant's Occupation Into the Correct Risk Class for Pricing, Surfaces a Prior Underwriting Case That Is Embedding-Similar by Job-Title Wording but Belongs to a Materially Different Risk Class, Causing the Agent to Apply the Wrong Class's Rate Factor to the Current Applicant

Embedding Retrieval Flags Unrelated Claimant as Fraud-Ring Match

Frequency:Occasional
Category:Insurance

A Fraud-Detection Agent's Link-Analysis Retrieval Step, Which Searches for Claimants Embedding-Similar to Known Fraud-Ring Members Based on Free-Text Claim-Narrative and Address Fields, Surfaces a Coincidental Lexical Match (a Common Surname, a High-Density Apartment Complex Address) and Treats It as a Fraud-Ring Association, Escalating a Legitimate Claimant for SIU Investigation Based on a Retrieval False Positive

Embedding Retrieval Maps New Product to Wrong Regulatory Rule by Lexical Similarity

Frequency:Occasional

A Compliance Agent Classifying a Newly Launched Financial Product Against the Applicable Regulatory Rule Set Selects the Rule Whose Description Is Most Lexically or Embedding-Similar to the Product's Marketing Description, Rather Than Matching on the Product's Structured Regulatory Classification Code, Applying the Wrong Rule Set to a Structurally Different Product

Embedding Retrieval Merges Similarly Named Issuer Entities in Data-Cleansing Pipeline

Frequency:Occasional

A Data-Quality Agent Deduplicating Issuer Records Across Multiple Source Feeds Using Embedding Similarity Over Issuer Names, Rather Than Matching on a Unique Identifier Such as LEI or CUSIP Issuer Code, Merges Two Distinct Issuer Entities With Coincidentally Similar Names Into a Single Record, Corrupting Downstream Holdings and Exposure Calculations

Embedding Retrieval Selects Wrong Historical Benchmark Order for TCA Comparison

Frequency:Occasional

A Transaction-Cost-Analysis Agent Benchmarking a Trade's Execution Quality Against Historical Comparable Orders Selects the "Most Similar" Past Order Using Embedding Similarity Over Free-Text Order Notes, Rather Than Matching on Instrument, Order Size, and Time-of-Day Liquidity Regime, Producing a Benchmark That Was Never Executed Under Comparable Conditions

Embedding Retrieval Selects Wrong Reference Instrument for Freshness Benchmark

Frequency:Occasional

A Market-Data Freshness-Monitoring Agent Checking Whether an Illiquid Instrument's Price Is Plausibly Current Selects a "Comparable" Reference Instrument Using Embedding Similarity Over Free-Text Descriptions Rather Than Matching on Sector, Duration, and Credit-Quality Attributes, Producing a Freshness Benchmark That Moves Differently From the Instrument Being Checked

Embedding-Retrieval Wrong Endorsement Version Applied

Frequency:Common
Category:Insurance

A Claims-Adjudication Agent's RAG Retrieval Step Pulls a Lexically Similar but Superseded or Wrong-State Policy Endorsement from the Document Store Instead of the Endorsement Actually Attached to the Policy in Force, Causing the Agent to Apply Incorrect Coverage Terms to the Claim

Fabricated Disclosure Figure Fills a Retrieval Gap in Fund Comparison

Frequency:Occasional

An Agent Generating a Client-Facing Fund Comparison or Recommendation Document Retrieves Most Required Disclosure Fields (Expense Ratio, Standardized Performance, Minimum Investment) From the Firm's Actual Fund Documents, but When Retrieval Misses One Specific Field for One Fund, Fills the Gap With a Plausible-Sounding Fabricated Number Rather Than Marking the Field as Unavailable

Multi-Agent Handoff Drops Jurisdiction Flag Between Account-Opening and Compliance-Screening Agents

Frequency:Occasional

An Account-Opening Agent Notes in Free Text That a New Client's Stated Residency and the Jurisdiction Implied by Their Funding Source Do Not Match, but the Structured Client Profile Handed Off to the Compliance-Screening Agent Has No Field for a Jurisdiction Conflict, So the Client Is Screened Only Under Their Stated Residency's Rules

Multi-Agent Handoff Drops Noted Exclusion Before Payment Step

Frequency:Occasional
Category:Insurance

A Coverage Exclusion Identified by an Earlier Stage of a Multi-Agent Claims Pipeline (Intake → Triage → Adjudication → Payment) Is Surfaced Only in That Stage's Free-Text Reasoning or Chat Transcript and Never Written to a Structured Field the Downstream Payment Agent Reads, So the Exclusion Is Silently Dropped Before Funds Are Disbursed

Multi-Agent Handoff Drops Pre-Inception Loss-Date Conflict Before SIU Triage

Frequency:Rare
Category:Insurance

An Initial-Review Agent's Free-Text Note Flagging That a Claimant's Reported Loss Date Appears to Predate the Policy's Effective Date Is Not Captured in the Structured SIU-Referral Schema, So the SIU-Triage Agent Processes the Referral Under a Generic High-Claim-Amount Category and Never Investigates the Actual Pre-Inception Loss Suspicion

Multi-Agent Handoff Drops Risk-Limit-Breach Flag Between Pre-Trade Risk Agent and Execution Agent

Frequency:Occasional

A Pre-Trade Risk Agent Notes in Free Text That an Order, Combined With Existing Positions, Would Push a Concentration or Leverage Limit Into a Marginal Breach Under a Plausible Adverse Price Move, but the Structured Pre-Trade Check Result Handed Off to the Execution Agent Has Only a Pass/Fail Field on Static Current-State Limits, So the Execution Agent Routes the Order as Clear

Stale Training-Corpus Cancellation-Notice Rule Overrides Live State-Lookup Tool

Frequency:Occasional
Category:Insurance

A Policy-Servicing Agent Determining How Many Days of Advance Written Notice a Carrier Must Give Before Cancelling or Non-Renewing a Policy in a Given State Answers From a General, Memorized Sense of Typical Notice-Period Rules Formed During Pretraining Instead of Calling the Live Regulatory-Requirements Lookup Tool It Has Available, Producing a Cancellation or Non-Renewal Notice That Understates the State's Actual Current Required Notice Period

Stale Training-Corpus Catastrophe-Zone Data Overrides Live Feed

Frequency:Occasional
Category:Insurance

An Underwriting Agent Answers Risk-Zone Questions (Flood Zone, Wildfire Risk Tier, Hurricane Exposure Band) from Facts Memorized During Pretraining Instead of Calling the Live Catastrophe-Model or Mapping Tool It Has Available, Producing Risk Assessments Based on Outdated Zone Designations

Stale Training-Corpus Fraud Typology Overrides Current SIU Red-Flag List

Frequency:Occasional
Category:Insurance

A Fraud-Detection Agent Screening Claims for SIU Referral Applies a Generic Fraud-Typology Pattern Absorbed During Pretraining (e.g., a Widely Discussed Staged-Collision Pattern or a Generic Soft-Tissue-Injury Red-Flag Profile) Instead of Querying the Live, Internally Maintained SIU Red-Flag List That the Carrier Has Available as a Tool, Missing a Recently Added Red Flag Specific to a Current Fraud Ring or Failing to Apply a Recently Retired Flag the Carrier Stopped Using Because It Generated Excessive False Positives

Stale Training-Corpus Prompt-Payment Deadline Overrides Current State Statute

Frequency:Occasional
Category:Insurance

A Claims-Processing Agent Determining the Statutory Deadline by Which a Claim Must Be Acknowledged, Investigated, or Paid Under a Given State's Prompt-Payment Law Answers From a General, Memorized Sense of Typical State Deadlines Formed During Pretraining Instead of Calling the Live Regulatory-Requirements Tool It Has Available, Producing a Processing Timeline Based on an Outdated or Generic Deadline Rather Than the State's Actual Current Statutory Requirement

Venue Selection Blindness

Frequency:Common

Agent Routes Orders to the Venue With the Best Quoted Price Without Accounting for Realistic Fill Probability, Rebate Structure, or Information Leakage Risk at That Venue