Short answer: The accounts payable process is the sequence a business runs to turn a supplier invoice into a payment: receive the invoice, capture its data, match it against the purchase order and receipt, route it for approval, resolve exceptions, schedule payment, pay, and reconcile. The job of the process is not speed for its own sake. It is to make sure you pay the right vendor, the right amount, once, on time, with an audit trail that proves it.
Last updated: July 2026.
Accounts payable is the process that everyone notices only when it fails. Nobody praises the team that paid 4,000 invoices correctly. They hear about the duplicate payment, the supplier who put the account on credit hold two days before a shipment, and the invoice that sat in someone's inbox for three weeks because the approver was on leave and there was no backup.
What follows is the process as it actually runs, the flow chart behind it, the controls that matter, and the numbers that tell you whether yours is competitive.
What is the accounts payable process?
Accounts payable is the money your business owes suppliers for goods and services it has already received but not yet paid for. It sits on the balance sheet as a current liability. The accounts payable process is the operational cycle that clears that liability in a controlled way.
Every step in it exists to answer one of four questions:
- Is this invoice real? Did we actually order this, from this vendor?
- Is it right? Does the amount match what was agreed and what we received?
- Is it approved? Did someone with the authority to spend this money say yes?
- Has it already been paid? The single most expensive question in AP, and the one most often skipped.
Strip any of those out and the process gets faster and worse. That is the tension the whole function lives in, and it is why AP is one half of a pair: the payables side of the ledger mirrors the collections side, and the two behave very differently, which is worth understanding through the differences between accounts payable and accounts receivable.
The accounts payable process steps
Here is the full cycle, step by step, with who normally owns each and what breaks when it is done badly.
| # | Step | Owner | What goes wrong here |
|---|---|---|---|
| 1 | Purchase order raised and issued | Requester and procurement | No PO at all, so nothing can be matched later and the invoice becomes an argument |
| 2 | Goods or services received and recorded | Receiving or project lead | Receipt never entered, so a correct invoice looks unmatched and stalls |
| 3 | Invoice received | AP inbox | Invoices arriving at ten different personal email addresses instead of one channel |
| 4 | Invoice captured and coded | AP clerk or capture software | Manual keying errors, wrong GL code, wrong entity, wrong currency |
| 5 | Matching against the PO and receipt | AP or the system | Tolerances set so tight that every freight charge becomes an exception |
| 6 | Approval routing | Budget holder | One named approver with no delegate, so leave equals a stalled invoice |
| 7 | Exception handling | AP and the buyer | Exceptions with no owner and no deadline, aging quietly in a queue |
| 8 | Payment scheduled and released | AP and treasury | Paying everything the day it arrives, or missing the discount window |
| 9 | Reconciliation and close | Accounting | Statements never reconciled, so duplicates and credits are found a year late |
The accounts payable process flow chart
A flow chart is more useful than the list above because it shows the decision points, which is where the time actually goes. In text form, the AP flow has three gates:
- Invoice arrives. Is there a purchase order referenced? If no, it goes down the non-PO path and needs a budget holder to confirm it was ordered at all. If yes, continue.
- Match gate. Do the invoice, the PO, and the receipt agree within tolerance? If yes, the invoice can be approved automatically under most policies. If no, it becomes an exception with a named owner and a clock.
- Approval gate. Is the amount within the approver's authority limit? If yes, approve and queue for payment. If no, escalate to the next threshold.
Draw those three diamonds and you have the flow chart most software is implementing. The value of drawing it for your own business is that it forces you to answer the questions teams usually leave undefined: what the tolerance actually is, who owns an exception, and what happens when the approver does not respond. If you want the approval branch in detail, including thresholds and delegation, it is a process in its own right: see the invoice approval workflow.
What is the three way match in accounts payable?
The three way match compares three documents before an invoice is paid: the purchase order (what you agreed to buy), the goods receipt (what actually arrived), and the invoice (what the vendor is billing you for). When all three agree within tolerance, the invoice is legitimate and can pay without a human deciding anything.
A two way match compares only the PO and the invoice. It is faster, and it is appropriate for services where there is nothing to physically receive, but it means you can pay in full for a delivery that arrived short. The choice between them is a risk decision, not a technical one.
The mistake most teams make is with tolerances. Set them to zero and a 4 dollar freight variance on a 9,000 dollar invoice creates a manual exception, a two day delay, and a phone call. Set them sensibly, usually a small percentage with a hard dollar cap, and you exception only the things worth a human's attention. The matching mechanics themselves, including how to handle partial deliveries and credits, are covered in the invoice reconciliation process.
Accounts payable benchmarks: what good looks like
The gap between an average AP function and a strong one is much larger than most finance leaders expect. Ardent Partners' 2025 State of ePayables research puts it in stark terms, and APQC maintains cross industry benchmarks on the same measures.
| Metric | Typical performer | Best in class |
|---|---|---|
| Fully loaded cost to process one invoice | About 10.89 dollars | About 2.78 dollars |
| Invoice cycle time (receipt to approval) | 17.4 days | 3.1 days |
| Invoice exception rate | 22 percent | 9 percent |
Read those three rows together and the story is obvious. The best performers are not paying faster because they work harder. They are paying faster because far fewer invoices become exceptions, and the exception is what costs the money. Every exception is a human touch, and human touches are where the 10.89 dollars goes.
Which means the highest leverage thing you can do to your AP process is not to speed up approvals. It is to stop creating exceptions: enforce purchase orders, get receipts recorded, set sane tolerances, and clean up vendor master data so invoices match the first time.
Accounts payable procedures and policies
The written policy is short and it should answer questions people actually argue about. At minimum:
- When a PO is required. A dollar threshold, plus the categories that always require one. Without this, the matching step has nothing to match against.
- Approval authority limits. Who can approve what amount, and what happens above it.
- Delegation. Every approver has a named backup. This one line removes a surprising share of your cycle time.
- Payment terms and runs. The default terms you offer, and the schedule of payment runs. Ad hoc payments are where duplicates and fraud live.
- Exception ownership. Who resolves a mismatch, and the deadline they have to do it.
The controls that stop payment fraud
Two controls prevent most of the losses in AP, and both are procedural rather than technical.
The first is segregation of duties. The person who can add or edit a vendor in the master file must not be the person who can release a payment. When one person can do both, they can create a vendor and pay it, and no system will stop them. In a small team where true separation is impossible, the compensating control is that a second person reviews every vendor master change against the payment run.
The second is out of band verification of bank detail changes. The most common serious loss in accounts payable is not an invented invoice, it is a real supplier whose bank details were changed by an attacker who emailed a convincing request. The rule that stops it: any change to vendor bank details is verified by calling the supplier back on the number you already had on file, never a number in the email requesting the change, and the verification is logged. Treat an urgent tone in such a request as a reason for more suspicion, not less. The same discipline belongs at the front of the relationship, when you first collect a supplier's banking and insurance paperwork during vendor onboarding.
How do you improve the accounts payable process?
In order of return, and none of the first three require you to buy anything:
- One inbox, one channel. Every invoice arrives at a single monitored address. Invoices in personal inboxes are invisible until they are late.
- Fix the vendor master. Duplicate vendor records are the root cause of duplicate payments and most matching failures.
- Set tolerances and delegates. Two policy lines that remove exceptions and stalls without any new software.
- Automate capture and matching. This is where the cost per invoice actually falls, because it removes the keying and the routine matching. The selection criteria are their own topic, covered in the guide to accounts payable automation software.
- Measure the right thing. Track exception rate and cycle time, not invoices processed per person. Volume per head rewards a team for touching more invoices, which is precisely the behavior you are trying to eliminate.
What is the difference between the AP process and the AP cycle?
Nothing meaningful. In practice the terms are used interchangeably for the same sequence, from invoice receipt through to payment and reconciliation. Some teams use "cycle" to emphasize that it repeats and closes each month, and "process" to describe the steps within it. If a distinction is being drawn in your organization, it is usually that the cycle includes the period close and the process stops at payment.
What are the main functions of accounts payable?
Four, and they map to the process above. Verifying that a liability is real and correct. Obtaining the right approval to settle it. Paying it accurately and on time, in line with agreed terms. Recording it so the books, the vendor statements, and the cash forecast all agree. Everything else an AP team does, from vendor queries to statement reconciliation, exists in service of those four.
How the AP process affects cash
A well run AP process gives finance a genuine choice about when to pay, because it knows what it owes and when. A badly run one does not, and it pays reactively, either too early (giving away cash for nothing) or too late (damaging supplier relationships and losing early payment discounts). The measure of how long you take to pay suppliers is days payable outstanding, and the goal is not to make it as high as possible. It is to pay exactly on terms, deliberately, every time.
The invoices themselves are the raw material for all of this, and the process of receiving, checking, and querying them well is worth treating as its own discipline: see vendor invoice management.