By Ammar Ashour
A convincing invoice is not proof that a payment belongs to the right person. To reduce exposure to AI assisted invoice fraud, verify the supplier, the underlying purchase, and any change in payment instructions before releasing money. Keep those checks in place even when an email sounds familiar or an automated system accepts the document.
For a small business owner or accounting team, the practical question is simple: what evidence must be present before this bill can be paid? This guide offers a suggested review process for United States businesses.
Why this matters for accounting teams in 2026
The FBI’s 2025 Internet Crime Report lists $3,046,598,558 in reported business email compromise losses (page 8). Its separate table of complaints with AI references lists $30,256,592 in BEC losses (page 42). These are complaint based figures for 2025, not estimates of all fraud. The overall BEC total must not be described as losses caused by AI.
The FBI has also warned that criminals use generative AI to produce persuasive messages, reduce spelling mistakes, and impersonate people through synthetic audio and video. That warning was issued December 3, 2024; it is background guidance, not a new announcement today.
The accounting implication is that clean writing and familiar sounding voices should not replace independent verification. The process needs to establish who is asking, what the business owes, and where the money will go.
What is AI invoice fraud?
In this article, “AI invoice fraud” means a payment deception in which AI helps make an invoice, supporting message, or impersonation more convincing. It is a descriptive term, not a separate category in the FBI statistics above. A fraudulent payment request can also involve no AI at all.
The FBI’s BEC guidance describes scams involving apparent vendors, altered payment instructions, and compromised email conversations. A real supplier name or an existing message thread therefore does not settle whether a new request is legitimate.
Seven checks before you pay
The following is a suggested accounting workflow, informed by the cited guidance. Adapt the responsibilities and approval thresholds to your business; it is not an official FBI checklist.
1. Confirm that the purchase belongs to your business
Find the purchase order, contract, or documented approval behind the bill. Ask the person who ordered the goods or service to confirm receipt or completion. If your business does not use purchase orders, record another clear basis for the obligation. A supplier logo alone is insufficient.
2. Reconcile the invoice details
Compare the supplier, invoice number, date, quantities, unit prices, and total with the supporting records. Investigate duplicate invoice numbers and unexpected charges. Keep unresolved items in a review queue. This check addresses the bill itself; it does not establish ownership of the receiving bank account.
3. Verify changed bank details independently
Treat a new account number or payment destination as a separate approval event. The IC3 recommends a secondary verification channel for account changes. Use a previously verified supplier contact or independently obtain the organization’s number. Do not rely on a phone number supplied in the message requesting the change. Record who confirmed it and when.
4. Check the request, even when the language looks right
Inspect the full sender address and reply destination. Pause when a message demands secrecy, introduces unusual urgency, or asks your team to bypass its normal process. The FBI advises particular caution with pressure to act quickly. Good grammar is not an approval control, and an incoming voice or video call should not override the verification process.
5. Separate preparing the payment from approving it
Where staffing permits, have one authorized person prepare the payment and another approve it. Show the approver the invoice, purchase evidence, payee, amount, and verification of any account change. For a very small team, involve the owner in reviewing exceptional payments and supplier changes before release. Document how that review occurred.
6. Keep AI suggestions separate from payment authority
For a pilot, let an approved tool organize invoice information or prepare an exception list, while authorized people decide whether to pay. A tool’s successful extraction of an amount should not authorize a transfer or a supplier record change. Test what connected systems can actually do; do not rely only on a written instruction to the assistant.
For the access layer, see AI Access to Accounting Software: A Practical Permissions Checklist. Review the provider separately using the AI Vendor Review for Accounting Firms.
7. Preserve the evidence with the payment record
Keep the original invoice, supporting purchase evidence, account change verification, approval, and payment reference together in your authorized system. Make unresolved exceptions visible to the person responsible for the payment run. A reviewer should be able to understand why the payment was approved without reconstructing the decision from scattered messages.
A hypothetical example: the invoice is right, the destination is wrong
A business expects a $4,800 supplier invoice. A message arrives with the correct amount and a request to use a new bank account. An automated review finds no arithmetic difference. That result only confirms the numbers it checked.
The reviewer holds the payment and calls the supplier using a previously verified number. The supplier says its bank details have not changed. The business escalates the suspicious request and verifies the legitimate payment route before proceeding. This is a fictional teaching example, not a client case or a claim about a particular AI product.
What if the payment has already been sent?
Act promptly. IC3 guidance says to contact the originating financial institution as soon as fraud is recognized and request a recall or reversal. File a detailed report with IC3. Preserve messages and transaction details for the bank and investigators. A recall request does not guarantee recovery.
One practical step for your next payment run
Choose one recent supplier account change and walk through its approval record with your team. Can you identify who requested it, how it was independently verified, and who approved the payment? Use any missing evidence to improve the process before the next payment run.
The goal is a payment decision your team can explain and support. AI may help prepare information, but the evidence should determine whether money moves.
Sources checked October 7, 2026. General educational guidance for accounting workflow planning, not a complete fraud prevention program. Cover image: AI generated editorial illustration.
