Payment Integration Bulk Telegraphic Transfer Format ... · Payment Integration Bulk Telegraphic Transfer Format Specifications ... Payment File Format ... All fields’ values must

Payment Integration Bulk Telegraphic Transfer

Format Specifications

Prepared by: Group Transaction Banking, Product Management

Electronic Delivery Channels

Date: Sep 2017

Content

1. Introduction ....................................................................................................................... 3 2. Payment File Format (from Customer to UOB) ................................................................. 5

2.1 File Control Header ................................................................................................... 6 2.2 Batch Header ............................................................................................................ 6 2.3 Batch Details ............................................................................................................. 7 2.4 Payment Advice format (Free Format) .................................................................... 11 2.5 Batch Trailer ............................................................................................................ 11

3. Fate File Format (from UOB to Customer)...................................................................... 12 3.1 Batch Header .......................................................................................................... 13 3.2 Batch Detail ............................................................................................................. 13 3.3 Batch Trailer ............................................................................................................ 14

4. Acknowledgment (Applicable to FTS/FileAct) ................................................................. 15 4.1 Acknowledgement Types ........................................................................................ 15 4.2 File Submission and Acknowledgement Scenarios ................................................. 15 4.3 Email Alert ............................................................................................................... 16

Appendix 1 Payment Advice .................................................................................................. 17 Appendix 2 Remittance Information ....................................................................................... 19 Appendix 3 ISO Country Codes ............................................................................................. 20 Appendix 4 Hash Algorithm ................................................................................................... 21 Appendix 5 Value Date .......................................................................................................... 23

Bulk Telegraphic Transfer Format Specification Version 2.5

Page 3 of 24

1. Introduction This document describes the format and mapping definition for the fixed file format of Bulk Telegraphic Transfer (TT). The bulk file can be uploaded through File Transfer Service (FTS), FileAct and BIBPlus. This information is intended for business users and IT departments that use this payment service.


Page 4 of 24

LEGEND OF COLUMN

COLUMN NAME EXPLANATION

FIELD DESCRIPTION Indicates the field name.

TYPE

Text

- Left justified with trailing spaces - Alpha-numeric, numeric or characters

Amount

- Right justified with leading zeros - 2 decimal places without decimal point - Example: 123.45 is presented as 000000000012345 Quantity

- Right justified with leading zeros Code

- Indicates pre-defined values Date

- Format in YYYYMMDD Time

- Format in HHMMSS

POSITION Indicates the starting position of the field.

LENGTH Indicates the length of the field.

MANDATORY

“Y” indicates a mandatory field “N” indicates an optional field “C” indicates fields which are conditional i.e. mandatory only if certain remittance conditions or other fields are used. Additional information provided in Remarks column.

REMARKS List the possible values, constraints, further explanations, etc.


Page 5 of 24

2. Payment File Format (from Customer to UOB) Record Size : 1800 File Structure : File Control Header (1 line) – refer to section 2.1 Batch Header (1 line) – refer to section 2.2 Batch Details (1 to multiple lines) – refer to section 2.3 Payment Advice (optional; multiple lines) – refer to section 2.4 Batch Trailer (1 line) – refer to section 2.5 File Naming : For FTS

File Name: UTPIddmmNN.txt

U UOB

TP Telegraphic Payment

I Incoming file from customer to bank

ddmm Date and month the file was created

NN Sequence Number, up to 99 payment files per day

Example: UTPI251001.TXT The above is a TT payment file sequence number 01 created on the 25

th of October.

For FileAct

File Name: CC_UTPIddmmNN_BIC.txt

CC Country Code

U UOB


I Incoming file from customer to bank



BIC Sender BIC (11 Characters)

Example: SG_UTPI251001_TELPSGS1XXX.txt The above is a TT payment file sequence number 01 created on the 25

th of October.

For BIBPlus

Filename need not conform to the above naming convention Filename has to be unique and contains a file extension

Examples: TTPayment1.txt, TTPayment2.txt ……etc


Page 6 of 24

2.1 File Control Header

# FIELD

DESCRIPTION TYPE POSITION LENGTH MANDATORY REMARKS

