3.3.3 Features

Support for:
  • Defaulting debit account IBAN in Ordering Customer (Field 50) Party Identifier field in the Outbound Cross-border / RTGS Customer Transfer (MT 103) transaction based on Source / Network level preference (PMDSORNW).
  • Defaulting Name, Address of Debit account from External Customer Input (STDCIFCR) as Field 50 Ordering Customer in Outbound Customer Credit Transfer (MT 103) transaction booked due to incoming MT101 based on system parameter value 'PAINFILE_CUST_DEFAULT'.
  • Skipping Field 72 code word validation for Customer Credit Transfer (MT 103) transactions based on system parameters.
  • Defining the list of applicable Transaction Type codes (or) Purpose codes for each of the Cross border / RTGS network codes and mapping for Transaction Type codes or Purpose Codes between Cross- border and RTGS networks; Validating the Transaction Type code (Field 26T) value inputted in Customer Credit Transfer (MT 103) transactions based on the list of applicable codes defined; Defining Non STP rules based on Transaction Type code field values; Mapping of Transaction Type code if the Inbound message network is different from the pass- through transaction network.
  • Populating the Outbound Customer Credit Transfer (MT 103) Regulatory Reporting (Field 77B) field based on the value received in the Transaction Type Code (Field 26T); Populating Transaction Type code (Field 26T) based on the value given in Field 77B Regulatory reporting for Outbound pass-through and Inbound transactions booked due to SWIFT messages upload; Defining Non STP rules based on rule elements related to Field 77B Regulatory Reporting value for Outbound / Inbound transactions; Populating the Transaction Type Code (Field 26T) based on value received in the Regulatory Reporting (Field 77B) for Outbound transactions booked via incoming MT 101.
  • Capturing the Account Status Enquiry service details in the External Credit Approval Interface (PMDINECA) maintenance; Defining Non STP Rules based on rule elements related to various account statuses like No Credit, Frozen, Dormant for the Credit Account and IBAN validations and moving the Incoming Cross-border / RTGS transactions to Non STP Queue.
  • Capturing Return preferences at Network Currency Preference (PMDNCPRF) level for Cross border / RTGS network codes.
  • Marking the Inbound / Outbound pass-through Customer Credit Transfer (MT 103) transactions for Return from Non STP Queue using cancel action resulting in transaction status updated as 'Return Initiated'; Initiating the outbound return transaction using the ‘Return’ user action introduced in the Outbound and Inbound Cross-border / RTGS Transaction View Summary screens; Capturing the original transaction reference in the Outbound Cross-border / RTGS transaction view screen and return transaction reference in the Inbound / Outbound pass-through Cross border / RTGS transaction view screen.
  • Capturing the MT195 message generation triggering event preference (PMDQFFMT) at the Non STP Rule level for Inbound SWIFT messages received via SWIFT and Capturing the MT195 message contents through a back-end table store; Logging the Inbound messages that are moved to Non STP Queue due to Non STP Rules marked for MT195 message generation; Generating the MT195 messages through a payment auto job (Preferably to be configured at the End of Day time).
  • Capturing separate account as charge account in the Inbound Cross-border / RTGS transaction input (PXDITONL) screen; Defaulting charge account maintained in Customer Preference screen (PMDFLPRF) as transaction charge account.; Handing off accounting entries for charge leg with force debit when different charge account is different from the credit account.

    Note:

    Feature not applicable for Customer Credit Transfer (MT 103) transactions with charge option as ‘OUR’.
  • Booking outbound charge claim settlement transaction (MT202 / pacs.009) with new UETR always.
  • Doing manual cover matching of payment message with cover messages without considering the value date as one of the matching criteria.
  • Marking messages in Inbound Unmatched Queue as Suppressed using a new user action 'Suppress' introduced in Unmatched Queue.
  • Defining rule-based pricing for Outbound / Inbound Customer Credit Transfer (MT 103) transactions based on the Transaction Type Code (Field 26T) field value.
  • Auto cancelling the Outbound Cross-border / RTGS Customer Credit Transfer (MT 103) transactions booked through uploads when the Charge Amount calculated is more than the Transfer Amount and Charge Whom option is BEN.
  • Deducting charges from credit account for incoming Cross-border / RTGS Customer Credit Transfer (MT 103) transactions with Charge Whom as OUR based-on Pricing Component level 'Borne By' flag value is 'Counterparty'.
  • Skipping the underlying transaction gpi check for Incoming Charge Claim (MT191) requests based on System Parameter.
  • Doing ECA check on the Outbound Claim settlement MT202 transaction booked for Incoming claim messages.
  • Populating the Correspondents in the Outbound Claim settlement MT202 transaction booked for incoming claim message when the original outbound MT103 was sent in cover settlement method.
  • Defining Currency Correspondent rules based on Field 58 Beneficiary Institution BIC for Outbound transactions.
  • Defining Cover Suppression rules based on Transfer Type and pass-through transaction flag for Outbound transactions.
  • Defining Verification rules based on debit account currency and pass-through flag for Outbound transactions.
  • Defining Pricing rules based on gpi Payment flag for Outbound / Inbound transactions.
  • Skipping defining network rules based on whether RMA is available for MT/MX message types for Creditor Agent BIC or Account with Institution BIC. Rule elements applicable for channel types ‘Single Payout’, ‘MT101’, ‘SWIFT’ and ‘SWIFT MX'.
  • Showing the Fields 70 – Remittance Information and Field 72 ‘Sender to Receiver Information in the ‘Transaction Preview’ screen in the Outbound Cross-border / RTGS Transaction Input (PXDOTONL) screen.
  • Showing the accounts of the payment transaction customer in the Charge Accounts LOV in the Outbound / Inbound Transaction Input screens.
  • Showing the original transaction remittance information and amendment request remittance information details in the Transaction Amendment Request Queue (PQSAMNAQ).
  • Updating the Message Status as 'Move to Sanctions Check Queue' when the incoming MT 202/205/202COV/205COV messages are meant for cover matching and when those messages are moving to sanctions check queue; Launching the Sanctions Check Queue for the 'View Queue (STP Layer)' user action when the Message Status value of the selected message is 'Move to Sanctions Check Queue'; Updating the Message Status as 'STP Cancelled' when the incoming payment messages getting cancelled from STP Layer exception queues like Business Override, Process Exception, Inbound Messages STP Queue; Launching the STP Layer Transaction View screen for the 'View Transaction' user action when the Message Status value of the selected message is 'STP Cancelled'.

Parent topic: Cross Border MT / RTGS MT Changes