Home   |  Current News & White Papers  |  Payment Systems Blog  |  Contact CONIX 

Home > Products> Dupe Detective Frequently Asked Questions

Duplicate Payment Prevention with Dupe Detective™

Learn More
How We Stop Duplicate Payments

How Dupe Detective Stops Duplicate Payments
  • Will I be able to identify duplicates in my outgoing cash letters before they are sent out?
     
  • Why should I stop duplicate payments before posting?
     
  • Why should I include ACH or other payment areas in duplicate payment identification?
     
  • How can I detect duplicate payments during my process flow? It will take too long.
     
  • How can I be sure the reported duplicates are really duplicates?
     
  • My system includes multiple financial institutions. How can I manage individual institutions?
     
  • Some of my customers write duplicate checks for their own reasons. Won’t these be stopped too?
     
  • This will add a lot of cost to my processing because I want my staff to review the duplicates you report.

  • Will I be able to identify duplicates in my outgoing cash letters before they are sent out?

    Yes. Your outgoing cash letters can be checked by Dupe Detective before being sent to your exchange gateway. Duplicates at the file, bundle and item level will be detected and reported, giving you the opportunity and the information needed to correct these cash letters before sending them. Your exchange partners will be happier because you won’t be sending duplicate files to them.
        Back to Top

    Why should I stop duplicate payments before posting?

    If you wait until after posting, your customer’s account will have been debited twice for a payment. This can cause tremendous embarrassment for your customer if it results in an overdraft or NSF condition.If your customer is lucky, no other legitimate payments will be impacted and they will just be confused by the posting and correcting entries.
        Back to Top

    Why should I include ACH or other payment areas in duplicate payment identification?

    Check payments are converted to ACH through ARC, BOC and other processes. Clerical errors have allowed the same check to be presented through ACH and as a check payment. Further, return checks can be represented as ACH payments, which have already been reported as a growing fraud risk. By reporting e-check payments to D upe Detective you prevent these errors and fraud items from being processed.
        Back to Top

    How can I detect duplicate payments during my process flow? It will take too long.

    It only takes seconds to enter and evaluate payments in the Dupe Detective database. Processing delays, if any, are nominal.
        Back to Top

    How can I be sure the reported duplicates are really duplicates?

    We only report a payment as a duplicate if all of the following data is matched: the routing and transit number, account number, check serial number and amount. Further, the Dupe Detective database is updated for returns and other item changes that will effect the decision. Finally, you can add accounts and individual payments to a filter table in order to recognize specific customer’s behavior that creates valid duplicates.
        Back to Top

    Some of my customers write duplicate checks for their own reasons. Won’t these be stopped too?

    They would be if we didn’t give you the ability to list these specific payments and/or customers so we can exclude them from being labeled as duplicate payments.
        Back to Top

    My system includes multiple financial institutions. How can I manage individual institutions?

    Dupe Detective provides full support for multi-bank processing. Each financial institution can be processed independently. Different configuration settings, such as search periods, data sources or business rules and filters, can vay by financial institution. Both financial institution- and system-level reporting are also provided.
        Back to Top

    This will add a lot of cost to my processing because I want my staff to review the duplicates you report.

    Not at all. In fact we expect to reduce your total operating costs with Dupe Detective by eliminating customer service calls and research cases. The Dupe Detective business rules engine allows you to determine which duplicate payments need to be reviewed by your staff for a final decision. All the others can be handled automatically. We also provide rules for exporting the duplicates to the appropriate systems for the most efficient handling. These rules can be changed quickly and easily by your Support or Supervisory staff so they can be updated as you learn more about your customer behavior.

    Quickly deploy new processes through user-defined business rules.

    Through user-defined business rules, you can easily customize the workflow to fit your needs. Select suspects of a given source or type for operator review. Route suspects identified by an operator as potentially fraudulent to your fraud department for investigation. Raise the review priority for high-dollar suspects. Set thresholds for rejecting or holding an entire unit of work based on the percentage or number of suspects. Identify recurring payments known to be false suspects. These are just a few of the options available to you.

    Dupe Detective’s business rules are defined by the user through a menu-driven interface and can take effect immediately or at some point in the future. This means you can accommodate new payment types and processes dynamically.


        Back to Top

    For more information on how Dupe Detective can eliminate risk and reduce expenses, including an ROI calculation for your bank, fill out the contact sheet below, then press the Submit button.

    *Name:

    *Title:

    *Bank/Business Name:

    *Telephone:

    *Email:

    Product:

    Question:

    Security Question: What is 5 plus 2?
     
    How Dupe Detective Stops Duplicate Payments

    More information on Dupe Detective

    How Dupe Detective Stops Duplicate Payments

    Duplicate Payments - Why Complying with the FFIEC RDC Guidance Isn’t Enough: Reducing the risk associated with all duplicate payment presentments – not just Remote Deposit Capture*

    Taking Control of Payment Duplication: An in-depth look at a serious operational challenge created by Check21.

    How Dupe Detective Stops Duplicate PaymentsUse Adobe Reader to view this file.Click on this button to download the Adobe Reader Program


    Privacy Policy  |  Conditions of Use |