Curated research

What finance teams actually think about AI

AI in finance statistics, each traced to its source: 59% of finance functions now use AI (Gartner, 2025), yet only 2.7% of finance staff would let it make judgment calls on its own (Deloitte, 2025). Finance teams are not sceptical about whether AI works. They are sceptical about letting it act unsupervised — and that single distinction explains almost everything else in the data. Each figure below carries its publisher, its year and a link to the document it came from.

Last updated:

Sources cited: 21

Want to know where your team sits against these numbers?

On a 30-minute call a Chartered Accountant will go through your process and tell you plainly which parts AI can take over safely today.

“Reza had some great suggestions and we ended up with a plan much better than what I was thinking of.”
Oliver Burke, Propeller Digital · Upwork client review

Why is AI the top finance priority but still not in production?

This is the widest gap in the data. Finance leaders expect AI to become standard equipment within a few years, and say so in large numbers. The share that has actually put it into daily use is far smaller — and in the most recent measurement, it barely moved at all.

AI use in the finance function, by year

Gartner's own series, asked the same way three years running. The jump happened in 2024. 2025 was flat.

2023
37%
2024
58%
2025
59%

What we take from this

Read the two adoption numbers together rather than picking the flattering one. Gartner asks a narrow question of a small, senior sample and gets 59%. KPMG asks a broader one of a thousand finance leaders and gets 75%. Both can be true, because "using AI" stretches from a chatbot somebody opened once to an extraction pipeline that feeds the ledger nightly. Anyone quoting a single adoption figure without saying which question it answers is not telling you much.

The number that is hard to argue with is the 91% reporting low or moderate impact at first. That is not a technology failure. It is what happens when a pilot runs on a sample of documents, in a sandbox, without the integration work that would let it touch the real process. The pilot succeeds and nothing changes, because nothing was ever wired in.

Our own read, from building these systems: the projects that stall are almost never stopped by model quality. They stop at the boundary — the ERP that will not accept a write, the approval step nobody owns, the exception queue with no home. That work is unglamorous, it is most of the job, and it is what separates a demo from a deployment.

Would a finance team let AI post an entry without a human checking?

Almost never — and the figure is starker than the general debate about AI at work would suggest. When Deloitte asked finance and accounting professionals how much decision-making authority they would hand an AI agent, the share willing to let it exercise judgment on its own did not reach three in a hundred.

How much decision authority finance staff will give an AI agent

Deloitte, 2025. The middle bar is the real finding: most people are not refusing AI, they are refusing unsupervised AI.

Only within a defined framework
59.7%
Not in any capacity
19.9%
Always, including judgment calls
2.7%

What we take from this

This is the section that explains every other section on the page. The bottleneck in finance AI is not capability, and has not been for a while. It is that the people who sign the accounts will not put their name to a system that acts without them.

Look at the shape of the answer, though, because it is more useful than the headline. Only one in five refuses AI outright. Six in ten will accept it inside a defined framework. That is not resistance — it is a specification. It tells you exactly what to build: something that proposes, evidences the proposal, and then waits.

Every build we ship works that way, because it is the only shape finance teams accept. AI drafts the collections email and a person releases it. AI extracts the invoice and a reconciliation gate checks the arithmetic before anything reaches the ERP. The autonomy people actually want handed over is autonomy over the reading and the keying, never over the decision.

Will AI replace accountants, or just the data entry?

The fear is real and widely reported. The labour statistics point somewhere more specific: the routine keying role is shrinking, the qualified accounting role is growing faster than the economy, and the official explanation for the shrinkage describes work being reshaped rather than removed.

Projected US employment change: two accounting occupations

Same profession, opposite directions. Bars show magnitude; the clerks figure is a decline. Source: US Bureau of Labor Statistics.

Accountants & auditors (2024–34)
+5%
All occupations, average
+3%
Bookkeeping & accounting clerks (2025–35)
−6%

What we take from this

The two BLS lines are the most useful pair of numbers on this page, because they come from the same agency, use the same method, and disagree with each other in exactly the way the headlines do not. Qualified accountants: growing faster than the economy. Clerks doing the keying: shrinking.

And the agency's own stated reason is not "replaced by software". It is that the same people move into analysis and advisory work once the routine entry stops. That is a description of a job changing, not ending — which matches what we see on site. Nobody has been let go because an extraction pipeline went live. The month-end just stopped eating the first week of it.

Where the fear is well-founded is in roles defined entirely by rekeying. If a job is transcription from a PDF into an ERP and nothing else, the honest answer is that the job is genuinely exposed. The realistic response is the one the BLS is already describing: move the person up the chain into exception handling, controls and analysis, which is work that needs somebody who understands the ledger.

