Quick Answer

An accounts payable process flow chart shows how a supplier invoice moves from purchase and receiving through capture, validation, matching, approval, payment, and reconciliation. A useful chart also shows the decision points, such as "Is it a duplicate?" and "Does it match?", and what happens when an invoice fails a check.

The Accounts Payable Process Flow Chart

Here is a complete AP process flow chart. The center column is the normal path, the left column shows who typically owns each step, and the right column shows exception paths.

Accounts payable process flow chart Accounts payable process flow chart from purchase order through goods receipt, supplier invoice receipt, capture and validation, a duplicate check, GL coding, two-way or three-way matching, a match decision with an exception review loop, approval with a rejection loop, payment scheduling, payment execution, reconciliation, and invoice closure with an audit trail. Each step lists its typical owner. TYPICAL OWNER PROCESS EXCEPTION PATH Purchase order createdand sent to supplier Procurement 1. Goods or services receivedReceiving report recorded Receiving / requester 2. Supplier invoice receivedEmail, portal, EDI, or mail AP 3. Invoice captured and validatedRequired fields and vendor checked AP Duplicateinvoice? No 4. GL codingAccount, cost center, project AP 5. Two-way or three-way matchPO vs receipt vs invoice AP Does itmatch? Yes 6. Routed for approvalBased on amount and approver limits Approver Approved? Yes 7. Payment scheduledBased on terms and due date AP / treasury 8. Payment executedACH, check, card, or wire Treasury / AP 9. AP and GL updated, reconciledMatched to bank and vendor records Accounting Invoice closedAudit trail retained Yes Reject duplicateNotify supplier; stop here No Exception reviewHold, investigate, correct No Returned or rejectedFix coding, data, or support Re-match Correct and resubmit Start / endProcess stepDecisionException path
Figure 1. Accounts payable process flow showing invoice receipt, validation, duplicate check, matching, exception review, approval, payment, and reconciliation. Owners are typical and vary by company.

What this flow chart covers

  • Purchase order and goods receipt
  • Supplier invoice receipt
  • Invoice capture and validation
  • Duplicate invoice check
  • GL coding
  • Two-way or three-way matching
  • Exception review and re-matching
  • Invoice approval and rejection
  • Payment scheduling
  • Payment execution
  • Reconciliation
  • Record keeping and audit trail

This chart starts at the purchase order. In a broader procure-to-pay process, the flow begins earlier with a purchase request and purchase approval. Not every company follows this exact path: some expenses, like utilities, don't use POs, some purchases only need two-way matching, and approval levels differ. Treat the chart as a common structure to adapt to your policies and controls.

What Is an Accounts Payable Process Flow Chart?

An AP process flow chart is a diagram that shows, step by step, how a business handles what it owes suppliers (vendors). It turns a process that often lives in people's heads, inboxes, and spreadsheets into a picture anyone can follow. You may also see it called an AP workflow diagram or AP process diagram.

Who uses one?

AP teams, accounting managers, controllers, finance leaders, procurement and operations teams, internal auditors, and companies documenting SOPs or rolling out AP software. Teams use it to train new staff, find where invoices get stuck, document internal controls for auditors, settle "who does what" questions, and spot manual steps worth automating.

For the full written explanation of each stage, see our accounts payable process guide. This page focuses on the visual flow.

Standard Flowchart Symbols Used in AP Diagrams

Flowchart shapes and what they mean
ShapeRepresentsAP example
Oval (terminator)Start or end"Purchase order created" or "Invoice closed"
RectangleA process step"GL coding"
ParallelogramInput or output of data or documents"Supplier invoice received"
DiamondA decision with two or more outcomes"Does it match?"
ArrowDirection of flowConnects one step to the next

Using standard shapes means anyone, from a new hire to an outside auditor, can read the chart without a legend.

The Accounts Payable Process Flow, Step by Step

  1. Purchase order createdProcurement issues a PO listing what's being bought, the price, quantity, and terms.
  2. Goods or services receivedReceiving or the requester confirms what arrived and records a receiving report (sometimes called a goods received note, or GRN).
  3. Supplier invoice receivedThe invoice arrives by email, supplier portal, EDI, or mail, ideally at one AP-controlled address.
  4. Invoice captured and validatedKey fields like supplier, invoice number, date, amount, and line items are entered or extracted, and checked for completeness.
  5. Duplicate checkThe invoice is compared with past invoices so the same bill isn't paid twice. Duplicates are rejected and the supplier is told.
  6. GL codingThe invoice is assigned to the right general ledger account, cost center, or project.
  7. Two-way or three-way matchThe invoice is compared with the PO, and with the receiving report when receipt matters.
  8. Exception reviewIf anything doesn't match, the invoice goes on hold until AP resolves it, then it's matched again.
  9. Invoice approvalThe invoice is routed to the right approver, often based on amount and approval limits. Rejected invoices go back for correction. Learn more about how approval fits inside the invoice workflow.
  10. Payment schedulingApproved invoices are scheduled based on terms (like Net 30) and any early-payment discounts.
  11. Payment executionTreasury or AP releases payment by ACH, check, card, or wire.
  12. Reconciliation and record keepingPayments are matched to bank and supplier records, AP and the general ledger are updated, and the full history is stored. See our accounts payable reconciliation guide.

