AP fraud detection: the short answer
AP fraud detection checks invoices, vendor changes and payment runs for signs of fraud or error before the money goes out. The software worth shortlisting catches duplicates, bank-detail change scams, fake vendors and split invoices, explains every alert and fits your approval workflow. AI improves the catch rate on the variants that fixed rules miss, but people still decide what is fraud and who gets paid.
When Accounts Payable Fraud Detection is appropriate
Dedicated fraud screening pays off once AP handles enough vendors and invoices that no one person knows them all: several entities, a shared service centre, frequent vendor onboarding or regular payments abroad. It also makes sense after a near miss, such as a bank-change request that was caught by luck. A very small AP team paying a stable set of suppliers often gets more from tight approvals and call-back verification than from new software.
When AI-Powered AP Fraud Detection is appropriate
Rules handle the exact cases well: identical invoice numbers, missing approvals, payments over a limit. AI is worth adding when the misses come from variants.
| Signal | A fixed rule catches | AI also catches |
|---|
| Duplicate invoices | Same vendor, number and amount | Swapped characters, extra suffixes, same invoice under a second vendor ID |
| Bank-detail changes | Any change, flagged equally | Changes unusual for that vendor, timed before a large payment |
| Fake vendors | Missing tax number | Address, phone or bank account shared with an employee or another vendor |
| Split invoices | None, unless thresholds are hard-coded | Several invoices just under an approval limit within days |
| Price and quantity | Mismatch against the order | Prices drifting above the vendor’s own history or contract |
Fraud types accounts payable software should catch
| Scheme | Red flags | Check that stops it | Data needed |
|---|
| Duplicate invoice | Same amount and date, near-identical number, resubmitted PDF | Fuzzy match against paid and open invoices across entities | Invoice history for every entity |
| Bank-detail change (business email compromise) | Change requested by email, urgency, new bank country, change shortly before a payment | Call-back on known contact, dual approval, hold on first payment | Vendor change log, payment schedule |
| Fictitious vendor | No purchase history, PO box address, bank account shared with an employee | Vendor-to-employee matching, onboarding verification | Vendor and employee master data |
| Look-alike vendor | Name one letter away from a real supplier, new domain | Name and domain similarity checks at onboarding | Vendor master, email domains |
| Split invoice | Several invoices just under an approval limit | Aggregate by vendor and period against limits | Invoices and approval matrix |
| Price or quantity inflation | Unit price above contract or history, quantity above receipt | Match against order, receipt and contract | Purchase orders, receipts, contracts |
| Kickback or collusion | One approver for one vendor, steady price creep | Approver-vendor concentration reports | Approval history |
The FBI’s public service announcement on business email compromise recommends using secondary channels or two-factor authentication to verify requests to change account information (verified October 2026). Build that into the vendor change process itself, not just the fraud tool.
How AI fraud detection works in accounts payable
- Fuzzy duplicate matching compares invoice numbers, amounts, dates and line items with tolerance for small differences, across every entity and vendor ID.
- Behavioural baselines learn what is normal for each vendor, such as typical amounts, frequency and bank country, and score departures from it.
- Entity resolution links records that describe the same company or person even when names and addresses are written differently, which exposes vendor-employee overlaps.
- Document reading extracts invoice content and checks it against the order, receipt and contract rather than trusting the header fields.
- Explained alerts state which signal fired, show the records behind it and estimate what payment would be stopped.
The last point matters most for buyers. An alert without its evidence just moves the investigation work to someone else.
AP automation providers that advertise fraud detection
Vendors fall into four broad categories. The examples below are based on each vendor’s own product pages (verified October 2026); we have not tested these products, and inclusion is not a recommendation.
| Category | What it does | Examples and what they state |
|---|
| AP automation suites with built-in detection | Fraud checks inside the invoice-to-pay workflow | Medius describes anomaly detection for supplier address or bank changes and duplicate payment detection; Tipalti describes an AP agent and flags possible duplicate bills |
| AI spend and invoice audit | Reviews invoices before payment, often alongside an existing AP system | AppZen describes AI agents built from AP work instructions and flagging of duplicate invoices and unusual requests |
| Vendor bank account validation | Verifies that a bank account belongs to the vendor and monitors payment files | Trustpair describes account validation across many countries and flags suspicious changes before payment release |
| Governed agents on your own infrastructure | Custom detection agents over ERP data you already hold, with your approval flow | Platforms such as VDF AI, where you define the scenarios, thresholds and reviewers |
Many companies combine categories: an AP suite for workflow, a validation service for bank details and an audit layer for cross-system checks.
Controls checklist for AP fraud
- Verify every vendor bank-detail change by calling a contact already on file, never one supplied in the request.
- Require a second person to approve vendor master changes, separate from whoever processes invoices.
- Hold the first payment to any new or changed bank account for review.
- Screen all invoices, not a sample, for duplicates across entities before each payment run.
- Match vendor bank accounts, addresses and tax numbers against employee records.
- Aggregate invoices by vendor and period to expose splitting under approval limits.
- Reconcile payment files against approved invoices immediately before release.
- Review dormant vendors regularly and deactivate those without recent activity.
- Log every alert, decision and rule change, and have internal audit retest them.
These map to control activities and monitoring in the COSO internal control framework; the tool supports the controls, it does not replace them.
Questions to ask in a vendor demo
- Run the detection on a year of our historical invoices and vendor changes: what does it flag, and how many alerts are false?
- Which signals are fixed rules and which are learned, and can we see why a specific alert fired?
- Can it compare across all our entities and ERPs, or only within one?
- What happens to a held payment, and who can release it?
- Where does our payment and vendor data go, and is it used to train models for other customers?
- How are detection rule changes approved and logged?
Designing the operating workflow
- Screen on arrival. Each invoice and vendor change is scored when it enters AP, not on payment day.
- Group alerts. Related alerts for the same vendor or payment become one case.
- Investigate. An investigator reviews the evidence and confirms, clears or escalates the case with a reason.
- Hold or release. Confirmed cases hold the payment through the approval route; cleared ones release normally.
- Pre-run check. Before each payment run, the agents re-screen the proposal for recent bank changes and duplicates.
- Learn. Dispositions feed threshold tuning, and new scenarios go through internal controls approval.
Data, integration, and evidence
| Evidence item | Produced by | Used for |
|---|
| Alert with triggering signal and linked records | Detection agents | Investigation |
| Vendor change history with requester and approver | Vendor master log | Bank-change verification |
| Disposition and reason | Investigator | Audit trail and tuning |
| Rule versions with owner and approval | Internal controls | Control testing |
The NIST AI Risk Management Framework is a useful reference for documenting what the detection models are meant to do and how their performance is monitored.
How VDF.AI supports this use case
VDF AI Agents run on-premises, in a private cloud or air-gapped, so invoices, vendor records and payment files stay inside your environment. Agents read ERP data through the read-only SQL tool, score outliers with the anomaly detection tool and route held payments to a named approver with the human approval request tool. Role-based access control separates who can change scenarios from who investigates, and audit logs record every alert and decision.
For the payables process around this, see the AI accounts payable agent for approvals and ERP-ready items, the AI invoice processing agent for capture and matching, and the related invoice matching and AP automation, expense policy compliance and vendor onboarding use cases in the finance use-case collection.