Bank transfers - CBI technical standards

Payments - Bank transfers
CBI - Technical standards
References
Subject:
Document Code:
CBI-BON-001
Release:
v. 6_16 Pages
File name:
CBI-BON-001_6_16
Most recent update:
14 February 2014
Creation date:
31 January 2005
Author:
Consorzio CBI
Reviewed by:
GdL Standard
This document includes material subject to regulation by the CBI mark.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 2/40
2014
Updates and revisions

LIST OF AMENDMENTS MADE TO PREVIOUS RELEASES
(Release 6.16 February 2014)
Date
Release
23
5.0
December
2004
With CBI Communication

effect
from
7
March
2005
Function
Network message of Bank transfer

23 December 2004
2.6
Record type 20
Payment
orders
2.6
Record type 20
Payment
orders
2.10
Record type70
Entering new field Flow

qualifier (position 31-37)
Payment
orders
2.10
Record type70
Entering new field MP Code

(position 38-42).
6.3
Payment
order advice
Record type 10
Entering new field Flow

qualifier (position 102-108)
6.3
Payment
order advice
Record type 10
Entering new field MP Code

(position 109-113).
Foreign bank 4.5

transfer
orders
Record type P1
Rejection of filler zeros for

CUX_5402
field
the
(position 41-52)
Payment
orders
31
January
2005
5.0
8
April 5.01
2005
Paragraph Paragraph Title Modification description
9 May Circular 1/2005

2005
9 May Network Message

2005
Bank transfer
21 Nov Circular7/2005
2005
Entering the validity check

on the Taxpayer's code
(position 101-116)
Bank transfer
6.1
Payment
order advice
2
Nov 5.02
2005
Entering the Taxpayer's

code (position 101-116) of
a new ABI [Italian Banking
Association] code 03262
Record type EP
Entering new fields that

form the Flow qualifier
string (position 31-37)
Bank transfer
Payment
orders
2.3
Record type 10
Payment
2.3
Record type 10
This document includes material subject to regulation by the CBI mark.
Entering new reasons

ZZ000 and ZV000 in the
reason field (pos. 29-33).
The field becomes
alphanumeric.
The Payee Account field
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 3/41
2014
orders
Payment
orders
2.3
Record type 10
Payment
orders
2.3
Record type 10
Payment
orders
2.3
Record type 10
Payment
orders
2.3
Record type 10
(pos. 80-91) becomes

optional for transfers with
reason ZV000 (reason field
pos. 29-33)
The Company Code field
(pos. 92-96) is compulsory
should the reason be ZV000
(reason field pos. 29-33)
and the Payee Account (pos.
80-91) not show a value.
The Code Type field (pos.
97) is compulsory should
the reason be ZV000
The payee customer code
(pos. 98-113) is compulsory
should the reason be ZV000
Additional information: for
reasons ZZ000 and ZV000,
the method of payment field
(pos. 114) must show either
blank or 1).
1
June 5.03
24 July Network message of 1 Bank transfer
2006
2006
June 2006
In the event of bank transfers showing the reason ZV000, the information on the recipients account details and the information on
the recipients company account details are not to be both present at the same time.
Payment orders 2.3
Record type 10
The Bank Code field (pos. 70-74) is

optional for bank transfers showing
the reason ZV000; the field is missing
if the reason is ZV000 (pos. 29-33)
and all the fields referring to the
ordering companys account details
(positions 92-113) show a value
Payment orders 2.3
Record type 10
Bank CAB field (pos. 75-79) optional

for transfers showing the reason
ZV000; field missing is the reason is
ZV000 (pos. 29-33) e and all the
fields referring to the ordering
companys account details (positions
92-113) show a value
Payment orders 2.3
Record type 10
Payee Account field (pos. 80-91)

optional for transfers showing reason
ZV000; field missing if the reason is
ZV000 (pos. 29-33) and all the fields
referring to the ordering companys
account details (positions 92-113)
show a value
Payment orders 2.3
Record type 10
Company Code (pos. 92-96) field
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 4/41
2014
missing if the reason is ZV000 (pos.
29-33) and the fields referring to the
recipient bank (record type 10, pos.
70-91 or record type 17) show a value
28 July 6.00
2006
Starting
Porting
service
Payment orders 2.3
Record type 10
Payee Customer Code (pos. 98-113)

