Pursuant to Section 7 paragraph 1 of the Decision on Electronic

Payment Transactions (“RS Official Gazette”, No. 57/2004), the

Governor of the National Bank of Serbia hereby issues

GUIDELINES
FOR THE FORMAT AND PURPOSE OF DATA EXCHANGE
MESSAGES IN PAYMENT TRANSACTIONS

1. These Guidelines set out the format and purpose of data

exchange messages used in electronic payment transactions between
the National Bank of Serbia, banks from Article 2 Section 10 provision a)
of the Law on Payment Transactions (“FRY Official Gazette”, No.
3/2002 and 5/2003 and “RS Official Gazette”, No. 43/2004 and 62/2006)
and other entities holding accounts with the National Bank of Serbia in
line with the law (hereinafter: participants).

2. The format and purpose of data exchange messages from

Section 1 hereof are given in Schedules 1–3 to these Guidelines.

2. The elements used for the verification of authenticity and

accuracy of electronic payment orders and authenticity of their
submitters shall be provided by SWIFT software – provided data
exchange messages from Section 1 hereof are sent via the SWIFT
network.

As regards data exchange messages sent via the network of

the National Bank of Serbia – the National Bank of Serbia shall provide
the participants with elements from paragraph 1 hereof.

4. On the day of effectiveness hereof, the Guidelines for the

Format and Purpose of Data Exchange Messages in Payment
Transactions (G. No. 1514 of 18 May 2004, G. No. 4757 оf 17 December
2004, G. No. 9770 of 2 November 2006 and G. No. 4466 оf 30 April
2009) shall cease to be valid.

5. These Guidelines shall come into effect on 16 November

2009.

G. No. Governor
10 November 2009 National Bank of Serbia
Belgrade
Radovan Jelašić
 2.

Schedule 2

Basic messages under SWIFT standard

1. Cashless payment order

Transfer order is the basic document for the transfer of funds in the system. Elements
of the transfer order are presented in the table below:

Description Format Mandatory Note

1 Method of execution Х Urgent=1
2 Name of the order issuer - payer 3*35Х yes
3 Name of the payee 3*35Х yes
4 Account number of the payer 18N Under the Decision1,
empty at cash pay-
ins
5 Account number of the payee 18N mandatory for Under the Decision,
interbank empty at cash pay-
banking and outs
payment
transactions
6 Currency code 3X yes RSD for dinars2
7 Amount 12N,NN yes At most 12 integers,
comma, at most two
decimal places, only
positive, the plus sign
is implied
8 Purpose of payment 3*35X
9 Payment code 3N From the Code List3
4
10 Model of debit authorization number 2X Under the Decision
11 Debit authorization number 20X Under the Decision4
12 Model of credit authorization number 2X Under the Decision4
13 Credit authorization number 20X Under the Decision4
14 Place of submission 20X
15 Date of submission DD/MM/YY
16 Value date DD/MM/YY yes
17 Verification – yes On paper documents,
stamped – if
envisaged

The table below presents the structure of cashless payment order in the system in
electronic form. Technical fields used internally in the system are not shown. The structure may vary to
some extent from one bank to another. Although these variations mostly refer to technical details, the
most important thing is that there is no loss of information.

Field Description Format

Initial bank identification Bank identification code (BIC) based on 8/11 characters in SWIFT

1
Decision on Unique Structure for Identification and Classification of Accounts and the Plan of Accounts for
Payment Transactions with a Bank.
2
In line with ISO 4217.
3
The Code List from the Decision on the Decision on the Form, Contents and Use of Unique Instruments in
Payment Transactions.
4
Decision on the Form, Contents and Use of Unique Instruments in Payment Transactions.
 3.

which the prescribed three-digit bank account

number from the Decision5 may be
unequivocally ascertained
Initial bank reference Unique identifier of payment order for the Up to 16 characters
initial bank in the course of one settlement
day
Method of execution Determining whether the order being 4 numerical signs,
processed should be treated as urgent or not 0000-0010 for the system
needs
0011-099 urgent
0100 not urgent
Name of the payer Name and address of the payer – holder of Up to 105 characters (3*35)
the debiting account
Name of the payee Name and address of the payment Up to 105 characters (3*35)
beneficiary, mandatory control element in the
payment process; if the beneficiary’s account
does not exist in the register of the bank
which received the order, this element has to
be entered (otherwise, contents from the
register are taken over to be reconciled
against the contents of the original
document)
Debiting account (payer’s Account to be debited, in the format and with 18 digits, fixed without lines, in
account) control elements as under the Decision5 line with the Decision5
Crediting account (payee’s Account to be credited, in the format and with 18 digits, fixed without lines, in
account) control elements as under the Decision5 line with the Decision5
Currency code Code of the currency in which the payment is 3 characters, in dinar payment
made, according to ISO standard transactions: RSD
Amount Amount of payment to be executed Up to 14 significant digits, up to
two decimal places separated by
a comma, has to be positive
Purpose of payment Description of the purpose of payment, free Up to 105 characters (3*35)
form

