Find the invoices you paid twice, paid too much, or never got credit for.
A fixed-price, two-week scan of your accounts payable data. You send one extract. I send back the evidence, the root causes and a fix list, so you see exactly where money is leaking and how to close the gaps.
AP leakage is money that leaves your business through duplicate, overpaid or uncredited supplier invoices. It is usually small per invoice, which is why it goes unnoticed.
Fixed price. Two weeks from a clean extract. No access to your systems.
- Paid twiceHarlow ComponentsINV-48213 in ERP A and INV-048213 in ERP B, six days apart. Each system saw one invoice.14,860.00
- Paid too muchNorthgate LogisticsInvoiced at 12.40 a unit against 10.90 on the purchase order, 800 units.1,200.00
- No credit appliedAldous FacilitiesCredit note CN-2291 was issued but never matched to an invoice, so it was never used.3,450.00
Services
AP Leakage Scan
A fixed-price, two-week analysis of your accounts payable data. It finds duplicate and overpaid invoices, price and receipt differences, unapplied credits and duplicate suppliers, then ranks the root causes of your invoice exceptions.
Works on any ERP. One read-only extract, no access to your systems.
What the scan checks
Deterministic matching on your extract. Every case gets an evidence line and a confidence level.
| Check | What it catches |
|---|---|
| Duplicate invoices | The same invoice entered twice, including leading zeros, prefixes and trailing letters, and the same amount inside a date window. |
| Across ERPs and entities | The same invoice number posted in two ERPs or entities, and the same invoice under two supplier records. |
| Price above PO | Invoice unit price above the purchase order price beyond your tolerance. |
| Quantity above receipt | Invoiced quantity above what was received. |
| Receipt controls | Paid before goods receipt, or paid with no receipt at all. |
| Unapplied credit notes | Credits from suppliers that never got applied to an invoice. |
| Supplier master data | Records that share bank details or a tax ID, and near-identical names. |
| Exception root causes | The hold reasons that cost the most time, ranked by count and days stuck, with the cause: supplier, buyer, receiving site or master data. |
What you get, and what you do
You send one extract per ERP, answer questions while I reconcile it, and join a 45-minute findings call and a 60-minute readout. I do the rest.
The sample uses synthetic data, so no real company appears in it.
- Findings workbookEvery candidate case with its evidence, the amount per currency and a confidence level.
- 10-page reportA clear summary for your AP, finance and audit teams: the totals, the ranked findings, the root causes and what to fix first.
- Root-cause ranking and fix listThe exceptions that hold invoices up longest, and what to change.
- Data reconciliation noteYour row counts and totals tied out before any analysis starts.
- Extract specificationA field list, sent after the NDA, that tells your ERP team exactly what to export.
- 60-minute readoutWalk through the results with the people who can act on them.
Two weeks from a clean extract
A clean extract is one whose row counts and totals reconcile with your figures. The clock starts that day.
Call
20 minutes. We check the scan fits your ERPs and volumes.
Sign
NDA, data processing agreement and a fixed-fee order, before any data moves.
Extract
You send a read-only export with bank details hashed. I tie its row counts and totals to your figures before any analysis.
Findings
Within 10 working days of a clean extract: you confirm or reject each priority case, then get the final workbook, report and readout.
Why you can rely on the numbers
- You confirm every caseOnly cases you confirm are reported as findings. The rest stay candidates.
- Evidence on every lineEach case shows the invoices, dates, amounts and the rule that matched them.
- Amounts stay per currencyNo conversions, so nothing is hidden in an exchange rate.
- Tested before it touches your dataThe method runs against a synthetic dataset with more than 300 planted errors and 40 look-alike traps. Real extracts are messier, which is why step one is reconciling your data.
Your data stays under your control
- Read-only extractI have no access to your systems and write nothing back.
- Your own secure shareReceived there, never by email.
- Processed on my own encrypted machine in the UKRows are never given to an AI service.
- Paperwork firstNDA and data processing agreement before any data moves.
- Deleted 30 days after deliveryWith written confirmation.
Fixed price
Launch rate, first three clients
£6,500 + VAT
In return for a case study you approve, and permission to use anonymised patterns. I run one scan at a time, so launch places go in order.
List price from the fourth client
£8,000 + VAT
- One ERP or several, up to 24 months and 300,000 invoices a year
- Workbook, 10-page report, readout
- Two weeks from a clean extract
Not ready for the full scan? After a first call I can run a smaller starter check on one entity and 12 months of data. It is credited against the full scan if you go ahead.
What it is not
It is an analytical review of your data, not an audit. It does not include supplier recovery claims, legal or tax advice, or any promise that money will be recovered. What it gives you is a documented, evidenced list of what to chase and what to fix.
The report relies only on the extract you supply and is for your internal use. Third parties should not rely on it.
If it finds nothing, you pay the fixed fee and you get a reconciled, documented answer that your AP controls hold, plus the exception root causes.
Questions
We already have an AP tool that checks duplicates.
A check inside one system cannot see an invoice posted in another. The scan matches across ERPs, entities and supplier records, and ranks what causes your exceptions.
What do you need from us?
One read-only extract per ERP covering 24 months, a named data owner, and your time for a 45-minute findings call and a 60-minute readout. The extract specification lists every field.
How long does it take?
Two weeks from receiving a clean extract. A clean extract means your row counts and totals reconcile, or the differences are documented.
Is our data safe?
You send a read-only extract through your own secure share, with bank account numbers hashed. I process it on my own encrypted machine in the UK, and it is deleted 30 days after delivery with written confirmation. An NDA and a data processing agreement come first.
Which ERPs does it work with?
It is built for any ERP extract. I map your column headers to the scan's fields, so there is no connector to install. On the first call we confirm that your ERP can export the fields the scan needs: invoice and supplier details, PO price and quantity, and goods receipt.
Who runs it
I am Laszlo van Ginkel, an ERP consultant with a background in Oracle applications, working across commercial companies and large public-sector organisations. I am independent of any software vendor, so the scan reports what your data shows, not what a platform sells.
Book a 20-minute call
Tell me which ERPs you run and roughly how many invoices you process a year. I will reply within one working day.
Email laszlo@lvgconsultancy.com
Or download the sample report first.