missing if the reason is ZV000 (pos.
29-33 and the fields referring to the
recipient bank (record type 10, pos.
70-91 or record type 17) show a value
Payment orders 2.3
Record type 10
Payment orders 2.6
Record type 20
Payment orders 2.5
Record type 17
Code Type field (pos. 97) missing if

the reason is ZV000 (pos. 29-33) and
the fields referring to the recipient
bank (record type 10, pos. 70-91 or
record type 17) show a value
Entering new ABI codes in the
Taxpayers Code field (pos. 101-116)
Record type 17 missing for reason
ZV000 and entering a value for the
Company account details (rec. 10,
positions 92113)
of Circular
7/2006
Inclusion of references to the New CBI Architecture, in particular to the Directory (cf. document DIRECTORY-MO-001).
Removal of references to the previous CBI Service operating model.
Payment orders
Removal of the Payment Orders

Authentication paragraph
Payment orders
Removal of the Overseas bank

transfer
orders
authentication
paragraph
Payment orders 2.3
Record type 10 Additional information on the check

to be carried out on the Code Type
field (pos. 97)
15 Dec 2006
Payment orders 2.3
Record type 10
15 Dec 2006
Foreign
bank 3.13
transfer orders
12 Feb 2007
Payment orders 2.3
12 Feb 2007
Payment orders 2.3
12 Feb 2007
Payment orders 2.5
15 Dec 6.01
2006
Circular
9/2006
Additional information on the checks
to be carried out on the Ordering
partys account (pos. 58-69) and
"Payee Account " (pos. 80-91)
Additional information on the checks
Record type P9 to be carried out on the CVS bank
field (pos. 55- 59)
Definition of rules to assign a value
Record type 10 for the recipient bank details (pos. 7091) should the reason be ZV000
Record type 10 for the Ordering Company account
details (92-113) should the reason be
ZV000
Record type 10 for Record type 17 should the reason
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 5/41
2014
be ZV000
20 Feb 6.01
2006
20
6.02
March
2007
ABI
Network
message of
20 Dec 2006
Payment orders 2.6
Record type 20
Payment orders 2.3
Record type 10
order 4.3
Record type 10
Payment orders 2.5
Record type 17
Network
message of
20 Mar 2007
Payment
advise
20 Dec 6.03
2007
Inclusion of a further compulsoriness

condition for Company Code,
Code Type and Payee Customer
Code fields.
Expression of the algorithm required
to check the validity of the
Reference Code field.
Removal of references to the previous
Network Infrastructure
3 June 2008 Network

message of
20 Dec 2007
2.4
Payment
advise
order 4.3
4.3
28 Mar 6.04
2008
Amendment of the note referring to

the ordering partys taxpayer code
Order
overseas
transfer
for 3.5
bank
Order
overseas
transfer
for 3.13
bank
Additional information on the

enforcement of compulsoriness for
the IBAN code. The checks to be
made on the individual fields are
explained better
.
The checks to be made on the
Record type 16 individual fields are explained better.
The type of check for the Anomaly
Record type 10 Type field (pos. 100-100) has been
corrected; the type of check must be
V.
The check of the Reference Code
Record type 10 field (pos. 60-94) has been corrected.
The types of checks to be made on the
Record type P1 fields currency on which debit
account is held (pos. 35-52) and
currency on which credit account is
held (pos. 53-70) are explained
better
3 June 2008 Circular

2/2008
3.13
3.13
Entry of new codes in the FTX_4451

Record type P9 field (pos. 17-19): CVA and
CDV;
REG code deleted
The CVS date filed was deleted
Record type P9 (pos. 20-27)
The customs clearance date field
Record type P9 was renamed (pos. 28-35) into
transaction date
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 6/41
2014
3.13
29 May 6.05
2008
3 June 2008 Network

message of
30 May
2008
Payment orders 2.3
Date Relea
se
With
effect
from
CBI
Communica
tion
Function
01 Jan 6.07
-2009
Record type 10
Paragraph Paragraph
Title
Payment orders 2.5
Record type 17
order 4.3
Record type 10
Payment orders 2.3
Record type 17
Payment orders 2.3
Record type 0
Payment
advice
31 Jul - 6.06
2008
The following fields were deleted:

Tipo record P9 CVS number (pos. 43-54), CVS
bank (pos. 55-59), Decanalised
indicator (pos. 83), Goods returned
indicator (pos. 84), Transport and
insurance costs (pos. 85-102)
A reference to the anti-recycling

regulations was introduced in note n.
1 (pos. 114)
Modification description
Addition of further information about

the current use of the IBAN code
which does not mean any change in
the diagnostic checks
A reference to the anti-recycling
regulations was introduced in note n.
4 (pos. 101)
31 Jul 2008 Network

message of
31 Jul -2008
Addition of further information about
the current use of the IBAN code
which does not mean any change in
the diagnostic checks
1 Mar 2010 Network

message of
16 Feb 2010
2.3
Record type
0
2.3
Record type10
2.3
Record type 10
2.5
Record type 17
The order execution date description

was changed (pos. 17-22). A note was
added for the forwarding agent the
about a consistency check with the
transaction date.
The field name pos.23-28 was
changed from payee value date into
payee bank value date together with
the description. A note was added for
the forwarding agent the about a
consistency check with the transaction
date.
Checks on field pos 70-74 about its
relation with reasons 34000 and
79000 were cancelled. These checks
were moved on the same field of
record 17.
Payees coordinates are no longer
mandatory for payment methods
equal to blank or 1..
This record becomes mandatory for
payment methods equal to blank or
27 Apr 6.08
-2010
03
June
2010
6.08
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 7/41
2014
2.10
Record type 70
The unique code filed check was

changed (pos. 71-100).
A suggestion on how to use
Record type P3 intermediary bank operation wad
added
for 3.7
bank
Payment
advice
order 4.3
Record type 10
4.3
Record type 10
4.3
Record type 10
The Unique code field (pos. 11- 40)

becomes optional.
Changes made to the compulsoriness
rule of field pos. 60-94 (reference
code) for the Anomaly type value in
pos. 100-100
The Anomaly type field in (pos.
100-100 was changed)
SUSPENDED Network
message of
28 Apr 2010
Order
overseas
transfer
for 3
bank
Order
overseas
transfer
for 3.5
bank
Order
overseas
transfer
for 3.13
bank
Order
overseas
transfer
for 3.13
bank
The total number of PE transaction

records was corrected
Record type P1 The description of currency code

fields, but not the type of check, was
modified pos. 32-34, 38-40, 56-58)
The record type was modified
Record type P9 according to the Bank of Italy
measure of 16 December 2009
A flag in pos. 102 was introduced to
Record type P9 identify the transaction type
Corrections
SUSPENDED
for 3
bank
Introduction
An error about the total number of PE

transaction records was corrected
6 Jun 2011
Payment order
5 Apr 6.10
2011
Record type 70
Order
overseas
transfer
Order
overseas
transfer
24 Nov 6.09
2010
2.10
1 and reason which does not equal

ZV000 except in cases where RID
users are refunded when all fields
referring to the Ordering Companys
details are assigned a value.
Addition of value 4 to REQUEST
FLAG (pos. 70-70).
Urgent payments management
6 Jun 2011
Payment order
Urgent payment managements advices
20 Feb 6.11
2013
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 8/41
2014
1 Feb 2014
Network
message of
20 Feb 2013
Order
overseas
transfer
13
6.12
Mar20
13
1 Jul 2013
for 3.6
bank
Urgent payment managements Record type PH advices
Network
message of
20 Mar 2013
SEPA payment management
Payment order
Payment
advice
18 Apr 6.13
2013
1 Jul 2013
SEPA payment/advice management
order
Network
message of
19 Apr-2013
SEPA payment management
Payment order
22 Oct 6.14
2013
20/01/ 6.15
2014
1 Feb 2014
Network
message of
23 Oct-2013
2.3
Record type 10
Payment order
2.3
Record type 10
Payment order
2.5
Record type 17
Payment order
2.4
Record type 16
County Code Field:

comment at foot of page
modified
Payment order
2.5
Record type 17
County Code Field:

comment at foot of page
modified
1 Feb 2014 Circular

CBI 1/2014
Order
overseas
transfer
14/02/ 6.16
2014
Field Ordering company's details

(pos.92-113) deleted
Field payee account pos. 80-91:
presence rule removed
New mandatory rule introduced
Payment order
for 3.6
bank
Record type PH Added the web link for EPC409-09

table
2.5
Record type 17 Changes made to following fields:

Check Digit and account number. V
control introduced.
31 mar 2014 Network