Which finance jobs do teams actually hand to AI first?

There is a clear ordering, and it tracks the trust data almost exactly. The work that gets automated first is the work where a mistake is visible, cheap and caught immediately. The work that stays human is the work where a mistake is expensive and quiet.

Most-adopted AI use cases in finance functions

Gartner, 2025. Three use cases were adopted by more than a third of finance organisations already running AI.

Knowledge management
49%
Accounts payable automation
37%
Error & anomaly detection
34%

What we take from this

Accounts payable sits second for a reason that has nothing to do with how interesting it is. An invoice has a right answer printed on the face of it. If the extraction is wrong, the arithmetic fails, the purchase-order match fails, and the exception surfaces before anything posts. It is the safest possible place to put a model, because the model's work can be checked by machine rather than by trust.

Anomaly detection ranks third for the same reason inverted: the AI never decides anything, it only raises a hand. A false positive costs a minute of somebody's attention. That is a risk profile a controller can sign off without a governance committee.

What sits far down the list — anything requiring judgment about a customer relationship, a disputed charge, a write-off — is exactly what the trust data predicts. Teams are not ranking use cases by how much value is available. They are ranking them by how quickly a mistake becomes visible. Start where the feedback loop is tightest and you get the adoption; start where the prize is biggest and you get a stalled pilot.

What actually blocks AI adoption in a finance team?

Not the model. Across every survey we could verify, the blockers cluster in the same three places: the state of the data, the systems the data lives in, and whether anyone could prove afterwards what the AI did.

Assurance-readiness changes the outcome

KPMG, 2026. Organisations able to evidence what their AI did report materially better results than those that cannot.

Error reduction — assurance-ready
33%
Error reduction — not assurance-ready
6%
Confident scaling AI — assurance-ready
42%
Confident scaling AI — not assurance-ready
14%

What we take from this

The assurance finding deserves more attention than it has had. It is not saying that careful organisations are pleasanter to deal with. It is saying that the ability to evidence what the AI did is what separates deployments that actually reduce errors from ones that do not — a five-fold difference on KPMG's own numbers.

That fits the pilot problem in the first section exactly. A pilot proves a model can read an invoice. Production requires that you can show an auditor, eleven months later, which version of which document produced which posting, and what the system was told at the time. Almost none of the effort in a pilot goes there. Almost all of the effort in a real deployment does.

So the readiness question for a finance team deciding where to start is not "is the AI good enough yet". It is "is our data reachable, and could we prove what happened". Both are answerable in an afternoon, before committing budget to anything — which is the entire point of the assessment linked below.

Why is AI held to a higher accuracy standard than people?

Because it is, measurably, and the research explaining why predates the current wave by a decade. People forgive a human error and generalise from a machine one. In finance this surfaces as a demand not merely for accuracy, but for accuracy that can show its working.

Acceptable error rate: AI against a human doing the same task

Lenskjold et al., BJR Open, 2023 (n = 44). Respondents allowed a human roughly two-thirds more error than they allowed the machine.

Acceptable from a human
11.3%
Acceptable from AI
6.8%

What we take from this

The Sage finding is the one to keep. A finance leader will turn down a tool that is right ninety-nine times in a hundred if it cannot show its working. That means explainability is not a feature competing with accuracy for space on the roadmap. It is a gate standing in front of accuracy: a system that cannot be interrogated never gets to compete on being right.

There is a sting in the KPMG data worth sitting with, though. The same population that demands machine-grade accuracy also reports that two-thirds of employees use AI output without checking it, and that more than half have made mistakes as a result. The stated standard and the actual behaviour are not the same standard. People want the machine to be perfect and they are not, personally, verifying that it is.

That gap is the argument for building the check into the system rather than into the policy. Asking people to reliably verify AI output does not work — the numbers above are what that looks like in practice. Making the arithmetic reconcile before anything can post does work, because it does not depend on anyone remembering to care at half past five on a Friday.

Answers

Short, sourced answers to the questions finance leaders most often ask about trusting AI and what it returns. Each leads with a figure from the research above, names its source, and shows what the same thing looks like in a system Fintask has built.

Should finance teams trust AI VAT and billing tools?

Yes, but only inside a defined framework: that is the position of 59.7% of finance and accounting professionals, against 2.7% who would let an AI agent make judgment calls on its own (Deloitte, 2025). The responsibility does not move to the software. Under HMRC's VAT Notice 700/22, Making Tax Digital software shows you the return and asks you to declare the information is correct before it is submitted. So trust a VAT or billing tool that shows the transaction behind every figure and leaves the final submit with a person; 71% of finance leaders would reject even a 99%-accurate tool that cannot explain its answers (Sage, 2026, a vendor survey).

