Cross Border Reversal Processing

This processing is done for the Incoming and Outgoing/Pass-through Cross Border/RTGS transactions.

Reversal accounting entries with event code as REVR and Transaction amount with negative sign gets passed in the application.

Transaction Date is the Date on which the reversal is done.
Event code is 'REVR'.
Value date is original value date.

Transaction Status on is marked as 'Reversed'.

If FX Reference Number is available in the transaction, then record for the transaction is logged in FX Unwind Queue (PQSFXCAN).

In the transaction reversal processing of Outbound Cross-border/RTGS transactions, the original message fields (Block 4) are added, if the transaction is a Non-gpi transaction and if the transfer type is Customer Transfer or Bank transfer and when the 'Generate Cancellation Request Message' is checked during reversal request.

Deferred Charge Liquidation Impact:

In case if Deferred pricing is set and transaction is already liquidated then on Reversing the transaction reversal entries are posted for the Charge Amount on the date of Reversal.

In case if Deferred pricing is set and the transaction is not yet liquidated then on Reversing the transaction the transaction status marked as 'Reversed' on Inbound Cross Border Payment View (PXDIVIEW) screen and Outbound Cross Border Payments View (PXDOVIEW) screen are excluded during liquidation.

Notification Changes:

Notification event "PAYMENT_REVERSAL" is available in the application.

After transaction reversal, notification gets generated in the application.

Listed below are the tag values which are sent in the Payment Reversal notification. Apart from below mentioned tag values all the other tag values in the Payment Reversal notification are similar to Payment Cancel notification.

Notification Tag

Value

PAYMENT_REVERSAL

This tag displays the maker id of user who initiated the Reversal

This tag displays the checker id of user who authorized the Reversal

Parent topic: Cross Border Reversal