message of
24/02/2014
Payment order
Order
overseas
transfer
for 3.13
bank
Record
type Record optionality introduced.
P9
- CVS
details
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 9/41
2014
Table of contents
1
INTRODUCTION ................................................................................................ 11
PAYMENT ORDER FUNCTION ....................................................................... 12
2.1
Head record structure - fixed code "PC".............................................................................................. 12
2.2
Tail record structure - fixed code "EF" ................................................................................................ 14
2.3
Record structure fixed code 10 ....................................................................................................... 14
2.4
Record structure fixed code 16 (payer's coordinates) ................................................................... 17
2.5
Record structure fixed code 17 (payee's coordinates) ................................................................... 18
2.6
2.7
2.8
2.9
Record structure fixed code 50/60 .................................................................................................. 21
2.10
OVERSEAS BANK TRANSFER ORDERS FUNCTION ................................. 24
3.1
Head record structure - fixed code "PE" .............................................................................................. 24
3.2
3.3
Record structure - fixed code H1 Header message ........................................................................... 25
3.4
Record structure - fixed code P0 Method of Payment .................................................................... 27
3.5
Record structure - fixed code P1 Amount ........................................................................................ 28
3.6
Record structure - fixed code PH Bank and current account ........................................................ 30
3.7
Record structure - fixed code P3 Description of bank ..................................................................... 30
3.8
Record structure - fixed code P4 Payer ............................................................................................. 31
3.9
Record structure - fixed code P5 Payee ............................................................................................. 31
3.10
Record structure - fixed code P7 Bank transfer references ............................................................. 32
3.11
Record structure - fixed code P8 Bank transfer references (structured) ....................................... 33
3.12
Record structure - fixed code P9 ....................................................................................................... 34
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 10/41
2014
PAYMENT ORDER RESULT FUNCTION ...................................................... 35
4.1
Head record structure - fixed code "EP" .............................................................................................. 35
4.2
4.3
4.4
4.5
4.6
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 11/41
2014
1 Introduction
This document defines the technical standards of flows relative to the "Bank transfer" function and, in particular:
-
Payment orders (ordinary and urgent)
Foreign bank transfer orders
Payment order result
Please refer to the relevant regulations issued by the competent bodies governing this function, as well as aspects
regarding the functioning of the technological infrastructures and their related applications.
For rules governing the representation and composition of flows exchanged when the "Corporate Banking
Interbancario - CBI" service is provided, please consult the document CBI-STD-001, which must be used as a
reference for all documents describing the various active CBI functions and which may also document any
exceptions or particularities.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 12/41
2014
2 Payment order function

Each order consists of 6 compulsory records (or 12 records if records 16, 17 and 60 are used) containing 120
characters each in the following sequence:
1st
10
2nd
16
3rd
17
4th
20
5th
30
6th
40
50/60
7th
8th
70
The group of orders is preceded by a head record and followed by a tail record, each consisting of 120
characters:
head record PC
tail record EF
Any field containing amounts present in the records set out below must never contain the "," and the two final
positions of these amounts are considered decimal places.
2.1 Head record structure - fixed code "PC"
position
c/o type
field name
check
contents
1-
Filler
blank
2-3
an
record type
"PC"
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 13/41
2014
4-8
an
sender
sender company code assigned by the SIA;

registered in the directory
9-13
Recipient
ABI code of the payer bank responsible for

processing the payment orders; registered in
the directory;
14-19
creation date:
date on which the "flow" is created by the

sender company, entered as DDMMYY
20-39
an
support name
open field available to the sender company;

this must have the same creation date and be
the same for both sender and receiver. 1
40-45
an
available field
field available to the sender company
46-104
Filler
Blank
105-111
Flow qualifier
This field is optional. It becomes compulsory

exclusively for operations not governed by
ordinary reference rules.
The field consists of three sub-fields, as given
below
105 o
an
Flow type
This has the value:

1 = operations generated as part of Market
Place activities
106 o
107-111
an
Flow qualifier
Shows the fixed value $
Transmitter Party
If the two preceding sub-fields are validated

with the values provided, the ABI code of the
Gateway MP Bank must be indicated.
Blank
It can take the following values:
blank = Standard payment
U = Urgent payment2.
If in the field is the U value is present, the
logical support must contain only one
payment transaction. This field has to be the
same in all the transactions in the support
(cfr. Record 10
pos.119) and in the tail record (cfr. Record
112
filler
113
an
Flag priority management V

payment
EF pos. 113)
114 -
an
currency code
Shows the fixed value E (EURO). This

field must be validated in the same way in all
of the orders in the support (see record 10,
position 120) and in the tail record
115 -
filler
Blank
This identifier must be quoted by the bank with their presentation of the current account financial statement for
the information area (record 62, position 87-120), corresponding to reason ABI 26 (record 62, position 42-43)
and to the customer reference value NROSUPCBI (record 62, position 78-86). It is compulsory to complete
this field.
2 According with the bank agreement. If these agreements are not present, the Bank can consider this value as not
received
116-120
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 14/41
2014
Field not available
No information may be entered in this field;
2.2 Tail record structure - fixed code "EF"
position
c/o type
field name
check
Contents
filler
blank
2-3
an
record type
"EF"
4-8
an
sender
same data as on the tail record
9-13
recipient
"
"
14-19
creation date:
"
"
20-39
an
support name
"
"
40-45
an
available field
field available to the sender company
46-52
number of orders
number of payment orders in the flow
53- 67
total
of
amounts
68-82
total of positive amounts V
total amount in hundredths of a euro - of

payment orders in the flow
83-89
number of records
number of records making up the flow

(including head and tail records)
90-112
filler
113
an

payment
blank
It must take the same value of the same field
of the head record, pos 113
114 -
an
currency code
this field must have the same value as the

field of the same name in the head record
115-120
Field not available
No information may be entered in this field;
negative V
this must be validated with "zeros".
2.3 Record structure fixed code 10
position
c/o type
field name
Check
Contents
1-
filler
blank
2 -3
an
record type
fixed code "10"
4-10
progressive number
order's progressive number inside the flow.

Begins with 1 and progresses by 1. The
number must be the same for all records of
the same order
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 15/41
2014
11-16
filler
Blank
17-22
date order was executed
Entered as DDMMYY, this field represents

the date 1 requested by the sender for the
transaction execution. This is the same as the
date when the debtors account should be
debited, which is the date the cheques are
drawn. This data should be entered a san
alternative to payee bank value date
requested.
23-28
payee bank value date
entered as DDMMYY; if the payment method

is "blank" or "1, it is the date when the
initiating bank pays the recipient bank (in
conformity with the service agreements
between the initiating bank and the customer).
2
29-33
an
reason
this may have the following values:

27000: general emoluments;
27010: emoluments - pension;
27020: emoluments - salaries;
34000: transfer; 3
48000: general bank transfers;
48015: bank transfers for national
insurance 4;
79000: funds transfer. 5;
ZV000: RID users refund 6;
ZZ000: credit transfers from companies
issuing credit cards for trades people 7.
1 The forwarding agent must check this date is the same as or occurs after the date the transaction is sent by the
customer and convey the flow, even if there are errors, providing it informs the customer.
2
The forwarding agent must check this date is the same as or occurs after the date the transaction is sent by the
customer and convey the flow, even if there are errors, providing it informs the customer.
3 transfer means the transfer of funds from one account to another both held by the same account holder at the
same bank. Therefore, the ABI codes for the ordering bank and the receiver bank must be the same.
4
this refers to payment orders carried out for national insurance purposes.
funds transfer means the transfer of funds from one account to another both held by the same account holder at
different banks. Therefore, the ABI codes for the ordering bank and the receiver bank must be different.
for presentations to the recipient and the possible outcome (if requested by the ordering party), reason ZV000 is
changed into 48000.
5 for presentations to the recipient and the possible outcome (if requested by the ordering party), reason ZZ000 is
changed into 48000.
6
The field is not subject to standardisation. Hence no validity check is conducted on it; plus, special characters
(such as /) are accepted.
6
For financial statements for end customers and the subsequent advice (if requested by the initiating party) the
ZV000 reason is converted into 48000.
For financial statements for end customers and the subsequent advice (if requested by the initiating party) the
ZZ000 reason is converted into 48000.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 16/41
2014
34-46
amount
order amount in Euro cents
47-
an
sign
Shows the fixed value " + "
48-69
Ordering bank's details
The ordering banks details include the three

following secondary fields.
48 -52
Bank code V
ABI code of the ordering bank processing the

payment orders; this must correspond to that
reported in the head record.
53-57
Bank CAB F
CAB code for the branch of the ordering

bank;
58-69
an
Ordering partys account F
reference code (a/c number)

sending/ordering company 1
of
the
recipient bank's details

ABI code of the receiver/beneficiary bank
of the payment orders.
70 -74
bank code
75-79
Bank CAB
CAB code for the branch of the receiver

bank;
80-91
an
payee account
reference code (a/c number) of the payee

customer 1 .
92-113
filler
blank
114 -
method of payment
blank or 1 - bank transfer/transfer/funds

transfer
2
banker's
draft 2
3
- non-transferable banker's draft 3
4
- receipt cheque 4 (F.A.D.)
For reasons ZV000 and ZZ000 (pos. 29-33) it
must show either the value blank or 1
115-118
filler
blank
1 The field is not subject to standardization. Therefore, no validation check is performed on it and the following
special characters are accepted (ex. /).
2
in this case, the ordering bank sends a banker's draft to the payee's address
4 according with the bank agreement. If these agreements are not present, the Bank can consider this value as not
received
119
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 17/41
2014
an

payment
It can take the following values:

blank = Standard payment
U = Urgent payment 4.
If in the field is the U value is present, the
logical support must contain only one
payment transaction. This field has to take
the same value than in the head and in the
tail record (pos.113)
If the payment method (pos. 114-114) has
the 2, 3 o 4 values, this field must be
only blank.
120 -
an
currency code
this field must be the same as the field in the

head record.
2.4 Record structure fixed code 16 (payer's coordinates)

Record type 16 is optional 1. If the information in record type 16 is different from the information in record type
10, the ordering bank will take the information in the fields for record type 16 as valid for the purposes of the
order.
Record type 16 is structured in such a way to contain the ordering partys IBAN details. The national IBAN
details consist of the following information:
- Country code (2 characters);
- Check digit (2 characters);
- CIN (1 character);
- ABI code (5 characters);
- CAB code (5 characters);
- Account number (12 characters).
c/o type
field name
check
Contents
position
1-
Filler
blank
2-3
an
record type
fixed code 16
4-10
progressive
same number as record 10 of the order
number
The following fields, up to and including pos. 37, form the IBAN code, compliantly with the national laws
V
11-12
c
an
The country code must either be IT or SM 2
country code
13-14
check digit
IBAN check digit
15-
an
CIN
CIN
The presence of Record 16 should be agreed between the customer and the Access Financial Institution.
The SM code is included in the SEPA area from 3 February 2014.
16-20
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 18/41
2014
ABI code
The bank's ABI code:

- this must correspond to the recipient's ABI
code (position 9-13) in the head record;
21-25
CAB code
The bank's CAB code;
26-37
an
account number
Current account ; it must consist of 12

characters; the entered values must consist of
numbers ranging from 0 to 9 and/or capital
letters from A to Z, aligned to the right with
the filler zeros to the left, excluding special
characters, separators or punctuation symbols.
38-120
Filler
Blank
2.5 Record structure fixed code 17 (payee's coordinates)
Record 17 is structured in such a way to contain the ordering partys IBAN details use in case of payment via
credit transfer.
Record type 17 is mandatory when method of payment (pos. 114 record 10) is blank or 1
The national IBAN details consist of the following information:
- Country code (2 characters);
- Check digit (2 characters);
- CIN (1 character);
- ABI code (5 characters);
- CAB code (5 characters);
- Account number (12 characters)
If the information in record type 17 is different from the information in record type 10, the ordering bank will
take the information in the fields for record type 17 as valid for the purposes of the order. For record type 17, the
forwarding agent must, as specified in the content column, carry out validity checks on the Check digit and
account number fields and transmit the flow even if there are errors, provided that the customer receives the
relevant information.
Position
17
c/o type
-
field name
Filler
check
N
Contents
blank
2-3
an
record type
fixed code 17
4-10
V
progressive number
The following fields, up to and including pos. 37, form the IBAN code, compliantly with the national laws
Similarly as is done for compulsory alphanumeric fields featuring an F check, the check is only on the actual
presence of the field.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 19/41
2014
11-12
an
country code
The country code must either be IT or SM 1
13-14
check digit
FV
IBAN check digit. Departing from what has

been specified in the apposite check
column, the check to be made by the
forwarding agent alone must be a validity
check; the forwarding agent is still to convey
the flow, even if there are errors, providing it
informs the customer
15-
an
CIN
16-20
ABI code
CIN
The bank's ABI code; if the reason for
payment is 34000 (transfer) in pos. 29-33
of record 10, this field must be the same as
the field in position 48-52 of record 10; if the
reason is 79000 (funds transfer) in pos. 2933 of record 10, this fields value should not
match the value of the field in pos. 48-52 of
record 10.
21-25
CAB code
26-37
an
account number
38-120
filler
The bank's CAB code

Current account; . Departing from what has
been specified in the apposite check
column, only the forwarding agent must
ascertain that the field consists of 12
characters, ranging from 0 to 9 and/or capital
letters ranging from A to Z, aligned to the
right, with filler zeros on the left and
excluding special characters, separators or
punctuation marks; the forwarding agent is
still to convey the flow, even if there are
errors, providing it informs the customer.
Blank
position
c/o type
field name
check
Contents
17
filler
blank
2 3
an
record type
Fixed code "20"
4-10
progressive number
Description of the ordering company (three segments of 30 characters each) 2
1
2
The SM code is included in the SEPA area from 3 February 2014.
this information must be recorded in the interbank's transmission of electronic messages in IDC 041, 043 and
D42 respectively so that the creditor's bank may record it in the presentation of the financial statement regarding
transactions (see structure of record type 63 in section V- Information Area). It is compulsory to complete this
field. It should be noted that the references to BON interbank procedure shall be applied until 1st February 2014.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 20/41
2014
11-40
an
Company name
ordering
purpose
company's
name
or
corporate
41-70
an
address
Address
71-100
an
city/town
City/town
101-116)
an
Tax coding
Ordering party's taxpayer's code/VAT number

2 this field is not subject to any checks,
neither a presence check nor a formal validity
check, if the ordering bank's ABI code
(position 48-52 of record 10 and position 1620 of record 16) is one of the following:
03034 03145 03171 - 03178 - 03195
03225 - 03530 06067 08540 03262
03287 03277 03237
117-120
filler
blank
position
c/o type
field name
check
Contents
1-
filler
blank
2 3
an
record type
fixed code "30"
4-10
progressive number
same number
order.
as
record
10
of
the
Description of the payee customer 1 (three segments of 30 characters each: payee customer's/recipient's name
or corporate purpose)
11-40
an
1st segment
41-70
an
2nd segment
71-100
an
3rd segment
101-116)
an
Customer's tax coding
customer/creditor's taxpayer's code
117-120
filler
Blank

Record type 40 is compulsory; it becomes optional if record type 10 shows the method of payment as "bank
transfer" (values are blank or 1).
position
c/o type
field name
check
contents
1-
filler
Blank
2 it must be shown in the possible inter-bank message (in IDC099 after the key word CFORDIN) in order to
allow the creditors bank to show it when presenting the transfer (see record type 63 structure in section V
Information Area). This task is compulsory.
1
In case of SEPA payment orders it is recommended the use of the first 70 characters.
2 -3
4-10
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 21/41
2014
an
record type
Fixed code "40"
progressive number
same number
order.
as
record
10
of
the
Payee customer's address

11-40
an
Address
street, street number and/or name of the

administrative district; this field becomes
compulsory if the method of payment is
neither
"blank
nor
1
(bank
transfer/transfer/funds transfer).
41-45
Postal code
postal code; this field becomes compulsory if

the method of payment is neither "blank nor
1 (bank transfer/transfer/funds transfer).
46-70
an
municipality
and V
province abbreviation
municipality and province abbreviation; this

field becomes compulsory if the method of
payment is neither "blank nor 1 (bank
transfer/transfer/funds transfer).
71-120
an
payee's bank/branch
payee's bank/branch coordinates; this field

may show the payee's bank/branch uncoded.
2.9 Record structure fixed code 50/60

This record type is compulsory for methods of payment blank or 1 (bank transfer/transfer/funds transfer). In
other cases, it may be present provided the company and the ordering bank agree on what may or may not be
showed.
These records which are mutually exclusive - are used according to the type of description given of the
payment order. If the description uses more than the 90 characters available, record 50 must be used or record 60
(for a minimum of 2 to a maximum of 5 characters).
position
c/o type
field name
check
contents
1-
filler
blank
2 -3
an
record type
fixed code "50" (c "60")
4-10
progressive number
same number as record 10 of the

order.
Description for the use of the payee customer - operation reference 1
11- 40
an
1st segment
41-70
an
2nd segment
the information recorded in records 50/60 must be recorded in the interbank's transmission (the procedure will
be discontinued from 1st February 2014)of electronic messages according to the following rule: if the total length
does not exceed 50 characters, the information is recorded in the IDC 062 (customer-customer information);
otherwise, the IDC 099 is used (bank/bank information) preceded by the appropriate keyword /BENEF/. In this
way, the creditor's bank will be able to record this information in the presentation of the financial statement
regarding transactions (see structure of record type 63 in section V- Information Area). It is compulsory to
complete this field. Notice that in case of SEPA payment orders, information in excess of 140 characters may not
be transmitted to the destination bank. The access banks are recommended to enable warnings to the customers.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 22/41
2014
71-100
an
3rd segment
101-120
filler
blank
To help the payee customer make use of the automatic processing of bank transfer information, it is
recommended that records 50/60 are structured in the following way:
in order to indicate a second payee (if different from the credit account holder), use the first record available
(record 50 if there are no other references to add in describing the bank transfer, or, alternatively, use the
first record available of record 60) up to a maximum of 50 characters (from position11 to 60);
in order to indicate references to invoices, structure each segment with 30 characters indicating the
invoice number aligned on 24 characters followed by the date of the invoice on 6 characters using the
DDMMYY format.

