On this page
Can an AI agent do accounts payable?
Yes, for most of the paperwork, and no, for the money. An AI agent for accounts payable can read supplier invoices from your inbox, pull out the data, code each line, match it to a purchase order and leave a draft bill in your accounting system for someone to approve. Agents run this in production today. Genpact reports a logistics client reaching about 65% touchless invoice processing with AI agents, and Twistag reports an agent processing more than 2,000 invoices a month for Aralab, a manufacturer. Both figures come from the vendors. Conventional AP automation sets the baseline agents are measured against: Esker reports that G's Group cut invoice processing from 17 to 5 days while handling nearly 70,000 invoices a year with a 10-person AP team.
What an agent should not do on its own is create vendors, change bank details, approve spending or release payments. Even Microsoft's Payables Agent, built into Business Central, drafts invoices but does not post them, and Microsoft lists approval flows and anomaly detection as unsupported. So treat this as a supervised hire: the agent does the keying and matching, and a person owns every decision that moves cash.
This page covers the invoice-to-approval part of AP. For expense reports see expense review and audit, and for the clerk role as a whole see accounts payable clerk.
What the agent does and what stays with you
Agent
- Collect invoices from the AP inbox and supplier portals
- Extract header and line data from invoice PDFs
Agent with review
- Identify the vendor and catch duplicates
Human
- Set up a new vendor and its bank details
Agent with review
- Code invoice lines to GL accounts and cost centers
- Match invoices to purchase orders and receipts
- Chase missing information with suppliers and requesters
Human
- Approve invoices for payment
- Release the payment run
Agent
- Report on aging, discounts and exceptions
10 tasks: 3 agent, 4 agent with review, 3 human
| Task | Who does it | Why |
|---|---|---|
| Collect invoices from the AP inbox and supplier portals | Agent | Microsoft documents its agent monitoring a mailbox and importing each PDF attachment, which is mechanical and easy to spot-check. |
| Extract header and line data from invoice PDFs | Agent | Extraction is the most mature step; the output can be checked against the PDF by sampling. |
| Identify the vendor and catch duplicates | Agent with review | Microsoft's agent stops and asks a supervisor when it cannot identify the vendor with confidence. |
| Set up a new vendor and its bank details | Human | A vendor created by Microsoft's agent stays blocked from processing until a relevant stakeholder unblocks it, and Microsoft says its agent provides no vendor approvals; vendors and bank accounts are usually confirmed by calling the vendor, which Microsoft says many places require for an audit. |
| Code invoice lines to GL accounts and cost centers | Agent with review | Agents suggest coding from invoice history and rules; the supervisor reviews, confirms, or changes the suggested purchase-document details before finalization. |
| Match invoices to purchase orders and receipts | Agent with review | Matching is rule-checkable, but price and quantity mismatches need a person to decide. |
| Chase missing information with suppliers and requesters | Agent with review | Messages leave the company, so a person should approve templates and unusual requests. |
| Approve invoices for payment | Human | Approval is a spending decision under your delegation of authority; Microsoft's agent does not run approval flows. |
| Release the payment run | Human | Moving money is irreversible in practice and is the main target of business email compromise. |
| Report on aging, discounts and exceptions | Agent | Reports are read-only summaries a person can check against the ledger. |
The split follows one rule: the agent can do anything a reviewer can check against a document, and a person does anything that commits the company. Extraction and reporting can be checked by sampling, so they go to the agent. Coding, matching and supplier follow-up are where agents save the most time but also make judgment errors, so each output that the agent flags gets a human decision. Vendor setup, approval and payment stay human.
The vendor-setup line matters more than it looks. Microsoft's documentation says that when its agent creates a vendor, the vendor stays blocked from processing until a relevant stakeholder unblocks it, and that the agent itself provides no vendor approvals. Microsoft explains that vendors and their bank accounts are usually confirmed by calling the vendor's finance department, and that in many places this is required for a successful audit. Keep that step even if your tool lets you skip it.
A worked example: one invoice
This is an illustration, not a customer story.
An invoice for $4,180 arrives from a packaging supplier as a PDF attached to an email. The agent picks it up from the AP mailbox, extracts the vendor, invoice number, date, three line items, sales tax and total, and finds the vendor in your vendor list. It checks for an earlier bill with the same number and amount and finds none. It codes two lines to packaging materials and one to freight, using last quarter's bills from the same supplier as reference. It matches the invoice to a purchase order for 2,000 boxes, but the receiving record shows 1,800 received, so it flags a quantity variance.
The draft bill lands in the accounting system with a note: "PO 1182: invoiced 2,000, received 1,800, variance $360." Your AP owner opens the flagged draft, confirms with the warehouse that the last 200 boxes arrive next week, and holds the invoice. Nothing was posted or paid by the agent. If the same email had also said "please note our new bank details," the agent would route it to the vendor-change procedure, and a person would call the supplier on the number already on file.
What you need to provide
The agent touches financial data (amounts, bank details, payment terms) and some personal data, because many small suppliers are sole traders invoicing under their own names. Give it the least access that gets the job done:
- Read access to the AP mailbox. Microsoft recommends a shared, internal-only mailbox that only the agent processes, so employees see invoices before the agent and stray emails stay out.
- A user in your accounting system that can create draft bills but cannot post, approve or pay.
- Your chart of accounts, cost centers and tax codes, plus a few months of posted bills so the agent can learn how you code each supplier.
- Open purchase orders and receiving records, if you use them.
- Your coding rules and approval thresholds, in writing. If they live only in someone's head, write them down first; the agent will be as consistent as the rules it gets.
Check the limits of whatever tool you use. Microsoft's agent, for example, processes only emails with PDF attachments, skips emails with more than 10 attachments, and handles at most 500 invoices a day. Invoices outside those limits need a manual route.
Job brief template
Use this as the brief for a vendor, an operator or an internal team setting up the agent. Replace the bracketed values with your own.
Copy-ready brief
- Goal
- Every supplier invoice that reaches the AP inbox is captured, coded, matched and queued for approval in the accounting system within one business day of arrival.
- Deliverable
- A draft bill for each invoice in the accounting system, with coding, PO match status and a short note on anything flagged, plus a daily exceptions list sent to the AP owner.
- Inputs
- Read access to the AP mailbox (a shared, internal-only mailbox is preferable)
- A user role in the accounting system that can create draft bills but cannot post or pay
- Chart of accounts, cost centers and tax codes export
- Vendor master list and 3–6 months of posted bills as coding history
- Open purchase orders and goods receipts, if you use POs
- Written coding rules and approval thresholds
- Acceptance criteria
- On a 50-invoice sample, header data (vendor, invoice number, date, total, tax) matches the PDF with at most 1 error.
- On the same sample, GL coding matches what the AP owner would choose with at most 2 errors.
- Every invoice arriving on a business day appears as a draft or on the exceptions list by the end of the next business day.
- No duplicate invoice (same vendor, number and amount) reaches the approval queue.
- No bill is posted, approved or paid by the agent, and no vendor record or bank detail is created or changed without a person's sign-off.
- Systems
- accounting system or ERP (for example QuickBooks Online, Xero, NetSuite or Business Central)
- email inbox for incoming invoices
- purchasing or receiving records, if you use purchase orders
- Constraints
- Invoices contain supplier bank details and personal data of sole traders; access is limited to the AP mailbox and AP module.
- The agent's account has no permission to post, approve or pay.
- Vendor creation and bank detail changes follow your existing verification procedure.
- Your retention and data-location rules apply to any copies the agent's provider stores.
- Volume
- Example: 200–2,000 invoices a month
- Cadence
- Example: daily, with a weekly exceptions review
- Human checkpoints
- New vendor or changed bank details: a person verifies by phone using a number already on file.
- Flagged invoices (no PO match, price or quantity variance, unknown vendor): the AP owner decides.
- Invoice approval: the budget holder approves under your thresholds.
- Payment run: a second person reviews and releases.
The acceptance criteria are the part to keep. A sample of 50 invoices checked against the PDF and against your AP owner's coding tells you more than any vendor accuracy claim.
What it costs
Human benchmark
Bookkeeping, accounting, and auditing clerks (includes accounts payable clerks)
$50,670
per year (median annual wage)
BLS OEWS 2025 national median for SOC 43-3031, as published by O*NET OnLine; wage only, no benefits or overhead
Source: 43-3031.00 - Bookkeeping, Accounting, and Auditing Clerks
Agent price range
$0.65 to $1.80
per invoice
Nanonets prices per block run with a $100 a month minimum for 100 credits after $50 in free credits; at its stated upper end of 6 blocks per invoice x $0.30 per run = $1.80 per invoice. Rhocash: $1.50 per invoice on Starter ($299 a month, up to 200 invoices) down to $0.65 per invoice on Business ($1,299 a month, up to 2,000 invoices). Plan minimums differ, so per-invoice rates are not directly comparable. Setup, payment fees and accounting software excluded.
Sources: AP automation pricing, Nanonets pricing
The two figures use different units. Compare them at your own volume.
The human figure is the 2025 national median annual wage for bookkeeping, accounting and auditing clerks (SOC 43-3031), the group that includes accounts payable clerks, as published on O*NET OnLine from BLS data. It is wage only. The agent figures are published prices from two vendors, and each comes with a monthly minimum. Rhocash charges $1.50 per invoice on its Starter plan at $299 a month for up to 200 invoices, down to $0.65 per invoice on its Business plan at $1,299 a month for up to 2,000 invoices. Nanonets prices each block run (one step of a workflow) from $0.02 to $0.30, with a $100 a month minimum for 100 credits once the free $50 in credits is used; it says a typical invoice workflow runs 4 to 6 blocks, so at the upper end, 6 blocks x $0.30 per run = $1.80 per invoice. Because the minimums differ, compare total monthly cost at your volume, not the per-invoice rates alone. Nanonets quotes its Growth plan on request and Rhocash prices Enterprise as custom. Microsoft's Payables Agent bills in Copilot Credits that vary with the interaction, with no per-invoice figure published.
Two costs sit outside both numbers: the time your reviewer spends on exceptions, and the setup work of writing down coding rules. Neither has a reliable public figure, so measure both in your trial.
Risks and human checkpoints
A fraudulent invoice or a forged bank-detail change is processed as genuine.
How you notice it
Track every bank-detail change and first payment to a new account; the FBI's IC3 recorded about $3.05 billion in business email compromise losses in 2025.
Lines are coded to the wrong GL account or cost center, and the error spreads through month-end.
How you notice it
Sample 20–50 drafts a week against the AP owner's coding and watch for spikes in reclasses at close.
Duplicate invoices are paid, for example a PDF and a paper copy, or a resend with a changed number.
How you notice it
Run a weekly duplicate report on vendor, amount and date, separate from the agent's own check.
Invoices go missing because the agent skips them, such as emails with no PDF or with too many attachments.
How you notice it
Reconcile the count of emails received against drafts plus exceptions each day; Microsoft documents both of these skip cases for its agent.
Wrong PO matches on partial deliveries or split orders lead to paying for goods not received.
How you notice it
Review every invoice with a quantity or price variance before approval, and sample matched invoices against receipts.
Human checkpoints
- New vendor or changed bank details: a person verifies by phone using a number already on file.
- Flagged invoices (no PO match, price or quantity variance, unknown vendor): the AP owner decides.
- Invoice approval: the budget holder approves under your thresholds.
- Payment run: a second person reviews and releases.
Fraud is the risk that justifies the checkpoints. The FBI's Internet Crime Complaint Center recorded about $3.05 billion in reported losses to business email compromise in 2025. That figure is about attacks on businesses, not on AP agents, but it is a reasonable inference that an agent reading invoices from email could meet the same forged invoices and bank-change requests your team sees today. The control is not a better model; it is keeping vendor changes and payments behind a person and a phone call.
The quieter risk is volume that disappears. If the agent skips an email it cannot process, nobody may notice until a supplier chases payment. A daily count of emails in, drafts out and exceptions raised catches this early.
How to run a trial
Run the agent alongside your current process for one month before you rely on it.
- Pick a slice: one entity or 3–5 high-volume suppliers, ideally with a mix of PO and non-PO invoices.
- Set the agent's permissions to draft only. Your team keeps processing as usual.
- Each week, compare 50 agent drafts with what your team booked: header data, GL coding, PO match and flags. Count errors against the brief's acceptance criteria.
- Log every exception the agent raised and every one it missed. A missed variance matters more than ten false alarms.
- Time your reviewer. Minutes per invoice reviewed is the number that decides whether the agent saves money.
- Send a test invoice with a changed bank account through the normal channel and confirm it lands in the vendor-change procedure, not the approval queue.
Pick a slice
One entity or 3–5 high-volume suppliers, ideally with a mix of PO and non-PO invoices
Set the agent's permissions to draft only
Your team keeps processing as usual
Each week, compare 50 agent drafts
With what your team booked: header data, GL coding, PO match and flags
Log every exception
The ones the agent raised and the ones it missed
Time your reviewer
Minutes per invoice reviewed decides whether the agent saves money
Send a test invoice with a changed bank account
Confirm it lands in the vendor-change procedure, not the approval queue
If the drafts meet the criteria for two weeks in a row, stop double-processing that slice and widen it. For more on structuring the test, see how to run a paid trial with an AI agent, and for writing the brief itself, how to write a job description for an AI agent. Related finance jobs: accounts receivable, month-end close and the finance overview.
This page is not financial, tax or accounting advice.
Sources
- Payables Agent overview in Business Central
Microsoft LearnPrimaryAccessed Nov 14, 2026
- 43-3031.00 - Bookkeeping, Accounting, and Auditing Clerks
O*NET OnLine (U.S. Department of Labor)PrimaryAccessed Nov 14, 2026
- 2025 IC3 Annual Report
FBI Internet Crime Complaint CenterPrimaryAccessed Nov 14, 2026
- Powering 65% touchless accounts payable with agentic AI
GenpactVendorAccessed Nov 14, 2026
- An autonomous AP agent handling 2,000+ invoices a month
TwistagVendorAccessed Nov 14, 2026
- G's Group accelerates invoice processing with Esker
EskerVendorAccessed Nov 14, 2026
- Nanonets pricing
NanonetsVendorAccessed Nov 14, 2026
- AP automation pricing
RhocashVendorAccessed Nov 14, 2026
What we could not verify
- Touchless rates (Genpact client ~65%, Twistag/Aralab 80%) are vendor-reported for single deployments; no independent study of agent accuracy on AP was found.
- Copilot Credit consumption per invoice for Microsoft's Payables Agent is not published, so it is not in the cost range.
- Only two vendors' published prices are in the cost range: Nanonets lists Growth as quote-based and Enterprise as custom, and Rhocash lists Enterprise as custom while publishing three other tiers. How other AP vendors price was not checked.
- No public incident report was found of an AP agent itself paying a fraudulent invoice; the fraud risk is inferred from the IC3 business email compromise data and Microsoft's vendor-approval guidance.
Related
- AI agents for finance: jobs they do and how to hire one
- Can AI replace accounts payable clerks? Task by task
- Can AI replace bookkeepers? A task-by-task answer
- AI agent for expense audit: what it checks, who approves
- AI agent for month-end close: what it does and needs
- AI agent for accounts receivable and collections
- AI agent job description: how to write one, with template
- How to test an AI agent before buying: run a paid trial
