SFMS - Guidelines

INTRODUCTION: .......................................................................................................................
3
1.
CUSTOMER FUNDS TRANSFERS ................................................................................... 5
1.1. CUSTOMER TTS/MTS. ......................................................................................................... 5

1.1.1. IMMEDIATE APPLICATION OF FUNDS AND USE OF TRADITIONAL MEANS OF RECONCILIATION.
(IFN 100)............................................................................................................................. 5
1.1.2. IMMEDIATE APPLICATION OF FUNDS AND USE OF IFN MESSAGES FOR RECONCILIATION. (IFN
100, 900 & 910)........................................................... ERROR! BOOKMARK NOT DEFINED.
1.1.3. RECONCILIATION OF MESSAGES WHILE APPLYING FUNDS ................................................. 10
1.1.3.1. Direct Method ............................................................................................................... 10
1.1.3.1.1. Reconciliation of TT Message using IFN 910/900 & 195/196 messages ................. 11
1.1.3.1.2. Reconciliation of TT Message using IFN 910 & 195/196 messages......................... 14
1.1.3.2. Indirect Method:............................................................................................................ 16
1.2. MULTIPLE CUSTOMER TTS/MTS. ..................................................................................... 19
1.2.1. IMMEDIATE APPLICATION OF FUNDS AND USE OF TRADITIONAL MEANS OF RECONCILIATION.
(IFN 102)........................................................................................................................... 19
1.2.2. IMMEDIATE APPLICATION OF FUNDS AND USE OF IFN MESSAGES FOR RECONCILIATION. (IFN
102, 900 & 910)................................................................................................................. 22
1.2.3. RECONCILIATION OF MESSAGES WHILE APPLYING FUNDS ................................................. 25
1.2.3.1. Direct Method ............................................................................................................... 25
1.2.3.1.1. RECONCILIATION OF MESSAGES WHILE APPLYING FUNDS (IFN 102, 195, 196, 900 &
910) ................................................................................................................................... 25
1.2.3.1.2. Reconciliation of TT Message using IFN 910 & 195/196 messages......................... 28
1.2.3.2. Indirect Method:............................................................................................................ 31
1.3. CUSTOMER REQUEST FOR TRANSFER OF FUNDS. ............................................................. 35
1.3.1. TRANSFER IS FOR CREDIT OF A SINGLE BENEFICIARY WHO ALSO BANKS WITH THE RECEIVER
OF THE MESSAGE. (IFN 101) .............................................................................................. 35
1.3.2. TRANSFER IS FOR CREDIT OF MULTIPLE BENEFICIARIES WHO ALSO BANK WITH THE BRANCH
TO WHICH THE IFN 101 MESSAGE IS ADDRESSED. .............................................................. 37
1.3.3. TRANSFER IS FOR CREDIT OF A SINGLE BENEFICIARY WHO BANKS WITH ANOTHER BRANCH
OF THE SAME BANK. (IFN 101, 100, 900 & 910) ................................................................ 40
1.3.4. TRANSFER IS FOR CREDIT OF MULTIPLE BENEFICIARIES WHO BANK WITH OTHER BRANCHES
OF THE BANK. (IFN 100, 101, 102, 900 & 910) .................................................................. 43
1.3.5. TRANSFER IS FOR CREDIT OF A SINGLE BENEFICIARY WHO BANKS WITH ANOTHER BANKS
BRANCH IN THE SAME ENTER AS THE BRANCH TO WHICH THE MESSAGE IS ADDRESSED. (IFN
101) ................................................................................................................................... 48
1.3.6. TRANSFER IS FOR CREDIT OF MULTIPLE BENEFICIARIES WHO BANK WITH OTHER BANKS
BRANCHES IN THE SAME ENTER AS THE BRANCH TO WHICH THE MESSAGE IS ADDRESSED.
(IFN 101)........................................................................................................................... 50
1.4. THIRD PARTY INSTRUCTION OR REQUEST FOR DEBIT OF CUSTOMERS ACCOUNT. (IFN
104) ..................................................................................................................................... 52
1.5. DD RELATED MESSAGES. .................................................................................................. 53
1.5.1. DD ADVICES. (IFN 110) ................................................................................................... 53
1.5.2. DD STOP PAYMENT REQUESTS. (IFN 111) ....................................................................... 54
1
1.5.3.
2.
REPLIES TO DD STOP PAYMENT REQUESTS. (IFN 112) .................................................... 54
INTER-BRANCH MESSAGES INVOLVING INTRA-BANK AND INTER-BANK

TRANSFER OF FUNDS:.................................................................................................... 56
2.1. REQUEST FOR TRANSFER OF FUNDS FROM DAD ACCOUNT OF ONE BRANCH TO ANOTHER.
(IFN 202, 210, 900 & 910)..................................................................................................... 56
2.2. REQUEST FOR TRANSFER OF FUNDS FROM DAD ACCOUNT OF ONE BRANCH TO DAD
ACCOUNT OF TWO OR MORE BRANCHES. (IFN 203, 210, 900 & 910)................................... 59
2.3. REQUEST FOR TRANSFER OF FUNDS FROM ONE BANKS BRANCH TO ANOTHER BANKS
BRANCH. (IFN 202, 201, 900 & 910) ..................................................................................... 68
2.4. ADVANCE NOTICE OF FUNDS EXPECTED TO BE RECEIVED. (IFN 210) ............................ 72
3.
COLLECTIONS:................................................................................................................. 73
3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
4.
ACKNOWLEDGEMENT OF RECEIPT OF COLLECTION BILLS. (IFN 410)........................... 73

ADVICE OF ACCEPTANCE: (IFN 412) ................................................................................ 75
TRACER (FATE ENQUIRY): (IFN 420) ............................................................................... 76
ADVICE OF FATE AND REQUEST FOR INSTRUCTIONS: (IFN 422) ..................................... 77
AMENDMENT OF INSTRUCTIONS: (IFN 430)...................................................................... 79
ADVICE OF PAYMENT: (IFN 400) ...................................................................................... 80
LETTERS OF CREDIT:..................................................................................................... 83
4.1.
4.2.
4.3.
4.4.
4.5.
4.6.
4.7.
4.8.
4.9.
4.10.
4.11.
4.12.
SHORT LCS (PRE-ADVICES). (IFN 705) ............................................................................ 83

LC ISSUE: (IFN 700 & 701) ............................................................................................... 85
ACKNOWLEDGEMENT OF LC MESSAGE: (IFN 730) ......................................................... 88
ADVICE OF ANOTHER BRANCHS LC: (IFN 710 & 711) ................................................... 89
TRANSFER OF LC: (IFN 720 & 721) .................................................................................. 92
ADVICE OF LC AMENDMENT: (IFN 707)........................................................................... 96
ADVICE OF PAYMENT/ACCEPTANCE/NEGOTIATION: (IFN 754) ...................................... 97
ADVICE OF PAYMENT: (IFN 756) ...................................................................................... 98
ADVICE OF DISCREPANCY: (IFN 750) ............................................................................. 100
AUTHORISATION TO PAY, ACCEPT OR NEGOTIATE: (IFN 752) ................................... 102
ADVICE OF DISCHARGE: (IFN 732) ............................................................................... 103
ADVICE OF REFUSAL: (IFN 734).................................................................................... 106
Introduction:
SFMS: Message Usage Scenarios:
The following 5 SFMS Message usage scenarios can be envisaged:
Intra Bank Messages

Inter bank Messages which do not require settlement at all
Inter bank Messages which do not require immediate settlement
Inter Bank Messages involving bilaterally agreed methods of settlement
Inter Bank Messages involving RBI for settlement
In this write up, only the first scenario has been addressed. The remaining four scenarios would
be discussed later. As such, messages that can be used for relaying inter bank transactions only,
such as IFN 3 category messages, which deal with inter bank forex and money market trade
confirmations have not been discussed here. Individual messages in other categories, which are
purely inter bank in nature, for e.g., IFN 200 (Request sent to a correspondent requesting for
transfer of funds between two accounts owned by the sender), IFN 950 (Account statements sent
by correspondent banks to account owners) have also not been discussed.
The various business models involving traditional methods of reconciliation and innovations that
can be introduced by leveraging on facilities provided by SFMS have been discussed in elaborate
detail in section 1 (Customer Funds Transfers). To avoid repetition, only a single business model
has been described in the remaining chapter. Users can decide on any of the business models
suggested in section 1 and apply it to the transactions described in remaining sections.
Dates expressed in IFN messages will have to be in the YYYYMMDD format and amounts will
have to be expressed without use of comma as delimiter between hundreds, thousands, lakhs etc.
However, to ensure clarity, all message formats given in examples express dates in
DDMMYYYY format and comma has been used as delimiter in amount fields.
Where the description of a particular field differs from the standard description given in IFN
message format publications, such descriptions have been printed in capitals. E.g., Actual
description of field 52A field in IFN 900 message is Ordering Institution, but it has been
described here as CONTRAPARTY BRANCH.
All the IFS Codes (IFSC) and many of the branches referred to in the examples are fictitious.
The scenarios, usages, practices and business models related in the following pages are
indicative and not exhaustive. Suggestions for additions, improvements, deletions and
modifications to the message usage descriptions, usage scenarios, business models, examples
etc., and information regarding errors if any would be gratefully accepted and incorporated.
Kindly forward your feed back to the following address:
A.P.Raja,
Project Consultant (SFMS Project),
BENEFICIARIES,
Masab Tank,
Hyderabad 500 057.
Phone : (040)3534981-4 (Extn. 2112).
Fax: (040)3534981
Email: apraja@BENEFICIARIES.ac.in
1. Customer Funds Transfers

1.1. Customer TTs/MTs.
IFN 100 messages should be used for relaying Customer TTs.
The following scenarios can be envisaged:
1. Immediate application of funds and use of traditional means of reconciliation.
2. Immediate application of funds and use of IFN messages for reconciliation.
3. Reconciliation of Messages while applying funds
1.1.1. Immediate application of funds and use of traditional means of

reconciliation. (IFN 100)
IFN 100 message is used for relaying the TT message. Reconciliation of the TT transaction is
done using the reconciliation process prevailing in the bank.
Example:
On 1.09.2001, Mr. L.P.Yadav who has an account with Andhra Bank, Masab Tank, Hyderabad,
requests the bank to transfer a sum of Rs 10,000/- to the account No. 123456 of Mr. N.C.Naidu
with Andhra Bank, Mumbai Main Branch. The payment represents monthly rent for August
2001, on a flat leased by Mr Yadav and Charges (if any,) at the paying branch are for the
beneficiarys account. The instruction is received within the cut-off time prescribed by the Bank
for same day value transfers. Andhra Bank, Masab Tank TT Reference No. is TT/567/2001.
The information to be provided by Andhra Bank, Masab Tank to Andhra Bank, Mumbai in the
TT message would be as follows:
Sending Branch
: Andhra Bank, Masab Tank, Hyderabad

(IFSC say ANDB0000456)
Receiving Branch
: Andhra Bank, Main Branch, Mumbai
(IFSC say ANDB0000123)
TT Reference No.
: TT/567/2001
TT Ordered By
: L.P.Yadav
Amount
: Rs 10,000.00
Value Date
: 17.10.2001
Favouring
: N.C.Naidu
Beneficiarys Account No.
: 123456
Account maintained with
: Andhra Bank, Mumbai Main Branch
Details of Payment for Beneficiary : Monthly rent for August 2001
Paying Bank charges to be borne by : Beneficiary
5
Andhra Bank, Masab Tank sends an IFN 100 message to Andhra Bank, Mumbai Main Branch
and reports the transaction by sending a credit Report to the Banks Reconciliation System
On receipt of a valid and authenticated IFN 100 message, Andhra Bank, Mumbai Main Branch
applies funds to Mr. Naidus account and reports the transaction by sending a debit report to the
Banks Reconciliation System.
Message Flow:
L.P.YADAV
FUNDS
ANDHRA
BANK
MASAB TANK
IFN
100
N.C.NAIDU
FUNDS
CREDIT
REPORT
ANDHRA BANK
RECONCILIATION
SYSTEM
ANDHRA
BANK
MUMBAI
DEBIT
REPORT
The extract of header and text block of the IFN 100 Message sent by Andhra Bank, Masab Tank
to Andhra Bank, Mumbai Main Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000123
IFN 100
Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Mumbai
Customer Transfer
Text Block:
Field Description
20
Transaction Reference No.
32A
Value Date Currency & Amount
50
Ordering Customer
59
Beneficiary
70
71A
Details of Payment
Details of Charges
Information
TT/567/2001
17092001INR10,000.00
L.P.YADAV
/123456
N.C.NAIDU
RENT FOR AUGUST 2001
BEN
6
1.2.
IFN 100 message is used for relaying the TT message. SFMS branches use IFN 900 (advice of
Debit) and IFN 910 (advice of Credit) for relaying the Debit and credit reports to the
Reconciliation System. This would necessitate changes at system and policy level in the
Reconciliation mechanism of the Bank. The benefits accruing to the Bank by adopting this
method are:
Debit entries relating to Paid TTs would normally be outstanding for a few minutes only.
Outstanding Credit entries relating to TT transactions would normally represent TTs issued
but not paid. As disposal of such entries are critical from a customer service stand point, it
will now be possible to view and monitor such entries from a central location.
Example:
In the example quoted in section 1.1.1 above, Andhra Bank, Masab Tank sends an IFN 100
message to Andhra Bank, Mumbai Main Branch and reports the transaction by sending an IFN
910 message to the Banks Reconciliation System.
applies funds to Mr. Naidus account and reports the transaction by sending an IFN 900 message
to the Banks Reconciliation System (IFSC say ANDB0000999).
Message Flow:
L.P.YADAV
FUNDS
ANDHRA
BANK
MASAB TANK
IFN
100
N.C.NAIDU
FUNDS
ANDHRA
BANK
MUMBAI
IFN
910
ANDHRA BANK
RECONCILIATION
SYSTEM
IFN
900
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000123
IFN 100

Andhra Bank, Mumbai
Customer Transfer
Text Block:
Field Description
20
32A
50
Ordering Customer
59
Beneficiary
70
71A
Details of Payment
Details of Charges
Information
TT/567/2001
17092001INR10,000.00
L.P.YADAV
/123456
N.C.NAIDU
BEN
to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000999
IFN 910

Andhra Bank Reconciliation System
Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
Account Identification
32A
52A
CONTRA PARTY BRANCH
Information
TT/567/2001
NONREF
INTER BRANCH ACCOUNT
17092001INR10,000.00
ANDB0000123
The extract of header and text block of the IFN 900 Message sent by Andhra Bank, Mumbai
Main Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000123
ANDB0000999
IFN 900
Andhra Bank, Mumbai

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/987/2001
(1)
TT/567/2001
17092001INR10,000.00 (2)
ANDB0000456
(1)
This is the paying branch TT Reference No.
(2)
The date to be furnished in Field 32A is the value date indicated in the original TT
message. Even if Andhra Bank, Mumbai Main Branch were to apply funds on the
next or any subsequent day, the date in field 32A should be the one mentioned in the
IFN 100 to facilitate reconciliation.
1.2.1. Reconciliation of Messages while applying funds

Reconciliation of customer payment transactions before applying funds requires changes at
system and policy level in the Reconciliation mechanism of the Bank. The benefits accruing to
the Bank by adopting this method are:
Debit entries relating to Paid TTs would not be outstanding at all.

Outstanding Credit entries relating to TT transactions would normally represent TTs issued
but not paid. As disposal of such entries are critical from a customer service stand point, it
will now be possible to view and monitor such entries from a central location.
This can be done in two ways namely the direct method and the indirect method.
1.2.1.1. Direct Method
IFN 100 messages are sent directly to the paying branch and IFN 910 message is sent to the
Reconciliation System. The paying branch queries the Reconciliation System before applying
funds.
The various possible scenarios under this method have been discussed below:
10
1.2.1.1.1. Reconciliation of TT Message using IFN 910/900 & 195/196 messages

The Ordering Branch uses IFN 100 message to relay the Payment Order to the Paying branch
and uses an IFN 910 message to relay the credit advice to the Reconciliation System. The Paying
Branch sends an IFN 195 message to the Reconciliation System requesting authorization to
debit. The Reconciliation System sends an IFN 196 authorizing the debit. The Paying branch
applies funds and uses an IFN 900 message to relay the debit advice to the Reconciliation
System.
Example:
sends an IFN 195 message to the Reconciliation System requesting authorization to debit. The
Reconciliation System sends an IFN 196 authorizing the debit. Andhra Bank, Mumbai Main
Branch applies funds to Mr. Naidus account and reports the transaction by sending an IFN 900
message to the Banks Reconciliation System.
Message Flow:
L.P.YADAV
FUNDS
ANDHRA
BANK
MASAB TANK
IFN
910
ANDHRA BANK
RECONCILIATION
SYSTEM
IFN
100
N.C.NAIDU
FUNDS
ANDHRA
BANK
MUMBAI
IFN
195
IFN
196
IFN
900
11
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000123
IFN 100

Andhra Bank, Mumbai
Customer Transfer
Text Block:
Field Description
20
32A
50
Ordering Customer
59
Beneficiary
70
71A
Details of Payment
Details of Charges
Information
TT/567/2001
17092001INR10,000.00
L.P.YADAV
/123456
N.C.NAIDU
BEN
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/567/2001
NONREF
17092001INR10,000.00
ANDB0000123
The extract of header and text block of the IFN 195 Query Message sent by Andhra Bank,
Mumbai Main Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000123
ANDB0000999
IFN 195
Andhra Bank, Mumbai

