Automating Accounts Payable Without Losing Control

Most AP automation projects die the same way. Someone buys a tool, the finance lead realizes approvals now happen somewhere they can't see, and within a quarter everything is back in a shared inbox. Nobody decided what the controls were first.

AP is five steps: capture, code, approve, pay, sync. Four are machine work. Exactly one — approve — stays human, and it should get sharper when you automate everything around it.

Capture: end the forwarding chain

Give AP one dedicated email address and put it on file with every vendor. Bills land there, OCR pulls vendor, invoice number, date, and amount, and a draft bill appears in QuickBooks with the source PDF attached. Bill.com, Ramp, and Melio all do this competently. An approval you can't trace back to the document is theater.

Coding: rules, not memory

Ninety percent of your bills come from the same forty vendors and hit the same accounts every time. Encode that. Vendor-level defaults for account, class, and location mean your clerk reviews a pre-coded bill instead of typing one.

Route the rest by exception: new vendor, unused GL account, amount 20% above trailing average, no matching PO. Those get a human. Everything else gets a glance.

Automation should cut the number of decisions, not the thinking behind them.

Approval: where control lives

• Thresholds. Under $500 against an approved vendor and open PO clears itself. $500 to $5,000 needs a manager. Above that, finance.
• Separation of duties. Whoever enters a bill can't approve it. Whoever approves can't release payment.
• Delegation and SLAs. An approver on vacation escalates after 48 hours instead of stalling the run.
• An immutable trail. Who approved, when — attached to the bill, not in someone's sent folder.

Payment: batch it, then verify it

Run payments on a schedule. Twice a week beats ad hoc — ad hoc means whoever emails loudest gets paid first. Batch by due date, then let the tool pick ACH, check, or virtual card.

One control is non-negotiable: never change vendor bank details from an email. Business email compromise is the most expensive fraud hitting midsize AP, and it always arrives as a polite remittance update. Call a number you already had.

Sync: one system of record

Bills, payments, and credits flow back to QuickBooks automatically, with duplicate detection keyed on vendor plus invoice number. If the AP tool and the GL disagree, you maintain two sets of books and a monthly argument.

If someone still retypes a bill, you bought software and kept the job.

We design the controls first, then build the pipes — see Workflow Automation and Bank & App Connections.