You can do fund transfer between two accounts of the same bank in Payments. Account to account transfers can be initiated as single payments or can be initiated as a part of bulk file uploads. A network of type "Book Transfer” has to be maintained in Network Maintenance (PMDNWMNT) for supporting book transfer transactions. ‘Book Transfer’ is the payment type attached for this network. Payments can be initiated with this Payment type only if both credit and debit accounts are available in External Account Maintenance. Payment type ‘Book transfer’ allows only ‘outgoing’ transaction type.
This chapter contains the following sections:
This section contains the below topics:
You can initiate book transfer transaction between accounts of the bank using ‘Book Transfer Input’ screen. You can invoke “Book Transfer Input” screen by typing ‘PBDOTONL’ 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..
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
For manually input transactions source code is defaulted as ‘MANL’. For transactions received through web services or rest services, the source code is populated as received in the request.
Network Code
This field would always get defaulted network maintained with payment type as 'Book Transfer’.
Transaction Reference number
The System generates the transaction reference number. For more details on the format, refer the Payments Core User Guide.
User Reference Number
The system defaults the transaction reference number as user reference number. However you can modify this.
Save as Template
Check this box to facilitate creation of new templates.
Prefunded Payments flag
Check this flag if debit account has to be replaced by Pre-funded Payment GL.
Credit to GL
Check this flag to if credit account has to be replaced by Intermediary Credit GL.
Note
You can capture Debtor/ Creditor and payment details in this screen.
Specify the following details:
Debtor Account Number
Specify the debtor account number. Alternatively, you can select the debtor account number from the option list. The list displays all open and authorized accounts maintained in the ECA-CIF account mapping.
Account IBAN
The system displays the Account IBAN of the debtor account based on the selected Debtor Account Number.
Account Branch
The system defaults account branch based on the debtor account number selected.
Account Currency
The system defaults account currency based on the debtor account number selected.
Debtor Name
Specify the debtor name.
Debit Amount
The system populated the debit amount based on the credit amount and exchange rate between debit/credit currencies.
SSI Label
Select the required SSI label from the list of values.
Note
This list will be populated with valid SSI Labels, applicable for the customer and the Network.
Creditor Account Number
Specify the creditor account number. Alternatively, you can select the creditor account number from the option list. The list displays all open and authorized accounts maintained in the External Account Maintenance.
Account IBAN
The system displays the Account IBAN of the Creditor account.
Account Branch
The system defaults account branch based on the creditor account number selected.
Account Currency
The system defaults account currency based on the creditor account number selected.
Creditor Name
The system displays the creditor name.However you can modify it.
Credit Amount
Specify the credit amount.
Booking Date
The system defaults the booking date as the application server date.
Instruction Date
The system defaults the instruction date as current system date. However you can select a future date. Debit currency, credit currency and network holiday checks are applicable for instruction date
Note
Activation Date
Activation Date is derived as Instruction date minus Debit Float Days as maintained in process cut off maintenance. Holiday check is done for activation date based on Branch Holidays maintained if Branch Holiday Check is applicable in Network Preferences.
Specify the exchange rate if debit account currency and credit account currency is different. The system retains the input value and validate the same against override and stop variances maintained in the Network preference.
Note
Enrich button
Enrich button is provided in transaction input screen to populate exchange rate, debit amount and charge/tax amounts.
Note
If exchange rate pick up or charge pick up fails, system will throw error.
For Book Transfer payments transaction, Charge/ Tax is applied based on the pricing code linked in the Network Currency Preferences (PMDNCPRF).
You can view and modify charge/tax details from this screen..
Specify the following details:
Pricing Component
The system defaults the pricing component based on the pricing code.
Pricing Currency
The system defaults the pricing currency.
Pricing Amount
The system defaults the pricing amount from Pricing Value Maintenance screen (PPDVLMNT) as applicable for the payment value date, Payment Source code & Debit Customer Service Model. However you can modify this value.
Note
If rate is maintained for Charge/Tax, then the same is applied on transfer amount and final amount that will be populated component wise in the Pricing tab.
Waiver
Check this box to waive a charge/tax component.
Debit Currency
The system displays the debit currency.
Debit Amount
The system displays the debit amount.
Click on the ‘UDF’ button to invoke this screen.
You can specify user defined fields for each transaction.
Click on the ‘MIS’ button to invoke this screen.
You can specify the MIS details in this sub-screen.
You can invoke “Book Transfer Summary” screen by typing ‘PBSOTONL’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.
You can search using the following parameter:
Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.
This section contains the below topics:
You can view the Book Transfer outgoing transaction in this screen. You can invoke “Book Transfer View” screen by typing ‘PBDOVIEW’ 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..
You can specify the following fields:
Transaction Reference Number
Query the existing book transfer details from the view screen by entering the transaction reference number. Alternatively, you can select the transaction reference number from the option list. The list displays all valid transaction reference numbers maintained in the system.
The system displays all the fields in the below mentioned tabs based on the transaction reference number selected.
You can view debtor/Creditor details in this screen. Click on the ‘Main’ tab to invoke this screen.
You can view pricing details in this screen. Click on the ‘Pricing’ tab to invoke this screen.
Click on the ‘Accounting Details’ tab to invoke this screen.
You can view the consolidated accounting entries of the transaction.
Click on the ‘UDF’ button to invoke this screen.
You can specify user defined fields for each transaction.
Click on the ‘MIS’ button to invoke this screen.
You can specify the MIS details in this sub-screen.
Book transfer request from web services or REST services are processed in ACH payment.
Following fields are mandatory in the request required:
For transactions received through web services or REST services, the source code will be defaulted as received in the request.
This section contains the below topics:
System performs below mentioned checks while saving a transaction:
For ‘Book Transfer’ payment types, and branch holiday checks are performed.
Below mentioned fields are mandatory in the request for ACH transaction:
Following parameters are validated with the static maintenances available for existence of the values:
If any of the above mentioned validation fails then the transaction will be rejected with an error message.
For transactions received from channels or bulk file, if the payment value date falls on a local branch holiday, then based on network preferences the value date is moved forward to nearest working date. A message is displayed on transaction booking to indicate the value date change. Initial value date will be stored as instruction date internally.
If transaction value date is a future date, then transaction processing follows future dated transaction specific process flow.
For a current dated transaction, processing is done during transaction authorization in the following order:
Accounting entries for credit and debit accounting are handed off to accounting system with debit/credit liquidation accounting code linked at Network Currency preferences.
As a part of debit/Credit liquidation, the following details are sent to accounting system:
Values handed off for Accounting | Debit Liquidation | Credit Liquidation | ||||
---|---|---|---|---|---|---|
Event | DRLQ | CRLQ | ||||
Amount Tag | XFER_AMT | XFER_AMT | ||||
*Transaction Account | Debit Account | Credit Account | ||||
Offset Account | This is maintained as part of accounting code | This is maintained in accounting system as part of accounting code | ||||
Transaction Currency | Debit Account Currency | Credit Account Currency | ||||
Transaction Amount | Debit Amount | Credit Amount | ||||
Value Date | Transaction Value Date | Transaction Value Date | ||||
Offset Currency | Credit Currency | Credit Currency | ||||
Offset Amount | Credit Amount | Credit Amount | ||||
Local Currency Amount | If either debit currency or credit currency is local currency, corresponding amount will be handed off as local currency amount | If not, debit amount will be converted to local currency in mid rate. | Local currency amount of DRLQ will be used |
Charge/tax related entries are handed off along with debit liquidation details. Transaction code, Debit/Credit indicator and Netting flag is applicable based on accounting code maintained.
If debit and credit liquidation are on same day, then the credit entries are sent with debit entries in a single hand off.
Following notifications are supported for Book Transfer transactions for the following processing stages:
On debit/credit liquidation and cancellation of the payment from queues, notifications are generated with all payment details in the common format.