ISO20022 standard Message Implementation

ISO20022 Business Application Header

ISO Message: “head.001.001.01 BusinessApplicationHeaderV01”

ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
head.001.001.01 Multi /NEFT
BusinessApplicationHe Multi
aderV01
Message Item
<AppHdr> Root tag [1..1] [1..1]
From <Fr> The sending 2.0 [1..1] [1..1]
MessagingEndpoin
t that has created
this Business
Message for the
receiving
MessagingEndpoin
t that will process
this Business
Message.
FinancialInstitutionIde <FinInstnId> Identification of 2.34 [0..1] [1..1]
ntification a financial
institution
ClearingSystemMemb <ClrSysMmbI ClearingSystemM 2.37 [0..1] [1..1]
erIdentification d> emberIdentificati
on
Member Identification <MmbId> IFSC of the 2.41 [1..1] [1..1] <From><FinInstnId><ClrSysMmbId>< Max35Te
Sending MmbId>CANB0239777</MmbId><Cl xt
participant rSysMmbId></FinInstnId></From>
To <To> The 3.0 [1..1] [1..1]
MessagingEndpoin
t designated by the
sending
MessagingEndpoin
t to be the
recipient who will
ultimately process

Reserve Bank of India

ISO Message, “head.001.001.01 BusinessApplicationHeaderV01”
1
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
head.001.001.01 Multi /NEFT
BusinessApplicationHe Multi
aderV01
Message Item
this Business
Message
FinancialInstitutionIde <FinInstnId> Identification of 3.34 [0..1] [1..1]
ntification a financial
institution
ClearingSystemMemb <ClrSysMmbI ClearingSystemM 3.37 [0..1] [1..1]
erIdentification d> emberIdentificati
on
Member Identification <MmbId> IFSC of the 3.41 [1..1] [1..1] <FinInstnId><ClrSysMmbId>MmbId> Max35Te
Sending HDFC0239777</MmbId></ClrSysMm xt
participant bId>FinInstnId>

Validation are:
Character Information R
position
First four Bank code F
characters
Fifth character Zero R
Last six Branch code B
characters
no w
BusinessMessageIden <BizMsgIdr> Uniquely 4.0 [1..1] [1..1] Same as MessageIdentification <BizMsgIdr>HDFC201210180000000 Max35Te
tifier identifies the <MsgId> in the associated business 218</BizMsgIdr> xt
business message
message
MessageDefinitionIde <MsgDefIdr> Message 5.0 [1..1] [1..1] Contains the MessageIdentifier that <MsgDefIdr> Max35Te
ntifier Identifier defines the Business Message as pacs.008.001.03</MsgDefIdr> xt
published on the ISO 20022
website. E.g. pacs.008.001.03
BusinessService <BizSvc> Business service 6.0 [0..1] [1..1] Comprises a fixed value of “RTGS”, <BizSvc>RTGS</BizSvc> Max35Te
and in the case of BAH for pacs.008 xt
and pacs.009 the fixed value of
“RTGS” must be followed by the
Reserve Bank of India
ISO Message, “head.001.001.01 BusinessApplicationHeaderV01”
2
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
head.001.001.01 Multi /NEFT
BusinessApplicationHe Multi
aderV01
Message Item
local instrument name, i.e. for
RTGS, BAH for pacs.008:
‘RTGSFIToFICustomerCredit’.
For RTGS, BAH for pacs.009:
-‘RTGSFIToFICredit’ or
-‘RTGSOwnAccTtransfer’ or
-‘RTGSNetSettlementXXzNN’

Where ‘XX’ is the clearing type

which may take values ‘GC’, ‘IB’,
‘FX’, MC, SE, OT & so on.

‘z’ is the indicator which may take

values C –Original, R-Return, L-Last
Return.
“NN” is the return serial.

“GC” stands for guaranteed

settlement of Securities and CBLO
segment.

"IB" stands for guaranteed

settlement of FOREX segment.

"FX" stands for non guaranteed

settlement.
“MC” Stands for MICR Clearing
“SE” stands for non-guaranteed
MNSB

“OT” stands for Other MNSB

Reserve Bank of India

ISO Message, “head.001.001.01 BusinessApplicationHeaderV01”
3
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
head.001.001.01 Multi /NEFT
BusinessApplicationHe Multi
aderV01
Message Item
CreationDate <CreDt> Date and time 7.0 [1..1] [1..1] Time up to seconds only <CreDt>2012-09-30T09:50Z</CreDt> ISONorm
when this alisedDat
Business eTime
Message (header)
was created.
CopyDuplicate <CpyDplct> Indicates 8.0 [0..1] [0..1] DUPL Duplicate(Message is for <CpyDplct>DUPL</CpyDplct> Code
whether the information/ confirmation
message is a purposes. It is a duplicate of a
Copy, a Duplicate message previously sent).
or a copy of a Valid Values are:
duplicate of a CODU
previously sent COPY
ISO DUPL
20022 Message.
Signature <Sgntr> Contains the 11.0 [0..1] [0..1] Optional (possibly future use)
digital signature XML digital signature
of the Business http://www.w3.org/2000/09/xml
Entity
dsig#
authorised to
sign this The Sgntr block contains the
Business following elements.
Message XML Tag
Message. item
XMLSigna <XML Sgntrs>
tures
Related <Rltd> Specifies the 12.0 [0..1] [0..1]
Business
Application
Header of the
Business
Message to
which this
Business

Reserve Bank of India

ISO Message, “head.001.001.01 BusinessApplicationHeaderV01”
4
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
head.001.001.01 Multi /NEFT
BusinessApplicationHe Multi
aderV01
Message Item
Message
relates.
Can be used
when replying to
a query; can also
be used when
canceling or
amending.
From <Fr> Element 12.2 [1..1] [1..1] Content is identical to
description is corresponding element content
same as that found in BAH of the message to
provided for the which this BAH (and the business
same element message) is in response to.
above.
This message
item is the part
of the Rltd
block.
To <To> -As Above- 12.53 [1..1] [1..1] -As Above-
BusinessMessageIden <BizMsgIdr> -As Above- 12.104 [1..1] [1..1] -As Above- Max35Te
tifier xt
MessageDefinitionIde <MsgDefIdr> -As Above- 12.105 [1..1] [1..1] -As Above- Max35Te
ntifier xt
Business Service <BizSvc> -As Above- 12.106 [0..1] [0..1] -As Above- Max35Te
xt
CreationDate <CreDt> -As Above- 12.107 [1..1] [1..1] -As Above- ISONorm
alisedDat
eTime
CopyDuplicate <CpyDplct> -As Above- 12.108 [0..1] [0..1] -As Above- Code

Reserve Bank of India

ISO Message, “head.001.001.01 BusinessApplicationHeaderV01”
5
 ISO20022 standard Message Implementation
Customer Credit Transfer
ISO Message: “pacs.008.001.03 FIToFICustomerCreditTransferV03” *

Applicable Areas: RTGS and NEFT

i) For defining Customer Transaction Messages in RTGS
(ii) For defining Outward Debit Message in NEFT
(iii) For Defining Credit List message in NEFT originating from RBI

This message formats would replace the current R41 used in current RTGS.
*Corresponds to R41 in current RTGS, N06 and N02 in NEFT.

The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business
application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain
the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business
message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 1|Page
 ISO20022 standard Message Implementation
ISO 20022 Message
Map ISO20022 Message - XML tag Description Index ISO RTGS/ Rules Example Data Type
ping FIToFICustomerCre Multi NEFT
ditTransferV03 Multi
Message Item
FIToFICustomerCred <FIToFICstmr Message Root
itTransfer CdtTrf> tag for
FIToFICustomer
CreditTransfer
GroupHeader <GrpHdr> Fields common 1.0 [1..1] [1..1]
to all the
transaction in
the message
MessageIdentificati <MsgId> Point to point 1.1 [1..1] [1..1] Uniquely identifies message <MsgId> Max35Text
on reference, as HDFC201210181000000218</
assigned by the Recommend MsgId>
account MessageIdentification be
servicing
GROUP HEADER - GROUP HEADER

structured as:
institution, and
Message Identification

sent to the XXXX- Sender IFSC [4]

account owner
YYYYMMDD - Creation Date
or the party
Reverse [8]
authorised to
receive the X – Channel [1]
message, to nnnnnnnnn- Sequence Number
unambiguously [9]
identify the
message. The values of Channel
Identification (X) is the same as
defined for
TransactionIdentification
<TxId>
CreationDateTime <CreDtTm> Payment 1.2 [1..1] [1..1] Time up to seconds only <CreDtTm>2011-04- ISODateTime
Creation Date &

origination date 24T09:30:32</CreDtTm>

Time

time

Date and time at

which the
Reserve Bank of India
ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 2|Page
 ISO20022 standard Message Implementation
message was
created.
NumberOfTransacti <NbOfTxs> Number of 1.4 [1..1] [1..1] Always 1 for customer payment <NbOfTxs>1</NbOfTxs> Max15Numer
No. of
Txs.

ons transaction in RTGS system and 10 or more icText

for NEFT
TotalInterbankSettl <TtlIntrBkSttl Total 1.6 [0..1] [1..1] Total amount transferred <TtlIntrBkSttlmAmt Amount
ementAmount mAmt> Settlement between debtor and creditor Ccy='INR'>3400.00</TtlIntrBk
Amount + SttlmAmt>
Currency
Currency as per the ISO 4217
list

InterbankSettlemen <IntrBkSttlm Settlement Date 1.7 [0..1] [1..1] Settlement date <IntrBkSttlmDt>2011-04- ISO date
tDate Dt> 24</IntrBkSttlmDt>
SettlementInformat <SttlmInf> Details on how 1.8 [1..1] [1..1]
ion settlement of
Settlement Information

transaction
happens
SettlementMethod <SttlmMtd> Method used to [1..1] [1..1] Must be CLRG (i.e., Settlement <SttlmMtd>CLRG</SttlmMtd> Code
Settlement

settle payments done through a payment

clearing system)

Other Codes are:

CLRG, COVE, INDA, INGA
InstructingAgent <InstgAgt> Agent that 1.21 [0..1] [1..1] Mandatory in RTGS
instructs the implementation
next party in
the chain to
carry out the
(set of)
instruction(s).
FinancialInstitutionI <FinInstnId> [1..1] [1..1]
dentification

ClearingSystemMe <ClrSysMmbI [0..1] [1..1]

mberIdentification d>

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 3|Page
 ISO20022 standard Message Implementation
