When R- transactions are received, system tries to match the transaction with the original Collections sent irrespective of the original transaction status. Transactions pending in exception queues / future value queues are also considered for matching.

If the original transaction fetched is not found or not in the expected status, system moves the R- message to an exception queue with appropriate error message.

You can verify the details of original transaction, initiate appropriate steps for moving the transaction to the required status and then re-initiate the processing of R-message.

More information on R- Messages Queue is available in the Exception Queues User Manual.

• Outbound Collections Reject/Return
  
• Outbound Reject/Return View
  
• Outbound Collections Reverse/Recall
  
• Outbound Reverse/Recall View
  
• Outbound Collections Refund
  
• Outbound Collections Refund View
  
• Inbound Collections Reject/Return
  
• Inbound Reject/Return Detailed View
  
• Inbound Collections Reverse/Recall
  
• Inbound Reverse/Recall Detailed View
  
• Inbound Collections Refund
  
• Inbound Collections Refund View
  
• Network Reject
  
• Non-urgent R transactions