The accounts payable process is the eight-step cycle a supplier invoice moves through between arriving at your company and being paid and recorded: purchase authorization, receipt of goods or services, invoice capture, verification and matching, GL coding, approval, posting to the ledger, and payment. Every control failure in AP happens because one of those eight steps was skipped or done by the wrong person.
Most finance teams have never written the process down. It exists as habit: Dana opens the AP inbox, Dana keys the invoice, Dana asks the department head if it looks right, Dana pays it. That works until Dana takes two weeks off, or until an auditor asks who authorized a $60,000 payment and the answer is a forwarded email. Writing it down is the cheap part. This is what to write.
What is the accounts payable process?
The accounts payable process is how a business receives, verifies, approves, records and pays what it owes to suppliers. It starts before the invoice exists, at the point somebody commits the company to spending money, and it ends when the payment clears and the entry sits correctly in the general ledger. AP is a control function first and a payment function second.
The word "process" matters more than it looks. Accounts payable is not a queue of invoices, it is a chain of custody for money leaving the business. Each step exists because a specific thing can go wrong at that point, and each step should have a named owner who is not the same person as the owner of the step before it.
What are the steps in the accounts payable process?
There are eight, in this order. The first two happen before AP sees anything, which is exactly why AP teams that only start at step three end up arguing about invoices they cannot verify.
| Step | What happens | Who should own it | What goes wrong without it |
|---|---|---|---|
| 1. Authorize the spend | Someone with budget authority commits to the purchase, ideally against a written threshold | Budget owner | Invoices arrive that nobody agreed to, and AP becomes the department that says no after the money is spent |
| 2. Receive the goods or service | The requester confirms what actually arrived, in what quantity, and in what condition | Requester or warehouse | You pay for 100 units when 80 arrived, and nobody can prove it either way six weeks later |
| 3. Capture the invoice | The supplier bill is collected from email, mail, a portal or an exchange network into one place | AP | Invoices sit in personal inboxes, age past terms, and the first anyone hears is a dunning notice |
| 4. Verify and match | Vendor, invoice number, amount, tax and line items are checked, and matched to the order and receipt where those exist | AP | Duplicate payments, price creep the supplier never announced, and lines nobody ordered |
| 5. Code to the general ledger | The invoice is assigned an account, and split across departments, projects or entities where needed | AP, reviewed by accounting | A quarter of spend lands in one catch-all account and the P&L stops telling you anything |
| 6. Approve | The person who owns that budget signs off, at the threshold your policy sets | Budget owner, not AP | Approval by forwarded email, no audit trail, and the same person requesting and approving |
| 7. Post to the ledger | The approved liability is recorded in the correct period with the document attached | Accounting | Expenses land in the wrong month and the close turns into an accrual argument |
| 8. Pay and reconcile | Payment is released on terms, then matched back against the bank statement | Treasury or controller | Early payments that cost you float, late payments that cost you discounts, unreconciled cash |
Steps 4 and 5 are where nearly all the manual hours go, and they are the two steps invoice processing software removes most completely, because extraction and coding are pattern work a machine does better than a tired person at 6pm on the last day of the month.
What does the accounts payable process flow look like end to end?
End to end, the flow is: commitment, delivery, document, check, classify, authorize, record, pay. Drawn as a flow chart it has three decision diamonds, and those three are the entire control design. Everything else is movement.
- Does this invoice match what we ordered and received? If no, it goes to exception handling, not to approval. An exception queue that nobody owns is how a disputed invoice quietly becomes a paid one.
- Is it within policy and within this approver's limit? If no, it escalates one level. Thresholds should be written as dollar amounts, not as job titles, because titles change and dollar amounts do not need an org chart to interpret.
- Have we already paid this? Checked against invoice number, vendor and amount together, because the same bill arriving once by email and once by mail will have identical amounts and slightly different metadata.
The most common design flaw in an AP flow chart is putting approval before verification. If the approver is the first person to look hard at the invoice, you have made a budget owner do AP's job, and they will do it badly because it is not their job. Verify, code, then approve.
What are accounts payable policies and procedures?
Accounts payable policies set the rules; procedures describe the steps that enforce them. A workable AP policy fits on two pages and answers six questions: who can commit the company to spend, at what dollar thresholds, what documentation is required, who approves what, how exceptions are handled, and how quickly invoices must be processed.
Write the thresholds as a table, not as prose. A reader should be able to find "$10,000" and know in one line who signs. And put the segregation rule in writing: the person who sets up a vendor should not be the person who approves payments to that vendor, and neither should be the person who releases the payment. Three roles, three people. In a small team where three people do not exist, compensate with a review: the owner or controller reviews the vendor master change log monthly. That is the control an auditor will accept when segregation genuinely is not possible.
What are the controls in the accounts payable process?
Five controls carry most of the weight, and they are cheap to run once the process is written down.
| Control | What it prevents | How to run it |
|---|---|---|
| Vendor master maintenance | Fictitious vendors and payments redirected to a changed bank account | Two-person approval on new vendors and on any bank detail change, plus callback to a number you already had on file, never a number from the request email |
| Matching to order and receipt | Paying for goods never delivered, or at a price nobody agreed | Full three-way matching where purchase orders exist, two-way where they do not |
| Duplicate detection | The same invoice paid twice through two channels | Automatic check on vendor plus invoice number plus amount, run at capture rather than at payment |
| Approval thresholds | Spend authorized by someone who does not own the budget | Dollar-based limits enforced by the system, with the approval recorded against the document |
| Payment release segregation | One person originating and releasing the same payment | Separate the AP clerk who prepares the run from the person who releases it at the bank |
Vendor master maintenance deserves the top row. Business email compromise targeting AP works by changing bank details on a real supplier, which defeats matching, defeats approval thresholds and defeats duplicate detection, because everything about the invoice is genuine except where the money goes.
What are accounts payable process best practices?
The practices that actually change the numbers are unglamorous. Route every supplier invoice to one dedicated address so nothing arrives in a personal inbox. Set payment terms deliberately and pay on them rather than early. Prune the chart of accounts until every account has a one-sentence definition somebody can apply, because GL coding accuracy is capped by how well the accounts are defined. Give the exception queue a named owner and a service level. Reconcile the vendor master quarterly and close the vendors nobody has used in a year.
One more, less obvious: measure the approval delay separately from the processing delay. Teams instinctively attack data entry because it feels like the work, but the calendar time almost always sits in step 6, waiting on a person. Automating capture on a process where approvals take nine days moves the cycle time by hours.
What should be on an accounts payable process checklist?
A weekly AP checklist that covers the real risk looks like this: every invoice in the inbox captured and none older than the service level, exception queue cleared or escalated, duplicate flags reviewed, vendor master changes since last week reviewed against the callback log, approvals older than five days chased, invoices coded and ready for posting, the payment run prepared by one person and released by another, and the bank reconciliation matched against posted liabilities.
At month end, add three: accrue for goods received but not invoiced, confirm nothing has been posted to the wrong period, and review the catch-all GL account for anything that should have been split. That last one takes ten minutes and is the single fastest way to find out whether your coding is working.
How do you document the accounts payable process?
Write it as a table of the eight steps with a named owner, a required document and a time limit for each, then a separate one-page threshold table. That is enough. Documentation fails when it becomes a 40-page narrative nobody opens, and it fails again when the answer to a question lives in a shared drive and an approver has to hunt for the contract that governs an invoice, which is when teams start reaching for a way to search across every internal system at once rather than opening six of them by hand.
Keep the documentation next to the work, not in a policy binder. If your AP system holds the thresholds and routes accordingly, the system is the documentation and the written version exists for auditors and new hires.
What is accounts payable process automation?
Accounts payable process automation means software performing steps 3 through 7 of the cycle: capturing the invoice from email or a portal, extracting vendor, invoice number, date, amount, tax and line items with invoice OCR software, matching against the order and receipt, proposing a GL code, routing the approval by dollar threshold, and posting the approved record to the ledger. Steps 1, 2 and 8 stay human and stay yours.
AP automation is one layer of a wider stack, and it helps to see where it sits among the other jobs accounting automation software is sold to cover. The part worth being precise about is that AP automation software does not decide your policy, it enforces the policy you wrote. Buying it before writing the thresholds down produces a system configured by whoever set it up, which is rarely the person accountable for the spend. Write the two tables above first. Configuration then takes an afternoon.
The market splits on whether the tool also moves the money. Some products process the invoice and hand a clean record to your ledger, leaving payment on the bank or card program you already run. Others hold payment licenses and charge a per payment fee underneath the seat price, so a plan that reads as $15 per user carries $0.59 an ACH and $1.99 a check on top. The published entry prices across the main vendors are laid out in our comparison of AP automation solutions, read and dated at source.
What is the accounts payable process cycle time?
Cycle time is the elapsed time from invoice receipt to payment authorization, and it is worth splitting into two numbers because they have different fixes. Touch time is how long the work takes: capture, coding, matching. Wait time is how long the invoice sits doing nothing, which is almost entirely approvals and exception handling.
Measure both for one month before buying anything. If touch time dominates, invoice capture and automated GL coding will pay for themselves quickly. If wait time dominates, the fix is approval thresholds that stop routing $200 invoices to a VP, plus automatic chasing. Most teams find wait time is four to five times touch time and are surprised, because touch time is the part they can see.
How is the accounts payable process different in SAP, NetSuite or QuickBooks?
The eight steps do not change. What changes is how much of steps 3 to 5 the system does for you. QuickBooks Online captures bills and reads date, vendor and total from a receipt, but does not read invoice line items, code by judgment, or run a multi-step approval chain. NetSuite includes purchase orders, three-way matching and approval routing inside the ERP, and leaves capture and coding as the least automated part. SAP has the full apparatus and the configuration burden that comes with it.
In all three, the common pattern is a dedicated capture and coding layer in front of the ledger, syncing the finished, approved record back. That keeps the system of record where your accountants want it and puts the pattern work where software is better than people.
Where to start if the process is currently in someone's head
Spend two hours writing the eight-step table with names in the owner column, and the threshold table with dollar amounts. Route every supplier invoice to one address. Then look at where the time goes for a month. That sequence costs almost nothing, survives Dana taking a holiday, and turns any later software decision into a configuration exercise rather than a guess.
Expenditure handles steps 3 through 7 on the invoices and card charges you already receive: it reads each document including the line items, proposes the GL code, checks it against your policy, routes the approval to whoever owns that budget, and posts the approved record to QuickBooks, Xero or NetSuite. It works with the cards and banks you already have, never moves or holds your money, and never sells or trains on your financial data. It is software and insight, not financial, tax or accounting advice, so keep your accountant in the loop on how the accounts are defined.
If you have reached the point of shortlisting tools, the five architectures this category actually splits into, and what each one publishes as a price, are laid out in accounts payable software.