position
c/o type
field name
Check
contents
1-
filler
blank
2 -3
an
record type
fixed code "70"
4-10
progressive number

order.
11-25
filler
blank
26-30
an
Field not available
No information may be entered in this field
31-37)
Flow qualifier

This field consists of three subfields, as given
below, which, if validated, must be the same
as those recorded in the head record.
31 o
an
Flow type
Shows the value:

Place activities
32 o
33-37 o
an
Flow qualifier
Transmitter Party

38-42).
an
MP Code
Code assigned by Gateway MP Bank to the

Market Place Manager; it becomes
compulsory if the preceding three fields that
make up the flow qualifier have been
validated. 1
43-69
filler
blank
70-
Request flag
This identifies the type of result requested by
The logic support may not be the same as for the MP code.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 23/41
2014
the ordering customer for the payment orders.
This may have the following values:
blank = as agreed by the customer and the
bank
1 = request ordered
2 = request cancelled
3 = both
4 = positive advice not required
71-100
an
Unique code
Unique code assigned by the company to each

individual payment order for which a result
has been requested. This is compulsory if the
Request flag field has been validated with
any value other than blank.
101-110
filler
blank
111
an
bank details CIN
CIN check on the payee customer's bank

details
112
filler
blank
113-120
an
check keys
These usually consist of logic keys to protect

