Sanctions Check

If sanction check is applicable for the Network and Source (based on the preference maintained in the existing maintenance Source Network Preferences PMDSORNW) and for the customer, Sanctions screening is done for the Payment Status Report (pacs.002) message.

If the flag is set as Yes, then the sanction system is picked up from the Sanction System mapping maintenance, Default Sanctions System / Network specific Sanction System.

A Sanctions request XML will be prepared and is sent to the Sanction System. A record is logged in to the Sanction Queue. The request is in Sanction Queue till the final response (Accept / Reject / Seizure) is received.

Based on the response from the sanctions response status, the below processing is done:

Approved/Rejected

If the response is received as Accepted/Reject on the same day, the Reject transaction sanctions status is updated accordingly, and the processing continues with the next step i.e. accounting.

If the response is received on a later date, the transaction processing date is updated as the current branch date if it is a branch and network working day. If the current branch date is a branch or network holiday, the processing date moves to the next possible working day for Branch and Network.

Seized

In the case of the Seized response, the Sanction status is updated as Seized. Seizure accounting entries are passed only in case of a negative payment status report (pacs.002).

Process Status of the transaction is updated as “Processed” in the incoming message browser after sanctions check.

Note:

You can select the check box ‘Disable for Inbound’ maintained for the Network Code and Message Type in the Sanctions Restrictions Detailed (PMDSCRES), to skip sanctions screening for Inbound Payment Status Report (pacs.002).