Accounts payable workflow playbook
Accounts payable workflow: from invoice receipt to clean books
Map an accounts payable workflow from invoice receipt through validation, coding, approval, posting, payment evidence, and reconciliation.
Short answer
An accounts payable workflow is the governed path a payable document follows from receipt to a recorded and reconciled outcome. A practical workflow collects the source, classifies the document, validates the details, resolves exceptions, applies coding, obtains approval, posts the record, and preserves the evidence needed for payment and close.
Key takeaways
- Treat intake, accounting preparation, approval, posting, and payment as related but separate stages.
- Give every active document one owner, one next action, and one truthful destination.
- A workflow is complete only when the accounting result and supporting evidence agree.
- Use exceptions to improve the process instead of hiding them inside a generic review queue.
The eight stages of a controlled AP workflow
The exact roles vary by company, but the underlying sequence stays remarkably consistent. Keeping the stages explicit prevents a captured document from being mistaken for an approved or posted liability.
- 01ReceiveAccept invoices, receipts, statements, credits, and supporting records through known intake lanes.
- 02PreserveStore the original source, sender or upload context, and a durable receipt before deeper processing begins.
- 03ClassifyDetermine whether the source is a bill, paid receipt, statement, credit, payment evidence, decision document, or not AP.
- 04PrepareExtract the vendor, reference, dates, amounts, terms, lines, tax, memo, and proposed accounting dimensions.
- 05CheckTest duplicates, existing accounting records, purchase-order or receipt relationships, and policy requirements.
- 06ResolveAsk only for the missing fact that blocks progress, then recompute readiness immediately.
- 07Approve and postRecord the authorization, perform the accounting write once, and verify the returned object.
- 08Reconcile and retainKeep the source, approval, posting receipt, attachments, payment evidence, and final destination connected.
Use workflow states that describe real business truth
Labels such as processing, attention, and complete are too vague when money and books are involved. A useful state tells the operator what is true and what action, if any, comes next.
| State | Meaning | Next action |
|---|---|---|
| Received | The source is stored but not yet prepared | Wait for analysis or retry a named failure |
| Needs checking | One or more facts are uncertain | Answer the leading question |
| Ready for approval | Required evidence is present | Review the proposal and approve or return |
| Ready to post | Approval and posting inputs are complete | Authorize the accounting write |
| Posted and verified | The accounting record read back correctly | Retain the receipt and continue reconciliation |
| Resolved without write | Existing truth or non-AP classification closed the work | Keep the evidence and reason |
Design the workflow around exceptions
The straight-through path is easy. The quality of an AP workflow is revealed by how it handles the uncertain vendor, repeated invoice number, partial purchase order, paid receipt, missing job, credit, statement line, or provider failure.
Each exception should name the disputed fact, show the evidence, offer a bounded decision, and return the document to the correct state. A generic warning that sends the reviewer to a dense detail page simply relocates the work.
- Prioritize the leading unresolved fact instead of stacking warnings.
- Keep relationship evidence separate from accounting treatment.
- Never use amount alone to prove that two records are the same.
- After a correction, reread live readiness rather than relying on stale client state.
- Preserve rejected candidates so the same false match is not proposed repeatedly.
Separate preparation, approval, posting, and payment authority
A small company may have one person wearing several hats, but the system should still distinguish the actions. Preparing a record is not approval. Approving a bill is not permission to release funds. Posting a liability is not proof that it was paid.
Clear action receipts make those boundaries visible even when one owner performs several steps. As the company grows, the same workflow can support role-based controls without reconstructing its history.
A simple weekly operating rhythm
The workflow should make the weekly review short enough to sustain. Start with intake health, clear the oldest or most consequential exceptions, approve ready records, verify posting outcomes, and finish with unresolved vendor statements or payment evidence.
- Confirm every expected source has checked in successfully.
- Resolve items blocked by one missing fact.
- Review duplicate and existing-transaction candidates before new writes.
- Approve and post only records with the source visible.
- Confirm partial failures and attachment jobs have a recovery owner.
- Carry a short aging list into the next review instead of reopening the entire queue.
Common questions
Plain answers for the next decision.
What is the accounts payable cycle?
The AP cycle runs from receiving a payable document through validation, coding, approval, posting, payment, and reconciliation. The workflow is the set of states, roles, evidence, and controls that governs that cycle.
What is the most common AP workflow failure?
A common failure is losing context between intake and accounting. The document sits in email, approval happens in a message, and posting occurs elsewhere, leaving no single record of what was reviewed.
Should every invoice require the same approval?
Not necessarily. Approval can depend on amount, vendor, location, job, category, purchase-order status, or policy. The rule and the resulting authority should be visible and auditable.
Where does payment fit in the workflow?
Payment follows a valid payable and any required payment authorization. Payment evidence should link back to the bill, but posting and payment should not be collapsed into one ambiguous status.
Sources and further reading
See the workflow in APStack
Move from the guide to the product path.
AP automation workflow
See the APStack product path for collection, review, approval, and posting.
Explore this workflowInvoice exception management
Explore how named blockers stay visible without slowing clean work.
Explore this workflowVendor invoice management
Keep vendor context and recurring decisions with the AP record.
Explore this workflowTry the workflow
Start with one real AP document.
Upload a bill, receipt, or statement and see how APStack keeps the source, review, approval, and QuickBooks path together.