Payment Status Report (pacs.002) Transaction Upload

Inbound Payment Status Report (pacs.002) message is received with business header.

After receiving the Inbound Payment Status Report (pacs.002) message the message is created and logged in the incoming message tables.

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, error details are recorded in the Inbound Message Browser.

On completing the format validations, the message is parsed and uploaded. Users can view the message status from the Inbound Browser Summary (PMSINBRW) screen.

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.

If the pacs.002 message matching fails, the pacs.002 transaction status is marked as ‘Unmatched’ under the Processing Details tab of the Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen, and Process status of the uploaded pacs.002 marked as ‘Processed’ in the Incoming Browser Summary (PMSINBRW).

Note:

Error Description

Matching of Original Instruction Identification/ Original UETR failed for the Payment Status Report (pacs.002) message received.

If the pacs.002 message matches with original pacs.008/pacs.009 message then:

The pacs.002 transaction status is marked as ‘In Progress’ under 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).
The incoming pacs.002 message get linked with original pacs.008/pacs.009 messages.

If pacs.002 message does not match with the pacs.008/pacs.009 message, 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.

If the pacs.002 message matching fails, the system record Match status as ‘Unmatched’ under 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).

If the pacs.002 message matches with pacs.004 message then:

The pacs.002 record transaction status marked as 'Blank', under Processing Details Tab of Generic Wires ISO Inbound Status Report View (PSDIGRJV) screen.
The pacs.002 record Match status marked as ‘Matched’, under 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 (i.e. Generated Reference field is updated with the Transaction Reference number of original pacs.004 messages).

You 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.

Source Code is derived as currently done for the PX module where the Source Maintenance Detailed (PMDSORCE) maintenance is referred with Incoming SWIFT flag as checked.

Network Code for the payment is derived as the Network Code of the original pacs.008/pacs.009/pacs.004 messages.

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