Payment code Three-digit code for the purpose of payment Three digits
as specified in the Code List, used for
statistical reporting and analysis
Payer’s reference Reference transferred to the payment Model of 2 characters and
beneficiary and shown in its account authorization number up to 20
statement. It consists of a debit authorization characters, total up to 22
model and number. characters, with two blank
places if the model is empty
Payee’s reference Reference transferred to the payment Model of 2 characters and
beneficiary and shown in its account authorization number up to 20
statement. It consists of a credit authorization characters, total up to 22
model and number. characters, with two zeroes if
the model is empty
Value date Date when the payment is due, i.e. when it Any clearly recognizable date
has to be executed. format
The order receipt before the maturity date
may be approved only in line with NBS
policy.

5
Decision on Unique Structure for Identification and Classification of Accounts and the Plan of Accounts for
Payment Transactions with a Bank.
 4.

2. Message МТ 103 – Single customer credit transfer

As message МТ 103 is a standard for credit transfers for clients in SWIFT, the
applicable fields of SWIFT message MT 103 are identical to those of cashless payment order. Its
elements are as follows:

Field Elements of cashless payment order Mandatory Note

113 Execution of message in RTGS (values 0011– Field 113 is in a block of 3
0099) is determined based on business priority; messages, if not specified
if wait lists are included, this is a priority of – value 0099 is implied,
execution of orders put on wait list execution in RTGS with
lowest priority
20 Reference number (TRN) of the initial bank yes TRN in SWIFT
23B Always CRED yes
23Е Always SDVA yes
26Т Under SWIFT
32А Value date, currency code (for dinars: RSD) and yes Example:
amount, date in format YYММDD 030123RSD5678,50
50К In format К yes Payer’s account is a
/account of the payer mandatory element, slash
name and address is a part of account
designation syntax; the
payer’s bank account
number should correspond
to the BIC of the bank
sending the message
53А Account and BIC of the bank executing yes Slashes and letter D are a
payment in format part of syntax
/D/account of the bank or /account of the bank
BIC
57А Account and BIC of the bank whose account is yes Has to correspond to the
credited (bank with which the payee’s account bank account number in
is held) in format 59, slashes and letter C
/C/account of the bank or /account of the bank are a part of syntax
BIC
59 No option yes Account is mandatory,
/account of the payee slash is a part of account
name and address designation syntax
70 The following elements are transferred: yes Example:
payment code, credit and debit authorization 70:SIF-111
numbers. These elements are designated with PBZ-97123456ABC
prefixes separated by a hyphen from the PBO-97123AFG14
contents, authorization numbers have, on the REF-456789
left side, accompanying appropriate models so
that the total length of fields is 22 characters.
PBZ – (debit authorization number)
PBO – (credit authorization number)
TRN – (reference number of connected
message – TRN)
71А Always SHA yes
72 Purpose of payment, up to 105 characters, also yes Example:
information for PVP, DVP and conditional 72:/BNF/UPLATA PO
payments6 //FAKTURI 123AFG14,
for the purpose of payment in the first line //RAZLIKA ZA MAJ
/BNF/, in other lines //, at most 4 lines, 105
characters

6
In line with the business policy of the National Bank of Serbia.
 5.

The payments system of the National Bank of Serbia allows the use of other fields,
although their contents are not checked and do not influence the syntax of messages.

3. Message МТ 202 – General financial institution transfer

Message МТ 202 is used for interbank transfers from one account to another account
in the RTGS, implying that MT 202 is executed only in this regime. Order for cashless payment
between banks is transferred to the applicable fields of SWIFT message MT 202. Its elements are as
follows:

Field Elements of cashless payment order Mandatory Note

113 Business value priority, as message is executed Field 113 is in a block of 3
in RTGS the values range from 0011 to 0099; if messages; if not specified,
wait lists are included, this is a priority of value 0099 is implied –
execution for messages put on wait list execution in RTGS with
lowest priority
20 Reference number (TRN) of the initial bank yes TRN in SWIFT
21 Connected reference yes Reference (TRN) of a
message to which this
message refers or NONREF
32А Value date, currency code (for dinars: RSD) and yes Example:
amount, date in format YYММDD 030123RSD8455678,50
53А Account and BIC of the bank executing payment yes Slashes and letter D are a
in format part of syntax
/D/account or /account
BIC
58А Account and BIC of the bank whose account is yes Slash and letter C are a part
credited (bank with which the payee’s account is of syntax
held) in format
/C/account or /account
BIC
72 The following elements are transferred: payment yes Example:
code, credit and debit authorization numbers. 72:/BNF/PBZ-97123456ABC
These elements are designated with prefixes //PBZ-97123AFG14
separated by a hyphen from the contents; //SIF-133-UPLATA PO
authorization numbers have, on the left side, //FAKTURI 123AFG14
accompanying appropriate models: //RAZLIKA ZA MAJ
PBZ – (debit authorization number)
PBO – (credit authorization number)
SIF – (payment code) – purpose of payment at
the beginning /BNF/, at the beginning of other
lines //, at most 5*35

The system allows the use of other fields, although they do not influence the execution
of transactions.

4. Message МТ 102 – Multiple customer credit transfer

