ACC-01 · FlowCount Assure

AP duplicate & anomaly detection

Catch the payment you already made.

اكتشف المدفوعات المكررة قبل أن تضيع

Pilot availableFor: Financial controller · AP manager · Internal audit

337,500

one invoice paid twice, found in the sample review

Basis: illustrative sample engagement (fictional data)

The problem

Duplicate and split payments leak cash quietly. When they go to non-residents, they leak WHT and VAT too.

“Same vendor. Same invoice. Paid twice. Two weeks apart.”

What FlowCount does

Duplicate, split and round-sum payments, and vendor-master anomalies, found with explainable rules.

AI and rules used
Rules; fuzzy matching; outlier models
Builds on
WHT Health Check data model

How it works

Who does each step

  1. 01Rules

    Exact and near duplicates

    Same vendor, invoice and amount; normalised invoice numbers (spaces, leading zeros, prefixes stripped); 30-day windows.

  2. 02Rules

    Patterns

    Same-day splits just under approval limits, round sums to non-residents, a resident flagged as non-resident, one bank account on two vendors.

  3. 03Reviewer

    Recover

    Recovery schedule and the control fix.

What you send

  • AP sub-ledger (the same extract as the WHT review)
  • Vendor master

What you receive

  • Anomaly register
  • Recovery schedule
  • Control-gap memo

Controls built in

  • Explainable rules only
  • Both occurrences flagged: order-invariant

KPIs we report

  • Recoveries in riyals
  • False-positive rate (target < 20% for near-duplicate rules)

Sample input → expected output

What the result looks like

Basis: illustrative sample engagement (fictional data)

Expected output: anomaly register
TestPayment refsVendorDetailAmount at riskAction
Exact duplicatePY-25-00688 + PY-25-00702SaaS Vendor IncInvoice INV-88213 paid 14-Sep-25 and 28-Sep-25337,500.00Recover from vendor; reverse WHT; strengthen AP duplicate check
Vendor masterPY-25-00790Riyadh Office Supplies CoSaudi vendor in non-resident populationCorrect residency flag

Portfolio scorecard

Where it sits on the roadmap

Value

2.80 / 5

Feasibility

4.75 / 5

Priority index

13.30 · rank 2 of 27

Quadrant

Fill-in

Delivery

Wave 1 (0-3 m)

T-shirt size XS: ≤ 2 weeks with 1 AI engineer + 0.25 tax SME, indicative build 25k to 50k. Rules on data an existing engine already produces. How we score and sequence →

Catch the payment you already made.

A pilot runs on your own data, under the full G0 to G7 gate model, with a partner signature on every conclusion.