Payments · the run validator13
Every payment run, someone hunts the anomalies.
🛡 Payment Run ValidatorLocal desktop app · deterministic reconciliation · v1.0 ● Offline
Validate a payment run
Pick the payment-run file and the vendor history to reconcile against. Everything runs on this machine.
▤ Payment run filepayment-run-2026-06.xlsx Browse…
▥ Reconcile against historyvendor-payment-history.xlsx Browse…
🔒Runs on your machine — no data leaves this computer, and nothing is sent to a model.
Run reconciliation →
Deterministic checks — rule-based flags, not a model score. Every finding is explainable.
High Bank account changed vs history Vendor A07 · was …4412, now …9981 — no prior payment to this account.
Warn Step-up payment Vendor A07 · this line is 3.2× the vendor's historical average payment.
Warn Possible duplicate Same invoice ref INV-5520 appears on two lines in this run.
Info Amount outside historical band Vendor B14 · above the vendor's usual range, but within tolerance.
✓ Bank account matches history · amount within band — 320 lines
✓ No duplicate invoice refs · no other anomalies — 121 lines
Audit trail — recorded automatically with every run
Files validated · SHA-256
payment-run-2026-06.xlsxa3f1c…9e22input hash
vendor-payment-history.xlsx7b0d4…1f88input hash
Run by · when
Deepak Sharma · Senior GM Finance · 09 Jun 2026, 14:32 IST
Result
1 high · 2 warnings · 1 info · 445 lines reconciled, 441 matched · 4 flagged for review
🔗Tamper-evident — change any input and the hash changes. You know exactly which file was validated.
Audit report · payment-run-2026-06.pdf
Payment Run — Validation Reportpayment-run-2026-06.xlsx · reconciled against vendor history
Hash
verified
Run summary
445
lines checked
1
high anomaly
2
warnings
441
clean matches
Anomaly findings
Bank account changed — Vendor A07 · …4412 → …9981 High
Step-up payment — 3.2× historical average Warn
Possible duplicate — invoice ref INV-5520 ×2 Warn
Amount outside band — Vendor B14, within tolerance Info
441 lines matched history — no action OK
Audit trail
Run by Deepak Sharma · Senior GM Finance · 09 Jun 2026, 14:32 IST
payment-run-2026-06.xlsx · SHA-256 a3f1c…9e22
vendor-payment-history.xlsx · SHA-256 7b0d4…1f88
Deterministic · ran locally · no data sent to any model.
⏱Per-approval check: 30–40 min → ~5 min — and hash-verified, so the control is stronger, not weaker.