Message МТ 102 is used for credit transfers to clients in clearing or RTGS. The
amount of each individual payment must be lower than the limit for large-value payments. All
payments of clients of one bank have to be sent in one message to the clients of another bank. Value
date has to be the same for all individual payments, as well as the currency code. Sum of all individual
payments has to correspond to the amount specified in field 32А. Under the SWIFT standard, the
message length is limited to 32 kilobytes. The message elements are as follows:

Field Elements of cashless payment order Mandatory Note

 6.

113 Business value priority determines that the Field 113 is in a block of 3
message is executed in clearing (0100) messages; if not specified,
value 0100 is implied –
execution is in clearing
In sequence A
20 Reference number (TRN) of the initial bank yes TRN in SWIFT
23 Always CREDIT yes
26Т Always REF yes
71А Always SHA yes
In a repetitive sequence B, for each individual
payment
21 Transaction reference yes
32B Currency code (for dinars: RSD) and amount yes Example:
RSD55678,50
50К /account of the payer yes Account is mandatory,
name and address of the payer slash is a part of account
designation syntax, bank
account number has to
correspond to BIC of the
bank whose account is
debited
59 /account of the payee yes Account is mandatory,
Name and address of the payee slash is a part of account
designation syntax, bank
account number has to
correspond to BIC of the
bank whose account is
credited
70 The following elements are transferred: payment yes Example:
code, credit and debit authorization numbers. 70:SIF-133
These elements are designated with prefixes PBZ-97123456ABC
separated by a hyphen from the contents, PBO-97123AFG14
authorization numbers have, on the left side, REF-123456/789ABC
accompanying appropriate models:
SIF – (payment code)
PBZ – (debit authorization number)
PBO – (credit authorization number)
REF – (reference number of connected message
– TRN)
77B Purpose of payment, 35+35+35 yes Example:
77B:UPLATA PO
FAKTURI 123AFG14,
RAZLIKA ZA MAJ
In sequence C
32А Value date, currency code (for dinars: RSD) and yes Example:
amount (sum of all transactions), date in format 030123RSD8455678,50
YYММDD
53А /D/IBAN of the bank executing payment or yes Slashes and letter D are
/account mandatory
BIC of the bank executing payment
54А Account and BIC of the bank whose settlement yes Has to correspond to the
account is credited, bank account number in
account is in the first line after /C/ or /, BIC in the field 59
second line

The system allows the use of other fields, although they do not influence the execution
of transactions.

5. Message MT 298/202 – credit transfers in an envelope

 7.

This format is used when clearing systems execute net clearing positions in RTGS.

Field Message elements Mandatory Note

20 Reference of the initial bank yes TRN – initiator is
external clearing
system
12 Type of message within an envelope yes Example:
12:202
77E yes
20: Body of message MT202 The whole message
to MT202 with all
72: elements and field
designations

Fields 12 and 77E are repeated for each MT202. Connected references for appropriate MT900 and
MT910 are fields 20 from message MT202.

The message is generated and sent by clearing systems, and responses to it are MT900 for the bank
whose account is debited, and/or message MT202 and MT910 for the bank whose account is credited.

6. Message МТ 900 – Confirmation of debit

Message МТ 900 is used as a confirmation of account debit after the execution of

transactions (103, 202 or 102). Message elements are as follows:

Field Message elements Mandatory Note

20 Reference of the initial bank yes TRN, RTGS is the initiator
21 Connected reference yes Reference of the
message – TRN to which
this message refers, i.e.
message whose
execution is confirmed
25 Account number yes Number of account
debited
32А Value date, currency code (for dinars: RSD) and yes Example:
amount, date in format YYММDD 030123RSD8455678,50
52A BIC of the transaction initiator yes – in case For debits initiated by
of third party third party
:52A:NBSRRSBD009
:52A:RTGSRSBG001
72 /OID/MIR financial transaction which initiated the yes Example:
debit :72:/OID/091015AIKBRS22
AXXX0001000017
and/or, for clearing, the designation of the cycle
and reference to the limit :72:/SESSION/MORNING
/RESDEBIT/CLEARING

7. Message МТ 910 – Confirmation of credit

Message МТ 910 is used as a confirmation of account credit after the execution of

transactions (103, 202 and 102). Message elements are as follows:

Field Message elements Obligatory Note

20 Reference of the initial bank yes TRN, RTGS is the initiator
21 Connected reference yes Reference of the
message – TRN to which
this message refers, i.e.
message whose
 8.

execution is confirmed
25 Account number yes Number of account
credited
32А Value date, currency code (for dinars: RSD) and yes Example:
amount, date in format YYММDD 030123RSD8455678,50
52А BIC of the transaction initiator yes Identification of the
institution which initiated
transaction, with a
connected reference and
value date it serves as a
unique identifier of the
message which initiated
the transfer
72 The designation of session for confirmation from yes for clearing Example:
clearing :72:/SESSION/MORNING

Field 56А is not used in the system.

8. Message МТ 920 – Request message