Query
12
Text Block:
Field Description
20
21
Related Reference
75
Queries
Information
TTP/987/2001
TT/567/2001
/18/ (Please authorize us to debit)
ANDB0000456
17092001INR10,000.00
The extract of header and text block of the IFN 196 Answer Message sent by the Reconciliation
System to Andhra Bank, Mumbai Main Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000999
ANDB0000123
IFN 196

Andhra Bank, Mumbai
Reply
Text Block:
Field Description
20
21
Related Reference
76
Answer
Information
TT/567/2001
TTP/987/2001
/10/ (We authorize you to debit)
Main Branch to the Reconciliation System to would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000123
ANDB0000999
IFN 900
Andhra Bank, Mumbai

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/987/2001
TT/567/2001
17092001INR10,000.00
ANDB0000456
13
1.2.1.1.2.
Reconciliation of TT Message using IFN 910 & 195/196 messages
debit. The Reconciliation System sends an IFN 196 authorizing the debit and treats the
transaction as reconciled without waiting for an IFN 900 from the Paying Branch. The Paying
branch applies funds. In other words, the IFN 195 message requesting authorization to debit also
acts as an IFN 900 (Debit Advice) Message.
Example:
Reconciliation System sends an IFN 196 authorizing the debit and treats the message as
reconciled. Andhra Bank, Mumbai Main Branch applies funds to Mr. Naidus account.
Message Flow:
L.P.YADAV
FUNDS
ANDHRA
BANK
MASAB TANK
IFN
910
ANDHRA BANK
RECONCILIATION
SYSTEM
IFN
100
N.C.NAIDU
FUNDS
IFN
195
IFN
196
ANDHRA
BANK
MUMBAI
14
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000123
IFN 100

Andhra Bank, Mumbai
Customer Transfer
Text Block:
Field Description
20
32A
50
Ordering Customer
59
Beneficiary
70
71A
Details of Payment
Details of Charges
Information
TT/567/2001
17092001INR10,000.00
L.P.YADAV
/123456
N.C.NAIDU
BEN
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/567/2001
NONREF
17092001INR10,000.00
ANDB0000123
The extract of header and text block of the IFN 195 Query Message sent by Andhra Bank,
Mumbai Main Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000123
ANDB0000999
IFN 195
Andhra Bank, Mumbai

Query
15
Text Block:
Field Description
20
21
Related Reference
75
Queries
Information
TTP/987/2001
TT/567/2001
ANDB0000456
17092001INR10,000.00
Header Block:
Sender
Receiver
Message Type
ANDB0000999
ANDB0000123
IFN 196

Andhra Bank, Mumbai
Reply
Text Block:
Field
20
21
75
1.2.1.2.
Description
Related Reference
Queries
Information
TT/567/2001
TTP/987/2001
Indirect Method:
Instead of sending the Payment Order to the Paying Branch, The Ordering Branch sends the IFN
100 message to the Reconciliation System. The Reconciliation System in turn, relays the IFN
100 message to the Paying Branch. The Paying branch applies funds and sends an IFN 900 to the
Reconciliation System. It is to be noted that the IFN 100 message from the Ordering Branch to
the Reconciliation System also acts as an Advice of Credit.
Example:
message to the Banks Reconciliation System. The Banks Reconciliation System in turn sends
an IFN 100 message to Andhra Bank, Mumbai Main Branch.
applies funds to Mr. Naidus account and reports the transaction by sending an IFN 900 message
16
Message Flow:
L.P.YADAV
ANDHRA
BANK MASAB
TANK
FUNDS
IFN
100
ANDHRA BANK
RECONCILIATION
SYSTEM
IFN
100
N.C.NAIDU
IFN
900
ANDHRA
BANK
MUMBAI
FUNDS
to the Banks Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000456
ANDB0000999
IFN 100

Andhra Bank, Reconciliation System
Customer Transfer
Text Block:
Field Description
20
32A
50
Ordering Customer
57A
Account with Bank (BRANCH)
59
Beneficiary
70
71A
Details of Payment
Details of Charges
Information
TT/567/2001
17092001INR10,000.00
L.P.YADAV
ANDB0000123
/123456
N.C.NAIDU
BEN
17
The extract of header and text block of the IFN 100 Message sent by the Banks Reconciliation
Header Block:
Sender
Receiver
Message Type
ANDB0000999
ANDB0000123
IFN 100

Andhra Bank, Mumbai
Customer Transfer
Text Block:
Field Description
20
32A
50
Ordering Customer
52A
Ordering Bank (BRANCH)
59
Beneficiary
70
71A
Details of Payment
Details of Charges
Information
TT/567/2001
17092001INR10,000.00
L.P.YADAV
ANDB0000456
/123456
N.C.NAIDU
BEN
Main Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ANDB0000123
ANDB0000999
IFN 900
Andhra Bank, Mumbai

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/987/2001
TT/567/2001
17092001INR10,000.00
ANDB0000456
18
1.3. Multiple Customer TTs/MTs.

IFN 102 messages should be used for relaying Multiple Customer TTs.
Immediate application of funds and use of traditional means of reconciliation.

Immediate application of funds and use of IFN messages for reconciliation.
Reconciliation of Messages while applying funds
1.3.1. Immediate application of funds and use of traditional means of

reconciliation. (IFN 102)
IFN 102 message is used for relaying multiple TTs in a single message. Reconciliation of the TT
transactions is done using the reconciliation process prevailing in the bank.
The Ordering Customers branch (Ordering Branch) sends an IFN 102 Message to the Paying
Branch and sends a Credit Report to the Banks Reconciliation System by traditional means. The
Paying Branch applies funds to the Beneficiaries accounts and sends a Debit Report to the
Banks Reconciliation System by traditional means.
Example:
On 1.09.2001, M/s. XYZ Ltd request Allahabad Bank, Kolkata to transfer funds for credit of
their employees accounts with Allahabad Bank, Bangalore as detailed below. The payments
represent salary for the month of August 2001
Sl. No.
1
2
3
Employees Name
K.L.Ram
M.N.Rahim
O.P.Roberts
Account No.
4567890
5678901
6789012
Amount (Rs)
12,000.00
12,500.00
13,000.00
Charges (if any,) at the paying branch are for the remitters account. The instruction is received
after the cut-off time prescribed by the Bank for same day value transfers. Allahabad Bank,
Kolkata Reference Nos. are TT/345/2001, TT/346/2001 and TT/347/2001 respectively.
While reporting multiple TTs to Reconciliation System, the practice in Allahabad Bank is that
both the issuing branch and paying branch quote the Reference No. of the first TT. viz.,
TT/345/2001 in this case.
The information to be provided by Allahabad Bank, Kolkata to Allahabad Bank, Bangalore in
the TT message would be as follows:
19
Information Common to all TTs:

Sending Branch
: Allahabad Bank, Kolkata

(IFSC say ALLA0000123)
Receiving Branch
: Allahabad Bank, Bangalore
(IFSC say ALLA0000234)
TTs Ordered By
: XYZ Ltd
Sum Total of all TTs
: Rs 37,500.00
Value Date
: 2.9.2001 *
Beneficiaries bank with
: Allahabad Bank, Bangalore
Details of Payment for Beneficiaries : Salary for August 2001
Paying Bank charges to be borne by : Ordering Customer
* Funds cannot be applied same day value viz., 1.9.2001, because the payment instruction
was received after the cutoff time for same day value TTs)
Information relevant to individual TTs:
TT Reference No.
TT/345/2001
TT/346/2001
TT/347/2001
Beneficiary
K.L.Ram
M.N.Rahim
O.P.Roberts

4567890
5678901
6789012
Allahabad Bank, Kolkata sends an IFN 102 message to Allahabad Bank, Bangalore Branch and
reports the transaction by sending a credit Report to the Banks Reconciliation System.
On receipt of a valid and authenticated IFN 102 message, Allahabad Bank, Bangalore applies
funds to the beneficiaries accounts and reports the transaction by sending a debit report to the
Message Flow:
XYZ LTD
FUNDS
ALLAHABAD
BANK
KOLKATA
IFN
102
K.L.RAM
FUNDS
M.N.RAHIM
FUNDS
O.P.ROBERTS
ALLAHABAD
BANK
BANGALORE
CREDIT
REPORT
ALLAHABAD BANK
RECONCILIATION
SYSTEM
DEBIT
REPORT
FUNDS
20
The extract of header and text block of the IFN 102 Message sent by Allahabad Bank, Kolkata to
Allahabad Bank, Bangalore Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000234
IFN 102
Allahabad Bank, Kolkata

Allahabad Bank, Bangalore
Multiple Customer Transfers
Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
Sending Institution IFSC Code
50
Ordering Customer
71A
Details of Charges
Transaction details: 1
21
Transaction Reference
32B
Currency & Amount
59
Beneficiary
21
32B
Currency & Amount
59
Beneficiary
21
32B
Currency & Amount
59
Beneficiary
Information
TT/345/2001
(1)
CREDIT
ALLA0000123
M/S XYZ LTD.,
KOLKATA
OUR
TT/345/2001
INR12,000.00
/4567890
K.L.RAM
TT/346/2001
INR12,500.00
/5678901
M.N.RAHIM
TT/347/2001
INR13,000.00
/6789012
O.P.ROBERTS
Settlement details
32A
Value Date, Currency & Amount 02092001INR37,500.00
(1) This is the reference to be quoted while reporting to the Reconciliation System.
21
1.3.2. Immediate application of funds and use of IFN messages for

reconciliation. (IFN 102, 900 & 910)
IFN 102 message is used for relaying Multiple TTs in a single message. SFMS branches use IFN
900 (advice of Debit) and IFN 910 (advice of Credit) for relaying the Debit and Credit reports to
the Reconciliation System.
The Ordering Customers branch (Ordering Branch) sends an IFN 102 Message to the Paying
Branch and reports to the Banks Reconciliation System by sending an IFN 910 Message. The
Paying Branch applies funds to the Beneficiarys account and reports to the Banks
Reconciliation System by sending an IFN 900 Message.
Example:
In the example quoted in section 1.2.1 above, Allahabad Bank, Kolkata sends an IFN 102
message to Allahabad Bank, Bangalore Branch and reports the transaction by sending an IFN
910 Message to the Banks Reconciliation System.
funds to the beneficiaries accounts and reports the transaction by sending an IFN 900 Message
to the Banks Reconciliation System (IFSC say ALLA0000999).
Message Flow:
XYZ LTD
FUNDS
ALLAHABAD
BANK
KOLKATA
IFN
102
K.L.RAM
M.N.RAHIM
O.P.ROBERTS
IFN
910
ALLAHABAD BANK
RECONCILIATION
SYSTEM
FUNDS
FUNDS
ALLAHABAD
BANK
BANGALORE
IFN
900
FUNDS
22
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000234
IFN 102

Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
50
Ordering Customer
71A
Details of Charges
21
32B
Currency & Amount
59
Beneficiary
21
32B
Currency & Amount
59
Beneficiary
21
32B
Currency & Amount
59
Beneficiary
Information
TT/345/2001
CREDIT
ALLA0000123
M/S XYZ LTD.,
KOLKATA
OUR
TT/345/2001
INR12,000.00
/4567890
K.L.RAM
TT/346/2001
INR12,500.00
/5678901
M.N.RAHIM
TT/347/2001
INR13,000.00
/6789012
O.P.ROBERTS
Settlement details
32A
the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000999
IFN 910

Allahabad Bank Reconciliation System
Credit Advice
23
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/345/2001
NONREF
02092001INR37,500.00
ALLA0000234
The extract of header and text block of the IFN 900 Message sent by Allahabad Bank, Bangalore
Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000234
ANDB0000999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/579/2001
(1)
TT/345/2001
02092001INR37,500.00 (2)
ALLA0000123
(1)
This is the paying branch TT Reference No.
(2)
The date to be furnished in Field 32A is the value date indicated in the original TT
message. Even if Allahabad Bank, Bangalore Branch were to apply funds on the next
or any subsequent day, the date in field 32A should be the one mentioned in the IFN
100 to facilitate reconciliation.
In case, Allahabad Bank, Bangalore is unable to apply one or more TTs conveyed in the above
message, it should still send the IFN 900 Message for the full amount and vouch reversal credits
to Allahabad Bank, Kolkata separately to avoid reconciliation errors.
24
1.3.3. Reconciliation of Messages while applying funds

Reconciliation of multiple customer payment transactions before applying can be achieved in
two ways namely the direct method and the indirect method.
1.3.3.1.
Direct Method
IFN 102 messages are sent directly to the paying branch and IFN 910 message is sent to the
Reconciliation System. The paying branch queries the Reconciliation System before applying
funds.
The various possible scenarios under this method have been discussed below:
1.3.3.1.1.
Reconciliation of Messages while applying funds (IFN 102, 195,

196, 900 & 910)
IFN 102 message is used for relaying the TT message. SFMS branches use IFN 910 (advice of
Credit) for relaying the credit reports to the Reconciliation System. The Paying Branch queries
the Reconciliation System before applying funds.
debit. The Reconciliation System sends an IFN 196 authorizing the debit. The Paying branch
applies funds and uses an IFN 900 message to relay the debit advice to the Reconciliation
System.
Example:
On receipt of a valid and authenticated IFN 102 message, Allahabad Bank, Bangalore Branch
Reconciliation System sends an IFN 196 authorizing the debit. Allahabad Bank, Bangalore
Branch applies funds to beneficiaries accounts and reports the transaction by sending an IFN
25
Message Flow:
ALLAHABAD
BANK
KOLKATA
XYZ LTD
FUNDS
IFN
910
ALLAHABAD BANK
RECONCILIATION
SYSTEM
IFN
102
IFN
195
IFN
196
K.L.RAM
M.N.RAHIM
ALLAHABAD
BANK
BANGALORE
FUNDS
O.P.ROBERTS
IFN
900
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000234
IFN 102

Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
50
Ordering Customer
71A
Details of Charges
21
32B
Currency & Amount
59
Beneficiary
Information
TT/345/2001
CREDIT
ALLA0000123
M/S XYZ LTD.,
KOLKATA
OUR
TT/345/2001
INR12,000.00
/4567890
K.L.RAM
26
21
32B
Currency & Amount
59
Beneficiary
TT/346/2001
INR12,500.00
/5678901
M.N.RAHIM
21
32B
Currency & Amount
59
Beneficiary
TT/347/2001
INR13,000.00
/6789012
O.P.ROBERTS
Settlement details
32A
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/345/2001
NONREF
02092001INR37,500.00
ALLA0000234
The extract of header and text block of the IFN 195 Query Message sent by Allahabad Bank,
Bangalore Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000234
ALLA0000999
IFN 195
Text Block:
Field Description
20
21
Related Reference
75
Queries

Query
Information
TTP/579/2001
TT/345/2001
ALLA0000123
02092001INR37,500.00
27
System to Allahabad Bank, Bangalore Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000999
ALLA0000234
IFN 196

Reply
Text Block:
Field Description
20
21
Related Reference
76
Answer
Information
TT/345/2001
TTP/579/2001
Header Block:
Sender
Receiver
Message Type
ANDB0000234
ANDB0000999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/579/2001
TT/345/2001
02092001INR37,500.00
ALLA0000123
In case, Allahabad Bank, Bangalore is unable to apply one or more TTs conveyed in the above
message, it should still send the IFN 900 Message for the full amount and vouch reversal credits
to Allahabad Bank, Kolkata separately to avoid reconciliation errors.
1.3.3.1.2.
Reconciliation of TT Message using IFN 910 & 195/196 messages
debit. The Reconciliation System sends an IFN 196 authorizing the debit and treats the
transaction as reconciled without waiting for an IFN 900 from the Paying Branch. The Paying
branch applies funds.
28
Example:
On receipt of a valid and authenticated IFN 102 message, Allahabad Bank, Bangalore Branch
Reconciliation System sends an IFN 196 authorizing the debit and treats the transaction as
reconciled. Allahabad Bank, Bangalore Branch applies funds to beneficiaries accounts.
Message Flow:
XYZ LTD
FUNDS
ALLAHABAD
BANK
KOLKATA
IFN
910
ALLAHABAD BANK
RECONCILIATION
SYSTEM
IFN
102
K.L.RAM
M.N.RAHIM
O.P.ROBERTS
IFN
195
IFN
196
FUNDS
FUNDS
FUNDS
ALLAHABAD
BANK
BANGALORE
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000234
IFN 102

29
Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
50
Ordering Customer
71A
Details of Charges
21
32B
Currency & Amount
59
Beneficiary
Information
TT/345/2001
CREDIT
ALLA0000123
M/S XYZ LTD.,
KOLKATA
OUR
TT/345/2001
INR12,000.00
/4567890
K.L.RAM
21
32B
Currency & Amount
59
Beneficiary
TT/346/2001
INR12,500.00
/5678901
M.N.RAHIM
21
32B
Currency & Amount
59
Beneficiary
Settlement details
32A
Value Date,Currency & Amount
TT/347/2001
INR13,000.00
/6789012
O.P.ROBERTS
02092001INR37,500.00
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/345/2001
NONREF
02092001INR37,500.00
ALLA0000234
30
The extract of header and text block of the IFN 195 Query Message sent by Allahabad Bank,
Bangalore Branch to the Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000234
ALLA0000999
IFN 195
Text Block:
Field Description
20
21
Related Reference
75
Queries

Query
Information
TTP/579/2001
TT/345/2001
ALLA0000123
02092001INR37,500.00
System to Allahabad Bank, Bangalore Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000999
ALLA0000234
IFN 196
Text Block:
Field Description
20
21
Related Reference
76
Answer

Reply
Information
TT/345/2001
TTP/579/2001
1.3.3.2. Indirect Method:

