The Accounts Payable Process: The 8 Steps, the Controls, and Which Ones an Agent Can Run

Your finance team has the AP process mapped on a whiteboard. The steps look clean. The logic is sound. And yet invoices still get stuck in someone's inbox, duplicate payments slip through quarterly, and month-end close runs two days late because nobody can explain where a specific bill went.

The problem is rarely the map. It is the gaps between steps where documentation is missing, approvals time out, and manual handoffs introduce errors that compound downstream. Human error, delayed approvals, and compliance gaps are the most consistent failure modes in accounts payable, and they do not disappear just because you have a documented accounts payable process.

This guide covers the eight canonical steps in order, the control that belongs at each gate, and a direct verdict on which steps an AI agent can run unattended versus which need a human in the loop.

The Accounts Payable Process in 8 Ordered Steps

The account payable process runs in a fixed sequence. Skipping or reordering steps is where most errors originate.

Step 1: Purchase Order Creation and Approval

A purchase order authorizes spending before a vendor delivers anything. Procurement creates the PO, a manager approves it within a defined dollar threshold, and the PO number becomes the anchor for every downstream document. Without a PO, invoice coding and matching have no reference point.

Step 2: Goods or Services Receipt and Confirmation

When goods arrive or services are delivered, the receiving team logs a goods receipt or delivery confirmation. This document proves that what was ordered was actually received. It is the second leg of the 3-way match and is frequently skipped in service-based businesses, which is where fraud exposure starts.

Step 3: Invoice Receipt and Capture

The vendor sends an invoice. Invoice capture converts that document, whether paper, PDF, or EDI, into structured data your system can read. Invoice automation handles this step through OCR or AI extraction, pulling vendor name, line items, amounts, and due date. Manual data entry at this step is the single largest source of downstream coding errors.

Step 4: 3-Way Matching — PO, Receipt, and Invoice

The accounts payable process is the end-to-end workflow a business uses to receive, validate, and pay vendor invoices in a controlled, auditable sequence. It begins with an approved purchase order and ends with a reconciled payment record. Every step in between exists to confirm that money leaving the business corresponds to goods or services actually received at the agreed price.

Three-way matching invoice validation is the control gate at the center of that process. It compares the purchase order, the goods receipt, and the vendor invoice across three fields: quantity, price, and vendor identity. If all three documents agree within tolerance, the invoice moves forward automatically. If they do not match, the invoice stops and generates an exception for human review. This is not a verification task. It is a fraud and overpayment prevention mechanism.

Step 5: Invoice Coding and GL Allocation

Coding assigns each invoice line to the correct general ledger account, cost center, and department. Consistent GL coding is what makes financial reporting accurate. Teams that code manually and inconsistently produce reports that require rework before every close. Automation tools can suggest coding based on vendor history, but someone needs to own and audit the coding rules.

Step 6: Approval Routing Based on Amount and Policy

Invoices above certain thresholds route to additional approvers. The routing logic is driven by your approval matrix: who can approve what dollar amount, whether a second signature is required, and how long an approval can sit before it escalates. Approval bottlenecks at this step are the most common cause of late payments and early-payment discount losses.

Step 7: Payment Scheduling and Execution

Approved invoices enter the payment queue. Payment scheduling matches due dates against cash flow position and payment method, ACH, check, wire, or card. Executing payments on the correct date prevents late fees and preserves vendor relationships. This step also determines whether the business captures early-payment discounts offered by suppliers.

Step 8: Reconciliation and Record Archiving

After payment executes, the AP team reconciles the payment against the invoice and the bank statement, then archives all supporting documents. Reconciliation closes the loop on each transaction and produces the audit trail required for compliance. Incomplete archiving at this step is the most common cause of failed audits.

The Internal Controls That Belong at Each Step

Finance ops teams that bolt controls on at month-end rather than at each process gate are managing risk after the fact. Fraud prevention controls are struggling to keep pace with invoice complexity in 2026, and the response cannot be a single review at close. Controls need to be embedded at each of the eight steps.

Segregation of Duties: Who Can Do What

No single person should be able to create a vendor, approve an invoice, and execute a payment. Segregation of duties means the person who requests a PO cannot approve it, the person who approves an invoice cannot initiate payment, and the person who executes payment cannot reconcile it.

In small teams this is the hardest control to enforce because headcount is limited. The practical fix is a compensating control: a manager reviews a random sample of completed transactions weekly, even if they could not approve each one in real time. Document the compensating control explicitly so auditors can test it.

Tolerance Thresholds and Exception Triggers

Every 3-way match needs a defined tolerance. A common threshold is plus or minus 2 to 5 percent on price variances and zero tolerance on quantity discrepancies. Invoices inside tolerance auto-approve. Invoices outside tolerance generate an exception that routes to a human reviewer.

Without documented thresholds, the matching step becomes a judgment call made differently by each team member. Auditors test whether tolerances are written into policy and consistently applied. If your tolerance lives in someone's head, it does not exist as a control.

Audit Trail Requirements at Each Gate

Every status change in an invoice's lifecycle needs a timestamped log: who received it, who coded it, who approved it, when it was paid, and which account it hit. Missing documentation, whether a purchase order, delivery confirmation, or approval record, creates gaps that cause problems during audits and regulatory reviews.

Your audit trail must be exportable. If retrieving it requires manual screenshot assembly from three different systems, it is not a functional control. Auditors test whether the trail is complete, not just whether it exists.

Which Accounts Payable Process Steps an AI Agent Can Own

Not every step in the AP workflow carries the same judgment requirement. Volume and repetition make some steps obvious automation candidates. Others carry financial, legal, or relationship risk that requires human accountability.

Steps Safe for Full Agent Execution (Low Judgment, High Volume)

