Accounts Payable Process: Steps, Best Practices & Automation

The accounts payable process is the end-to-end workflow that turns a supplier invoice into a paid liability. It runs from invoice receipt through data capture, matching, approval routing, payment, and reconciliation back to the general ledger. The way you run it shapes how much cash, time, and audit risk your finance team carries.

The economics are stark. Top-performing AP teams process invoices at $2.78 each in 3.1 days with a 49.2% touchless processing rate, according to Ardent Partners' 2025 State of ePayables report. Average teams pay $12.88 per invoice and take 17.4 days. That gap isn't headcount or budget. It's process discipline plus automation, in that order.

The canonical AP process runs through seven discrete steps, each with its own controls and its own opportunity for cost and cycle-time savings.

Key Takeaways

• The AP process is a seven-step workflow: invoice receipt, capture and validation, GL coding, matching to PO and receipt, approval routing, payment execution, and reconciliation to the ERP.

• The cost-per-invoice and cycle-time gap between top-performing and average AP teams closes through standardization first, automation second, in that order.

• Three-way matching catches the majority of overbilling and goods-receipt fraud. Two-way matching is appropriate for service and recurring spend. Four-way adds an inspection check for regulated or high-value goods.

• Segregation of duties matters most at four boundaries: vendor master maintenance, invoice entry, approval, and payment execution.

• Touchless processing rate is the leading KPI for an automated AP function. Cost per invoice, cycle time, first-pass match rate, and DPO complete the picture.

• AP automation that integrates natively with Acumatica, NetSuite, Sage Intacct, Microsoft Dynamics 365, QuickBooks, Xero, Oracle, and SAP keeps the ERP as the system of record and avoids re-keying.

What is the accounts payable process?

The accounts payable process is the workflow your finance team uses to receive, validate, approve, pay, and reconcile supplier invoices. It sits between the moment a supplier delivers goods or services and the moment your books close on the resulting liability. Done well, it pays the right vendors the right amount on the right day, with a clean audit trail behind every transaction.

The AP process is not the same as procurement, which sits upstream and covers sourcing suppliers, negotiating contracts, and issuing purchase orders. Procurement decides what you buy and from whom. AP handles what happens after the goods or services arrive. The boundary between the two is where the source-to-pay arc and procurement function hand off the purchase order to AP, with the goods receipt closing the loop.

How accounts payable fits into the source-to-pay arc

Source-to-pay is the broader cycle that runs from supplier sourcing through purchase order issuance, goods receipt, invoice processing, payment, and reconciliation. AP owns the back half, from receipt through reconciliation. Procurement owns the front half. The two functions handshake at the purchase order and the goods receipt, which are the documents AP needs to match invoices against.

Accounts payable vs. accounts receivable: the quick distinction

Accounts payable and accounts receivable are mirror functions. AP is money your company owes suppliers; AR is money customers owe your company. On the GL side, AP debits expense accounts and credits cash or a payable when invoices are paid. The mirror posting in AR debits receivables and credits revenue when customers are billed. The processes look similar on paper, but the discipline is different. AP runs on policy and approval, while AR runs on credit and collections.

What are the seven steps of the accounts payable process?

The canonical AP process runs in seven steps: invoice receipt, capture and validation, GL coding, matching, approval routing, payment scheduling and execution, and reconciliation. Each step has its own controls, exception paths, and KPIs. The order matters. Skipping or scrambling steps is how duplicate payments and unapproved spend slip through.

Step 1: Receive the invoice (and centralize intake)

Invoices arrive by email, EDI, supplier portal, paper mail, and occasionally fax. The first control is centralizing all of them into a single intake queue. Personal inboxes are where invoices die. They sit unread while a controller is on vacation, then surface two weeks past due with the supplier already calling about payment. A shared AP inbox, an OCR-fed digital queue, or a supplier portal puts every invoice in the same place with the same logging.

