Every AI use case, mapped to the business.

32 use cases owners are being sold this year, sorted by where they act in a business of 5 to 100 people. Only 3 are proven in production.

Status
Pick a room to see its use cases
How we rate

Four statuses, one rule: rate the evidence, not the pitch.

Each entry gets a status for how proven it is in businesses of 5 to 100 people, and a separate rating for how strong the evidence behind that status is.

Evidence strength

StrongSeveral independent studies or large independent surveys.
ModerateAt least one independent study or credible survey, plus consistent case evidence.
ThinA handful of independent data points.
Vendor claimsOnly what sellers publish about their own products.

How an entry is made

Each entry is drafted from public sources: academic studies, regulators, independent surveys and reputable reporting. Every figure carries a numbered citation you can open. Anything a vendor says about its own product is labelled as a vendor claim.

Review and updates

Every source in this edition was opened and checked against the text in October 2026. Each entry is then signed off by a named operator and re-checked when the evidence moves. Until that sign-off, the entry is marked as a draft at the top of the page.

The full guide

All use cases at a glance

Field GuideRisk, compliance & securityDuplicate-payment detection

Duplicate‑payment detection

Also called duplicate invoice detection, double payment checks, AP recovery audit

EvidenceModerate
ClassAnalytics

Duplicate-payment checks match bills on supplier, amount, date and reference. Audits show they recover real money; the case for AI is weaker.

ReviewDraft, awaiting operator review
Drafted27 October 2026
Fact-checkedEvery source opened, October 2026
Key takeaway

Duplicate payments are real and recoverable, and data matching finds them. The Cabinet Office's National Fraud Initiative identified 819 duplicate payments worth about £11 million over 2022 to 2024 and recovered 93%⁠. Of 237,261 invoices a US city processed in two years, its auditor flagged 5,249, followed up 204 and confirmed 50 duplicates worth $5.76 million⁠, which shows how much checking a flag list takes. We found no independent study showing AI matching beats well-set rules. Start with the checks already in your software.

At a glance

StatusIn production
What it doesCompares bills and payments on supplier, amount, date and invoice reference to flag likely double payments before they go out, or to find ones already made.
Typical costVaries by vendor; basic duplicate warnings already ship in some accounting and approval tools⁠, and some bookkeeping tools sell it as an add-on⁠
Data it needs12 to 24 months of bills and payments with supplier, invoice number, date, amount and bank account, plus a clean supplier master file.
Setup effortLow: switch on the checks in existing software; Medium if you also run a historical look-back sweep.
EvidenceModerate. Public-sector audit and data-matching results, the ACFE fraud survey and one university project; AI-matching claims come from vendors.

What is duplicate-payment detection?

Duplicate-payment detection checks your bills and payments for the same obligation paid twice. Some duplicates are fraud, but audits find plenty of plain errors⁠:

  • the same invoice posted twice
  • small differences in invoice numbers
  • a supplier set up twice in the system
  • a payment sent to the wrong supplier and then again to the right one

It runs at two points. Before payment, a check warns a bookkeeper or approver that a new bill looks like an existing one. After payment, a sweep looks back over months or years of transactions to find money to recover. Some tools describe the matching as AI. In practice the core is comparison rules on supplier, amount, date and reference, sometimes with a tolerance to catch near-identical entries⁠.

How does it work?

The simplest check compares each new bill with existing ones. One approval tool flags a bill when supplier, date and exact gross amount match, or when supplier and reference match, and warns rather than blocks⁠. Another compares contact, date and value within a date window, set by default to five days either side⁠.

A historical sweep applies looser rules across the whole ledger. A US city auditor flagged invoices over $500 with the same amount, date and vendor but different invoice numbers, plus invoices with the same number and amount paid to different vendors⁠. It then followed up 204 of them with departments to confirm⁠. Machine-learning approaches add anomaly scores: a university student project on a payables department handling more than a million invoices a year flagged over 53,000 potential anomalies and duplicates for review⁠.

Every method ends the same way: a person checks the flag against the supplier statement and asks for a credit or refund.

