7.2.1 Transaction Upload and Matching

Transaction Upload and Matching is the process of uploading and reconciling payment transactions within the payment system.

The details are as follows:
  • Incoming Return (pacs.004) message is received with business header.
  • After receiving the Incoming Return (pacs.004) message, the message is logged in the incoming message tables.
  • System does format validations for the pacs.004 message received based on the schema details maintained for the message in File Parameter Detailed (PMDFLPRM) maintenance screen.
  • On completing the format validations, the message is parsed and uploaded. Users can view the message status from the Inbound Browser Summary (PMSINBRW) screen.
  • If pacs.004 TARGET2 message is matched with TARGET 2 pacs.008/pacs.009 transaction.
  • If pacs.004 CBPRPlus message is matched with CBPRPlus pacs.008/pacs.009 transaction.
  • After parsing the pacs.004 message, the message is matched with the original pacs.008/pacs.009 messages using the following matching criteria:
    • Original instruction identification received in the incoming message is matched with Instruction Identification of pacs.008/pacs.009 messages.
    • Original UETR received in the incoming message is matched with UETR of pacs.008/pacs.009 messages.
  • If the pacs.004 message matching fails, then pacs.004 record Return transaction status under Processing Details tab from the Generic Wires ISO Inbound Payment Return View (PSDICBRV) screen is marked as Unmatched and process status of the uploaded pacs.004 is Processed in incoming browser (PMSINBRW).
  • If the pacs.004 message matches with original pacs.008/pacs.009 messages then:
    • The pacs.004 record return transaction status under Processing Details tab from the Generic Wires ISO Inbound Payment Return View (PSDICBRV) screen is marked as In Progress.
    • Process status of the uploaded pacs.004 is Processed in the incoming browser (PMSINBRW).
    • The incoming pacs.004 message get linked with original pacs.008/pacs.009 messages (that is, Generated Reference field is updated with the Transaction Reference number of original pacs.008/pacs.009 messages).
  • Source Code is derived as currently done for the PX module where the Source Maintenance Detailed (PMDSORCE) maintenance screen is referred with Incoming SWIFT option as checked.
  • The Network Code for the payment is derived as the Network Code of the original pacs.008/pacs.009 messages.

Parent topic: Inbound Return Processing