Duplicate payment detection
Duplicate payment detection checks every payment before it is released. Payments that match an earlier one on account holder, transaction, case and person are held for review instead of paid, which protects public and company funds and saves the work of recovering money after the fact.
See the PERKESO case studyWhat it does
Pre-payout matching
Each payment is compared with earlier ones before release.
Hold for review
Suspected duplicates are held with the matching record shown.
Database-level rules
Checks run as data rules, so no payment path can skip them.
Common questions
How are duplicate payments caught before payout?
Every payment is checked against earlier payments on account holder, transaction, case and person. A match holds the payment for review.
What happens to a held payment?
A finance officer sees the matching record and either releases or cancels the payment, and the decision is logged.
Can a payment skip the check?
No. The checks are enforced as data rules, so every payment path goes through them.
Have a process you want to automate?
Tell us how the work runs today. We will reply with the next step and a quote in RM.