Ideas, insights and practical guidance

Accounts payable is often introduced as a basic concept in accounting: a current liability representing amounts owed to suppliers. That definition is correct, but it is incomplete in the way most finance teams experience AP.

Vendor onboarding can look simple until it becomes urgent, and vendor onboarding for accounts payable is often where long-term issues begin. Someone needs a new supplier today, details arrive via email and PDFs, and accounts payable is expected to set the record up fast, with no mistakes. In many organisations, that leads to duplicate vendor records, invoices stuck in exceptions, payment reissues, and controls that are hard to defend when an audit asks, show me how this was approved.

For most finance leaders, the question isn’t whether AP automation is a good idea in principle. It’s whether the investment still makes sense once you account for implementation effort, process change, and the messy reality of approvals and exceptions.

Accounts payable on the balance sheet appears as a current liability, representing supplier invoices that have been recognised as owed but not yet paid. That is the accounting answer, and it is correct. The operational challenge is that the AP number depends on what has been processed and posted by the reporting cut-off.

Most finance teams don’t automate accounts payable because they want a new system. They do it because the current process becomes harder to defend, harder to scale, and harder to manage each year.

The real differences show up in how AP and AR behave operationally, who controls the timing, where the risks sit, and what good looks like when you zoom out beyond processing.