Matching with Inbound Payment
The incoming cancellation requests (camt.056) are logged in the existing Inbound Cancellation Browser screen (PXSICLBR) with the Process Status as ‘Unprocessed’ once the Inbound Cancellation Request message inputted manually is authorized.
The incoming cancellation request (camt.056) message is matched with an Inbound transaction. Matching criteria for incoming cancellation request are as follows:
- The original UETR field of the Incoming cancellation request is matched with the UETR of the Inbound transaction.
- Process Status value is updated as ‘Matched’ in the Inbound Cancellation Browser.
- Queue action log is populated with action as ‘MATCH’ along with maker/checker ids as SYSTEM and maker/checker timestamps against the Cancellation Request (camt.056) message.
- A recall request record is logged to show under the ‘Exception’ screen of the Inbound Transaction view screen.
User can manually match the Incoming Cancellation Request (camt.056) by taking Manual Match user action on the Inbound Cancellation Browser screen (PXSICLBR).
In case you match the Incoming Cancellation Request (camt.056) with an Incoming transaction that is already cancelled/seized, the Incoming Cancellation Request (camt.056) is left in the Inbound cancellation browser with status as Rejected. You are allowed to take only Reject action on the transaction.
Incoming Cancellation Request (camt.056) is moved to the Inbound Cancellation Request queue (PQSICLRQ) for user actions.
Cancellation processing for an Inbound transaction is done based on the transaction status and queue code.
Parent topic: Inbound Cancellation Request Processing