3.4.1 SFMS ACK/NAK Messages Processing

Message Name Message Description
F23 This is a Delivery Notification message.
F20 This is an acknowledgment message from SFMS.
F25 This is a Negative acknowledgment message from SFMS. User can take manual action on outgoing payment transaction.
F26 This is a Negative acknowledgment message from SFMS user. User can take manual action on outgoing payment transaction.
F27 This is an acknowledgment message from Bank API (IDRBT/RBI).

If this message is Negative Acknowledgment, then user can take manual action on outgoing payment transaction.
F29 This is Delivered At NEFT. This is ISO migration to notify about the delivery of message. This message supports in both format - ISO and IFN.

Processing Steps

ACK Processing:

On receipt of incoming F20/F27 ACK messages from SFMS, system parses the message and process. The parent transaction is fetched based on following matching fields: (Note: F20/F27 ACK is received for the outgoing pacs.008.001.09 messages sent in a bundle of 10)
  • Matching:

    - External Application Sequence number mentioned in the F20/F27 message is matched against the sequence number sent in the original outgoing payment transaction/message (outgoing pacs.008.001.09) in Block A header and the IFSC Code of the Originating branch (Our IFSC Code).

  • Message Status Update: If matched,
    • For F20 (Message Identifier in the format) received, original outgoing payment gets updated
    • i.e, All the ‘10’ transactions sent in the outgoing pacs.008.001.09 bundle having the same sequence number is updated
  • For F27 (Message Identifier in the format) received,
    • System checks the ‘Bank API Response Code’ field
    • i.e, All the ‘10’ transactions sent in the outgoing pacs.008.001.09 bundle having the same sequence number is updated

NAK Processing:

On receipt of incoming F25/F26/F27 NAK messages from SFMS, system parses the message and process. The parent transaction is fetched based on following matching fields: (Note: F25/F26/F27 ACK is received for the outgoing pacs.008.001.09 messages sent in a bundle of 10)

- Matching:

- External Application Sequence number mentioned in the F25/F26/F27 message is matched against the sequence number sent in the original outgoing payment transaction/message (outgoing pacs.008.001.09) in Block A header and the IFSC Code of the Originating branch (Our IFSC Code).

Manual action and Message Status Update: If matched,
  • System waits for user action to be taken from the new screen – Negative Acknowledgement Message Details. Screen PTSFNAKQ will no longer be used and removed from the system.
  • Below steps are performed form new screen - Negative Acknowledgement Message Details:
    • User will select the outgoing pacs.008.001.09 single record from PTSOUTBR and click ‘Process NAK’ option. In case, multiple records are selected and ‘Process NAK’ option is clicked then system throws an error.
    • System opens the Negative Acknowledgement message details screen.
    • Transaction Details section of the screen lists out the transactions bundled in the original outgoing pacs.008.001.09 message. By default, all the messages are selected. So, the manual action is applicable for all the underlying transactions in the outgoing pacs.008.001.09 bundled message.
Dispatch Reversal Accounting for NEFT Outbound Event Dr/Cr Account Account Type Amount Tag
NEFT Outbound DCLG Dr Nostro Account Account FILE_AMT
NEFT Outbound DCLG Cr Network Clearing GL GL FILE_AMT
Dispatch Reversal Accounting for NEFT Outbound Event Dr/Cr Account Account Type Amount Tag
NEFT Outbound DRLQ Dr Network Clearing GL GL XFER_AMT
NEFT Outbound DRLQ Cr Intermediary GL GL XFER_AMT
NEFT Outbound DRLQ Dr Intermediary GL GL XFER_AMT
NEFT Outbound DRLQ Cr Customer Account Account XFER_AMT

Parent topic: NEFT Acknowledgment Processing