Instead of sending the Payment Order to the Paying Branch, The Ordering Branch sends the IFN
102 message to the Reconciliation System. The Reconciliation System in turn, relays the IFN
102 message to the Paying Branch. The Paying branch applies funds and sends an IFN 900 to the
Reconciliation System. It is to be noted that the IFN 102 message from the Ordering Branch to
the Reconciliation System also acts as an Advice of Credit
Example:
message to the Banks Reconciliation System. The Banks Reconciliation System in turn sends
an IFN 102 message to Allahabad Bank, Bangalore.
31
funds to the beneficiaries accounts and reports the transaction by sending an IFN 900 Message
to the Banks Reconciliation System.
Message Flow:
XYZ LTD
ALLAHABAD
BANK
KOLKATA
FUNDS
IFN
102
ALLAHABAD BANK
RECONCILIATION
SYSTEM
IFN
102
K.L.RAM
M.N.RAHIM
O.P.ROBERTS
IFN
900
FUNDS
FUNDS
FUNDS
ALLAHABAD
BANK
BANGALORE
the Banks Reconciliation System, would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000123
ALLA0000999
IFN 102

32
Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
50
Ordering Customer
71A
Details of Charges
21
32B
Currency & Amount
57A
Account With Institution
59
Beneficiary
Information
TT/345/2001
CREDIT
ALLA0000123
M/S XYZ LTD.,
KOLKATA
OUR
TT/345/2001
INR12,000.00
ALLA0000234
/4567890
K.L.RAM
21
32B
Currency & Amount
57A
59
Beneficiary
TT/346/2001
INR12,500.00
ALLA0000234
/5678901
M.N.RAHIM
21
32B
Currency & Amount
57A
59
Beneficiary
TT/347/2001
INR13,000.00
ALLA0000234
/6789012
O.P.ROBERTS
Settlement details
32A
The extract of header and text block of the IFN 102 Message sent by the Banks Reconciliation
System to Allahabad Bank, Bangalore would be as follows:
Header Block:
Sender
Receiver
Message Type
ALLA0000999
ALLA0000234
IFN 102

Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
50
Ordering Customer
71A
Details of Charges
Information
TT/345/2001
CREDIT
ALLA0000123
M/S XYZ LTD.,
KOLKATA
OUR
33
21
32B
Currency & Amount
59
Beneficiary
TT/345/2001
INR12,000.00
/4567890
K.L.RAM
21
32B
Currency & Amount
59
Beneficiary
TT/346/2001
INR12,500.00
/5678901
M.N.RAHIM
21
32B
Currency & Amount
59
Beneficiary
Settlement details
32A
Value Date,Currency & Amount
TT/347/2001
INR13,000.00
/6789012
O.P.ROBERTS
02092001INR37,500.00
Header Block:
Sender
Receiver
Message Type
ANDB0000234
ANDB0000999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/345/2001
NONREF
02092001INR37,500.00
ALLA0000123
34
1.4. Customer Request for Transfer of Funds.

SFMS also supports messages, which enable the customer of a particular branch of a bank to
issue instructions through another branch of the bank to transfer funds from his account
maintained at the first branch to his own account or a third partys account maintained at one of
the branches of the bank or branches of another bank in the same center as the branch to which
the message is addressed.
The customer will have to execute a special agreement with the Account Servicing Branch
authorizing them to execute such instructions if they are guaranteed by another branch. IFN 101
Messages are used for relaying such requests for transfer of funds.
IFN 101 is a very useful message which, if properly implemented, enables customers to
move funds to their own accounts or to third party accounts from remote centres. Such
requests, if promptly executed, virtually realise Any Branch Banking.
IFN 101 (Single Customer TT) messages should be used for relaying Customer TTs.
1.4.1. Transfer is for credit of a single beneficiary who also banks with the
receiver of the message. (IFN 101)
As the beneficiary banks with the branch to which the IFN 101 message is addressed, the funds
are applied to the debit of the ordering customer. No reporting to the Banks Reconciliation
System is involved since the movement of funds is from one account of the branch to another.
Example:
On 10.09.2001, M/s. ABC Ltd request Bank of Maharastra, Pune to instruct their Karad branch
to debit M/s. ABC Ltds account with Bank of Maharastra, Karad and transfer Rs 10,000.00
same day value for credit of Account No. 76543 of JK&Co with Bank of Maharastra, Karad in
full settlement of Inv. 74747. ABC Ltds reference is PYT173314. All charges are for
beneficiarys account.
The information to be provided by Bank of Maharastra, Pune to Bank of Maharastra, Karad in
the IFN 101 message would be as follows:
Sending Branch
Receiving Branch
Transfer Request Reference No.
Ordering Party
Their Reference
: Bank of Maharastra, Pune

(IFSC say BOMA0000001)
: Bank of Maharastra, Karad
(IFSC say BOMA 0000456)
: DR5678/2001
: ABC Ltd
: PYT173314
35
Amount
Value Date
Account to be debited
Beneficiary
Details of Payment for Beneficiary
Paying Bank charges to be borne by
: Rs 10,000.00
: 10.09.2001
: 3534981
: JK&Co
: 76543
: Full settlement of Inv. 74747
: Beneficiary
Bank of Maharastra, Pune sends an IFN 101 message to its Karad branch. On receipt of a valid
IFN 101 message, Bank of Maharastra, Karad debits ABC Ltds account and credits JK&Cos
account and sends a debit advice to the former and a credit advice to the latter.
Message Flow:
ABC LTD
INSTRUCTION
DEBIT
ADVICE
IFN
101
CREDIT
ADVICE
JK&CO
JK&COS
ACCOUNT
WITH BOM,
KARAD
BANK OF
MAHARASTRA
PUNE
FUNDS
BANK OF
MAHARASTRA
KARAD
ABC LTDS
ACCOUNT
WITH BOM,
KARAD
The extract of header and text block of the IFN 101 Message sent by Bank of Maharastra, Pune
to their Karad branch would be as follows:
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 101
Bank of Maharastra, Pune

Bank of Maharastra, Karad
Request for Transfer
36
Text Block:
Field Description
20
Senders Reference No.
21
Customer Specified Reference
50H
Ordering Customer
30
21
32B
59
Requested Execution Date

Currency & Amount
Beneficiary
70
71A
Remittance Information
Details of Charges
Information
DR5678/2001
PYT173314
/3534981
ABC LTD
10092001
DR5678/2001
INR10,000.00
/76543
JK&CO
INV. 74747 FULL SETTLEMENT
BEN
1.4.2. Transfer is for credit of multiple beneficiaries who also bank with the
branch to which the IFN 101 message is addressed.
As the beneficiaries bank with the branch to which the IFN 101 message is addressed, the funds
System is involved since the movement of funds is from one account of the branch to other
accounts in the same branch.
Example:
to debit M/s. ABC Ltds account with Bank of Maharastra, Karad and transfer Rs 10,000.00 &
Rs 12,000.00 same day value for credit of Account No. 76543 of JK&Co and 9211 of AN&Co.
respectively with Bank of Maharastra, Karad in full settlement of Inv. 74747 and Inv. No. 24680
respectively. ABC Ltds reference is PYT173315. All charges are for beneficiarys account.
Bank of Maharastra, Pune Reference No. is DR5679/2001 for the IFN 101 and DR5679/01/2001
and DR5679/02/2001 for the individual transactions.
Common Information:
Sending Branch
Receiving Branch
Ordering Party
Their Reference
Value Date

: DR5679/2001
: ABC Ltd
: PYT173314
: 10.09.2001
37
: 3534981
Paying Bank charges to be borne by : Beneficiaries
Information relevant to individual transactions:
Bank of Maharastra
Pune Reference Nos.
DR5679/01/2001
DR5679/02/2001
Amount
10,000.00
12,000.00
Beneficiary Account
No.
JK&Co.
76543
AN&Co.
9211
Payment Details for

Beneficiary
Full settlement Inv. 74747
Bank of Maharastra, Pune sends an IFN 101 message to their Karad branch. On receipt of a valid
IFN 101 message, Bank of Maharastra, Karad debits ABC Ltds account and credits JK&Co and
AN&Cos accounts and sends debit advice to the instructing party and credit advices to the
beneficiaries.
Message Flow:
ABC LTD
INSTRUCTION
DEBIT
ADVICE
JK&CO
IFN
101
CREDIT
ADVICE
CREDIT
ADVICE
AN&CO
JK&COS
ACCOUNT
AN&COS
ACCOUNT
BANK OF
MAHARASTRA
PUNE
FUNDS
BANK OF
MAHARASTRA
KARAD
ABC LTDS
ACCOUNT
FUNDS
38
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 101

Text Block:
Field Description
20
21
50H
Ordering Customer
30
Transaction details 1
21
32B
Currency & Amount
59
Beneficiary
70
71A
Details of Charges
21
32B
Currency & Amount
59
Beneficiary
70
71A
Details of Charges
Information
DR5679/2001
PYT173315
/3534981
ABC LTD
10092001
DR5679/01/2001
INR10,000.00
/76543
JK&CO
BEN
DR5679/02/2001
INR12,000.00
/9211
AN&CO
BEN
39
1.4.3. Transfer is for credit of a single beneficiary who banks with another
branch of the same bank. (IFN 101, 100, 900 & 910)
As the beneficiary banks with another branch of the same bank, after debiting of the ordering
customers account, the branch to which the IFN 101 message is addressed sends an IFN 100
message to the branch which maintains the beneficiarys account. An IFN 910 message is used
for reporting the inter branch credit transaction to the Banks Reconciliation System. The
beneficiarys branch applies funds on receipt of a valid IFN 100 message and reports the debit
transaction to the Banks Reconciliation System using an IFN 900 message.
Example:
same day value for credit of Account No. 56765 of GDD Ltd with Bank of Maharastra, Satara in
full settlement of Inv. 89012. ABC Ltds reference is PYT173316. All charges are for
beneficiarys account. Bank of Maharastra, Pune Reference No. is DR5680/2001.
Sending Branch
Receiving Branch
Ordering Party
Their Reference
Amount
Value Date
Beneficiary

: DR5680/2001
: ABC Ltd
: PYT173316
: Rs 10,000.00
: 10.09.2001
: 3534981
: GDD Ltd
: 56765
: Bank of Maharastra, Satara
(IFSC say BOMA 0000123)
Details of Payment for Beneficiary : Full settlement of Inv. 89012
Paying Bank charges to be borne by : Beneficiary
IFN 101 message, Bank of Maharastra, Karad debits ABC Ltds account and sends an IFN 100
message (TT Ref: TT/876/2001) to Bank of Maharastra, Satara instructing them to credit the
proceeds to Account No. 56765 of GDD Ltd. An IFN 910 message is sent to the Banks
Reconciliation System.
40
On receipt of a valid and authenticated IFN 100 message, Bank of Maharastra, Satara applies
funds to GDD Ltd.s account and reports the transaction by sending a debit report to the Banks
Reconciliation System. Their Reference is TTP/1020/2001.
Message Flow:
ABC LTD
INSTRUCTION
DEBIT
ADVICE
BANK OF
MAHARASTRA
PUNE
IFN
101
ABC LTDS
ACCOUNT
FUNDS
BANK OF
MAHARASTRA
KARAD
GDD LTD
CREDIT
ADVICE
GDD LTDS
ACCOUNT
FUNDS
IFN
100
BANK OF
MAHARASTRA
SATARA
IFN
910
BOM
RECONCILIATION
SYSTEM
IFN
900
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 101

41
Text Block:
Field Description
20
21
50H
Ordering Customer
30
21
32B
57A
59

Currency & Amount
Account with Institution
Beneficiary
70
71A
Details of Charges
Information
DR5680/2001
PYT173316
/3534981
ABC LTD
10092001
DR5680/2001
INR10,000.00
BOMA0000123
/56765
GDD LTD
BEN
The extract of header and text block of the IFN 100 Message sent by Bank of Maharastra, Karad
to their Satara branch would be as follows:
Header Block:
Sender
Receiver
Message Type
BOMA0000456
BOMA0000123
IFN 100

Bank of Maharastra, Satara
Customer Transfer
Text Block:
Field Description
20
32A
Value Date, Currency & Amount
50
Ordering Customer
59
Beneficiary
70
71A
Details of payment
Details of Charges
Information
TT/876/2001
10092001INR10,000.00
ABC LTD
/56765
GDD LTD
BEN
to the Reconciliation System (IFSC Say BOMA0000999) would be as follows:
Header Block:
Sender
Receiver
Message Type
BOMA0000456
BOMA0000999
IFN 910

Bank of Maharastra Reconciliation System
Credit Advice
42
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/876/2001
NONREF
10092001INR10,000.00
BOMA0000123
The extract of header and text block of the IFN 900 Message sent by Bank of Maharastra, Satara
Header Block:
Sender
Receiver
Message Type
BOMA0000123
BOMA0000999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/1020/2001
TT/876/2001
10092001INR10,000.00
BOMA0000456
1.4.4. Transfer is for credit of multiple beneficiaries who bank with other
branches of the bank. (IFN 100, 101, 102, 900 & 910)
As the beneficiaries bank with other branch(es) of the same bank, after debiting of the ordering
customers account, the branch to which the IFN 101 message is addressed sends one or more
IFN 100 or IFN 102 messages to the branch(es) which maintain the beneficiaries accounts. IFN
910 messages are used for reporting the inter branch credit transactions to the Banks
Reconciliation System. The beneficiaries branches apply funds on receipt of valid IFN 100 or
IFN 102 messages and report the debit transaction(s) to the Banks Reconciliation System using
IFN 900 message(s).
Example:
Rs 12,000.00 same day value for credit of Account No. 76543 of JK&Co and 9211 of AN&Co.
respectively with Bank of Maharastra, Satara in full settlement of Inv. 74747 and Inv. No. 24680
respectively. ABC Ltds reference is PYT173317. All charges are for beneficiariesaccounts.
43
Bank of Maharastra, Pune Reference No. is DR5679/2001 for the IFN 101 and DR5679/01/2001
and DR5679/02/2001 for the individual transactions.
Common Information:
Sending Branch
Receiving Branch
Ordering Party
Their Reference
Value Date

: DR5679/2001
: ABC Ltd
: PYT173314
: 10.09.2001
: 3534981
: Bank of Maharastra, Satara
: Beneficiaries

Bank of Maharastra
Pune Reference Nos.
DR5679/01/2001
DR5679/02/2001
Amount
10,000.00
12,000.00
Beneficiary Account
No.
JK&Co.
76543
AN&Co.
9211
Payment Details for

Beneficiary
Bank of Maharastra, Pune sends an IFN 101 message to its Karad branch. On receipt of a valid
IFN 101 message, Bank of Maharastra, Karad debits ABC Ltds account sends a debit advice to
them and sends an IFN 102 message (TT Ref: TT/877/2001) to Bank of Maharastra, Satara
instructing them to credit the proceeds to Account No. 76543 of JK&Co and 9211 of AN&Co.
respectively. Bank of Maharastra, Karad Reference Nos. for the individual TTs are TT/321/2001
and TT/322/2001 respectively. An IFN 910 message is sent to the Banks Reconciliation System.
On receipt of a valid and authenticated IFN 102 message, Bank of Maharastra, Satara applies
funds to JK&Co and AN&Cos accounts and reports the transaction by sending a debit report to
the Banks Reconciliation System and sends credit advices to the beneficiaries. Their Reference
No. is TTP/578/2001.
44
Message Flow:
ABC LTD
BANK OF
MAHARASTRA
PUNE
INSTRUCTION
DEBIT
ADVICE
IFN
101
FUNDS
BANK OF
MAHARASTRA
KARAD
JK&CO
AN&CO
IFN
102
CREDIT
ADVICE
CREDIT
ADVICE
JK&COS
ACCOUNT
AN&COS
ACCOUNT
FUNDS
BANK OF
MAHARASTRA
SATARA
ABC LTDS
ACCOUNT
IFN
910
BOM
RECONCILIATION
SYSTEM
IFN
900
FUNDS
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 101

Text Block:
Field Description
20
21
Information
DR5679/2001
PYT173315
45
50H
Ordering Customer
/3534981
ABC LTD
10092001
30
21
32B
Currency & Amount
57A
59
Beneficiary
DR5679/01/2001
INR10,000.00
BOMA0000123
/76543
JK&CO
BEN
70
71A
Details of Charges
21
32B
Currency & Amount
57A
59
Beneficiary
70
71A
DR5679/02/2001
INR12,000.00
BOMA0000123
/9211
AN&CO
BEN
Details of Charges
to their Satara branch would be as follows:
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 102

