The accounts payable process covers supplier onboarding, intake, capture, coding, matching, exception routing, approval, posting, payment, and reconciliation. Each stage has an owner. Invoices rarely fail inside a stage, and they fail in the gap between two stages, where one role finishes and another picks up without everything it needs.
Key takeaways
- Most maps describe stages accurately and stop there. The missing sentence names who hands what to whom, and what the receiving role is entitled to expect.
- Very little of an average 8.2-day cycle involves work on the invoice. Most is waiting at a seam.
- Pass evidence rather than a status. An exception labelled price variance is a status. Attach the PO line, the contract rate, and the receipt quantity, and the next person settles it in one pass.
- Rank seams by rework rather than volume. A handoff failing on 4 percent of invoices and sending each back through two roles costs more than a noisy one that resolves in place.
The process is also a loop rather than a line, since most corrections end as a vendor master fix.
The stages are documented, the seams are not
Open any accounts payable (AP) standard operating procedure (SOP) and you will find intake, capture, coding, matching, approval, posting, and payment, each with a paragraph. What you will not find is a sentence naming who hands what to whom. That omission is where cycle time is lost.
Ardent Partners published its State of ePayables 2025 benchmarks in January 2026, reporting 2025 data. The average invoice takes 8.2 days from receipt to approval, costs $9.84 to process, and is one of a population with an 18.4 percent average exception rate. Most of those 8.2 days is waiting at a seam, for a goods receipt to post, for an approver to interpret a variance, or for a call on which vendor record is right.
Seam failures share a signature. The work gets redone. Route an exception without its evidence and the next person opens the document and restarts the investigation. Make a coding decision before the cost center owner is confirmed and it gets reversed after approval. Each repeat adds a supplier email, and Ardent found AP staff spend 21.9 percent of their time on inquiries.
How to read your own accounts payable process
Take your process map and work the arrows rather than the boxes. For each one, name the role that owns the upstream stage. Then name the artifact that crosses the seam, with its evidence attached, and the condition that lets the downstream role act without asking a question.
Then ask who owns the arrow itself. Usually nobody does, which is why seam failures survive improvement projects. Stages get owners because stages appear on org charts.
Two rules make the exercise useful. First, name a person's role rather than a department, because a line reading finance owns it resolves to nobody at eight in the morning. Second, require the upstream role to pass evidence rather than a status.
Rank the seams by rework rather than volume, and redesign the worst one first.
The accounts payable process lifecycle, stage by stage
Supplier onboarding and vendor master setup. Procurement or a vendor master steward owns this stage. The record gets created under the trading name while the supplier invoices under its registered legal entity, so nothing matches on arrival. Bank details arrive on an emailed form and get keyed without a callback. The Association for Financial Professionals surveyed 465 treasury practitioners in January 2026 and found 76 percent of US organizations hit by payments fraud in 2025, 74 percent of them through business email compromise (BEC).
Invoice intake. The AP shared mailbox team owns this stage. One email carries four attachments, one a statement and one last month's invoice resent, and the same supplier also submits through the portal. Nothing stamps a reliable arrival time, so cycle time measurement starts at the wrong moment.
Capture and extraction. The capture engine owns this stage, with an AP processor reviewing low-confidence fields. The extracted supplier string matches two vendor records and the processor picks one under time pressure. The capture engine misses line detail on a multi-page invoice, so the processor codes from a header total.
General ledger coding. AP owns this stage for purchase order (PO) backed invoices, and the budget owner owns it for everything else. AP codes the invoice to a cost center whose owner left months ago, or tax gets applied at header level on an invoice with mixed treatment. Non-PO-backed coding is the harder half, and automating GL codes for those invoices is where most manual effort is spent.
Matching. AP owns this stage, with receiving and the requisitioner as dependencies. The PO exists and the goods receipt does not, because the warehouse posts receipts weekly. AP reads a match failure as a supplier problem when the cause is internal timing.
Exception routing. An AP exception analyst owns this stage. The analyst passes the exception forward with a reason code and no evidence, so the receiving role rebuilds the case from scratch. Classifying exceptions well changes this more than any routing rule, and our AP invoice processing taxonomy sets out how.
Approval. The budget holder owns this stage under the delegation of authority matrix. The approver receives a price variance they have no authority to settle, and approves it anyway to clear a queue. Or the approver signs version one while coding changed afterward.
Posting to the enterprise resource planning system. An AP supervisor or systems accountant owns this stage. The posting date falls into a closed period, the entry posts in the next month, and accruals quietly break. Payment terms default because the vendor record has none.
Payment. Treasury owns this stage. The remit-to on the invoice differs from the bank record and nobody re-verified it before the run. That same AFP survey found 58 percent of organizations reporting that checks are subject to fraud, and 72 percent of organizations using checks plan to continue, with 68 percent citing vendor requirements.
Reconciliation and supplier inquiry. AP owns this stage alongside the general ledger accountant. The supplier statement shows open items your enterprise resource planning (ERP) system shows as paid, because of short-pays, credit memos, and payments applied to the wrong record. The Washington State Auditor put duplicate payments at 0.8 percent to 2 percent of total payments in 2022 research. Most corrections end as a vendor master fix, returning you to stage one.
Where the two paths diverge
PO-backed and non-PO-backed invoices run identically through intake and capture, then split at coding.
A PO-backed invoice inherits coding from the purchase order and approval from the requisition that was already authorized. Matching is deterministic, because invoice, PO, and goods receipt exist as independent records. The exception population is narrow, mostly quantity, price, and timing.
A non-PO-backed invoice has no upstream commitment to inherit. Someone assigns a GL account and cost center, and someone with budget authority approves it. No goods receipt exists for services, so three-way matching cannot apply. Contract terms, rate cards, and the supplier's billing history become the reference points instead. Route both populations through one queue and the non-PO half sets the wait time for everything.
What a better accounts payable process does not fix
A clean process still reads dirty data at the same speed, producing wrong answers faster. Duplicate vendor records, missing tax identification numbers, and stale bank details survive any redesign, so fix the master file first.
Redesign does not change supplier behavior either. A supplier who sends a file with no PO number keeps doing so until someone runs an enablement program. Ardent found that 57.4 percent of suppliers submit invoices electronically on average in its 2025 data.
It does not add capacity for peak volume either. Month-end concentrates arrivals, and a well-drawn process with the same headcount still builds a backlog. No SOP repairs a delegation of authority matrix the business never agreed to, and ambiguous authority shows up as approvals nobody wanted to give.
Where current approaches fall short
Most improvement projects renovate stages. They add a routing rule, a new queue, a tighter tolerance, and leave the seams as they were, so the same invoice waits somewhere else. Centralization gets treated the same way, as a move of desks rather than a redistribution of ownership. Consolidate four regional teams into one shared service without naming who owns each handoff and you produce the original process at larger scale.
The supplier inquiry load rarely appears on the process map at all, even though it consumes more than a fifth of staff time. Status emails, remittance requests, statement copies, and bank change notices arrive in a mailbox outside every system the team measures. Because that work is invisible on the map, it never gets an owner, and whoever has capacity that morning does it.
How we approach the accounts payable process
We work the seams. Our AI reads the invoice and resolves the supplier against your vendor master rather than assuming one clean record exists. It predicts GL coding for non-PO-backed invoices from vendor and cost center history, runs multi-line PO matching, and posts to the ERP with evidence attached to each decision. A person receives an exception with the PO line, the receipt, and the supplier's billing history already assembled, so they settle it in one pass.
The supplier mailbox runs on the same platform through AP Inbox Service Center. There the Duplicate Invoice Gatekeeper, Bank Change Verification Guardian, Payment Status Responder, and other Agents process intake and answer supplier inquiries directly. Customers see a 60 percent reduction in email processing time, and Georgetown University reached a 74 percent reduction. More sits on our AI-powered accounts payable page.
The bottom line
Redraw your process map around the arrows instead of the boxes, name a role on each, and define the evidence that has to travel with the invoice. That one change removes more rework than any new routing rule.
Frequently asked questions
What are the stages of the accounts payable process?
The stages are supplier onboarding and vendor master setup, invoice intake, capture and extraction, GL coding, matching, exception routing, approval, posting to the ERP, payment, and reconciliation. Coding and matching behave differently for PO-backed and non-PO-backed invoices, so the two populations need separate handling.
Who owns the accounts payable process?
Ownership is shared, and that is the difficulty. Procurement or a vendor master steward owns supplier records, AP owns intake through posting, budget holders own approval, and treasury owns payment. Name a role for each handoff between them, because seams without an owner are where invoices sit.
How long should invoice processing take?
Ardent Partners reported an average cycle time of 8.2 days for 2025, with a $9.84 average processing cost. Its top-performing tier runs 79 percent faster. Most elapsed time is waiting rather than working.
Why do duplicate payments still happen with a documented process?
Duplicates enter across seams rather than inside stages. The same invoice arrives by email and through a portal, or under two vendor records for one supplier. Software has to check every channel and record at once, which a stage-level control cannot do.