100% found this document useful (1 vote)
12K views16 pages

NEFT Message Formats

This document contains message formats for transmitting transactions through the National Electronic Funds Transfer (NEFT) system. It includes: 1. The message format for transmitting credit transactions from the NEFT gateway to banks, which contains fields for the transaction reference number, batch time, total transactions, total amount, and details for each credited transaction. 2. The message format for transmitting debit transactions from NEFT branches to the gateway, which contains fields for the transaction reference number, batch time, total transactions, total amount, and details for each debited transaction. 3. The message format for transmitting return transactions from NEFT branches to the gateway, which is similar to the debit format but includes fields for the related reference

Uploaded by

mukeshkpatidar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
12K views16 pages

NEFT Message Formats

This document contains message formats for transmitting transactions through the National Electronic Funds Transfer (NEFT) system. It includes: 1. The message format for transmitting credit transactions from the NEFT gateway to banks, which contains fields for the transaction reference number, batch time, total transactions, total amount, and details for each credited transaction. 2. The message format for transmitting debit transactions from NEFT branches to the gateway, which contains fields for the transaction reference number, batch time, total transactions, total amount, and details for each debited transaction. 3. The message format for transmitting return transactions from NEFT branches to the gateway, which is similar to the debit format but includes fields for the related reference

Uploaded by

mukeshkpatidar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 16

Institute for Development and Research in