Multiple Customer Transfer
Text Block:
Field Description
20
File Reference
23
Bank Operation Code
51A
50
Ordering Customer
71A
Details of Charges
21
32B
Currency & Amount
59
Beneficiary
70
21
32B
Currency & Amount
Information
TT/877/2001
CREDIT
IFSC BOMA0000456
M/S ABC LTD.
BEN
TT/321/2001
INR10,000.00
/76543
JK&CO
TT/322/2001
INR12,000.00
46
59
Beneficiary
/9211
AN&CO
70
Settlement details
32A
Header Block:
Sender
Receiver
Message Type
BOMA0000456
BOMA0000999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TT/877/2001
NONREF
10092001INR22,000.00
BOMA0000123
The extract of header and text block of the IFN 900 Message sent by Bank of Maharastra, Satara
Header Block:
Sender
Receiver
Message Type
BOMA0000123
BOMA0000999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/578/2001
TT/877/2001
10092001INR22,000.00
BOMA0000456
Though in the above example, all the beneficiaries have been shown to be banking with one
branch only, more often than not, beneficiaries would be banking in several branches of the
bank. In such case, several IFN 100 messages (to those branches where only one beneficiary has
an account) and IFN 102 messages (to those branches where more than one beneficiaries have
accounts) will have to be sent to the concerned branches.
47
1.4.5. Transfer is for credit of a single beneficiary who banks with another
banks branch in the same enter as the branch to which the message
is addressed. (IFN 101)
As the beneficiary banks with the branch of another bank, the branch to which the IFN 101
message is addressed uses traditional methods of payment such as pay orders. After debiting the
ordering customers account, the receiving branch sends a pay order for proceeds favouring the
beneficiary and forwards it to the beneficiary. As the funds are settled through local clearing, the
Banks Reconciliation System is not involved in settlement/reconciliation of funds.
Example:
same day value for credit of M/s GDD Ltd in full settlement of Inv. 89012. ABC Ltds reference
is PYT173316. All charges are for beneficiarys account. M/s GDD Ltd bank with Bank of India,
Karad.
Sending Branch
Receiving Branch
Ordering Party
Their Reference
Amount
Value Date
Beneficiary
Details of Payment for Beneficiary

: DR5680/2001
: ABC Ltd
: PYT173316
: Rs 10,000.00
: 10.09.2001
: 3534981
: GDD Ltd
: 56765
: Union Bank of India, Karad
(IFSC say UBIN0000321)
: Full settlement of Invoice 89012
IFN 101 message, Bank of Maharastra, Karad debits ABC Ltds account and issues a pay order
for the proceeds favouring M/s GDD Ltd and forwards it to the beneficiaries and sends a debit
advice to M/s. ABC Ltd.
48
Message Flow:
ABC LTD
BANK OF
MAHARASTRA
PUNE
INSTRUCTION
DEBIT
ADVICE
GDD LTD
IFN
101
BANK OF
MAHARASTRA
KARAD
FUNDS
FUNDS
ABC LTDS
ACCOUNT
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 101

Text Block:
Field Description
20
21
50H
Ordering Customer
30
21
32B
Currency & Amount
57A
59
Beneficiary
70
71A
Details of Charges
Information
DR5680/2001
PYT173316
ABC LTD
10092001
DR5680/2001
INR10,000.00
UBIN0000321
GDD LTD
INV. 89012 full settlement
BEN
49
1.4.6. Transfer is for credit of multiple beneficiaries who bank with other
banks branches in the same enter as the branch to which the
message is addressed. (IFN 101)
As the beneficiaries bank with the branch to which the IFN 101 message is addressed, the funds
System is involved since the movement of funds is from one account of the branch to other
accounts in the same branch.
Example:
Rs 12,000.00 same day value for credit of M/s JK&Co and M/s AN&Co. in full settlement of
Inv. 74747 and Inv. No. 24680 respectively. ABC Ltds reference is PYT173315. All charges are
for beneficiaries account. The beneficiaries bank with Bank of India, Karad. Bank of Maharastra,
Pune Reference No. is DR5679/2001 for the IFN 101 and DR5679/01/2001 and
DR5679/02/2001 for the individual transactions.
Common Information:
Sending Branch
Receiving Branch
Ordering Party
Their Reference
Value Date

: DR5679/2001
: ABC Ltd
: PYT173315
: 10.09.2001
: 3534981
: Union Bank of India, Karad
: Beneficiaries

Bank of Maharastra
Pune Reference Nos.
DR5679/01/2001
DR5679/02/2001
Amount
10,000.00
12,000.00
Beneficiary Account
No.
JK&Co.
76543
AN&Co.
9211
Payment Details for

Beneficiary
50
Bank of Maharastra, Pune sends an IFN 101 message to their Karad branch. Bank of
Maharastra,. On receipt of a valid IFN 101 message, Bank of Maharastra, Karad debits ABC
Ltds account and issues pay orders for the proceeds favouring M/s JK&Co. and AN&Co. and
forwards it to the beneficiaries and sends a debit advice to M/s. ABC Ltd.
Message Flow:
ABC LTD
BANK OF
MAHARASTRA
PUNE
INSTRUCTION
DEBIT
ADVICE
IFN
101
JK&CO
FUNDS
AN&CO
BANK OF
MAHARASTRA
KARAD
FUNDS
FUNDS
ABC LTDS
ACCOUNT
Header Block:
Sender
Receiver
Message Type
BOMA0000001
BOMA0000456
IFN 101

Text Block:
Field Description
20
21
50H
Ordering Customer
30
21
32B
Currency & Amount
57A
Account with institution
59
Beneficiary
70
Information
DR5680/2001
PYT173315
/3534981
ABC LTD
10092001
DR5680/01/2001
INR10,000.00
UBIN0000321
JK&CO
51
71A
Details of Charges
21
32B
Currency & Amount
57A
Account with institution
59
Beneficiary
70
71A
Details of Charges
BEN
DR5680/02/2001
INR12,000.00
UBIN0000321
AN&CO
BEN
1.5. Third Party Instruction or Request for Debit of Customers

Account. (IFN 104)
A creditor or his branch may instruct or request the debtors branch either directly or through an
intermediary branch, to debit the debtors account and transfer the proceeds to the creditors
branch for credit to the creditors account. Whether the message represents an instruction or a
request depends on the terms and conditions laid down in a special agreement executed by the
debtor with the creditor and the account servicing branch.
IFN 104 messages enable banks and term lending institutions in ensuring timely repayment
of installments. This is achieved by stipulating at the time of granting of the loan, that the
borrower should make prior arrangements with the account servicing institution to accept
instructions or requests from the lender banks to transfer the installment amounts to them
(lender banks).
IFN 104 message is used for relaying the instruction/request for debiting the customer and
transferring of funds. The creditors branch sends an IFN 104 Message to the debtors branch.
On receipt of the message, the debtors branch debits his account and transfers the amount to the
creditors branch using an IFN 100 Message. On receipt of the IFN 100 Message, the creditors
branch applies funds to his account.
As such, it will be necessary to agree on the format of the mandate and also draw up country
specific message usage rules before implementing this message type.
52
1.6. DD Related Messages.

At present, there are three IFN Message Formats for relaying of information pertaining to DD
related transactions.
1.6.1. DD Advices. (IFN 110)

IFN 110 messages are used for relaying single or multiple DD advices.
Example:
On 15.10.2001, Bank of India, Surat has drawn following DDs on Bank of India, Lucknow.
DD No.
300007
300023
300045
Amount (Rs.)
1,50,000.00
1,00,000.00
2,20,000.00
Payee
FGH Ltd.
SD&Co.
ABC Charitable Trust
The extract of header and text block of the IFN 110 message sent by Bank of India, Surat would
be as follows:
Header Block:
Sender
Receiver
Message Type
BKID0000101
BKID0000756
IFN 110
Text Block:
Field Description
20
Transaction details 1.
21
DD Number
30
Date of Issue
32B
Currency & Amount
59
Payee
21
DD Number
30
Date of Issue
32B
Currency & Amount
59
Payee
21
DD Number
30
Date of Issue
32B
Currency & Amount
59
Payee
Bank of India, Surat

Bank of India, Lucknow.
Advice of Cheque (DD)
Information
DD ADVICES
300007
15102001
INR1,50,000.00
FGH LTD
300023
15102001
INR1,00,000.00
SD&CO.
300045
15102001
INR2,20,000.00
ABC CHARITABLE TRUST
53
1.6.2. DD Stop Payment Requests. (IFN 111)

IFN 111 messages are used for relaying DD stop payment requests.
Example:
On 25.10.2001, the purchaser of DD No. 300045 reported to Bank of India, Surat that the DD in
question appeared to have been lost in transit and requested for issue a duplicate in lieu. Bank of
India, Surat sends an IFN 111 to the drawee branch requesting for stop payment of the DD.
The extract of header and text block of the IFN 111 message sent by Bank of India, Surat would
be as follows:
Header Block:
Sender
Receiver
Message Type
BKID0000101
BKID0000756
IFN 111
Text Block:
Field Description
20
21
DD Number
30
Date of Issue
32B
Currency & Amount
59
Payee
75
Reason for stop payment
CODE: /21/

Request for Stop Payment
Information
DD STOP PAYMENT
300045
15102001
INR2,20,000.00
/21/
DD lost or stolen
1.6.3. Replies to DD Stop Payment Requests. (IFN 112)

IFN 112 messages are used for replying to DD stop payment requests.
Example 1:
On 26.10.2001, Bank of India, Lucknow responds to the stop request by sending an IFN 112
message advising that the DD is still unpaid and that the stop payment request has been noted.
The extract of header and text block of the IFN 112 message sent by Bank of India, Lucknow
would be as follows:
54
Header Block:
Sender
Receiver
Message Type
BKID0000756
BKID0000101
IFN 112
Text Block:
Field Description
20
21
DD Number
30
Date of Issue
32B
Currency & Amount
59
Payee
76
Reply
CODE:
/13/

Reply to Request for Stop Payment
Information
DD STOP PAYMENT
300045
15102001
INR2,20,000.00
/13/
Stop payment instruction duly recorded
Example 2:
On 26.10.2001, Bank of India, Lucknow responds to the stop request by sending an IFN 112
message advising that the stop payment request cannot be accepted as the DD has already been
paid on 20.10.2001.
The extract of header and text block of the IFN 112 message sent by Bank of India, Lucknow
would be as follows:
Header Block:
Sender
Receiver
Message Type
BKID0000756
BKID0000101
IFN 112
Text Block:
Field Description
20
21
DD Number
30
Date of Issue
32B
Currency & Amount
59
Payee
76
Reply
CODE:
/12/

Reply to Request for Stop Payment
Information
DD STOP PAYMENT
300045
15102001
INR2,20,000.00
/12/DD PAID IN CLEARING ON
20.10.2001.
Stop payment instructions not acceptable
55
2. Inter-Branch Messages involving Intra-Bank and InterBank Transfer of Funds:

Often, branches of the same bank exchange messages, which involve transfer of funds to or
receipt of funds from another branch of the same bank or another bank. There are several IFN
message formats available for relaying such messages.
Various scenarios involving such messages have been discussed below:
2.1. Request for transfer of funds from DAD account of one branch
to another. (IFN 202, 210, 900 & 910)
The branch requesting for transfer of funds sends an IFN 202 message to the branch that is being
requested to transfer the funds. The receiver of the message transfers the amount by the
traditional method of sending to the local RBI DAD, an RBI cheque for the amount with the RBI
TT requisition slip requesting transfer of funds.
Example:
On 10.10.2001, Canara Bank, Chennai sends an IFN 202 message to Canara Bank, New Delhi
requesting transfer of Rs 10 Crores same day value from DAD account of Canara Bank with
RBI, New Delhi to DAD account (No. 987654) of Canara Bank with RBI, Chennai. Canara
Bank, Chennai also sends an IFN 910 message to the Banks Reconciliation System. Their
Reference No. is TRF/789/2001. Canara Bank, Chennai also sends an IFN 210 message to RBI
Chennai advising them that it expects Rs 10 crores to be credited same day value into its
Account No. 987654 through Canara Bank, New Delhi and RBI, New Delhi.
On receipt of a valid and authenticated IFN 202 message, Canara Bank, New Delhi Branch
arranges with RBI New Delhi to transfer funds as requested sends an IFN 900 message to Canara
Bank, Chennai advising them that the funds have been transferred and reports the transaction by
sending an IFN 900 message to the Banks Reconciliation System. Their Reference No. is
TTP/1357/2001
It is assumed that the IFSCs of the various entities are as follows:
Canara Bank Chennai
Canara Bank New Delhi
Canara Bank Reconciliation System
RBI, Chennai
RBI, New Delhi
: CNRB0000321
: CNRB0000654
: CNRB0009999
: RBIN0000CHN
: RBIN0000DEL
56
Message Flow:
RBI CHENNAI
A/C CANARA
BANK
IFN
210
CANARA
BANK
CHENNAI
F
U
N
D
S
RBI NEW DELHI

A/C CANARA
BANK
IFN
900
RBI
CHEQUE &
TT REQUEST
IFN
202
IFN
910
CANARA BANK
RECONCILIATION
SYSTEM
CANARA
BANK
NEW DELHI
IFN
900
The extract of header and text block of the IFN 202 Message sent by Canara Bank, Chennai to
Canara Bank, New Delhi Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
CNRB0000321
CNRB0000654
IFN 202
Canara Bank Chennai

General Financial Institution Transfer
Text Block:
Field Description
20
21
Related Reference
32A
54A
Receivers Correspondent
57A
58A
Beneficiary Institution
Information
TRF/789/2001
NONREF
10102001INR10,00,00,000.00
RBIN0000NDL
RBIN0000CHN
CNRB0000321
Header Block:
Sender
Receiver
Message Type
CNRB0000321
CNRB0009999
IFN 910
Canara Bank Chennai

Credit Advice
57
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TRF/789/2001
NONREF
10102001INR10,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 210 Message sent by Canara Bank Chennai to
RBI, Chennai would be as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
25
30
21
32B
52A
56A
CNRB0000321
RBIN0000CHN
IFN 210
Canara Bank Chennai

RBI, Chennai
Notice to Receive
Description
Value Date
Related Reference
Currency & Amount
Ordering Institution
Intermediary
Information
TRF/789/2001
987654
10102001
TRF/789/2001
10102001INR10,00,00,000.00
CNRB0000654
RBIN0000NDL
The extract of header and text block of the IFN 900 Message sent by Canara Bank, New Delhi
Branch to Canara Bank, Chennai would be as follows:
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0000321
IFN 900
Canara Bank, New Delhi

Canara Bank , Chennai
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
Information
TTP/1357/2001
TRF/789/2001
10102001INR10,00,00,000.00
58
The extract of header and text block of the IFN 900 Message sent by Canara Bank, New Delhi
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0009999
IFN 900
Canara Bank, New Delhi

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/1357/2001
TRF/789/2001
10102001INR10,00,00,000.00
CNRB0000321
2.2. Request for transfer of funds from DAD account of one branch
to DAD account of two or more branches. (IFN 203, 210, 900 &
910)
Funds Managers can send an IFN 203 message to a branch of the Bank requesting it to transfer
funds to DAD accounts of 2 or more branches of the same bank. IFN 210 messages are sent to
each of the branches whose DAD account is being credited to advise them that their DAD
accounts are being funded. The receiver of the 203 message uses traditional means for
transferring the amounts to the DAD accounts of the concerned branches and uses IFN 900
messages to advise the branches whose DAD accounts are being funded. IFN 900 messages are
also used to relay debit advices to the Banks Reconciliation System. Receivers of IFN 210
messages ensure that the funds are credited to their DAD accounts and send IFN 910 messages to
advise the Banks Reconciliation System of the credits.
Example:
On 10.10.2001, Central Funds Dept., Canara Bank sends an IFN 203 message to Canara Bank,
New Delhi requesting transfer of Rs 25 Crores same day value from DAD account of Canara
Bank with RBI, New Delhi to various DAD accounts of Canara Bank as detailed below.
DAD account with RBI, Chennai Rs 10 Crores
DAD account with RBI, Mumbai Rs 8 Crores
DAD account with RBI, Kolkata Rs 7 Crores
Central Funds Dept., Canara Bank also sends an IFN 210 message each to the above three
branches with Reference Nos. FND/567/2001, FND/568/2001 and FND/569/2001 respectively
which are also the Reference Nos. for individual transactions in the IFN 203 message.
59
On receipt of a valid and authenticated IFN 203 message, Canara Bank, New Delhi Branch
arranges with RBI New Delhi to transfer funds as requested and reports the transaction by
sending IFN 900 messages to the Banks Reconciliation System. It also sends IFN 300 messages
to the branches whose DAD accounts are being funded.
On receipt of valid IFN 210 messages from the funds department, the recipient branches in turn
send IFN 210 messages to the local RBI offices advising them that their accounts are being
funded. The branches ensure that their respective DAD accounts have been credited and send
IFN 910 messages to the Banks Reconciliation System, advising the credits.
It is assumed that the IFSC codes of the various entities are as follows:
Canara Bank Chennai
: CNRB0000321
Canara Bank Kolkata
: CNRB0000789
Canara Bank Mumbai
: CNRB0000876
: CNRB0000654
Canara Bank Funds Department
: CNRB0005555
Canara Bank
RBI, Chennai
: RBIN0000CHN
RBI, Kolkata
: RBIN0000CAL
RBI, Mumbai
: RBIN0000MUM
RBI, New Delhi
: RBIN0000NDL
And Account Nos. of Canara Banks accounts with various RBI Offices are as follows:
RBI, Chennai
RBI, Kolkata
RBI, Mumbai
RBI, New Delhi
: CHNCAN135
: CALCAN357
: MUMCAN579
: NDLCAN791
60
Message Flow:
IFN
210
IFN
210
CANARABANK
FUNDS DEPT.
IFN
210
CANARA
BANK
CANARA
CHENNAI
BANK
CANARA
MUMBAI
BANK
KOLKATA
IFN
210
IFN
900
IFN
910
IFN
900
IFN
910
CANARA BANK
RECONCILIATION
SYSTEM
CANARA
BANK
NEW DELHI
IFN
900
IFN
900
IFN
210
IFN
910
IFN
900
IFN
203
IFN
210
RBI CHENNAI
A/C CANARA
RBI MUMBAI
BANK
RBI KOLKATA
A/C CANARA
BANKA/C CANARA
BANK
IFN
900
F
U
N
D
S
F
U
N
D
S
F
U
N
D
S
RBI N. DELHI
A/C CANARA
BANK
RBI
CHEQUE &
TT REQUEST
The extract of header and text block of the IFN 203 Message sent by Central Funds Dept.,
Canara Bank to Canara Bank, New Delhi Branch would be as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
19
30
54A
CNRB0005555
CNRB0000654
IFN 203
Canara Bank, Central Funds Dept.