Member <MmbId> IFSC of the [1..1] [1..1] Sender IFSC <InstgAgt><FinInstnId><ClrSys Max35Text
Identification Sending MmbId><MmbId>HDFC02397
participant 77</MmbId></ClrSysMmbId>
</FinInstnId></InstgAgt>
InstructedAgent <InstdAgt> Agent that is 1.22 [0..1] [1..1] Mandatory in RTGS
instructed by the implementation
previous party
in the chain to
carry out the
(set of)
instruction(s).
FinancialInstitutionI <FinInstnId> [1..1] [1..1]
dentification
ClearingSystemMe <ClrSysMmbI [0..1] [1..1]
mberIdentification d>
Member <MmbId> IFSC of the [1..1] [1..1] Receiver IFSC <InstdAgt><FinInstnId><ClrSys Max35Text
Identification Receiving MmbId><MmbId>HDFC02397
participant 77</MmbId></ClrSysMmbId>
</FinInstnId></InstdAgt>
CreditTransferTrans <CdtTrfTxInf Contains 2.0 [1..n [1..1] Only one occurrence allowed
IN F O R

actionInformation > information on ] for Customer Payment in RTGS

individual system and 10 or more for
Payment Identification

transactions NEFT.
CREDIT TRANSFER

PaymentIdentificati <PmtId> Contains 2.1 [1..1] [1..1]

MATION

on references to a
payment

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 4|Page
 ISO20022 standard Message Implementation
EndToEndIdentificat <EndToEndId End to End 2.3 [1..1] [1..1] Unique identification, as <EndToEndId>TREF23121354 Max35Text
ion > Identification assigned by the bank’s 65781</EndToEndId>
customer, to unambiguously
(Related identify the transaction. This
Reference ) identification is passed on,
unchanged, throughout the
entire end-to-end chain to the
beneficiary.

For MT101, this field

corresponds to field 21( Related
Reference)

For MT103 this field