the orders and can be validated by the
company provided agreements have been
made beforehand with the ordering bank
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 24/41
2014
3 Overseas bank transfer orders function

The overseas bank transfer flow can be used for the following types of payment order:
payment orders in Euros or in currency made to foreign payees
domestic payment orders in currency
payment orders in Euros from a foreign account.
Each order consists of a minimum of 5 to a maximum of 10 different record types, 120 characters each; while
the total number of record making a transaction spans from a minimum of 5 to a maximum of 13 records, 120
characters each.
The information structure for each foreign bank transfer order reflects the international standard Edifact
(Electronic Data Interchange for Administration, Commerce and Transport) and, in particular, the Payer
message.
All fields containing amounts, which are present in the records detailed in the paragraphs below, must terminate
with "," followed by two decimal places. These last two decimal places are validated as zero if the relevant
currency code does not allow for decimals.
characters.
3.1 Head record structure - fixed code "PE"

position
c/o type
field name
Check
contents
1-
filler
blank
2-3
an
record type
"PE"
4-8
an
sender
sending company's SIA code
9-13
recipient
ordering bank's ABI code;
14-19
creation date:

20-39
an
support name
open field available to the sender company;

this must have the same creation date and be
the same for both sender and receiver.
40-45
an
available field
field available to the sender
46-104
filler
blank
105-111
Flow qualifier

below
105 o
an
Flow type
Shows the value:

Place activities
106 o
107-111
an
Flow qualifier
Transmitter Party
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 25/41
2014
112-115
filler
Blank
116-120
Field not available

position
c/o type
field name
check
contents
1-
filler
blank
2-3
an
record type
"EF"
4-8
an
sender
same data as on the head record
9-13
recipient
"
"
14-19
creation date:
"
"
20-39
an
support name
"
"
40-45
an
available field
46-52
number of orders
number of bank transfer orders in the flow
53- 64
filler
blank
65-82
total of amounts
summation of the amounts for each individual

order in the support (cf. record P1, position
14-31); this total must record the explicit
decimal point in position 80;
83-89
number of records

90-114
filler
blank
115-120
Field not available
3.3 Record structure - fixed code H1 Header message

Compulsory record.
position
c/o type
field name
Check
contents
1-
filler
blank
2 -3
an
record type
fixed code "H1"
4-10
progressive number
order number inside the flow (begins with 1

and progresses by 1). This number must be
the same for all the records for the same order
and must increase for each new order
11-24
an
UNH_S009
11-16 c
an
UNH_0065
shows the value "PAYORD"
17-19 c
an
UNH_0052
shows the value "D"
20-22 c
an
UNH_0054
shows the value "93A"
message identifier
23-24 c
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 26/41
2014
an
UNH_0051
an
BGM_C002
25-27 c
an
BGM_1001
shows the value

Payment Order
28-61 c
an
BGM_1004
unique identifier of the bank transfer order

assigned by the ordering customer (the same
reference must be returned by the ordering
bank to the customer in the books listing
debits and in the description of movement on
the financial statement for record-type
current accounts 62 position, 87-120
preceded by the constant PAYORDREF at
position 78-86)
filler
blank
an
BGM_1225
Shows the fixed value 9
DTM_1
65-67 o
DTM_2005
data qualifier; this has the value "137" =

order creation date
68-75 o
DTM_2380
date in YYYYMMDD format; this field must

be validated if the preceding field has been
validated
76-78 o
DTM_2379
date format; this has the value"102" and

must
be
validated
if
the
preceding field has been validated. No check
if the previous field is not inserted
DTM_2
79-81 o
an
DTM_2005
if"203" , it is the customer's request date for

the execution of the order; if "228" , it is the
debit value date requested by the customer
82-89 o
DTM_2380
date in YYYYMMDD format; this field

becomes compulsory if the preceding field
has been validated
90-92 o
DTM_2379
this has the value "102"; this field becomes