Message МТ 920 is used as a request for information on account balances or request
for the delivery of account statement. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference of the initial bank yes TRN
12 Requested response (type of message: 941 or yes 941 refers to account
942) status and 942 is a
temporary statement from
the last 940, 941 or 950
message
25 Account number yes Number of account to
which the message refers
34F Currency code (for dinars: RSD), designation C Example:
for credit (sum of debits) or D for debit (sum of RSDC100000,
credits) and amount, amount refers to the limit
below which transactions are not included in the
report
34F Currency code (for dinars: RSD), designation C Example:
for credit (sum of debits) or D for debit (sum of RSDC100000,00
credits) and amount, amount refers to the limit
below which transactions are not included in the
report

Fields 12, 25 and 34F are repeated, implying that several reports referring to more
accounts, with different limits, may be requested by one message.

9. Message МТ 941 – Balance report

Message МТ 941 is used for sending information on account balance, as a response

to request МТ 920 – request for information on account balance at a given moment. Message
elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN, RTGS is the initiator
21 Connected reference yes Reference of message МТ 920
– TRN, with which this
message was initiated
 9.

25 Account number yes Number of account to which

the message refers
28 Balance number/Message sequence yes Balance number is the ordinal
number of balance which is
sent for the specified account
from the beginning of the year.
If the balance is sent in several
messages, such messages are
to be numbered within a
sequence (from 1 onwards)
60F Opening balance in the form (D/C), date, Example:
currency code, amount. D stands for debit – C030717RSD100995,01
positive balance, and C for credit – negative
balance.
90D Number of debit transactions, currency code Example:
and amount 12RSD100000,00
90C Number of credit transactions, currency code Example:
and amount 122RSD200000,99
62F Closing balance for date in the form (D/C), date, yes Example:
currency code, amount. D stands for debit – C030717RSD200996,
positive balance, and C for credit – negative
balance.
64 Available balances in the form (D/C), date, Example:
currency code, amount. D stands for debit – C030717RSD200996,
positive balance, and C for credit – negative
balance.

10. Message МТ 942 – Interim statement

Message МТ 942 represents an interim statement relative to a previously taken

balance or statement. This message is sent as a response to request МТ 920. Message elements are
as follows:

Field Message elements Mandatory Note

20 Reference yes TRN, RTGS is the initiator
21 Connected reference Reference of message МТ 920
– TRN, which initiated the
message
25 Account number yes Number of account to which
the message refers
28C Balance number/Message sequence yes Balance number is the ordinal
number of balance which is
sent for the specified account
from the beginning of the year.
If the balance is sent in several
messages, such messages are
to be numbered within a
sequence (from 1 onwards)
34F Currency code (for dinars: RSD), letter C for yes Example:
credit or D for debit and amount; the amount RSDC100000,
refers to the limit below which transactions are
not included in the report
34F Currency code (for dinars: RSD), letter C for Example:
credit or D for debit and amount; the amount RSDD100000,00
refers to the limit below which transactions are
not included in the report
13D Date and time, in format YYММDDHHММ yes Example:
 .
10

0307171515+0100
61 Statement line *1
90D Number of debit transactions, currency code Example:
and amount 12RSD100000,00
90C Number of credit transactions, currency code Example:
and amount 122RSD200000,99

Field 61 is repeated for each in the statement.

Format of field 61:
value date (YYММDD),
credit/debit (C, D, EC, ED),
amount (up to 12 integers, up to 2 decimal places),
transaction type identifier code, 1+3 characters,
reference for account holder, up to 16 characters
//,
reference of the institution servicing the account, up to 16 characters,
additional details, up to 34 characters.

11. Message МТ 950 – Statement message

Message МТ 950 is an account statement. It is sent automatically at the end of the

day. Message elements are as follows:

Field Message elements Obligatory Note

20 Reference yes TRN, RTGS is the initiator
25 Account number yes Number of account to which
the message refers
28C Balance number/Message sequence yes Balance number is the ordinal
number of balance which is
sent for the specified account
from the beginning of the year.
If the balance is sent in several
messages, such messages are
to be numbered within a
sequence (from 1 onwards)
60F Opening balance in the form (D/C), date, yes Example:
currency code, amount C030717RSD100995,01
61 Statement line *1
62F Closing balance in the form (D/C), date, yes Example:
currency code, amount C030717RSD200996,

Field 61 is repeated for each in the statement.

Format of field 61:
value date (YYММDD),
credit/debit (C, D, EC, ED),
amount (up to 12 integers, up to 2 decimal places),
transaction type identifier code, 1+3 characters,
reference for account holder, up to 16 characters
//,
reference of the institution servicing the account, up to 16 characters,
additional details, up to 34 characters.

12. Message МТ 940 – Customer statement message (with

details)

*1 See: SWIFT User Handbook.

 .
11

Message МТ 940 is an account statement. It is sent automatically at the end of the

day, if the member wishes so. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN, RTGS is the initiator
25 Account number yes Number of account to which
the message refers
28C Balance number/Message sequence yes Balance number is the ordinal
number of balance which is
sent for the specified account
from the beginning of the
year. If the balance is sent in
several messages, such
messages are to be
numbered within a sequence
(from 1 onwards)
60F Opening balance in the form (D/C), date, yes Example:
currency code, amount C030717RSD100995,01
61 Statement line *1
86 Information to the account holder, with 103 Up to 6*35 characters
50К, 59 (accounts only) and 4 lines for 70,
with 202 only 53А and 58А (accounts only)
62F Closing balance in the form (D/C), date, yes Example:
currency code, amount C030717RSD200996,

