How Much of Accounts Payable Can AI Really Handle?

The invoices that hold up a payables team are usually not wrong, only unproven: the warehouse hasn't posted the receipt, the supplier left off the PO number, or the price comes from a contract nobody attached to the order.

Each one sits on hold while the supplier calls to ask where the money is, and the ones nobody has time to question get paid as billed.

Ask a vendor how much of that AI can handle and you get a touchless rate, which counts only the invoices nobody had to touch.

The real answer is a setting you make in three places: the tolerance that decides which invoices skip a person, the exceptions whose answer already sits in your own systems, and the few steps a person keeps at any setting.

Here is how to set each one, and how Qvery builds the agent that works your exceptions on autopilot.

The worked month below runs on assumptions; your own month replaces them.

A Touchless Rate Counts Only the Invoices Nobody Touched

A touchless invoice, also called straight-through, goes from the inbox to the payment run without anyone editing, matching or chasing it.

In Ardent Partners' 2026 benchmarks, a survey of nearly 200 AP and finance leaders, the best fifth of teams by cost and speed process 55.2% of invoices with no manual touch. Everyone else manages 31.4%. So even the best teams send 44.8% of their invoices past a person.

Sorting last month's invoices into four piles tells you your own share. The rest of the work sits in the invoices that needed someone, and they aren't one kind of problem.

Sort Last Month's Exceptions by What Would Close Them

Take every invoice that needed someone last month and write down what finally let it be paid.

Missing evidence. The answer was already somewhere in your company: a receipt in the warehouse system not yet posted, a PO the supplier didn't quote, a contract amendment nobody loaded into the order.

A judgment. Someone had to decide: a disputed delivery, a price rise nobody agreed, a bill with no budget owner.

A control. A person acts whatever the documents say: changed bank details, a new supplier's first invoice, the payment run itself.

An invoice with no PO clears against a reference you keep: the contract rate, the subscription price, the budget owner's standing approval. Matching last month's amount isn't proof it's right.

A dispute stays a judgment, but its paperwork needn't: the short-pay note or credit request can be drafted from the receipt and the order, for a person to send.

Now put hours on it. Say 1,200 invoices a month and an exception rate near Ardent's 2026 average of 19.9%: about 240 exceptions. Assume 170 are missing evidence at 15 minutes of chasing each, 60 are judgments at 30 minutes, and 10 are controls at 20 minutes.

That's about 43 hours of chasing, 30 of deciding and 3 of control work. In that month, most of the exception hours go to finding documents, not to making decisions.

A rules engine parks all 170 of those invoices and waits; an agent can go and get the missing document.

Your Tolerance Decides How Many Invoices Skip a Person

An invoice skips a person only when it matches its PO and receipt, isn't a duplicate, and meets its approval rule. The tolerance is the part you set as a number: how far an invoice may differ before someone looks.

Set it two ways at once where your system allows. In Microsoft's Dynamics 365 Finance, for one, a line can carry a percentage and an amount, and exceeding either one stops it. Use both: on a $500 invoice, 2% is ten dollars of rounding, and on a $40,000 one it's $800 nobody checks.

Price the band both ways before you pick it. Say 60 of last month's exceptions were price differences between 1% and 3%. Widening the band from 1% to 3% clears all 60 and gives back the 15 hours they took.

It also means up to 3% of every matched invoice is paid without a look, every month.

So set it by what you buy, not one number for everything:

• Near zero on a fixed-price contract, where any difference is a billing error.
• Freight and tax as their own lines, with their own small band.
• Tight, or none, on a new supplier's first invoices, until you know what normal looks like.

Then write the rule in one sentence an auditor could check: "Pay any line within 2% or $250 of the PO price, whichever is lower, for suppliers with six months of history; hold everything else."

Run it on last quarter's invoices before switching it on, and count both columns: the invoices it would have cleared, and the money it would have waved through.

Releasing Payment and Changing Bank Details Stay With a Person

In a team of two or three, the steps that move money are often one person's job, and payables fraud counts on that.

In the Association for Financial Professionals' 2026 survey of 465 treasury practitioners, business email compromise hit 74% of organizations in 2025, mostly fraudsters posing as suppliers or executives and asking to change payment instructions. The FBI's 2025 crime report puts reported losses to it at $3,046,598,558.

So the agent holds no right to approve, release a payment or edit a supplier record.

A new bank account, a new remit-to address or a second record for the same supplier gets flagged, confirmed by a call to a number already on file (never one from the email), and approved by a second person before the next run.

Every invoice is also checked for a duplicate under a new number, and for one bill split into pieces that each fall under an approval limit. Whoever releases the run sees what the agent cleared since the last one and every supplier record that changed.

Microsoft draws the same line for its own payables agent in Business Central: it prepares draft invoices from the AP inbox and doesn't post them, and a supplier it creates stays blocked until a person unblocks it.

Start the agent where it only proposes: your team works as before, with a note beside each invoice saying what the agent would have done, and it acts on its own once those notes have proved right.

How Qvery Builds the Agent That Works Your Payables Exceptions

The agent we build lives on your AP inbox and your accounting system, and it runs on your company's rules rather than a vendor's defaults. It matches each invoice to its PO and receipt and lets through what passes your written tolerance.

For the rest it does the legwork your team does by email today: it asks the warehouse whether the delivery came, finds the PO the supplier didn't quote, checks a higher price against the contract on file, and holds a bill with no PO against its contract rate.

A judgment reaches its owner as one file: the invoice, the documents and what doesn't match. Payments and supplier records stay with people.

It works on autopilot beside your AP team, inside NetSuite, Sage Intacct, Business Central or QuickBooks, the shared inbox and the payment run they already use.

We begin with how your team closes each kind of exception now, and turn that into the tolerance sentence and the approval lines above. A first working version runs on your real exceptions within two weeks, and we train your AP team and approvers to work with it.

Then every week we report two numbers: hours saved on the exception queue and errors avoided, such as a duplicate stopped, a price above the order held, or a bank change caught before the run.

Count Three Numbers Every Friday

Three numbers tell you whether it's working: the share of invoices that went through untouched, by kind of invoice; the age of the oldest open exception; and what the checks stopped before payment.

A touchless rate that climbs while credits and supplier disputes climb with it is a looser tolerance, not progress. The same count names which receipts arrive late, and from which site, which is the list that gets receiving fixed.

On Monday, pull last month's exceptions and write beside each one what finally closed it. The rows that say "found the document" are how much of your payables an agent can take.