The accounts payable process, built from the task list
A weekly AP run is six or seven recurring tasks wearing one name. How to map the accounts payable process into steps, owners, checks and exceptions.

Ask a finance team who does the AP run and you will usually get one name. Ask what the AP run actually is and the answer gets longer: invoices arrive, get coded, get matched, get approved, get scheduled, get paid, get reconciled, and suppliers ring up about the ones that did not. That is not one task. It is six or seven recurring tasks that happen to share a name, a deadline and, too often, a person. This post walks through the accounts payable process the way we think every recurring process should be written down: built from the task list, step by step, with an owner, a check and an exceptions route for each.
Why "the AP run" hides the work
When a process carries one name, it tends to get one owner, one line on the close calendar and one rough estimate of time. All three are wrong in useful ways.
One owner means nobody else knows the steps in the middle. One line on the calendar means the slow parts, usually chasing approvals, never show up as work. One estimate means nobody can see where the hours go, so nobody can fix them. As with the real cost of a bank reconciliation, the money sits in the exceptions and the chasing, and AP ends in a payment that is hard to take back.
The accounts payable process as a task list
Here is a weekly AP run broken into recurring tasks. Take it as a hypothetical mid-size finance team paying suppliers every Thursday. Your steps will differ in the detail. The shape usually holds.
1. Capture incoming invoices
Runs daily. Someone logs each invoice from email, portal or post and checks it is addressed to the right entity. The check: no invoice sits in the inbox for more than a working day. The common exception is a statement or reminder posing as an invoice.
2. Code and match
Runs daily or every other day. Each invoice gets a supplier, a nominal code, a cost centre and a VAT treatment, and where there is a purchase order, it is matched to the order and the goods received note. The check: the totals agree within a written tolerance. The exceptions are price differences, part deliveries and invoices with no order at all.
3. Get approval
Runs continuously, with a cut-off. Invoices outside the purchase order route go to a budget holder. This is the step that eats the week. The check is simple: every invoice in the payment run has an approval from someone with the authority for that amount. The task is the chasing, and it deserves its own owner and a written reminder rule, like any other chase that recurs every week.
4. Verify supplier changes
Runs whenever it is triggered, but it belongs on the list. New suppliers and changes to supplier bank details are where payment fraud gets in. The step is to confirm any change by calling a number already on file, not one given in the email that requested the change, and to record who confirmed it and when. This step should never be skipped to make a deadline.
5. Prepare the payment run
Runs weekly, on Wednesday in this example. Select approved invoices due before the next run, apply any credit notes, check cash against the forecast and produce the proposed list. The check: the list reconciles to the approved, unpaid invoices in the ledger, and anything held back has a written reason.
6. Approve and release the payment
Runs weekly. A second person, with authority, reviews the proposed list and releases it in the bank. This is a four eyes control, and like the payroll check it is recurring work with its own method that should be written down: what the approver actually looks at, and what makes them stop.
7. Post, reconcile and answer suppliers
Runs weekly, the day after. Payments are matched to the bank, remittances go out, and the supplier queries from the week are answered and logged. The check: the AP control account agrees to the aged creditors report.
What to capture for each task
Once the run is a list, each line can carry the same fields as any other recurring task:
- Calendar rule. "Every Wednesday by 2pm", "daily before 11am", "on trigger".
- Owner and backup. Two names, not one, for every step.
- Checklist. The checks above, written as steps someone else could follow.
- Inputs. Where the invoices, orders and approvals come from, and what format they arrive in.
- Exceptions. The usual kinds, and where each one goes. An exceptions log kept against each step shows which kinds come back.
- Effort. Measured from when the step started and finished, not guessed.
Say, for illustration, that the team above spends ten hours a week on AP. Written as one task, that is ten hours of "AP". Written as seven, it might turn out that three of those hours are chasing approvals and two are answering suppliers who were not told about a held invoice. Those are fixable numbers. "AP takes ten hours" is not.
Where the steps differ for an agent
Splitting the run also makes it easier to talk honestly about AI, because the steps are very different in kind.
Capture, coding and matching are frequent, rule bound and checked by totals. They are reasonable candidates for an agent that drafts while a person reviews, once the coding rules and tolerances are written down. Preparing the proposed payment list is similar: an agent can assemble it, and a person checks it.
Verifying supplier bank changes and releasing the payment are different. The blast radius is a payment that may not come back. They should stay with people, and the written method for them is a control, not a step to hand over. Answering supplier queries sits in between: an agent can draft the reply from the ledger, and a person sends it.
Without the list, the conversation is "should AI do our AP", which has no good answer. With it, the conversation is about one step at a time. This is the kind of task level picture Beaks is built to hold, but a shared spreadsheet is enough to start.
Bring the people who do it
The best version of this list comes from the people who run AP. They know which approver always needs a second reminder and which step quietly takes Thursday morning. Ask them to write it, and say what it is for: better cover, fewer late payments, and taking the dullest steps off their desks first.
One thing to do this week
Sit with whoever runs your next payment run and write down every step they take, from the first invoice in the inbox to the last remittance out. Put a name and a rough time next to each step. Then mark any step with only one name against it. That is where to start writing things down.

