Inbound High Value Payments Transaction Input

You can create RTGS Inbound transaction. All transactions that are entered using this screen has payment type as ‘RTGS’ and transaction type as ‘Inbound’. Inbound RTGS transactions of transfer type – Customer Transfer (MT 103, MT 103+) or Bank Transfer (MT 202) – can be created from this screen. This screen should be used as a “fallback” mechanism for processing Inbound payments when the Inbound RTGS payment messages cannot be received automatically from SWIFT.

You can book RTGS Inbound transactions through Inbound Cross Border transaction screen. by selecting RTGS network in the ‘Network Code’.

On Homepage, specify PXDITONL in the text box, and click next arrow.
Inbound Cross Border Payments Transaction Input screen is displayed.

Figure 3-26 Inbound Cross Border Payments Transaction Input

Description of "Figure 3-26 Inbound Cross Border Payments Transaction Input"
Operations supported for Inbound Transaction.
- 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.
- 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.
  - Transaction in any of the exception queues can be reversed.
- 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.

On Inbound Cross Border Payments Transaction Input screen, specify the fields.

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

Table 3-13 Inbound High Value Payments Transaction Input - Field Description

Field	Description
Transaction Branch code	System defaults the transaction branch code with the user’s logged in branch code.
Branch Name	Displays the Branch Name
Host code	System defaults the host code of transaction branch.
Host Code Description	System defaults the description of the host code.
Source Code	System defaults the source code field. For manual transactions source code is defaulted as MANL.
Source Code Description	System displays the description of the Source code selected.
Transaction Reference number	System generates the transaction reference number. For more information on the format, refer the Payments Core User Manual.
Related Reference Number	System displays transaction reference number. However you can modify this.
Source Reference Number	Specify the Source Reference Number, if required.
Transfer Type	Select the required type of transfer: C - Customer Transfer B - Bank Transfer
Network Code	You can select the required network. All open and authorized networks for a transaction and transfer type are listed.
Network Code Description	System displays the description of the Network code selected.
gpi Enabled	System defaults the gpi Enabled.
Inbound gpi	Check this box to indicate the transparency between all the parties involved in payment chain, when the settlement is completed
UETR	UETR is Unique End to End Transaction Reference number. This is a reference number specific to the transaction which is used to track the transaction through the life cycle
Credit to GL	Check this flag to receive inbound payments from other systems internal to the Bank, for which actual credit is processed by that system itself. This flag indicates that the Inbound RTGS payment needs to be credited to a GL instead of a beneficiary customer account. Note: It is not mandatory to have a credit account /customer for the transaction if credit to GL flag is checked. On enrich or save the system populates the credit account as the ‘Intermediary Credit GL’ maintained for the source.

Parent topic: RTGS Inbound Transaction