Inbound gFIT Confirmation Message Processing

Incoming MT 299 message is identified as a gFIT confirmation message if the Block 3 - Field 111 is present with a value '004'.

Once the Incoming MT 299 message is identified as gFIT confirmation message, then the same is matched against an Outbound bank transfer transaction. Matching criteria is as follows:

- Block 3 - Field 121: UETR of Incoming MT 299 gFIT confirmation = UETR of Outbound Bank Transfer transaction.

Once the matching is successful, the Inbound confirmation message is parsed and populated in gFIT confirmation table to show in 'Tracker Confirmations' - gFIT Confirmations section.

All received gFIT confirmation message is shown in the Inbound gpi Confirmations Summary (PXSIGPCN) screen with the matched status and the matched transaction reference (if matched).

If the matching is unsuccessful, the 'Confirmation For' field is populated with a value 'Beneficiary Institution'
If the matching is successful, the 'Confirmation For' field is populated with a value 'Instructed Agent'

Impact on gCCT/gCOV Confirmation Message Processing

If the Inbound gCCT/gCOV confirmation message is matched against an Outbound transaction, the 'Confirmation For' field value is populated with a value 'Instructed Agent'.

Parent topic: gFIT Processing