Field 61 is repeated for each in the statement.

Format of field 61:
value date (YYММDD),
credit/debit (C, D, EC, ED),
amount (up to 12 integers, up to 2 decimal places),
transaction type identifier code, 1+3 characters,
reference for account holder, up to 16 characters,
//,
reference of the institution servicing the account, up to 16 characters,
additional details, up to 34 characters.

13. Message МТ 970 – Clearing statement message

Message МТ 970 is a clearing account statement. It is sent automatically at the end of

the session. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN, RTGS is the initiator
25 Account number yes Number of account to which
the message refers
28C Balance number/Message sequence yes Balance number is the ordinal
number of balance which is
sent for the specified account
from the beginning of the
year. If the balance is sent in
several messages, such
messages are to be
numbered within a sequence
(from 1 onwards)
60F Opening balance in the form (D/C), date, yes Example:
currency code, amount C030717RSD100995,01
1
61 Statement line *

*1 See: SWIFT User Handbook.

 .
12

86 Information to the account holder, with 103 Up to 6*35 characters

50К, 59 (accounts only) and 4 lines for 70,
with 202 only 53А and 58А (accounts only)
62F Closing balance in the form (D/C), date, yes Example:
currency code, amount C030717RSD200996,

Field 61 is repeated for each in the statement.

Format of field 61:
value date (YYММDD),
credit/debit (C, D, EC, ED),
amount (up to 12 integers, up to 2 decimal places),
transaction type identifier code, 1+3 characters,
reference for account holder, up to 16 characters,
//,
reference of the institution servicing the account, up to 16 characters,
additional details, up to 34 characters.

14. Message MT x92 – Message cancellation request7

Field Message elements Mandatory Note
20 Reference yes TRN
21 Connected reference yes TRN of the message to
which the query refers
11S МТ yes To supplement the
Date of original message unique key
Session and sequence of the original message
79 BIC of participant who sent the message and yes
value date

Message MT 192 is used for messages МТ 103 and МТ 102, while message MT 292 is used
for message МТ 202.

15. Message МТ x95 – Message query

Message МТ х95 is used as a query on the previously sent message МТ 103 or МТ

202. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN
21 Connected reference yes TRN of the message to
which the query refers
75 Queries yes Requests:
STAT – message status
DUPL – message
duplicate
PRTY – priority
77А New priority on the change of priority Mandatory for request
for change of priority,
not used with other
requests
11S МТ To supplement the
Date of original message unique key

*1 See: SWIFT User Handbook.

7
Used only in systems with active centralised wait lists.
 .
13

Session and sequence of the original message

79 BIC of participant who sent the message and yes
value date

Message MT 195 is used for messages МТ 103 and МТ 102, while message MT 295
is used for message МТ 202.

16. Message МТ x96 – Responses to requests, queries and

messages on error

Message МТ х96 is sent as a response to messages МТ х92 or МТ х95, or the

system response to a message with an error. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN
21 Connected reference yes TRN of the message to
which the query refers
76 Responses yes Responses to requests:
STAT – message status
DUPL – message
duplicate
PRTY – priority
77А Textual description On the occurrence of
errors, and an
appropriate text if the
response contains a
message on the error
11R МТ yes To supplement the
date of the original message unique key

If status is requested (STАТ), field 76 may contain the following responses:

STAT Message has been cancelled by the МТn92 message sent by a participant.
REJT
STAT Message has been cancelled pursuant to the rules of the system, it is sent even when the
CANC system rejects a message, without any particular request.
STAT Message execution is underway.
EXEC
STAT Message has been settled.
SETL
STAT An error occurred during the processing of a non-financial message, it is sent even when the
ERRC NBS rejects a message on account of an error in the message, without a particular request.
STAT An error occurred during the processing of payment, it is sent even when the NBS rejects a
ERRP message on account of an error in the message, without a particular request.
STAT Message is waiting for connected conditional payments.
COND
STAT Message is on wait list.
WAIT
STAT Message is suspended.
SUSP
STAT Message is accepted for clearing. Participants may cancel it.
NETR
STAT Message is settled after the clearing procedure. It cannot be cancelled.
NETS
STAT Message is accepted for clearing with the value date on the next day. It can be cancelled.
NETL
STAT Message is not cancelled during the clearing procedure but it is not settled. It can be cancelled
NETE if the clearing procedure is cancelled.
 .
14

ERRC and ERRP are received even when the message is cancelled due to error,
without any particular request. Message MT 196 is used for messages МТ 103 and МТ 102, while
message MT 296 is used for message МТ 202.

17. Message МТ 985 – Status enquiry