1 Record Type Code 1 1 Y Must be "0".

2 File Name Text 2 10 Y

Must match with filename excluding the “.txt” extension, examples:

“UTPI251001” for FTS

“TTPayment1” for BIBPlus

3 File Creation

Date Date 12 8 Y

Must not be later than current date.

Must not be earlier than 30 days from current date.

4 File Creation

Time Time 20 6 Y

5 Company ID Text 26 12 C Mandatory for FTS/FileAct, this is to be provided by the bank.

6 Check

Summary Quantity 38 15 Y

File check summary (i.e. hash total) for validating the file integrity.

Refer to Appendix 4 for the Hash Algorithm.

7 Company ID Text 53 12 C Mandatory for FTS/FileAct, this is to be provided by the bank.

8 Filler Text 65 1736 N To fill with spaces.

2.2 Batch Header

# FIELD

DESCRIPTION TYPE POSITION LENGTH MANDATORY REMARKS


2 Bulk Customer

Reference Text 2 20 N

For customer’s internal use to reference their bulk file.

3 Payment Advice Header Line 1

Text 22 105 N Refer to Appendix 1 for Payment Advice.

4 Payment Advice Header Line 2

Text 127 105 N Refer to Appendix 1 for Payment Advice.



Page 7 of 24

2.3 Batch Details There should be at least one batch detail record. All fields’ values must be SWIFT compliant. Do not use the characters below as they are NOT SWIFT-compliant; failure to comply may result in delays in the payment processing.

` ~ ! @ # $ % ^ & * _ = < > [ ] { } \ | "

# FIELD DESCRIPTION TYPE POSITION LENGTH MANDATORY REMARKS

1 Record Type Code 1 1 Y Must be "2”.

2 Payment Type Code 2 3 Y Must be “TT ”.

3 Payment Currency Code 5 3 Y Refer to Appendix 3 for the currency list accepted by the bank.

4 Payment Amount Amount 8 15 Y

5 Value Date Date 23 8 Y Refer to Appendix 5 for Value Date

6 Payment Detail (Line 1) Text 31 35 C

Mandatory to some countries or for certain currencies.

Refer to Appendix 2 for Remittance Information.

7 Payment Detail (Line 2) Text 66 35 N Same as above



10 Beneficiary Name and

Address (Line 1)

Text 171 35 Y

Will be printed on first page of payment advice.

Refer to Appendix 1 for Payment Advice.




Address (Line 2)

Text 276 35 Y




Address (Line 3) Text 311 35 N Same as above


Address (Line 4) Text 346 35 N Same as above


17 Beneficiary Country

Code Code 396 3 Y

Refer to Appendix 3 for ISO Country Codes.


19 Beneficiary A/C No.

Text 402 34 Y

Only alphanumeric values are accepted i.e. no space, no bracket “( )”, no dash “-“, no slash “/”, etc. are allowed.

Use IBAN for payments to Europe or other countries where IBAN is required.

20 Beneficiary Bank Name

and address (Line 1) Text 436 35 Y


and address (Line 2) Text 471 35 N


Page 8 of 24






24 Beneficiary Bank

Country Code Code 576 3 N


25 Filler Text 579 3 N To fill with spaces

26 Beneficiary Bank

SWIFT Code Code 582 12 C

Mandatory if payment to country where Beneficiary Bank Clearing Code is not required.

27 Beneficiary Bank Clearing Code

Code 594 30 C

Mandatory if payment to some countries or certain currencies.


28 Beneficiary Bank

Clearing Code Type Code 624 4 C


29 Intermediary Bank Name and address

(Line 1) Text 628 35 N







33 Intermediary Bank

Country Code Code 768 3 N




SWIFT Code Code 774 12 N

Same as Beneficiary Bank SWIFT Code


Clearing Code Code 786 30 N

Same as Beneficiary Bank Clearing Code


Clearing Code Type Code 816 4 N

Same as Beneficiary Bank Clearing Code Type

38 Sender to Receiver Info

Line 1 Text 820 35 N

To fill with spaces if not required.










42 Party bearing Bank’s

Charges

Code 960 3 Y

“SHA” – UOB Singapore bank charges paid by customer

“OUR” – Local and Overseas bank charges paid by customer

“BEN” – Local and Overseas bank charges paid by beneficiary


Page 9 of 24


43 Debiting A/C No.

Code 963 20 Y

Right justified with leading zeros.

Only numeric values are accepted i.e. no space, no bracket “( )”, no dash “-“, no slash “/”, etc. are allowed.

44 Debiting A/C Currency Code 983 3 Y e.g. “SGD”, “USD”

45 FX Contract 1


Reference number for FX contract.

Below list of characters are not allowed ` ~ ! @ # $ % ^ & * _ = < > [ ] { } \ |