compulsory if the preceding field has been
validated. No check if the previous field is not
inserted
DTM_3
93-95f
an
DTM_2005
if 140, it is the credit value date requested

for the payee; if 227, it is the date
requested for funds to be available at the
payee's bank
96-103 o
DTM_2380
date in YYYYMMDD format; this field

becomes compulsory if the preceding field
has been validated
104-106 o
DTM_2379

validated. No check if the previous field is not
inserted
25- 64
62- 63-64 f
65-78
79-92
93-106
shows the value "UN"

message name
"450"
which
means
order creation date
execution date/debtor value date
payee's value in account/available funds
107-112
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 27/41
2014
an
transaction type
107-109 c
an
BUS_3279
this has the value
"IN " meaning "international" ,

when the payee's bank is a foreign
bank
DO meaning domestic when

payment is credited to an Italian
bank (or the Italian branch of a
foreign bank)
or
110-112 o
an
BUS_4487
this can have the value "1 " meaning "Clean

Payment"
113-115 -
filler
blank
an
Field not available
116-120
3.4 Record structure - fixed code P0 Method of Payment

Optional record.
position
c/o type
field name
check
contents
1-
filler
blank
2 -3
an
record type
fixed code "P0"
4-10
progressive number
same number as record H1 of the order
11-13
an
PAI_4461
this specifies the payment method requested;

it can have the following values :
"23 ": cheque to be sent by the ordering bank
"8
": keep at the creditor's bank
"26 ": cheque to be sent by the creditor's bank
blank: credit the payee's current account
14-16
an
FCA_4471
method for debiting commission fees; this can

have
the
following
values:
blank or "14 ": each party pays their own
bank's
commission
fees
"13 ": commission fees are paid in full by the
payee
of
the
bank
transfer
"15 ": commission fees are paid in full by the
ordering party of the bank transfer
17-46
an
FCA_C878
debit account for commission fees alone (if

different from the debit account from which
the transaction amount is taken); the whole
field does not have to be validated should
there be a request for commission fees to be
paid in full by the payee (namely, if
FCA_4471= "13")
17-21 o
an
FCA_3434
account CAB code;
22-24 o
an
FCA_1131

Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 28/41
2014
validated
25-27 o
an
FCA_3055

validated
28-44 o
an
FCA_3194
code of the current account from which the

customer requests commission fees to be
debited; this field becomes compulsory if the
preceding field has been validated
45- o
an
CIN
CIN check on account
filler
blank
46-120
3.5 Record structure - fixed code P1 Amount

Compulsory record.
position
c/o type
field name
check
contents
1-
filler
blank
2 3
an
record type
fixed code "P1"
4-10
progressive number
11-13
an
MOA_5025
this defines the relationship between the

currency in which the bank transfer amount is
made
and
the
currency
debited;
"9 : when the two currencies are the same
57 : when the two currencies are different
14-34
an
bank transfer amount
The following fields, up to and including 34, contain information on the bank transfer amount
14-31 o
MOA_5004
value amount (explicit decimal point in fixed

position 29)
32-34 o
an
MOA_6345
the currency in which the amount is expressed

(cf. doc. CBI-STD-001: Appendix D)
The following fields, up to and including 52, contain information on the debiting of the bank transfer
35-37 o
an
CUX_6347
If present, shows the fixed value 2
38-40 f
an
CUX_6345
currency code for the debit account (cf. doc.

CBI-STD-001: Appendix D)
Should the CUX_6347 field (pos. 35-37)
show a value, it becomes compulsory and
must be other than the currency specified in
field MOA_6345 (pos. 32-34).
No check if the field CUX_6347 shows no
value.
41-52 o
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 29/41
2014
CUX_5402
exchange rate agreed upon for debiting the

exchange value of the amount; the last 5
characters are decimals (implicit decimal
point); this field is validated only if the
exchange rate has been calculated in advance
agreed upon with the ordering bank. Not all
zeros are to be filled.
No check if the field CUX_6347 shows no
value.
The following fields, up to and including 70, contain information on the crediting of the bank transfer
53-55 o
an
CUX_6347
If present, it shows the fixed value 3. The

field is compulsory if the currency in the
credit account is other than that of the amount
(namely, when field MOA_5025 in pos. 1113 is 57). The field must be missing if the
currency of the credit account is the same as
that of the amount (namely, when field
MOA_5025 in pos. 11-13 is 9)
56-58 f
an
CUX_6345
currency code for the debit account (cf. doc.

CBI-STD-001: Appendix D)
Should the CUX_6347 field (pos. 53-55)
show a value, it becomes compulsory and
must be other than the currency specified in
field MOA_6345 (pos. 32-34).
No check if the field CUX_6347 (pos. 53-55)
shows no value.
59-70 o
CUX_5402
exchange rate agreed upon for debiting the

exchange value of the amount; the last 5
characters are decimals (implicit decimal
point); this field is validated only if the
exchange rate has been agreed upon with the
ordering bank in advance
No check if the field CUX_6347 (pos. 53-55)
shows no value.
71-81
filler
82-119
an
instructions
82-84 o
an
RFF_1153

"ADC" = the customer requests that the bank
transfer is applied to an advance account
according to agreements made with the
customer's bank "FX " the customer specifies
that reference must be made to an exchange
contract indicated in the following field
85-119 o
an
RFF_1154
contract identifier as specified in the previous

point
filler
blank
120-
blank
executions instruction for the ordering bank
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 30/41
2014
3.6 Record structure - fixed code PH Bank and current account

Compulsory record. Information relating to the interested parties' respective current accounts at their banks
express in code must be recorded.
position
c/o type
field name
check
contents
1-
filler
blank
2 3
an
record type
fixed code "PH"
4-10
progressive number
11-44
an
Ordering party's IBAN
Ordering party's IBAN coordinates.
45-55
an
Ordering party's BIC
Ordering party's BIC.
56-60
filler
blank
61-94
an
payee's IBAN
if available, Payee's IBAN code; if not, other

account details
IBAN is mandatory in case of payment orders
for UE area account.
95-105
an
Payee's BIC
Payee's bank BIC

In case of presence, this field must be aligned
to the left with filler "blanks" on the right.
In case of presence and in case it assumes a
value defined by EPC for area SEPA country
identification (please refer to EPC409-09
document
published
on
http://www.europeanpaymentscouncil.eu/k
nowledge_bank_detail.cfm?documents_id=
328), the following control shall be
implemented:
1) Control of presence of the payees IBAN
(pos. 61-94 aligned to the left with filler
"blanks" on the right).
2) Control of consistency between Payee's
BIC Country Code ISO (pos. 99-100) and
the payee's IBAN Country Code ISO (pos.
61-62).
106-120
filler
Blank
3.7 Record structure - fixed code P3 Description of bank

Optional; can be repeated up to 3 times. Information relating to the bank may be recorded in description form;
however, it is preferred that bank identification is carried by using the codes expressed in the record PH.
If the BIC data is contained in the record type PH, the latter has priority over the description included in the
record type P3 and the recipient bank can ignore the content of the record type P3.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 31/41
2014
The following approach is strongly suggested for the intermediary bank: BIC data can be included more than one
time and, if known, it must be included both in the bank name (pos. 14-48) and the town/city of the branch (pos.
49-83).
position
c/o type
field name
check
Contents
1-
filler
Blank
2 -3
an
record type
fixed code "P3"
4-10
progressive number
11-13
an
FII_3035
This may have the following values:

