Stopping the payment before the wrong IBAN is used
A finance shared-services centre paying supplier invoices against purchase orders, after an attempted invoice-redirection fraud.
Who they are.
A finance shared-services centre paying supplier invoices for a group of operating companies. Three-way matching — invoice, purchase order, delivery note — was done by eye, at volume, under month-end pressure.
Anonymised at the client’s request. Client names are never disclosed without written permission.
What had to be solved.
An attempted invoice-redirection fraud made the weakness explicit: a changed IBAN on a familiar letterhead looked exactly like a legitimate update, and nothing compared it to the supplier master record. Duplicate invoices were found during reconciliation, after payment.
What success looked like.
- Match amount, quantity and bank details across all three documents
- Stop a bank-detail change from passing as a routine update
- Catch duplicates at intake rather than at reconciliation
What Ceertia does here.
A use case for supplier payments that reconciles the three documents and checks the invoice IBAN against the supplier master record. A difference does not fail the invoice — it holds it for a person to look at, with both values cited.
The IBAN on the invoice must match the IBAN held in the supplier master record; any difference holds the payment for human review.
How it runs, step by step.
The file arrives with its documents, in any format, from whoever sends it.
Every page is identified and mapped against the expected document list. Missing documents, duplicates and out-of-scope pages are flagged on receipt.
Each rule asks the file a question and answers it directly on the documents, with page, zone and source text attached to the verdict.
The team approves, requests a fix, or rejects. No file is approved or rejected automatically.
What changed.
One redirection attempt was stopped before payment. Duplicates now surface at intake, and month-end closes without the reconciliation surprises that used to define it.
- Three-way matching was done by eye, at volume, under month-end pressure.
- A changed IBAN on a familiar letterhead looked exactly like a legitimate update.
- Duplicate invoices were found during reconciliation, after payment.
- Amount, quantity and bank details are matched across invoice, order and delivery note.
- A bank detail that differs from the supplier master record stops the file.
- Duplicates are caught at intake, not at reconciliation.
Anonymised case. Client names are never disclosed without written permission. Figures describe the file volumes and checks in this scenario.
Other files, same engine.
A consumer lender whose analysts spent the first twenty minutes of every file confirming that the documents agreed with each other.
Read the case → ComplianceA KYC refresh campaign that finishes on timeA financial institution required to refresh know-your-customer files across its corporate book, with documents expiring on eleven thousand different dates.
Read the case →See it run on your own files.
Bring one real file to a 30-minute demo. Watch the verification run, evidence on screen.