46 Filler Quantity 1006 20 N To fill with zeros.

47 FX Contract 1

Utilization Amount Amount 1026 15 N

Optional1 only if FX contract 1 is

available.

48 FX Contract 2


Same as FX Contract 1 Reference


50 FX Contract 2


Same as FX Contract 1 Utilization Amount

51 FX Contract 3




53 FX Contract 3



54 FX Contract 4




56 FX Contract 4



57 FX Contract 5




59 FX Contract 5



60 Debiting A/C No. for

Charges Code 1261 20 N

Right justified with leading zeros.

Only numeric values are accepted i.e. no space, no bracket “( )”, no dash “-“, no slash “/”, etc. are allowed.

61 Debiting A/C Currency

for Charges Code 1281 3 N e.g. “SGD”, “USD”









1 If no utilisation amounts are indicated, the payment amount will be first deducted from the FX contract 1 followed by the next indicated FX

contract (if the previous indicated contracts have insufficient amounts).


Page 10 of 24



71 Payment Advice

Indicator Code 1496 1 Y

To indicate if customer wants to send Payment Advice to beneficiary via email:

“Y” – To send Payment Advice “N” – Do not send

72 Delivery Mode Code 1497 1 C

Mandatory if Payment Advice Indicator is “Y”.

Must be “E”.

Email delivery of the payment advice to beneficiary.

73 Advice Format Code 1498 1 C


Must be “1”.

74 Beneficiary ID Text 1499 20 N

To be printed on first page of advice.


75 Beneficiary City Text 1519 17 N Beneficiary’s city.

76 Email Address of

Beneficiary

Text 1536 50 C


Must be a valid email address.

77 Facsimile Number of

Beneficiary Text 1586 20 N To fill with spaces

78 Payer’s Name (line 1)

Text 1606 35 N



79 Payer’s Name (line 2)

Text 1641 35 N



80 Reference Number

Text 1676 20 N

Customer’s reference number for this invoice.





Page 11 of 24

2.4 Payment Advice format (Free Format) Optional; do not populate this record if no payment advice is required.



2 Spacing Lines Quantity 2 2 Y

Value 00 to 50 only, any value greater than 50 will be defaulted to 50.

It is to indicate how many spacing lines to be printed before this advice line.

3 Payment Advice Details Text 4 105 Y Refer to Appendix 1 for Payment Advice.


2.5 Batch Trailer Total number of transactions and payment amounts in Batch Detail must tally with the trailer counts.



2 Total Number of

Transactions Quantity 2 8 Y

Total number of transactions in record type “2”.

3 Total Payment

Amount Amount 10 15 Y

Total of the payment amounts in record type “2”.



Page 12 of 24

3. Fate File Format (from UOB to Customer)

Record Size : 800 File Structure : Batch Header (1 line) – refer to section 3.1 Batch Details (1 to multiple lines) – refer to section 3.2 Batch Trailer (1 line) – refer to section 3.3 File Naming : For FTS

File Name: UTPOddmmNN_xxxxA

U UOB


O Outgoing file from bank to customer

ddmm Same value as incoming file

NN Same value as incoming file

xxxxA UOB assigned reference

For FileAct

File Name: CC_UTPOddmmNN_BIC.txt

CC Country Code

U UOB





BIC Sender BIC (11 Characters)

For BIBPlus

File Name: UTMOxxxxxxxxxxxxxx

U UOB

TM Telegraphic Payment