What it needs to work

Detection depends on clean, consistent bill and payment records in one ledger. If suppliers exist twice or invoice numbers are optional, no tool will match reliably.

  1. All supplier bills captured in the accounting system, not paid directly from email or a banking app
  2. Invoice number, supplier, date, gross amount and currency filled in on every bill, with one consistent format for invoice numbers
  3. A deduplicated supplier master file: one record per supplier, with company registration or VAT number and verified bank details
  4. Bank feed connected and reconciled monthly, so payments can be matched to bills
  5. At least 12 months of history for a first look-back sweep, two years if available
  6. A named person who works the flag list every payment run, and a standard request to suppliers for credits or refunds

Most use cases in this guide succeed or fail here, on the data underneath them, before any AI is involved.

What does the evidence show?

Independent evidence that duplicates exist and can be recovered is solid, though most of it comes from the public sector. The Cabinet Office's National Fraud Initiative data matching identified 819 duplicate payments worth about £11 million over 2022 to 2024, recovered £10.3 million and corrected or removed 548 duplicate supplier records⁠. Richmond, Virginia's auditor confirmed 50 duplicates over two years, including a $5.09 million wire processed twice; 26% of the duplicates were paid without a purchase order⁠.

For small firms, the ACFE's 2024 fraud survey found billing fraud in 31% of cases at organisations with under 100 staff, against 22% at larger ones⁠. Proactive data monitoring was associated with median losses of $100,000 against $200,000 and schemes lasting 9 months against 18⁠. The 2026 edition, covering 2,402 cases, again links anti-fraud controls with lower losses⁠.

We found no independent study showing AI or machine-learning matching outperforms well-set rules.

Exact-match rules vs fuzzy or AI matching

Compared onExact-match rulesFuzzy or AI matching
What it catchesSame supplier and reference, or same supplier, date and amount⁠Near-identical references⁠ and unusual patterns⁠
Error profileMisses near-duplicates; flags recurring fixed bills⁠Long review lists; one project flagged over 53,000 items⁠
Cost modelOften included in accounting or approval software⁠Add-on subscription⁠ or a recovery audit; varies by vendor
Best forEvery small business, at the point of bill entryAnnual look-back sweeps, several entities or high bill volumes

Status and evidence

StatusIn production
Evidence strengthModerate

Rated production for rules-based duplicate checks: government audits and data-matching programmes show measurable recoveries⁠, and duplicate warnings ship in common small-business accounting and approval tools⁠. Evidence is moderate: the results are mostly public-sector, and the ACFE data covers fraud broadly rather than duplicates⁠. The claim that AI matching beats rules rests on vendor material only⁠.

Where does it go wrong?

  • Too many flags. Loose rules on a busy ledger produce long lists: one city audit flagged 5,249 invoices to confirm 50 duplicates⁠. If nobody works the list, the check is decoration.
  • Recurring bills flagged every month. A user of one accounting package's built-in review reports a fixed monthly bill with no invoice number being flagged each month⁠.
  • Exact-match rules miss near-duplicates. An invoice keyed as INV-1043 and as 1043, or a supplier set up twice, can slip past a check on exact reference⁠.
  • Bank transactions left out. One tool excludes bank transactions from its duplicate check by default, and warns that including them may significantly increase flags⁠.
  • Payments outside the system. Duplicates paid without a purchase order bypass preventive checks such as invoice matching⁠.
  • Slow discovery. One vendor says some organisations take up to two years to find duplicates⁠, by which time the supplier may dispute the refund.

Numbers it should move

Possible duplicate paymentsSupplier payments that look like the same bill paid twice.
Creditor daysHow long you take to pay suppliers, on average.
13-week cash viewWhat the bank balance is likely to do over the next quarter.

Ask the demo business

Northgate Supply is a fictional wholesale distributor of catering and packaging supplies: 28 staff, R46.6m in sales over the last year. Its data is generated for this demo, to 30 September 2026.

Fictional data
Have we paid any supplier twice?
2pairs to check

