On receipt of any Inbound Common Group message and subsequently matching it with a payment transaction, the system sends the actual received message to Sanctions system for scanning.

• This involves sending of the actual SWIFT message embedded in the Sanctions request XML to Sanctions system.
• During matching, if match is found then the transaction reference number of the original transaction is updated in the "Cross Border Contract Reference Number" field against the MT n99/MT n96/MT n91/MT n92 message record present in the Common Group Message Sanction Summary (PQSSNCST) screen.

  Note:

  The above second bullet point is only applicable after receiving the incoming MT n99, MT n96, MT n91 and MT n92 messages.
• If the received message was repaired in the Inbound Message Browser then the repaired message is sent for Scanning.

If any status other than Approved is received from Sanctions system then system moves the Inbound Common Group message to the Sanctions queue.

• In the queue screen, a new column in the grid called “SWIFT Message Type” would help in identifying Inbound Common Group message transactions, as described above.
• You can take up appropriate action on the message in the queue similar to the existing functionality for payment transactions.
• If Auto-cancellation has been configured for a Reject response from Sanctions then the Inbound Common Group message is auto-cancelled and not processed further.