1. Cross Border User Guide
  2. SWIFT gpi
  3. gCCT Transaction Processing
  4. Inbound gCCT processing

Inbound gCCT processing

The Outbound MT 199 gCCT confirmation generation functionality remains same as below:

System performs the following during the incoming MT 103 payment message processing
Set ‘Incoming gpi’ flag based on (111:001) at transaction level Check ‘gpi processing enabled’ flag at host level (PXDGPIPF) Check if Processing branch 11-Character BIC/Transfer currency is present in gpi Directory(PMDGPIDR) Set ‘gpi agent’ at transactio n leve
Yes Yes Yes Yes
No Yes No No
Yes No Skipped No
No No Skipped No
Set ‘Incoming gpi’ flag based on (111:001) at transaction level Check ‘gpi processing enabled’ flag at host level (PXDGPIPF) Check if Processing branch 11-Character BIC/Transfer currency is present in gpi Directory(PMDGPIDR) Set ‘gpi agent’ at transaction level
No Yes Yes Yes
Yes Yes No No

If the ‘gpi Agent’ sets to ‘No’ as per above tables functionality, then system generates MT 199 gCCT confirmation messages (without Field 111) after RMA+ validation for Tracker BIC as explained above in the Outbound (pass-through) section.

System sets ‘gpi Agent’ to ‘Yes’ if the processing branch BIC/transfer currency is present in gpi directory.

System performs the below operations when ‘Incoming gpi flag’ is ‘No’
  • Network Cutoff Time Check is done as for normal SWIFT incoming payments from the Inbound BIC Cutoff time (PXDINCOF)
  • MT 199 gets triggered automatically when the ‘71A’ is ‘OUR’ and 71G is lesser than the calculated charges. This can be triggered manually without any restriction
  • Generates gCCT confirmation message with 111:001 (RMA+ validation not required)

Network Cutoff Time Check:

For ‘gpi Enabled’ = ‘Yes’
  • Sender BIC (11-Character BIC as received in the Block 2 of the Inbound MT message) is considered from the new screen (PXDSRIAG) for Inbound gpi payments sender agreement, if present.
  • If not present, cutoff time is taken from the gpi directory for the Processing branch BIC (11-Character BIC as received in Block1 of the Inbound MT message), Transfer Currency combination.
  • If not found as in step (2), cutoff time is taken from the gpi directory for the Processing branch BIC (11-Character BIC maintained as default BIC in STDCRBRN), Transfer Currency combination.
  • If the gpi transaction passed this cut-off time, then the transaction moves to Network Cutoff queue.

Charge Option OUR:

For ‘gpi enabled’ transactions, where 71A is ‘OUR’
  • If 71G charges is equal to or more than calculated charges, then system deducts for the calculated charges/tax and post receiver charge entries as per current functionality.
  • If 71G is less than calculated charges,
    • System suppresses generation of MT 191 charge claim advice for gpi payments. A validation is added to not to trigger or send MT 191 charge claim messages either automatically or manually when the gpi Service Identifier is present in the Inbound MT 103 and if at host level preference 'gpi processing enabled' is set as 'Y'.
    • System automatically expenses out for the amount shortfall irrespective of the claim tolerance if any maintained for the Sender of the MT 103 message.
    • Existing accounting is continued, i.e. accounting templates for debit /credit liquidation maintained in PMDNCPRF is used.
    • Expense GL maintained in Charge Claim Default preferences is debited in DRLQ and Receivable GL from the same maintenance is credited.

Parent topic: gCCT Transaction Processing