Reverse Message Evaluation - SWIFT CBPRPlus
Reverse Message evaluation is done only for SWIFT CBPRPlus messages.
Reverse Message evaluation logic is applied based on value received in below
fields:
- Group Header/Settlement Information/Settlement Account/Identification/IBAN (i.e. GrpHdr/SttlmInf/SttlmAcct/Id/IBAN)
- Group Header/Settlement Information/Settlement Account/Identification/Other/Identification (i.e. GrpHdr/SttlmInf/SttlmAcct/Id/Othr/Id)
If Settlement Account (i.e. GrpHdr/SttlmInf/SttlmAcct/Id/Othr/Id) is received in
the incoming message then
- System checks the Reverse Message Agreement is maintained for the Settlement Account in the Reverse Message Agreement Maintenance (PMDREVAG) screen.
- Reverse Message evaluation is done based on the Settlement Account.
If Settlement Account ' IBAN (i.e. GrpHdr/SttlmInf/SttlmAcct/Id/IBAN) is received
in the incoming message then
- Customer Account is derived from IBAN using External Customer Account Input (STDCRACC) maintenance.
- System checks if Reverse Message Agreement is maintained for the Derived Account in the Reverse Message Agreement Maintenance (PMDREVAG) screen.
- Reverse Message evaluation is done based on the derived Customer Account.
For Outbound-passthrough Reverse Message, the Reverse Message agreement validation is done on Booking Date and on Value Date in case if Value Date is a future date.
Transaction moves to Business Override Queue in case of Reverse Message agreement validation failure.
Parent topic: STP Layer - pacs.009 Processing