AI in Finance & Operations

HPE’s internal “Alfred” platform analyzes finance and operational data for a 40–50 person weekly finance-and-sales review. Agents now perform calculations and surface why performance changed so the meeting can focus on actions.

Regional chat agents run every Monday, query millions of Redshift rows, combine structured finance data with field reports, flag anomalies, and produce leadership-ready talk tracks. A separate agent produces scenario analysis and a five-sheet Excel output for target setting.

The agent assembles account context, predicts likely late payments and disputes, routes incoming email, matches payments to invoices, and drafts replies. Case managers start the day with prioritized, “act-ready” work instead of searching across systems.

IBM used ledger analysis to identify automation opportunities, then combined custom watsonx models, orchestration, RPA, input validation, and anomaly detection. A finance manager approves before the system schedules journal submission to the ledger.

A finance agent compares Salesforce opportunity and revenue data with customer order forms stored as PDFs in Box, then produces Excel reconciliation reports through a chat-style Streamlit interface.

Copilot for Finance connects the finance team’s familiar Excel workflow to Dynamics 365 data, matching transactions and highlighting reconciliation items. The broader environment includes automated invoice flows and Power BI reporting.

FloQast AI Transaction Matching applies rules and thresholds to POS and banking data, leaving the accounting team to investigate outliers. Hourly Workday refreshes move discrepancy review closer to real time.

A two-person finance team queries its planning data in natural language, compares budget to actuals, investigates program performance, and generates ad hoc reporting. Teams integration distributes answers to the CEO and CFO without requiring them to use Vena directly.

Finance uses Copilot to search and summarize hundreds of chats, messages, emails, long tax documents, and foreign-language materials. Analysts also query Excel sheets and generate reports with a few commands.

Finance uses Copilot to generate complex Excel formulas, explore spreadsheet features, make dashboard data more accessible, and move results into presentations or email.

The finance team compiles its weekly bulletin with Copilot and routes potential compliance issues to owners. Budget planning uses historical data and market trends to create forecasts and suggested action plans.

COFO Robin Washington uses AI to analyze prior questions, understand competitive developments, summarize information, and focus earnings messaging. Salesforce has not used AI to generate its public 10-K, preserving a clear boundary around regulated reporting.

PayPal’s finance team uses AI agents to create internal analytical content and summarize strategy into executive-ready first drafts. The team has not extended the practice to public 10-K production.

Alphabet’s CFO described agentic AI operating inside the finance back office to process invoices and automate payment and reconciliation steps, with additional treasury use under way.

A centralized report replaced local SAP-to-Excel downloads and uses AI and natural-language generation to explain common variance patterns, flag anomalies, and drill to line items. Controllers validate and revise commentary; the stated design target was up to 95% auto-generated content.

A managed “AI employee” captures invoices from email, codes and matches them in Xero, supports continuous bank reconciliation, and uses Slack for approval notifications and exception alerts. Historical testing preceded go-live.

Capgemini standardized request formats and handoffs before deploying UiPath automation into Oracle R12 for more than 8,500 monthly invoice-creation requests. This is older RPA, not generative AI — and the clearest direct finance proof that transformation comes from redesign plus a capacity decision.

IBM consolidated financial data into an enterprise performance-management platform, added AI-driven forecasting, and reduced more than 500 finance applications to fewer than 20. Analysts refine scenarios and exceptions while the platform predicts roughly 140,000 data points monthly.

PwC combined process elimination, RPA, integration, self-service data, and broad digital upskilling across Business Services. The finance result is not simply time saved: the team’s skill mix and work allocation changed structurally.

Biffa connected field transactions, purchasing, AP, the general ledger, leases, and reporting across roughly 100 legal entities. The volume and control environment make this a strong lighthouse analog, but it remains Structural until the zero-touch rate and avoided-hire baseline are published.

The system replaced layout-specific trained models with whole-document interpretation and removed many manual checks. It is high-volume Act mode in a finance-operations provider; no staffing or P&L decision is disclosed, so the score remains Structural.

A two-person finance team replaced spreadsheet-based clinical-trial accruals with contract-accurate estimates across three to five concurrent studies. Material to the team and directly relevant to the backfill ladder, but not an enterprise-scale cost pool.

Leapfin standardizes operational revenue data, automates complex revenue logic, and exposes an AI agent for analysis and workflow building. The case shows how capacity changes a small team’s role, but the economics are vendor-published and company-specific.

An AI-native ERP unified multi-entity accounting, integrations, reconciliations, revenue recognition, commentary, and transaction matching. The capacity claim is explicit and useful for backfill design, but it remains a young-company vendor story rather than independent enterprise proof.

After a city refused to consolidate 200+ monthly gas, water, and electric invoices, a controller had ChatGPT write Python that pulls the PDFs from email, extracts invoice numbers, dates, amounts, and property names, and outputs an Excel file ready to upload to the accounting system. He published his actual prompts and code — and is candid that it is not commercial-grade.

A recent grad in a Fortune 100 finance org — self-described novice coder — uses a company-approved LLM to write Python automations. Notably disciplined for a grassroots build: the LLM is cleared for confidential financial data, and packages are safety-checked before running.

