- Cross Border User Guide
- Cross Border Outbound Transactions
- Outbound Transaction Input
- Outbound Cross Border Payments Transaction Input
- Main Tab
Main Tab
- Click the Main tab in the Outbound Cross Border Payments Transaction
Input screen.
Figure 4-2 Outbound Cross Border Payments Transaction Input_Main Tab
- On the Main tab, specify the fields.
For more information on fields, refer to the field description below:
Table 4-2 Outbound Cross Border Payments Transaction Input_Main tab - Field Description
Field Description Instructed Currency Indicator Select Instructed Currency Indicator from the following: - Transfer Currency - If the Instructed currency option is ‘Transfer Currency’ then the Instructed amount provided will be considered as the Transfer Amount.
- Debit Currency - If the option is ‘Debit Currency’, then the debit amount provided is to be input & Transfer amount is derived based on the Debit amount and transfer currency.
Payment Details -- Booking Date Booking date is read only field defaulted as the current logged in branch date. Instruction Date Select the customer advised Value Date of the transaction using the adjoining calender widget. Activation Date System retains the Activation Date input by the user. Also,Activation date is an optional field. If the activation date is not provided, system derives the same. Activation Date is calculated in the following way:
- The required number of days are present between activation date and instruction date taking into consideration the settlement days, float days and holidays
- Activation date is not a back date
- Activation Date is not a branch holiday
User can correct the dates and retry, if the entered validation fails. Error message id displayed for the same.
Note:
Future dated Cross Border transactions are processed on the booking date if activation date derived post deducting currency settlement days is current date.- If the payment request is received through web services, system will re-derive the activation date and proceed with the payment.
- If the transaction is moved to Network cut off queue, it is possible to provide Activation Date and Instruction date while performing Carry Forward action.
- The’ Value Date change’ action from Future Valued Queue allows providing a new Activation date & Instruction date
- For cross border transactions on Force release with a new instruction date, messages are generated with new instruction date in field 32A.
Transfer Currency Specify the currency in which the payment needs to be made. Alternatively, you can select the currency from the option list. The list displays all valid currencies maintained in the system. Note:
- If Transfer Currency is specified as CNH in an outbound transaction, then system checks whether CNH Conversion is required at host level.
- If CNH Conversion is maintained as yes in PXDCNHCN, then transaction is created with the currency as CNH. In the Outgoing message generated, the transfer currency is converted to CNY.
- If CNH Conversion is maintained as No in PXDCNHCN, transaction is processed and message is generated with CNH currency as per current functionality.
Transfer Amount Specify the Transfer amount, if Instructed currency indicator is Transfer Currency. If it is Debit currency, then the transfer amount is derived based on the Debit amount and Transfer currency applying exchange rate. Debit Account Specify the debit account of the transaction. Alternatively, user can select the debit account from the option list. The list displays all valid accounts maintained in the system. Debtor Name System defaults the Name on selecting the Debit Account. Debit Account Currency System displays the debit account currency based on the debit account selected. In case of Prefunded payment, where Debit happens on a GL, Debit Account Currency is considered same as Transfer Currency. In case if Debtor Account selected is a GL account, you can specify it from the list of values. Debit Currency Name System defaults account currency name based on the debit account number selected. Debit Account Branch System defaults Debit Account Branch based on the debit account number selected. Debit Amount Specify the Debit Amount for the transaction, if Instructed Currency Indicator is selected as Debit Currency. If it is selected as Transfer Currency, then this field is disabled and derived based on the Transfer currency, amount & Debit account currency. Exchange Rate The exchange rate is applicable for cross-currency transactions. The transaction is considered as cross-currency transaction if for an Outbound payment the debit account currency is different from the transfer currency. FX Reference Specify the foreign exchange reference. Local Currency Equivalent Local Currency Equivalent amount is populated on clicking of Enrich button while defaulting Debit / Credit Amount. Transactions that are received through services the Local Currency Equivalent amount is derived along with Debit / Credit amount values.
Transactions that are moved to Internal/External Exchange rate queue, the Local Currency Equivalent amount is rederived along with Debit / Credit amount values when user provides exchange rate manually to process the transaction further from Exchange Rate Queue.
Note:
Local Currency Equivalent Amount is derived as below:- If Debit Account Currency is same as Branch LCY, then Debit Amount is defaulted as Local Currency Equivalent amount.
- If Credit Account Currency is same as Branch LCY, then Credit Amount is defaulted as Local Currency Equivalent amount.
- If Debit Account Currency, Credit Account Currency and Branch LCY are all different, then the Local Currency Equivalent amount is derived by applying STANDARD-MID rate on the Credit Account Currency.
Customer Number
System defaults the Customer Number of the Debit Account selected. Charge Account Number
Specify the Charge Account Number by selecting an account number from the LOV. Charge/ tax amounts are debited to this Charge Account Number. If Charge Account is not available charge amounts are debited to the transaction debit account. Charge Account Branch
System defaults the Branch of the Charge Account selected. Charge Account Currency
System defaults the Account Currency of the Charge Account selected. SSI Label
Specify the required SSI label from the list of values. Valid SSI labels for the debit customer, network and currency is listed in the list of values. Enrich Button
Click on Enrich button upon providing the Payment details and the valid account number/ Payment Identifier based on the Transfer Type selected. This is mandatory. System defaults the debit/credit account details and payment chain building in the respective fields, based on the data entered.
Note:
This list is populated with valid SSI Labels, applicable for the customer and the Network. If Customer or Network details are not available, the fetch action of the list of values displays the information message to this effect. The list of values is queried based on the fields SSI Label, Beneficiary Bank ID, Beneficiary Account & Account IBAN.
If a valid Customer Preference maintenance (open & authorized) is found, then the Pricing account, Pricing account's currency and Pricing account's branch gets defaulted into Charge Account Number, Charge Account currency and Charge Account Branch respectively.
Charge account defaulting is done only if the Charge Account number is not provided by user at the time of clicking Enrich button.
Credit Account Specify the credit account of the transaction. Alternatively, you can select the Credit account from the option list. The list displays all valid accounts maintained in the system. Creditor Name System defaults the Name on selecting the Credit Account. Credit Account Currency System displays the credit account currency based on the credit account selected. Credit Currency Name System defaults account currency name based on the credit account number selected. Debit Entry on Select the Debit entry posting date preference from the following: - On Activation Date
- On Value Date
Credit Entry on Select the Credit entry posting date preference from the following: - On Activation Date
- On Value Date
Credit Value Date Credit Value Date is derived and displayed on clicking Enrich button. This is same as the Instruction date. Debit Value Date Debit Value Date is derived and displayed on clicking Enrich button. Activation Date is defaulted in this field, if Debit value date option at Network Preference is set as Activation Date. If the preference is Instruction date, then the Instruction date input above is copied on to this field. Message Date For Outbound transactions, the system computes the message date based on the credit value date and displays it here along with the cut-off time Ignore Settlement Days Check this flag if system should ignore the settlement days while deriving instruction/ activation dates. By default, this field value is unchecked. Remarks Specify any Operations remark or additional info pertaining to this transaction. Note:
On Outgoing Cross Border Transaction liquidation, Debit Advice is generated as per current advice framework, to the debtor, Advice tag '_REMARKS_' for Remark is available in the generated mail advice.
Bank Operation Code Select the bank operation code from the list of values. Options available are as follows:
- CRED – Credit Transfer with No SWIFT Service Level
- CRTS – Credit Transfer for Test Purposes
- SPAY – Credit Transfer for SWIFT Pay Service Level
- SPRI – Credit Transfer for Priority Service Level
- SSTD – Credit Transfer for Standard Service Level
If no value is selected then system defaults this field value to “CRED”.
Note:
This is applicable only for customer transfersBanking Priority Specify the priority of banking from the following: - Normal
- Urgent
- High
Charge Whom Specify the charge bearer for the transaction from the following: - OUR
- BEN
- SHA
Note:
For manual booking, if the customer does not select the 'Charge Whom' value, the System defaults 'Charge Whom' value for Transfer Type 'Customer Transfer' through System Parameter CHARGE_WHOM. It is also applicable for Cross Border Payment Template.50:Ordering Customer System displays the name and address of the customer ordering the transaction, based on the debit account selected. This is applicable only for ‘Customer Transfer’ type of transaction. The ordering customer details including name and address are defaulted based on the debit account selected. However you can modify these details.
Chinese code words are supported for Name and address fields of Ordering Customer. Refer Chinese Codeword Changes for more details.
52:Ordering Institution Specify the details of the financial institution that has ordered for the payment to be initiated. 56: Intermediary Bank Specify the details of intermediary bank which is the correspondent bank of Account with institution. Specify the below mentioned details of the intermediary bank.
- Specify the correspondent account number in the first line starting with “/”.
- Specify the bank identifier and bank code in the second and third lines. If the bank identifier is BIC then you can select the appropriate BIC code from the adjoining option list that displays all valid BICs maintained in the system.
Specify the Name and Address of the Intermediary bank instead of the BIC Code, in lines 4 to 7.
57: Account with Institution Specify the financial institution at which the beneficiary maintains their account. The beneficiary can be a retail/corporate in Customer Transfers or a Bank in case of Bank Transfers. Input is mandatory for ‘Customer Transfer’ type of transactions. - Specify the correspondent account number in the first line starting with “/”.
- Specify the bank identifier and bank code in the second and third lines. If the bank identifier is BIC then you can select the appropriate BIC code from the adjoining option list that displays all valid BICs maintained in the system.
- Specify the Name and Address of the Intermediary bank instead of the BIC Code, in lines 4 to 7.
Note:
The clearing code and mask validation failure results in error.
If payment chain building fails as BIC could not be derived, then the transaction fails with that error code. The above validations are applicable to pass through transactions as well. There is no Clearing code validations specified for fields 53, 54 & 55 in SWIFT manual, though it is possible to send or receive the clearing identifier for these parties.
58: Beneficiary Institution Specify the financial institution which is the ultimate recipient of the funds being transferred. This is applicable only to Bank Transfers.
Specify the below mentioned details of the Beneficiary Institution.
- Specify the account number in the first line starting with “/”
- Specify the BIC code in the second line. You can also select the appropriate BIC code from the adjoining option list that displays all valid BICs maintained in the system.
- Specify the Name and Address of the Beneficiary Institution instead of the BIC Code, in lines 3 to 5.
59: Ultimate Beneficiary Specify the details of the Ultimate Beneficiary of the payment. This field is available only for ‘Customer Transfer’ type of transactions. Specify the below mentioned details of the Beneficiary.
- In Line 1, specify the customer beneficiary account number to which the transaction amount should be credited. You can specify the IBAN of the account. Alternatively, you may search and select the account number using LOV if the beneficiary account is maintained with the bank, which is the case in Inbound payments. This field is available only for ‘Customer Transfer’ type of transactions.
- Specify the Name and Address of the Beneficiary in lines 2 to 5. Chinese code words are supported for Name and address fields. For more details, refer to the Chinese Codeword Changes section.
- Instead of the Name and Address, you can also specify the BIC code of the Beneficiary in line 2.
- IBAN validations is conditional
mandatory for Cross Border Outbound Payments
- If first 2 character of the Beneficiary Account number does not match IBAN ISO country code of the BIC (AWI BIC or the receiver BIC if AWI BIC not available), then the account number is treated as non IBAN.
- IBAN validation is skipped in this case, even if IBAN is mandatory for the country code derived from the BIC.
For example,
Beneficiary account is maintained as /2121212121, IBAN validation will not be done even if it is required for the country derived from the BIC.
- Let the country derived from BIC is ‘DE’ and the Account also starts with ‘DE’. System verifies whether- IBAN check is required for country code DE
- Whether there is a record available in IBAN Plus for the BIC with
- IBAN ISO country code as ‘DE’
- If yes, then IBAN format validation is done based on IBAN Structure applicable for DE.
- Let the country code derived from BIC is GB and the account number provided starts with ‘CH’- IBAN check is required for country code GB
- Whether there is a record available in IBAN Plus for the BIC with
- IBAN ISO country code as ‘CH’
- If yes, then IBAN format validation will be done based on IBAN Structure applicable for CH
- IBAN validation for ultimate beneficiary account is done by the system when BIC is present in tag 57(AWI) and IBAN check is set as required for AWI BIC’s country. System fetches the ISO country code from BIC code (5th & 6th char).
- IBAN validation is done based on the data maintained in the existing IBAN Information Maintenance (ISDESBAN)
- If BIC code is not present in tag 57, system fetches the ISO country code from the receiver of the payment. If IBAN check is required for the receiver country then system validates IBAN for ultimate beneficiary account.
- These validations are applied on Customer & Bank Transfer transactions, both on Origination from the system & for pass through cases.
Receiver Details -- Receiver System derives the Receiver (bank) of the Outbound payment message as part of Payment chain building activity and populates the BIC code of this bank in this field. This field is also populated on clicking Enrich button.
Select to override the system derived Receiver with a different BIC code and input the same over here. On save, system validates if a SWIFT message can be sent to the user specified Receiver BIC code.
Note:
The Receiver field is defaulted with the BIC of the Currency Correspondent when all the below conditions are satisfied:
- Resolved/User inputted Network is of type RTGS
- Transfer Type is Bank Transfer
- RTGS Network Account defaulted from Network Currency Preferences Maintenance (PMDNCPRF) is one of the Currency Correspondent accounts defined in Currency Correspondent Maintenance (PMDCYCOR).
- Currency Correspondent BIC is a valid participant of selected RTGS network (RTGS Directory maintenance - PMDRTGSD)
Receiver Description System defaults the description of the Receiver selected. Receiver of Cover System derives the Receiver of Cover (bank) of the Outbound payment message as part of Payment chain building activity if a Cover message is required to be sent in addition to the payment messages. The BIC code of this bank is populated in this field. This field is also populated on clicking Enrich button.
Select to override the system derived Receiver of Cover with a different BIC code and input the same over here. On save, system validates if the user specified Receiver of Cover is a currency correspondent and a SWIFT message can be sent to this BIC code.
Receiver of Cover Description System defaults the description of the Receiver of Cover selected. Processing Window -- Earliest Release Date System displays the Earliest Release Date. Earliest Release Time System displays the Earliest Release Time.
Parent topic: Outbound Cross Border Payments Transaction Input