Accounts payable (AP) is the money a business owes to its suppliers for goods and services received but not yet paid for, recorded as a liability. The term also covers the process and team that receive invoices, check them, record them and pay them. It is where AI agents meet real payments, so bounds matter most here.
Why does accounts payable matter once agents act?
AP is full of reading and matching: invoices arrive by email in many formats, each must be checked against a purchase order and a goods receipt, coded to the right account and scheduled for payment. That is ideal agent work.
It is also where fraud concentrates. Fake invoices, duplicate invoices and, above all, requests to change a supplier's bank details all arrive by the same email route as genuine ones. An agent that trusts an emailed invoice or a letter asking for a new account number can send money to a criminal at machine speed. The safe design keeps the agent on preparation and keeps payment release, and any bank detail change, with people.
How does accounts payable work in practice?
A typical AP cycle runs:
| Step | What happens | Agent's role |
|---|---|---|
| Receive | Invoices arrive by email, portal or post | Reads and extracts the details |
| Match | Invoice checked against purchase order and receipt | Matches and flags differences |
| Code | Assigned to the right account in the chart of accounts | Proposes coding |
| Approve | Budget holder approves | Routes for approval |
| Pay | Payment run prepared and released | Prepares the run; a person releases |
Our guide on connecting an AI agent to your accounts payable automation tool covers the connections and permissions.
An example from a manufacturer
Take a manufacturer whose AP agent processes several hundred invoices a week. One morning an email arrives, apparently from a regular supplier, with an invoice and a note that the supplier has changed banks. The invoice matches an open purchase order exactly.
The agent processes the invoice against the existing supplier record. It does not change the bank details, because a bank detail change is outside its role and the email is external information, which cannot authorise a payment change. It flags the request for the supplier management team, who call the supplier on the number already on file. The supplier has not changed banks.
How is accounts payable different from accounts receivable?
Accounts payable is what the business owes others. Accounts receivable is what others owe the business. AP is a liability; AR is an asset.
For agents, the risk runs in opposite directions. In AP, the danger is money leaving wrongly: paying a fake invoice, a duplicate or a fraudster's account. In AR, the danger is mainly in how customers are treated when chasing payment, and in recording cash correctly. AP agents need the tightest payment controls; AR agents need the tightest conduct controls.
Which terms sit next to accounts payable?
- Days payable outstanding: how long, on average, the business takes to pay suppliers.
- Three-way match: checking invoice, purchase order and goods receipt agree.
- Payment run: the batch of supplier payments released together.
- AP balances feed the figures an agent might use to prepare management accounts.
Where Pryme fits
In Pryme, an emailed invoice arrives as external provenance and a supplier's master record as sealed. External claims cannot authorise a payment, so a bank change in an email can never reach the payment run. Preparing a run is depth 3 work; releasing it is depth 4, and most firms keep release held for a named person, as set out in AI agents for finance: books you can audit.
Questions people ask
Can an AI agent pay invoices on its own?
It can prepare payments. Releasing them is a depth 4 action that moves money, which most firms keep with people, at least above a low limit and always for new suppliers or changed details.
How do agents catch duplicate invoices?
By comparing supplier, amount, date and invoice number across open and paid invoices, including near matches such as a changed digit. Possible duplicates are held for a person.