An accounts payable workflow is the structured path a supplier invoice follows from receipt to approval, payment, recording, and filing. A good workflow spells out what happens at each step, who owns it, what gets checked, and what happens when something doesn't match. Not every invoice takes the same path: PO invoices, non-PO invoices, and invoices with problems each need their own route.
What Is an Accounts Payable Workflow?
An AP workflow is the set of steps and rules that move each supplier invoice through your business. It answers four questions for every invoice:
- What's next? The next step after this one.
- Who does it? The person or role responsible.
- What gets checked? The controls an invoice must pass.
- What if it fails? Where it goes and who fixes it.
Without a clear workflow, invoices get lost in inboxes, approvals stall, duplicates slip through, and nobody can say quickly where a bill stands. If you're new to the basics, start with our guide to accounts payable.
AP Workflow vs AP Process
The terms overlap, but they answer different questions. The process is the big picture; the workflow is how the work actually moves.
| AP process | AP workflow | |
|---|---|---|
| Scope | The whole AP function | The path each invoice follows |
| Starts | Can start with purchasing | Usually starts when the invoice arrives |
| Focus | What AP does overall | Routing, handoffs, approvals, and exceptions |
| Question it answers | "What is our AP function?" | "Where does this invoice go next, and who handles it?" |
For the broader lifecycle, see the accounts payable process guide.
The 11 Steps of an Accounts Payable Workflow
1Receive the invoice
Invoices arrive by email, supplier portal, e-invoicing, EDI, mail, or upload. The goal is one controlled entry point, not personal inboxes and desk piles.
Usually owned by: AP team
2Capture invoice data
Pull out vendor, invoice number, dates, PO number, line items, tax, total, and terms, either by hand or with OCR and AI. Deeper detail is in invoice processing in accounts payable.
Usually owned by: AP team or capture software
3Validate the invoice
Check the vendor is real and active, the totals and tax add up, required fields are there, and it isn't a duplicate. Catching problems here is cheaper than catching them after approval.
Usually owned by: AP team
4Code the invoice
Assign the GL account and any department, cost center, project, location, or entity. Recurring vendors often get default codes to save time.
Usually owned by: AP team, confirmed by the budget owner
5Match to supporting documents
For PO invoices, a two-way match compares the invoice to the PO. A three-way match adds the receiving record. Not every invoice needs matching: services, utilities, and recurring bills often follow other controls.
Usually owned by: AP team, with purchasing and receiving
6Route for approval
The invoice goes to whoever has authority for that amount or spend. Escalation rules send it higher when it's over someone's limit. See how routing works below.
Usually owned by: approvers and budget owners
7Handle exceptions
Invoices that fail a check leave the normal path with a reason, an owner, and a next action. This step is where most delays happen, so it gets its own section.
Usually owned by: AP team, with whoever can fix the cause
8Authorize payment
Approved invoices are scheduled based on due date, terms, cash, and any early-payment discount. Many companies keep payment authorization separate from invoice approval as a control.
Usually owned by: AP manager or controller
9Process the payment
Pay by ACH, wire, check, virtual card, or another approved method, and link the payment back to the invoice so its status shows "paid."
Usually owned by: treasury or finance, separate from vendor setup
10Record and reconcile
Post to the accounting system, then tie open invoices, vendor balances, and the AP control account together. Our guide to accounts payable reconciliation walks through it.
Usually owned by: accounting
11Archive with an audit trail
Keep the invoice, PO, receipt, coding, approval history, exception notes, and payment confirmation together. That's what auditors ask for first.
Usually owned by: AP team
The Three Paths an Invoice Can Take
Real workflows aren't a straight line. Most invoices follow one of three paths, and a good workflow defines each one before invoices start moving:
For a full printable chart with decision points and owners, see our accounts payable process flow chart.
How Approval Routing Works
Approval routing decides who signs off on each invoice. Companies build routing rules from factors like:
| Factor | Example rule |
|---|---|
| Amount | Above an approver's limit, escalate to their manager |
| Department or cost center | Send to the budget owner for that department |
| Vendor | New vendors need an extra review |
| Project or entity | Route to the project or entity lead |
| Invoice type | Non-PO invoices need budget-owner approval |
The simplest and most common model is an approval limit with escalation: each approver can sign off up to a set amount, and anything larger moves up to their manager.
Approval limits vary widely by company, so set them from your own policy and risk tolerance rather than a generic table. Add a backup approver for every person, plus reminders, so invoices don't wait when someone is out. Rule-based invoice approval software applies those rules automatically.
Exception Handling: The Step That Makes or Breaks a Workflow
A workflow that only works when everything matches isn't really a workflow. For each exception type, decide who owns it and what they do:
| Exception | Usual owner | Typical fix |
|---|---|---|
| Missing PO | Requester or purchasing | Create the PO or route under the non-PO policy |
| Price mismatch | Purchasing | Confirm the agreed price; request a corrected invoice or credit |
| Quantity mismatch | Receiving | Confirm what arrived; pay what was received |
| Missing receipt | Receiving | Record the receipt, then re-match |
| Possible duplicate | AP | Compare to the existing record; reject if it's a true duplicate |
| Wrong tax or missing coding | AP or budget owner | Correct the invoice or coding |
| Unknown vendor | Vendor master owner | Verify and set up the vendor before anything is paid |
Give each exception type a deadline too. Otherwise the exception queue simply becomes the new overflowing inbox.
Who Owns Each Step
Workflows break at handoffs. Writing down who does what, and keeping key duties separate, prevents both delays and fraud.
| Role | Main responsibilities |
|---|---|
| AP specialist | Intake, capture, validation, coding, exceptions, filing |
| Approver or budget owner | Confirms the spend is valid and within budget |
| Purchasing | Issues POs, resolves price questions |
| Receiving | Records what actually arrived |
| AP manager or controller | Authorizes payment runs, owns policy and controls |
| Treasury or finance | Releases payments |
| Accounting | Posting, reconciliation, month-end close |
Key separation: the person who sets up or changes a vendor's bank details shouldn't be the one who approves that vendor's invoices or releases payment.
Manual vs Automated AP Workflow
The steps stay the same. What changes is how the work gets done:
| Step | Manual | Automated |
|---|---|---|
| Intake | Scattered inboxes and paper | One queue for every invoice |
| Capture | Typed by hand | Extracted by OCR or AI, reviewed by a person |
| Duplicate checks | Someone remembers, or doesn't | Flagged automatically |
| Approval | Email chains and follow-ups | Routed by rule with notifications |
| Exceptions | Sit in inboxes | Flagged with a reason and owner |
| Status | "Let me check" emails | Visible in the system |
| Records | Spread across systems | Invoice and approval history kept together |
Automation doesn't remove judgment. People still review exceptions, approve spend, and make payment decisions.
Common AP Workflow Problems
| Problem | Usual cause |
|---|---|
| Invoices go missing | Too many intake channels |
| Approvals stall | No deadline, backup approver, or escalation |
| Data-entry errors | Retyping every field |
| Matching delays | Late POs, unrecorded receipts, no exception owner |
| "Where's my payment?" calls | Status hidden in email threads |
| Slow audits | Invoice, approval, and payment records stored separately |
How to Improve an Accounts Payable Workflow
Start by mapping how invoices move today. For each step, ask:
- What happens here?
- Who owns it?
- What information is needed?
- What usually causes delays?
- What happens when something fails?
- Which system holds the record?
- What approval is required?
- How do we know it's done?
Then fix the biggest gaps first:
- One intake channel, such as a dedicated AP email or portal
- Written approval rules with backups and deadlines
- Automated capture instead of retyping every field
- Defined exception paths with owners
- Connected records so invoice, approvals, and payment live together
- Regular KPI reviews to find where invoices wait
A good test: could a new AP hire follow the workflow without asking one specific person what happens next?
AP Workflow KPIs to Track
| KPI | What it tells you |
|---|---|
| Invoice cycle time | How long invoices take from receipt to approval or payment |
| Approval time | How long invoices wait for sign-off, and with whom |
| Exception rate | Share of invoices needing manual work, by reason |
| First-pass match rate | Share of PO invoices that match on the first try |
| Duplicate rate | How often duplicates are caught or paid |
| Invoices near due date, unapproved | Early warning for late payments |
| Cost per invoice | What the whole workflow costs per bill |
Formulas and examples for each are in our guide to accounts payable metrics.
Where AP Automation Fits Into the Workflow
| Good fit for automation | Still needs people |
|---|---|
| Invoice intake and capture | Resolving disputes with vendors |
| Duplicate and field checks | Deciding if a price difference is acceptable |
| Routing and reminders | Approving spend |
| Status tracking and reporting | Payment timing and cash decisions |
| Keeping records together | Verifying new vendors and bank changes |
The goal isn't to automate every step; it's to make the workflow consistent while people stay in charge of judgment calls. Learn more about AP workflow automation.
Running the AP Workflow in Salesforce With Quick Payable
Quick Payable runs AP natively in Salesforce. Here's how its workflow maps to the steps above, based on the Quick Payable workflow documentation:
| Workflow step | How Quick Payable handles it |
|---|---|
| Intake and capture | Email or upload, with AI OCR extracting invoice data; vendors can also submit through a vendor portal |
| Validation | Highlights fields where extracted data doesn't match the PDF so someone can correct them |
| Duplicates | Detected duplicates are marked Rejected instead of being routed |
| Approval routing | Each user has an assigned monetary limit and manager; invoices above the limit escalate up the manager chain |
| Notifications and status | Approvers are notified and can act from any device; staff track status in list views and the AP dashboard |
| Reporting | Standard Salesforce reports such as approval cycle time and payment status |
To be specific about limits: Quick Payable routes by monetary limit and manager chain only. It doesn't currently route by vendor, department, cost center, or project. If your workflow depends on those rules, raise them in a demo.
See an AP Workflow Run Inside Salesforce
Bring your approval limits and a few real invoices to a short demo. 15-day free trial, no credit card required.
Conclusion
An accounts payable workflow defines how each supplier invoice moves from receipt through validation, coding, matching, approval, payment, reconciliation, and filing. The strongest workflows don't just pass invoices from person to person. They define owners, routing rules, exception paths, and records. Start by mapping what you do today, find where invoices wait, then standardize or automate those steps.
Frequently Asked Questions
An accounts payable workflow is the structured path a supplier invoice follows from receipt through validation, coding, approval, payment, reconciliation, and recordkeeping, including who owns each step and what happens when a check fails.
Invoice receipt, data capture, validation, coding, matching, approval, exception handling, payment authorization, payment, recording and reconciliation, and archiving.
The AP process is the broader accounts payable function. The AP workflow is how each invoice moves through specific steps, approvals, controls, and exceptions.
A two-way match compares the invoice to the purchase order. A three-way match also compares the receiving record, confirming the goods or services were actually received before payment.
No. Three-way matching is common for PO-based purchases of goods. Services, utilities, recurring charges, and non-PO invoices often follow different controls, such as budget-owner approval.
Yes. Non-PO invoices usually follow a separate path with extra coding and approval checks, because there is no purchase order to match against.
Each approver can sign off on invoices up to a set amount. Invoices above that amount escalate to the next level, often the approver's manager. The limits themselves are set by company policy.
Manual data entry, stalled approvals, unclear ownership, duplicate invoices, matching exceptions without an owner, scattered records, and poor visibility into invoice status.
Invoice cycle time, approval time, exception rate, first-pass match rate, duplicate rate, unapproved invoices near their due date, and cost per invoice.
Software can handle intake, data capture, duplicate and field checks, approval routing and reminders, status tracking, reporting, and recordkeeping, while people handle exceptions, approvals, and payment decisions.
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.