xxxxxxxxxxxxxx 14 digit BIBPlus reference number


Page 13 of 24

3.1 Batch Header

# FIELD DESCRIPTION TYPE POSITION LENGTH REMARKS

1 Record Type Code 1 1 Must be "1".

2 Bulk Customer Reference Text 2 20 Same as incoming file

3 Payment Advice Header Line 1 Text 22 105 Same as incoming file

4 Payment Advice Header Line 2 Text 127 105 Same as incoming file

5 Filler Text 232 569 Spaces

3.2 Batch Detail

# FIELD

DESCRIPTION TYPE POSITION LENGTH REMARKS

1 Record Type Code 1 1 Must be “2”.

2 Payment Type Code 2 3 Same as incoming file.

3 Payment Currency Code 5 3 Same as incoming file.

4 Payment Amount Amount 8 15 Same as incoming file.

5 Value Date Date 23 8 Same as incoming file.

6 Beneficiary Name

and Address (Line 1) Text 31 35 Same as incoming file.

7 Fillers Text 66 35 Spaces.

8 Fillers Text 101 35 Spaces.

9 Debiting Currency Code 136 3 Same as incoming file.

10 Debiting Amount Amount 139 15 Total debiting amount including charges.

11 Remit amount Amount 154 15 Actual payment amount to beneficiary (in payment currency) less charges.

12 FX Contract 1

Reference Text 169 20

Same as incoming file.

13 FX Contract 1 Rate Amount 189 20 Same as incoming file.

14 FX Contract 1

Utilized Amount Amount 209 15 Same as incoming file.

15 FX Contract 2

Reference Text 224 20 Same as incoming file.


17 FX Contract 2


18 FX Contract 3



20 FX Contract 3


21 FX Contract 4



23 FX Contract 4


24 FX Contract 5



26 FX Contract 5


27 Total amount of bank

charges Amount 444 15

Sum of Commission, Agent and Cable Charges

28 Commission Charge Amount 459 15 Commission charge in payment currency

29 Agent Charge Amount 474 15 Agent charge in payment currency with 2 decimal places


Page 14 of 24

# FIELD

DESCRIPTION TYPE POSITION LENGTH REMARKS

30 Cable Charge

Amount 489 15

Cable charge in payment currency with 2 decimal places

31 Postage Charge Amount 504 15 Not applicable 32 MT110 Charge Amount 519 15 Not applicable

33 Exchange Rate 1 Rate 534 20 Bank’s board rate 1 with 8 decimal places.

00000000001234567890 means 12.34567890

34 Exchange Rate 2 Rate 554 20

Bank’s board rate 2 with 8 decimal places.

Applicable when payment currency and debiting currency are in 3rd cross currency pair, e.g. HKD and GBP.

35 Bank Reference No Text 574 20 Bank’s reference No.

36 Process Status Code 594 2 ‘0 ’ – Processed successfully

‘1 ’ – Rejected

37 Process Remarks Text 596 50 Rejection Reason.

38 Payment Advice

Indicator Code 646 1

‘Y’ – Sent

‘N’ – Not sent

39 Reason of Not Sent Text 647 50 States the reason why the advice cannot be sent.

40 Reference Number Text 697 20 For customer’s reference, same as incoming file.

41 Beneficiary ID Text 717 20 Same as incoming file.

42 Filler Text 737 64 Spaces.

3.3 Batch Trailer

# FIELD DESCRIPTION TYPE POSITION LENGTH REMARKS

1 Record Type Code 1 1 Must be “9”.

2 Total Number of

Successful Transactions Quantity 2 8

Total number of successfully processed detail records in the file.

3 Total debiting amount Amount 10 15 Total debiting amount including charges in 2 decimal places.

4 Total Number of Rejected

Transactions Quantity 25 8

Total number of rejected detail records in the file.

5 Total Payment Amount of

Rejected Transactions Amount 33 15

Total payment amount of rejected transactions regardless of payment currency in 2 decimal places.

6 Filler Text 48 753 Spaces.


Page 15 of 24

4. Acknowledgment (Applicable to FTS/FileAct)