Message МТ 985 is used for sending status enquiries. The response thereto is sent
via message МТ 986. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN
57А BIC of the institution with which the account is yes
held
59 Account to which the enquiry refers, slash and yes
BIC of account holder in front of the account
75 Request yes Requests:
STAT – account status
SQDC – report on the
wait list
TTLS – clearing
session totals, session
after the slash (title:
MORNING, EVЕNING
or FINAL) and date
(YYMMDD)
TTLD – clearing day
totals, date after the
slash (YYMMDD)
PCLT – currently set
and/or used clearing
limit

18. Message МТ 986 – Status report

Message МТ 986 is sent as a response to status enquiry.

Field Message elements Mandatory Note

20 Reference yes TRN
21 Reference of the message to which the report yes
refers
59 Account to which the report refers, slash and BIC
of account holder in front of the account
79 Response yes

Possible responses to STAT enquiry:

Response Meaning
АА Account is not blocked.
DA Account is blocked for debit.
AC Account is blocked for credit.
DC Account is blocked.
 .
15

The response to query SQDC contains 4 lines. Each consists of a code – 2 characters,
currency code – 3 characters, total amount, a slash and the total number of messages. The codes are
the following:

Code Meaning
SD Sum and number of suspended transactions crediting the
account
SC Sum and number of suspended transactions debiting the
account
ED Sum and number of transactions on the wait list crediting the
account
EC Sum and number of transactions on the wait list debiting the
account

The response to queries TTLS and TTLD contains data on the request – 1 line, the number of
received messages – 1 line in format: (received/accepted/rejected) and accepted, cleared, on the wait
list and rejected messages – 4 lines in format (amount/number of messages/number of instructions) in
session and/or clearing day.
A participant receives the message TTLS automatically after each clearing, without request.
The response to query PCLT contains data in the following sequence: the limit level, available account
balance and potential position for the next cycle.
A participant receives the message PCLT automatically from the system in pre-clearing of the third
cycle.

19. Меssage МТ 999 – Free format message

Message МТ 999 is a free-format message. Message elements are as follows:

Field Message elements Mandatory Note

20 Reference yes TRN
79 Text of the message, in the first line: yes BIC of the recipient in
/TEXTMESSAGE/BIC the outcoming, and of
the sender in the
incoming message

or, for setting the clearing limit, the field contains: I is used for an
/SETACCOUNTLIMIT/CLEARING increase, D for a
/STATUS/ decrease in the limit
/ACTION/ amount, new limit
/DIRECTION/I or D amount is entered for
/ACCOUNT/account number the account
/AMMOUNT/amount

/GETBUSINESSDAYPERIOD/

Report request on the

:20:R8172855/999 business day period
:21:890310001256780c
:79:Ok

Note: in case the operator sets the limit, the bank receives МТ999 on the set limit as a notice, and words
SETACCOUNTLIMIT shall be followed by the title of the limit.

МТ999 is also used as an answer to the correctly accepted МТ998. Message elements are as follows:
 .
16

Field Message elements Mandatory Note

20 Reference yes TRN
21 Reference of the message to which the response refers. yes
79 Ok
 .
17

Schedule 2

Own format messages – extension of standards

1. Own format messages

SWIFT message МТ 998 is used an envelope for own format messages in the NBS payment system.
Within this framework, own format messages are defined as an extension of standards.

Fields that are used in MT 998 message are given in the table below. Subfields of 77E field are made of
standard SWIFT format fields. Within 77E field, 79 field is used, whose subfields may be in their own format.
This document presents the ways of using own format message subtypes.

Field Message elements Mandatory Note

20 Reference yes TRN
12 Message subtype yes Own message subtype in
the message envelope.
Designations of permitted
subtypes must be from the
set stated below.
77Е Contents of message envelope which corresponds to the stated yes In the NBS payment
own format message subtype system, contents of an
own format message
envelope are only made of
fields standardised in
advance in line with
Guidelines.

59A BIC of the recipient yes

54А BIC of the sender
21 Connected reference
Other fields by SWIFT standard if used in a specific own
format message
79 Own format fields Only a hyphen is
mandatory in the first line,
own format fields do not
have a colon at the
beginning

Permitted own format message subtypes are given in the following table:

Subtype Subtype title Use

designation
SMT710 Information on the grounds for Banks send to the enforced collection organisation data on the
execution grounds for execution

SMT713 Information on account Organisations entitled to enforced collection through the NBS
blocking payment system send to banks information on blocking of all
accounts of a client with the specified personal ID number

SMT714 Information on account After completed enforced collection information is sent on

unblocking unblocking of all accounts that were blocked by a
reference-bearing single message from group message
of the SMT713 subtype
SMT718 Information on balance of Banks send information on the balance of blocked accounts on
 .
18

blocked account the basis of received individual message from the group
message of SMT 713 subtype
SMT719 Request for funds transfer Funds transfer from blocked account is requested with message
SMT 719
SMT720 Information on funds After the final execution of funds transfer, the bank uses this
transferred message to send information on the funds transfer to the
blockade initiator

SMT796 Information on own format It is used as a response to an own format message that
message error due to error could not be processed
SMT730 Request for debit transfer Request for funds transfer sent by one bank to another

SMT731 Information on accepted or Response to message SMT 730

rejected request for debit
transfer

