Accounts Payable Automation Challenges: A Bookkeeper's View

Accounts payable automation removes the typing, not the judgement. Bills still need the right coding, clean cut-off and exactly one payment each. The software has got better; the failure points have simply moved. Here is where they sit now, and what we do about each one.

The work moves to the exceptions

Automation handles the clean invoice: known vendor, known number, matching amount. Everything else lands in a queue. Unreadable scans, price variances, new vendors and changed remittance details all wait for a person, and that queue is the job now.

Where purchase orders are in use, any variance stops the line. Without a written tolerance, the queue grows until people approve anything to clear it. Set a small percentage and amount threshold in policy, so trivial differences post themselves and real variances reach someone with time to look. Clear the queue weekly; a backlog at month-end becomes a cut-off problem.

How do duplicates still get through?

Duplicate detection keys on vendor, invoice number and amount. It fails in predictable ways. A supplier re-issues an unpaid bill as 1187R after a query, and the tool reads it as new. A monthly subscription bills the same amount with the same reference every month. One invoice arrives by email and again through a supplier portal, and both get ingested.

Sort the payment run by vendor before you release it, not by date. Duplicates sit next to each other that way. Reconcile the four or five largest suppliers to their statements every month. Statements catch what matching misses.

Default coding drifts quietly

Most tools code an invoice from rules stored against the vendor. That works until the vendor changes what it sells. A stationery supplier that starts billing annual software support will keep posting to office supplies until someone notices. The ledger stays tidy and wrong.

Give the mapping rules an owner and a review date. Clear the coding-holding account weekly, while the invoice is still fresh. At month-end, scan the largest accounts for anything that has grown faster than the business explains.

Does automation respect your cut-off?

Usually not without help. Tools commonly post on the approval date or the entry date, not the service period. An invoice dated the 28th for March service, approved on 4 April, lands in April. March is understated and nobody gets an error.

Make the unapproved-bills report a standing source in the close. Everything dated on or before period end, still sitting in a queue, is an accrual candidate. Review it with the same care as the bank reconciliation, because the automation will not flag it for you.

Approval evidence lives outside the ledger

The bill sits in the ledger; the approval sits in the tool. If anyone questions a payment later, the ledger alone will not answer. Export or attach the approval record with the period's working papers, or at least record where it lives.

Watch for approvals that happen outside the system. A manager replying "fine, pay it" by email leaves no trace in the tool. Agree the approval log to the bills posted each month. The gap between the two lists is where unapproved payments hide.

The vendor file is the control that matters

Duplicate supplier records produce duplicate payments and broken year-end reporting. Changed bank details are the standard fraud route, and automation can make the payment faster than anyone checks. Restrict who can edit the vendor file. Verify every bank detail change by phone, on a number you already hold, before the next run. Keep supplier statement reconciliations in the monthly cycle even though the invoices arrive automatically.

Switching tools turns into a migration

Changing AP systems moves open bills, history and attachments, and in our experience the two systems rarely agree on the way across. Before the switch, agree what history moves and what stays behind, and take a full read-only copy of the old data. After it, tie the opening payables aging to the closing balance of the old system to the penny.

If bills, attachments or histories arrive missing or doubled, that has stopped being bookkeeping. It is a data migration problem, and it belongs with a specialist before anyone posts corrections by hand.

A close checklist for automated payables

The month-end routine changes shape rather than shrinking. Standing items:

• clear the exception queue before you close, not after
• accrue anything dated on or before period end that is still unapproved
• agree the approval log to the bills posted
• reconcile the aging to the payables control account
• reconcile the major suppliers to their statements

None of that is typing. All of it is judgement, and judgement is the part automation was never going to take.