Canara Bank, New Delhi Branch
Multiple Financial Institution Transfer
Description
Sum of Amounts
Value Date
Receivers Correspondent
Information
25,00,00,000.00
10102001
RBIN0000NDL
61
Transaction Details 1
20
32B
Currency & Amount
57A
58A
20
32B
Currency & Amount
57A
58A
20
32B
Currency & Amount
57A
58A
FND/567/2001
10102001INR10,00,00,000.00
RBIN0000CHN
CNRB0000321
FND/568/2001
10102001INR8,00,00,000.00
RBIN0000MUM
CNRB0000876
FND/569/2001
10102001INR7,00,00,000.00
RBIN0000CAL
CNRB0000789
Canara Bank to Canara Bank Chennai, would be as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
25
30
21
32B
52A
CNRB0005555
CNRB0000321
IFN 210

Canara Bank, Chennai Branch
Notice to Receive
Description
Value Date
Related Reference
Currency & Amount
Information
FND/567/2001
RBIN0000CHN
10102001
FND/567/2001
10102001INR10,00,00,000.00
CNRB0000654
Canara Bank to Canara Bank Mumbai, would be as follows:
Header Block:
Sender
Receiver
Message Type
CNRB0005555
CNRB0000876
IFN 210

Canara Bank, Mumbai Branch
Notice to Receive
Text Block:
Field
Description
20
25
Information
FND/568/2001
RBIN0000MUM
62
30
21
32B
52A
Value Date
Related Reference
Currency & Amount
10102001
FND/568/2001
10102001INR8,00,00,000.00
CNRB0000654
Canara Bank to Canara Bank Kolkata, would be as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
25
30
21
32B
52A
CNRB0005555
CNRB0000789
IFN 210

Canara Bank, Kolkata Branch
Notice to Receive
Description
Value Date
Related Reference
Currency & Amount
Information
FND/569/2001
RBIN0000CAL
10102001
FND/569/2001
10102001INR7,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 210 Message sent by Canara Bank Chennai, to
RBI, Chennai would be as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
25
30
21
32B
52A
CNRB0000321
RBIN0000CHN
IFN 210

RBI, Chennai
Notice to Receive
Description
Value Date
Related Reference
Currency & Amount
Information
FND/567/2001
CHNCAN135
10102001
FND/567/2001
10102001INR10,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 210 Message sent by Canara Bank Mumbai, to
RBI, Mumbai would be as follows:
63
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
25
30
21
32B
52A
CNRB0000876
RBIN0000MUM RBI, Mumbai
IFN 210
Notice to Receive
Description
Value Date
Related Reference
Currency & Amount
Information
FND/568/2001
MUMCAN579
10102001
FND/568/2001
10102001INR8,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 210 Message sent by Canara Bank Kolkata, to
RBI Kolkata would be as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
25
30
21
32B
52A
CNRB0000789
RBIN0000CAL
IFN 210

RBI, Kolkata
Notice to Receive
Description
Value Date
Related Reference
Currency & Amount
Information
FND/569/2001
CALCAN357
10102001
FND/569/2001
10102001INR7,00,00,000.00
CNRB0000654
Header Block:
Sender
Receiver
Message Type
CNRB0000321
CNRB0009999
IFN 910

Credit Advice
64
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TRF/567/2001
TRF/567/2001
10102001INR10,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 910 Message sent by Canara Bank, Mumbai to
Header Block:
Sender
Receiver
Message Type
CNRB0000876
CNRB0009999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TRF/568/2001
TRF/568/2001
10102001INR8,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 910 Message sent by Canara Bank, Kolkata to
Header Block:
Sender
Receiver
Message Type
CNRB0000789
CNRB0009999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TRF/569/2001
TRF/569/2001
10102001INR7,00,00,000.00
CNRB0000654
The extract of header and text block of the IFN 900 Messages sent by Canara Bank, New Delhi
Branch to Canara Bank, Chenai would be as follows:
65
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0000321
IFN 900

Canara Bank, Chennai
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
Information
TRF/567/2001
NONREF
10102001INR10,00,00,000.00
Branch to Canara Bank, Mumbai would be as follows:
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0000876
IFN 900

Canara Bank, Mumbai
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
Information
TRF/568/2001
NONREF
10102001INR8,00,00,000.00
Branch to Canara Bank, Kolkata would be as follows:
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0000789
IFN 900

Canara Bank, Kolkata
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
Information
TRF/569/2001
NONREF
10102001INR7,00,00,000.00
66
1.
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0009999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
2.
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0009999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
3.
Header Block:
Sender
Receiver
Message Type
CNRB0000654
CNRB0009999
IFN 900
Information
TRF/567/2001
NONREF
10102001INR10,00,00,000.00
CNRB0000321
Information
TRF/568/2001
NONREF
10102001INR8,00,00,000.00
CNRB0000876

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TRF/569/2001
NONREF
10102001INR7,00,00,000.00
CNRB0000789
67
2.3. Request for transfer of funds from one banks branch to

another banks branch. (IFN 202, 201, 900 & 910)
IFN 202 messages can be used to instruct a branch to transfer funds using traditional methods to
another Banks branch. Usually the proceeds of such remittances represent shortfalls in current
accounts maintained by bank branches with the branch of another bank, which maintains the
clearing house in the centre where the branch requesting transfer of funds is located.
Example:
On 15.10.2001, Bank of Baroda, Mysore sends an IFN 202 message to Bank of Baroda, Mumbai
requesting transfer of Rs 2 Crores same day value to State Bank of India, Mumbai. The proceeds
represent funds borrowed by Bank of Baroda, Mysore from State Bank of India, Mysore (which
manages the Mysore Bankers Clearing House) to make up the short fall in the current account
maintained by Bank of Baroda, Mysore with State Bank of India, Mysore. Bank of Baroda,
Mysore also sends an IFN 910 message to the Banks Reconciliation System. Their Reference
No. is TTDISC/234/2001.
State Bank of India, Mysore sends an IFN 210 message with Reference No. TTRECV/765/2001
to State Bank of India, Mumbai advising that a sum of Rs 2 Crores same day value is expected to
be credited to the latters account by Bank of Baroda, Mumbai.
On receipt of a valid and authenticated IFN 202 message, Bank of Baroda, Mumbai arranges to
transfer funds as requested using traditional means and reports the transaction by sending an IFN
900 message to the Banks Reconciliation System. It also sends an IFN 900 message to its
Mysore Branch advising that the transfer request has been executed. Their Reference No. is
TTP/2468/2001
On receipt of funds, State Bank of India, Mumbai cross checks the amount and particulars with
the information contained in the IFN 210 message to ascertain that the expected amount is
received in full and sends an IFN 910 message to the Banks Reconciliation System. It also sends
an IFN 910 message to State Bank of India, Mysore confirming receipt of funds. State Bank of
India, Mysore responds to the IFN 910 message by sending an IFN 900 message to the Banks
Reconciliation System. SBI Mumbai Reference No. is TTR/3542/2001
It is assumed that the IFSC codes of the various entities are as follows:
Bank of Baroda, Mysore
Bank of Baroda, Mumbai
Bank of Baroda Reconciliation System
State Bank of India, Mysore
State Bank of India, Mumbai
State Bank of India Reconciliation System
: BARB0000MYS
: BARB0000MUM
: BARB0000REC
: SBIN0000876
: SBIN0000001
: SBIN0009999
68
Message Flow:
BOB MYSORE
A/C WITH SBI
MYSORE
BOB MYSORE
F
U
N
D
S
IFN
900
BOB MUMBAI
SBI MYSORE
IFN
210
IFN
900
IFN
202
IFN
910
IFN
910
BANK OF BARODA
RECONCILIATION
SYSTEM
IFN
900
F
U
N
D
S
SBI MUMBAI
SBI
RECONCILIATION
SYSTEM
IFN
910
The extract of header and text block of the IFN 202 Message sent by Bank of Baroda, Mysore to
Bank of Baroda, Mumbai would be as follows:
Header Block:
Sender
Receiver
Message Type
BARB0000MYS Bank of Baroda, Mysore

BARB0000MUM Bank of Baroda, Mumbai
IFN 202
General Financial Institution Transfer
69
Text Block:
Field Description
20
21
Related Reference
32A
53D
Senders Correspondent
58A
Information
TTDISC/234/2001
NONREF
15102001INR2,00,00,000.00
OUR DAD ACCOUNT WITH RBI
MUMBAI
SBIN0000001
The extract of header and text block of the IFN 910 Message sent by Bank of Baroda, Mysore to
Bank of Barodas Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type

BARB0000REC Bank of Baroda Reconciliation System
IFN 910
Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTDISC/234/2001
TTDISC/234/2001
15102001INR2,00,00,000.00
BARB0000MUM
The extract of header and text block of the IFN 210 Message sent by State Bank of India,
Mysore to State Bank of India, Mumbai would be as follows:
Header Block:
Sender
Receiver
Message Type
SBIN0000876
SBIN0000001
IFN 210
Text Block:
Field Description
20
30
Value Date
21
Related Reference
25
32B
52A
Currency & Amount


Notice to Receive
Information
TTRECV/765/2001
15102001
TTRECV/765/2001
MUMBAI
INR2,00,00,000.00
BARB0000MYS
70
The extract of header and text block of the IFN 900 Message sent by Bank of Baroda, Mumbai to
Bank of Baroda Mysore would be as follows:
Header Block:
Sender
Receiver
Message Type

IFN 900
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
Information
TTP/2468/2001
TTDISC/234/2001
MUMBAI
15102001INR2,00,00,000.00
The extract of header and text block of the IFN 900 Message sent by Bank of Baroda, Mumbai to
Bank of Barodas Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type

BARB0000REC Bank of Baroda Reconciliation System
IFN 900
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
TTP/2468/2001
TTDISC/234/2001
15102001INR2,00,00,000.00
BARB0000MYS
Mumbai to State Bank of Indias Reconciliation System would be as follows:
Header Block:
Sender
Receiver
Message Type
SBIN0000001
SBIN0009999
IFN 910
Text Block:
Field Description
20
21
Related Reference

State Bank of India Reconciliation system
Credit Advice
Information
TTR/3542/2001
TTRECV/765/2001
71
25
32A
52A
CONTRA PARTY BRANCH

15102001INR2,00,00,000.00
SBIN0000876
Mumbai to State Bank of India, Mysore would be as follows:
Header Block:
Sender
Receiver
Message Type
SBIN0000001
SBIN0000876
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
56A

Intermediary
Information
TTR/3542/2001
TTRECV/765/2001
OUR DAD ACOUNT WITH RBI
MUMBAI
15102001INR2,00,00,000.00
BARB0000MYS
BARB0000MUM
Mysore to State Bank of Indias Reconciliation System would be as follows:
Field
20
21
25
32A
52A
Description
Related Reference
CONTRA PARTY BRANCH
Information
TTR/3542/2001
TTRECV/765/2001
15102001INR2,00,00,000.00
SBIN0000001
2.4. Advance Notice of Funds Expected to be Received. (IFN 210)

Branches can use IFN 210 messages to advice another branch to give advance notice of funds
expected to be credited by another branch of the same bank or another bank. Examples of such
messages and the message flows have been illustrated in sections 2.1, 2.2 and 2.3 above.
72
3. Collections:
SFMS has several message types for relaying information relating to collection bills. All such
messages belong to category 4 of IFN viz., they all begin with the number 4 such as 400, 410,
430 etc. Interpretation of information provided in all category 4 messages is subject to ICC
Uniform Rules for Collections.
Some of the possible uses of SFMS message types in relaying information relating to collection
bill transactions have been detailed below:
3.1. Acknowledgement of Receipt of Collection Bills. (IFN 410)

IFN 410 messages are used for relaying acknowledgement of receipt of one or more collection
bills.
Example:
M/s Baroda Supari Supplies who bank with Corporation Bank, Baroda
purchases supari
regularly from M/s SK Supari Co. whose bankers are Corporation Bank, Udupi. On 15.10.2001,
M/s SK Supari Co. submits documents relating to their bill No. BSS/654/2001 to their bankers.
The details of the bil1 are as follows.
Drawee
Bill Date
Amount
Terms
Tenor
: M/s Baroda Supari Supplies

: 15.10.2001
: Rs 1,00,000/: Documents against Acceptance
: 60 days from bill date
Corporation Bank, Udupi sends the bill under their Reference No. OBC/791/2001 to their Baroda
branch.
Corporation Bank Receives the bill. Its Reference No. is IBC/680/2001. While acknowledging
the Bill, Corporation Bank, Baroda will have to furnish the following details:
Sender of the Message
: Corporation Bank, Baroda

(IFSC say CORP0000456)
Receiver of the Message
: Corporation Bank, Udupi
(IFSC say CORP0000321)
: IBC/680/2001
Receivers Reference No.
: OBC/791/2001
Bill Amount
: Rs 1,00,000.00
Tenor
: 60 days from Date of Bill of Exchange
Corporation Bank, Baroda sends an IFN 410 message to their Udupi branch acknowledging
receipt of the collection bill and enclosures.
73
Message Flow:
SK SUPARI CO
CORPORATION
BANK
UDUPI
DOCUMENTS
D
O
C
U
M
E
N
T
S
IFN
410
CORPORATION
BANK
BARODA
The Extract of header and text block of the IFN 410 message sent by Corporation Bank, Baroda
to their Udupi branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32K
(1)
(2)
CORP0000456
CORP0000321
IFN 410
Corporation Bank, Baroda

Corporation Bank, Udupi
Acknowledgement
Description
Related Reference (1)
Amount Acknowledged
Information
IBC/680/2001
OBC/791/2001
D060BEINR1,00,000.00 (2)
Corporation Bank, Udupi Reference No.

60 D (Days) from BE (Date of the Bill of Exchange viz., 15.10.2001)
74
3.2. Advice of Acceptance: (IFN 412)

IFN 412 messages are used to relay advices of acceptance.
Example:
Let us assume that in the example quoted in section 3.1 above, the drawees accepted the bill.
While advising their Udipi branch, Corporation Bank, Baroda will have to furnish the following
details:
Bill Amount
Due Date (1)

: IBC/680/2001
: OBC/791/2001
: Rs 1,00,000.00
: 15.12.2001
(1) As the due date has been crystallized, tenor need not be indicated
Corporation Bank, Baroda would then send an IFN 412 message to Corporation Bank, Udupi
advising them of acceptance.
Message Flow:
SK SUPARI CO
DOCUMENTS
CORPORATION
BANK
UDUPI
D
O
C
U
M
E
N
T
S
BARODA
SUPARI
SUPPLIES
PRESENTATION
ACCEPTANCE
IFN
412
CORPORATION
BANK
BARODA
75
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32A
CORP0000456
CORP0000321
IFN 412

Advice of Acceptance
Description
Related Reference
Maturity, Currency, Amount
Accepted
Information
IBC/680/2001
OBC/791/2001
15122001INR1,00,000.00
3.3. Tracer (Fate Enquiry): (IFN 420)

IFN 420 messages are used to enquire fate of bills sent for collection.
Example:
Let us assume that in the example quoted in section 3.1 above, Corporation Bank, Udupi, did not
receive advice of acceptance within a reasonable period. They would then send an IFN 420
message to Corporation Bank, Baroda requesting them to advise fate. The information to be
provided in the message will be as follows:
Bill Amount
Tenor

: OBC/791/2001
: IBC/680/2001
: Rs 1,00,000.00
76
Message Flow:
SK SUPARI CO
CORPORATION
BANK
UDUPI
DOCUMENTS
D
O
C
U
M
E
N
T
S
IFN
420
CORPORATION
BANK
BARODA
The Extract of header and text block of the IFN 420 message sent by Corporation Bank, Udupi to
their Baroda branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32K
CORP0000321
CORP0000456
IFN 420

Tracer
Description
Related Reference
Amount Traced
Information
OBC/791/2001
IBC/680/2001
D060BEINR1,00,000.00
3.4. Advice of Fate and Request for Instructions: (IFN 422)

IFN 422 messages are used to relay advices of fate and request for instructions. Though this
message is normally sent in response to a tracer, it could also be sent as an advice of nonpayment/non-acceptance without waiting for a tracer.
77
Example:
Let us assume that in the example quoted in section 3.1 above, the drawees refused to accept the
bill demanding that the tenor of the bill be changed to 90 days instead of 60 days from the date of
the bill of exchange. Corporation Bank, Baroda would then send an IFN 422 message to
Corporation Bank, Udupi advising them of non-acceptance, reasons thereof, seeking fresh
instructions.
While advising their Udipi branch, Corporation Bank, Baroda will have to furnish the following
details:
Bill Amount
Tenor
Reason for non-acceptance

: IBC/680/2001
: OBC/791/2001
: Rs 1,00,000.00
: Drawees want the tenor of the bill be changed to 90 days
instead of 60 days from the date of the bill of exchange
Message Flow:
SK SUPARI CO
CORPORATION
BANK
UDUPI
DOCUMENTS
D
O
C
U
M
E
N
T
S
BARODA
SUPARI
SUPPLIES
PRESENTATION
NON-ACCEPTANCE
IFN
420
IFN
422
CORPORATION
BANK
BARODA
78
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32K
75
CORP0000456
CORP0000321
IFN 422

