Interactive demo · no login
A supplier’s bank details changed. See what happens.
This is the product, not a video of it. An ERP payment file has arrived, one line is going somewhere it should not, and you are the approver. Three clicks, start to finish. Follow the bar along the bottom.
What you just saw
Four controls, none of which depend on somebody being careful.
01
The check happened before anyone looked
Halstead’s account did not match the vendor master, so Capallo held that line at ingest. Nobody had to notice. Nobody had to remember to look.
02
The person who prepared it could not approve it
Sofia built the run and is blocked from approving her own work. The same split is enforced again at execution, and again at reconciliation, by different people each time.
03
The held line was cut out, not flagged
On release the instruction is removed from the pain.001 itself and both control totals are rewritten. The bank receives four payments. There is no queue of warnings somebody has to work through.
04
And it can be proved afterwards
The excision is sealed against the original file. Two digests, a line-by-line account of what was removed and why, and a chained audit event that still verifies. That is what an auditor asks for.
Want to see it against your own payment file?
Send a real pain.001 and we will run it through and show you what it catches. Calder Industrial Group is fictional. The controls are not.
Book a conversation