SMT501
SMT502
SMT549 Types of messages whose contents are regulated by the Guidelines for the Format and Purpose of
SMT509 Messages for Data Exchange Between Participants at Auction Securities Trading
SMT515

The text below contains the description of field formats of own format messages 77E for messages
7XX. Messages 5XX are explained in detail by the Guidelines for the Format and Purpose of Messages for Data
Exchange Between Participants at Auction Securities Trading.

2. Message SМТ 710 – data on the grounds for account blocking

Message SМТ 710 is used as a transfer of data on the grounds of blocking the beneficiaries’ accounts
with specified ID numbers. Message elements in :79: field are as follows:

Field Message elements Mandatory Note

71010: Account number, beginning with a slash Account number that the
blockade refers to, if
known
71020: Account title Account title to which the
blockade refers to, if
known, 35 characters

71030: Holder’s ID number yes Mandatory, blockade

follows the ID number

71040: Holder’s tax identification number yes Mandatory

71051: Type of document yes 10 – bills and
authorizations without a
warranty,
20 – bills and
authorizations without a
warranty on the burden of
the main debtor
30 – bills and
authorization on the
warrantor’s burden

71052: Date and time of receipt yes YYMMDD HH:MM:SS

 .
19

71053: Maturity date yes YYMMDD

71054: Priority yes 01 to 10
71056: Execution amount (uncollected amount) and/or forbidding yes
disposal
71059: Document number, number of court yes А35
decision, number of acceptance order

Details of account blocking, fields in message MT103 Fields are designated with:
format (57A, 59, 70 and 72), which is to be executed so that 57A:, 59:, 70: and 72:
enforced collection is completed
71070: If disposal is forbidden – date until it is forbidden or word VEFIFY – data from the
PERMANENT if there is no term; in case of enforced order are reliable and
collection – bank’s confirmation that data are reliable and accurate
accurate

71090: Date of yes In format YYMMDD

Message MT 998 is used as an envelope.

3. Message SМТ 713 – data on account blocking

Message SMT 713 is the group message for blocking all clients’ accounts with specified ID numbers. It
consists of maximum 50 individual messages on blocking (in the previous version: message SMT 711). The
fields used in message SMT 713 are given in the following tables.

Message MT 998 is used as an envelope and therefore message SMT 713 consists of two parts. The
message heading contains the following fields:

Field Message elements Mandatory Note

20 Reference yes TRN of group message
SMT 713
12 Message subtype yes Own format message
subtype found in the
message – SMT 713
77Е The contents of the message envelope corresponding to the yes In the NBS payment
stated own format message subtype system, own format
message envelope contents
consists solely of
previously standardised
fields in line with the
Guidelines
59A BIC of the recipient yes
54A BIC of the sender yes

The second part of the message consists only of field 79, which is repeated as many times as there are
individual blockages in message SMT 713, with message elements in field :79: as follows:

Field Message elements Mandatory Note

79 Own format fields Only a hyphen is
mandatory in the first line,
own format fields do not
have a colon at the
beginning

71310: Ordinal number yes Ordinal number of an

individual message within
a group message of length
 .
20

2
In an order from 01 to 50
20: Reference yes TRN of individual
blockade
21: Connected reference yes Being referenced to itself,
the same as in the previous
field 20:
11А: BIC, MT and date of the original message yes For supplement of unique
key, in 79
71130: Debtor’s ID yes Mandatory, blockade by
the ID number
71140: Debtor’s tax ID number yes Mandatory
71150: Currency designation and initial amount of the blockade yes Example
balance RSD200996,10
71190: Date of change yes In format YYMMDD

In case of further referencing during the sending of messages, referencing is done in respect of
individual blocking within message SMT 713 and/or message SMT 718 in field 21 (connected reference) – its
contents are as in field 20 of individual blockade, within field 79 of message SMT 713.

4. Message SМТ 714 – data on account unblocking

Message SMT 714 is a group message of unblocking of all clients’ accounts with specified ID numbers. It
consists of maximum 50 individual messages on unblocking (in the previous version of SMT 712). Fields used
in message SMT 714 are given in the following tables.

Message MT 998 is used as an envelope, and therefore message SMT 714 consists of two parts. The
message heading contains the following fields:

Field Message elements Mandatory Note

20 Reference yes TRN of group message
SMT 714
12 Message subtype yes Own format message
subtype found in the
message envelope –
SMT 714

77Е Contents of message envelope corresponding to the specified yes In the NBS payment
own format message subtype system, own format
message envelope
contents consist only of
previously standardized
fields in line with
Guidelines

59A BIC of the recipient yes

54A BIC of the sender yes

SMT 714 message has no field 21 in its first part as it cannot have reference to a group message due to lack of
data comprised for the same personal ID numbers.

The second part of the message consists of field 79 only, which is repeated as many times as there are
individual unblockings within SMT 714 message itself, with message elements in field :79: as follows:

Field Message elements Mandatory Note

79 Own format field In the first line, only a
hyphen is mandatory,
own format fields do not
 .
21

have a colon at the