corresponds to field 70
(Remittance Information) with
codeword ROC (Ordering
customer's reference). If field
70 does not carry this optional
reference, then field 20
(Sender's Reference) should be
used.

For MT202 COV, this field

corresponds to field 21(Related
Reference).

If not known a fixed value of

‘NOTPROVIDED’ must be used.

As per the description, it should

be unique transaction reference
to identify the transaction.
TransactionIdentific <TxId> Transaction 2.4 [1..1] [1..1] Use UTR (Unique Transaction <TxId> Max35Text
ation Identification Reference) format (22 HDFCR12012042400000023</
characters) TxId>
XXXX- Sender IFSC [4]
Reserve Bank of India
ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 5|Page
 ISO20022 standard Message Implementation
X-Payment System [1] In FAQ Channels are
X-Channel [1] mentioned as ATM, Internet
YYYYMMDD-Date [8] banking etc.,
nnnnnnnn- Sequence Number Codes for Payment System (X)
[8] are:
R->RTGS
Unique identification, as N->NEFT
assigned by the first instructing A-> ACH
agent, to unambiguously
identify the transaction For Further Information on
that is passed on, unchanged, Channel, pl refer to FAQ on
throughout the entire interbank Channel.
chain.

Usage: The transaction

identification can be used for
reconciliation, tracking or to
link tasks relating to the
transaction on the interbank
level.
Usage: The instructing agent
has to make sure that the
transaction identification is
unique for a pre-agreed
period.
PaymentTypeInfor <PmtTpInf> Payment 2.6 [0..1] [1..1] Priority is mandatory in RTGS
mation Information implementation
InstructionPriority <InstrPrty> Instruction 2.7 [0..1] [1..1] HIGH / NORM <InstrPrty>HIGH</InstrPrty> Code
Payment Information

Priority
Indicator of the urgency or
order of importance that the
instructing party would like the
instructed party to apply to the
processing of the instruction at
application level. Priority
“NORM” will result in liquidity
Savings.
Reserve Bank of India
ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 6|Page
 ISO20022 standard Message Implementation
HIGH: Priority Level is high.
NORM: Priority Level is normal
Default is HIGH.
ServiceLevel <SvcLvl> Service level 2.9 [0..1] [0..1] Agreement under which or
rules under which the
transaction should be
processed.
Proprietary <Prtry> Proprietary 2.11 [0..1] [1..1] For RTGS processing priority is <Prtry>80</Prtry> Max35Text
Service Level in range 00 – 99. (For RTGS
Code lower the
To be used for managing number
queues by sending bank before highest will
settlement. be the
priority.
For Banks
priority range
is from 11 to
99. Priority
from 00 to 10
is reserved
for RBI.
LocalInstrument <LclInstrm> Local 2.12 [0..1] [1..1]
instrument type

(User
community
specific
instrument.)
Proprietary <Prtry> Proprietary 2.13 [0..1] [1..1] Type of local instrument. <Prtry> FIToFICustomerCredit Max35Text
instrument type For RTGS pacs.008 use: </Prtry>
code - ‘FIToFICustomerCredit’

CategoryPurpose <CtgyPurp> Purpose of the 2.15 [0..1] [1..1]

Instrument.
Payment
purpose must
be a value listed
Reserve Bank of India
ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 7|Page
 ISO20022 standard Message Implementation
in ISO category
purpose code
Code <Cd> ISO External 2.16 [1..1] [1..1] FROM ISO 20022External Code <Cd>OTHR</Cd> Code
category list
purpose code (Max4Text)
list. Codes are The following codes are
"SALA - available.
SalaryPayment, CASH:
Loan-Loan, CashManagementTransfer
PENS- CORT: TradeSettlementPayment
PensionPaymen DIVI: Dividend
t, etc. Details in GOVT: GovernmentPayment
3.55 of UNIFI HEDG: Hedging
(ISO20022) Msg INTC: IntraCompanyPayment
Definition Rpt. INTE: Interest
LOAN: Loan
PENS: PensionPayment
SALA: SalaryPayment
SECU: Securities
SSBE: SocialSecurityBenefit
SUPP: SupplierPayment
TAXS: TaxPayment
TRAD: Trade
TREA: TreasuryPayment
VATX:
ValueAddedTaxPayment
WHLD: WithHolding
OTHR: Other

The generic code for the normal

funds transfer may be 'OTHR'.
This code will be the default
purpose code which stands for
"Other Payment Purpose".
Example:
<CtgyPurp><Cd>OTHR</Cd>
</CtgyPurp>

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 8|Page
 ISO20022 standard Message Implementation
For additional codes, please
refer to document
ExternalcodeLists_3Q2012_22
Oct2012_v4.xls available at
www.iso20222.org

Banks to suggest additional

India Specific codes .
InterbankSettlemen <IntrBkSttlm Settlement 2.18 [1..1] [1..1] Amount transferred between <IntrBkSttlmAmt Amount
Interbank Settlement

tAmount Amt> Amount + debtor and creditor Ccy='INR'>3400.00</IntrBkSttl

Currency mAmt>
Amt

ChargeBearer <ChrgBr> Code 2.33 [1..1] [1..1] Codes & meanings are: <ChrgBr>DEBT</ChrgBr> Code
Charge Bearer

=CRED/DEBT/SH DEBT -> BorneByDebtor

AR/SLEV CRED-> BorneByCreditor
SHAR-> Shared
SLEV-> FollowingServiceLevel
ChargesInformation <ChrgsInf> 2.34 [0..*] [0..1] If ChargeBearer contains DEBT,
then ChargesInformation may
be present
If ChargeBearer contains CRED,
then at least one occurrence of
Charges Information

ChargesInformation must be
present
If ChargeBearer contains SHAR
or SLEV, then
ChargesInformation is optional.
Amount <Amt> Transaction 2.35 [1..1] [1..1] <Amt Amount
charges to be Ccy='IND'>5000.00</Amt>
paid by the
charge bearer.

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 9|Page
 ISO20022 standard Message Implementation
Agent <Agt> 2.36 [1..1] [1..1] Agent that takes the
transaction charges or to which
the transaction charges are
due.
FinancialInstitution <FinInstnId> [1..1] [1..1]
Identification
ClearingSystemMe <ClrSysMmbI [0..1] [1..1]
mberIdentification d>
Member <MmbId> [1..1] [1..1] Max35Text
Identification
Debtor <Dbtr> ORDERING 2.49 [1..1] [1..1]
CUSTOMER
Debtor (Ordering Customer)

Name <Nm> Ordering [0..1] [1..1] Name is mandatory <Nm>Umesh Kapoor</Nm> Max140Text
Customer’s
Name
PostalAddress <PstlAdr> Ordering [0..1] [0..1]
Customer’s
Postal Address
AddressLine <AdrLine> Adress in free [0..7] [0..4] Number of occurrences is <AdrLine>Boulevard Max70Text
form text restricted to 4 in RTGS Road</AdrLine>
implementation.
DebtorAccount <DbtrAcct> Identification of 2.50 [0..1] [1..1]
Debtor's A/c (Ordering Customer's

the account of
the debtor to
which a debit
entry will be
made as a result
A/C)

of the
transaction.
Identification <Id> [1..1] [1..1]
Other <Othr> [1..1] [1..1]
Identification <Id> Debtor's [1..1] [1..1] <Id>265385644663</Id> Max35Text
Account
number
(ORD
Agen

INSTI

DebtorAgent <DbtrAgt> ORDERING 2.51 [1..1] [1..1] Pl see FAQ for more details on
Debt

ERIN

TUTI
ON)
or's

G
t

INSTITUTION DebtorAgent
Reserve Bank of India
ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 10 | P a g e
 ISO20022 standard Message Implementation
(Financial (i.e Sub-Member)
institution For Participant, IFSC
servicing an
account for the
debtor.)
FinancialInstitutionI <FinInstnId> [1..1] [1..1]
dentification
ClearingSystemIden <ClrSysMmbI ClearingSystemI 2.1.6 [0..1] [1..1]
tification d> dentification
Member <MmbID> IndianFinancialS 2.1.6 [1..1] [1..1] For Participant, IFSC code to be <DbtrAgt><FinInstnId><ClrSys
Identification ystemCodeIden keyed in. For Non- Participant, MmbId><MmbId>HDFC02397
tifier for IFSC, or Name and Other 77</MmbId>></ClrSysMmbId
participants / Identification with optional ></FinInstnId></DbtrAgt>
Name and Address.
Identification
for non
Participants is
mandatory
Name <Nm> Ordering [0..1] [0..1] Optional. To be filled if <Nm>Bank A</Nm> Max140Text
Institution Ordering Customer is other
Name than the Sender of the msg.
PostalAddress <PstlAdr> Ordering [0..1] [0..1]
Institution
Postal Address
AddressLine <AdrLine> Address in free [0..7] [0..4] Number of occurrences is <AdrLine>Corn Exchange 5th Max70Text
format text restricted to 4 in RTGS Floor</AdrLine>
implementation <AdrLine>Mark Lane
55</AdrLine>
<AdrLine>EC3R7NE
London</AdrLine>
<AdrLine>GB</AdrLine>
CreditorAgent <CdtrAgt> Beneficiary 2.53 [1..1] [1..1]
Creditor's Agent
(BENEFICIARY
INSTITUTION)

Institution
identification
FinancialInstitutionI <FinInstnId> [1..1] [1..1]
dentification
ClearingSystemMe <ClrSysMmbI ClearingSystemI 3.37 [0..1] [1..1]
Reserve Bank of India
ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 11 | P a g e
 ISO20022 standard Message Implementation
mberIdentification d> dentification
Member <MmbId> IndianFinancialS [1..1] [1..1] For Participant, IFSC code to be <CdtrAgt><FinInstnId><ClrSys Text
Identification ystemCodeIden keyed in. For Non- Participant MmbId><MmbId>HDFC02397
tifier (i.e. Participant who do not 77</MmbId></ClrSysMmbId>
have IFSC code), Name and <</FinInstnId></CdtrAgt>
Other Identification to be keyed
in..
Name <Nm> Beneficiary [0..1] [0..1] <Nm>Bank B</Nm> Max140Text
Institution
Name
Creditor <Cdtr> Beneficiary 2.55 [1..1] [1..1]
Customer
Creditor (BENEFICIARY

Information
Name <Nm> Beneficiary [0..1] [1..1] Mandatory in view of Indian <Nm>Beneficiary</Nm> Max70Text
CUSTOMER)

Customer Context (Ref. Circular issued by

Name RBI)
PostalAddress <PstlAdr> Beneficiary [0..1] [0..1] Optional Field. Enter
Customer's Beneficiary customer Address if
Postal Address reqd.
AddressLine <AdrLine> Adress in free [0..7] [0..4] Number of occurrence is <AdrLine>Boulevard Max70Text
form text restricted to 4. Road</AdrLine>
CreditorAccount <CdtrAcct> Beneficiary 2.56 [0..1] [1..1] Mandatory in RTGS
Institution implementation
Creditor's A/c (BENEFICIARY

identification
Identification <Id> [1..1] [1..1]
CUSTOMER's A/C)

Other <Othr> ClearingSystemI [1..1] [1..1]

dentification
Identification <Id> IndianFinancialS [1..1] [1..1] Existing account number <Id>2147743292</Id> Max35Text
ystemCodeIden
tifier
Currency <Ccy> Identification of [0..1] [0..1] For NG-RTGS, “INR” is the only <Ccy>INR</Ccy> Code
the currency in currency that can be specified.
which account
is held

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 12 | P a g e
 ISO20022 standard Message Implementation
InstructionForCredit <InstrForCdtr Beneficiary 2.58 [0..n] [0..2]
Instruction For Creditor Agent

orAgent Agt> Customer

Information
Code <Cd> Coded 2.59 [0..1] [0..1] PHOB = Phone Beneficiary <Cd>PHOB</Cd> Max4Text
information Pl see FAQ for other Codes
related to the
processing of
the payment
instrument,
provided by the
initiating party.
RemittanceInforma <RmtInf> Beneficiary 2.69 [0..1] [0..1]
Beneficiary Information

tion Customer's
Postal Address
Unstructured <Ustrd> Remittance 2.69 [0..n] [0..4] Size restricted to a maximum of Max140Text
Information 140 4 repeats of 140 characters.
characters up to
4 can be used
Sender to
Receiver
Information

Note:- [1..1] -> Mandatory; [0..1] -> Optional ; [1..n] -> Mandatory and n times repeated ; [0..n] -> Optional and n times repeated;

Reserve Bank of India

ISO 20022 Message, “pacs.008.001.03 FIToFICustomerCreditTransferV03” 13 | P a g e
 ISO20022 standard Message Implementation
Customer Debit Credit Notification
ISO Message “camt.054.001.003 BankToCustomerDebitCreditNotificationV03”
Applicable Areas: RTGS & NEFT
1. For defining Debit Notification in MNSB (RTGS)
2. For defining Credit Notification in MNSB (RTGS)

The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business
application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain
the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business
message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

ISO 20022 Message

Reserve Bank of India 1|Page

ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
camt.054.001.03 Multi /NEFT
BankToCustomerDebitCredit Multi
NotificationV03
Message Item
<BkToCstmrDbtC Root tag [1..1] [1..1]
dtNtfctn>
GroupHeader <GrpHdr> Fields common to all 1.0 [1..1] [1..1]
the transaction in the
message
MessageIdentification <MsgId> Uniquely identifies 1.1 [1..1] [1..1] Uniquely identifies message <MsgId> Max35Text
the message HDFC201210181000000218</MsgId>
Recommend MessageIdentification be
structured as:

XXXX- Sender IFSC [4]

YYYYMMDD - Creation Date Reverse [8]
X – Channel [1]
nnnnnnnnn- Sequence Number
[9]

The values of Channel Identification

(X) is the same as defined for
TransactionIdentification <TxId>
CreationDateTime <CreDtTm> Payment origination 1.2 [1..1] [1..1] Time upto seconds only <CreDtTm>2011-04-24T09:30:32</CreDtTm> ISODateTim
date time e
Notification <Ntfctn> Notifies debit and 2.0 [1..n] [1..1] or Occurs once in RTGS, but [1..10] in NEFT
credit entries for [1..10]
the account.
This msg element is
the part of the
Ntfctn block.
Identification <Id> Unique 2.1 [1..1] [1..1] <Id>EODZERO</Id> Max35Text
identification, as
assigned by the
account servicer, to
unambiguously
identify the account
notification.
CreationDateTime <CreDtTm> Date and time at 2.5 [1..1] [1..1] <CreDtTm>2011-04-24T07:30:32</CreDtTm> ISODateTim
which the message e
was created.
This msg element is
the part of the
Reserve Bank of India 2|Page
ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
camt.054.001.03 Multi /NEFT
BankToCustomerDebitCredit Multi
NotificationV03
Message Item
Ntfctn block.
Account <Acct> Unambiguous 2.11 [1..1] [1..1]
identification of the
account to which
credit and debit
entries are made.
This msg element is
the part of the
Ntfctn block.
Identification <Id> [1..1] [1..1]
Other <Othr> [1..1] [1..1]
Identification <Id> Settlement account [1..1] [1..1] <Acct><Id><Othr><Id>353565651234</Id></ Max35Text
number Othr></Id></Acct>
Entry <Ntry> Set of elements 2.45 [0..n] [1..1]
used to specify an
entry in the debit
credit notification.
This msg element is
the part of the
Ntfctn block.
Amount <Amt> Amount and currency [1..1] [1..1] <Amt Ccy="INR">10000.00</Amt> Amount
This msg element is
the part of the Ntry
block.
CreditDebitIndicator <CdtDbtInd> Indicates whether [1..1] [1..1] Codes to be used are: <CdtDbtInd>DBIT</CdtDbtInd> Code
the total net entry CRDT: Credit -> Operation is an increase
amount is a credit DBIT: Debit -> Operation is an decrease
or a debit amount.
Usage: A zero
balance is
considered to be a
credit balance.
This msg element is
the part of the Ntry
block.
Status <Sts> Status of an entry [1..1] [1..1] Always BOOK meaning booked amount. <Sts>BOOK</Sts> Code
on the books of the Status Booked is the only status that

Reserve Bank of India 3|Page

ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
camt.054.001.03 Multi /NEFT
BankToCustomerDebitCredit Multi
NotificationV03
Message Item
account service.r can be reversed.
Code for status Others Code for status are:
BOOK/INFO/PDNG/F BOOK/INFO/PDNG/FUTR
UTR For more details pl refer para 2.81 of
This msg element is ISO documentation “Payment
the part of the Ntry
Maintenance 2009.pdf”.
block.
ValueDate <ValDt> This msg element [0..1] [1..1]
is the part of the
Ntry block.
<ValDt><DtTm>2010-10-
DateTime <DtTm> Value date time [0..1] [1..1] Settlement time 18T13:15:00</DtTm></ValDt> DateTime
Set of elements used
to fully identify the
type of underlying
transaction resulting
in an entry.
This msg element is
the part of the Ntry
BankTransactionCode <BkTxCd> block. [1..1] [1..1]
Bank transaction
code in a proprietary
form, as defined by
Proprietary <Prtry> the issuer. [1..1] [1..1]
Code <Cd> Proprietary bank [1..1] [1..1] <BkTxCd><Prtry><Cd>0001</Cd></Prtry></Bk Max35Text
transaction code to TxCd>
identify the
underlying
transaction.
EntryDetails <NtryDtls> Provides details on [0..n] [1..1]
the entry
This msg element is
the part of the Ntry
block.
TransactionDetails <TxDtls> [0..n] [1..1]
References <Refs> [0..1] [1..1]
EndToEndIdentification <EndToEndId> Transaction reference 2.128 [0..1] [1..1] Unique identification, as assigned <EndToEndId>TREF765628561242 Max35Text
number. </EndToEndId>
by the bank’s customer, to
This msg element is

Reserve Bank of India 4|Page

ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
camt.054.001.03 Multi /NEFT
BankToCustomerDebitCredit Multi
NotificationV03
Message Item
the part of the Refs unambiguously identify the
block.
transaction. This identification is
passed on, unchanged, throughout
the entire end-to-end chain to the
beneficiary.
For MT101, this field corresponds
to field 21( Related Reference)

For MT103 this field corresponds to

field 70 (Remittance Information)
with codeword ROC (Ordering
customer's reference). If field 70
does not carry this optional
reference, then field 20 (Sender's
Reference) should be used.

For MT202 COV, this field

corresponds to field 21(Related
Reference).
TransactionIdentification <TxId> Related reference 2.129 [0..1] [1..1] Use UTR (Unique Transaction <TxId> Max35Text
number.
Reference) format (22 characters) HDFCR12012042400000023</TxId>
This msg element is
the part of the Refs XXXX- Sender IFSC [4]
block. X-Payment System [1] For Further Information, pl refer to
X-Channel [1] FAQ on Channel.
YYYYMMDD-Date [8]
nnnnnnnn- Sequence Number [8]

Unique identification, as assigned

by the first instructing agent, to
unambiguously identify the
transaction
that is passed on, unchanged,
Reserve Bank of India 5|Page
ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
camt.054.001.03 Multi /NEFT
BankToCustomerDebitCredit Multi
NotificationV03
Message Item
throughout the entire interbank
chain.

Usage: The transaction

identification can be used for
reconciliation, tracking or to link
tasks relating to the
transaction on the interbank level.
Usage: The instructing agent has to
make sure that the transaction
identification is unique for a pre-
agreed

Amount <Amt> Transaction amount [1..1] [1..1] <Amt Ccy="INR">10000.00</Amt> Amount

This msg element is
the part of the
TxDtls block.
CreditDebitIndicator <CdtDbtInd> Indicates whether 2.59 [1..1] [1..1] Codes are DBIT & CRDT. <CdtDbtInd>DBIT</CdtDbtInd> CreditDebit
the transaction is a Code
credit or a debit Codes Meanings
transaction. DBIT Debit
This msg element is CRDT Credit
the part of the
TxDtls block.
RelatedParties <RltdPties> Set of elements used 2.179 [0..1] [1..1]
to identify the parties
related to the
underlying
transaction.
This msg element is
the part of the
TxDtls block.
Debtor <Dbtr> IFSC of the participant 2.184 [0..1] [1..1] Must reflect the pacs.008 and pacs.009
which caused the structure for BOTH Debtor and Creditor
credit
Identification <Id> Identification [0..1] [1..1]

Reserve Bank of India 6|Page

ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
camt.054.001.03 Multi /NEFT
BankToCustomerDebitCredit Multi
NotificationV03
Message Item
OrganisationIdentification <OrgId> organization [1..1] [1..1]
identifier
Other <Othr> [0..n] [1..1]
Identification <Id> ifsc [1..1] [1..1] <RltdPties><Dbtr><Id><OrgId><Othr><Id>CAN Max35Text
B0239777</Id></Othr></OrgId></Id></Dbtr>
</RltdPties>
Purpose <Purp> Underlying reason for [0..1] [0..1] Usage: Purpose is used by the end-
the payment customers, that is initiating party, (ultimate)
transaction. debtor, (ultimate) creditor to provide
This msg element is information concerning the nature of the
the part of the TxDtls payment.
block.
Proprietary <Prtry> Purpose, in a [1..1] [1..1] Code values are: REPO or REVREPO Max35Text
proprietary form.
RemittanceInformation <RmtInf> Remittance 2.214 [0..1] [0..1]
Information.
This msg element is
the part of the
TxDtls block.
Unstructured <Ustrd> Remittance 2.215 [0..n] [1..4] Size restricted to a maximum of 4 repeats of Max140Text
Information 140 140 characters.
characters up to 4
can be used
Sender to Receiver
Information
Note:- [1..1] -> Mandatory; [1..0] -> Optional ; [1..n] -> Mandatory and n times repeated ; [0..n] -> Optional and n times repeated

Reserve Bank of India 7|Page

ISO Messages, “camt.054.001.03 BanktoCustomerDebitCreditNotificationV03”
 ISO20022 standard Message Implementation
Interbank Transfer
ISO Message: “pacs.009.001.03 - FinancialInstitutionCreditTransferV03” *

Applicable Areas: RTGS

1) For defining Interbank message in RTGS. The same is not applicable to NEFT as there is no concept of Interbank in NEFT.

This message formats would replace the current R42 used in current RTGS.
*Corresponds to R42 in current RTGS.
The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business
application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain
the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business
message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

Reserve Bank of India 1|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation

ISO 20022 Message

Map ISO20022 Message XML tag Description Index ISO RTGS Rules Example Data Type
ping - pacs.009.001.03- Multi Multi
FinancialInstitution
CreditTransferV03
Message Item
FinancialInstitution <FinInstn Root tag
CreditTransfer CdtTrf>
GroupHeader <GrpHdr Fields common to 1.0 [1..1] [1..1]
> all the transaction
in the message
MessageIdentificati <MsgId> Uniquely identifies 1.1 [1..1] [1..1] Uniquely identifies message <MsgId> Max35T
on the message HDFC201210181000000218</MsgI ext
GROUP HEADER - GROUP HEADER

Recommend MessageIdentification d>

be structured as:
Message Identification

XXXX- Sender IFSC [4]

YYYYMMDD - Creation Date Reverse
[8]
X – Channel [1]
nnnnnnnnnn- Sequence Number
[9]

The values of Channel Identification

(X) is the same as defined for
TransactionIdentification <TxId>
Creation Date &

CreationDateTime <CreDtT Payment 1.2 [1..1] [1..1] Time up to seconds only <CreDtTm>2011-04- ISODateT
m> origination date 24T09:30:32</CreDtTm> ime
Time

time

Reserve Bank of India 2|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
NumberOfTransacti <NbOfTx Number of 1.4 [1..1] 1..1] Always 1 for Interbank payment in <NbOfTxs>1</NbOfTxs> Max15N
No. of Txs.

ons s> transactions RTGS umericTe

xt

TotalInterbankSettl <TtlIntrB Total Settlement 1.6 [0..1] [1..1] Total amount transferred between <TtlIntrBkSttlmAmt Amount
ementAmount kSttlmA Amount + debtor and creditor. Ccy='INR'>3400</TtlIntrBkSttlmAmt
mt> Currency >

InterbankSettleme <IntrBkSt Settlement Date 1.7 [0..1] [1..1] <IntrBkSttlmDt>2011-04- ISO date
ntDate tlmDt> 24</IntrBkSttlmDt>
SettlementInformat <SttlmInf Details on how 1.8 [1..1] [1..1]
ion > settlement of
transaction
happens
Settlement Information

SettlementMethod <SttlmMt Method used to 1.9 [1..1] [1..1] Must be CLRG (i.e., Settlement <SttlmMtd>CLRG</SttlmMtd> Code
d> settle payments done through a payment clearing
system)

Other Codes are:

CLRG, COVE, INDA, INGA
InstructingAgent <InstgAg Agent that 1.21 [0..1] [1..1]
t> instructs the next
party in the chain
to carry out the
(set of)
instruction(s).
FinancialInstitutionI <FinInstn [1..1] [1..1]
dentification Id>
ClearingSystemMe <ClrSysM [0..1] [1..1]
mberIdentification mbId>
Member <MmbId IFSC of the [1..1] [1..1] Sender IFSC <InstgAgt><FinInstnId><ClrSysMmb Max35Te
Identification > Sending Id><MmbId>HDFC0239777</MmbI xt
participant d></ClrSysMmbId></FinInstnId></I
nstgAgt>

Reserve Bank of India 3|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
InstructedAgent <InstdAg Agent that is 1.22 [0..1] [1..1] Mandatory in RTGS implementation
t> instructed by the
previous party in
the chain to carry
out the (set of)
instruction(s).
FinancialInstitutionI <FinInstn [1..1] [1..1]
dentification Id>
ClearingSystemMe <ClrSysM [0..1] [1..1]
mberIdentification mbId>
Member <MmbId> IFSC of the [1..1] [1..1] Receiver IFSC <InstdAgt><FinInstnId><ClrSysMmb Max35Te
Identification Receiving Id><MmbId>HDFC0239777</MmbI xt
participant d></ClrSysMmbId></FinInstnId></I
nstdAgt>
CreditTransferTran <CdtTrfT Contains 2.0 [1..n] [1..1] Only one occurrence allowed for
sactionInformation xInf> information on Interbank Payment
individual
transactions
PaymentIdentificat <PmtId> Contains 2.1 [1..1] [1..1]
CREDIT TRANSFER INFORMATION

ion references to a
payment
EndToEndIdentifica <EndToE End to End 2.3 [1..1] [1..1] For FI Credit Transfer (pacs.009), <EndToEndId>TREF2312135465781 Max35Te
tion ndId> Identification this must be the same value as </EndToEndId> xt
Payment Identification

(Related TransactionIdentification.
Reference)
TransactionIdentific <TxId> Transaction 2.4 [1..1] [1..1] Use UTR (Unique Transaction <TxId> Max35Te
ation Identification Reference) format (22 characters) HDFCR12012042400000023</TxId> xt
XXXX- Sender IFSC [4]
X-Payment System [1] For Further Information, pl refer to
X-Channel [1] FAQ on Channel.
YYYYMMDD-Date [8]
nnnnnnnn- Sequence Number [8]

Unique identification, as assigned

by the first instructing agent, to
Reserve Bank of India 4|Page
ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
unambiguously identify the
transaction
that is passed on, unchanged,
throughout the entire interbank
chain.

Usage: The transaction

identification can be used for
reconciliation, tracking or to link
tasks relating to the
transaction on the interbank level.
Usage: The instructing agent has to
make sure that the transaction
identification is unique for a pre-
agreed
period.
PaymentTypeInfor <PmtTpI Payment 2.6 [0..1] [1..1] Priority is mandatory in RTGS
mation nf> Information implementation
Payment

InstructionPriority <InstrPrt Priority 2.7 [0..1] [1..1] HIGH / NORM <InstrPrty>NORM</InstrPrty> Code
y>
Indicator of the urgency or order of
importance that the instructing
Payment Information

party would like the instructed

Information

party to apply to the processing of

the instruction at application level.
Priority “NORM” will result in
Payment Information

liquidity Savings.

HIGH: Priority Level is high.

NORM: Priority Level is normal.
ServiceLevel <SvcLvl> Service level 2.9 [0..1] [0..1] Agreement under which or rules
under which the transaction should
be processed.

Reserve Bank of India 5|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
Proprietary <Prtry> Proprietary 2.11 [0..1] [1..1] For RTGS used to indicate RTGS <Prtry>80</Prtry> Max35Te
Service Level Code processing priority in range 00– 99. xt

To be used for managing queues by

sending bank before settlement.
LocalInstrument <LclInstr Local instrument 2.12 [0..1] [1..1]
m> type

(User community
specific
instrument.)
Proprietary <Prtry> Proprietary 2.13 [0..1] [1..1] Type of local instrument. <Prtry> FIToFICredit </Prtry> Max35Te
instrument type For RTGS, pacs.009 use: xt
code - ‘FIToFICredit’
CategoryPurpose <CtgyPur Purpose of the 2.15 [0..1] [1..1]
p> Instrument.
Payment purpose
must be a value
listed in ISO
category purpose
code
Code <Cd> ISO External 2.16 [1..1] [1..1] FROM ISO 20022External Code list <Cd>SALA</Cd> Code
category purpose
code list. Codes The following codes are available. (Max4Te
are "SALA - CASH: CashManagementTransfer xt)
SalaryPayment, CORT: TradeSettlementPayment
Loan-Loan, PENS- DIVI: Dividend
PensionPayment, GOVT: GovernmentPayment
etc. Details in 3.55 HEDG: Hedging
of UNIFI INTC: IntraCompanyPayment
(ISO20022) Msg INTE: Interest
Definition Rpt. LOAN: Loan
PENS: PensionPayment
SALA: SalaryPayment
SECU: Securities
SSBE: SocialSecurityBenefit
Reserve Bank of India 6|Page
ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
SUPP: SupplierPayment
TAXS: TaxPayment
TRAD: Trade
TREA: TreasuryPayment
VATX: ValueAddedTaxPayment
WHLD: WithHolding
OTHR: Other

The generic code for the normal

funds transfer may be 'OTHR'. This
code will be the default purpose
code which stands for "Other
Payment Purpose". Example:
<CtgyPurp><Cd>OTHR</Cd></Ct
gyPurp>

For additional codes, please refer to

document
ExternalcodeLists_3Q2012_22Oct
2012_v4.xls available at
www.iso20222.org
Banks to suggest additional India
Specific codes .
Amt
Interbank
Settlement

InterbankSettleme <IntrBkSt Settlement 2.18 [1..1] [1..1] Amount transferred between <IntrBkSttlmAmt Amount
ntAmount tlmAmt> Amount + participants Ccy='INR'>3400</IntrBkSttlmAmt>
Currency
Debtor <Dbtr> ORDERING 2.40 [1..1] [1..1]
INSTITUTION)

INSTITUTION
(ORDERING
Debtor

FinancialInstitutionI <FinInstn [1..1] [1..1]

dentification Id>
ClearingSystemMe <ClrSysM [0..1] [1..1]
mberIdentification mbId>

Reserve Bank of India 7|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
Member <MmbId IndianFinancialSys [1..1] [1..1] <Dbtr><FinInstnId><ClrSysMmbId> Max35Te
Identification > temCodeIdentifier <MmbId>HDFC0239777</MmbId>< xt
for participants / /ClrSysMmbId></FinInstnId></Dbtr
Name and >
Identification for
non Participants is
mandatory
Name <Nm> Ordering [0..1] [0..1] <Nm>Bank A</Nm> Max140T
Institution Name ext
Creditor <Cdtr> Beneficiary 2.46 [1..1] [1..1]
Institution
identification
FinancialInstitutionI <FinInstn [1..1] [1..1]
dentification Id>
Creditor (BENEFICIARY INSTITUTION)

ClearingSystemMe <ClrSysM [0..1] [1..1]

mberIdentification mbId>
Member <MmbId> IndianFinancialSys [1..1] [1..1] <Cdtr><FinInstnId><ClrSysMmbId>< Max35Te
Identification temCodeIdentifier MmbId>HDFC0239777</MmbId></ xt
for participants / ClrSysMmbId></FinInstnId></Cdtr>
Name and
Identification for
non Participants is
mandatory
Name <Nm> Beneficiary [0..1] [0..1] <Nm>Bank b</Nm> Max70Te
Institution Name xt
PostalAddress <PstlAdr> Beneficiary [0..1] [0..1]
Institution Postal
Address
AddressLine <AdrLine> Adress in free [0..7] [0..4] Number of occurrence is restricted <AdrLine>Boulevard Max70Te
form text to 4 Road</AdrLine> xt

Reserve Bank of India 8|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
Other <Othr> used when [0..1] [0..1]
correspondants
are involved

Identification <Id> Identification [1..1] [1..1] Max35Te

assigned by an xt
institution

CreditorAccount <CdtrAcct Beneficiary 2.47 [0..1] [0..1]

> Customer account
identification
Identification <Id> Account number [1..1] [1..1] It must be used for recording <Id>0510085</Id> Max35Te
of Beneficiary account number for the beneficiary xt
bank for STP process.
RemittanceInforma <RmtInf> Remittance 2.55 [0..1] [0..1]
tion Information
Information
Remittance

Unstructured <Ustrd> Remittance 2.56 [0..n] [0..4] Size restricted to a maximum of 4 Max140T
Information 140 repeats of 140 characters. ext
characters up to 4
can be used
Sender to Receiver
Information

Note:- [1..1] -> Mandatory; [0..1] -> Optional ; [1..n] -> Mandatory and n times repeated ; [0..n] -> Optional and n times repeated;

Reserve Bank of India 9|Page

ISO Messages, “pacs.009.001.03 - FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation

Multilateral Net Settlement Batch (MNSB) Request *

ISO message pacs.009.001.03 FinancialInstitutionCreditTransferV03 is used for defining the MNSB request.
If clearing member in debit, the credit leg will have the clearing house identifier and vice versa.

This message formats would replace the current R12 used in current RTGS.
*Corresponds to R12 in current RTGS.

The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business
application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain
the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business
message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

ISO 2002 Message

Reserve Bank of India 1|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
<FinInstnCd Root tag [1..1] [1..1]
tTrf>
GroupHeader <GrpHdr> Fields common to all 1.0 [1..1] [1..1]
the transaction in the
message
MessageIdentification <MsgId> Uniquely identifies 1.1 [1..1] [1..1] Uniquely identifies message <MsgId> Max35Text
the message CCIL201210181000000218</MsgId>
Recommend
MessageIdentification be
structured as:

XXXX- Sender IFSC [4]

YYYYMMDD - Creation Date
Reverse [8]
X – Channel [1]
nnnnnnnnn- Sequence Number
[9]

The values of Channel

Identification (X) is the same as
defined for
TransactionIdentification <TxId>
CreationDateTime <CreDtTm> Payment origination 1.2 [1..1] [1..1] Time upto seconds only <CreDtTm>2011-04-24T09:30:32</CreDtTm> ISODateTime
date time
NumberOfTransaction <NbOfTxs> Number of 1.4 [1..1] [1..1] Equal to number of participants in the <NbOfTxs>3</NbOfTxs> Max15Numeri
s transactions batch cText

TotalInterbankSettlem <TtlIntrBkS Total Settlement 1.6 [0..1] [1..1] Total amount of money moved <TtlIntrBkSttlmAmt Amount
entAmount ttlmAmt> Amount + between the instructing agent and Ccy='INR'>3400.00</TtlIntrBkSttlmAmt>
Currency the instructed agent.
InterbankSettlementD <IntrBkSttl Settlement Date – 1.7 [0..1] [1..1] Value date of payment must be same <IntrBkSttlmDt>2011-04-24</IntrBkSttlmDt> ISODate
ate mDt> will settle only as RTGS date. Mandatory in RTGS
current day implementation

Reserve Bank of India 2|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
SettlementInformation <SttlmInf> Details on how 1.8 [1..1] [1..1]
settlement of
transaction happens
SettlementMethod <SttlmMtd> Method used to 1.9 [1..1] [1..1] Must be CLRG (i.e., Settlement <SttlmMtd>CLRG</SttlmMtd> Code
settle payments done through a payment clearing
system)

Other Codes are:

CLRG, COVE, INDA, INGA
InstructingAgent <InstgAgt> Agent that 1.21 [0..1] [1..1]
instructs the next
party in the chain
to carry out the
(set of)
instruction(s).
FinancialInstitutionId <FinInstnId [1..1] [1..1]
entification >
ClearingSystemMem <ClrSysMm [0..1] [1..1]
berIdentification bId>
Member <MmbId> IFSC of the Sending [1..1] [1..1] Sender IFSC <InstgAgt><FinInstnId><ClrSysMmbId><M Max35Text
Identification participant mbId>CCIL0PI0001</MmbId></ClrSysMm
bId></FinInstnId></InstgAgt>
InstructedAgent <InstdAgt> Agent that is 1.22 [0..1] [1..1]
instructed by the
previous party in
the chain to carry
out the (set of)
instruction(s).
FinancialInstitutionId <FinInstnId [1..1] [1..1]
entification >
ClearingSystemMem <ClrSysMm [0..1] [1..1]
berIdentification bId>

Reserve Bank of India 3|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
Member <MmbId> IFSC of the [1..1] [1..1] Receiver IFSC <InstdAgt><FinInstnId><ClrSysMmbId><M Max35Text
Identification Receiving mbId>RBIS0RTGS00</MmbId></ClrSysMm
participant bId></FinInstnId></InstdAgt>
CreditTransferTransact <CdtTrfTxInf Contains information 2.0 [1..n] [1..n] Multiple occurrence based on number
ionInformation > on individual of participants
transactions
PaymentIdentification <PmtId> Contains references 2.1 [1..1] [1..1]
to a payment
EndToEndIdentification <EndToEndI End to End 2.3 [1..1] [1..1] For FI Credit Transfer (pacs.009), <EndToEndId>TREF2312135465781</EndT Max35Text
d> Identification this must be the same value as oEndId>
(Related Reference) TransactionIdentification.
TransactionIdentificati <TxId> Transaction 2.4 [1..1] [1..1] Use UTR (Unique Transaction <TxId> CCILR12012042400000023</TxId> Max35Text
on Identification Reference) format (22 characters)
XXXX- Sender IFSC [4] For Further Information, pl refer to FAQ
Main clearing
X-Payment System [1] on Channel.
Reference Number
X-Channel [1]
for return clearing
YYYYMMDD-Date [8]
nnnnnnnn- Sequence Number [8]

Unique identification, as assigned

by the first instructing agent, to
unambiguously identify the
transaction
that is passed on, unchanged,
throughout the entire interbank
chain.
Usage: The transaction
identification can be used for
reconciliation, tracking or to link
tasks relating to the
transaction on the interbank level.
Usage: The instructing agent has
to make sure that the transaction
Reserve Bank of India 4|Page
ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
identification is unique for a pre-
agreed
period.
PaymentTypeInformat <PmtTpInf> Payment 2.6 [0..1] [1..1]
ion Information
InstructionPriority <InstrPrty> Priority 2.7 [0..1] [1..1] HIGH / NORM <InstrPrty>NORM</InstrPrty> Code

Indicator of the urgency or order

of importance that the instructing
party would like the instructed
party to apply to the processing of
the instruction at application level.
Priority “NORM” will result in
liquidity Savings.

HIGH: Priority Level is high.

NORM: Priority Level is normal.
ServiceLevel <SvcLvl> Service level 2.9 [0..1] [0..1] Agreement under which or rules
under which the transaction
should be processed.

Proprietary <Prtry> Proprietary Service 2.11 [0..1] [1..1] For RTGS used to indicate RTGS <Prtry>80</Prtry> Max35Text
Level code processing priority in range 0 0–
99.

To be used for managing queues0

by sending bank before
settlement.
LocalInstrument <LclInstrm> Local instrument 2.12 [0..1] [1..1]
type

(User community

Reserve Bank of India 5|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
specific
instrument.)
Proprietary <Prtry> Proprietary 2.13 [0..1] [1..1] Type of local instrument. <Prtry> NetSettlement </Prtry> Max35Text
instrument type For RTGS, pacs.009 use:
code -‘RTGSNetSettlementXXzNN’

Where ‘XX’ is the clearing type

which may take values ‘GC’, ‘IB’,
‘FX’, MC, SE, OT & so on.

‘z’ is the indicator which may take

values C –Original, R-Return, L-Last
Return.

“NN” is the Return serial.

“GC” stands for guaranteed

settlement of Securities and CBLO
segment.

"IB" stands for guaranteed

settlement of FOREX segment.

"FX" stands for non guaranteed

settlement.
“MC” Stands for MICR Clearing.

“SE” stands for non-guaranteed

MNSB

“OT” stands for Other MNSB

InterbankSettlementA <IntrBkSttlm Settlement Amount 2.18 [1..1] [1..1] Settlement amount. <IntrBkSttlmAmt Amount

Reserve Bank of India 6|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
mount Amt> Ccy='INR'>3400.00</IntrBkSttlmAmt>
Debtor <Dbtr> Debtor 2.40 [1..1] [1..1] If net credit then RBI-RTGS IFSC. If net
debit the Member IFSC
If net debit of RBI current account
then RBI-CBS IFSC. If net credit of RBI
current account then RBI-RTGS IFSC.
FinancialInstitutionIden <FinInstnId> [1..1] [1..1]
tification
ClearingSystemMembe <ClrSysMm [0..1] [1..1] Mandatory in RTGS implementation
rIdentification bId>
Member Identification <MmbId> IndianFinancialSyste [1..1] [1..1] <Dbtr><FinInstnId><ClrSysMmbId><MmbId>H Max35Text
mCodeIdentifier for DFC0239777</MmbId></ClrSysMmbId></FinIn
participants / stnId></Dbtr>
Name and
Identification for non
Participants is
mandatory
Creditor <Cdtr> creditor 2.46 [1..1] [1..1] If net credit then Member IFSC. If net
debit then RBI-RTGS IFSC. If net debit
of RBI current account then RBI-RTGS
IFSC. If net credit of RBI current
account then RBI-CBS IFSC.
FinancialInstitutionIden <FinInstnId> [1..1] [1..1]
tification
ClearingSystemMembe <ClrSysMm [0..1] [1..1] Mandatory in RTGS implementation
rIdentification bId>
Member Identification <MmbId> IndianFinancialSyste [1..1] [1..1] <Cdtr><FinInstnId><ClrSysMmbId><MmbId>HD Max35Text
mCodeIdentifier for FC0239777</MmbId></ClrSysMmbId></FinInst
participants / nId></Cdtr>
Name and
Identification for non
Participants is
mandatory
RemittanceInformatio <RmtInf> Remittance 2.75 [0..1] [0..1]
n Information

Reserve Bank of India 7|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditT
ransferV03
Message Item
Unstructured <Ustrd> Remittance 2.76 [0..n] [0..4] Size restricted to a maximum of 4 Max140Text
Information 140 repeats of 140 characters.
characters up to 4
can be used
Sender to Receiver
Information
Note:- [1..1] -> Mandatory; [0..1] -> Optional ; [1..n] -> Mandatory and n times repeated ; [0..n] -> Optional and n times repeated;

Reserve Bank of India 8|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
Own Account Transfer (OAT)*
ISO message “pacs.009.001.03 FinancialInstitutionCreditTransferV03” is used for defining the Own account transfer in RTGS.

This message formats would replace the current R10 used in current RTGS.
*Corresponds to R10 in current RTGS.
The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business
application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain
the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business
message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

ISO 20022 Message

ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
<FinInstnCd Root tag
tTrf>
GroupHeader <GrpHdr> Fields 1.0 [1..1] [1..1]
common to all

Reserve Bank of India 1|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
the
transaction in
the message
MessageIdentification <MsgId> Uniquely 1.1 [1..1] [1..1] Uniquely identifies message <MsgId> Max35T
identifies the HDFC201210181000000218</MsgId> ext
message Recommend
MessageIdentification be
structured as:

XXXX- Sender IFSC [4]

YYYYMMDD - Creation Date
Reverse [8]
X – Channel [1]
nnnnnnnnn- Sequence Number
[9]

The values of Channel

Identification (X) is the same as
defined for
TransactionIdentification <TxId>
CreationDateTime <CreDtTm> Payment 1.2 [1..1] [1..1] Time upto seconds only <CreDtTm>2011-04-24T09:30:32</CreDtTm> ISODateTi
origination date me
time
NumberOfTransactions <NbOfTxs> Number of 1.4 [1..1] [1..1] Always 1 for own account transfer <NbOfTxs>1</NbOfTxs> Max15Nu
transactions mericText
TotalInterbankSettleme <TtlIntrBkSt Total 1.6 [0..1] [1..1] Amount
ntAmount tlmAmt> Settlement
Amount +
Currency
InterbankSettlementDa <IntrBkSttl Settlement Date 1.7 [0..1] [1..1] ISODate
te mDt> – will settle only
current day
SettlementInformation <SttlmInf> Details on how 1.8 [1..1] [1..1]
settlement of

Reserve Bank of India 2|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
transaction
happens
SettlementMethod <SttlmMtd> Method used 1.9 [1..1] [1..1] Must be CLRG (i.e., Settlement <SttlmMtd>CLRG</SttlmMtd> Code
to settle done through a payment clearing
payments system)

Other Codes are:

CLRG, COVE, INDA, INGA
InstructingAgent <InstgAgt Agent that 1.21 [0..1] [1..1] Mandatory in RTGS
> instructs the implementation
next party in
the chain to IFSC of the bank initiating OAT.
carry out the
(set of)
instruction(s).
FinancialInstitutionIde <FinInstnI [1..1] [1..1]
ntification d>
ClearingSystemMemb <ClrSysM [0..1] [1..1]
erIdentification mbId>
Member <MmbId> IFSC of the [1..1] [1..1] <InstgAgt><FinInstnId><ClrSysMmbId><MmbI Max35Te
Identification Sending d>HDFC0239777</MmbId></ClrSysMmbId>< xt
participant /FinInstnId></InstgAgt>
InstructedAgent <InstdAgt Agent that is 1.22 [0..1] [1..1] Mandatory in RTGS
> instructed by Implementation
the previous
party in the
chain to carry IFSC of RBI
out the (set of)
instruction(s).
FinancialInstitutionIde <FinInstnI [1..1] [1..1]
ntification d>
ClearingSystemMemb <ClrSysM [0..1] [1..1]
erIdentification mbId>

Reserve Bank of India 3|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
Member <MmbId> IFSC of the [1..1] [1..1] <InstdAgt><FinInstnId><ClrSysMmbId><MmbI Max35Te
Identification Receiving d>RBIS0000001</MmbId></ClrSysMmbId></ xt
participant FinInstnId></InstdAgt>
CreditTransferTransacti <CdtTrfTxIn Credit transfer 2.0 [1..n] [1..1] Only one occurrence allowed for own
onInformation f> information account transfer
containing
credit and debit
information
PaymentIdentification <PmtId> Payment 2.1 [1..1] [1..1]
Identification
EndToEndIdentification <EndToEndI End to End 2.3 [1..1] [1..1] Related reference. In case of <EndToEndId>TREF2312135465781</EndToE Max35Te
d> Identification returned transaction. Else same as ndId> xt
(Related TransactionIdentification
Reference)
TransactionIdentificatio <TxId> Transaction 2.4 [1..1] [1..1] Use UTR (Unique Transaction <TxId> HDFCR12012042400000023</TxId> Max35Te
n Identification Reference) format (22 characters) xt
XXXX- Sender IFSC [4] For Further Information, pl refer to FAQ on
X-Payment System [1] Channel.
X-Channel [1]
YYYYMMDD-Date [8]
nnnnnnnn- Sequence Number [8]

Unique identification, as assigned

by the first instructing agent, to
unambiguously identify the
transaction
that is passed on, unchanged,
throughout the entire interbank
chain.

Usage: The transaction

identification can be used for
reconciliation, tracking or to link
tasks relating to the
Reserve Bank of India 4|Page
ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
transaction on the interbank level.
Usage: The instructing agent has
to make sure that the transaction
identification is unique for a pre-
agreed
period.
PaymentTypeInformati <PmtTpInf> Payment 2.6 [0..1] [1..1] Priority is mandatory in RTGS
on Information implementation.

InstructionPriority <InstrPrty> Priority must 2.7 [0..1] [1..1] HIGH / NORM <InstrPrty>NORM</InstrPrty>
be valid ISO
priority code Indicator of the urgency or order
value
of importance that the instructing
party would like the instructed
party to apply to the processing of
the instruction at application level.
Priority “NORM” will result in
liquidity Savings.

HIGH: Priority Level is high.

NORM: Priority Level is normal.
ServiceLevel <SvcLvl> Service level 2.9 [0..1] [0..1] Agreement under which or rules
under which the transaction
should be processed.

Proprietary <Prtry> Proprietary 2.11 [0..1] [1..1] For RTGS used to indicate RTGS <Prtry>80</Prtry> Max35Te
Service Level processing priority in range 00– xt
Code 99.

To be used for managing queues

by sending bank before
settlement.
LocalInstrument <LclInstrm Local 2.12 [0..1] [1..1]

Reserve Bank of India 5|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
> instrument
type

(User
community
specific
instrument.)
Proprietary <Prtry> Proprietary 2.13 [0..1] [1..1] Type of local instrument. <Prtry> OwnAccTransfer </Prtry> Max35Te
instrument For RTGS, pacs.009 use: xt
type code -‘OwnAccTransfer’
InterbankSettlementA <IntrBkSttl Settlement 2.18 [1..1] [1..1] Amount transferred between <IntrBkSttlmAmt Amount
mount mAmt> Amount accounts Ccy='INR'>3400.00</IntrBkSttlmAmt>

Debtor <Dbtr> ORDERING 2.40 [1..1] [1..1]

INSTITUTION
FinancialInstitutionIdent <FinInstnId [1..1] [1..1]
ification >
ClearingSystemMemberI <ClrSysM [0..1] [1..1] Mandatory in RTGS implementation
dentification mbId>
Member Identification <MmbId> IndianFinanci [1..1] [1..1] IFSC of participant sending the <Dbtr><FinInstnId><ClrSysMmbId><MmbId>HDFC Max35Tex
alSystemCodeI payment request 0239777</MmbId></ClrSysMmbId></FinInstnId>< t
dentifier for /Dbtr>
participants /
Name and
Identification
for non
Participants is
mandatory
DebtorAccount <DbtrAcct 2.41 [0..1] [1..1] Mandatory in RTGS implementation
>
Identification <Id> [1..1] [1..1]
Other <Othr> [1..1] [1..1]
Identification <Id> Account [1..1] [1..1] From account of participant <DbtrAcct><Id><Othr><Id>34545353</Id></Othr Max35Tex
Number ></Id></DbtrAcct> t

Reserve Bank of India 6|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data Type
pacs.009.001.03 Multi Multi
FIToFICustomerCreditTr
ansferV03
Message Item
Currency <Ccy> Account [0..1] [0..1] <Ccy>INR</Ccy>
currency
Creditor <Cdtr> Beneficiary 2.46 [1..1] [1..1]
Institution
identification
FinancialInstitutionIdent <FinInstnId [1..1] [1..1]
ification >
ClearingSystemMemberI <ClrSysMm [0..1] [1..1] Mandatory in RTGS implementation
dentification bId>
Member Identification <MmbId> IFSC [1..1] [1..1] IFSC of participant receiving the <Cdtr><FinInstnId><ClrSysMmbId><MmbId>RBIS0 Max35Tex
payment request. 000001</MmbId></ClrSysMmbId></FinInstnId></ t
Cdtr>
CreditorAccount <CdtrAcct> 2.47 [0..1] [1..1] Mandatory in RTGS implementation
Identification <Id> [1..1] [1..1]
Other <Othr> [1..1] [1..1]
Identification <Id> [1..1] [1..1] To account of participant <CdtrAcct><Id><Othr><Id>546545353</Id></Othr Max35Tex
></Id></CdtrAcct> t
Currency <Ccy> Account [0..1] [0..1] <Ccy>INR</Ccy>
currency
RemittanceInformation <RmtInf> Remittance 2.55 [0..1] [0..1]
Information
Unstructured <Ustrd> Remittance 2.56 [0..n] [0..4] Size restricted to a maximum of 4 Max140T
Information 140 repeats of 140 characters. ext
characters up to
4 can be used.

Reserve Bank of India 7|Page

ISO Messages, “pacs.009.001.03 FinancialInstitutionCreditTransferV03”
 ISO20022 standard Message Implementation

Payment Return
ISO message “pacs.004.001.03 PaymentReturnV03”

Bank-to-Bank message, settlement already completed in NG-RTGS. Function of the pacs.004 message is “sent by an agent to the previous agent in the payment
chain to undo a payment previously settled.”

This message formats would replace the current R42 for return & N07 in NEFT messages.
*Corresponds to R42 in current RTGS & N07 in NEFT messages

The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business
application. Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain
the business sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business
message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

ISO 20022 Message

Reserve Bank of India 1|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Message Item XML tag Description Index ISO NEFT/ Rules Example Data
ISO20022 Messages - Multi RTGS Type
pacs.004.001.03 multip
PaymentReturnV03 licity
Message root <PmtRtr> Root tag for PaymentReturn [1..1]
Message
GroupHeader <GrpHdr> Fields common to all the 1.0 [1..1]
transaction in the message
MessageIdentification <MsgId> Uniquely identifies the message 1.1 [1..1] [1..1] Uniquely identifies message <MsgId>
HDFC201210181000
Recommend 000218</MsgId>
MessageIdentification be
structured as:

XXXX- Sender IFSC [4]

YYYYMMDD - Creation Date
Reverse [8]
X – Channel [1]
nnnnnnnnn- Sequence
Number [9]

The values of Channel

Identification (X) is the same
as defined for
TransactionIdentification
<TxId>
CreationDateTime <CreDtTm> Payment origination date time 1.2 [1..1] [1..1] ISODateT
ime
NumberOfTransactions <NbOfTxs> Number of transactions 1.7 [1..1] [1..1] Max15N
umericTe
xt
TotalReturnedInterban <TtlRtrdIntrBkSttl Total amount of money moved 1.10 [0..1] [1..1] Amount
kSettlementAmount mAmt> between the instructing agent and
the instructed agent in the return
message

Reserve Bank of India 2|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Message Item XML tag Description Index ISO NEFT/ Rules Example Data
ISO20022 Messages - Multi RTGS Type
pacs.004.001.03 multip
PaymentReturnV03 licity
InterbankSettlementDat <IntrBkSttlmDt> 1.11 [0..1] [0..1] ISO Date
e

SettlementInformation <SttlmInf> Specifies the details on how the 1.12 [1..1] [1..1]
settlement of the transactions
between the instructing agent and
the instructed agent is completed.
SettlementMethod <SttlmMtd> Method used to settle payments [1..1] [1..1] Default value ‘CLRG’ Code
Other Codes are: CLRG, COVE,
INDA, INGA
</SttlmInf>
</GrpHdr>

OriginalGroupInformati <OrgnlGrpInf> 2.0 [0..1]

on
OriginalMessageIdentif <OrgnlMsgId> 2.1 [1..1] Max35T
ication ext
OriginalMessageNameI <OrgnlMsgNmId 2.2 [1..1] Max35T
dentification > ext
OriginalCreationDateTi <OrgnlCreDtTm> 2.3 [0..1] [0..1] ISODate
me
TransactionInformatio <TxInf> Contains information on individual 3.0 [0..n] [1..10]
n transactions NEFT
[1..1]
RTGS

Reserve Bank of India 3|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Message Item XML tag Description Index ISO NEFT/ Rules Example Data
ISO20022 Messages - Multi RTGS Type
pacs.004.001.03 multip
PaymentReturnV03 licity
ReturnIdentification <RtrId> Transaction Identification, as 3.1 [0..1] [1..1] Transaction Reference Max35T
assigned by an returning party for Number of 22 Chars of ext
an sending party, to unambiguously Instucting Party
Identify the returned transaction.
Use UTR (Unique Transaction
Reference) format (22
characters)
XXXX- Sender IFSC [4]
X-Payment System [1]
X-Channel [1]
YYYYMMDD-Date [8]
nnnnnnnn- Sequence Number
[8]
OriginalTransactionIde <OrgnlTxId> Unique Transaction reference , as 3.8 [0..1] [1..1] Original Max35Te
ntification assigned by the original first Transaction Reference xt
instructing agent(sender), to Number
unambiguously identify the Instructing party.
Transaction. This must contain
Transaction Reference Number of
the received inward credit message
at bank branch that is returned.
ReturnedInterbankSettl <RtrdIntrBkSttlmA Amount being returned between 3.11 [1..1] [1..1] Amount Amount
ementAmount mt> instructing and instructed parties
on account of returned
transaction. This amount should be
same as the amount requested by
the originator as NEFT doesn’t have
concept of settling a part amount
and returning the rest .

Reserve Bank of India 4|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Message Item XML tag Description Index ISO NEFT/ Rules Example Data
ISO20022 Messages - Multi RTGS Type
pacs.004.001.03 multip
PaymentReturnV03 licity
InterbankSettlementD <IntrBkSttlmDt> Settlement Date. Date on which 3.12 [0..1] [1..1] ISODate
ate reversal of the settlement takes
place. It can be only the current
date. It will have the Date of the
return transaction and not the
original instruction
InstructingAgent <InstgAgt> Sender IFSC .This should be the IFSC 3.20 [0..1] [1..1]
that is sending the return request
and not the branch that has sent
the original instruction
FinancialInstitutionIden <FinInstnId> [1..1] [1..1]
tification
ClearingSystemMembe <ClrSysMmbId> This should contain the Sender IFSC [0..1] [1..1] Sending Branch’s IFSC
rIdentification of the transaction i.e branch IFSC
code .This is the Code allocated to a
financial institution by the ISO 9362
Registration Authority as described
in ISO 9362
MemberIdentification <Mmbid> [1..1] [1..1] Sending Branch’s IFSC Max35Te
xt
</Mmbid></ClrSy
sMmbId></FinInst
nId></InstgAgt>
InstructedAgent <InstdAgt> Receiver IFSC .This should be the 3.21 [0..1] [1..1]
IFSC to which the return transaction
is being sent i.e. the IFSC which is
receiving the return message
FinancialInstitutionIden <FinInstnId> [1..1] [1..1]
tification

Reserve Bank of India 5|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Message Item XML tag Description Index ISO NEFT/ Rules Example Data
ISO20022 Messages - Multi RTGS Type
pacs.004.001.03 multip
PaymentReturnV03 licity
<ClrSysMmbId> [0..1] [1..1]
ClearingSystemIdentific
ation

MemberIdentification <Mmbid> This should contain the Receiver [1..1] [1..1] Beneficiary branch’s IFSC
IFSC of the transaction i.e.
beneficiary branch where the
account needs to be credited back
because of return request. This is
the Code allocated to a financial
institution by the ISO 9362
Registration Authority as described
in ISO 9362
</Mmbid>
</FinInstnId></Ins
tdAgt>

ReturnReasonInformati <RtrRsnInf> Provides detailed information on the 3.22 [0..n] [1..1]

on return reason.
Originator <Orgtr> Originator of remittance 3.23 [0..1] [0..1] Originator of Remittance
information
(Party that issues the return)

[This message item is composed of

the following PartyIdentification43
element(s). i.e., Name, Postal
Address, Contact Details, etc.]
Name <Nm> [0..1] [0..1] Max140Te
xt
PostalAddress <PstlAdr> [0..1] [0..1]
AddressLine <AdrLine> [0..7] [0..4] Max70Tex
t

Reserve Bank of India 6|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Message Item XML tag Description Index ISO NEFT/ Rules Example Data
ISO20022 Messages - Multi RTGS Type
pacs.004.001.03 multip
PaymentReturnV03 licity
</PstlAdr>
ContactDetails <CtctDtls> [0..1] [0..1]
MobileNumber <MobNb> [0..1] [0..1] PhoneNu
mber
EmailAddress <EmailAdr> Address for electronic mail (e-mail). [0..1] [0..1] Max2048
Text
</CtctDtls></Orgt
r>
Reason <Rsn> Specifies the reason for the return. 3.24 [0..1] [1..1]
Code <Cd> This must contain the reason codes [1..1] [1..1] <Rsn><Cd>NARR</Cd></Rsn> External
for rejection ReturnRe
For Other Reason Codes are: ason1Co
NARR, BE01, BE06, CUST, …. de
For detail pl refer to External
CodeLists_3Q2012_22Oct201
2_v4
</Rsn>
AdditionalInformation <AddtlInf> Further details on the return reason 3.27 [0..n] [1..1] <AddtlInf>RETURN DUE TO Max105T
WRONG ACCOUNT ext
CREDIT</AddtlInf>
</RtrRsnInf></Or
gnlTxRef></TxInf>
</PmtRtr>

Reserve Bank of India 7|P a g e

ISO message “pacs.004.001.03 PaymentReturnV03”
 ISO20022 standard Message Implementation
Payment Status Report *
ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”

Applicable Areas: RTGS

1) For defining “MNSB Response” in RTGS.
2) For defining “Own Account Transfer Response” in RTGS