2 pairs of payments go to the same supplier for the same amount within two weeks, worth R216 436 in total. The references differ only in punctuation, which is how duplicates usually slip past a manual check.

Harbour Packaging
INV-20882 paid 27 Apr, INV20882 paid 30 Apr
R76 655
Granite Hygiene
INV-21456 paid 27 Jul, INV 21456 paid 4 Aug
R139 781
How this was worked out

Compares every pair of supplier payments made within 14 days of each other, flagging the same supplier and the same amount to the cent.

Answered in 1 msScanned 254 rowsFrom supplier payments
Want this on your own numbers, in the AI tools you already use?Book a demo

Where the data usually lives

XeroSage Business Cloud AccountingSage Pastel / EvolutionQuickBooksBank feedsEmail inboxes

Where the records this use case needs are usually kept in a small business. It is not a list of recommended tools.

Frequently asked questions

How common are duplicate payments in a small business?

We found no reliable independent rate for small firms. Public-sector audits show the scale in larger bodies: the UK's National Fraud Initiative found 819 duplicates worth about £11 million in two years⁠, and one US city confirmed 50 duplicates out of 237,261 invoices⁠. Separately, the ACFE found billing fraud in 31% of cases at organisations with under 100 staff⁠.

How much does duplicate payment detection software cost?

Basic checks may already be in tools you pay for: one approval add-on warns on matching supplier and reference⁠, and users of one accounting package describe its built-in duplicate bill review⁠. Some bookkeeping tools charge for it as an add-on⁠. Specialist recovery audit pricing varies by vendor. Check what you already have before buying anything new.

Do I need a developer to set up duplicate payment checks?

No. Built-in checks are switched on in settings, and approval add-ons connect to the accounting package⁠. A one-off historical sweep can be done in a spreadsheet: export two years of bills, sort by supplier and amount, and look for matches within a few days of each other. A bookkeeper or accountant can run it.

Is AI better than rules at catching duplicate invoices?

Not proven. We found no independent study comparing them. Vendor commentary says inconsistent invoice coding caused 75% of duplicate payments in one federal department's audit, the kind of near-match these tools target⁠. Machine-learning projects can surface unusual items, but one flagged over 53,000 for review⁠. For a small business, clean supplier records and the rules already in your software are the place to start.

What should I do when I find a duplicate payment?

Confirm it against the supplier statement, then ask the supplier for a refund or a credit against the next invoice. Recovery is usually possible: the UK's National Fraud Initiative recovered 93% of the value of the duplicates it found⁠. Fix the cause too, whether a duplicate supplier record, a missing invoice number or a payment made without a purchase order⁠.

More in risk, compliance & security

Sources

  1. 1
    Occupational Fraud 2024: A Report to the Nations
    Association of Certified Fraud Examiners (copy hosted by Ivey Business School), 2024Survey
  2. 2
    Occupational Fraud 2026: A Report to the Nations
    Association of Certified Fraud Examiners, 2026Survey
  3. 3
    National Fraud Initiative Report 2022 - 2024
    Cabinet Office and Public Sector Fraud Authority, 2025Government
  4. 4
    Continuous Monitoring – Duplicate Payments (OCA 2026-09)
    City of Richmond Office of the City Auditor, 2026Government
  5. 5
    How automated duplicate payment detection helps governments recover lost funds
    Route Fifty (commentary by an apexanalytix executive), 2025Vendor
  6. 6
    UR Accounts Payable: Automating Accounts Payable Anomaly and Duplicate Detection
    University of Rochester Goergen Institute for Data Science, 2025Study
  7. 7
  8. 8
    Using the Duplicate transactions check
    Dext Help Centre, 2026Vendor
  9. 9
    Bills - Duplicate bill review
    Xero Product Ideas (user forum), 2026Vendor
  10. 10

This entry is educational. It is not legal, financial or professional advice, and it does not recommend any vendor. Figures attributed to vendors are their own claims.

Ask your own business. Get the true number in seconds.

Veld connects your accounting, sales and operations data to the AI tools you already use, and keeps it running, so every answer comes from your numbers.

Book a demo