Sources: Deloitte, 2025; HMRC, VAT Notice 700/22, 2022; Sage, 2026

From a Fintask build

Fintask builds work this way. In the accounts payable system built for a Canadian industrial safety distributor, a reconciliation gate checks every extracted invoice before anything reaches the ERP, and in its first production run it stopped a $23,908 extraction error. Read the case study

Go further: Invoice automation · How we control what AI can do

How do finance teams build trust in AI-generated journal entries and reconciliations?

By making the AI propose, evidence and wait. Only 2.7% of finance professionals would let an AI agent decide on its own, while 59.7% accept one that works inside a defined framework with judgment left to people (Deloitte, 2025). Before trusting an AI-drafted entry, check that it links to its source document, that the totals reconcile by machine rather than by eye, and that a named person approves the posting. That evidence trail pays: organisations able to show what their AI did report error reduction at 33%, against 6% for those that cannot (KPMG, 2026).

Sources: Deloitte, 2025; KPMG, 2026

From a Fintask build

In the collections agent Fintask built for a Norwegian equipment rental group, every email chasing its 1,080 open invoices is drafted by AI and approved by a person, every figure in a draft comes from ledger data, and legal threats or bankruptcy mentions go straight to a human. Read the case study

Go further: Accounting automation · Accounts receivable automation

Do finance teams trust automated discrepancy detection over manual review?

Increasingly, yes: error and anomaly detection is the third most adopted AI use case in finance, run by 34% of finance organisations that use AI (Gartner, 2025). It earns trust because it never decides anything; it only flags, so a false alarm costs a minute of someone's time. The advantage over manual review is coverage, because an automated check runs on every transaction where a person usually samples.

Sources: Gartner, 2025

From a Fintask build

For an Irish pan-European freight operator, the Fintask job-costing system surfaced a €41,000 cost gap across 13 trip legs that the transport management system had missed: found by the system, not by an accountant. Read the case study

Go further: ERP finance automation

How much of the financial close can realistically be automated with AI today?

No survey measures a single percentage, but the parts that automate well are clear: reconciliations, transaction matching and draft journals. Only 31% of organisations automate most or all of their reconciliations, and half of them close the quarter within six business days, against a third of those with little or no automation (Ventana Research / ISG, 2023). In earlier Ventana research, 88% of companies applying substantial automation closed the month within six business days, against 40% applying little or none (2019); the cross-industry median close is 8.0 days (APQC). What stays human is judgment: accruals, provisions and anything a controller signs for.

Sources: Ventana Research / ISG, 2023; Ventana Research, 2019; APQC, 2026

From a Fintask build

In the Fintask build for an Irish pan-European freight operator, more than 110,000 toll and fuel-card transactions a year are allocated to individual jobs and mapped to Sage nominal codes automatically, work the finance team used to do in Excel. Read the case study

Go further: Accounting automation · Month-end close statistics

What is the ROI of AI in finance?

71% of finance leaders say AI is meeting or exceeding their ROI expectations, with the strongest returns in decision quality, forecast accuracy and responsiveness (KPMG, 2026, 1,013 finance leaders). Early results are usually modest: 91% reported low or moderate impact at first (Gartner, 2025), because a pilot that is not wired into the ledger changes nothing. The clearest measured return is in accounts payable, where the best 20% of organisations process an invoice for $2.65 against an average of $9.84 (Ardent Partners, 2025).

Sources: KPMG, 2026; Gartner, 2025; Ardent Partners, 2025

From a Fintask build

Fintask's AI invoice processing for a Canadian industrial safety distributor extracts around 1,500 supplier invoices a month and matches them to purchase orders before they reach the ERP. Read the case study

Go further: Automation ROI calculator · AP cost per invoice calculator

How do finance teams scale without hiring?

By raising output per person rather than headcount. The cross-industry median is 12,000 invoices processed per accounts payable FTE a year (APQC), and teams well below it are usually losing the difference to rekeying. Hiring is getting harder anyway: 55,152 US accounting degrees were awarded in 2023–24, down 6.6% (AICPA, 2025), against about 124,200 projected openings for accountants and auditors a year (US Bureau of Labor Statistics). More finance organisations are now focused on upskilling their existing teams (38%) than on hiring for new skills (28%) (KPMG, 2026).

Sources: APQC, 2026; AICPA, 2025; US Bureau of Labor Statistics, 2025; KPMG, 2026

From a Fintask build

A Norwegian equipment rental group runs a €7.6M receivables ledger with a one-person AR team; the Fintask collections agent drafts the chasers for its 1,080 open invoices and that person approves them. Read the case study