This message formats would replace the current R13 used in current RTGS for MNSB response & R40 used in Current RTGS for Own A/c
Transfer (OAT) response.
*Corresponds to R13 & R 40 in current RTGS.

The ISO 20022 Business Message consists of two parts: (1) ISO 20022 Business Appl. Header (2) ISO 20022 Messages

Business Application Header is a business header and should not be confused with a file or transport header. It is created before the transport routing header is applied
to the business message and is retained after the transport header is removed. So any parties between the two business applications that don't perform a business
function are not mentioned in the BAH. Such 'technical' middle men don't open or change the Business Message; they only forward it to the correct business application.
Although the BAH is not the transport header, data in the BAH can be used by transport applications to determine the routing header since it does contain the business
sender, receiver and document details. It can also be used by the business applications to determine the appropriate process to perform on the business message.

Message fields description

ISO Business Application Header

Business Application Header (Refer related documentation “RBI_NG_RTGS_ISO20022_BusinessApplicationHeader”)

Reserve Bank of India 1|Page

ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”
 ISO20022 standard Message Implementation

ISO 20022 Message

ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data
pacs.002.001.04 Multi Type
FIToFIPaymentStatusRep
ortV04
Message Item
<FIToFIPmtSts Root tag [1..1] [1..1]
Rpt>
GroupHeader <GrpHdr> Fields common to 1.0 [1..1] [1..1]
all the transaction
in the message
MessageIdentification <MsgId> Uniquely identifies 1.1 [1..1] [1..1] Uniquely identifies message <MsgId> Max35Te
the message HDFC201210181000000218</MsgId> xt
Recommend MessageIdentification be
Point to point structured as:
reference, as
assigned by the XXXX- Sender IFSC [4]
account servicing YYYYMMDD - Creation Date Reverse [8]
institution, and X – Channel [1]
sent to the nnnnnnnnn- Sequence Number [9]
account owner or
the party The values of Channel Identification
authorised to
(X) is the same as defined for
receive the
TransactionIdentification <TxId>
message, to
unambiguously
identify the
message.
CreationDateTime <CreDtTm> Message date time 1.2 [1..1] [1..1] Time upto seconds only <CreDtTm>2011-04- ISODateT
24T09:30:32</CreDtTm> ime
OriginalGroupInformatio <OrgnlGrpInfA Original group 2.0 [1..1] [1..1]
nAndStatus ndSts> information
concerning the
group of
transactions, to
which the status
report message
Reserve Bank of India 2|Page
ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data
pacs.002.001.04 Multi Type
FIToFIPaymentStatusRep
ortV04
Message Item
refers to.
OriginalMessageIdentific <OrgnlMsgId> Transaction 2.1 [1..1] [1..1] <OrgnlMsgId>TREF097865123125</Orgn Max35Te
ation reference . lMsgId> xt
This msg element is
part of
OrgnlGrpInfAndSts
block.
OriginalMessageNameId <OrgnlMsgNmI Specifies the 2.2 [1..1] [1..1] <OrgnlMsgNmId>pacs.009.001.03</Orgn Max35Te
entification d> original message lMsgNmId> xt
name identifier
to which the
message refers.
This msg element is
part of
OrgnlGrpInfAndSts
block.
OriginalCreationDateAnd <OrgnlCreDtTm Original Message 2.3 [0..1] [1..1] Mandatory in RTGS implementation <OrgnlCreDtTm>2011-04- ISODateT
Time > date time. 24T09:30:32</OrgnlCreDtTm> ime
This msg element is
part of
OrgnlGrpInfAndSts
block.
GroupStatus <GrpSts> Specifies the status 2.6 [0..1] [1..1] Mandatory in RTGS implementation <GrpSts>ACSC</GrpSts> Code
of a group of For details on status code, pl refer to
transactions. para 2.6 of documentation “Payment
Status code- Clearing & Settlement – Maintenance
ACSC/ACSP/ACTC/ 2012 by ISO”.
PDNG/RCVD/RJCT.
This msg element is
part of
OrgnlGrpInfAndSts
block.
StatusReasonInformation <StsRsnInf> Reason for success 2.7 [0..n] [0..1] Repeats only once
/ failure.
This msg element is