"OR
"
(Ordering
"BF
"
(Payee
"I1 " (Intermediary bank)
14-83
an
FII_C088
14-48 c
an
FII_3432
name of the bank
49-83 c
an
FII_3436
town/city of the branch
filler
Blank
84-120
bank)
bank)
bank identification
3.8 Record structure - fixed code P4 Payer

Optional; if not present, the company corresponding to the SIA code expressed in the head record PE (positions
4-8) will be taken as the effective ordering party for the bank transfer.
position
c/o type
field name
check
contents
1-
filler
Blank
2 -3
an
record type
fixed code "P4"
4-10
Progressive number
11-13
an
NAD_3035
Shows the fixed value "OY " (Ordering

customer)
14-115
an
NAD_3124
14-48 c
an
block 1
Corporate purpose
49-83 c
an
block 2
Address
84-115 c
an
block 3
Piazza
an
NAD_3039
Ordering company's SIA code
116-120
Ordering customer
3.9 Record structure - fixed code P5 Payee

Compulsory record.
position
c/o type
field name
check
contents
1-
filler
Blank
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 32/41
2014
2 -3
an
record type
fixed code "P5"
4-10
progressive number
11-13
an
NAD_3035
Shows the fixed value "BE "
14-115
an
NAD_3124
14-48 c
an
block 1
Corporate purpose
49-83 c
an
block 2
Address
84-115 c
an
block 3
Piazza
an
NAD_3039
Payee's SIA code (if applicable and if known

by the ordering customer)
116-120
Payee customer
Optional record; to be used only if it is necessary to give special payment instructions to the payee's bank (this
exists if it is necessary to inform the payee as quickly as possible).
position
c/o type
field name
check
contents
1-
filler
Blank
2 -3
an
record type
fixed code "P6"
4-10
progressive number
11-13
an
INP_3301
fixed value "BF" as the action is requested by

the payee's bank
14-16
an
INP_4403
fixed value "1"
17-19
an
INP_4401
this may have the

"AP
":
advise
"AT ": advise by telex
20-22
an
CTA_3139

BC
(Contact
for
the
bank)
NT (Contact to notify third parties)
23-39
an
CTA_3413
referring function or office
40-74
an
CTA_3412
referring name
75-120
filler
Blank
following values:
by
telephone
3.10 Record structure - fixed code P7 Bank transfer references

The record type is optional and may be used as an alternative to record P8 1. This shows the bank transfer
references for the payee in uncoded form. This can be repeated twice if the first instance is not sufficient up to a
maximum of 140 characters in uncoded form.
position
c/o type
field name
check
Contents
1-
filler
Blank
2 -3
an
record type
fixed code "P7"
4-10
Progressive number
11-13
an
FTX_4451
this has the value "PMD"
If record type P7 is present, record type P8 is automatically excluded; however, both record types can be absent
at the same time.
14-118
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 33/41
2014
an
FTX_C108
14-48 c
an
first segment
49-83 o
an
second segment
this cannot be used for a second instance of

the record
84-118 o
an
third segment
this cannot be used for a second instance of

the record
filler
Blank
119-120
uncoded information that is communicated to

the payee of the bank transfer
3.11 Record structure - fixed code P8 Bank transfer references

(structured)
The record type is optional and may be used as an alternative to record P7 1. This shows the bank transfer
references for the payee in uncoded form. This can be repeated up to two times for a maximum of 4 reference
documents;
position
c/o type
field name
check
Contents
1-
filler
Blank
2 -3
an
record type
fixed code "P8"
4-10
Progressive number
11-44
an
DOC_C002
11-13 o
an
DOC_1001
document type; this can have the following

values:
"380":
Commercial
invoice
"381":
credit
note
"382":
commission
fees
"383:
debit
note
"315": contract
14-30 c
an
DOC_1000
document identifier code
31-33 c
an
DTM_2005
this has the value "171"
34-41 c
DTM_2380
document date in YYYYMMDD format
42-44 o
DTM_2379
Blank
45-60
Filler
61-94
an
DOC_C002
61-63 o
an
DOC_1001
first document
second document,
V
document type; this can have the following

values:
"380":
Commercial
invoice
"381":
credit
note
"382":
commission
fees
"383":
debit
note
"315": contract
If record type P7 is present, record type P8 is automatically excluded; however, both record types can be absent
at the same time.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 34/41
2014
64-80 c
an
DOC_1000
document identifier number
81-83 c
an
DTM_2005
84-91 c
DTM_2380
document date (in YYYYMMDD format)
92-94 o
DTM_2379
Filler
Blank
95-120
3.12 Record structure - fixed code P9

Mandatory Optional record (at minimum once, it can be repeated until a maximum of 6 times, in oder to manage
different currency causes)
position
c/o type
field name
check
Contents
1-
Filler
Blank
2 3
an
record type
fixed code "P9"
4-10
Progressive number
11-13
an
GIS_7365
fixed code: "ZZ "
14-16
an
NAD_3035
Fixed code RA
17-19
an
FTX_4451
20-27
filler
blank
28-35
Presentation date
Date in AAAAMMGG format
36-42
Customs tariff
Customs tariff
43-59
filler
blank
60-64
an
Currency cause
UIC/ Italian Central Bank cause code
65-82
Amount
amount to which the currency cause is

referred (explicit comma in fixed pos. 80); in
case of more than one P9 record, this amount
is a subset of the total amount of the
transaction inserted in record P1, pos. 14-31
83-102
filler
blank
103-105
Payee's country code
Payee's country according to UIC codes
106-120
filler
blank
Only the following values are permitted:

EMI (Management of CVS)
INF (Less than the limit of CVS)
SNR (Non resident subject)
CVA (Currency cause only)
CDV (Currency transfer among residents)
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 35/41
2014
4 Payment order result function

The information flow contains information relating to the result of the payment orders which the ordering
customer requested by means of validating fields specially set in the original order (cf. Payment orders Record
type 70). Each order consists of 4 records of 120 characters each in the following sequence:
1st
10
2nd
20
3rd
30
4th
70
characters:
head record EP
tail record EF
4.1 Head record structure - fixed code "EP"
position
c/o type
field name
check
Contents
1-
filler
blank
2-3
an
record type
"EP"
4-8
an
sender
ABI code of the bank that communicates the

results of the payment orders received from
the ordering company;
9-13
recipient
SIA code of the ordering company that

requested the results. .
14-19
creation date

20-39
an
support name
open field available to sender. This must have

the same creation date and be the same for
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 36/41
2014
both sender and recipient.
40-45
an
available field
46-104
filler
blank
105-111

Flow qualifier

below
105 o
an
Flow type
This has the value:

Place activities
106 o
107-111
an
Flow qualifier
This has the fixed value $
Transmitter Party

112-115
filler
blank
116-120
Field not available
No information may be entered in this field.
position
c/o type
field name
check
Contents
filler
blank
2-3
an
record type
"EF"
4-8
an
sender
same data as on the head record
9-13
recipient
"
"
14-19
creation date:
"
"
20-39
an
support name
"
"
40-45
an
available field
46-52
number of orders
number of bank transfer orders in the flow
53- 67
filler
blank
68-82
total of amounts
This is the sum of the values indicated in the