beginning
71410: Ordinal number yes Ordinal number of
individual message
within one group
message of length 2
In sequence from 01 to
50
20: Reference yes TRN of individual
unblocking
21: Connected reference yes TRN of individual
blockade that unblocking
refers to
11А: BIC, MT and date of original message yes For supplement of
unique key, in 79
71210: Debtor’s personal ID number yes Mandatory, unblocking
is under the personal ID
number, in 79

71240: Debtor’s tax ID number yes Mandatory

71290: Date of transaction yes In format YYMMDD

Field 21 in the second part of SMT 714 message has contents as in field 20 of individual blocking (in field 79) to
which unblocking refers.

5. Message SМТ 718 – Information on balance of blocked account

Message SMT 718 is used for transmission of information on the balance of blocked account. Message elements
in :79: field are as follows:

Field Message elements Mandatory Note

11А: BIC, MT and date of original message yes For supplement of
unique key, in 79
71810: Owner’s ID number yes Mandatory,
unblocking is under
the personal ID
number, in 79

71820: Number of account starts with slash yes Number of account

blocked
71830: Designation of currency and account balance yes Example
RSD200996,10
71840: Owner’s tax and ID number yes
71890: Date and time of change yes In format:
YYMMDD HHMM

MT 998 is used as an envelope.

6. Message SМТ 719 – request for funds transfer upon account

blocking

Message SМТ 719 is used as a request for funds transfer from the blocked account, with message
elements in field :79: as follows:

Field Message elements Mandatory Note

11А: BIC, MT and date of original message yes To supplement the
 .
22

unique key in 79
Data on blocking, fields in message MT 103 (32A, 57А, 59, yes Format 32A, 57А:,
70 and 72), which is to be executed so that enforced collection 59:, 70:, 72:, in 79
is completed
71910: ID number yes Account owner’s ID
number
71920: Account number starts with slash yes Number of account
blocked
71940: Tax ID number yes

MT 998 is used as an envelope.

7. Message SМТ 720 – confirmation of funds transfer upon account

blocking

Message SМТ 720 is used as a confirmation of funds transfer from the blocked account, with message
elements in field :79: as follows:

Field Message elements Mandatory Note

11А: BIC, MT and date of original message yes To supplement the
unique key in 79
Data on blocking, fields in message MT 103 (32A, 57А, 59, yes Format 32A, 57А:,
70 and 72), which is to be executed so that enforced collection 59:, 70:, 72:, in 79
is completed
72010: ID number yes Account owner’s ID
number
72020: Account number starts with slash yes Number of account
blocked
72040: Tax ID number yes

MT 998 is used as an envelope.

8. Message SМТ 796 – message on error for own format messages

Message SМТ 796 is used as a response to an own format message that could not be processed due to
an error, with message elements in field :79: as follows:

Field Message elements Mandatory Note

11А: BIC, MT and date of original message yes To supplement the
unique key in 79
79610: Code and description of error yes Two-digit code and
text of the description
of the error due to
which the message
could not be
received, with
maximum length of
42 characters

MT 998 is used as an envelope.

9. Message SМТ 730 – request for debit transfer

 .
23

Message SМТ 730 is used as a request for debit transfer. The transfer is made by message MT 103 or
МТ 202, with connected reference to message SMT 730 that initiated the transfer. If transfer requirements are
not met, the transfer is rejected by message SMT 731.

Field Message elements Mandatory Note

73010: Account number, starts with slash yes Number of account
being debited, in 79
73020: Account title Title of the account
being debited, if
known,
3*35 characters
Fields 32A, 57А, 59, 70 and 72 of MТ 103, which are Format 32A:, 57А:,
expected in transfer 59:, 70: and 72:
73080: Additional information on debit Descriptively, 6*35
characters
73090: Date of change yes In format
YYMMDD
73091: Priority Collection priority
01-10, in line with
Law

MT 998 is used as an envelope.

10. Message SМТ 731 – information on accepted or rejected request

for debit transfer

Message SМТ 731 is used as a response to a syntactically correct message SMT 730, with message
elements in field :79: as follows:

Field Message elements Mandatory Note

11А: BIC, MT and date of original message yes To supplement the
unique key, in 79
73110: REJECTED-‘reason’ or ACCEPTED yes After REJECTED,
hyphen is followed
by a code and the
description of reasons
why the message was
not executed, in 79

MT 998 is used as an envelope.

 .
24

Schedule 3

Use of Cyrillic letters in SWIFT messaging

As the use of Cyrillic letters is not allowed in SWIFT messaging, such letters have to be
coded/decoded into Latin characters for all fields, where deemed reasonable, according to the
following table:

Cyrillic letter Latin code Cyrillic letter Latin code

А A а a
Б B б b
В V в b
Г G г g
Д D д d
Ђ DJ ђ dj
Е E е e
Ж ZZ ж zz
З Z з z
И I и i
Ј J ј j
К K к k
Л L л l
Љ LJ љ lj
М M м m
Н N н n
Њ NJ њ nj
О O о o
П P п p
Р R р r
С S с s
Т T т t
Ћ CC ћ cc
У U у u
Ф F ф f
Х H х h
Ц C ц c
Ч CH ч ch
Џ DZ џ dz
Ш SS ш ss