ADMI.004.001.01 Messages Processing

MX admi.004.001.01 SystemEventNotificationV01 messages are sent to notify the occurrence of an event in a central system.

System supports processing of below event codes in the ADMI.004.001.03 messages:

Message Definition Identifier	Message Description
F20	This is an acknowledgment message from SFMS.
F22	This is the non-delivery warning message sent by SFMS to CBS.
F23	This is the delivery notification message sent by SFMS to CBS.
F25	This is a Negative acknowledge message from SFMS. If this message is received then system will reverse the corresponding outgoing payment contract.
F27	This is an acknowledgment message from Bank API (IDRBT/RBI). If this message is Negative Acknowledgment then the corresponding transaction is reversed If this message is Positive Acknowledgment then the ACK of original transaction is updated.

Processing Steps:

ACK Processing:

On receipt of incoming admi.004.001.01 messages from SFMS, system parses the message and process. The parent transaction is fetched based on following matching fields:

Matching:
- The field <BizMsgIdr> in the incoming admi.004.001.01 message is matched against the field <BizMsgIdr> in the Business Application Header of original outgoing payment message sent pacs.008.001.03 / pacs.009.001.03.
Message Status Update: If matched,
- then, system identifies the event code based on the below field in the incoming admi.004.001.01 message.
- <EvtCd> - This field identifies the type of system event notification. This field can be F20, F27.
- If <EvtCd> is ‘F27’, then, system checks the field ‘<EvtParam>’. Based on the Bank API Response code for the positive ack – ACK status gets updated.

NAK Processing:

Manual action and Message Status Update on receipt of admi.004 with event code F25 and F27: If matched,

Regenerate Action:

When user clicks the 'Regenerate Messages' option then system regenerates pacs.008/pacs.009 transaction and send it to SFMS.
For this regenerated pacs.008/pacs.009 message, system creates new Message ID and Transaction ID (UTR). This new Message ID and Transaction ID (UTR) will be mapped to regenerated message.
Regenerated pacs.008/pacs.009 message is visible on PLSOUTBR screen as a new record. Message ID of original transaction is mapped for such messages under the 'Original Message ID' column.

Reject Action:

When User clicks the 'Reject Messages' option then system will mark the pacs.008/pacs.009 transaction as 'Rejected'.
Reject will be processed for each transaction. EAC (only for non-prefunded GL, originated by other channels) and accounting will be done as part of reject processing.

Reversal Account entries are posted as given below:

Accounting for Reversal of RTGS Outbound	Event	Dr/Cr	Account	Account Type	Amount Tag
RTGS Outbound - Reversal	DRLQ	Dr	Nostro Account	Account	XFER_AMT
RTGS Outbound - Reversal	DRLQ	Cr	Intermediary GL	GL	XFER_AMT
RTGS Outbound - Reversal	CRLQ	Dr	Intermediary GL	GL	XFER_AMT
RTGS Outbound - Reversal	CRLQ	Cr	Customer Account	Account	XFER_AMT

Authorize Action:

Regenerate and Reject action will go for Supervisor Authorization.
Using this 'Authorize' action, supervisor can approve/reject the records.

Parent topic: RTGS Acknowledgment Processing