Reserve Bank of India 3|Page

ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data
pacs.002.001.04 Multi Type
FIToFIPaymentStatusRep
ortV04
Message Item
part of
OrgnlGrpInfAndSts
block.
Reason <Rsn> Reason code 2.9 [0..1] [1..1]
Proprietary <Prtry> Actual reason code 2.11 [1..1] [1..1] /!3x Reason desc /012 No Liquidity Max35Te
and reason xt
description
Original Transaction <OrgnlTxRef> Key elements 3.20 [0..1] [1..1] Mandatory in RTGS implementation for
Reference used to identify Net Clearing response
the original
.transaction that
is being referred
to.
InterbankSettlementAmo <IntrBkSttlmA This msg element 3.21 [0..1] [1..1] Mandatory in RTGS implementation <IntrBkSttlmAmt Amoun
unt mt> is the part of Ccy="INR">10000.00</IntrBkSttlmAmt> t
OrgnlTxRef block
PaymentTypeInformatio <PmtTpInf> Set of elements [0..1] [1..1]
n used to provide
further details of
the type of
payment.
This msg element
is the part of
OrgnlTxRef block.
LocalInstrument <LclInstrm> User community [0..1] [1..1]
specific instrument.
This element is
used to specify a
local instrument,
local clearing
option and/or
further qualify the
service or service
level

