
Accounts payable automation captures each vendor bill when it arrives, checks it against what was ordered and received, routes it to the person who approves it, and schedules payment by its due date. It also holds any change to a vendor's payment details until a person confirms the change through a second channel. A person approves the payment and every payment-detail change.
This article walks through those steps and the one control that matters most, using two FBI Internet Crime Complaint Center (IC3) sources. It is not legal, accounting, or banking advice.
The Papers a Bill Touches
A vendor bill is one document in a short chain. Knowing the chain is the first step in automating it:
- The vendor bill, which arrives by email, mail, or a vendor portal. - The purchase order, where your business uses one. - The receiving record, which shows what actually arrived or what work was done. - The approval, from the person who knows whether the bill is right. - The payment, on or before the due date. - The vendor's payment details on file, which is where the money goes.
Receivables is the other side of this. Our article on invoice follow-up automation covers money owed to your business. This one covers money your business owes.
Capture, Match, Route, Schedule
Each step below is a fixed path, which is the kind of work a workflow handles well. Our piece on what an AI agent is explains why a task with steps you can list usually starts as a workflow, not an agent.
Capture. Vendor invoice capture means the bill is pulled into one place when it arrives, with the vendor, amount, date, and due date read from it, instead of sitting in an inbox. A person checks anything the system could not read clearly.
Match. The system compares the bill to the purchase order and the receiving record, and flags a difference: an amount that does not match, a quantity not received, a bill with no order behind it. Flagging is the job. Deciding whether the difference is acceptable is not.
Route. For bill approval routing, the system sends the bill to the right approver and keeps it moving. If the approver has not acted, it reminds them. Our article on approval workflow automation covers the general pattern of a decision waiting on one person. A vendor bill is one example, followed from arrival to payment.
Schedule. Once approved, the payment is scheduled against the due date, so approved bills are not forgotten. The person who releases payment still reviews the batch.
The same habit from our job shop article applies here. Before you automate a document, list where each piece of information in it comes from. See building the quote from scattered data.
Hold Payment-Detail Changes
This is the step to get right if you do nothing else. The FBI's IC3 defines business email compromise (BEC) as a scam targeting businesses or individuals working with suppliers and businesses that regularly perform wire transfer payments. It is carried out by compromising email accounts and other forms of communication, such as phone numbers and virtual meeting applications, through social engineering or computer intrusion, to make an unauthorized transfer of funds.
A request to change where a vendor gets paid is exactly where that scam lands. IC3's 2025 annual report lists BEC at 24,768 complaints and $3,046,598,558 in complaint losses for 2025. Those figures are all complaints reported to IC3 by businesses and individuals. They are not small business losses, and they are not accounts payable losses. IC3's September 2024 public service announcement says BEC continues to target small local businesses and larger corporations, as well as personal transactions.
Its recommended prevention tips include using secondary channels, two-factor authentication, or both to verify requests for changes in account information. It also advises checking that the URL in an email belongs to the business it claims to come from, and that the sender's address appears to match who it is supposed to be from.
In practice, that gives you a rule an automated system can enforce:
- A request to change a vendor's bank or payment details is never applied from the email that asked for it. - The system flags the request and puts the vendor's payment on hold. - A person confirms the change by contacting the vendor on a channel you already had on file, such as a phone number from your records, not one in the request. - Only after that does the change go in.
IC3's AI section states that chat generators can quickly create official-sounding emails that mimic a company's CEO or other officials, and that there are multiple BEC tactics, not all of them AI-enabled. A request that reads well tells you nothing about whether it is real, which is another reason the check does not depend on how the message sounds.
What Stays With a Person
Automation routes, matches, flags, and holds. A person approves the payment and every change to payment details. A person also handles the unusual cases: a bill with no order, a vendor disputing an amount, a request that feels off. That is how AI supports people instead of replacing them.
How to Start Small
Pick one vendor you pay every month. Trace its bill from arrival to payment and write down who touches it and where it waits. Then set the one control that costs the least to put in place: a second-channel confirmation for any change to payment details. Once that is working, add capture, then matching, then routing.
If you would like help mapping one payables path, get your free AI assessment.
Frequently Asked Questions
What does accounts payable automation do?
It captures vendor bills, checks them against orders and receiving records, routes them for approval, and schedules payment. A person approves the payment.
Can AI approve and pay vendor bills on its own?
We do not recommend it. A person should approve each payment and every change to a vendor's payment details.
How should a business handle a request to change a vendor's bank details?
IC3 recommends using secondary channels, two-factor authentication, or both to verify requests for changes in account information. Hold the change until a person confirms it that way.
Do the IC3 figures show how much small businesses lose?
No. They are complaints and losses reported to IC3 by all complainants, businesses and individuals, and they are not limited to small businesses or to accounts payable.

