Managing Duplicates

Duplicate Detect uses the definitions in namespaces to analyze payment items and assess whether they match previously processed items. When an incoming item matches a previously processed item, it is called a potential duplicate of the previously processed item. If a namespace definition specifies that potential duplicates must be reviewed by human operators, the items are retained by Duplicate Detect until potential duplicates are reviewed.
Note: The namespace definition can also specify that operator review is not required. In this case, Duplicate Detect is said to auto-decision items and matching items are immediately considered duplicates with no operator review.

A unit of work describes a group of items that are introduced to Duplicate Detect in a file. An example of a unit of work is an image cash letter file containing payment items.

When a unit of work contains potential duplicates, which must be reviewed by operators, the entire unit of work is held by Duplicate Detect until all potential duplicate items are reviewed. The review process is done using pages presented by the Duplicate Detect user interface.

After all items are reviewed for a unit of work, Duplicate Detect sends them to the next processing step in the payment processing system.

Reviewing duplicates is done using the functions provided under the tab labeled manage duplicates. The items processed by the system are viewable by a unit of work or by a date.

The Duplicate Detect user interface fast data and image retrieval feature enhances the application's ability to retrieve data and images of work items for a period of time as opposed to accessing the database or engine for each request from the browser. The list of work items are locked by the user and returned to the browser as XML files along with images and data for comparison items. The XML file is parsed in the browser which helps the Duplicate Detect user interface to display work items at a faster rate.

Audit logging is used to log significant user actions in Duplicate Detect. The information is saved in the database and can be reviewed from audit information page. For audit purposes, the following are logged:
  • Disposition of work items
  • Administrator actions, such as updating configuration properties, create or delete purge tasks, delete unit of work items

Duplicate Detect audit log messages can be filtered on the audit information page by using the component name Duplicate Detect. The component name can be found on the about page. For more information about the audit information screen, see Transaction Server User's Guide.

Note: The following program is required in order to use audit logging:
  • Transaction Server