Customers sending payment files via BIBPlus may ignore this section. 4.1 Acknowledgement Types When customers send payment file via FTS/FileAct, they will receive acknowledgement with regards to the status of the file submission. The table below shows 4 types of acknowledgement from the bank.

ACK TYPE

RESPONSE TIME

ACK FILE NAMING ACK FILE CONTENT

FTS FILEACT

File Received

Within 10 mins from file submission

UTPIddmmNN SG_UTPIddmmNN_TELSGS1XXX 1201,UTPI011201 has

been received

File Accepted

UTPIddmmNN_ACC SG_UTPIddmmNN_ACC_TELSGS1XXX 1201,UTPI011201 has

been accepted

File Rejected

UTPIddmmNN_REJ SG_UTPIddmmNN_REJ_TELSGS1XXX 1201,UTPI011201,Rec #:,1,Invalid company ID in control record

File Duplicated

UTPIddmmNN_DUP SG_UTPIddmmNN_DUP_TELSGS1XXX 1201,UTPI011201,Rec

#:,1,Duplicate file

With reference to the Ack. File Naming column in the table above, additional file extension will be appended depending on the encrypted software used, e.g. PGP encryption will have the file extension of “.pgp”. With reference to the Ack. File Content column in the table above, the acknowledgement file has a fixed record size of 80 characters and will be in the format of “MMDD,Filename,Message<spaces>” where:

MMDD – file creation month and day

Filename – Payment filename

Message – acknowledgement or rejection messages

4.2 File Submission and Acknowledgement Scenarios The 3 scenarios below depict the types of acknowledgement UOB will send upon receiving your payment file via FTS. Do inform your UOB contact immediately if the acknowledgement files are not returned within the expected response time given in section 4.1. Scenario 1: Payment File is received and accepted

Customer

UOB

UTPI010201.TXT.pgp

UTPI010201.pgp

UTPI010201_ACC.pgp


Page 16 of 24

Scenario 2: Payment File is received and rejected Scenario 3: Payment File is received and rejected due to duplication

customer uploaded payment file to UOB UOB acknowledged payment file

4.3 Email Alert Customers can also request to receive these acknowledgements via email alerts. Please liaise with your UOB contact if this is required.

Customer

UOB

UTPI010201.TXT.pgp

UTPI010201.pgp

UTPI010201_REJ.pgp

Customer

UOB

UTPI010201.TXT.pgp

UTPI010201.pgp

UTPI010201_REJ.pgp


Page 17 of 24

Appendix 1 Payment Advice Payment Advice generated in the PDF file as shown below. It will be attached in the email to the beneficiary.


Page 18 of 24

The following table describes the print areas of the payment advice.

PRINT AREA DESCRIPTION PAYMENT FILE MAPPING

Top Left Area Mailing Name & Address Line

(4 lines)

Section 2.3 field 10 – Beneficiary Name and Address (Line 1) Section 2.3 field 13 – Beneficiary Name and Address (Line 2) Section 2.3 field 14 – Beneficiary Name and Address (Line 3) Section 2.3 field 15 – Beneficiary Name and Address (Line 4)

Top Right Area

Date Section 2.3 field 5 – Value Date

Payer’s Name (2 lines) Section 2.3 field 78 – Payer’s Name (line 1) Section 2.3 field 79 – Payer’s Name (line 2) Default to Company Name if above not provided.

Beneficiary ID Section 2.3 field 74 – Beneficiary ID

Bank Reference TT reference number generated by the bank

Reference No Section 2.3 field 80 – Reference Number

Payment for the account of Section 2.3 field 19 – Beneficiary A/C No Masked by bank except last 3 digits.

Amount Section 2.3 field 3 – Payment Currency Section 2.3 field 4 – Payment Amount

Center Area

Payment Advice Header (2 lines)

Section 2.2 field 3 – Payment Advice Header Line 1 Section 2.2 field 4 – Payment Advice Header Line 2

Payment Advice Details (multiple lines)

Section 2.4 field 3 – Payment Advice Details

Bottom Area (Last Page)

Disclaimer Bank provides this on the last page of the payment advice.


