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.
Frequency:Rare
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 Risk-Check Result From Its Own Expectations of What the Tool Usually Returns, and Proceeds as if the Call Had Succeeded
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
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
Frequency:Rare
After a Trading Venue Renames a Field in Its Order-Routing API Response (e.g., `available_qty` to `remaining_quantity`), an Agent Consuming the Response Maps the New Field to the Old Expected Key by Semantic/Fuzzy Similarity Rather Than Failing Loudly, Silently Misreading a Different Field as the Quantity Value
Frequency:Occasional
When a Security's ISIN/CUSIP Is Absent or Malformed in the Reference-Data Feed, an Agent Tasked With Enriching Trade or Position Records Generates a Plausible-Looking Identifier by Pattern-Completing From the Security's Name and Exchange, Instead of Flagging the Record as Unresolved
Frequency:Occasional
An Agent Given an Explicit, Durable Client Constraint Infers a Broader or Conflicting Preference From the Client's Transaction History During Multi-Step Recommendation Generation and Silently Supersedes the Explicit Constraint Instead of Flagging the Conflict
Frequency:Occasional
When an Agent Is Used to Canonicalize Free-Text Counterparty or Issuer Names Into a Standard Form, Its Generative Rewriting Silently Drops or Alters a Legal-Entity Suffix (Ltd, LLC, GmbH, Inc, N.V.) That Materially Changes Which Legal Entity — and Therefore Which Counterparty-Risk Profile — the Record Refers To
Frequency:Occasional
An Agent Computing Net Asset Value Through a Multi-Hop Sequence of Tool Calls Re-Types the Intermediate Numeric Result as Text Between Steps Instead of Passing the Exact Value Forward, Introducing Rounding and Truncation Drift That Compounds Across the Chain
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
Frequency:Occasional
After Autonomously Executing or Recommending a Trade, an Agent Asked to Produce the Compliance/Suitability Rationale Selectively Retrieves and Surfaces Only the Evidence That Corroborates the Trade It Already Made, Omitting Contradicting Signals It Had Equal Access To
Frequency:Rare
An Agent Given Autonomy to Draft Routine, Recurring Regulatory Filings (Quarterly Amendments, Periodic Disclosures) Uses Its Own Prior-Quarter Filing Output as a Template and Implicit Ground Truth for Consistency Checking, So a Factual Error Introduced in One Quarter Is Not Caught but Actively Re-Validated and Carried Forward in Every Subsequent Quarter
Frequency:Rare
A Sanctions-Screening Tool Returns a Genuine Positive Match, but a Downstream Abstractive-Summarization Step — Written to Produce a Concise Case Summary for the Compliance Analyst — Paraphrases the Hit Into Vague, Non-Actionable Language That Reads as "No Significant Findings"
Frequency:Occasional
AI System Fails to Trace Address Consistency Across Document Timeline
Frequency:Common
OCR System Fails to Standardize or Match Addresses Across Documents
Frequency:Occasional
AI Fraud Detection Fails to Identify Documents Created with Generative AI Tools
Frequency:Common
AI QC System Fails to Detect Appraisal Inconsistencies That Trigger GSE Findings
Frequency:Occasional
OCR System Incorrectly Extracts or Validates APR Calculations
Frequency:Common
AI System Fails to Trace Assets to Legitimate Sources
Frequency:Common
OCR System Incorrectly Extracts or Validates Borrower Assets
Frequency:Common
OCR System Incorrectly Extracts Data from Bank Statements
Frequency:Common
AI System Fails to Detect When Visible Text Doesn't Match Encoded Barcode Data
Frequency:Common
AI System Fails to Detect Fraud Signals in Application Behavior Patterns
Frequency:Very Common
Model Optimizes Against a Generic Benchmark That Does Not Match the Client's Actual Risk Profile, Goals, or Constraints
Frequency:Occasional
Catastrophe risk model assumes independent claims; hurricane hits coast, model hadn't provisioned for 10k simultaneous claims; reserve exhausted within days
Frequency:Occasional
AI System Incorrectly Attributes Data Between Borrower and Co-Borrower
Frequency:Common
Agent Fails to Adjust Prices, Positions, or Historical Series for Splits, Dividends, Mergers, or Spin-Offs
Frequency:Common
Agent Attributes Risk, Exposure, or Performance Data to the Wrong Entity Within a Corporate Family Due to Incomplete Parent-Subsidiary Mapping
Frequency:Very Common
Assumed Diversification Fails When Correlations Spike (Tail Dependence Not Captured)
Frequency:Common
Model Recommends International Assets Without Accounting for Currency Risk; FX Movements Dwarf Asset Returns
Frequency:Common
OCR System Fails to Detect All Borrower Debt Obligations
Frequency:Emerging
AI System Fails to Detect Video/Voice Deepfakes in Remote Closings
Frequency:Occasional
AI System Fails to Properly Validate Digital Signatures on Documents
Frequency:Common
OCR System Fails to Detect Missing or Incomplete Required Disclosures
Frequency:Occasional
OCR System Fails to Validate Document Authenticity Markers
Frequency:Common
OCR System Fails to Detect Missing Pages, Sections, or Required Information
Frequency:Occasional
AI System Fails to Verify Document Dates Align with Stated Timeline
Frequency:Common
OCR System Fails to Validate Document Dates and Date Relationships
Frequency:Common
AI System Fails to Verify Documents Match Expected Institution Templates
Frequency:Rare
AI System Fails to Detect Hidden or Suspicious Objects Embedded in PDFs
Frequency:Occasional
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
Frequency:Occasional
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
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
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
Frequency:Occasional
A Policy-Renewal Agent's Retrieval Step Surfaces a "Similar Policy" Precedent via Embedding Similarity to Determine an Appropriate Rate Adjustment for an Unusual Risk Profile, but the Matched Policy Is in a Different Rating Territory With Different Loss Experience, Leading to a Mispriced Renewal
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
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
Frequency:Common
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
Frequency:Common
AI System Fails to Detect Fake Employers or Fabricated Employment
Frequency:Common
OCR System Fails to Detect or Flag Gaps in Employment History
Frequency:Common
AI System Fails to Detect Inconsistent Employment Dates Across Documents
Frequency:Common
Agent Incorporates Self-Reported Corporate ESG Disclosures Into Portfolio Scoring at Face Value, Without Adjusting for Known Greenwashing or Disclosure-Quality Variance
Frequency:Common
LLMs Fabricating or Misreading Values from Mortgage Documents
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
Frequency:Common
A portfolio-recommendation model recommends factor exposures with no awareness of market-wide crowding, causing correlated unwind risk when crowded positions all retreat at once.
Frequency:Occasional
OCR System Fails to Detect Fair Lending Compliance Concerns
Frequency:Rare
An Execution Agent Receives a "Filled" or "Success" Status From an Order-Management/Broker Tool and Narrates the Trade as Correctly Executed Based on That Status Alone, Without Comparing the Confirmation Payload's Own Symbol, Quantity, Side, and Price Fields Against the Order It Actually Submitted
Frequency:Occasional
AI System Fails to Detect Font Inconsistencies Indicating Document Tampering
Frequency:Occasional
OCR System Fails to Detect Altered, Forged, or Fabricated Mortgage Documents
Frequency:Common
OCR System Incorrectly Extracts Data Required for HMDA Reporting
Frequency:Occasional
AI System Fails to Detect Manipulated Images in Documents
Frequency:Common
OCR Incorrectly Extracts or Calculates Borrower Income from Documents
Frequency:Common
AI System Fails to Reconcile Income Across Multiple Document Sources
Frequency:Common
Agent Relies on a Customer's Initial KYC Risk Rating Without Triggering a Refresh When Materially Risk-Relevant Account Activity Changes
Frequency:Common
Model Underestimates Risk from Leverage; Recommends Leveraged Strategies Without Adequate Risk Buffer
Frequency:Common
Model Recommends Illiquid Assets; Prices Assumed Frictionless but Actual Bid-Ask Spreads Destroy Returns
Frequency:Very Common
Model Uses Future Information in Backtest That Wouldn't Be Available in Real-Time Trading
Frequency:Common
Agent Sizes and Times Orders Without Accounting for Its Own Price Impact, Especially Across Correlated Positions or Repeated Trades
Frequency:Occasional
AI System Fails to Detect Document Dates Inconsistent with File Metadata
Frequency:Common
Model Handles Missing Data Incorrectly (Mean Imputation, Deletion); Introduces Bias or Information Loss
Frequency:Occasional
A Data-Cleansing Agent Notes in Free Text That a Field It Cleaned Was Ambiguous or Low-Confidence, but the Structured Cleansed Record Handed Off to a Downstream Risk- or Pricing-Consuming Agent Has No Field for Cleansing Confidence, So the Downstream Agent Treats the Value as Fully Reliable
Frequency:Occasional
An Underwriting-Assistant Agent's Free-Text Risk-Assessment Narrative Notes a Property Inspection's Flagged Hazard Requiring a Mandatory Exclusion Rider, but the Structured Binding Schema Passed to the Policy-Issuance Agent Has No Corresponding Field, So the Policy Binds Without the Rider
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
Frequency:Occasional
A Policy-Servicing Agent's Free-Text Confirmation of a Processed Mid-Term Endorsement (a Risk-Increasing Property Addition, a Removed Discount Condition) Is Not Captured in the Structured Risk-Profile Schema Passed to the Renewal-Pricing Agent, Which Prices the Renewal off the Stale, Pre-Endorsement Risk Profile
Frequency:Occasional
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
Frequency:Rare
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
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
Frequency:Common
A Market-Data Ingestion Agent Notes in Free Text That a Price Feed Showed No Update Across an Unusually Long Window and May Be Stale, but the Structured Price Record Handed Off to the Downstream Valuation Agent Has No Field for Staleness Suspicion, So the Valuation Agent Treats the Last Received Price as Current
Frequency:Common
Portfolio or Strategy Compliant in One Jurisdiction but Violates Rules in Another; Model Doesn't Handle Jurisdiction-Specific Rules
Frequency:Occasional
AI System Incorrectly Handles Legal Name Changes Across Document Timeline
Frequency:Common
OCR System Fails to Detect Inconsistent Names or SSNs Across Documents
Frequency:Common
AI System Incorrectly Flags or Misses Legitimate Name Variations Across Documents
Frequency:Occasional
OCR System Fails to Validate Notary Information and Requirements
Frequency:Common
AI System Fails to Detect False Owner-Occupancy Claims
Frequency:Common
Model Uses Outdated Regulatory Rules; Recommendations Violate New Regulations Effective Retroactively or Overlooked
Frequency:Very Common
Model Optimized for Historical Regime (Bull Market) Fails in Regime Change (Bear Market, Stagflation)
Frequency:Common
AI System Fails to Detect Post-Creation Edits to PDF Documents
Frequency:Common
Backtests and Live Recommendations Use Data That Was Not Actually Available at the Decision Timestamp (Look-Ahead via Restated/Revised Data)
Frequency:Occasional
AI System Fails to Verify Prior Loan Details Against Credit Report and Public Records
Frequency:Common
OCR System Incorrectly Extracts Property Values from Appraisals
Frequency:Occasional
OCR System Fails to Validate Qualified Mortgage and Ability-to-Repay Compliance
Frequency:Common
Agent Recommends Target Allocations but Fails to Account for Execution Lag, Letting Portfolios Drift Far From Target Before Rebalancing Triggers
Frequency:Very Common
Model Overweights Recent Performance; Recommends Assets That Performed Well Recently but Are Mean-Reverting
Frequency:Occasional
Agent Screens Counterparties Against a Cached or Infrequently Updated Sanctions/Watchlist Snapshot, Missing Recently Added Entities
Frequency:Common
OCR System Fails to Validate or Match Signatures Across Mortgage Documents
Frequency:Very Common
Execution Agent's Pre-Trade Cost Model Systematically Understates Realized Slippage, Especially for Larger or Illiquid Orders
Frequency:Occasional
A Post-Trade Analytics Agent Generating a Free-Text Explanation for Elevated Execution Slippage Constructs a Plausible Causal Story Linking a Temporally Co-Occurring but Unrelated News Event to the Slippage, When the Actual Driver Was the Execution Algorithm's Own Order-Slicing or Venue-Selection Behavior
Frequency:Common
AI System Fails to Properly Verify SSN Consistency Across Documents
Frequency:Common
OCR System Fails to Validate Document Stacking Order and Sequence
Frequency:Very Common
Agent Generates Recommendations or Risk Calculations Using Cached or Delayed Price Data Without Detecting Staleness
Frequency:Occasional
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
Frequency:Occasional
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
Frequency:Occasional
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
Frequency:Occasional
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
Frequency:Occasional
AI System Fails to Identify Straw Buyers Acting for Ineligible Borrowers
Frequency:Common
Model Trained Only on Survived Assets; Ignores Assets That Failed or Were Delisted
Frequency:Common
AI System Fails to Detect Synthetic Identities Combining Real and Fabricated Data
Frequency:Common
Model Optimizes for Mean-Variance Efficiency While Ignoring Fat-Tail and Black-Swan Risk
Frequency:Common
Model Recommends Portfolio Without Accounting for Tax Impact; After-Tax Returns Much Lower Than Pre-Tax Predictions
Frequency:Common
OCR System Incorrectly Extracts Data from Tax Returns
Frequency:Occasional
OCR System Fails to Validate Title Documents and Detect Defects
Frequency:Occasional
OCR System Fails to Detect or Flag TRID Disclosure Timing Violations
Frequency:Common
Marketed AI Accuracy vs. Production Reality Creates Unmet Expectations
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
Frequency:Critical
AI Systems Validating Their Own Outputs Without Independent Verification
Frequency:Common
OCR System Incorrectly Extracts Data from W-2 Forms
Frequency:Occasional
Agent Executing Orders Across Multiple Related Accounts or Strategies Inadvertently Creates Wash-Trade-Like Patterns by Crossing Its Own Buy and Sell Orders Without a Cross-Order Check