8.2.1.1 Payment Status Report (pacs.002) Transaction Upload

This topic explains the details of payment status report (pacs.002) transaction upload.

The process is as follows:
  1. Inbound Payment Status Report (pacs.002) message is received with business header.
  2. A message is created and logged in the incoming message tables.
  3. System does format validations for the Payment Status Report (pacs.002) message received based on the schema details maintained for the message in File Parameter Detailed (PMDFLPRM) maintenance screen. The error details are recorded in the Inbound Message Browser.
  4. The message is parsed and uploaded. Users can view the message status from the Inbound Browser Summary (PMSINBRW) screen.
  5. After parsing the incoming Payment Status Report (pacs.002) 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.
  6. If the pacs.002 message matching fails, then the pacs.002 transaction status is marked as Unmatched from the Processing Details tab of the Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen. Also, process status of the uploaded pacs.002 marked as Processed in the Incoming Browser Summary (PMSINBRW) screen.

    Note:

    Error Description: Matching of Original Instruction Identification or Original UETR failed for the Payment Status Report (pacs.002) message received.

  7. If the pacs.002 message matches with original pacs.008/pacs.009 message, then:
    • The pacs.002 transaction status is marked as In Progress from the Processing Details tab of the Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen.
    • The process status of the uploaded pacs.002 is Processed in the Incoming Browser Summary (PMSINBRW) screen.
    • The incoming pacs.002 message get linked with original pacs.008/pacs.009 messages.
  8. If pacs.002 message does not match with the pacs.008/pacs.009 message, then the system matches the pacs.002 with pacs.004 message using the following matching criteria:
    • Original Instruction Identification received in the incoming message is matched with Original Instruction Identification of pacs.004 message.
    • System matches the original UETR received in the incoming message with the Original UETR of pacs.004 message.
  9. If the pacs.002 message matching fails, the system record match status as Unmatched from the Processing Details tab of Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen. The Transaction Status remains Blank. Process status of the uploaded pacs.002 is Processed in the incoming browser (PMSINBRW).
  10. If the pacs.002 message matches with pacs.004 message, then:
    • The pacs.002 record transaction status marked as Blank, from the Processing Details tab of Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen.
    • The pacs.002 record Match status marked as Matched, from the Processing Details tab of Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen.
    • Process status of the uploaded pacs.002 is Processed in the incoming browser (PMSINBRW).
    • The incoming pacs.002 message gets linked with pacs.004 message (that is, Generated Reference field is updated with the transaction reference number of original pacs.004 messages).
  11. User can view the Transaction Status for incoming pacs.002 message on the Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen as Duplicate if pacs.002 matches with another pacs.002 messages.
  12. Source Code is derived as currently done for the PX module where the Source Maintenance Detailed (PMDSORCE) maintenance is referred with Incoming SWIFT option as checked.
  13. Network Code for the payment is derived as the Network Code of the original pacs.008/pacs.009/pacs.004 messages.

Parent topic: Positive or Negative Payment Status Report (Common Processing)