2.14.1 Repair
| Payment Type | Transaction Type | Screen Name |
|---|---|---|
| SWIFT CBRPPlus | Outgoing | PSDOCBCT |
| SWIFT CBRPPlus | Incoming | PSDICBCT |
| TARGET2 ISO | Outgoing | PSDOT2CT |
| TARGET2 ISO | Incoming | PSDIT2CT |
The fields that can be modified are enabled based on the Repair Amend Allowed Field Maintenance for the function ID and Network Code.
- 'Amend only repairable fields 'flag is checked, only the repair required fields as per the exception raised only is allowed to be amended. If the flag is not checked all the fields listed as amendable is enabled for modification.
User can edit the payment attributes only, for any of the missing/ incomplete information. EU Payer relevant attributes are Name, Account No. and Address of either Payer or Payee.
On Repair, Rule check is repeated for Missing/incomplete information and if it is Compliance failure then the respective STP action is applied.
Repair is not allowed if user doesn’t modify any of the missing information.
If repair is done on the transaction for which payment attributes are not mandatory, then it is treated as an approval and the transaction is processed further.
If any of the field details are changed on Repair, the transaction is marked as ‘Repaired’ and the sanction XML has the Repaired field as ‘Y’.
Parent topic: EU Payer Compliance Queue