The interesting part is who is building: not an analyst carving out time, but the finance leader himself — putting deal economics where the sales conversation already happens instead of in a spreadsheet someone has to open.

The most common single workflow in every thread we read: an FP&A manager uses the company’s Copilot license to generate VBA that automates Excel-based reporting. Worth noting the same post argues the profession’s outlook is “bleak” — adoption and anxiety are coming from the same people.

Input: a workbook with cost-center variances to budget and a detail tab. Output: a generated tab per negative variance with its breakdown. The governance improvisation is telling — cost centers and employees are passed as codes and record numbers, not names, to avoid exposing sensitive data.

The analyst never fed ChatGPT confidential data. Instead she described the file schema — “in DataDump1 there’s a column called Rev, in DataDump2 it’s Net Revenue; tag both as Revenue” — then tested the script, pasted errors back, and iterated until it worked.

The full prompt is in the thread: act as a research analyst, study the most recent quarterly filings for Verizon and AT&T, compare performance to the telecom industry, and return a SWOT formatted for a senior executive. A one-person version of what HPE built a platform for.

The documentation flow inverts the usual pattern — instead of drafting from a blank page, the practitioner has the model ask detailed questions about the process, then “it pulls it all together.” Cheap, repeatable knowledge capture for exactly the tribal-process problem every finance team has.

Long-document synthesis is the second-most-cited grassroots pattern after code generation: grant documentation, commercial agreements, and pre-signature research packs get loaded once and queried repeatedly — the persistent-workspace features (Projects, NotebookLM) matter more than the chat.

This is the quiet unlock behind the “self-serve BI” promise: the bottleneck was never the dashboard, it was the formula language underneath it. One practitioner “automated a bulk of my previous job by using power query functions taught to me by GPT.”

The most instructive thread we found on enterprise Copilot: roughly a 50/50 split between practitioners getting real value (deck baselines, search, code) and skeptics who tried the marquee use case — writing — and walked away. The value concentrates where output is verifiable, not where it is stylistic.

Two independent small-firm owners describe AI-assisted tax research (Blue J) displacing legacy subscriptions — it starts the research, helps finish it, and drafts the plain-language client email. The hiring-substitute framing is the notable part: the tool is absorbing work a vacant seat was supposed to do.

Ten years across Big 4 and industry, now running finance at an AI startup — the most bullish credible voice in the sample, and a preview of what finance looks like when tooling constraints disappear. His advice to the profession: “upskill yourselves… learn how to craft with AI.”

Two ends of the same insight: LLM-written Python is only useful to the team if others can run it. Colab notebooks — zero install, shareable link — are the grassroots distribution model showing up before any official platform exists.

The complete transformative fact pattern in a single case: high-volume standardized work, Act mode with humans on exceptions, and an explicit leadership capacity decision. Hiring managers report the redeployed support engineers among their best hires — the redeployment was real, not euphemism.

The most instructive case in the tier. The savings were real, but overshoot surfaced as a quality floor on nuanced cases, and the CEO conceded they cut too far — landing on AI-for-routine, human-service-as-premium. The failure mode of transformation is under-designed exception handling, not AI that doesn’t work.

The only case in the tier where freed capacity became a revenue line instead of a cost line. The 53% of enquiries Billie could not resolve revealed unmet demand for design advice — the reskilling target came out of the bot’s failure data.

Pactum’s agent runs text-based negotiations with thousands of tail-spend suppliers in parallel — contracts that were previously never negotiated at all because humans could not cover the volume. The purest “new capability” case in the tier, with direct margin and working-capital impact.

Amazon Q’s transformation agent upgraded more than half of Amazon’s production Java systems in under six months — the classic “dreaded backlog” that never competes with feature work for staffing. The work got done precisely because no human org ever would have done it.

Included deliberately: this is machine learning from 2017, not generative AI. The transformative pattern — extreme volume, standardized documents, machine owns the transaction — predates the current technology cycle by eight years. The gate was never model capability.

Claims is a control process — intake, validation, fraud screen, payment authorization — run by the machine at native speed with humans on exceptions. Built into the operating model from day one rather than retrofitted, which is why the automation rate keeps climbing.

The compounding case: a bounded virtual assistant, aimed at the highest-volume question types and improved continuously for eight years. No single year looked transformative; the accumulated substitution is five digits of FTE-equivalents.

Treat as directional: ServiceNow’s sales motion depends on this story. Included because “flat headcount while growing” is the second canonical form of the capacity decision — avoidance rather than redeployment — and it is only measurable if the baseline is set before deployment.

Output transformation rather than cost transformation: same company, an order of magnitude more shipped product. The second cautionary signal in the tier: the brand cost came from how the “AI-first, fewer contractors” message landed, not from the technology.

Structural today, T-track if it changes recruiter staffing structurally: the compression directly feeds growth capacity (~300 new restaurants a year at ~30 employees each). The measured outcome is workflow speed, not yet an org-level capacity decision.

Team-scale absorption of correspondence volume with humans still in the loop — every AI email is labeled, and customers can escalate to a person at any point. S rather than T: no disclosed change to the staffing model, and satisfaction leads the story rather than cost.