Accounts payable is often described by its outputs rather than its functions, which makes it hard to staff or improve. Seven distinct tasks make up the work, and two boundaries define where it stops. Being clear about both is what lets a team say what is theirs to fix and what belongs to somebody else.
The seven tasks
Receiving and recording invoices. Validating them against what is already known. Matching against orders and receipts. Routing for approval and recording the decision. Coding to accounts and cost centres. Scheduling and executing payment. And maintaining supplier records including bank details, which is the one most often treated as incidental and is the highest-risk of the seven.
The upstream boundary
Purchasing decides what is bought and issues orders; operational staff record what arrives. Payables inherits the quality of both and controls neither. This is why an efficient payables team can still be busy: the ratio of matchable to unmatchable invoices is set outside the function, and reporting it is more effective than absorbing it.
The downstream boundary
The general ledger and the accounting treatment. Payables produces accurate, timely detail; how a transaction should be classified, accrued or reported is decided by your accountant. Keeping that boundary clear stops payables being asked to make judgements it is not positioned to make and is not accountable for.
Questions people ask about accounts payable functions
Which function carries the most risk?
Supplier record maintenance, because bank details decide where money goes. It is frequently the least controlled of the seven.
How should the team be measured?
On queue state, the age of the oldest item and the clean match share, with the last understood as partly a measure of other departments.
Where does statement reconciliation fit?
Within validation and supplier maintenance. It is the check that finds invoices you never received.