Amount field of the results in the flow
(record 10, position 41-53)
83-89
number of records

90-114
filler
blank
115-120
Field not available
No information may be entered in this field.
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 37/41
2014

Record type 10 is compulsory. It contains information necessary for reconciliation with the original order.
position
c/o type
field name
Check
Contents
1-
filler
blank
2 -3
an
record type
fixed code "10"
4-10
progressive number
order's progressive number inside the flow.

Begins with 1 and progresses by 1. The
number must be the same for all records of
the same order
Identifier information of the original order.

11-40
an
Unique code
Unique code assigned by the company to each

individual payment order for which an advice
has been requested. It contains the same value
as in record type 70, pos. 71-100 of the
original transaction.
41-53
Amount
Amount of each individual payment order for

which a result has been requested (cf. Record
type 10, position 34-46 of the original order)
54-58
an
Ordering
code
party's SIA V
Ordering customer's SIA code (Record type

10, position 92-96 of the original order). This
code, if applicable, must be validated for each
individual order in the same logic support
and must always have the same value. This
can be different from the SIA code in the
head record and it is not necessarily
registered in the applicative centre's routing
table.
Information assigned by the ordering bank

59 -59
an
Reference code type
This identifies the type of information

expressed in the Reference code field. This
may have the following values:
1 = if the Reference code field contains the
C.R.O.;
2 = if the Reference code field contains the
bank's internal code.
This is compulsory if the Reference code
field (position 60-94) has been validated.
60-94
an
Reference code
Reference code operation assigned by the

ordering bank to the payment order.
If the Method of payment field (position
101-101) has the value 1 and the Anomaly
type field (pos. 100-100) I blank, this field is
mandatory.
95-99
Reason
It must show one of the following values:

27000:
general
emoluments;
27010:
emoluments
pension;
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 38/41
2014
27020:
emoluments
salaries;
1
34000:
transfer;
48000:
general
bank
transfers;
2
48015: bank transfer for national insurance;
68000:
cancellation
of
order;
3
79000: funds transfer.
100100
Anomaly type
Anomaly found by the ordering bank on one

order error not blocking the order). If validated,
this must have the following value:
2 = Transaction not executed;
4 = Incorrect Transaction structure 4.
101-101
Method of payment
Method of payment effected by the ordering

bank. This must have one of the following
values:
1 = bank transfer/transfer/funds transfer
2
=
banker's
draft 5
3 = non-transferable banker's draft 6
4 = receipt cheque 7 (F.A.D)
102-108)
Flow qualifier

This field consists of three subfields, as given
below, which, if validated, must be the same
as those recorded in the head record.
102 o
an
Flow type
Shows the value:

Place activities
103 o
an
Flow qualifier
104-108 o
Transmitter Party

109-113). o
an
MP Code
Code assigned by Gateway MP Bank to the

Market Place Manager; it becomes
compulsory if the preceding three fields that
make up the flow qualifier have been
validated. This code, if applicable, must be
validated for each individual order in the
1 transfer means the transfer of funds from one account to another both held by the same account holder at the
same bank. Therefore, the ABI codes for the ordering bank and the receiver bank must be the same.
2
This refers to payment orders carried out for national insurance purposes.
funds transfer means the transfer of funds from one account to another both held by the same account holder at
different banks. Therefore, the ABI codes for the ordering bank and the receiver bank must be different.
This code could be used from the Executing Banks which might be not able to offer SEPA conversion services.
in this case, the ordering bank sends a non-negotiable cheque to the payee's address
in this case, the ordering bank sends a banker's draft and receipt to the payee's address
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 39/41
2014
same logic support and must always have the
same value.
114-114
an
Execution mode flag
If present, it must be the value U in order to

confirm the execution in the urgent mode
according with the customer original request
115-120
filler
blank

Record type 20 is optional. This contains some additional information regarding the methods of execution and
debiting of the original order.
position
c/o type
field name
check
Contents
filler
blank
2 3
an
record type
Fixed code "20"
4-10
progressive number
Additional information on the ordering bank

11-16
Ordering party's currency
In the DDMMYY format, this represents the

currency applied to the ordering customer.
17-22
Payee's currency

currency applied to the payee.
23-28
Order date

date the order was given by the bank (cf. IDC
D28).
29-34
Debit accounting date

accounting date the ordering customer was
debited.
35-40
Execution date
Entered as DDMMYY, this field represents

the date the bank transfer was executed, or
the date the banker's draft was issued, or the
date the cheque receipt was issued
41-53
Commission fees
Amount of commission fees applied to the

ordering customer for the execution of the
order.
54-66
Costs
Amount of commission fees applied to the

ordering customer for the execution of the
order.
67-79
Penalties
Amount of penalties applied to the ordering

customer for the execution of the order.
80-95
an
Cheque number
Cheque number issued.
96-120
filler
blank
Title:
Code
Release
CBI-BON-001 6.16
Document type:
Date
Page
14 February 40/41
2014

This record type is optional and is available by means of a bilateral agreement between the customer and the
ordering bank.
position
c/o type
field name
check
contents
1-
filler
blank
2 -3
an
record type
Fixed code "30"
4-10
progressive number
Same number as record 10 of the

order.
11-120
an
Available field
Available by means of a bilateral agreement

between the customer and the ordering bank.

Record type 70 is optional and set aside for future use.
position
c/o type
field name
Check
contents
1-
filler
blank
2 -3
an
record type
fixed code "70"
4-10
progressive number

order.
11-120
filler
blank
End of document

Bank transfers - CBI technical standards

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bank transfers - CBI technical standards

Uploaded by

Copyright:

Available Formats

Payments - Bank transfers

CBI - Technical standards

CBI - Technical standards

Most recent update:

This document includes material subject to regulation by the CBI mark.

Updates and revisions

With CBI Communication

Network message of Bank transfer

Entering new field Flow

Entering new field MP Code

Entering new field Flow

Entering new field MP Code

Foreign bank 4.5

Rejection of filler zeros for

Paragraph Paragraph Title Modification description

9 May Circular 1/2005

9 May Network Message

Entering the validity check

Entering the Taxpayer's

Entering new fields that

This document includes material subject to regulation by the CBI mark.

Entering new reasons

(pos. 80-91) becomes

The Bank Code field (pos. 70-74) is

Payment orders 2.3

Bank CAB field (pos. 75-79) optional

Payment orders 2.3

Payee Account field (pos. 80-91)

Payment orders 2.3

Company Code (pos. 92-96) field

Payment orders 2.3

Payee Customer Code (pos. 98-113)

Payment orders 2.3

Payment orders 2.6

Payment orders 2.5

Code Type field (pos. 97) missing if

Removal of the Payment Orders

Removal of the Overseas bank

Payment orders 2.3

Record type 10 Additional information on the check

Payment orders 2.3

Payment orders 2.3

Payment orders 2.3

Payment orders 2.5

Payment orders 2.3

Payment orders 2.5

Inclusion of a further compulsoriness

3 June 2008 Network

Amendment of the note referring to

Additional information on the

3 June 2008 Circular

Entry of new codes in the FTX_4451

3 June 2008 Network

Payment orders 2.5

Payment orders 2.3

Payment orders 2.3

The following fields were deleted:

A reference to the anti-recycling

Addition of further information about

31 Jul 2008 Network

1 Mar 2010 Network

The order execution date description