Advice of Fate & Request for Instructions
Description
Related Reference
Amount of Collection
Queries
Information
IBC/680/2001
OBC/791/2001
D060BEINR1,00,000.00
DRAWEES WANT THE TENOR
CHANGED TO 90 INSTEAD OF
60 DAYS FROM DATE OF BILL
OF EXCHANGE. PL.ADVISE
REVISED INSTRUCTONS.
3.5. Amendment of Instructions: (IFN 430)

IFN 430 messages are used to relay amendments to the instructions of a collection item.
Example:
Let us assume that in the example quoted in section 3.4 above, the drawers agreed to change
tenor of the bill to 90 days instead of 60 days from the date of the bill of exchange. Corporation
Bank, Udupi would then send an IFN 430 message to Corporation Bank, Baroda advising them
of amended instructions. The information to be provided in the message will be as follows:
Bill Amount
Original Tenor
Amended Tenor

: OBC/791/2001
: IBC/680/2001
: Rs 1,00,000.00
79
Message Flow:
SK SUPARI CO
CORPORATION
BANK
UDUPI
DOCUMENTS
D
O
C
U
M
E
N
T
S
BARODA
SUPARI
SUPPLIES
PRESENTATION
NON-ACCEPTANCE
IFN
422
IFN
430
CORPORATION
BANK
BARODA
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32K
33K
CORP0000321
CORP0000456
IFN 430

Amendment of Instructions
Description
Related Reference
Existing Maturity Date.
Currency amount
Amended Maturity Date.
Currency amount
Information
OBC/791/2001
IBC/680/2001
D060BEINR1,00,000.00
D090BEINR1,00,000.00
3.6. Advice of Payment: (IFN 400)

IFN 400 messages are used to relay advice of payment of a collection item.
Let us assume that the bill in example quoted in section 3.5 above is retired by the drawees on
14.01.2002. Corporation Bank, Baroda would then send an IFN 400 message to Corporation
Bank, Udupi advising them that the bill has been paid and that they have been credited through
the Inter Branch Account for Rs 99,500.00 being proceeds of collection after deducting their
commission of Rs 500.00. They would also send an IFN 910 message to the Banks
Reconciliation System for Rs 99,500.00 and a debit advice to M/s Baroda Supari Suppies.
80
Corporation Bank, Baroda will have to furnish the following details:

Bill Amount
Tenor
Date of Payment
Charges Deducted
Proceeds Remitted

: IBC/680/2001
: OBC/791/2001
: Rs 1,00,000.00
: 14.1.2002
: Rs 500.00
: Rs 99,500.00
On receipt of a valid IFN 400 message, Corporation Bank, Udupi would credit the proceeds to
M/s SK Supari Co.s account and send them a credit advice and send an IFN 900 message to the
Banks Reconciliation System for Rs 99,500.00.
Message Flow:
S.K. SUPARI
COS
ACCOUNT
FUNDS
DOCUMENTS
S.K. SUPARI CO
CREDIT
ADVICE
CORPORATION
BANK
UDUPI
D
O
C
U
M
E
N
T
S
IFN
400
IFN
900
CORPORATION BANK
RECONCILIATION
SYSTEM
DOCUMENTS
BARODA
SUPARI
SUPPLIES
DEBIT
ADVICE
BARODA
SUPARI
SUPPLIES
ACCOUNT
CORPORATION
BANK
BARODA
IFN
910
FUNDS
81
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32K
33A
71B
CORP0000456
CORP0000321
IFN 400

Advice of Payment
Description
Related Reference
Amount Collected
Proceeds Remitted
Details of Charges
Information
IBC/680/2001
OBC/791/2001
D090BE INR1,00,000.00
14012002INR99,500.00
/COMM/INR500.00
The extract of header and text block of the IFN 910 Message sent by Corporation Bank, Baroda
Header Block:
Sender
Receiver
Message Type
CORP0000456
CORP0000999
IFN 910

Corporation Bank Reconciliation System
Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
IBC/680/2001
NONREF
14012002INR99,500.00
CORP0000321
The extract of header and text block of the IFN 900 Message sent by Corporation Bank, Udupi
Header Block:
Sender
Receiver
Message Type
CORP0000321
CORP0000999
IFN 900

Corporation Bank Reconciliation System
Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
OBC/791/2001
IBC/680/2001
14012002INR99,500.00
CORP0000456
82
4. Letters of Credit:
All messages relating to Letters of Credit and Guarantee transactions are grouped under category
7 of IFN. Interpretation of information provided in all category 7 messages relating to LCs is
subject to ICC Uniform Customs and Practice for Documentary Credits (Latest Revision).
Some of the possible uses of SFMS message types in relaying information relating to LC
transactions have been discussed below:
4.1. Short LCs (Pre-Advices). (IFN 705)

IFN 705 messages are used for relaying Short LCs.
Example:
M/s Super Auto Corporation, 123, Manish Auto Market, 16, Grant Road, Mumbai 400 007 who
bank with Syndicate Bank, Mumbai (IFSC say SYND0000011) purchases Automobile spare
parts from M/s Uttam Singh Agarwal & Sons, USA House, 206/B, Kashmir Gate, New Delhi.
110024, whose bankers are Syndicate Bank, New Delhi (IFSC say SYND0000022). On
15.10.2001, M/s Super Auto Corporation, request their bankers to issue a short cable transferable
LC favoring M/s Uttam Singh Agarwal & Sons. The details of the LC are as follows.
Date and Place of Expiry
Latest Date for Shipment
Amount
Descrption of Goods
: 31.12.2001, New Delhi

: 25.12.2001
: Rs 2,00,000/: 100 Nos. API Clutch Discs for Premier Padmini
100 Nos. API Clutch Discs for Ambassador Nova
100 Nos. API Clutch Discs for Mahindra MM540
200 Nos. KAP Rear Axle Shafts for Premier Padmini
200 Nos. KAP Rear Axle Shafts for Ambassador Nova
Syndicate Bank, Mumbai issues and the LC (No. ILC/3254/2001) and advises the short LC
through its New Delhi branch.
83
Message Flow:
SUPER AUTO
CORPORATION
LC REQUEST
SYNDICATE
BANK
MUMBAI
IFN
705
UTTAM SINGH
AGARWAL &
SONS
LC ADVICE
SYNDICATE
BANK
NEW DELHI
The Extract of header and text block of the IFN 705 message sent by Syndicate Bank, Mumbai to
their New Delhi branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000011
SYND0000022
IFN 705
Syndicate Bank, Mumbai

Syndicate Bank, New Delhi
Pre-Advice
Text Block:
Field
40A
20
31D
50
Description
Form of Documentary Credit
Documentary Credit No.
Applicant
59
Beneficiary
32B
44C
Currency and Amount

Latest Date of Shipment
Information
IRREVOCABLE TRANFERABLE
ILC/3254/2001
31122001NEW DELHI
SUPER AUTO CORPORATION
123, MANISH AUTO MARKET,
16, GRANT ROAD,
MUMBAI 400 007
UTTAM SINGH AGARAWAL &
SONS, USA HOUSE,
206/B,KASHMIR GATE
NEW DELHI 110 024
INR2,00,000.00
25122001
84
45A
Description of Goods
100 NOS. API CLUTCH DISCS

FOR PREMIER PADMINI
FOR AMBASSADOR NOVA
FOR MAHINDRA MM540
200 NOS. REAR AXLE SHAFTS
FOR PREMIER PADMINI
FOR AMBASSADOR NOVA
4.2. LC Issue: (IFN 700 & 701)

IFN 700 and IFN 701 messages are used to relay LC messages. IFN 701 messages are used for
continuation of an LC message when the entire LC information cannot be conveyed in a single
IFN 700 message.
Example:
The beneficiaries of the LC in the example quoted in section 4.1 above, M/s Uttam Singh
Agarwal & Sons, request the openers to arrange for relaying a detailed LC message.
The other details of the LC are as follows:
Draft Particulars
: Sight Drafts (in duplicate)for 100% FOB value to be drawn on

the Opening Bank
Part shipments
: Not allowed
Transhipment
: Not allowed
: 100 Nos. API Clutch Discs for Premier Padmini
at Rs 325/- per Pc.
100 Nos. API Clutch Discs for Ambassador Nova
at Rs 350/- per Pc
100 Nos. API Clutch Discs for Mahindra MM540
at Rs 425/- per Pc
200 Nos. KAP Rear Axle Shafts for Premier Padmini
at Rs 200/- per Pc
200 Nos. KAP Rear Axle Shafts for Ambassador Nova
at Rs 250/- per Pc
Goods to be dispatched from : New Delhi
Goods to be dispatched to
: Mumbai
Document Required
: Invoices 3 copies
Lorry Receipt of any IBA Approved Road Transport Operator
Packing List 3 Copies.
85
Additional Conditions
: Immediately after dispatch, a copy of the Lorry Receipt to be

faxed to the openers.
Carbon copies of invoices acceptable but not Xerox copies.
The openers request their bankers to advise full LC particulars to the beneficiaries. On
25.10.2001, Syndicate Bank, Mumbai sends an IFN 700 message and uses an IFN 701 message
to relay Desrciption of Goods.
Message Flow:
SUPER AUTO
CORPORATION
LC REQUEST
SYNDICATE
BANK
MUMBAI
IFN
700
UTTAM SINGH
AGARWAL &
SONS
LC ADVICE
IFN
701
SYNDICATE
BANK
NEW DELHI
The Extract of header and text block of the IFN 700 and IFN 701 messages sent by Syndicate
Bank, Mumbai to their New Delhi branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
27
40A
20
23
31C
31D
50
SYND0000011
SYND0000022
IFN 700

Advice of Documentary Credit
Description
Sequence of Total
Reference to Pre-Advice
Date of Issue
Applicant
Information
1/2
ILC/3254/2001
ILC/3254/2001
15102001
31122001NEW DELHI
16, GRANT ROAD,
MUMBAI 400 007
86
59
Beneficiary
32B
41D
Currency and Amount

Available with .. by ..
42C
Drafts at ..
42A
43P
43T
44A
44B
44C
46A
Drawee
Part shipments
Transhipment
DISPATCH FROM ..
For Transporation to ..
Documents Required
47A
71B
Charges
49
Confirmation Instructions
Header Block:
Sender
Receiver
Message Type
SYND0000011
SYND0000022
IFN 701

SONS, USA HOUSE,
206/B,KASHMIR GATE
NEW DELHI 110 024
INR2,00,000.00
ANYBANK
NEGOTIATION
SIGHT (IN DUPLICATE) FOR 100
PCT FOB VALUE
SYND0000011
PROHIBITED
PROHIBITED
NEW DELHI
MUMBAI
25122001
INVOICES 3 COPIES
LORRY RECEIPT OF ANY IBA
APPROVED ROAD TRANSPORT
OPERATOR - ORIGINAL
PACKING LIST 3 COPIES
1. IMMEDIATELY AFTER
DISPATCH COPY OF THE
LORRY RECEIPT TO BE FAXED
TO THE OPENERS.
2.
CARBON
COPIES
OF
INVOICES ACCEPTABLE BUT
XEROX
COPIES
NOT
ACCEPTABLE
ALL
CHARGES
FOR
BENEFIARIES ACCOUNT
CONFIRM

87
Text Block:
Field
27
20
45B
Description
Sequence of Total
Information
2/2
ILC/3254/2001
FOR PREMIER PADMINI AT RS
325/- PER PC
FOR AMBASSADOR NOVA AT
RS 350/- PER PC
FOR MAHINDRA MM540 AT RS
425/- PER PC
200/- PER PC
RS 250/- PER PC
4.3. Acknowledgement of LC Message: (IFN 730)

IFN 730 message is used to Acknowledge LC messages and other messages related to LCs.
Example:
The receivers of the LC message in the example quoted in section 4.1 above, Syndicate Bank
New Delhi acknowledge the LC message by sending an IFN 730 message to Syndicate Bank,
Mumbai.
Message Flow:
SUPER AUTO
CORPORATION
SYNDICATE
BANK
MUMBAI
LC REQUEST
IFN
700
UTTAM SINGH
AGARWAL &
SONS
LC ADVICE
IFN
701
IFN
730
SYNDICATE
BANK
NEW DELHI
88
The Extract of header and text block of the IFN 730 message sent by Syndicate Bank, New Delhi
(Quoting their Inward LC Reference No. LCADV/1025/2001) to their Mumbai branch would
appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
30
SYND0000022
SYND0000011
IFN 730

Acknowledgement
Description
SendersReference
Receivers Reference
Date of the Message being
Acknowledged
Information
LCADV/1025/2001
ILC/3254/2001
25102001
4.4. Advice of Another Branchs LC: (IFN 710 & 711)

IFN 710 and IFN 711 messages are used to advice LC messages of another branch. IFN 711
messages are used for continuation of an LC message when the entire LC information cannot be
conveyed in a single IFN 710 message.
Example:
The beneficiaries of the LC in the example quoted in section 4.1 above, M/s Uttam Singh
Agarwal & Sons, have recently transferred their account to Kashmir Gate Branch of Syndicate
Bank. They request the openers to arrange advising the LC through their bankers. On
29.10.2001, Syndicate Bank, Mumbai send an IFN 799 Free format message to their New Delhi
Branch to advise the LC through their Kashmir Gate Branch.
The Extract of header and text block of the IFN 799 message sent by Syndicate Bank, Mumbai to
their New Delhi branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000011
SYND0000022
IFN 700