Banking Technology
Hyderabad
NEFT Message Formats
FEBRUR! "#$#
Table of Contents
1 Message for transmitting NEFT credit lists to Bank Gateway - IFN298N2!!!!!!!!!!!!!!!"
2 #$tward %e&it Messages from NEFT Branc'es IFN298N(!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
" *et$rn Transactions from NEFT Branc'es IFN298N+!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!+
, #$tward - Inward .redit confirmation message at &ranc' IFN298N1!!!!!!!!!!!!!!!!!!!!1
) Message for transmitting ret$rn transaction details to Bank Gateway IFN298N"
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!11
( Transmission of *e/ected Transactions at NEFT 0er1ice 0tation to Bank Branc'es
IFN298N9!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1"
+ End-of-%ay-End-of-Batc' Message IFN298N,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1)

1 Message for transmitting NEFT credit lists to Bank Gateway -
IFN2!N"2
M#$ Field No Field Name Contents #
$%tions
&escri%tion
M 2020 Transaction
Reference
Number
16x Uniquely identifies the
message.
M !! "atch Time #$n %t is the netting batch time
&hose settlement resulted in
this in&ard credit.
M !1'0 Total ( of
transactions
'n Total ( of transactions )loo*s+
in the message
M #110 Total amount 1,d -um of .mounts in loo*s
Re*eating /rou* "egins
M 2020 Transaction
Reference
Number
16x Uniquely identifies the
transaction )loo*+. %t is the
transaction reference
s*ecified by the sender in
originating 2,'N06 message.
0 2006 Related
Reference
Number
16x Transaction reference of the
original N02 message that is
returned through N012 for
&hich this N02 is created..
This is *o*ulated only &hen
an N02 is created because of
an N01 message. N02
%n&ard return.
M !1!6 -ending
branch3s
%4-5
#$a#$c6$c7 -ending branch3s %4-5
0 60! -ending
customer a8c
ty*e
2$c -ender3s account ty*e.
M 6021 -ending
customer a8c
(
!x -ender3s account Number
M 60,1 -ending
customer a8c
name
!0x -ender3s account name
M 1002 0riginator of
Remittance
#9!x
M !!6, "eneficiary
branch3s
%4-5
#$a#$c6$c7 Reci*ient branch3s %4-5
0 610 "eneficiary
customer a8c
ty*e
2$c Recei:ing customer3s
account ty*e
M 6061 "eneficiary
customer a8c
(
!x Recei:ing customer account
Number
M 60'1 "eneficiary !0x Recei:ing customer3s
customer a8c
name
account name
0 !!6! "eneficiary
customer
address
#9!x "eneficiary customer address
0 1#,! Remittance
information
69!x %nformation on remittance
gi:en by the sending
customer
0 6#6 Reason 5ode $x %t is the reason code for
&hich an initial N02 message
&as returned. This is
*o*ulated only &hen an N02
is created because of an N01
message.
0 666 Re;ection
Reason
!0x <escri*tion of the reason for
return. This is *o*ulated only
&hen an N02 is created
because of an N01 message.
M #0' .mount 1,d =alue of the remittance
M '0 =alue <ate '$n <ate on &hich settlement has
ta>en *lace
M 1! Remittance
<ate
'$n <ate on &hich the sender
branch initiated the
remittance.
Re*eating /rou* ?nds
Note' The message 2,'N02 is recei:ed from R"% after the netting *rocess is com*leted. The
message is sent to the beneficiary ban>3s ser:ice center from &here it reaches the final
beneficiary branch. The branch that initiates the out&ard debit )2,'N06+ or return transaction
)2,'N01+ &ould not recei:e any message if the messages &ere acce*ted at R"%. The beneficiary
ban> &ill recei:e only 2,'N02 message irres*ecti:e of the debiting ban> is sending a 2,'N06 or
2,'N01 message. The only difference bet&een a 2,'N02 recei:ed for a 2,'N06 or 2,'N01
message is *resence of fields 2006)Related Reference Number+2 6#6 )reason code+ and 666
)Re;ection Reason+ in a 2,'N02 message that is recei:ed because of a return transaction
)2,'N01+.
2 $(tward &ebit Messages from NEFT Branc)es IFN2!N"*
M80 4ield
No
4ield Name 5ontents 8
0*tions
<escri*tion
M 2020 Transaction Reference
Number
16x Uniquely identifies the message.
0 !! "atch Time #$n "atch Time.
The field is o*tional but if s*ecified it
must be either 100 or 1200 or 1600.
M 1106 Total number of loo*s
in the message
!n Number of transactions)loo*s+ in the
message
M #06 -um of .mounts 1,d -um of all amounts in the loo*s
Re*eating /rou* "egins
M 2020 Transaction Reference
Number
16x Uniquely identifies the transaction
)loo*+
M #0' .mount 1,d =alue of the remittance
M '0 =alue <ate '$n <ate on &hich settlement ta>es
*lace. %t can be only the current date.
M !1!6 -ending branch3s %4-5 #$a#$c6$c7 -ending branch3s %4-5.
The %4-5 must be -4M- ?nabled
only.
0 60! -ending 5ustomer
.ccount Ty*e
2$5 -ender3s account ty*e
.llo&ed :alues are
10 @ -.=%N/- ".NA
11 @ 5URR?NT .550UNT
1 @ 5.-B 5R?<%T
1# @ C0.N .550UNT
12 @ 0:erdraft
#0 D NR?
!0 D Remittance for 5ustomer not
ha:ing account in ban>
!1@ %ndo Ne*al Remittance
!2 D 5ard to 5ard Eayments
M 6021 -ending 5ustomer
.ccount Number
!x -ender3s account Number
M 60,1 -ending 5ustomer
.ccount Name
!0x -ender3s account name
$ +*2 ,ending C(stomer
Mobile No#Email Id
-.c
*2/
,ender0s mobile n(mber or e-mail
id1
-.c s)o(ld be eit)er ,M, or EM2
only
*2/ contains e-mail id or mobile
n(mber
Mobile n(mber s)o(ld be at least
1" digits
M 1002 0riginator of
Remittance
#9!
M !!6, "eneficiary branch3s
%4-5
#$a#$c6$c7 Reci*ient branch3s %4-5
The %4-5 must be -4M- ?nabled
only.
%4 =al )60!+ F !1
Then =al )!!6,+ F -"%N000##0
0 610 "eneficiary 5ustomer
.ccount Ty*e
2$5 Recei:ing customer3s account ty*e
.llo&ed :alues are
10 @ -.=%N/- ".NA
11 @ 5URR?NT .550UNT
1 @ 5.-B 5R?<%T
1# @ C0.N .550UNT
12 @ 0:erdraft
#0 D NR?
M 6061 "eneficiary 5ustomer
.ccount Number
!x "eneficiary 5ustomer .ccount
Number
%4 =al )60!+ F !1
Then =al )6061+ F 2,,#6'0##02
M 60'1 "eneficiary 5ustomer
.ccount Name
!0x Recei:ing customer3s account name
0 !!6! "eneficiary 5ustomer
.ddress
#9!x "eneficiary customer address
0 1#,! -ender to Recei:er
%nformation
69!x Remittance %nformation from sender
to recei:er
Re*eating /rou* ?nds
Note' The 2,'N06 message is the first message to initiate an N?4T transaction. %t is generated
from the branch that recei:es a funds transfer request from their customer to a customer in
different ban>. .ll the 2,'N06 messages are to be sent to the ser:ice center branch of the ban>.
.t the ser:ice center ban>2 the N?4T a**lication &ill consolidate the indi:idual transactions from
the branches into a bigger message of 10 loo*s and sends the message to R"% N?4T center by
allocating the next a:ailable batch. %f the batch time is s*ecified by the branch in the 2,'N06
message then the message &ill be released to R"% to settle in the batch s*ecified.
The 2,'N06 messages that are recei:ed by the N?4T a**lication at the ser:ice center can be
re;ected8rescheduled for :arious reasons. The N?4T a**lication in this case &ould release a
2,'N0, message to the branch that initiates the transaction. The ban>s ha:e to ta>e care that the
core ban>ing a**lication does not re;ect the transaction that recei:e a 2,'N0, message &ith a
reschedule reason code.
The reason codes that are used for rescheduling at the "an>3s ser:ice center areG
101 D Cate arri:al at -5 )This re;ection is recei:ed &hen a transaction is recei:ed by the ser:ice
center branch after the batch time s*ecified in the 2,'N06 message.+
101 D East =alue <ate
10' D Boliday at -er:ice 5enter
- 3et(rn Transactions from NEFT Branc)es IFN2!N"4
M80 4ield No 4ield Name 5ontents 8
0*tions
<escri*tion
M 2020 Transaction
Reference
Number
16x Uniquely identifies the message.
0 !! "atch Time #$n "atch Time.
This is not *o*ulated in the current
a**lication &here the user returns
an in&ard credit using the Return
Mar>ing functionality of -4M-.
M 1106 Total number
of loo*s in
the message
!n Total number of loo*s in the
message
M #06 -um of
.mounts
1,d -um of all amounts in the loo*s
Re*eating /rou* "egins
M 2020 Transaction
Reference
Number
16x Uniquely identifies the transaction
)loo*+
M 2006 Related
Reference
Number
16x Transaction Reference Number of
the recei:ed in&ard credit message
at ban> branch that is returned
M #0' .mount 1,d =alue of the remittance
M '0 =alue <ate '$n <ate on &hich settlement ta>es
*lace.
The system &ill *o*ulate the current
date &hen the user mar>s a
transaction for returning.
M !1!6 -ending
"ranch3s
%4-5
#$a#$c6$c7 -ending branch3s %4-5
0 60! -ending
5ustomer
.ccount
Ty*e
2$5 -ender3s account ty*e
.llo&ed :alues are
10 @ -.=%N/- ".NA
11 @ 5URR?NT .550UNT
1 @ 5.-B 5R?<%T
1# @ C0.N .550UNT
12 @ 0:erdraft
#0 D NR?
M 6021 -ending
5ustomer
.ccount
Number
!x -ender3s account number
M 60,1 -ending
5ustomer
.ccount
Name
!0x -ender3s account name
M 1002 0riginator of
Remittance
#9!x
M !!6, "eneficiary
branch3s
%4-5
#$a#$c6$c7 Reci*ient branch3s %4-5
0 610 "eneficiary
5ustomer
.ccount Ty*e
2$5 Recei:ing customer3s account ty*e
.llo&ed :alues are
10 @ -.=%N/- ".NA
11 @ 5URR?NT .550UNT
1 @ 5.-B 5R?<%T
1# @ C0.N .550UNT
12 @ 0:erdraft
#0 D NR?
!0 D Remittance for 5ustomer not
ha:ing account in ban>
!1@ %ndo Ne*al Remittance
!2 D 5ard to 5ard Eayments
M 6061 "eneficiary
5ustomer
.ccount
Number
!x Recei:ing customer account
number
M 60'1 "eneficiary
5ustomer
.ccount
Name
!0x Recei:ing customer3s account name
0 !!6! "eneficiary
5ustomer
.ddress
#9!x "eneficiary customer address
M 6#6 Reason 5ode $c Return 5ode
M 666 Re;ection
5ode
!0x <escri*tion of the reason for
re;ection
0 1#,! -ender to
Recei:er
%nformation
69!x Remittance %nformation from sender
to recei:er
Re*eating /rou* ?nds
Note' . 2,'N01 message is released to re;ect a 2,'N02 message that is recei:ed by the ban>
branch from R"% and could not a**ly the funds because of :arious reasons gi:en belo&G
R01 .550UNT 5C0-?<
R02 .550UNT TR.N-4?RR?<
R0 .550UNT <0?- N0T ?H%-T
R0# N0 -U5B .550UNT TIE?
R0! "?N?4%5%.RI N.M? <%44?R?-
R06 .550UNT B0C<?R ?HE%R?<
R01 .550UNT UN<?R .TT.5B?M?NT
R0' /.RN%-B% 0R<?R R?5?%=?<
R0, 0E?R.T%0N- -U-E?N<?<
R10 E.RTIJ- %N-TRU5T%0N-
R11 .NI 0TB?R R?-0N-
R12 5R?<%T T0 NR% .550UNT
The 2,'N01 message is sent to the ser:ice center branch &here it is consolidated in multi*le
loo*s and then released to R"% N?4T center. .s ex*lained for the 2,'N06 message2 a 2,'N01
message can also be re;ected or rescheduled at the ser:ice center branch and the ban> has to
ta>e care not to re;ect the transaction that is re;ected &ith a reschedule reason code. The same
reason codes as s*ecified in the 2,'N06 message are the reschedule reason codes.
NoteG .ll the fields &ill be *o*ulated by the system &hile creating the 2,'N01 message using the
Return Mar>ing functionality of -4M-. The user ;ust needs to select the re;ection code for the
returning a transaction.
5 $(tward # Inward Credit confirmation message at branc)
IFN2!N1"
M#$ Field No Field Name Contents #
$%tions
&escri%tion
M 2020 Transaction
Reference
Number
16x Uniquely identifies the
message.
Re*eating /rou* "egins
M 2020 Transaction
Reference
Number
16x Uniquely identifies the
transaction. )loo*+
M !!1' %4-5 of
0riginator of
Remittance
#$a#$c6$c7 %4-5 of <ebit 0riginator
M 2006 Related
Reference
16x Transaction Reference
Number of the recei:ed
in&ard credit message at
ban> branch that is credit
confirmed.
M !01 .mt 5redited
Time
'$n
6$n
<ate and Time &hen the
amount is credited to the
customer
'$n is the credited date
IIIIMM<<
6$n is the credited time
BBM%--
Re*eating /rou* ?nds
. 2,'N10 message is released to confirm that the amount in 2,'N02 message that is recei:ed
by the beneficiary ban> branch from R"% is credited to customer. The 2,'N10 message is sent to
the beneficiary ser:ice center &here it is consolidated in multi*le loo*s and then released to R"%
N?4T center. "an> &ise segregation of N10 messages &ill be done at R"% and N10 messages
are sent to the res*ecti:e -ender "an> ser:ice centers and subsequently to the actual N06
sender branch.
NoteG .ll the fields &ill be *o*ulated by the system &hile creating the 2,'N10 message using the
5redit 5onfirmation functionality of -4M-. The user ;ust needs to select the transaction to be
credit confirmed.
+ Message for transmitting ret(rn transaction details to Bank
Gateway IFN2!N"-
M#$
Field No Field Name Contents /
Options
Description
M 2020 Transaction
Reference
Number
16x Uniquely identifies the
message.
M !! "atch Time #$n %t is the "atch time
during &hich the
message has been
re'ected at R"%.
M !1(!
Total ( of
transactions
(n Total Number of
transactions )loo*s+
*resent in the message
M #11! Total
amount
re'ected
1,d
,um of amounts in the
loo*s.
Re*eating -rou* "egins
M 2020 Transaction
Reference
Number
16x ,ystem generated unique
transaction reference.
M !.!6 ,ending
branch/s
%0,1
11$x ,ending branch/s %0,1
M 2006 Related
Transaction
Ref. No.
16x Transaction Reference
Number s*ecified in the
originating 22(N06
message
M !!62 "eneficiary
branch/s
%0,1
11$x Reci*ient branch/s %0,1
s*ecified in the
originating 22(N06
message
3 610 "eneficiary
customer a4c
ty*e
2$c Recei5ing customer/s
account ty*e s*ecified in
the originating 22(N06
message
M 6061 "eneficiary
customer a4c
6
!x Recei5ing customer
account Number
s*ecified in the
originating 22(N06
message
M 60(1 "eneficiary
customer a4c
!0x Recei5ing customer/s
account name s*ecified
name in the originating
22(N06 message
3 !!6! "eneficiary
customer
address
#7!x "eneficiary customer
address s*ecified in the
originating 22(N06
message
M #0( 8mount 12d 9alue of the remittance
s*ecified in the
originating 22(N06
message
M (0 9alue :ate ($n :ate on &hich the
re'ection is done.
M
.! Remittance
:ate
($n :ate on &hich the sender
branch initiated the
remittance
3 (1 3riginal
5alue date
($n 3riginal 5alue date
s*ecified in the 22(N06
message sent from
ban;/s ser5ice center
M
6#6 Reason
1ode
$x Re'ection code
M 666 Re'ection
Reason
!0x :escri*tion of the
re'ection code
3 .#2! Remittance
information
67!x %nformation on
remittance gi5en by the
sending customer
Re*eating -rou* <nds
Note: 8 22(N0 message is recei5ed by the sending ban; ser5ice center and in turn by
the sending branch if a 22(N06 or 22(N0. message is re'ected or rescheduled at R"%
N<0T center. The field 2006 &ill ha5e the transaction reference of the 22(N06 or
22(N0. message that is re'ected or rescheduled. The reason for re'ection or rescheduling
is s*ecified in the field 6#6 and 666. %n case of reschedule the transaction is still li5e at
R"% but it is 'ust an information bac; to the sending ban; that the message could not be
settled in the batch or 5alue date s*ecified in the outgoing message from the ban;. The
ban;s ha5e to ta;e care that they do not re'ect their transactions in their core ban;ing
a**lications on recei*t of a N0 message &ith a reschedule reason code.
The reason codes that are used for rescheduling at R"% N<0T center are=
02# > "atch does not exist on ,aturday
02( > ?oliday at R"%
022 > @ast 9alue :ate
100 > Aate 8rri5al for a batch
0or all other reason codes the transaction needs to be re'ected in the ban;/s a**lication.
* Transmission of 3e6ected Transactions at NEFT ,er7ice
,tation to Bank Branc)es IFN2!N"
M/O Field No Field Name Contents /
Options
Description
M 2020 Transaction
Reference
Number
16x Uniquely identifies the
message.
M !! "atch Time #$n "atch Time.
%t is the batch time during
&hich the 22(N02
message is created at
,er5ice center.
M !1(! Total
Number of
transactions
re'ected by
,er5ice
1enter of
"an;
-ate&ay
(n Total Number of re'ected
transactions in the message
M #11! Total
amount
re'ected by
,er5ice
1enter at
"an;
-ate&ay
12d Total amount of re'ected
transactions in the message
Re*eating -rou* "egins
M 2020 Transaction
Reference
Number
16x Transaction Reference
Number is unique for each
transaction)loo*+.
%t is system generated.
M !.!6 ,ending
"ranch/s
%0,1
#$a#$cB$cC ,ending branch/s %0,1
M 2006 Related
Reference
16x Transaction Reference of
the original N06 message
M !!62 "eneficiary
branch/s
%0,1
#$a#$cB$cC Reci*ient branch/s %0,1
3 610 "eneficiary
1ustomer
8ccount
2$c Recei5ing customer/s
account ty*e
Ty*e
M 6061 "eneficiary
1ustomer
8ccount
Number
!x Recei5ing customer
account number
M 60(1 "eneficiary
1ustomer
8ccount
Name
!0x Recei5ing customer/s
account name
3 !!6! "eneficiary
1ustomer
8ddress
#7!x "eneficiary customer
address
M #0( 8mount 12d 9alue of the remittance
M (0 9alue :ate ($n :ate on &hich settlement
ta;es *lace
M .! Remittance
:ate
($n :ate on &hich the sender
branch initiated the
remittance
3 (1 3riginal
5alue date
($n 3riginal settlement date
for &hich the transaction
&as initiated
M 6#6 Reason
1ode
$x Re'ection code
M 666 Re'ection
Reason
!0x :escri*tion of the reason
for re'ection
3 .#2! ,ender to
Recei5er
%nformation
67!x Remittance %nformation
from sender to customer
Re*eating -rou* <nds
Note: 8s stated abo5e for 22(N06 and 22(N0. messagesD this message is sent by the
N<0T ser5ice center branch of the ban; if an out&ard debit or return transaction message
is re'ected or rescheduled at N<0T ser5ice center. The field 2006 &ill ha5e the
transaction reference of the 22(N06 or 22(N0. message that is re'ected or rescheduled.
The fields 6#6 and 666 &ill s*ecify the reason code and re'ection reason for re'ection
or rescheduling of the transaction.
The reason codes that are used for rescheduling at the "an;/s ser5ice center are=
101 > Aate arri5al at ,1 )This re'ection is recei5ed &hen a transaction is recei5ed by the
ser5ice center branch after the batch time s*ecified in the 22(N06 message.+
10. > @ast 9alue :ate
10( > ?oliday at ,er5ice 1enter
The ban;s ha5e to ta;e care that the core ban;ing a**lication does not re'ect the
transaction that recei5e a 22(N02 message &ith a reschedule reason code.
4 End-of-&ay#End-of-Batc) Message IFN2!N"5
M#$ Field No Field Name Contents #
$%tions
&escri%tion
M (! Transaction
:ate
($n :ate of transaction
3 !! "atch Time #$n "atch Time.
This is *o*ulated only in
case of <nd of "atch
message. Ehen this field is
*o*ulatedD all the details
mentioned in this message
are of this batch only and not
<nd of :ay.
M !1.! No of
3ut&ard
:ebit Txns at
N<0T4,1
(n Total number of acce*ted
and re'ected :ebit
transactions.
M #10! Total 8mt of
3ut&ard
:ebit Txns at
N<0T4,1
12d Total amount of acce*ted
and re'ected :ebit
transactions.
M !1(0 No 3f
3ut&ard
:ebit Txns
acce*ted at
N<0T4,1
(n Total No. of 3ut&ard :ebits
transactions acce*ted
M #110 ,um 8mt of
3ut&ard
:ebit Txns
acce*ted at
N<0T4,1
12d Total amount of 3ut&ard
:ebits transactions acce*ted
M !1(! No 3f
3ut&ard
:ebit Txns
re'ected at
N<0T4,1
(n Total No. of 3ut&ard :ebits
transactions re'ected
M #11! ,um 8mt of
3ut&ard
:ebit Txns
re'ected at
N<0T4,1
12d Total amount of 3ut&ard
:ebits transactions re'ected
M !26. No of %n&ard
credits
(n Total No. of %n&ard 1redits
recei5ed for the ban;4branch
recei5ed for
the
ban;4branch
M ##10 ,um 8mt of
the in&ard
credits
recei5ed
12d Total amount of %n&ard
1redits recei5ed for the
ban;4branch
M !0#. No of Return
Txns recei5ed
for the ban;
or branch
(n Total No. of Return
transactions recei5ed for the
ban; or branch.
M ##60 ,um 8mt of
the return
Txns
recei5ed
12d Total amount of Return
transactions recei5ed for the
ban;4branch
Note: The <nd of :ay message )22(N0#+ is sent after the last batch is settled at R"%. %t
gi5es the details about all the messages that are sent by the ban;/s ser5ice center branch
to R"% and the number and amount of the messages that are acce*ted or re'ected. Ehen
the message is recei5ed at the ban;/s ser5ice centerD the ser5ice center &ill release an
<3: message to all the branches that ha5e initiated the N<0T messages for the day &ith
the count and amount of acce*ted and re'ected messages along &ith total message count
and amount.
The <nd of "atch Message is sent after each batch exce*t the last batch of the day. %.e. %f
there are batches in a day. <.g. 100D 1200D 1600 then an End of Batch Message is
recei5ed for batches 100 and 1200. 8nd End of Day message is recei5ed after 1600.
There &on/t be an End of Batch message for 1600 batch.

You might also like