What Happens When an Invoice Doesn't Match?

An invoice that fails a two-way or three-way match shouldn't move to payment. It's placed on hold while AP investigates. Common reasons include:

  • Quantity billed doesn't match quantity received
  • Price differs from the PO
  • Missing purchase order
  • Missing receiving report
  • Duplicate invoice
  • Wrong supplier details or remit-to address
  • Tax or math errors
  • Amount above the approver's limit
Mismatch flagged Invoice on hold Investigate with supplier or buyer Correct or approve variance Re-match Approval Payment

Matching exceptions are a common reason invoices are delayed, so give each exception type a clear owner and a target time to resolve it.

Two-Way, Three-Way, and Four-Way Matching Explained

Three-way match comparing purchase order, receiving report, and supplier invoice The purchase order shows what was ordered, the receiving report shows what arrived, and the supplier invoice shows what is billed. All three feed a match check. If they agree the invoice goes to approval; if not it goes to exception review. Purchase orderWhat you ordered Receiving reportWhat actually arrived Supplier invoiceWhat you're being billed Do quantity, price, and termsagree across all three? Yes: send for approval No: exception review
Figure 2. A three-way match compares the purchase order, receiving report, and supplier invoice before an invoice moves to approval.
Matching methods compared
Match typeWhat it comparesOften used for
Two-wayPO and invoicePurchases where a separate receiving record isn't needed, such as some services
Three-wayPO, receiving report, and invoiceGoods and purchases where confirming receipt matters
Four-wayPO, receipt, invoice, and inspection or acceptanceGoods that need a quality check before payment

No single method fits every purchase. Many companies set matching rules by purchase type, amount, or supplier, and allow small price or quantity tolerances before an invoice is flagged.

Example: One Invoice From Receipt to Payment

A company orders 100 units of inventory at $120 each. The supplier sends a $12,000 invoice.

Three-way match example
DocumentQuantityUnit priceTotal
Purchase order100$120$12,000
Receiving report100
Supplier invoice100$120$12,000

Normal path: all three agree, so the invoice is coded, routed to the department manager, approved, and scheduled for payment on Net 30 terms.

Exception path: if the invoice billed 110 units ($13,200) but only 100 arrived, the match fails. AP puts the invoice on hold and asks the supplier for a corrected invoice or credit memo for the extra 10 units before it moves to approval.

AP Process Flow vs Procure-to-Pay vs Invoice Approval Workflow

How these related flows differ
AP process flowProcure-to-pay (P2P)Invoice approval workflow
Starts atPO or invoice receiptPurchase requestInvoice ready for review
Ends atPayment and reconciliationPayment and reconciliationApproved or rejected
Main focusSupplier invoices and paymentsWhole purchasing cycleWho signs off, and when
Includes purchasing?PartlyYesNo

The approval workflow is one stage inside the AP flow, and the AP flow is one part of P2P. Our guide to the accounts payable workflow goes deeper on routing and approval mechanics.

Manual vs Automated AP Process Flow

The steps don't change. What changes is who or what does the work at each step.

Same steps, different handling
StepManual APAutomated AP
Invoice captureStaff type in invoice dataData can be captured and extracted electronically
Duplicate checkSomeone searches past invoicesLikely duplicates can be flagged by the system
MatchingDocuments compared by handMatching can be done by system rules
ApprovalInvoices forwarded by emailRouting can follow predefined rules, with notifications
Status trackingSpread across emails and filesTracked in one system
ExceptionsFound manually, often lateCan be flagged for review when they occur
Audit trailPieced together from emailRecorded automatically on each invoice

Key Controls to Include in an AP Process Flow

A flow chart is also a map of your controls. Make sure these show up on yours:

Controls and where they belong
ControlWhere it sits in the flow
Purchase approvalBefore the PO is issued
Supplier master controlsSupplier setup and changes, including bank details
Duplicate invoice checkRight after capture
Two-way or three-way matchingBefore approval
Approval limitsApproval step
Payment authorizationBefore payment release
Bank detail verificationBefore paying a new or changed account
Segregation of dutiesAcross setup, approval, payment, and reconciliation
Reconciliation and audit trailAfter payment

