Vendor Master
Monitor vendor master changes that precede suspicious payments.
- Ledger + 2 client documents
- Key analysis in Purchases & payables
How the result is read
Change the IBAN, let a payment go out, change it back — the footprint is in the change log, not the GL. The reversion is what distinguishes the pattern from an ordinary banking update: a test that stops at change-then-payment finds every legitimate change a supplier ever notified. The same shape applies to a name, address or tax identifier altered around a payment, and to a vendor created, paid and blocked inside one period.
The worksheet, on the demo engagement
Vendor Master, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per change to a payment-relevant field.
- IBAN change to pay
- 4
- Employee-vendor
- 2
- SoD
- 5
Click Orion to open cross-module fraud-pattern view.
Result grid4 rows
| Vendor | Exception | Detail | Flag |
|---|---|---|---|
| Orion Supplies | IBAN change + pay | IBAN changed 2024-12-18; paid 6,400 on 2024-12-22 | change-pay 4 days |
| Cedar Office | Employee match | shares IBAN with employee R.Kahn | employee-vendor |
| Summit Tools | Reactivated | Inactive 2y then Active 2024-11; paid 1,900 | reactivated |
| Orion Supplies | SoD | created_by = R.Kahn; first invoice by R.Kahn | no segregation |
In the application
Vendor Master is filed under Purchases & payables, index letter D. "Run all analyses" runs it with every other analysis the ledger and the documents loaded can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under D, beside an index of the source files with their SHA-256 fingerprints.
Also listed in the application as Duplicate Vendor Master
.
Read it with
Run your next audit file test without the Excel crash.
One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.
- 20 minutes
- Runs on a fictional engagement
- No client data required