This is also the step where invoice processing automation earns most of its keep. AI-OCR pulls header data — vendor name, invoice number, dates, totals — and line-item detail straight out of the PDF or image. The intake queue becomes searchable and time-stamped, which makes the rest of the process auditable.

Step 2: Capture and validate invoice data

After intake, the invoice's data has to be captured and validated against business rules. Modern AI-OCR achieves around 99% accuracy on line-item extraction on standard invoice formats, per Corpay product benchmarking against typical mid-market invoice samples (2025). The remaining edge cases route to AP for manual review. Validation rules check that the vendor exists in the vendor master, the tax ID matches, the invoice isn't a duplicate, and the dollar amounts are within sane bounds.

Duplicate detection is the unglamorous workhorse here. A single duplicate paid in a year of high-volume AP is expensive; a recurring duplicate scheme tied to a fraudulent vendor record is catastrophic. The validation step is where you catch both, before the invoice ever gets routed for approval.

Step 3: Code to the GL, cost center, and project

Every invoice has to land against a general ledger account, a cost center, and (where you run project accounting) a project code. Auto-coding rules pay off here by reading the supplier and the historical coding pattern, applying the same coding automatically, and routing only the exceptions to AP. The function shifts from clerical coding to coding-exception review.

The wrinkle is project-driven industries like construction, professional services, and creative agencies, where invoices have to allocate across multiple jobs at varying percentages. The coding rules get more complex, but the principle stays simple. Rules handle the common case, and humans handle the edge.

Step 4: Match the invoice (2-way, 3-way, or 4-way)

Matching is the AP control that catches overbilling, goods that were ordered but never received, and price discrepancies between the PO and the invoice. The match compares the invoice to the purchase order (2-way), to the PO plus the goods receipt (3-way), or to the PO, receipt, and an inspection record (4-way). Three-way matching is the standard for goods purchases because it confirms three things at once: the price the supplier billed, the quantity the supplier shipped, and that you actually received what you paid for.

Matching is also the single step where automation produces the largest cycle-time gain. A human matcher comparing line items across three documents averages a few minutes per invoice; software matches the same three documents in seconds, with exception routing for anything outside tolerance.

Step 5: Route for approval

Approval routing sends each invoice to the right approver based on dollar threshold, department, vendor category, and policy. A $400 office-supplies invoice doesn't need the CFO's signature; a $400,000 capital expenditure does. The workflow has to enforce those thresholds without becoming a bottleneck. Most AP teams add an escalation path so an invoice waiting too long for one approver routes to a backup.

The friction signal AP managers report most often shows up here. When a buyer compares multiple invoices in an approval queue and the interface doesn't let them open them side by side, the approval step slows down for reasons that have nothing to do with the invoices themselves. Approval-workflow ergonomics matter more than they look like they should.

Step 6: Schedule and execute payment

Payment scheduling and execution is where AP turns from a workflow into a treasury function. The system schedules each approved invoice based on its due date and any early-payment discount terms (2/10 net 30 still saves real money when you can take it). Execution sends the payment through whichever rail fits the supplier and the policy, whether ACH, check, virtual card, wire, or cross-border.

The choice of rail isn't neutral. Virtual cards earn rebates from the issuer, which means a portion of supplier spend routed through cards comes back to the buyer as cash. Checks cost the issuer real money to print and mail and are the most fraud-prone rail still in common use. ACH is cheap and reliable but offers no rebate. The economics of the payment-execution step are why managed AP services exist, and why the question of whether to insource, outsource, or automate AP is worth taking seriously when you start optimizing cash flow with AP automation.

Step 7: Reconcile to the GL and report

The final step posts the payment to the GL, updates the vendor ledger, archives the audit trail, and reports the AP KPIs. Reconciliation closes the loop. The invoice that was a payable two weeks ago is now a paid expense, with the bank settlement and the GL entry tied to the same record. The audit trail captures who approved what, when, and why, which is what an external auditor will ask for first.

