3.2.3 Features

Support for:

  • Validating Role level / User level limit amounts for manually booked Outbound / Inbound FI to FI Customer credit Transfer (pacs.008), FI Credit Transfer (pacs.009) and Liquidity Credit Transfer (camt.050) transactions.
  • Allowing the authorizer to reject (or) send to maker for modification of manually booked Outbound / Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions.
  • Generating the messages immediately after Payment Chain building process and an option for user to preview the messages in the transaction Messages sub screen. This feature supported for Outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions.
  • Allowing user to modify the Future Valued Outbound / Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions in Warehouse Queue using ‘Modify’ user action.
  • Processing Outbound / Pass-through FI-to-FI Customer Credit Transfer (pacs.008), Outbound Payment Return (pacs.004) transactions and Pass-through FI Credit Transfer COVER (pacs.009) with only Name (without Address Lines) in Parties - Debtor / Creditor / Initiating Party / Ultimate Debtor / Ultimate Creditor.
  • Defaulting debit account IBAN as Debtor IBAN value in the Outbound FI to FI Customer Credit Transfer (pacs.008) transactions based on the Source / Network level preferences (Function ID: PMDSORNW).
  • Defaulting the BIC code associated with the Debit Account and populating BIC code in the outgoing pacs.009 message when Debtor Account number is provided in the Outgoing pacs.009 message.
  • Defaulting of customer LEI from Customer LEI Preferences Maintenance (Function ID: PMDEXLEI) for Outbound FI to FI Customer Credit Transfer (pacs.008) transactions.
  • Defaulting Sender BIC, Creditor details on Enrich user action while booking inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions manually.
  • Showing only the accounts of the payment transaction customer in the Charge Accounts LOV in the Outbound / Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transaction input screens.
  • Moving the Outbound FI to FI Customer Credit Transfer (pacs.008) transactions booked through Incoming SWIFT MT 101 and SWIFT CBPRPlus pain.001 messages to NON STP Queue by allowing user to define Generic Wires ISO transaction related rules in NON STP rules for Channel Type ‘MT101’.
  • Defining Non STP rules based on the Account Identification field and various account status values and moving the transaction to Non STP Queue based on the defined rules. Account status values are referred by calling the Service exposed by FCUBS.
  • Inputting values in ‘Purpose Proprietary’ field from an LOV field, validating the ‘Purpose Proprietary’ field valued based on system parameter value for manually booked transactions, Defining Non STP rules based on rule elements introduced for Purpose Code / Proprietary field values and Defining rule-based pricing based on the Purpose Code or Purpose proprietary field value.
  • Mapping the data received in existing Sender's charges and Receiver's charges fields of Single Payout Service to Outbound FI to FI Customer Credit Transfer (pacs.008) transactions.
  • Mapping the newly added Structured Remittance, Regulatory Reporting, Related Remittance, Settlement Time Requirement and Structured Address fields in Single Payout Service to Outbound FI to FI Customer Credit Transfer (pacs.008) and to Outbound FI Credit Transfer (pacs.009) transactions.
  • Deriving the ISO Clearing code from the 2-character SWIFT network code value while booking Outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions via Single Payout service.
  • Booking Standing Instruction Templates and defining Standing Instructions for FI-to-FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions.
  • Deriving credit account from the creditor BIC received in Inbound FI-to-FI Customer Credit Transfer (pacs.008) / FI Credit Transfer (pacs.009) messages using BIC Code Customer (Function ID: ISDBICPB), External Customer Account (Function ID: STDCRACC) and BIC Code Account Details (Function ID: PSDBICAC) maintenances.
  • Deriving transaction type as Incoming for Incoming FI Credit Transfer (pacs.009) messages without having Creditor Agent based on Creditor BIC being a Vostro correspondent.
  • Moving incoming FI to FI Customer Credit Transfer (pacs.008), FI Credit Transfer (pacs.009) transactions to Network Cutoff queue if transaction is initiated after network cutoff time and for moving incoming transaction to Non STP queue on the processing date.
  • Doing messaging only on successful completion of accounting entries posting processing and after network cutoff validations and updating Transaction Status as ‘Processed’. Transaction Status is set as ‘Exception’ till the accounting is pending in Accounting Queue.
  • Making Assignment Identification field in Outbound FI to FI Cancellation Request (camt.056) Input screen as an editable field, defaulting Assignment Identification field with the value as NONREF on clicking Enrich user action and allowing user to modify the defaulted value.
  • Populating the transaction reference generated or the external system reference received in the Instruction Identification field of Single Payout Request to the newly introduced ‘Source Reference Number’ field in Outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions and populating either the Transaction Reference (or) Source Reference as Instruction Identification in generated messages; Populating the Source reference in Outbound Debit Confirmation (camt.054) message for outbound transactions; Populating the incoming message Instruction Identification as the Source Reference Number for pass-through outbound / for outbound booked via uploaded Customer to Bank pain.001 and SWIFT CBPRPlus pain.001 and Populating Source reference Number in the gpi / Universal confirmation messages generated for pass-through transactions; Populating Source reference Number in the Sanction handoff and accounting handoff request.
  • Putting the generated Outbound messages on Hold and releasing them or suppressing the generated Outbound messages based on the Message Hold Release (PMDHSRLP) rules defined.
  • Earliest Release Date / Time feature for Outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions.
  • Deriving Debit / Credit Entry on values for Outbound transactions FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) based on Source Network Preference and handing off the accounting entries on the entry date – Activation Date or Value Date.
  • Capturing separate account as charge account in the Inbound FI to FI Customer Credit Transfer (pacs.008), FI Credit Transfer (pacs.009) Transaction Input screens and defaulting charge account maintained in Customer Preference screen (PMDFLPRF) as transaction charge account. Handing off accounting entries for charge leg with force debit when charge account is different from the credit account.

    Note: Feature is exempted for pacs.008 transactions with Charge Bearer as ‘DEBT’.

  • Auto booking of Payment Return / Reject transactions for the Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions based on the Credit Account validations related error codes to Return or Reject mapping done (Function ID: PSDRJTRM).
  • Suppressing the Outbound Payment Return (pacs.004) or Payment Reject (pacs.002) message generation, accounting entries posting and confirmation message generation for Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions.
  • Suppressing the Outbound Payment Return (pacs.004) (or) the Outbound Payment StatusReport (pacs.002) message for the cover leg when the incoming SWFT CBPRPlus FI to FI Customer Credit Transfer (pacs.008) transaction with Settlement Method as 'COVE' is getting returned based on a system parameter value.
  • Performing Cross validation / Network Validation rules for Outbound Payment Return (pacs.004) transactions - Charges Information, Creditor Agent, Return Instructed Amount, Currency, Return Exchange Rate fields.
  • Marking the Incoming Payment Status (pacs.002) transaction status as "Suppressed" if Incoming Payment Status (pacs.002) message received for outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer ADVICE (pacs.009 ADV) transactions having Settlement Method as Cover without any processing.
  • Validating duplicate check on the incoming SWIFT CBPRPlus Interbank Customer Credit Transfer Initiation (pain.001) messages based on Host Code, Sender, Message Identification (Under Group Header) fields and Moving to Business Override Queue for user action.
  • Doing auto cover matching of incoming FI Credit Transfer Advice (pacs.009 ADVICE) against Nostro account statement entries populated in Statement Browser (Function ID: PMDSTBRW).
  • Capturing the Settlement Instruction Label (SSI Label) and defaulting the settlement instructions based on SSI label value for Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions.
  • Generating the un-generated and suppressed outbound messages in Outbound Message Browser (PMSOUTBR) manually.
  • Modifying the incoming XML message that are in Inbound Message Browser with status as Repair and Submitting the repaired message for Reprocessing on authorization.
  • Generating Notification on successful processing, on cancellation, on moving to Future Valued Queue of Outbound FI to FI Customer Credit Transfer (pacs.008), Outbound FI to FI Credit Transfer (pacs.009) transaction processing and populating the underlying message ISO message type value in the notifications. Generating Notification on receiving inbound Payment Return (pacs.004) and Payment Status Report (pacs.002) for Outbound FI to FI Customer Credit Transfer (pacs.008), Outbound FI to FI Credit Transfer (pacs.009) transactions.
  • CNY CNH Currency conversion in all the Outbound / Inbound SWIFT CBPRPlus messages and in all the Outbound / Inbound SWIFT gpi / Universal confirmation messages.
  • Validating process cut-off checks for transactions booked via Single Payout service against the Checker date & time value received in service request and for transactions via C2B pain.001 uploads based on Creation Date Time field value received in file upload.
  • Reversing the Inbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions manually; Posting reversal accounting entries. Reverse action opens the Outbound Payment Return (pacs.004) with Return Type as ‘Reverse’.
  • Capturing Factory-shipped ISO 2-Char country codes and Listing factory-shipped ISO 2-Char country codes in the Country Code field of Structured Address maintenances - Customer Structured Address (STDCRCAD) / Account Structured Address(STDACCAD) and in the Country Code, Country of Residence fields of Generic Wires ISO Outbound / Inbound Transaction Input screens. Option to map the 3-Char country code defined in Common Core Country Code maintenance with the ISO 2-Char country code and defaulting ISO 2-Char country code in the Generic Wires ISO transaction screens by mapping 3-Char country code given in the customer / address maintenances.
  • Displaying Sanctions / ECA Queue Cancellation Reason details on Inbound / Outbound cancelled pacs.008/pacs.009 transaction viewscreens.
  • Charge Claim Processing – For Outbound Claims, Income entry posting is done on realization of claim amount when the newly introduced system parameter ‘REALIZED_INCOME_FOR_CLAIMS’ value is set as ‘Y’ instead of posting entry at the time of claim message generation.
  • Reversing the Outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transactions via Service and Posting reversal accounting entries.
  • Deriving Transaction Code based on Transaction Code rules for Return and Reversal transactions.
  • Defining Standard or Rule-based Pricing for Outbound Payment Return (pacs.004) transactions, posting charge accounting entries and populating the charges information details in the Outbound message.
  • Generating Debit Confirmation and Credit confirmation in SWIFT MT format for FI-to-FI Customer Credit transfer (pacs.008), FI Credit transfer (pacs.009), Payment Return (pacs.004) transactions. based on the format preference selected in the Bilateral Agreement (PMDCMAGT) maintenance. Generating Debit Confirmation and Credit confirmation in Mail format for Outbound / Inbound FI to FI Customer Credit Transfer (pacs.008), FI Credit Transfer (pacs.009) and Payment Return (pacs.004) transactions.
  • Populating Remittance Information, Instruction for Next Agent details of FI-to-FI Customer Transfer (pacs.008) in the Debit Credit Confirmation advice generated in ISO (camt.054) format.
  • Populating Confirmed Amount considering charges excluding Counterparty charges (Credit Amount minus Charge Amount) in Universal Confirmation (trck.001) - Credit Confirmation.
  • Skipping book dated validations for both outbound /inbound Generic Wires transactions based on the parameter for Booking dated processing set in Source Network Preferences. The following processing steps are completed before moving the transactions to Future Valued Queue:
    • Mandatory field checks
    • Upfront reject validations
    • Routing rules

      If the Activation Date is in future, the transaction status is marked as ‘Future Valued’ and the transaction is moved to Future Valued Queue without further processing. Non STP validations are applicable on release from Warehouse queue.

  • Showing the Network Status and Clearing System Reference values in the Outbound FI to FI Customer Credit Transfer (pacs.008) and FI Credit Transfer (pacs.009) transaction view screens. Generating Network status Notification ‘NETWORK_STATUS’ after processing Inbound Payment Status Report (pacs.002) and when the Notification preference is enabled.