Reserve Bank of India 4|Page

ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data
pacs.002.001.04 Multi Type
FIToFIPaymentStatusRep
ortV04
Message Item
Proprietary <Prtry> Proprietary [0..1] [1..1] Type of Local Instrument. Max35T
instrument type RTGSFIToFICredit' or ext
code -'RTGSOwnAccTtransfer' or
-'RTGSNetSettlementXXzNN'
Where 'XX' is the clearing type which
may take values 'GC', 'IB', 'FX', MC, SE,
OT & so on.
'z' is the indicator which may take
values C -Original, R-Return, L-Last
Return.
"NN" is the return serial.
"GC" stands for guaranteed settlement
of Securities and CBLO segment.
"IB" stands for guaranteed settlement
of FOREX segment.
"FX" stands for non guaranteed
settlement.
"MC" Stands for MICR Clearing
"SE" stands for non-guaranteed MNSB
"OT" stands for Other MNSB.
Clearing party / 3.1.63 [0..1] [0..1] Mandatory in RTGS implementation for
Debtor <Dbtr> sponsoring 4 Own Account Transfer and Net Clearing
institution. response
This msg element
is the part of
OrgnlTxRef block.
FinancialInstitutionIdenti <FinInstnId> [1..1] [1..1]
fication
ClearingSystemMemberI <ClrSysMmbId [0..1] [1..1]
dentification >
Member Identification <MmbId> [1..1] [1..1] <Dbtr><FinInstnId><ClrSysMmbId><Mm Max35Te
bId>HDFC0239777</MmbId></ClrSysM xt
mbId></FinInstnId></Dbtr>
DebtorAccount <DbtrAcct> Unambiguous 3.1.677 [0..1] [0..1] Mandatory in RTGS implementation for