Page 19 of 24

Appendix 2 Remittance Information Clearing Code and / or Payment Details to Beneficiary may be required for TT Payments to some countries or in certain TT currencies and the omission may result in delays or rejections of the transaction from the beneficiary bank.

Beneficiary Country

TT Currency

IBAN Required?

Clearing Code (& Code Type)

Additional Payment Details

Angolan Kwanza

AOA Y

Australia AUD 6-digit BSB (AU) -

Mandatory

Bangladesh BDT Beneficiary bank’s name and branch address

Brunei BND Detailed Reason for Payment

Canada CAD 9-digit DPRN (CC)

– Optional

China CNY or CNH

12-digit CNAPS

(CN) – Mandatory Detailed Reason for Payment

Any Countries

CNY or CNH

Detailed Reason for Payment

Denmark DKK Y

Egypt EGP a) Beneficiary contact number in the payment

details b) Detailed Reason for Payment

Countries in Europe

Any currency

Y

India Any

Currency, except INR

Detailed Reason for Payment

India INR 11-digit IFSC (IN)

- Mandatory Detailed Reason for Payment

Korea Any

Currency

a) Beneficiary’s contact number in payment details b) Detailed Reason for Payment

Kuwaiti KWD Y Detailed Reason for Payment

Malaysia Any

Currency

a) Detailed Reason For payment b) Additional supporting documents may be

requested to support the payment reason.

Myanmar USD a) Beneficiary's identification or passport number

and Date of Birth b) Detailed Reason for Payment

Any Countries

MXN

c) Detailed Reason for Payment d) The 18-digit CLABE account number for credit to

all depository accounts in Mexico e) If the Beneficiary Bank is located outside of

Mexico, to provide their MXN account number (with their appointed Mexican Correspondent Bank) along with their 11 character SWIFT BIC.

New Zealand

NZD 6-digit NZNCC (NZ) - Optional

Norway NOK Y

Pakistan PKR Y

a) Beneficiary's telephone no. in payment details b) Beneficiary's NTN in the payment details field, if

the beneficiary is a Pakistani tax payer. (Payments to individuals or non-Pakistani tax payers will not require an NTN.)


Page 20 of 24

Beneficiary Country

TT Currency

IBAN Required?

Clearing Code (& Code Type)

Additional Payment Details

c) A written purpose of payment and related Purpose Code (to be issued by the beneficiary) in the payment details field

Saudi Arabia

SAR Y Detailed Reason for Payment

Sri Lanka LKR Detailed Reason for Payment

Sweden SEK Y

Switzerland CHF Y

Taiwan Any

Currency

a) Beneficiary’s contact number in the payment details

b) Detailed Reason for Payment

Thailand THB Detailed Reason for Payment

United Arab Emirates

(UAE) AED Y Detailed Reason for Payment

United Kingdom

GBP Y

6-digit SC (SC), mandatory if

account number is not IBAN

United Kingdom

Any Currency,

except GBP

Y

United States

USD

9-digit FW (FW) or 4-digit CHIPS

Participant code (CP) - Optional

Vietnam Any

Currency Detailed Reason For payment

West African

States CFA Franc

BCEAO

XOF Y

Central African

States CFA Franc BEAC

XAF Y

For further updates to the above list, please refer to the UOB website below. https://uniservices1.uobgroup.com/secure/forms/business/BINPlus_clearing_codes.html

Appendix 3 ISO Country Codes Please refer to the ISO website below for more information. http://www.iso.org/iso/home/standards/country_codes.htm

https://uniservices1.uobgroup.com/secure/forms/business/BINPlus_clearing_codes.html

http://www.iso.org/iso/home/standards/country_codes.htm


Page 21 of 24