To test whether these controls are actually working, use our accounts payable audit checklist.

Common Bottlenecks an AP Flow Chart Can Reveal

  • Invoices in a shared inbox with no owner or deadline
  • Approvals stuck with one person who is traveling, out, or slow to respond
  • No PO on file, forcing back-and-forth to confirm the purchase
  • Duplicates slipping through because nobody checks invoice numbers
  • Unclear approval limits, so nobody knows who can approve what amount
  • Exceptions with no owner, leaving held invoices sitting for weeks

A quick tip: if one box on your chart has several arrows coming in and only one going out, that's usually where invoices pile up.

How to Create an Accounts Payable Process Flow Chart

  1. Pick the starting pointDecide whether your chart starts at the purchase request, PO creation, or invoice receipt.
  2. List every step as it happens todayMap the real process, not the policy manual. The gap between the two is often where problems live.
  3. Add decision pointsFor example: Is a PO required? Is it a duplicate? Does it match? Is approval needed? Is it approved?
  4. Map exception pathsShow where an invoice goes when it fails each check, and how it gets back on track.
  5. Assign ownersLabel each step with a role: AP, procurement, receiving, approver, treasury, or accounting.
  6. Add controlsMark approval limits, matching rules, duplicate checks, and payment authorization.
  7. Test it with real invoicesWalk one normal invoice and one problem invoice through the chart with the people who do the work.
  8. Review and updateRevisit it on a set schedule and whenever your process changes.

Any diagramming tool works, or you can download the chart above as a starting template.

Common Mistakes and When to Update Your Chart

Mistakes to avoid

  • Too much detail in one chart; keep each box to one action
  • Showing only the happy path, with no exception loops
  • Leaving off owners for each step
  • Mixing up AP with accounts receivable steps
  • Setting approval limits without finance leadership
  • Never updating it after it's drawn

Update the chart when you

  • Change accounting or ERP software
  • Change approval limits or levels
  • Add invoice channels or payment methods
  • Change matching rules or tolerances
  • Add automation
  • Change who owns a step

How Automation Changes the Accounts Payable Process Flow

Automation doesn't remove the stages in the chart. It can reduce manual handoffs by capturing invoice data, flagging duplicates, applying matching rules, routing approvals, and tracking status in one system. Modern AP systems may use OCR, AI-based document extraction, or other tools to capture invoice data, and people still review exceptions and make approval decisions. For more on the data-entry and checking steps, read about invoice processing in accounts payable.

For Salesforce teams, Quick Payable supports the middle of this flow inside Salesforce: invoices arrive by email or upload, AI OCR extracts the key fields, duplicates are flagged and rejected, approvals route to an assigned approver and escalate to their manager above that person's monetary limit, and every step is recorded on the invoice audit trail.

Ready to Improve Your AP Process?

See how Quick Payable captures invoices, routes approvals, and tracks AP activity inside Salesforce. Bring your flow chart to a short demo. 15-day free trial, no credit card required.

Conclusion

An accounts payable process flow chart gives finance, procurement, receiving, and approvers a shared view of how invoices move from purchase order to payment. The most useful charts show more than the normal path: they include matching decisions, approval requirements, exception handling, payment controls, reconciliation, and who owns each step. Start with the chart above, adapt it to how your team really works, and update it whenever your process changes.

Frequently Asked Questions

It is a diagram that shows each step a supplier invoice follows, from purchase order and receipt through capture, validation, matching, approval, payment, and reconciliation, including decision points and exception paths.

Common steps are purchase order, goods receipt, invoice receipt, capture and validation, duplicate check, GL coding, matching, exception review, approval, payment scheduling, payment execution, and reconciliation.

A three-way match compares the purchase order, the receiving report, and the supplier invoice. If quantity, price, and terms agree, the invoice moves to approval. If not, it goes to exception review.

The invoice is placed on hold while AP investigates the difference with the supplier or the buyer. Once it is corrected or the variance is approved, the invoice is matched again before moving to approval and payment.

The terms overlap. An AP process flow usually describes the full sequence of steps from purchase order to reconciliation, while an AP workflow often focuses on how work is routed between people and systems, especially approvals.

Pick a starting point, list each step as it really happens, add decision points and exception paths, assign an owner to each step, mark key controls, test it with real invoices, and review it whenever the process changes.

Many steps can be supported by software, including invoice capture, duplicate checks, matching, approval routing, and status tracking. The stages stay the same, and people still review exceptions and approve invoices.

Shyam Agarwal
Sr. Project Manager

Shyam Agarwal is a technology professional with 12+ years of experience in Salesforce consulting, development, and administration. He writes about accounts payable, AP automation, and Salesforce, drawing on his experience delivering scalable technology solutions that support business needs and improve operational efficiency.