Reserve Bank of India 5|Page

ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data
pacs.002.001.04 Multi Type
FIToFIPaymentStatusRep
ortV04
Message Item
identification of Own Account
the account of the
debtor to which a
debit entry will be
made as a result of
the transaction.
This msg element
is the part of
OrgnlTxRef block.

Identification <Id> [1..1] [1..1]

Other <Othr> [1..1] [1..1]
Identification <Id> Account Number [1..1] [1..1] From account of participant <DbtrAcct><Id><Othr><Id>34545353</Id Max35Te
></Othr></Id></DbtrAcct> xt
Currency <Ccy> Account currency [0..1] [1..1] For NG-RTGS , “INR” is the only <Ccy>INR</Ccy> Code
currency that can be specified.
Clearing party / 3.1.79. [0..1] [0..1] Mandatory in RTGS implementation for
Creditor <Cdtr> sponsoring 9 Own Account Transfer and Net Clearing
institution. response
This msg element
is the part of
OrgnlTxRef block.
FinancialInstitutionIdenti <FinInstnId> [1..1] [1..1]
fication
ClearingSystemMemberI <ClrSysMmbId [0..1] [1..1]
dentification >
Member Identification <MmbId> [1..1] [1..1] <Cdtr><FinInstnId><ClrSysMmbId><Mmb Max35Te
Id>HDFC0239777</MmbId></ClrSysMm xt
bId></FinInstnId></Cdtr>
CreditorAccount <CdtrAcct> Unambiguous 3.1.842 [0..1] [0..1] Mandatory in RTGS implementation for
identification of Own Account
the account of the
creditor to which a

Reserve Bank of India 6|Page

ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”
 ISO20022 standard Message Implementation
ISO20022 Message - XML tag Description Index ISO RTGS Rules Example Data
pacs.002.001.04 Multi Type
FIToFIPaymentStatusRep
ortV04
Message Item
credit entry will be
made as a result of
the transaction.
This msg element
is the part of
OrgnlTxRef block.
Identification <Id> [1..1] [1..1]
Other <Othr> [1..1] [1..1]
Identification <Id> Account Number [1..1] [1..1] From account of participant <CdtrAcct><Id><Othr><Id>34545353</Id Max35Te
></Othr></Id></CdtrAcct> xt
Currency <Ccy> Account currency [0..1] [1..1] For NG-RTGS , “INR” is the only <Ccy>INR</Ccy> Code
currency that can be specified.

Note:- [1..1] -> Mandatory; [0..1] -> Optional ; [1..n] -> Mandatory and n times repeated ; [0..n] -> Optional and n times repeated;

Reserve Bank of India 7|Page

ISO message “pacs.002.001.04, FIToFIPaymentStatusReportV04”