Appendix 4 Hash Algorithm Check Summary Calculation is performed on the payment file excluding the File Control Header (i.e. record type 0). Depicted below is the high-level logic of the hash algorithm. The SUM is the final hashing value right justified with leading zeros and populated in Check Summary (section 2.1, field 6) Set HASH CODE index to 1. Set RECORD NUMBER to 1. Read first record. Loop1: Read next record If not (end of file) Increase Record Number by 1 Set COLUMN NUMBER to 1 (each record has 1800 characters including trailing spaces) If COLUMN NUMBER is within 1800 Loop2: Retrieve the character from the COLUMN NUMBER position of the record Translate the character to ASCII value (refer to ASCII Table) If HASH CODE index > 23 Reset HASH CODE index to 1 End if SUM = SUM + RECORD NUMBER + (RECORD NUMBER + COLUMN NUMBER) * ASCII value * Hash Code (refer to HASH CODE Table) Increase HASH CODE index by 1 Increase COLUMN NUMBER by 1 Go to Loop2 End if End if Go to Loop1

NOTE 1) Hashing calculation will start from RECORD NUMBER 2 as record type 0 in the first record will be skipped. 2) HASH CODE index will increment over to the next record number without reset to 1 e.g. if the HASH CODE index

of the 1800th column on record number 10 is 3, the hash code index of the 1

st column on record number 11 will

be 4. 3) HASH CODE Table is used to retrieve the hash code based on the HASH CODE index.

Index Hash Code Index Hash Code

1 23 13 19

2 5 14 2

3 17 15 24

4 20 16 18

5 4 17 6

6 13 18 16

7 22 19 8

8 3 20 12

9 11 21 9

10 21 22 15

11 7 23 14

12 10 24 N.A

4) It is not advisable for the total number of records to exceed 30,000. Otherwise, the computed hashing might

exceed the limit of 15 digits.


Page 22 of 24

5) ASCII Table is used to retrieve the code based on each column of the file record.


Page 23 of 24

Appendix 5 Value Date Payment instructions received by the cut-off times listed below will be processed within the same day by the bank.

CHANNELS FTS/FILEACT BIBPLUS

Client Cutoff time 2pm SGT 4pm SGT

Processing Date and Value Date for payments received before Client Cutoff time

- Processing Date: The day when UOB debits the applicant’s account and sends the payment instruction to our correspondent bank.

- Value Date: The day when our correspondent bank executes our payment instruction. (Value Date does not necessarily determine the day the beneficiary will receive the funds as UOB has no control when the beneficiary banks will credit the account)

The following table shows the processing date and value date of the payment currencies.

Currency Currency Description Processing Date Value Date

SGD Singapore Dollar T T

Value Same Day

CAD Canadian Dollar T T

EUR Euro T T

GBP British Pound Sterling T T

USD United States Dollar T T

MYR Malaysian Ringgit T T

TWD New Taiwan Dollar T T

VND Vietnamese Dong T T

KRW Korean Won T T

HKD Hong Kong Dollar T T + 1

Value TOM

AUD Australian Dollar T T + 1

BND Brunei Dollar T T + 1

CHF Swiss Franc T T + 1

CNH* Chinese Yuan/Renminbi T T + 1

DKK Danish Krone T T + 1

JPY Japanese Yen T T + 1

NOK Norwegian Krone T T + 1

NZD New Zealand Dollar T T + 1

SEK Swedish Krona T T + 1

INR Indian Rupee T T + 2

Value SPOT

IDR Indonesian Rupiah T T + 2

PHP Philippine Peso T T + 2

THB Thai Baht T T + 2

AED United Arab Emirates Dirham T T + 2

SAR Saudi Arabian Riyal T T + 2

ZAR South African Rand T T + 2

BDT Bangladeshi Taka T T + 2


Page 24 of 24

Currency Currency Description Processing Date Value Date

EGP Egyptian Pound T T + 2

KWD Kuwaiti Dinar T T + 2

LKR Sri Lankan Rupee T T + 2

MXN Mexican Peso T T + 2

PKR Pakistani Rupee T T + 2

AOA** Angolan Kwanza T T + 2

XAF** Central African CFA Franc T T + 2

XOF** West African CFA Franc T T + 2

* Not ISO currency, offshore currency code used by the bank. ** Currencies to take effective from 1-Mar-2017.

Documents

Payment Integration Bulk Telegraphic Transfer Format ... · Payment Integration Bulk Telegraphic Transfer Format Specifications ... Payment File Format ... All fields’ values must