Reporting in a mature AP function isn't just month-end close. It's an ongoing dashboard, covering cost per invoice, cycle time, touchless rate, and exception volume, that AP leadership uses to find the next process improvement before it becomes a fire.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

When does 2-way vs. 3-way vs. 4-way matching apply?

Two-way matching compares the invoice to the purchase order. Three-way matching adds the goods receipt. Four-way matching adds an inspection record. The right choice depends on what you're buying and how much receipt or inspection evidence the spend warrants.

Two-way matching applied to a goods purchase is how overbilling and under-delivery slip through. Three-way matching applied to a SaaS invoice creates artificial friction with no risk reduction. Picking the wrong match level on a category of spend is one of the more common AP process design mistakes, and it costs both money and AP-team time. The good news: most automation platforms support all three levels and let you set the rule per vendor or per category.

What controls and segregation of duties does the AP process need?

The AP process needs controls at each step, but the controls that matter most sit at four segregation-of-duties boundaries. The same person should not control adjacent steps, because that's where collusion-free fraud schemes become possible. AP fraud cases almost always trace back to a missing boundary somewhere in this chain. Common patterns include a vendor master that an AP clerk could edit, an approval threshold one person could authorize and execute, or a bank reconciliation done by the same person who released the payment run.

The four segregation-of-duties boundaries every AP team needs

These four boundaries cover the points where a single person controlling adjacent steps creates fraud opportunity:

• Vendor master maintenance is separated from invoice entry. The person who can add a new vendor record can't be the same person who enters invoices against it. Otherwise a fake vendor plus a fake invoice equals a paid invoice.

• Invoice entry is separated from approval. The person who keys in the invoice doesn't approve it for payment. This is the most common control, and the easiest to enforce in software.

• Approval is separated from payment execution. The approver doesn't release the payment run. This stops an approver from rushing payments outside of policy or executing a payment they're not authorized to release.

• Payment execution is separated from bank reconciliation. The person who released the payment doesn't reconcile the bank account afterward. That's how you catch payments that left but weren't supposed to.

Audit trail and compliance posture

Every step in the AP process has to leave an audit trail. At a minimum, that trail captures:

• Invoice entry: who entered it, when, against which PO, with what coding applied

• Approval: who approved it, at what dollar threshold, under whose delegated authority

• Payment execution: who released the payment run, against which bank account, on what rail

• Reconciliation: who matched the bank settlement to the GL entry and closed the loop

A clean audit trail is what an external auditor wants to see, and it's what a CFO needs when a payment later comes into question.

Compliance posture matters too. Corpay is SOC 2 Type II compliant, which means an independent auditor has verified that operating controls over invoice handling, payment execution, and customer data meet the trust service criteria. When you're routing invoices and payment instructions through an AP platform, that audit is the assurance that the platform isn't its own source of risk.

What are the best practices and KPIs for the AP process?

Best practices for AP fall into two buckets. First comes the process discipline. Second come the metrics that tell you whether the discipline is working. The discipline itself is unglamorous: documented workflows, clean vendor masters, real approval thresholds, periodic payment-run review. The metrics are where the discipline shows up.

Standardize before you automate

Document your current-state AP workflow before automating any part of it. Auxis' 2026 AP automation research is direct about this — automating a broken process bakes the broken process into software. Sit with your AP team for a week, map what they actually do (not what the process documentation says they do), and fix the obvious breaks before introducing a tool. The AP automation best practices write-up walks through what process standardization looks like in practice.

Track the five KPIs that matter

There are dozens of possible AP metrics. Five carry most of the diagnostic weight:

• Cost per invoice. The total fully loaded cost of running AP, divided by invoice volume. This is the headline benchmark from the Ardent figures referenced in the intro — a wide spread between top-performing and average teams.

• Cycle time. Days from invoice receipt to payment release. The same Ardent dataset shows a 14-day gap between top and average performers, which is roughly the difference between paying inside discount terms or missing them.

