Main Tab

  1. Click on Main Tab on the IMPS Outbound Payment Transaction Input Detailed screen.

    Figure 4-2 IMPS Outbound Payment Transaction Input Detailed - Main Tab

    Description of Figure 4-2 follows
    Description of "Figure 4-2 IMPS Outbound Payment Transaction Input Detailed - Main Tab"
  2. On Main Tab, specify the fields.

    For more information on fields, refer to the field description below:

    Table 4-2 IMPS Outbound Payment Transaction Input Detailed_Main tab - Field Description

    Field Description
    Debtor Details --
    Debtor Account Number Select the Debit Account Number from the list of values. All open and authorized accounts maintained in the India Payment Account Preferences (PMDEXACP) are listed for this field. System displays only the ‘Savings/Current' type accounts in the LOV.

    System defaults the following details on selecting the Debit Account Number and the details cannot be modified:

    • Debtor Account Type
    • Debtor Account Branch
    • Debtor Name
    • Customer No
    • Debtor Mobile Number
    • Debtor MMID
    • Debtor Bank Name
    • Debtor Bank IFSC Code
    Payment Details --
    Booking Date System defaults the current date as Booking Date. This is disabled for user modification.
    Instruction Date System defaults the current application server date. This date can be modified by the user. This is the requested execution date by the customer. Back dates are not allowed as instruction date.
    Activation Date Activation Date is derived from Instruction date and is disabled for modification.

    Since Network / Branch holidays are applicable for IMPS payments, activation date is same as instruction date. Payment is submitted to NPCI on Activation date and processed by NPCI on the same date.

    Transaction Currency System defaults the Transfer currency as ‘INR’. This field is disabled for modification.
    Transaction Amount Specify the Transaction Amount.
    Remarks Any internal remarks can be input in this field. This is a free text field of allowed character length ‘50’.
    Beneficiary ID --
    Beneficiary ID Select the Beneficiary ID from the list of values. This field fetches the Beneficiary IDs maintained for the debtor account number and beneficiary type combination.

    Note:

    • For the selected debtor account number, if IMPS transaction type selected is ‘P2A’, the LOV displays only beneficiary IDs of type ‘P2A’ with beneficiary details maintained in A/ C+IFSC section of beneficiary registration (PMDBENRN) for the network ‘IMPS’.
    • Similarly, for P2P IMPS transaction types, Beneficiary ID LOV, fetches only the P2P beneficiary type records maintained for the debtor account number.
    Beneficiary Details --
    A/C + IFSC System defaults the following A/C + IFSC details on selecting the valid Beneficiary ID:
    • Beneficiary Name
    • Beneficiary Account Number
    • Beneficiary Account Type
    • IFSC Code
    • Bank Name
    • Branch Name
    • Mobile Number and Email ID (if available)

    On saving the transaction, following validations are done by the system:

    • System validates if IMPS transaction type applicable is maintained in IMPS Outbound Payment Preferences (PJDNWOPF). If not input for IMPS transaction type, system throws a warning message ‘This Particular IMPS Transaction type <IMPS_TXN_TYPE> is not enabled. Unable to process’.
    • System validates if the values for the above fields (Beneficiary Name, Ben Account Number and IFSC Code) are present for the IMPS transaction type ‘P2A (A/C + IFSC)’. If not input, system throws a warning message ‘Please enter Beneficiary Name, Account Number, IFSC Code to proceed’.
    • System shows ‘Transfer to Overdraft, Cash Credit, Loan Account, Account is not allowed through IMPS.’ as per the beneficiary account type input.
    • System validates if the debtor account type is allowed for the Outbound Payment and Network Code as maintained in Account Type Restrictions screen (PJDACSTR). If the account type is not allowed for the network, system shows error message ‘This Account Type is not allowed for IMPS transfer.’ The transaction is moved to Process Exception queue.
      • If the validation is successful, it is moved to the next step of outbound processor.
      • In cases where beneficiary account type is not input, system still processes the transaction as validation successful.
    • System validates for ‘On-US Transfer’ (for P2P transfer within same bank) for Outbound IMPS as below:
      • System derives the NBIN based on the first four-digits of beneficiary MMID input at the transaction level.
      • Compare this derived NBIN with the NBIN maintained at the IMPS outbound payment preferences screen PJDNWOPF.
      • If found to be same, the outbound transaction is blocked and rejected. System shows the warning message ‘IMPS Transfer within the same bank is not allowed. Unable to Save’.

    Note:

    • All the fields in the grid, except Bank and Branch Name can be edited, only if the Beneficiary ID is ‘NULL’ (without beneficiary registration)
    • System does not allow the user to select same bank as that of remitter bank’s IFSC Codes as per the LOV restriction.
    • LOV Restriction condition: NBIN maintained in (PJDNWOPF) is equal to Bank IFSC Code (first four characters) as maintained in the screen NBIN Details (PJDNBIFS).
    MMID + Mobile Number System defaults the following MMID + Mobile Number details on selecting the valid Beneficiary ID:
    • Beneficiary Name
    • MMID
    • Mobile Number

    On saving the transaction, following validations are done by the system:

    • System validates if the values for the above fields (Beneficiary Name, MMID, Mobile Number) are present for the IMPS transaction type ‘P2P (MMID + Mobile Number)’. If not input, system throws a warning message ‘Please enter Beneficiary Name, MMID, Mobile Number to proceed’.
    • All the above fields are editable only if Beneficiary ID is ‘NULL’ (without beneficiary registration) and the debtor account number is not of ‘GL’ type.
    Enrich Button On clicking the Enrich button, system computes the Charges, and Tax on Charges if applicable, based on the maintenance for Transaction Pricing Code specified in IMPS Outbound Payment Preferences screen (PJDNWOPF).