89
Text Block:
Field
20
79
Description
Narrative
Information
ILC/3254/2001
THE BENEFICIARIES OF OUR
ABOVE
REFERRED
LC
RELAYED
TO
YOU
ON
15.10.2001 HAVE REQUESTED
THAT THE LC BE ADVISED
THOUGH OUR KASHMIR GATE
BRANCH. PLEASE ARRANGE
ACCORDINGLY.
On 30.10.2001, Syndicate Bank, New Delhi sends an IFN 710 and IFN 711 message to relay the
LC (Their Reference LCADV/1025/2001) to Syndicate Bank, Kashmir Gate Branch (IFSC Say
SYND.
Message Flow:
SUPER AUTO
CORPORATION
SYNDICATE
BANK
MUMBAI
LC REQUEST
IFN
700
IFN
701
IFN
730
IFN
799
SYNDICATE
BANK
NEW DELHI
IFN
710
UTTAM SINGH
AGARWAL &
SONS
LC ADVICE
IFN
711
SYNDICATE
BANK
KASHMIR GATE
90
Bank, New Delhi to their Kashmir Gate branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000022
SYND0000420
IFN 710

Syndicate Bank, Kashmir Gate
Advice of Third Banks Documentary Credit
Text Block:
Field
27
40A
21
20
23
31C
31D
52A
50
Description
Sequence of Total
Senders Reference
Reference to Pre-Advice
Date of Issue
Issuing Bank
Applicant
59
Beneficiary
32B
41D
Currency and Amount

42C
Drafts at ..
42A
43P
43T
44A
44B
44C
46A
Drawee
Part shipments
Transhipment
DISPATCH FROM ..
Documents Required
47A
Information
1/2
LCADV/1025/2001
ILC/3254/2001
ILC/3254/2001
15102001
31122001NEW DELHI
SYND0000011
16, GRANT ROAD,
MUMBAI 400 007
SONS, USA HOUSE,
206/B, KASHMIR GATE
NEW DELHI 110 024
INR2,00,000.00
ANYBANK
NEGOTIATION
PCT FOB VALUE
SYND0000011
PROHIBITED
PROHIBITED
NEW DELHI
MUMBAI
25122001
INVOICES 3 COPIES
OPERATOR - ORIGINAL
91
71B
Charges
49
TO THE OPENERS.
2.
CARBON
COPIES
OF
XEROX
COPIES
NOT
ACCEPTABLE
ALL
CHARGES
FOR
BENEFIARIES ACCOUNT
CONFIRM
N.B: The message is very similar to an IFN 700 message. The only 2 additional fields in
the IFN 710 message are Fields are 21 and 52A.
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
27
20
45B
SYND0000022
SYND0000420
IFN 711

Advice of Third Banks Documentary Credit
Description
Sequence of Total
Information
2/2
ILC/3254/2001
325/- PER PC
RS 350/- PER PC
425/- PER PC
200/- PER PC
RS 250/- PER PC
4.5. Transfer of LC: (IFN 720 & 721)

IFN 720 and IFN 721 messages are used to advice LC particulars to a beneficiary in whose name
the LC has been transferred. IFN 721 messages are used for continuation of an LC message
when the entire LC information cannot be conveyed in a single IFN 720 message.
92
Example:
On 5.11.2001, the beneficiaries of the LC in the example quoted in section 4.1 above, M/s Uttam
Singh Agarwal & Sons, request the advising bank to transfer the LC in favour of M/s Satnam
Singh Arora & Sons, 25/12, G.T.Road, Goraya who bank with Syndicate Bank, Goraya(IFSC
say SYND0000579).
On the same day, Syndicate Bank, Kashmir Gate sends an IFN 720 and IFN 721 message to their
Goraya Branch, transferring the LC in favour od M/s Satnam Singh Arora & Sons.
Message Flow:
SUPER AUTO
CORPORATION
SYNDICATE
BANK
MUMBAI
LC REQUEST
IFN
700
IFN
701
IFN
730
IFN
799
SYNDICATE
BANK
NEW DELHI
IFN
710
UTTAM SINGH
AGARWAL &
SONS
LC ADVICE
TRANSFER REQUEST
SYNDICATE
BANK
KASHMIR GATE
IFN
720
SATNAM
SINGH ARORA
& SONS
LC ADVICE
IFN
711
IFN
721
SYNDICATE
BANK
GORAYA
93
Bank, Kashmir Gate branch (Their Ref. LCADV/679/2001) to their Goraya branch would appear
as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000420
SYND0000579
IFN 720

Syndicate Bank, Goraya
Transfer of Documentary Credit
Text Block:
Field
27
40A
21
20
31C
31D
52A
50
Description
Sequence of Total
Senders Reference
Date of Issue
Issuing Bank
First Beneficiary
59
Second Beneficiary
32B
41D
Currency and Amount

42C
Drafts at ..
42A
43P
43T
44A
44B
44C
46A
Drawee
Part shipments
Transhipment
DISPATCH FROM ..
Documents Required
47A
Information
1/2
LCADV/679/2001
ILC/3254/2001
15102001
31122001NEW DELHI
SYND0000011
SONS, USA HOUSE,
206/B,KASHMIR GATE
NEW DELHI 110 024
SATNAM SINGH ARORA &
SONS, 25/12, G.T.ROAD,
GORAYA.
INR2,00,000.00
ANYBANK
NEGOTIATION
PCT FOB VALUE
SYND0000011
PROHIBITED
PROHIBITED
NEW DELHI
MUMBAI
25122001
INVOICES 3 COPIES
OPERATOR - ORIGINAL
TO THE OPENERS.
2.
CARBON
COPIES
OF
94
71B
Charges
49

XEROX
COPIES
NOT
ACCEPTABLE
ALL
CHARGES
FOR
BENEFIARIES ACCOUNT
CONFIRM
N.B: The message is very similar to an IFN 700 message. The only 2 additional fields in
the IFN 720 message are Fields are 21 and 52A. And in the Field 50, the name of the
original beneficiary is shown instead of the openers and in Field 59, the name of the
transferee is shown instead of the transferor. If the LC were to be transferred again, Field
50 would contain the present transferee (viz., Satnam Singh Arora & Sons) will be shown
and the new transferees name will appear in Field 59.
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
27
20
45B
SYND0000022
SYND0000420
IFN 721

Transfer of Documentary Credit
Description
Sequence of Total
Information
2/2
ILC/3254/2001
325/- PER PC
RS 350/- PER PC
425/- PER PC
200/- PER PC
RS 250/- PER PC
95
4.6. Advice of LC Amendment: (IFN 707)

IFN 707 messages are used to advice amendments to LC messages.
Example:
On 15.11.2001, the beneficiaries of the LC in the example quoted in section 4.1 above, M/s
Uttam Singh Agarwal & Sons, request the openers to amend the LC and extend the Last date for
shipment to 31.12.2001 and date of expiry of LC to 7.1.2002 and advise it to the second
beneficiaries viz., Satnam Singh Arora & Sons through Syndicate Bank, Goraya. On openers
request, Syndicate Bank, Mumbai amends the LC accordingly and sends an IFN 707 message to
their Goraya Branch.
Message Flow:
SUPER AUTO
CORPORATION
AMENDMENT REQUEST
SYNDICATE
BANK
MUMBAI
IFN
707
SATNAM
SINGH ARORA
& SONS
AMENDMENT ADVICE
SYNDICATE
BANK
GORAYA
The Extract of header and text block of the IFN 707 sent by Syndicate Bank, Mumbai (Their
Ref. LCAMD/786/2001) to their Goraya branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000011
SYND0000579
IFN 707

Amendment of a Documentary Credit
96
Text Block:
Field
20
21
59
Description
Senders Reference
Receivers Reference
Second Beneficiary
31E
44C
New Date of Expiry

(1)
Information
LCAMD/786/2001
NONREF
(1)
SATNAM SINGH ARORA
SONS, 25/12, G.T.ROAD,
GORAYA.
31122001
07012002
&
As the IFN 720 and IFN 721 messages would have been sent by Syndicate Bank,
Kashmir Gate to Syndicate Bank, Goraya, the latter would not have sent an IFN
730 message to Syndicate Bank, Mumbai. As such, Syndicate Bank, Mumbai
would have to use NONREF in Field 21.
4.7. Advice of Payment/Acceptance/Negotiation: (IFN 754)

IFN 754 message is used to relay advice of Payment/Acceptance/Negotiation of bills covered by
an LC. The message is usually sent by the paying/accepting/negotiating bank to the issuing bank
Whether an IFN 754 message conveys advice of Payment, Acceptance or Negotiation depends
on the nature of the LC.
If the LC is available by Payment, Deferred Payment or Mixed Payment, then IFN 754
message conveys advice of payment.
If the LC is available by Acceptance, then IFN 754 message conveys advice of acceptance.
If the LC is available by Negotiation, then IFN 754 message conveys advice of negotiation.
Example:
On 5.01.2002, the beneficiaries (Transferees) of the LC in the example quoted in section 4.5
above, M/s Satnam Singh Arora & Sons, 25/12, G.T.Road, Goraya submit a bill (their Ref.
OB/2468) for Rs 2,00,000/- under the LC for negotiation to Syndicate Bank, Goraya.
Syndicate Bank, Goraya negotiate the bill and send an IFN 754 advice of negotiation message to
their Mumbai branch.
97
Message Flow:
SYNDICATE
BANK
MUMBAI
SUPER AUTO
CORPORATION
IFN
754
SATNAM
SINGH ARORA
& SONS
DOCUMENTS
FUNDS
SYNDICATE
BANK
GORAYA
The Extract of header and text block of the IFN 754 sent by Syndicate Bank, Goraya (Their Ref.
LCBP/135/2001) to their Mumbai branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32A
SYND0000579
SYND0000011
IFN 754

Advice of Negotiation
Description
Senders Reference
Receivers Reference
Principal Amount Negotiated
Information
LCBP/135/2001
ILC/3254/2001
05012002INR2,00,000.00
4.8. Advice of Payment: (IFN 756)

IFN 756 message is used to relay advice of Payment of a bill drawn under and LC. IFN 756
message is often confused with IFN 754 as both messages can be used as advices of payment. It
is therefore important to note that IFN 754 is sent to the issuing bank by a bank that pays the
beneficiary of an LC available by payment whereas IFN 756 messages are sent by the issuing
bank to a bank, which has negotiated/accepted/paid a bill under an LC.
98
Example:
In the example quoted in section 4.7 above, Syndicate Bank, Goraya forwards the documents
pertaining to the bill negotiated by it to its Mumbai branch who having examined and found the
bill to be in order, take up the bill on 11.01.2002 and send an IFN 756 message advising them of
payment of the bill. It also sends an IFN 910 message to the Banks Reconciliation System and a
notice to the applicants viz., M/s Super Auto Corporation, to retire the bill.
On receipt of a valid and authenticated IFN 756, Syndicate Bank, Goraya passes necessary
adjustment entries in its LC Bills Account and sends an IFN 900 message to the Banks
Reconciliation System.
Message Flow:
SUPER AUTO
CORPORATION
SYNDICATE
BANK
MUMBAI
D
O
C
U
M
E
N
T
S
SATNAM
SINGH ARORA
& SONS
DOCUMENTS
FUNDS
IFN
756
IFN
910
CORPORATION BANK
RECONCILIATION
SYSTEM
SYNDICATE
BANK
GORAYA
IFN
900
The Extract of header and text block of the IFN 756 sent by Syndicate Bank, Mumbai (Their
Reference LCBR 9753/2001) to their Goraya branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32B
33A
SYND0000011
SYND0000579
IFN 756

Advice of Payment
Description
Senders Reference
Receivers Reference
Total Amount Claimed
Amount Paid
Information
LCBR 9753/2001
LCBP/135/2001
INR2,00,000.00
11012002 INR2,00,000.00
99
The extract of header and text block of the IFN 910 Message sent by Syndicate Bank, Mumbai to
the Reconciliation System (IFSC say SYND0009999) would be as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000011
SYND0009999
IFN 910

Syndicate Bank, Reconciliation System
Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
LCBR 9753/2001
LCBP/135/2001
11012002 INR2,00,000.00
SYND0000579
The extract of header and text block of the IFN 900 Message sent by Syndicate Bank, Goraya
Header Block:
Sender
Receiver
Message Type
SYND0000579
SYND0009999
IFN 900

DebitAdvice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
LCBP/135/2001
LCBR 9753/2001
11012002 INR2,00,000.00
SYND0000011
4.9. Advice of Discrepancy: (IFN 750)

IFN 750 messages are used to advice discrepancies in documents submitted for negotiation/
payment/acceptance under an LC. The message is sent by the negotiating/paying/accepting bank
to the issuing bank requesting for authorization to negotiate/pay/accept.
100
Example:
On 5.01.2002, the beneficiaries (Transferees) of the LC in the example quoted in section 7.5
above, M/s Satnam Singh Arora & Sons, 25/12, G.T.Road, Goraya submit a bill (their Ref.
OB/2468) for Rs 2,00,000/- under the LC for negotiation to Syndicate Bank, Goraya.
On scrutinizing the documents, Syndicate Bank, Goraya find that the goods were dispatched on
2.1.2002, viz., after the latest date of shipment, which is, 31.12.2001 after the amendment
mentioned in section vi. above. They therefore send an IFN 750 advice of discrepancy message
to their Mumbai branch on 5.01.2002, requesting permission to negotiate.
Message Flow:
SYNDICATE
BANK
MUMBAI
SUPER AUTO
CORPORATION
IFN
750
SATNAM
SINGH ARORA
& SONS
DOCUMENTS
FUNDS
SYNDICATE
BANK
GORAYA
The Extract of header and text block of the IFN 750 sent by Syndicate Bank, Goraya to their
Mumbai branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32B
77J
SYND0000579
SYND0000011
IFN 750

Advice of Discrepancy
Description
Senders Reference
Receivers Reference
Discrepancies
Information
LCBP/135/2001
ILC/3254/2001
INR2,00,000.00
SHIPMENT EFFECTED ON
2.1.2002
101
4.10. Authorisation to Pay, Accept or Negotiate: (IFN 752)

IFN 752 message is used to convey authorisation to negotiate/pay/accept documents with
discrepancies submitted under an LC. It is normally sent by the issuing bank in response to an
IFN 750 advice of discrepancy message.
Example:
If the discrepancies mentioned in the IFN 750 message discussed in the example quoted in
section 4.9 above, are acceptable to the applicants of the LC, Syndicate Bank, Mumbai would
send an IFN 752 message to their Goraya branch authorising them to negotiate the discrepant
documents.
Message Flow:
SUPER AUTO
CORPORATION
ADVICE OF DISCREPANCY
INSTRUCTION
SYNDICATE
BANK
MUMBAI
IFN
750
SATNAM
SINGH ARORA
& SONS
DOCUMENTS
FUNDS
IFN
752
SYNDICATE
BANK
GORAYA
The Extract of header and text block of the IFN 752 sent by Syndicate Bank, Mumbai to their
Goraya branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
23
30
SYND0000011
SYND0000579
IFN 754

Description
LC Number
Presenting Banks Reference
Further Identification
Date of advice of
Discrepancy
Information
ILC/3254/2001
LCBP/135/2001
NEGOTIATE
05012002
102
4.11. Advice of Discharge: (IFN 732)

IFN 732 messages are normally sent by the issuing bank to advise the negotiating bank that the
documents negotiated with discrepant documents have been taken up. In such cases, the
negotiating bank would have proceeded with negotiation of the bill with discrepant documents
without referring discrepancies to the issuing bank through an IFN 750 message. Instead, the
discrepancy would be mentioned in the IFN 754 advice of Negotiation and the issuing bank
would be requested to take up the documents.
Example:
Let us assume that in the example quoted in section 4.9 above, Syndicate Bank, Goraya branch
proceeds to negotiate the bill on 5.1.2002 in spite of the discrepancies in the supporting
documents and sends an IFN 754 advice of negotiation on the same day, requesting their
Mumbai branch to take up the documents and forwards the documents to Syndicate Bank,
Mumbai. The discrepancies are acceptable to the applicants of the LC. Syndicate Bank, Mumbai
ON 11.01.2002, send an IFN 732 message to their Goraya branch advising them that the
documents have been taken up in spite of the discrepancies. They also send an IFN 910 message
to the Banks Reconciliation System.
On receipt of a valid and authenticated IFN 732 message, Syndicate Bank, Goraya passes
necessary adjustment entries in its LC Bills Account and sends an IFN 900 message to the
Message Flow:
SUPER AUTO
CORPORATION
SYNDICATE
BANK
MUMBAI
ACCEPTANCE
IFN
754
SATNAM
SINGH ARORA
& SONS
DOCUMENTS
FUNDS
D
O
C
U
M
E
N
T
S
SYNDICATE
BANK
GORAYA
IFN
910
IFN
732
CORPORATION BANK
RECONCILIATION
SYSTEM
IFN
900
103
The Extract of header and text block of the IFN 754 sent by Syndicate Bank, Goraya to their
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32A
72
SYND0000579
SYND0000011
IFN 754

Description
Senders Reference
Receivers Reference
Sender to Receiver
Information
Information
LCBP/135/2001
ILC/3254/2001
05012002INR2,00,000.00
WE HAVE NEGOTIATED IN
SPITE OF THE FOLLOWING
DISCREPANCY: LAST DATE
FOR SHIPMENT EXCEEDED BY
2 DAYS. KINDLY ADVISE
DISCHARGE ASAP.
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
30
32B
72
SYND0000011
SYND0000579
IFN 732

Advice of Discharge
Description
LC Number
Date of Advice of Payment/
Acceptance/Negotiation
Amount of Utilisation
Sender to Receiver
Information
Information
ILC/3254/2001
LCBP/135/2001
05012002
INR2,00,000.00
WE HAVE TODAY CREDITED
YOU THRU INTER BRANCH
ACCOUNT FOR RS 2,00,000/-
104
The extract of header and text block of the IFN 910 Message sent by Syndicate Bank, Mumbai to
the Reconciliation System (IFSC say SYND0009999) would be as follows:
Header Block:
Sender
Receiver
Message Type
SYND0000011
SYND0009999
IFN 910

Credit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
LCBR 9753/2001
LCBP/135/2001
11012002 INR2,00,000.00
SYND0000579
The extract of header and text block of the IFN 900 Message sent by Syndicate Bank, Goraya
Header Block:
Sender
Receiver
Message Type
SYND0000579
SYND0009999
IFN 900

Debit Advice
Text Block:
Field Description
20
21
Related Reference
25
32A
52A
CONTRA PARTY BRANCH
Information
LCBP/135/2001
LCBR 9753/2001
11012002 INR2,00,000.00
SYND0000011
105
4.12. Advice of Refusal: (IFN 734)

IFN 734 messages are normally sent by the issuing bank to advise the paying/negotiating bank
that the documents paid/negotiated with discrepancies in the documents forwarded are not
acceptable and that the documents are either being held at the negotiating banks risk or is being
returned to them. In such cases, the paying/negotiating bank would have proceeded with
payment/negotiation of the bill with discrepant documents without referring discrepancies to the
issuing bank through an IFN 750 message. Instead, the discrepancy would be mentioned in the
IFN 754 advice of Payment/Negotiation/Acceptance and the issuing bank would be requested to
take up the documents.
Example:
Let us assume that in the example quoted in section 4.9 above, Syndicate Bank, Goraya branch
proceeds to negotiate the bill on 5.1.2002 in spite of the discrepancies in the supporting
documents and sends an IFN 754 advice of negotiation on the same day, requesting their
Mumbai branch to take up the documents and forwards the documents to Syndicate Bank,
Mumbai. The discrepancies are not acceptable to the applicants of the LC. Syndicate Bank,
Mumbai on 11.01.2002, sends an IFN 734 message to their Goraya branch advising them that the
discrepancies are not acceptable and that documents are being held at their risk and disposal.
Message Flow:
SUPER AUTO
CORPORATION
SYNDICATE
BANK
MUMBAI
REFUSAL
IFN
754
SATNAM
SINGH ARORA
& SONS
DOCUMENTS
FUNDS
D
O
C
U
M
E
N
T
S
SYNDICATE
BANK
GORAYA
IFN
910
IFN
734
CORPORATION BANK
RECONCILIATION
SYSTEM
IFN
900
106
The Extract of header and text block of the IFN 754 sent by Syndicate Bank, Goraya (to their
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32A
72
SYND0000579
SYND0000011
IFN 754

Description
Senders Reference
Receivers Reference
Sender to Receiver
Information
Information
LCBP/135/2001
ILC/3254/2001
05012002INR2,00,000.00
WE HAVE NEGOTIATED IN
SPITE OF THE FOLLOWING
DISCREPANCY: LAST DATE
FOR SHIPMENT EXCEEDED BY
2 DAYS. KINDLY DISCHARGE
US ASAP.
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
32A
SYND0000011
SYND0000579
IFN 734

Advice of Refusal
77J
Description
LC Number
Date and Amount of
Utilisation
Discrepancies
77B
Disposal of Documents
Information
LCBR 9753/2001
LCBP/135/2001
05012002 INR2,00,000.00
LAST DATE FOR SHIPMENT
EXCEEDED BY 2 DAYS.
DOCUMENTS HELD AT YOUR
RISK. ADVISE DISPOSAL ASAP
107
5. Guarantees:
SFMS provides message types for Issuing or Requesting for issuing of a guarantee,
acknowledgement of a guarantee message, amendments to a guarantee and advice of reduction or
release.
5.1. Issue of Guarantee:

IFN 760 messages are used to relay guarantees.
Example:
On 10.11.2001, M/s National Power Systems request State Bank of Mysore, Hosur (IFSC Say
SBMY0000765) to issue a Bank Guarantee for Rs 1,00,000/- favouring State Bank of Mysore,
Nagpur Branch (IFSC Say SBMY0000345).
The details of the guarantee are as follows:
M/s National Power Systems have agreed to supply and install 2 X 25.0 KVA UPS Systems with
Battery at State Bank of Mysore, Nagpur branch Premises in terms of their Order No. SBM/0102/1305 Dated 06.10.2001. As per the order terms, M/s National Power Systems have to arrange
for issue of a Bank Guarantee for Rs 1,00,000/-, valid up to 10.02.2002, indemnifying them (viz.,
State Bank of Mysore, Nagpur) from any loss or damage caused by M/s National Power
Systems inability to execute the order as per order terms.
After obtaining a counter guarantee from M/s National Power Systems, State Bank of Mysore,
Hosur send an IFN 760 message to SBM Nagpur, (Their Ref. BG/310/2001) undertaking to pay
the receiver of the message up to Rs 1 lakh in case of breach of purchase order terms by M/s
National Power Systems.
Message Flow:
NATIONAL
POWER
SYSTEMS
REQUEST TO ISSUE GUARANTEE
COUNTER GUARANTEE
STATE BANK OF
MYSORE
HOSUR
IFN
760
STATE BANK OF
MYSORE
NAGPUR
108
The Extract of header and text block of the IFN 760 message sent by State Bank of Mysore,
Hosur to their Nagpur branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
SBMY0000765
SBMY0000345
IFN 760
State Bank of Mysore, Hosur

State Bank of Mysore, Nagpur
Guarantee
Text Block:
Field
Description
Information
27
Sequence of Total
1/1
20
Transaction Ref. Number
BG/310/2001
23
ISSUE
(1)
30
Date (OF ISSUE)
10112001
77C
Details of Guarantee
(2)
AMOUNT OF GUARANTEE RS. 98,800/GUARNTEE COVER FROM 24.08.2001 TO 22.07.2002
.
(3)
THIS DEED OF GUARANTEE EXECUTED BY THE STATE BANK OF
MYSORE, AN ASSOCIATE OF STATE BANK OF INDIA, UNDER THE
STATE BANK OF INDIA SUBSIDIARY ACT 1959, HAVING ITS HEAD
OFFICE AT KEMPEGOWDA ROAD, BANGALORE 560 009 AND
AMONGST OTHER PLACES, A BRANCH AT HOSUR, TAMILNADU
(HEREINAFTER REFERRED TO AS BANK) IN FAVOUR OF STATE BANK
OF MYSORE, NAGPUR (HEREINAFTER REFERRED TO AS
BENEFICIARIES ) FOR AN AMOUNT NOT EXCEEDING RS.1,00,000/(RUPEES ONE LAKH ONLY) AT THE REQUEST OF M/S NATIONAL
POWER SYSTEMS BANGALORE ROAD, HOSUR (HEREINAFTER
REFERRED TO AS VENDOR)
.
IN CONSIDERATION OF BENEFICIARIES HAVING AGREED TO ACCEPT
THIS BANK GUARANTEE OF RS.1,00,000/- (RUPEES ONE LAKHONLY)
REQUIRED FROM VENDOR TOWARDS SATISFACTORY PERFORMANCE FOR THE SUPPLY OF 1 SET OF 2 X 25.0 KVA UPS SYSTEMS WITH
BATTERY INSTALLED AT BENEFICIARIES PREMISES, ACCORDIING TO
THE TERMS AND CONDITIONS OF THE PURCHASE ORDER NO.
SBM/01-02/1305 DATED 26.10.2001, THE BANK DOES HEREBY
UNDERTAKE TO PAY BENEFICIARIES, AN AMOUNT NOT EXCEEDING
RS.1,00,000/- (RUPEES ONE LAKHONLY) AGAINST ANY LOSS OF
DAMAGE CAUSED TO OR SUFFERED OR WOULD BE CAUSED TO OR
SUFFERED BY BENEFICIARIES BY REASON OF ANY BREACH BY THE
SAID VENDOR OF ANY OF THE TERMS AND CONDITIONS OF THE
SAID PURCHASE ORDER.
109
WE, STATE BANK OF MYSORE, HOSUR, DO HEREBY UNDERTAKE TO

PAY THE AMOUNTS DUE AND PAYABLE UNDER THIS GURANTEE
WITHOUT ANY DEMUR ON A DEMAND FROM BENEFICIARIES
STATING THAT THE AMOUNT CLAIMED IS DUE BY WAY OF LOSS OR
DAMAGE CAUSED TO OR SUFFERED BY BENEFICIARIES BY REASON
OR ANY BREACH BY THE VENDOR OF ANY OF THE TERMS AND
CONDITIONS OF THE SAID PURCHASE ORDER
.
ANY SUCH DEMAND MADE ON THE BANK SHALL BE CONCLUSIVE
AS REGARDS THE AMOUNT DUE AND PAYABLE BY THE BANK
UNDER THIS GURANTEE
.
NOT WITHSTANDING ANYTHING CONTAINED HEREIN:
.
A. OUR LIABILITY UNDER THIS BANK GUARANTEE SHALL NOT BE
EXCEED EXCEEDING RS.1,00,000/- (RUPEES ONE LAKHONLY)
B. THIS BANK GUARANTEE SHALL BE VALID UPTO 10.02.2002 AND
THEREAFTER CEASES TO BE IN EFFECT IN ALL RESPECTS, WHETHER
OR NOT THE ORIGINAL BANK GUARANTEE IS RETURNED TO US AND
C. WE ARE LIABLE TO PAY THE GUARANTEED AMOUNT OR ANY
PART THEREOF UNDER THIS BANK GUARANTEE ONLY IF YOU SERVE
UPON US A WRITTEN CLAIM OR DEMAND ON OR BEFORE 10.02.2002
(1)
(2)
(3)
The words ISSUE in field 23 indicate that the sender of the message is issuing the
guarantee and that the receiver of the message is the party being indemnified. If the
words REQUEST appears in field 23, then it indicates that the receiver of the
message is being requested to issue a guarantee on behalf of the sender of the
message.
The column for field 77C has been widened to carry the rather lengthy guarantee
message.
In SFMS, blank lines are not allowed. It is therefore necessary to use a .to indicate
blank lines.
5.2. Request to issue a Guarantee:

IFN 760 messages are also used to relay requests sent by one branch to another requesting the
receiver to issue a guarantee on behalf of the sender of the message.
Example:
In the example given in section 5.1 above, let us assume that the beneficiary is not State Bank of
Mysore, Nagpur but a Nagpur based company say SSR Ltd. State Bank of Mysore, Hosur would
then send an IFN 960 message to its Nagpur branch, requesting the latter to issue the guarantee
on its behalf.
110
Message Flow:
NATIONAL
POWER
SYSTEMS

COUNTER GUARANTEE
STATE BANK OF
MYSORE
HOSUR
IFN
760
SSR LTD
GUARANTEE
STATE BANK OF
MYSORE
NAGPUR
Header Block:
Sender
Receiver
Message Type
SBMY0000765
SBMY0000345
IFN 760
State Bank of Mysore,Hosur

Guarantee
Text Block:
Field
Description
Information
27
Sequence of Total
1/1
20
BG/310/2001
23
REQUEST
(1)
30
Date (FOR ISSUE)
10112001
(2)
77C
Details of Guarantee
AMOUNT OF GUARANTEE RS. 98,800/GUARNTEE COVER FROM 24.08.2001 TO 22.07.2002
.
THIS DEED OF GUARANTEE EXECUTED BY THE STATE BANK OF
MYSORE, AN ASSOCIATE OF STATE BANK OF INDIA, UNDER THE
STATE BANK OF INDIA SUBSIDIARY ACT 1959, HAVING ITS HEAD
OFFICE AT KEMPEGOWDA ROAD, BANGALORE 560 009 AND
AMONGST OTHER PLACES, A BRANCH AT NAGPUR (HEREINAFTER
REFERRED TO AS BANK) IN FAVOUR OF M/S SSR LTD., NAGPUR
(HEREINAFTER REFERRED TO AS BENEFICIARIES ) FOR AN AMOUNT
NOT EXCEEDING RS.1,00,000/- (RUPEES ONE LAKH ONLY) AT THE
111
REQUEST OF M/S NATIONAL POWER SYSTEMS BANGALORE ROAD,

HOSUR (HEREINAFTER REFERRED TO AS VENDOR)
.
IN CONSIDERATION OF BENEFICIARIES HAVING AGREED TO ACCEPT
THIS BANK GUARANTEE OF RS.1,00,000/- (RUPEES ONE LAKHONLY)
REQUIRED FROM VENDOR TOWARDS SATISFACTORY PERFORMANCE FOR THE SUPPLY OF 1 SET OF 2 X 25.0 KVA UPS SYSTEMS WITH
BATTERY INSTALLED AT BENEFICIARIES PREMISES, ACCORDIING TO
THE TERMS AND CONDITIONS OF THE PURCHASE ORDER NO.
SBM/01-02/1305 DATED 26.10.2001, THE BANK DOES HEREBY
UNDERTAKE TO PAY BENEFICIARIES, AN AMOUNT NOT EXCEEDING
RS.1,00,000/- (RUPEES ONE LAKH ONLY) AGAINST ANY LOSS OF
DAMAGE CAUSED TO OR SUFFERED OR WOULD BE CAUSED TO OR
SUFFERED BY BENEFICIARIES BY REASON OF ANY BREACH BY THE
SAID VENDOR OF ANY OF THE TERMS AND CONDITIONS OF THE
SAID PURCHASE ORDER
.
WE, STATE BANK OF MYSORE, NAGPUR, DO HEREBY UNDERTAKE TO
PAY THE AMOUNTS DUE AND PAYABLE UNDER THIS GURANTEE
WITHOUT ANY DEMUR ON A DEMAND FROM BENEFICIARIES
STATING THAT THE AMOUNT CLAIMED IS DUE BY WAY OF LOSS OR
DAMAGE CAUSED TO OR SUFFERED BY BENEFICIARIES BY REASON
OR ANY BREACH BY THE VENDOR OF ANY OF THE TERMS AND
CONDITIONS OF THE SAID PURCHASE ORDER
.
ANY SUCH DEMAND MADE ON THE BANK SHALL BE CONCLUSIVE
AS REGARDS THE AMOUNT DUE AND PAYABLE BY THE BANK
UNDER THIS GURANTEE
.
NOT WITHSTANDING ANYTHING CONTAINED HEREIN:
.
A. OUR LIABILITY UNDER THIS BANK GUARANTEE SHALL NOT BE
EXCEED EXCEEDING RS.1,00,000/- (RUPEES ONE LAKH ONLY)
B. THIS BANK GUARANTEE SHALL BE VALID UPTO 10.02.2002 AND
THEREAFTER CEASES TO BE IN EFFECT IN ALL RESPECTS, WHETHER
C. WE ARE LIABLE TO PAY THE GUARANTEED AMOUNT OR ANY
PART THEREOF UNDER THIS BANK GUARANTEE ONLY IF YOU SERVE
(1) The words REQUEST in field 23, indicates that the receiver of the message is being
requested to issue a guarantee on behalf of the sender of the message
(2) The date on which the receiver should issue the guarantee.
(3) The guarantee has been worded as it would appear if the receiver were to issue the
guarantee. It can also be worded as if sender was issuing the guarantee. The receiver
would effect the necessary changes.
112
5.3. Acknowledgement of Guarantee Message:

IFN 760 messages are used to relay amendments to a guarantee.
Example:
In the example given in section 5.2 above, Stata Bank of Mysore would send an IFN 768
message to acknowledge the guarantee message.
Message Flow:
NATIONAL
POWER
SYSTEMS
COUNTER GUARANTEE
STATE BANK OF
MYSORE
HOSUR
IFN
767
GUARANTEE
SSR LTD
IFN
768
STATE BANK OF
MYSORE
NAGPUR
Nagpur to their Hosur branch would appear as follows:
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
30
SBMY0000345
SBMY0000765
IFN 768

Guarantee Acknowledgement
Description
Related Reference
Date of messsage being acknowledged
Information
BG/102/2001
BG/310/2001
10112001
113
5.4. Guarantee Amendment:

IFN 760 messages are used to relay amendments to a guarantee.
Example:
In the example given in section 5.2 above, let us assume that on 31.1.2002, M/s National Power
Systems, request State Bank of Mysore, Hosur to extend the validity period of the guarantee up
to 31.3.2001. State Bank of Mysore, Hosur would then send an IFN 767 message to its Nagpur
branch, requesting the latter to advise M/s SSR Ltd of the amendment to the guarantee.
Message Flow:
REQUEST TO AMEND GUARANTEE
NATIONAL
POWER
SYSTEMS
AMENDED COUNTER GUARANTEE
STATE BANK OF
MYSORE
HOSUR
IFN
767
GUARANTEE AMENDMENT
SSR LTD
STATE BANK OF
MYSORE
NAGPUR
Header Block:
Sender
Receiver
Message Type
Text Block:
Field
27
20
21
23
30
26E
SBMY0000765
SBMY0000345
IFN 767
State Bank of Mysore,Hosur

Guarantee Amendment
Description
Sequence of Total
Related Reference
Date (FOR AMENDMENT)
Number of Amendment
Information
1/1
BG/310-AMD1/2001
BG/310/2001
REQUEST
31012001
1
114
31C
Date of Request to Issue
10112001
77C
Amendment Details
THE GUARANTEE HAS BEEN AMENDED AS FOLLOWS.
.
1. THE VALIDITY PERIOD OF THE GUARANTEE HAS BEEN EXTENDED
UP TO 31.3.2002.
2. THE BANK GUARANTEE SHALL BE VALID UPTO 31.03.2002 AND
THEREAFTER CEASE TO BE IN EFFECT IN ALL RESPECTS, WHETHER
WE ARE LIABLE TO PAY THE GUARANTEED AMOUNT OR ANY PART
THEREOF UNDER THIS BANK GUARANTEE ONLY IF YOU SERVE
3. ALL OTHER TERMS AND CONDITIONS REMAIN UNCHANGED.
5.5. Advice of Reduction or Release:

Header Block:
Sender
Receiver
Message Type
Text Block:
Field
20
21
30
33B
SBMY0000345
SBMY0000765
IFN 769

Advice of Reduction
Description
Related Reference
Date of Reduction/Release
Amount Reduced/Released
Information
BG/102/2001
BG/310/2001
31012001
1
6. Debit Credit Advices:

7. Opinion Reports:
7.1. Request for Opinion Report
Header Block:
Sender
Receiver
Message Type
SBMY0000345
SBMY0000765
IFN 985

Status Enquiry
Text Block:
115
Field
20
59
75
Description
Enquired Party
Queries
Information
BG/102/2001
31012001
1
7.2. Opinion Reports:
Header Block:
Sender
Receiver
Message Type
SBMY0000345
SBMY0000765
IFN 986

Status Report
Text Block:
Field
20
59
79
Description
Enquired Party
Narrative
Information
BG/102/2001
31012001
1
116

SFMS - Guidelines

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SFMS - Guidelines

Hochgeladen von

Copyright:

Verfügbare Formate

INTRODUCTION: .......................................................................................................................

CUSTOMER FUNDS TRANSFERS ................................................................................... 5

1.1. CUSTOMER TTS/MTS. ......................................................................................................... 5

REPLIES TO DD STOP PAYMENT REQUESTS. (IFN 112) .................................................... 54

INTER-BRANCH MESSAGES INVOLVING INTRA-BANK AND INTER-BANK

ACKNOWLEDGEMENT OF RECEIPT OF COLLECTION BILLS. (IFN 410)........................... 73

SHORT LCS (PRE-ADVICES). (IFN 705) ............................................................................ 83

Intra Bank Messages

1. Customer Funds Transfers

1.1.1. Immediate application of funds and use of traditional means of

: Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Mumbai

This is the paying branch TT Reference No.

1.2.1. Reconciliation of Messages while applying funds

Debit entries relating to Paid TTs would not be outstanding at all.

1.2.1.1.1. Reconciliation of TT Message using IFN 910/900 & 195/196 messages

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Mumbai

Andhra Bank Reconciliation System

Andhra Bank, Mumbai

Reconciliation of TT Message using IFN 910 & 195/196 messages

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank, Mumbai

Andhra Bank Reconciliation System

Andhra Bank, Masab Tank, Hyderabad

Andhra Bank Reconciliation System

Andhra Bank, Mumbai

1.3. Multiple Customer TTs/MTs.

Immediate application of funds and use of traditional means of reconciliation.

1.3.1. Immediate application of funds and use of traditional means of

Information Common to all TTs:

: Allahabad Bank, Kolkata

Beneficiarys Account No.

Allahabad Bank, Kolkata

1.3.2. Immediate application of funds and use of IFN messages for

Allahabad Bank, Kolkata

Allahabad Bank, Kolkata

Allahabad Bank, Bangalore

This is the paying branch TT Reference No.

1.3.3. Reconciliation of Messages while applying funds

Reconciliation of Messages while applying funds (IFN 102, 195,

Allahabad Bank, Kolkata

Allahabad Bank, Kolkata

Allahabad Bank, Bangalore

Allahabad Bank Reconciliation System

Allahabad Bank, Bangalore

Reconciliation of TT Message using IFN 910 & 195/196 messages

Allahabad Bank, Kolkata

Allahabad Bank, Kolkata

Allahabad Bank, Bangalore

Allahabad Bank Reconciliation System

1.3.3.2. Indirect Method:

Allahabad Bank, Kolkata

Allahabad Bank Reconciliation System

Allahabad Bank, Bangalore

1.4. Customer Request for Transfer of Funds.

: Bank of Maharastra, Pune

Bank of Maharastra, Pune

Requested Execution Date