Automated controls run every time without getting tired. Manual controls bring judgement. A good payables process needs both.
Automated accounts payable controls run inside a system on every transaction, such as blocking a duplicate invoice number or enforcing approval limits. Manual controls rely on a person, such as calling a supplier to confirm new bank details. Automate rules that are clear and high volume, keep manual controls where judgement or outside contact is needed, and test both regularly.
An automated control is performed by a system: it runs the same way on every transaction once it is set up. Examples are a duplicate invoice block, a three-way match tolerance, a payment approval workflow and a rule that stops a payment to a supplier whose bank details changed recently.
A manual control is performed by a person: a reviewer reading the payment run, a call back to a supplier, a monthly review of supplier master changes or a reconciliation of the payables ledger.
Many controls are a mix: a system produces an exception report, and a person reviews and clears it. Auditors often call these IT-dependent manual controls.
| Feature | Automated | Manual |
|---|---|---|
| Coverage | Every transaction | Often a sample or a summary |
| Consistency | Same result every time | Depends on the person and the day |
| Judgement | None beyond the rule | Strong |
| Contact outside the system | Not possible | Possible, such as a call back |
| Main risk | Wrong set-up, or someone changes the rule | Skipped, rushed or rubber-stamped |
| Evidence | System settings and logs | Sign-offs, notes and records |
| Testing | Test the set-up and change control | Test samples across the period |
A spreadsheet can carry automated-style tests too: a duplicate test or a payment run gate built from formulas runs on every row, as long as the formulas are locked and the file is controlled.
The concepts are the same in the UK and the US. US teams working under SOX often use the terms "automated control", "manual control" and "IT-dependent manual control" in their control documentation. UK teams use similar language under their own audit and internal control frameworks.
Supplier statement to AP ledger. Finds invoices you haven't posted, credit notes still to come, price differences, duplicate postings and payments in transit, and builds the supplier reconciliation. Runs in your browser on your own computer: nothing is uploaded.
Paste your invoice list and see likely duplicates in minutes. Free Excel file: enter your work email to download it.
The Accounts Payable Control System runs four duplicate-invoice tests, supplier master fraud checks and a three-way match on every invoice, with a payment run release gate that blocks release while exceptions are open. Excel, no macros, one-time price.
No. They are consistent and cover every transaction, but they cannot use judgement or contact a supplier. Most strong AP processes combine automated detection with manual review and decisions.
Usually by checking the set-up, confirming the rule works on a test case and reviewing change controls over the system. Manual controls are usually tested by sampling across the period.
A control where a person reviews a report produced by a system, such as an exception report. The report and the review both need to be reliable.
Last updated 11 November 2026. General guidance for finance teams; check it against your own policies, systems and local rules.