Overview
- the MICR data for payments that have been marked invalid by payment validation rules
- the currency of an item when payment validation rules are not available to properly set the currency
When an image cash letter file is ingested by the Gateway, the institution’s validation rules are called to validate the MICR data for each item in the cash letter. The validation results are recorded for each MICR field. If invalid data is found, the batch created for the cash letter is marked for repair in the FTM database. The Transaction Server posts a message to a WebSphere® MQ queue every time a batch with repairable items is created. A message notifies Payment Repair that a batch needs to be repaired.
Payment Repair uses its own database tables to keep track of repairable items and their data. When notification of a batch requiring repair arrives, Payment Repair creates a unit of work with a name based on the cash letter file name. After creating the unit of work, Payment Repair obtains data for the repairable items from the FTM database.
To repair the items, an authorized repair operator logs in to the Control Center and accesses the repair page. Payment Repair provides a way for trained repair operators to view the payment images and MICR data for repairable items. The repair page displays a sequence of repairable items and data. The operators repair the invalid MICR fields, which are highlighted, by referring to the payment image displayed.
Each proposed repair is validated again by calling the validation rules. A message is sent to the Transaction Server for each repaired payment. The MICR data is stored and the payment is marked repaired, which makes it available for downstream processing.
Instead of repairing an item, repair operators can decide an item cannot be resolved with the available information. This information is sent to the Transaction Server and unresolved items can be adjusted by downstream processing.