Outbound gCOV Confirmations - MT 299 Message Generation
The gCOV MT 299 confirmation message is generated with fields 20,21,79. The
Outbound MT 299 gCOV confirmation message will be automatically linked to the pass-thru
or original Inbound gCOV transaction.
- BIC address to send MT 299 confirmation to Tracker is referred from the gpi Host preferences maintenance (PXDGPIPF). System will not perform RMA/RMA+ validation on the Tracker BIC.
- Fields 20 (Transaction Reference), 21 (gCOV reference of F20 of MT 202COV/MT 205COV) and 79.
- Block 3 of the FIN message has gpi tags 111:001, 121: UETR of gCOV.
- Field 79 of the status confirmation message MT 299, populates the following details:
Line 1
- //date and time
- //1601121515+1300
Date & Time Format:Date in YYMMDD format and Time in HHMM and the
time zone (of Host) in which "time" is expressed is to be identified by means of the
offset (positive or negative) against the UTC.
Note:
Time offset HH will be <=13 and MM will be <=59Line 2
- //status code [/reason code]
gCOV confirmation messages by Intermediary Reimbursement /Last Reimbursement
Agent
| Transaction Type | Processing status | Message generated | Status Code/ Reason Code | Date & Time details | Payment Processing Status [PXDGPIST] | In-progress Codes – gCOV [PXDGPIST] |
|---|---|---|---|---|---|---|
| Incoming | For the below scenarios, apply this validation before gpi confirmation generation: Check transaction level ‘gpi’ agent as ‘Yes’ & ‘Incoming gpi’ set as ‘Yes’ OR ‘gpi agent’ flag as ‘Yes’ & Incoming gpi set as ‘No’ | For the below scenarios, apply this validation before gpi confirmation generation: Check transaction level ‘gpi’ agent as ‘Yes’ & ‘Incoming gpi’ set as ‘Yes’ OR ‘gpi agent’ flag as ‘Yes’ & Incoming gpi set as ‘No’ | For the below scenarios, apply this validation before gpi confirmation generation: Check transaction level ‘gpi’ agent as ‘Yes’ & ‘Incoming gpi’ set as ‘Yes’ OR ‘gpi agent’ flag as ‘Yes’ & Incoming gpi set as ‘No’ | For the below scenarios, apply this validation before gpi confirmation generation: Check transaction level ‘gpi’ agent as ‘Yes’ & ‘Incoming gpi’ set as ‘Yes’ OR ‘gpi agent’ flag as ‘Yes’ & Incoming gpi set as ‘No’ | For the below scenarios, apply this validation before gpi confirmation generation: Check transaction level ‘gpi’ agent as ‘Yes’ & ‘Incoming gpi’ set as ‘Yes’ OR ‘gpi agent’ flag as ‘Yes’ & Incoming gpi set as ‘No’ | -- |
| Incoming | Processed & credited to instructed agent’s account [MT 910 generated] | On accounting completion | ASCS | Credit value date & current time | PROCESSED | NA |
| Incoming | Pending by EOD in process exceptions queues (Including warehouse queue) | EOD job | ACSP/ G002 | Message generation Date & time | INPROGRESS | PENDING CREDIT |
| Incoming | Transaction is Sanctions Seized | After Seizure entry posting | RJCT | Message generation Date & time | REJECT ED | NA |
| Outgoing (Pass through as SWIFT/other network messages) | COV Processed & forwarded as a gpi message to gpi agent. Message generation Suppressed | FIN message/FIN Copy service gpi message is sent out | ACSP/ G000 | Message generation Date & time | -- | -- |
| Outgoing (Pass through as SWIFT/other network messages) | COV Processed & forwarded as a gpi message to non-gpi agent. Message generation Suppressed | FIN message/FIN Copy service gpi message is sent out | ACSP/ G001 | Message generation Date & time | -- | -- |
| Outgoing (Pass through as SWIFT/other network messages) | COV transaction is pending by EOD in process exceptions( including warehouse queue) | EOD job | ACSP/ G002 | Message generation Date & time | -- | INPRO GRESS |
| Outgoing (Pass through as SWIFT/other network messages) | Transaction is Sanctions Seized | After Seizure entry posting | RJCT | Message generation Date & time | -- | REJEC TED |
gCOV confirmation messages by gCOV Instructed Agent
| Transaction Type | Processing status | Message generated | Status Code | Date & Time details | Payment Processing Status [PXDGPIST] | In-progress Codes – gCOV [PXDGPIST] |
|---|---|---|---|---|---|---|
| -- | On successful cover matching of a gCCT transaction with gCOV | On successful cover match | ASCS | Cover match Date & time | PROCESSED | NA |
Line 3
//status originator (BIC)[/ forwarded to (BIC)]
Status Originator field:
This contains the BIC code of the gpi bank that provided the status in the gCOV Confirmation (standard MT representation for identifier code: 4!a2!a2!c[3!c]), optionally followed by the identifier (BIC) of the financial institution to which the gCOV leg was transferred.
Forwarded-to agent field:
This field informs recipients of gCOV confirmations to which agent the gCOV leg was transferred to
**Presence of this field is mandatory when confirmation status is ACSP/G000
- Example: //GPIBBICXXXX/GPICBICXXX
Line 4
//currency and amount
- Currency includes currency used in field 32A of gCOV leg with format 3!a
- Amount includes amount used in field 32A of gCOV leg with format 15d
- For ACSC, RJCT, ACSP/G002 and ACSP/G003, the "gCOV leg" to consider is the Inbound one for the currency field value.
- For ACSP/G000 and ACSP/G001, the "gCOV leg" is the Outbound one for the currency field value
Note:
There will not be any Sanctions Check validation done for the gpi Confirmation messages.
The Tracker generates gCOV confirmations to gpi agents automatically in case of ACSP/G000 and ACSP/G001, based on content of transferred MT 103 or MT 202/5 COV on FIN network.