1. Payments Core User Guide
  2. Payments Core Processes
  3. Verification Queue Processing
  4. Modify Action Processing

Modify Action Processing

Modify Action launches PXDOTONL screen with Payment type as Cross Border / RTGS.

The transaction details are populated into the underlying transaction input table if no data available earlier (Transaction is an uploaded transaction and was not moved to Non-STP queue and modified/released). Otherwise, a new version is to be created and shown to the user for modification. The data in the host tables are populated into transaction input tables even for manually inputted transactions because there can be data modifications done during the transaction processing. E.g. Transaction data modified in Repair Queue.

You can modify the data only for the fields that are maintained in the Verification Amend Allowed Fields Detailed (PMDVFAMD).

On Authorization of the modification, the data in the transaction input tables is updated to the host tables for further processing after the below processing is successful.
  • ECA Reversal Request is sent out, if ECA Check was applicable.
  • FX Reversal Request is sent out, if External Exchange Rate was applicable.
  • FX Unwind request is logged after cancellation, if transaction is a cross currency transaction and FX Reference is present.
  • Generated payment messages gets deleted.

The modified transaction is processed from the beginning starting from Repair validations for both Originated payments and for Pass-through payments.

For Pass-through payments, if Split Accounting is already done, then the same is reversed and reversal accounting entries are sent to accounting system. 'Debit Liquidation Status' is reset to 'Pending'.

Parent topic: Verification Queue Processing