• Touchless processing rate. The percentage of invoices that flow from intake to approval with zero manual touches. The top-performing benchmark sits near half of all invoices.

• First-pass match rate. The percentage of invoices that match the PO and receipt on the first try, without exception handling. A low rate signals upstream problems — sloppy PO data, vendor master gaps, or inappropriate match levels.

• Days payable outstanding (DPO). How long you take to pay suppliers, on average. DPO is a working-capital lever; the question isn't "high or low?" but "intentional or accidental?"

Capture early-pay discounts and card rebates

Two cash-flow levers hide inside the AP process. The first is dynamic discounting, which means taking 2/10 net 30 terms when they're offered, because a 2% discount on a 20-day acceleration is an outsized return on cash (the implied annualized yield is around 36%, per IOFM benchmarking). The second is virtual card rebates. When a portion of supplier spend routes through commercial cards, the issuer pays a rebate back to the buyer. Per RPMG Research's 2023 Electronic Payments Survey, commercial card rebates typically run between 0.5% and 1.5% of card spend depending on volume and category mix. For AP teams processing several million dollars a year in card-eligible spend, rebates can offset a meaningful share of the platform cost. The 10 signs your AP process is costing you more than it should covers the cost levers in more detail.

See how Corpay AP Automation handles supplier enablement, virtual card rebates, and ERP integration in a single workflow.

How does AP process automation change the economics?

Automation collapses the cost per invoice and the cycle time. It does so by removing manual touches from the four steps where humans don't add judgment: intake, capture, coding, and matching. AP teams that automate reduce processing costs by roughly 78% relative to their peers, with an average first-year ROI of around 200% (Auxis, 2026 AP Automation Best Practices). The platform-specific cost and cycle-time impact is covered in the Corpay product section below.

What touchless processing actually means

Touchless processing is an end-to-end automation pattern where an invoice arrives, gets captured, gets coded, gets matched, and routes to the right approver without an AP clerk touching it. The Emburse 2026 AP automation guide describes this as the standard expectation for mid-market AP teams. top-performing teams hit the touchless-rate benchmark mentioned earlier because they've automated the steps where humans don't add judgment and concentrated AP labor on exception handling, vendor management, and analysis.

Where AI-OCR plus matching collapses cost and cycle time

The mechanism is straightforward. A human AP clerk processing a typical invoice manually performs around fourteen touches — opening the email, downloading the PDF, keying header data, looking up the vendor, validating against the PO, matching to the receipt, coding the GL accounts, routing for approval, following up on approval, scheduling the payment, executing the payment, reconciling the payment, archiving the documents, and updating the vendor record. AI-OCR plus rules-based matching collapses most of those into automated steps, leaves the human with the genuinely judgment-bound work, and produces a per-invoice cost that competitors charging $12 a touch can't match.

Ardent Partners' 2025 research shows 75% of AP departments now use some form of AI or automation tooling. The question isn't whether to automate; it's where on the curve you sit, and what the next investment is worth.

How does the AP process work across your ERP?

Corpay AP Automation runs natively against Acumatica, NetSuite, Sage Intacct, Microsoft Dynamics 365, QuickBooks, Xero, Oracle, and SAP, plus the construction ERPs eCMS, CMiC, and Computer Guidance Corporation. The integration keeps the ERP as the system of record and writes captured invoices, approved liabilities, and posted payments back to the GL automatically.

The integration model matters because re-keying between AP and the ERP is where automation savings leak. If the AP system captures an invoice and an AP clerk has to re-enter it in the ERP afterward, you've automated half a step and added a second step. A native integration provides bidirectional API sync, vendor master alignment, and COA-aware coding, which is what makes the touchless rate achievable. For finance teams running on NetSuite, the Corpay-NetSuite AP integration overview walks through what the integration looks like at the workflow level. The managed AP service for Sage Intacct covers the rebate-revenue angle for Sage shops.

