The accounts payable process is the workflow a business uses to manage supplier invoices from purchase request through payment and recordkeeping. A typical AP process includes purchasing, receiving, invoice receipt, matching, approval, recording, payment scheduling, payment, and reconciliation with record retention.
What Is the Accounts Payable Process?
The accounts payable (AP) process is the set of steps a business follows to make sure every supplier invoice is real, accurate, approved, recorded, and paid on time. If you need the basics first, see our guide to what accounts payable is.
A good AP process has five goals:
- Pay only for what was ordered and received
- Get every invoice approved by the right person
- Pay suppliers on agreed terms
- Keep liabilities and the books accurate
- Reduce the risk of duplicate, wrong, or fraudulent payments
The same steps apply whether a business handles 100 invoices a month or 100,000. What changes with volume is how much of the work is done by hand.
AP Process vs AP Cycle vs Full-Cycle AP vs Procure-to-Pay
These terms overlap, and people often use them loosely. Here's how they usually differ:
| Term | What it usually covers |
|---|---|
| Accounts payable process | The steps AP takes to handle supplier invoices: receive, check, match, approve, record, pay, and reconcile |
| AP cycle | The repeating loop of those steps for every invoice, from receipt to closed and filed |
| Full-cycle AP | Managing every AP stage end to end, including vendor setup, reconciliation, and reporting. See our guide to full-cycle accounts payable. |
| Procure-to-pay (P2P) | The broader purchasing lifecycle, from requisition and purchasing through receiving, AP, and payment |
AP and P2P are related but not the same thing. AP is one part of P2P, focused on invoices and payments. P2P also includes deciding what to buy, choosing suppliers, and issuing purchase orders.
The 10 Steps of the Accounts Payable Process at a Glance
| Step | What happens | Key document or output |
|---|---|---|
| 1 | Purchase request | Purchase requisition |
| 2 | Purchase order created | Purchase order (PO) |
| 3 | Goods or services received | Receiving report |
| 4 | Supplier invoice received | Supplier invoice |
| 5 | Invoice checked and matched | Match result or exception |
| 6 | Invoice approved | Approval record |
| 7 | Invoice recorded | AP liability in the ledger |
| 8 | Payment scheduled | Payment schedule or run |
| 9 | Supplier paid | Payment record or remittance |
| 10 | Reconciled and archived | Reconciliation and audit record |
Want to see these steps as a diagram with decision points? Use our accounts payable process flow chart.
The Accounts Payable Process, Step by Step
1Purchase request
A department identifies a need, like office supplies, inventory, software, equipment, or professional services, and submits a purchase request. Many companies require a manager to approve it before anything is bought.
Usually owned by: the requesting department and its manager
2Create a purchase order
Procurement issues a PO to the supplier listing the items, quantities, prices, payment terms, and delivery details. The PO is the buyer's official order and becomes the reference point for checking the invoice later.
Usually owned by: procurement or purchasing
3Receive goods or services
When the order arrives, receiving or the requester checks quantity, condition, and delivery date, and notes anything damaged or missing. This is recorded on a receiving report (sometimes called a goods received note). For services, the requester confirms the work was done.
Usually owned by: receiving, warehouse, or the requester
4Receive the supplier invoice
The supplier sends an invoice with the invoice number, PO number, supplier details, amount, payment terms, and due date. Asking suppliers to send invoices to one AP email address or portal keeps invoices from getting lost.
Usually owned by: accounts payable
5Check and match the invoice
AP enters or captures the invoice data, checks it for a possible duplicate, codes it to the right GL account, and compares it with the PO and receiving report. If everything agrees, the invoice moves to approval. If not, it becomes an exception (see below).
Usually owned by: accounts payable
6Approve the invoice
The invoice is routed to the right approver based on the company's rules, often the amount and approval limits. Approvers confirm the purchase is valid and sign off, or send it back. Digital invoice approval software replaces email chains and keeps a record of every decision.
Usually owned by: budget owners, managers, or finance
7Record the invoice
The approved invoice is recorded in the accounting system or ERP, creating the liability until it's paid.
| Account | Debit | Credit |
|---|---|---|
| Expense or Inventory | $1,000 | |
| Accounts Payable | $1,000 |
In some companies the invoice is recorded when it arrives and approval happens afterward. Either way, it must be in the books for the right period.
Usually owned by: accounts payable or accounting
8Schedule the payment
Finance schedules payment based on terms like Net 15, Net 30, Net 45, or Net 60, and decides whether an early-payment discount (for example, 2/10 net 30) is worth taking. Many companies group payments into weekly or twice-monthly payment runs.
Usually owned by: AP and treasury
9Pay the supplier
Payment goes out by ACH, check, virtual card, wire, or another method, and the liability is cleared.
| Account | Debit | Credit |
|---|---|---|
| Accounts Payable | $1,000 | |
| Cash | $1,000 |
Usually owned by: treasury or AP, with a separate person authorizing release
10Reconcile and archive
Payments are matched to bank records and supplier statements, and AP balances are checked against the general ledger. Invoices, approvals, and payment records are stored for audits, tax reporting, and supplier questions, usually digitally.
Usually owned by: accounting
Documents Used in the Accounts Payable Process
| Document | Created by | What it proves |
|---|---|---|
| Purchase requisition | Requesting department | Someone needed the item and a manager agreed |
| Purchase order | Procurement | What was ordered, at what price and terms |
| Receiving report | Receiving or requester | What actually arrived, and in what condition |
| Supplier invoice | Supplier | What the supplier is billing and when it's due |
| Credit memo | Supplier | A reduction for returns, errors, or discounts |
| Payment record | AP or treasury | When, how, and how much was paid |
| Supplier statement | Supplier | What the supplier thinks you still owe |
Who Is Involved in the AP Process?
| Role | Main responsibility |
|---|---|
| Requesting department | Asks for the purchase and confirms services were received |
| Procurement | Chooses suppliers and issues purchase orders |
| Receiving | Checks deliveries and records receipts |
| Accounts payable | Captures, checks, matches, records, and tracks invoices |
| Approvers | Authorize invoices within their limits |
| Treasury or payments team | Schedules and releases payments |
| Accounting or controller | Reconciles balances, closes the books, and owns controls |
In small businesses, one or two people may cover several roles. That's when compensating controls, like an owner reviewing every payment run, matter most.
Two-Way vs Three-Way Matching
| Method | Compares | Commonly used for |
|---|---|---|
| Two-way match | PO and invoice | Services and purchases without a separate receiving step |
| Three-way match | PO, receiving report, and invoice | Physical goods, where confirming receipt matters |
Three-way match example
| Document | Quantity | Price | Total |
|---|---|---|---|
| Purchase order | 100 units | $10 | $1,000 |
| Receiving report | 100 units | ||
| Invoice | 100 units | $10 | $1,000 |
Result: match, ready for approval. If the invoice instead billed 100 units at $11 ($1,100), or only 90 units arrived, the match would fail and the invoice would go to exception review.
Not every purchase needs a PO. Utilities, rent, and some subscriptions are often approved directly against a contract or a budget instead.
What Happens When an Invoice Doesn't Match?
Common exceptions include:
- Price mismatch
- Quantity mismatch
- Missing PO
- Missing receiving report
- Duplicate invoice
- Wrong supplier or remit-to details
- Problem with the goods or services
- Disputed invoice
Give each exception type an owner and a target time to resolve it, so held invoices don't turn into late payments.
Accounts Payable Reconciliation
Reconciliation confirms that what your records say you owe matches reality. It ties together:
It catches missing invoices, duplicate payments, unapplied credits, and posting errors before they reach the financial statements. Most companies reconcile AP at every month-end. Our guide shows how to do accounts payable reconciliation step by step.
AP Controls and Fraud Prevention
| Control | What it prevents |
|---|---|
| Segregation of duties | One person creating a supplier, approving an invoice, and paying it |
| Approval limits | Large purchases approved by someone without authority |
| Supplier master controls | Fake suppliers and unauthorized changes |
| Bank detail verification | Payments redirected by a fake "new bank account" email |
| Duplicate invoice checks | Paying the same invoice twice |
| PO requirements | Paying for purchases nobody authorized |
| Payment authorization | Payments released without review |
| Audit trail | Not knowing who did what, and when |
Always confirm bank detail changes by calling the supplier at a number you already have on file. To test whether your controls are working, use our accounts payable audit checklist.
Example: One Purchase Through the Whole AP Process
If the invoice had billed for six laptops when five arrived, it would have stopped at day 10 until the supplier sent a corrected invoice.
Common Challenges in the AP Process
- Slow approvals that push invoices past their due dates
- Manual data entry that leads to typos and wrong amounts
- Duplicate invoices that arrive by both email and mail
- Lost invoices sitting in personal inboxes
- No visibility into where each invoice stands
- Weak controls that make fraud easier
- Delayed month-end close from missing or unrecorded invoices
When should a business improve its AP process?
Look closer when invoice volume is growing, approvals happen by email, invoices are hard to track, duplicates have slipped through, month-end close keeps running late, or your team spends much of its week entering data and chasing sign-offs.
Manual, Digital, and Automated AP Processes
| Manual | Digital | Automated | |
|---|---|---|---|
| Invoice intake | Paper and personal inboxes | Shared AP inbox, scanned PDFs | Captured and data extracted by software |
| Matching | By hand | By hand using spreadsheets | By system rules, with exceptions flagged |
| Approval | Paper sign-off | Rule-based routing with notifications | |
| Status | Ask around | Spreadsheet tracker | Visible on each invoice |
| Audit trail | Filing cabinets | Email threads | Recorded automatically |
The steps stay the same at every level. What changes is how much is done by hand. Automation tends to become useful when volume, approvers, or exceptions grow beyond what a spreadsheet can track. Learn how it works in our overview of accounts payable automation.
For companies that run on Salesforce, Quick Payable handles steps 4 through 9 inside Salesforce: invoices arrive by email or upload, AI OCR extracts the data, duplicates are flagged, approvals route by approver limit, and each invoice's status and audit trail stay on its record.
Best Practices for an Efficient AP Process
- Write down your process and approval rules, and keep them current
- Use purchase orders consistently for goods and large purchases
- Send all invoices to one AP inbox or portal
- Match invoices before approval, not after
- Give every exception an owner and a deadline
- Separate supplier setup, approval, and payment duties
- Verify every bank detail change by phone
- Reconcile AP and supplier statements every month
- Review the AP aging report before each payment run
- Track metrics like processing time and on-time payment rate
See How Quick Payable Runs the AP Process in Salesforce
Bring your current process and a few real invoices to a short demo. Try it free for 15 days, no credit card required.
Conclusion
The accounts payable process is how a business makes sure it pays the right supplier, the right amount, at the right time, and records it correctly. The core steps are the same everywhere: request, order, receive, invoice, match, approve, record, schedule, pay, and reconcile. What separates a strong process from a weak one is clear ownership, consistent matching, good exception handling, and controls that are actually followed.
Frequently Asked Questions
The accounts payable process is the workflow a business uses to manage supplier invoices from purchase request through payment and recordkeeping, including receiving, matching, approval, recording, payment, and reconciliation.
Purchase request, purchase order, receiving goods or services, receiving the invoice, checking and matching, approval, recording the invoice, scheduling payment, paying the supplier, and reconciling and archiving records.
Procure-to-pay covers the whole purchasing lifecycle, from requisition and purchasing through payment. Accounts payable is one part of P2P that focuses on supplier invoices, approvals, payments, and recording.
Full-cycle accounts payable means managing every AP stage end to end, including supplier setup, invoice receipt, verification, approval, payment, reconciliation, and reporting.
A three-way match compares the purchase order, the receiving report, and the supplier invoice. If quantities, prices, and terms agree, the invoice moves to approval. If not, it is held as an exception.
Common documents include the purchase requisition, purchase order, receiving report, supplier invoice, credit memo, payment record, and supplier statement.
The AP team runs most of it, but requesting departments, procurement, receiving, approvers, treasury, and accounting each own specific steps. A controller or finance leader usually owns the overall controls.
The invoice is put on hold while AP works with the supplier or buyer to resolve the difference, usually through a corrected invoice, a credit memo, or an approved variance. It is then matched again before approval.
Document the process, use purchase orders consistently, centralize invoice intake, match before approval, assign owners to exceptions, separate duties, verify bank changes, reconcile monthly, and track key metrics.
Automation tends to make sense when invoice volume is growing, approvals depend on email, invoices are hard to track, duplicates occur, or the team spends significant time on data entry and follow-ups.
By