4. RTGS Inbound Transaction Input
This chapter contains the following sections:
l Section 4.1.1, "India RTGS Inbound Payments Transaction Input"
l Section 4.1.2, "India RTGS Inbound Payment View"
4.1.1 India RTGS Inbound Payments Transaction Input
Inbound Payment transaction gets automatically created from the pacs.008.001.03/pacs.009.001.03 incoming message received from the RBI Clearing. The transfer type can be Customer Transfer/Bank Transfer/ Bank Transfer Own Account.
For any transaction entered from this screen, payment type is considered as ‘RTGS’ and transaction type as ‘Incoming’.
You can invoke ‘RTGS Inbound Payment Input Detailed’ screen by typing ‘PLDITONL’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button. Click ‘New’ button on the Application toolbar
.
Operations supported for Inbound Transaction
l New
– This option enables to create a new transaction as described above. The transaction reference number is generated based on format specified in this document.
l Delete
– This enables the user to delete unauthorized transactions from the system.
– If a transaction has been authorized at least once, deletion of the transaction is not allowed.
– After the transaction has been reversed and authorized, it is not possible to do further operations on the transaction.
l Copy
– This option enables copying an existing transaction details to create a new transaction. New Transaction reference number will be generated for the new transaction.
– All details of copied (existing) transaction are retained in the new transaction created.
You can specify the following fields:
Transaction Branch code
The system defaults the transaction branch code with the user’s logged in branch code.
Host code
The system defaults the host code of transaction branch.
Source Code
Select the Source Code via which the payment request is received from the list of values. All the source codes created in the host are listed here.
Network Code
You can select the required network. All open and authorized networks for a transaction and transfer type are listed.
Transfer Type
Select the required type of transfer.
l Customer Transfer
l Bank Transfer
l Bank Transfer own account
Transaction Reference number
The system generates the transaction reference number. For more information on the format, refer the Payments Core User Manual.
Incoming Message ID
Specify the Incoming Message ID if any.
Sender Transaction ID
Specify the Sender Transaction ID if any.
Sender End to End ID
Specify the Sender End to End ID if any.
Sender Instruction ID
The system defaults the Transaction Reference number. However, you can modify the same.
Credit to GL
This is a flag to enable credit to GL account.
4.1.1.1 Main Tab
Specify the following details
Creditor Details
Beneficiary Account Number
Specify the Beneficiary account number. Alternatively, you can select the Beneficiary account number from the option list. The list displays Loan Account numbers along other customer account.
Beneficiary Account Type
Select the Beneficiary Account type from the list of values displayed. Following are the options listed:
l Savings Bank (10)
l Current Account (11)
l Cash Credit (13)
l Loan Account (14)
l Overdraft (12)
l NRE (40)
Beneficiary Name
System defaults the Debtor Name of the account selected.
Creditor Account Number
Specify the Creditor Account Number from the list of values. The list displays all open and authorized Customer account and GL accounts.
Credit Account Currency
System defaults the Credit Account Currency of the Creditor Account Number selected.
Credit Account Branch
System defaults the Credit Account Branch of the Creditor Account Number selected.
Debtor Details
Debtor Account Number
Specify the debit account number.
Debtor Account Type
Select the Debtor Account type from the list of values displayed. Following are the options listed:
l Savings Bank
l Current Account
l Cash Credit
l Loan Account
l Overdraft
l NRE
IFSC Code
Specify the IFSC code of the Debtor
Debtor Name
System defaults the Debtor Name of the account selected
Payment Details
Transfer Currency
System defaults the currency as INR.Only INR is allowed for RTGS India Payments Booking Date.
Transfer Amount
Specify the Transfer amount.
Booking Date
The system defaults the booking date as application server date.
Instruction Date
The system defaults this date as application server date and the payment will be processed on the Instruction Date.
User can modify the date to a future date, if required. Back valued payments will not be allowed. Instruction date will be validated for network holidays maintained and error message will be thrown. User will be forced to change the instruction date to a working date for the network.
Activation Date
The system defaults the activation date same as application server date.
Credit Value Date
The system would derive the credit value date as part of transaction processing. This field will be disabled for user input.
Debit Value Date
The system would derive the debit value date as part of transaction processing. This field will be disabled for user input.
Instruction Priority
Instruction priority is maintained here. Allowed values are High, Normal. System defaults the value as ‘High’.
Charge Bearer
For RTGS, charges bearer information is maintained here. Allowed values are CRED/DEBT/SHAR/SLEV. System defaults the value as ‘DEBT’.
4.1.1.2 Additional Tab
Specify the additional details in this screen. Click on the ‘Additional’ tab to invoke this screen.
You can capture the address details of debtor/creditor and remittance information from the sender to receiver. These fields gets updated with values from the Inbound payment message.
For details pertaining to fields, please refer to section 2.3.1.2 Additional details Tab.
4.1.1.3 Pricing Tab
This tab displays the pricing details of the charges computed by system based on the transaction attributes in the Main tab..
The below mentioned attributes are available in the Pricing tab:
Pricing Component
Displays the Name of the pricing component applicable for the transaction.
Pricing Currency
Displays the Currency in which the charge amount is calculated for the Pricing component.
Pricing Amount
Displays the charge amount calculated for each pricing component.
Waived
Check this box to indicate that the charge is waived for the pricing component.
Debit currency
Displays the currency in which the charge amount is debited for the pricing component.
Debit amount
Displays the amount in debit currency to be debited.
4.1.1.4 UDF button
Click on the ‘UDF’ button to invoke this screen.
You can specify user defined fields for each transaction.
4.1.1.5 MIS button
Click on the ‘MIS’ button to invoke this screen.
You can specify the MIS details in this sub-screen.
4.1.1.6 Saving of Inbound Transaction
The system performs the mandatory field checks and the transaction validations, as mentioned below, during the save of RTGS Inbound payment transaction.
If any of the transaction validation fails, transaction will be rejected with proper error code.
For transaction created through upload of file or message, the transaction will be moved to repair queue.
4.1.1.7 India RTGS Inbound Payments Input Summary
You can invoke “India RTGS Inbound Payments Input Summary” screen by typing ‘PLSITONL’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button
.
You can search for the records using one or more of the following parameters:
l Transaction Reference
l Sender Instruction ID
l Source Reference
l Network Code
l Source Code
l Transaction Branch
l Booking Date
l Instruction Date
l Customer No
l Beneficiary Account Number
l Debit Account Number
l Authorization Status
l Transfer Type
l Credit to GL
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or select a record and click on ‘Details’ button to view the detailed maintenance screen.
4.1.2 India RTGS Inbound Payment View
You can view the RTGS Inbound transaction in this screen.
You can invoke “India RTGS Inbound Payments” screen by typing ‘PLDIVIEW’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button
.
l From this screen, click Enter Query. The Transaction Reference field gets enabled which opens an LOV screen.
l Click the Fetch button and select the required value.
l Along with the transaction details in the Main, Additional Details and Pricing tabs user can also view the Status details for the following:
– External System Status
– Transaction Status
– Pending Queue Details
l Click Execute Query to populate the details of the transaction in the Inbound India RTGS Payments View screen.
For more details on Main, Additional Details and Pricing tabs refer to ‘PLDITONL’ screen details above.
Note
The system generates Message type 'CREDIT_ADVICE' on credit to beneficiary account. This generation happens based on the 'Customer Advice Preference' (PMDCSADV) screen maintained per account & network combination.
4.1.2.1 Exceptions Tab
You can view the Return/Reject details and its references, if available in the Exception tab for the specified Transaction Reference Number. Click on the ‘Exceptions Tab’ to view the Return/Reject references.
4.1.2.2 View Queue Action Log
User can view all the queue actions for the respective transaction initiated. You can invoke this screen by clicking the ‘View Queue Action’ button in View screen, where the Transaction Reference Number is auto populated and related details are displayed.
Following details are displayed:
l Transaction Reference Number
l Network Code
l Action
l Remarks
l Queue Code
l Authorization Status
l Maker ID
l Maker Date Stamp
l Checker ID
l Checker Date Stamp
l Queue Status
l Queue Reference No
l Primary External Status
l Secondary External Status
l External Reference Number
User can view the request sent and the corresponding response received for each row in Queue Action Log.
Also you can view the request sent to and the response received from external systems for the following:
l Sanction screening
l External Account Check
l External price fetch
l Accounting system
4.1.2.3 UDF button
Click on the ‘UDF’ button to invoke this screen.
You can specify user defined fields for each transaction.
4.1.2.4 MIS button
Click on the ‘MIS’ button to invoke this screen.
You can specify the MIS details in this sub-screen.
4.1.2.5 View Repair Log
User can view all the Repair actions for the respective transaction initiated. You can invoke this screen by clicking the ‘View Repair Log’ button in View screen, where the Transaction Reference Number is auto populated and related details are displayed.
Following details are displayed:
l Queue Reference No
l Field Name
l Old Value
l Repaired Data
l Error
4.1.2.6 Accounting Entries
You can click the “Accounting Entries” link in the transaction input screen to invoke the screen.
The system displays the following details in a grid form that contains accounting entries in multiple rows:
Transaction Reference Number
Displays the Transaction reference number.
Event Code
Displays the Accounting event code.
Account
The system displays the transaction account number that is debited or credited in the accounting entry.
Account Branch
The system displays the account branch.
TRN Code
The system populates the transaction code of the accounting entry from the Account Template maintenance.
Dr/Cr.
The system displays whether the accounting entry is ‘debit’ or ‘credit’ leg.
Amount Tag
The system displays the amount tag of the Amount being debited/credited.
Account Currency
The system displays the transaction account currency.
Transaction Amount
The system displays the transaction amount being debited/credited.
Netting
The system displays if Netting of accounting entries is required.
Offset Account
The system displays the Offset Account of the accounting entry for posting the offset debit/credit.
Offset Account Branch
The system displays the Offset Account Branch.
Offset TRN Code
The system displays the Offset Transaction Code from the Account Template maintenance.
Offset Amount Tag
The system displays the Offset Amount Tag of the Offset amount.
Offset Currency
The system displays the Offset Amount Currency.
Offset Amount
The system displays the Offset Amount being debited or credited.
Offset Netting
The system displays if the Offset Netting is required.
4.1.2.7 All Messages Tab
Click the “All Messages” link in the View screen to invoke this sub-screen.
The system displays the following details in a grid form containing one or multiple rows for the Transaction Reference Number specified.
l Transaction Ref No
l Message Reference No
l Message Type
l Message Status
l Value Date
l Release Date
l Acknowledgement Status
l Duplicate Check Required
l Duplicate Status
l Direction
Note
You can click ‘Message’ button from the ‘All Messages’ sub screen to view generated camt.059.001.04 message.
4.1.2.8 India RTGS Inbound Payment View Summary
You can invoke “RTGS Inbound Payment View Summary” screen by typing ‘PLSIVIEW’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button
.
You can search for the records using one or more of the following parameters:
l Source Code
l Network Code
l Transaction Branch
l Transaction Reference
l Sender Transaction ID
l Sender End to End ID
l Booking Date
l Instruction Date
l Activation Date
l Transfer Currency
l Transfer Amount
l Transfer Type
l Debtor Account Number
l Debtor Account Type
l IFSC Code
l Beneficiary Account Number
l Beneficiary Account Type
l Queue Code
l Authorization Status
l Transaction Status
l Sanction Seizure
l Message ID
l Credit to GL
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or select a record and click on ‘Details’ button to view the detailed maintenance screen.
4.2 RTGS Inbound Payments Processing
4.2.1 India RTGS Inbound Payments Validations
The incoming RTGS payments are received as pacs.008.001.03/ pacs.009.001.03 messages from RBI Clearing. The beneficiary bank has to credit the beneficiary's account within 30 minutes of receiving the funds transfer message.
System parses and processes the payments messages based on predefined processing. steps.
Following Processing changes are covered as part of the process:
l Business Override Checks
l Process Exception Checks
l Network Validations
l Authorization Limit Check
l Future Valued Check
l Accounting Handoff
l SOD/EOD Message Processing
4.2.1.1 Initial validations
l RCLG accounting is not applicable for RTGS incoming payments on file upload.
l Resolution of transfer type based on pacs.008.001.03/ pacs.009.001.03 messages. The transfer type can be Customer Transfer/Bank Transfer/ Bank Transfer Own A/c.
4.2.1.2 Business Override checks
This is applicable for RTGS transfers as per current functionality.
4.2.1.3 Process Exception checks
l If Account Type and Account Number mapping is not done by the beneficiary bank or in case of account type mismatch, transaction moves to Process Exception queue.
l In case of account type mismatch (Beneficiary account type in the system and the account type sent in the message), transaction moves to Process Exception queue.
4.2.1.4 LEI Validation
l The system validates the Beneficiary LEI field value received in the incoming message when all below listed conditions satisfy as part of Repair Validations processing step:
– Transaction amount is more than the LEI Threshold Amount maintained in India Payments Common Preferences (PMDNFTPF).
– Beneficiary is a 'Non-Individual' .i.e. Customer Type is not 'Individual'.
l The incoming transaction moves to Business Override Queue (BO) when any of the below Beneficiary LEI validation fails:
– Beneficiary LEI is not available in the incoming message.
– Beneficiary LEI is available in the incoming message but there is no LEI captured at beneficiary customer level (no maintenance).
– Beneficiary LEI is available in the incoming message, but the LEI captured at beneficiary customer level is different from Beneficiary LEI value received.
– Beneficiary LEI is available in the incoming message, but the LEI captured at beneficiary customer level is expired (Expiry Date is less than value date of the transaction).
l On Approval from Business Override Queue, the transaction is processed further.
Note
l Beneficiary LEI is validated only for Customer Transfer (pacs.008) message for Incoming RTGS (Only Incoming NEFT / RTGS Customer Transfer in scope).
l Since the Beneficiary LEI is received in Line 2 of Sender to Receiver Information field and within '//BL/' & '/', the LEI is extracted and validated.
4.2.1.5 Network Validations
l Debtor/ Creditor/Bank/Additional details for a payment transaction is validated against valid characters allowed for the network. In case of Network character validation failure, transaction is moved to repair queue.
l IBAN check is not applicable for RTGS incoming payments.
Non-NRE A/c to NRE A/c Payment Check:
l System checks if the debtor’s account type belongs to Non-NRE account type. If there is no code word ‘NRE’ found in the below tags, the debtor’s account is identified as Non-NRE account,:
– Debtor Account: (<DbtrAcct> <Typ> <Prtry>): has ‘NRE’ code word.
– Remittance Information (Unstructured: <RmtInf> <Ustrd> Information Line 1): has ‘NRE’ code word.
l System will check the Beneficiary account type belongs to NRE account type. This is identified based on the code word ‘NRE’ found in the below tags:
– Creditor Account: <CdtrAcct> <Typ> <Prtry>: has ‘NRE’ code word.
l If it is resolved as Non-NRE a/c type to NRE a/c type payment, the incoming payment transaction is moved to the Repair queue. Available actions in the Repair queue are
– Repair. There is no change in the Repair processing logic.
– Return (Note: Returns Processing can be done only from ‘Repair’ Queue. Return processing is explained in detail in Return of Payments section.)
l In all other account type cases, the transaction moves to the next processing stage.
Validations for Repair Queue
l System validates whether account record is open and authorized.
l Beneficiary Name Check is done. If the validation fails, the incoming payment transaction is moved to the Repair queue.
l In cases of Invalid beneficiary account or Credit to FCY account, the inbound payment transaction is moved to the Repair queue.
l If Beneficiary account branch could not be derived based on the Beneficiary branch IFSC (:Creditor Agent) from the inbound pacs.008/pacs.009 message, then it is moved to the Repair queue.
4.2.1.6 Authorization limit check
Authorization limit check, has only one Auth Limit Queue.
4.2.1.7 Future Valued Check
This is not applicable for RTGS inbound payments.
4.2.1.8 FX Limit check
FX Limit check is not applicable for RTGS inbound payments.
4.2.1.9 Accounting Handoff
Post EAC Check successful, transaction accounting and accounting handoff is done.
Following entries are posted for the transaction booked:
|
Dr./ Cr. |
Account |
Value Date |
TXN_CCY |
|
Dr. |
Nostro Account |
Activation Date |
Account Currency |
|
Cr. |
Intermediary GL |
Activation Date |
Transfer ccy |
|
Dr. |
Intermediary GL |
Activation Date |
Transfer ccy |
|
Cr. |
Customer Account |
Activation Date |
Transfer ccy |
4.2.1.10 Notifications
Following notification is triggered, for the RTGS payment transaction received:
l Credit Notification to Beneficiary for inbound payment
Notification is sent to the external system, by further sending it to beneficiary advising the credit.
4.2.1.11 SOD/EOD Message Processing
l The camt.054 message sends the SOD/EOD messages to banks.
l After receiving the camt.054 message, the message is logged in a separate message log table. The message is logged into the RTGS Inbound Message Browser (PLSINBRW). The ‘Message Type’ field value is populated as ‘camt.054.001.03 SOD’ for SOD message and as ‘camt.054.001.03 EOD’ for EOD message.
4.2.1.12 Credit Confirmation Message Processing
The system performs following processing for India RTGS inbound customer transfer payment transaction (pacs.008.001.03):
l On successful credit accounting posting to the beneficiary account of the inbound customer transfer payment, system generates credit acknowledgement message camt.059.001.04.
l Credit acknowledgement message camt.059.001.04 generated is available to view from 'All Messages' sub screen of India RTGS Inbound Transaction View (PLDIVIEW).
l Credit acknowledgement message camt.059.001.04 generated is available to view from India RTGS Outbound message browser (PLSOUTBR).
4.3.1 India RTGS Inbound Message Browser
You can view all the Inbound RTGS messages such as pacs.008, pacs.009, admi.004, pacs.004, and camt.059 generated in this screen.
You can invoke ‘RTGS Inbound Message Browser’ screen by typing ‘PLSINBRW’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search for the records using one or more of the following parameters:
l Generated Reference Number
l Message Reference Number
l Received Date
l Message Type
l Message Status
Following sub screens/ actions are available in the message browser screen:
View Message
Select a record and click on ‘View Message’ button to view the message details. You can view the pacs.008, pacs.009, admi.004, pacs.004, camt.054 SOD, camt.054 EOD, and camt.059 message details here. System displays the following details with the respective fields.
l Message Reference Number
l Message
View Transaction
Select a record and click on ‘View Transaction’ to view the complete transaction details. You can view the details of pacs.008, pacs.009, admi.004, pacs.004, camt.054 SOD, camt.054 EOD, and camt.059 messages in the detailed view screen.
View Detailed screen (PLDIVIEW) is launched on clicking ‘View Transaction’.
Retry RTGS Inbound Message
On clicking Retry, RTGS Upload Retry sub screen is displayed.
On Retry action system re-process the upload of error records. On completion of the upload, Message status is marked as 'Processed'.
Retry action is enabled for pacs.008, pacs.009, pacs.004, camt.054,admi. 004, pacs.002 & camt.059 message uploads.
4.3.2 India RTGS Inbound Credit Confirmation Message Status Summary
You can view the matching status (Match, Pending Match) of incoming camt.059.001.04 message received in this screen.
You can also view any unmatched credit confirmation message that are not matched based on Transaction ID i.e. UTR, of the outbound customer transfer payment through this screen.
You can invoke ‘India RTGS Inbound Credit Confirmation Message Matching Status Summary’ screen by typing ‘PLSICRCN’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search for the records using one or more of the following parameters:
l Generated Reference Number
l Message Reference Number
l Received Date
l Message Status
l Branch Code
l Original Message ID
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.
4.3.3 Camt.054 Message Summary
This screen is to view Camt.054 debit and credit notification message received in system.
You can invoke ‘Camt.054 Message Summary’ screen by typing ‘PLSCMT54’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search for the records using one or more of the following parameters:
l Generated Reference Number
l Message Reference Number
l Received Date
l Message Type
l Matched Status
l Purpose Code
You can perform following actions:
View Message
System displays the message as it is received from RBI.
View Transaction
If selected transaction is Debit or Credit, RTGS Outbound Detailed View (PLDOVIEW) / RTGS Inbound Detailed View (PLDIVIEW) screen is launched respectively.