6.1.2 Pacs.002.001.11 - NEFT RBI Reject of Outbound Payment (pacs.008.001.09)/Outbound Return (Pacs.004)

System will parse the incoming pacs.002 reject message having group of outgoing payment transactions bundled in a single message.

The pacs.008.001.09 parent transaction is fetched based on following matching fields:

pacs.002.001.11 tags	pacs.008.001.09 tags
Original End to End Identification <OrgnlEndToEndId>	End To End Identification <End- ToEndId>
Original Transaction Identification <OrgnlTxId>	Transaction Identification <TxId>

The pacs.004 parent transaction is fetched based on following matching fields:

pacs.002.001.11 tags	pacs.004.001.10
Original End to End Identification <OrgnlEndToEndId>	End To End Identification <End- ToEndId>
Original Transaction Identification <OrgnlTxId>	Transaction Identification <TxId>

System checks the tag Transaction Status <TxSts> and Rejection Code <Rsn><Cd>.

In case of Reject: Transaction Status is RJCT

In case of rescheduling: Transaction Status is ACWP (Accepted without posting)

If the reject code is of 'Reschedule' type & matched transaction is of pacs.008.001.09:

• The original outgoing payment transaction message status is marked as 'Rescheduled'.
• No further action is required on the original transaction.
• Transactions in the 'Rescheduled' message status is allowed for further processing in its life-cycle (Return, Credit Done).
  • Network Reject details are updated with Reject Reference, Reject Code, Rejection Reason for the original Outgoing transaction.
  • This can be viewed under Exception tab of the Outgoing transaction - View Screen.

PPTDOVIEW ->Exception Tab	Pacs.002.001.11 tags
Reject/Reschedule Reference	Status ID <StsId>
Reject/Reschedule Date	<CreDtTm>
Reject/Reschedule Code	Reason Code<Rsn><Cd>

If the reject code is of 'Reschedule' type & If the matched transaction is of pacs.004:

• The return transaction (pacs.004) message status is updated as 'Return Rescheduled'.
• Network Reject details are updated with Reject Reference, Reject Code, Rejection Reason (as per N03 Mapping) for the Inward Return- Network Reject.
• This can be viewed in the Incoming - View Screen. Mapping same.
• No further action is required on the return transaction.

If the reject code is of Reject type -

- When user clicks the 'Process NAK' option from NEFT Inbound Message Browser (PTSINBRW), system launches NEFT Network Reject Summary View (PTSN03TX) screen.