One authored observation worth flagging: when you evaluate AP automation platforms, ask the vendor for before-and-after AP cost-per-invoice and cycle-time data from a customer of roughly your size and industry, not from a demo environment. Demo numbers are optimized for the demo. Customer numbers are what you'll actually see.

Modernize your accounts payable process with Corpay

Corpay AP Automation handles all seven steps of the AP process end-to-end. AI-OCR captures invoices at the line-item accuracy level discussed in Step 2, configurable 2-way and 3-way matching applies the right control to the right category of spend, approval workflows route by dollar threshold and policy, and payments execute by ACH, check, virtual card, wire, or cross-border. The platform integrates with 180+ ERPs, including the construction-specific ERPs most platforms skip.

The managed payment service is what changes the AP team's role. Corpay handles supplier outreach, enables suppliers for virtual card payments, executes the payments, and manages the reconciliation. AP shifts from a cost center running clerical work to a function that earns rebates on the spend it routes through cards. For finance teams already evaluating the build-vs-buy question, the comparison of automating versus outsourcing AP is the right starting point.

Per-invoice cost drops from $10–15 to under $3, cycle time from 17 days to 3–5, and about 40% of AP-team capacity opens up for higher-value work. As the #1 commercial Mastercard issuer working with 800,000+ businesses, Corpay has the network effect that makes supplier enablement and virtual card acceptance real, not theoretical.

See how Corpay AP Automation fits your ERP and your AP workflow, or take a wider view with the Corpay Complete integrated spend platform if your team is also evaluating cards and expense.

Frequently Asked Questions

What is the accounts payable process?

The accounts payable process is the workflow that turns a supplier invoice into a paid liability — invoice receipt, data capture, GL coding, matching to a purchase order and receipt, approval routing, payment execution, and reconciliation to the ERP. It owns everything between supplier delivery and the closed books.

What are the steps in the accounts payable process?

There are seven canonical steps: receive the invoice, capture and validate the data, code to the GL and cost center, match to the PO and receipt, route for approval, schedule and execute payment, and reconcile to the GL. Some teams collapse the first three into "invoice intake," but the discipline of each step still applies.

What is the difference between accounts payable and accounts receivable?

Accounts payable is money your company owes suppliers; accounts receivable is money customers owe your company. AP debits expense accounts when invoices are paid; AR debits receivables when customers are billed. The processes are mirror images, but AP runs on approval policy and AR runs on credit and collections.

What is the accounts payable cycle?

The AP cycle is the recurring loop the process runs in — receive, capture, match, approve, pay, reconcile, repeat. Some finance teams use "AP cycle" interchangeably with "AP process"; others use it more narrowly to describe the timing pattern (when invoices come in, when payment runs go out, how the cycle closes against the month-end accrual).

What is three-way matching in accounts payable?

Three-way matching compares the supplier invoice to the purchase order and the goods receipt before approving the invoice for payment. It confirms three things at once: the price the supplier billed matches the negotiated price, the quantity the supplier shipped matches what you ordered, and you actually received what you're being asked to pay for.

How do you automate the accounts payable process?

AP automation typically combines AI-OCR for invoice capture, rules-based matching against the PO and receipt, workflow-driven approval routing, and integrated payment execution across multiple rails. The AP automation platform overview covers the architecture and what good looks like in evaluation.

What KPIs should I track for the accounts payable process?

The five most diagnostic KPIs are cost per invoice, cycle time, touchless processing rate, first-pass match rate, and days payable outstanding. The Ardent Partners and IOFM benchmarking surveys publish industry medians for each, which gives you a calibration point for where your AP function sits relative to peers.

Should I outsource accounts payable or automate it in-house?

It depends on the trade-off between control and capacity. Automation in-house keeps the process under your team's control but requires platform investment and ongoing operations. Outsourcing — including managed AP services — shifts the operational burden but reduces day-to-day visibility. The pragmatic middle ground for most mid-market teams is automation with a managed payment service layer, which keeps AP in-house while handing the supplier-enablement and payment-execution work to a specialist.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation

Payments Automation