Go further: Accounts receivable automation · Accounts payable automation

What is the trust cost of AI in finance, and how does it slow adoption?

Trust is the single leading barrier to agentic AI in finance, named by 21.3% of finance professionals, ahead of integration with existing systems at 20.1% (Deloitte, 2025). The cost shows up as stalled projects: 91% of finance AI users reported low or moderate impact at first (Gartner, 2025), and Gartner predicts more than 40% of agentic AI projects will be cancelled by the end of 2027 on cost, unclear value or weak risk controls. The fix is evidence rather than persuasion: organisations that can evidence what their AI did report 42% confidence in scaling it, against 14% for the rest (KPMG, 2026).

Sources: Deloitte, 2025; Gartner, 2025; Gartner, 2025; KPMG, 2026

From a Fintask build

Fintask's collections workspace for a US insurance services firm risk-scores 7,700+ open invoices across 1,200 customers every day and escalates them, leaves every decision to the team, and was built without touching their ERP. Read the case study

Go further: Free AI readiness assessment · How we control what AI can do

Want these numbers put against your own process?

A 30-minute call with a Chartered Accountant who builds these systems. You leave knowing which parts are safe to automate first.

How this page was put together

Every figure was read out of the publisher's own document — the report, the press release, the paper, the statistical handbook — and not out of an article quoting it. Each line carries the publisher, the edition and a link, so you can check any of it in a click.

Statistics are tagged by where they come from. Official statistics, academic work and independent research are stronger evidence than a vendor-commissioned survey. Vendor research is included where the sample is large and the method is disclosed, but it is labelled so you can weigh it accordingly — one figure on this page carries that tag.

Where two credible surveys disagree — as Gartner and KPMG do on how many finance functions actually use AI — both are printed with the disagreement explained, rather than picking the one that suits the argument. And where a widely-repeated statistic could not be traced to a document we could open, it was left out: that cost this page the much-quoted S&P Global figures on abandoned AI projects, which sit behind a subscription with only trade-press quotes retrievable.

Two sources are older than the five-year bar this page normally applies. Both are kept deliberately: the 2015 algorithm-aversion paper, still the reference for why a machine error is punished harder than a human one, and KPMG's 2023 measurement of whether financial reporting leaders expect AI to take their jobs, which nothing since has asked as directly.

Reviewed annually. Gartner's AI in Finance survey lands each November, KPMG's Global AI in Finance each May and the BLS projections each year, so this page is re-checked against the newest editions every August.

Questions people ask

What percentage of finance teams use AI?

59% of finance leaders used AI in finance in 2025, against 58% in 2024 and 37% in 2023 (Gartner, 183 leaders). KPMG's May 2026 survey of 1,013 finance leaders put it at 75%, up from 30% in 2024. The surveys ask different questions, so cite the question too.

Would finance teams let AI post a journal entry or pay an invoice without human review?

Very few. In a January 2025 Deloitte poll of more than 3,300 finance professionals, 2.7% trust AI agents to always make decisions, including judgment calls. 59.7% trust them only within a defined framework and 19.9% not at all. Trust was the leading adoption barrier, named by 21.3%.

Will AI replace accountants?

The labour data points to reshaping, not replacement. The US Bureau of Labor Statistics projects accountant and auditor jobs to grow 5% from 2024 to 2034, against 3% for all occupations, while bookkeeping, accounting and auditing clerks decline 6% from 2025 to 2035 as routine tasks are automated.

Which finance processes do teams automate with AI first?

Three use cases were adopted by more than a third of finance teams already using AI (Gartner, 2025): knowledge management (49%), accounts payable automation (37%) and error and anomaly detection (34%). Each can be checked mechanically, since an invoice has a right answer and an alert only raises a hand.

What is the biggest barrier to AI adoption in finance?

Data and trust, not the technology. 36% of finance leaders cite data quality as their biggest barrier (KPMG, 2026), and Gartner names data literacy and data quality as the largest obstacles. In Deloitte's 2025 poll, trust led at 21.3%, ahead of system integration at 20.1% and skills shortages at 13.5%.

Is AI held to a higher accuracy standard than humans in finance?

Yes. 71% of finance leaders would reject a 99%-accurate AI tool that could not explain its answers (Sage, 2026). A 2023 BJR Open study found people accept a 6.8% error rate from AI against 11.3% from a human. Dietvorst, Simmons and Massey documented this algorithm aversion in 2015.

The bottleneck is trust, not technology

If the numbers above describe your team — convinced by the idea, unwilling to let anything post unsupervised, unsure whether your systems could even evidence what happened — that is the normal starting position, and a solvable one. The assessment is free and tells you where your data and process actually stand.