AI in Finance and FP&A: What Actually Works (And What's Hype)

"You're going to find that it hallucinates stuff. Figuring financial data is not a good use for ai yet. I had the opposite experience, where I developed an AI solution but because of the "black box" and the amount of verification required, it was easier to code our system to do it."

— Source: r/Accounting (327 upvotes)

AI is everywhere in tech right now. Your CEO has probably asked: "Can we use AI to automate our month-end close?" Your CFO has heard: "AI can forecast cash flow with 95% accuracy." Your finance team has seen demos where AI generates board packs in seconds.

Most of it is hype. Or worse: it works on clean demo data but fails on your messy reality.

This guide cuts through the noise: (1) what AI actually works for in FP&A, (2) what it fails at spectacularly, (3) why, and (4) how to deploy it responsibly without losing audit trails or accuracy.

Every AI finance vendor claims one of these:

• "AI-powered finance function that automates analyst work"
• "Autonomous close in 24 hours"
• "Machine learning that predicts revenue"
• "Self-healing GL that catches all errors"
• "AI that reads contracts and auto-codes journal entries"

Rarely true. What they actually deliver: a tool that requires heavy validation, weeks of tuning, and usually ends up complementing (not replacing) existing processes.

Why the gap between demo and reality?

• Demos use clean data. Vendor shows a perfect CSV with 12 months of actuals, 5 products, and $0 errors. Your data has encoding issues, missing dates, duplicate transactions, and typos.
• AI generalizes; your business is specific. AI trained on generic financial data doesn't understand your intercompany eliminations, your seasonal patterns, or your unique cost structure.
• Hallucination isn't obvious in demos. When AI generates a forecast of $5M, the demo doesn't ask "where did you get that number?" Real deployments need answers.
• Vendors bury the validation requirements in fine print. Every AI output in finance requires human review. That human work eats the time savings.

The honest take: AI is useful in finance, but not as a replacement. It's a tool that amplifies your processes.

Use Case 1: Variance Narrative Drafting

The problem: Month-end, you have a $500K variance in gross margin. Someone has to explain it: "Q2 freight rates spiked due to fuel surcharge. Offsetting: higher ASP on new SKU launch. Net impact: $280K unfavorable."

What AI does well: Given the underlying data (freight costs up 15%, ASP up 8%, volume up 3%), AI can draft a narrative that ties movements together. Not perfect, but a great starting point.

Real ROI: Your FP&A analyst goes from 2 hours of narrative writing to 20 minutes of review/edit. Over a year, that's 80+ hours saved per analyst.

The caveat: Every number in the narrative must be traceable to source GL rows. If AI says "freight up 15%", that 15% must match your GL data, not be invented.

"It's just another tool honestly. The biggest impact has been using it to help write SQL and now I can have reports without waiting on IT. What would take weeks, hours now."

— Source: r/FPandA (36 upvotes)

Use Case 2: Source Mapping and Reconciliation

The problem: Bank reconciliation takes 2+ hours per account because you have to match 200+ transactions, find duplicates, and flag exceptions.

What AI does well: AI can build matching rules ("if transaction amount, date, and counterparty name are within X%, it's likely the same transaction"). It catches duplicates and flags exceptions that don't auto-match.

Real ROI: One accountant reported reducing bank reconciliation from 1.5 days to 1 hour by automating the matching logic. The AI doesn't eliminate manual work, but it concentrates it on the 2-3% of transactions that actually need human judgment.

Key: You still need the human review. But instead of reviewing 200 transactions, you review 5 exceptions. The leverage is massive.

Use Case 3: SQL and Report Code Generation

The problem: Your IT team is backlogged. A simple "run a report of Q3 gross margin by channel" takes 2 weeks because IT has to write SQL.

What AI does well: Give AI a data schema and ask it to write SQL. It generates correct (or near-correct) queries 70% of the time. For the other 30%, it gets 90% of the way there, and a data analyst can fix it in minutes.

Real ROI: Finance teams that use AI for SQL code generation report weeks of turnaround time → hours. One CFO said: "I used to wait on IT for ad hoc reports. Now I can ask AI, validate the output, and have it in 2 hours."

Caveat: Validate the SQL logic. AI can generate syntactically correct code that answers the wrong question.

Use Case 4: Anomaly Detection (But Not Root Cause)

The problem: Buried in 10K GL transactions is an expense charged to the wrong cost center. Takes hours to find.

What AI does well: Scan transactions for statistical outliers ("this transaction is 3 standard deviations above the average for this account") or policy violations ("expense charged to wrong cost center based on vendor name").

Real ROI: Instead of reviewing 10K transactions, you review 20 flagged anomalies. The savings come from reducing the scope of human review.

Caveat: AI flags anomalies but doesn't explain them. You still need a human to understand root cause. ("Why is this transaction flagged?" "Because it's 3x the normal amount." "But I approved it because the vendor had a bulk discount." "OK, override the flag.")

Fail Case 1: Forecasting Without Historical Patterns

The ask: "AI, forecast our revenue for next year. We're launching a new product line."

What AI does: Extrapolates historical trends. If historical growth was 15%, it forecasts 15% growth forever. It doesn't know about the new product.

Why it fails: AI learns from data. If you have zero historical data on the new product, AI can't forecast it. It will hallucinate a number.

Real example: A CFO asked an AI to forecast cash flow for a 2-year horizon. The AI generated beautiful-looking output. Months later, actual cash came in 30% lower because the AI didn't account for a market shift the CFO forgot to mention.

The fix: Use AI to build time-series models from clean historical data (24+ months). For new initiatives, provide AI with external data (market research, pilot results, customer surveys). Don't ask AI to forecast from zero.

Fail Case 2: Expense Categorization (OCR + Coding)

The ask: "Read this PDF receipt and code it to the GL."

What AI does: OCR (reads text from receipt), then tries to categorize it. Looks at vendor name and amount.

Why it fails: Ambiguous receipts break it. A $500 Staples charge might be office supplies (5000) or shipping/packaging materials (5200). Only context (the project, the location, the requestor) tells you which. AI guesses.

Real example: A team automated receipt coding with AI. After 6 months, they realized 15% of small-dollar expenses were miscoded. The manual effort to audit/correct exceeded the time saved by automation.

The fix: Use AI for high-confidence items only (vendor name exactly matches GL category, amount is in typical range). Flag ambiguous items for human review. Don't batch-code without spot-checking.

Fail Case 3: "Autonomous Close" (Sounds Good, Isn't Real)

The pitch: "AI automates your entire month-end close. Press a button, get financial statements."

The reality: You still need to: (1) reconcile bank feeds, (2) match intercompany transactions, (3) review accruals, (4) validate FX calculations, (5) spot-check the GL, (6) review variance explanations. That's 90% of the work.

Why it fails: Close isn't mechanical. It's judgment-heavy. Your controller looks at a journal entry and says, "That looks wrong. Let me investigate." AI can't do that.

Real talk: A CFO at a mid-market manufacturing company spent $200K implementing an "AI close" solution. After 6 months, the finance team still spent the same number of hours because they had to validate every AI step. They downgraded to a manual close with better processes, saved more money.

Hallucination: when AI generates plausible-sounding output that is factually wrong.

"Give values of 3.87%, 5% and 6.1%. Report comes out 3.4%, 5% and 6.1%. (The 3.87% became 3.4% because the AI changed it.)"

— Source: r/CFO (79 upvotes)

In finance, this is catastrophic. Your board gets a P&L with invented numbers. Your auditor asks, "Where did the $100K accrual come from?" You can't trace it.

Why hallucination happens

• AI generates the most likely next token, not the correct one. When asked for a number, AI doesn't look it up; it predicts what a number would fit. Sometimes it's right. Sometimes it makes one up.
• AI doesn't understand "I don't know." If asked a question it can't answer from training data, it invents an answer instead of saying "I don't have that data."
• Finance requires precision; AI provides plausibility. 3.4% looks right. It could be. But it's wrong. And nobody caught it until audit.

Real consequences

A former r/FPandA poster noted: "A coworker used AI to summarize financial data. It invented a whole business line focused on forex. The business is legally not allowed to operate outside the state, so no one knows where that came from."

Translation: finance + hallucination = audit failure, embarrassment, or worse.

How to mitigate hallucination

• Never use AI to generate numbers without a source. Every number in finance must trace to a GL row, a transaction, or an external data point.
• Use AI for text (narratives, explanations), not numbers. AI is good at reasoning about relationships ("Why did gross margin decline?"). It's bad at generating numbers ("What is gross margin?").
• Build verification into every AI output. Use skill files or templates that AI must follow (e.g., "Generate a variance narrative using ONLY these GL line items"). This reduces hallucination.
• Treat AI as a draft, not a final answer. Every AI output should go to a human for validation before it leaves the finance team.

Case 1: Mid-Market Company with Multi-Entity Close

Setup: A $50M apparel brand with 3 entities (US parent + UK + Mexico). Month-end consolidation took 3 days because of manual GL review and elimination entries.

AI deployed: Used AI to read each entity's trial balance, flag anomalies (unusual journal entries, accounts out of balance), and generate a draft consolidation template.

Result: Close time: 3 days → 1.5 days. The AI caught 5 unusual journal entries that the controller would have found manually. The real win: the controller spent less time on mechanical review and more on actual analysis.

ROI: 8 hours/month × 12 = 96 analyst hours saved. At $80K salary, that's roughly $37K/year value. Tool cost: $1.5K/month ($18K/year). Net savings: ~$19K/year, plus better accuracy.

Case 2: Cash Flow Visibility Across Channels

Setup: A $15M DTC brand with Shopify, Amazon, and wholesale. Cash comes from 5 different payment processors (Stripe, Square, Amazon Seller Central, wire transfers). Reconciliation took 4-6 hours weekly.

AI deployed: Built daily reconciliation automation that pulls from all 5 sources, matches amounts/dates using fuzzy logic (AI rules), and flags exceptions. Exceptions are manually reviewed.

Result: Weekly reconciliation: 4-6 hours → 30 minutes. The AI handles 95% of matching; the human reviews 5% exceptions.

ROI: 3-4 hours/week × 50 weeks = 150-200 hours/year saved. At $60K analyst salary, that's $5K-7K value. Tool cost: ~$500/month ($6K/year). Marginal ROI: small, but accurate visibility and reduced errors paid additional value.

Case 3: What Not to Do

Setup: A CFO wanted an "AI financial analyst" to generate a monthly board pack automatically.

Deployed: Fancy AI tool that took GL data and generated charts, narratives, and KPI insights.

Result (after 3 months): The CFO realized: (1) Every chart needed review; formatting drifted; (2) Narratives were sometimes plausible but incorrect; (3) KPI calculations were sometimes off by rounding errors; (4) The time spent validating the AI exceeded the time saved by using it.

Lesson: Don't try to automate judgment. Automate mechanics (SQL, report generation, reconciliation matching). Judgment stays human.

Principle 1: Every Number Must Trace to Source

If AI generates a forecast, a narrative, or an accrual, you must be able to point to the GL row or transaction that supports it. No exceptions.

Principle 2: Use AI for Mechanics, Not Judgment

Use AI for: SQL writing, reconciliation matching, anomaly detection, narrative drafting.

Don't use AI for: revenue recognition decisions, expense categorization (without rules), forecasting new business, goodwill impairment assessments.

Principle 3: Build Verification Into the Process

• Use skill files or templates that constrain AI output (e.g., variance narrative template that references only specific GL accounts).
• Require sign-off on AI output by a human. AI draft → Human review → Use.
• Track error rates. Monthly, spot-check 5-10% of AI outputs. If error rate > 2%, pull the feature and redesign.

Principle 4: Start Small

Don't deploy AI to replace your month-end close. Start with a low-stakes use case: bank reconciliation, SQL generation, or narrative drafting. Prove value in 3 months. Then expand.

Principle 5: Keep Humans in the Loop

Responsible AI in FP&A: AI is supporting, not central. It flags anomalies, drafts variance narratives, and suggests consolidation entries. But a human FP&A analyst reviews everything before it's finalized. The human is the decision-maker; AI is the assistant.

AI is useful in FP&A. But not how vendors pitch it. Not as a replacement. Not as a black box that you feed data and get magical insights.

AI works when deployed narrowly: reconciliation matching, SQL writing, narrative drafting, anomaly flagging. And always with human validation.

What AI doesn't do: replace judgment, forecast the future without historical data, or generate accurate numbers. When vendors pitch those, they're selling hype.

The finance teams seeing real ROI from AI are the ones using it to amplify their processes: not replace them. An analyst spends 30% less time on mechanics (reconciliation, reporting, drafting) and 30% more time on judgment (variance drivers, scenarios, business partnering).