Accounts payable workflow: 7 steps, controls, and a flowchart

An accounts payable workflow is the controlled path an invoice follows from receipt through validation, approval, payment, reconciliation, and record storage. It is both an accounting process and a business process management (BPM) problem: every step needs an owner, a rule, and a safe exception path.

The short version: receive the invoice in one place, check that it is valid and unique, match it to what the business ordered or received, route it to the right approver, release payment under policy, and retain the evidence. Anything that fails a check goes on hold with a named human owner.

What an accounts payable workflow means

Accounts payable is the record of money a business owes vendors. The workflow is the operating system around that record: how an invoice enters, how its details are checked, who approves the spend, who releases the payment, and how finance proves what happened later.

Most teams need two routes. A PO-backed invoicecan be checked against a purchase order and, when relevant, a receiving record. A non-PO invoice needs coding, business-purpose context, and approval from the person who owns the spend. Both routes should rejoin before payment authorization.

The point is not to make every invoice take the same route. The point is to make the route predictable, visible, and controlled when the invoice does not match the happy path.

A process flowchart is useful only if it shows the stop conditions. Missing POs, price or quantity variances, suspected duplicates, overdue approvals, and changed payment details should route to an exception queue—not quietly continue toward the bank.

The seven accounts payable workflow steps

1. ReceiveGive vendors one invoice address or portal. Create a received timestamp and a unique workflow record so email is no longer the status system.
2. Capture and validateRecord the vendor, invoice number, invoice date, amount, currency, due date, PO or contract reference, and supporting document. Check required fields and likely duplicates before routing.
3. Code and matchAssign the GL account, cost center, project, and tax treatment. For PO-backed spend, compare the invoice to the purchase order and receiving evidence; document approved tolerances.
4. ApproveRoute by spend owner, amount, category, and entity. Show the approver the invoice, supporting evidence, match result, and reason for any exception.
5. Authorize paymentConfirm the invoice is approved, the vendor is eligible, the payment details are verified, the due date is appropriate, and the payment batch follows policy.
6. Execute and notifyRelease the payment through the approved bank or payment platform, prevent duplicate submission, and send remittance details when the vendor needs them.
7. Reconcile and retainMatch the payment to the open bill and bank activity, post it correctly, resolve residual balances, and store the invoice, approval, exception notes, and proof of payment together.

Each stage needs a role, not a vague department. AP can own intake and completeness; the requester or buyer owns business context; the budget owner approves spend; an authorized payer releases funds; and finance reconciles the result. Small teams can combine roles, but the same person should not prepare, approve, and release a payment without an independent review.

The exception path is the real AP workflow

Routine invoices are rarely the reason an AP process fails. The delay and risk collect around exceptions. A useful workflow names the system action, human owner, and evidence required to release each hold.

Where accounts payable automation should stop

AP automation is strongest when it performs repeatable, evidence-based work and makes the remaining judgment visible. Microsoft's accounts payable guidance describes the same boundary: invoices that meet defined criteria can move through automated review, while the rest are flagged for an authorized user.

• Automate: invoice intake, file naming, and workflow record creation.
• Automate: field extraction with confidence thresholds and source links.
• Automate: duplicate checks, policy routing, reminders, and escalation timers.
• Automate: match attempts, status updates, and audit-log capture.
• Hold for review: low-confidence extraction or missing support.
• Hold for review: price, quantity, receipt, or coding exceptions.
• Hold for review: new vendors and changed payment instructions.
• Hold for review: payment release, unusual timing, or policy overrides.

AI can classify documents, extract fields, suggest coding, and summarize the evidence for an approver. It should not quietly invent a missing PO, resolve a bank change, or release funds. Give every automated action an idempotency rule so a retry cannot create a second bill or payment, and give every failure a resumable workflow orchestration path.

If documents are still scattered across inboxes and shared drives, start with the document workflow around intake, review, and storage before adding AI. If the process is clear enough to implement, the workflow automation consulting guide explains how to scope one supervised pilot.

A 30-day supervised AP workflow pilot

Start with one invoice type, one entity, and one approval path. The first month should prove that the workflow is safer and easier to operate—not merely that the software can move a PDF.

1. Week 1 / MapFollow real invoices from receipt to reconciliation. Record owners, systems, wait time, touch time, exceptions, rework, and the evidence required at each decision.
2. Week 2 / ShadowConfigure capture, routing, checks, and holds. Run beside the current process without releasing payments; compare every proposed action with what finance actually did.
3. Week 3 / ControlMove the selected invoice type into the new workflow with human review at matching, exceptions, and payment release. Keep a rollback path and log every correction.
4. Week 4 / DecideReview the evidence with AP and the controller. Fix recurring exception causes, document ownership, and expand only if the controls and operator experience hold up.

Measure: end-to-end cycle time, active touch time, first-pass match rate, exception rate, approval age, duplicate holds, corrections after posting, and vendor status inquiries. Baseline first; improvement claims come after the pilot.

ArcVelocity's Workflow Diagnostic is built for this first step: map one real handoff, define the exception path, and decide whether implementation is justified.

Straight answers

What to fix first

I start with the invoice path that repeats often, stalls visibly, and carries meaningful risk. For many small teams, that is scattered intake, approval routing, duplicate checking, or vendor payment changes—not a complete AP platform replacement.

Give that path one intake point, one owner per stage, one approval policy, one exception queue, one payment-release control, and one record location. Then automate the repeatable parts after the handoff is clear enough to survive a normal month-end.

Back to top