Invoice capture, 3-way matching on clean data, and GL coding on known vendors are the steps where agent automation delivers the most value with the least risk. These tasks are high-volume, pattern-based, and produce a binary output: match or exception, correct code or flag.

AP handling time can be reduced significantly through automation at these steps, but that result assumes clean vendor master data and a well-mapped process going in. Automating a broken matching process does not fix the breaks. It accelerates them.

This is exactly the category of work Predflow agents are built for. Rather than layering a tool on top of your existing process, Predflow starts with process mapping, identifying the steps where automation adds value without introducing risk, then deploys agents that handle edge cases and flag exceptions for human review. The result is end-to-end coverage without the blind spots that come from tools-first implementations.

Steps That Need Agent-Assist with Human Sign-Off

Approval routing and GL coding on new or irregular spend sit in the middle tier. An agent can trigger the routing and suggest the code, but a human needs to confirm before the invoice advances. Teams using ap automation software like NetSuite AP automation or bill.com follow this pattern in practice: the platform handles matching and routing, but users still manually resolve exception invoices, which make up a disproportionate share of the total processing time.

The agent-assist model works because it removes the mechanical steps from the human's workload while keeping judgment in human hands. The reviewer sees only the invoices that need a decision, not every invoice in the queue.

Steps That Should Stay Human-Led

Vendor onboarding, payment execution above defined thresholds, and exception resolution require human accountability. Vendor master management is the step most teams skip or under-resource, and it is where payment fraud most often originates. A bad actor who can create or edit a vendor record controls where payments go. That step must have a human approver who is not the same person who submitted the change.

Common Accounts Payable Process Failures and How to Fix Them Before Automating

Automating a broken process does not fix it. It locks the errors in at higher speed. These are the three failure patterns that appear most consistently before automation projects start.

Duplicate Invoices and How They Survive Approval Workflows

A duplicate invoice enters when the same bill arrives twice, by email and by mail, or when a vendor resubmits after not receiving a response. The duplicate survives because approvers check whether the invoice looks valid, not whether it has already been processed.

The structural cause is the absence of a duplicate detection rule at invoice capture. The fix is a lookup against open and paid invoices at the point of entry, comparing vendor, invoice number, amount, and date before the document enters the approval queue. This is a rules-based check that costs nothing to implement but requires the rule to be explicitly defined before automation can enforce it.

Approval Bottlenecks That Delay Payment and Damage Vendor Relationships

An invoice sits in an approver's inbox for eight days. The vendor charges a late fee. The approver did not know the invoice was there because the notification went to a shared email alias. This pattern is structural, not personal.

Approval workflows without escalation rules and without visibility into queue age are the cause. The fix is a maximum dwell time per approval stage, an automatic escalation to a backup approver after that time expires, and a dashboard that shows every invoice currently awaiting approval and how long it has been waiting. Define this logic before deploying any ap automation software, because automation will only route invoices into the same broken queue faster.

Missing Documentation That Creates Audit Exposure

Auditors test completeness, not just accuracy. An invoice that was paid correctly but lacks a PO, a goods receipt, or an approval log is still an audit finding. Teams that rely on email threads as documentation cannot produce a clean audit trail quickly.

The fix is a document attachment requirement at each step. No invoice advances without an attached PO reference. No payment executes without an attached approval record. This sounds basic because it is. But teams consistently skip it until an audit exposes the gap.

Frequently Asked Questions

What is the accounts payable process step by step?

The accounts payable process runs in eight steps: purchase order creation and approval, goods or services receipt, invoice capture, 3-way matching against the PO and receipt, GL coding and allocation, approval routing by amount and policy, payment scheduling and execution, and reconciliation with record archiving. Each step triggers the next, and each has a corresponding control that prevents errors or fraud from advancing downstream.

What is 3-way matching in accounts payable?

Three-way matching compares three documents: the purchase order, the goods receipt, and the vendor invoice. If quantity, price, and vendor identity align across all three within your defined tolerance, the invoice passes automatically. If any field falls outside tolerance, the invoice stops and routes to a human reviewer. It is a fraud and overpayment prevention control, not just a verification step.

How does AP automation software reduce processing time?

AP automation handles the high-volume, rules-based tasks: invoice capture, data extraction, duplicate detection, 3-way matching within tolerance, and approval routing. These tasks make up the majority of invoice processing time. Removing manual handling at each of these stages compresses cycle time significantly, but the reduction depends on data quality and how well the process is mapped before automation is deployed.

What is the difference between AP outsourcing and AP automation?

AP outsourcing moves your process to an external team. AP automation keeps the process in-house but removes manual steps through software and agents. Outsourcing transfers accountability and headcount. Automation retains control internally while reducing labor requirements. Most businesses use automation to handle volume and reserve outsourcing for specific functions like vendor communication or dispute resolution.

How do I know if my accounts payable process is ready for automation?

Your process is ready for automation when three conditions are met. First, your vendor master data is clean and has a documented owner. Second, your approval matrix is written down and consistently applied. Third, your exception rate is low enough that agents will spend most of their time on clean invoices rather than routing problems to humans. If any of those three conditions is missing, fix it before deploying agents.

Make the Decision Your Process Is Now Ready For

You have the eight steps, the control that belongs at each gate, and a clear verdict on which steps an agent can own. The process is not abstract anymore.

The remaining question is whether your current workflow is clean enough to hand off. Before you evaluate any tool or platform, ask yourself one question: if you handed your AP process to an agent tomorrow, which step would break first? That answer is your starting point, not a vendor comparison or a software demo.

If you want to see how Predflow maps your existing AP workflow before deploying any agents, book a process review call. No demo deck, just a structured conversation about your current steps and where automation fits.