Direct Exchange – Notes on the Electronic Interface
Table of Contents
1.
Introduction
5
2.
Overview of Available Banking Services
6
3.
Formats: File-Naming Conventions
7
4.
Data Exchange/Communication
9
4.1
Delivery of Files to “Eingang” Directory
9
4.2
Collection of Account Information in “Ausgang” Directory
9
5.
Establishing a Connection
11
5.1
Process
11
5.2
Encryption
12
6.
E-Documents
13
6.1
Introduction
13
6.2
Overview of E-Document Services via Direct Exchange
13
6.3
Download Steps for E-Documents
13
6.4
File Names
14
6.5
Metadata
14
6.5.1
Separate XML File
14
6.5.2
Structure of the XML File
14
6.5.3
Included Metadata
15
6.6
Available Documents
17
7.
Formats
18
7.1
DTA Payment Orders
18
7.2
LSV+ Collections
18
7.3
Credit Transfers
18
7.3.1
Referencing between pain.001 and pain.002
18
7.3.2
Salary and Pension Payments
18
7.3.3
Type of Booking, Type of Display, and Deadlines for Submission
19
7.4
SEPA Direct Debit
20
7.5
Payment Status Report
20
7.6
Account Statement (MT940 and Provisional Bookings/Intraday (MT942)
20
7.6.1
Credit Suisse Account Statement (MT940)
20
7.6.2
Credit Suisse Provisional Bookings/Intraday (MT942)
21
7.6.3
Structure of Field 61 (Credit Suisse)
21
7.6.4
Structure of Field 86 (Credit Suisse)
22
7.7
BESR (ESR Type3)
24
8.1
Purpose and Prerequisites
25
8.2
Overview of Processing
25
8.2.1
Filegate Framework
25
8.2.2
DTA Processing
25
8.2.3
LSV+-Processing
26
8.3
Schema Structure
26
8.4
Processing Log
27
8.5
DTA Processing Log
28
8.5.1
Log Structure
28
8.5.1.1
File Summary
28
8.5.1.2
Information on Payment Groups
30
8.5.1.3
Rejected Payments
34
8.5.1.4
Severe Errors/Reason for Rejection
36
8.5.2
Scenarios
36
8.5.2.1
Processed
36
8.5.2.2
Rejected
37
8.6
LSV
+Processing Log
37
8.6.1
Log Structure
38
8.6.1.1
FileDetails
39
8.6.1.2
Payment Group Details
41
8.6.1.3
Validations
45
8.6.2
Scenarios
47
8.6.2.1
Error-Free File
47
8.6.2.2
File without Serious Errors
48
8.6.2.3
File with Severe Errors – Rejected File
48
8.6.2.4
Double Transmission of File
48
8.6.2.5
Test File
48
9.
Error Messages
49
9.1
DTA Error Messages
49
9.2
LSV+ Error Messages
51
10.
E-Documents: Feeder Applications, Group Names and Document Types
56
10.1
Feeder Application ID and Group Names
56
10.2
Document Types: Payment Transactions
57
10.3
Document Types: Securities
58
10.4
Document Types: Statement of Investments/Investment Performance
68
10.5
Document Types: Mortgages
69
10.6
Document Types: Account Records
69
11.
Appendix
71
11.1
Appendix A: Filegate Headers
71
11.2
Appendix B: Types
73
1.
Introduction
Direct Exchange is the electronic interface for connecting large systems to the Credit Suisse payment
transaction infrastructure. Using Direct Exchange, our clients can automatically execute all payments (DTA
format) from their ERP solutions as well as LSV+ collections. They automatically receive the necessary
data for comparison in Accounting, can collect information on account administration (MT940/MT942),
and retrieve their e-documents.
The client does not log into Direct Exchange, but simply sends the relevant files to the bank. These files
are encrypted and enciphered, and on request, electronic certificates and/or line encryption may be
agreed upon for additional security. Credit Suisse checks the client authorization on the basis of the
agreed rights and executes the instructions. Alternatively, the client can also send individual orders,
needing separate approval by means of a form.
The openness and flexibility needed for large systems is achieved by the use of standards such as
FTP, MQ or SWIFT FileAct
SSL, SSH, Secure+ and VPN for encryption of communication and data transfer also across public
networks (public internet)
as well as through proven file transfer products supported by numerous systems.
Due to the implementation costs, Direct Exchange is only suitable for large corporate clients.
Our Electronic Banking experts will be pleased to help you choose the most suitable delivery interface for
your company. You can reach us on freephone number 0800 88 11 88, Monday through Friday, from
07:30 to 17:30.
Further information on electronic banking and additional bank services can also be found at
2.
Overview of Available Banking Services
Depending on the type of client connection involved, Direct Exchange allows access to a wide range of
banking services. The following overview table details these.
Table 1: Overview of Direct Exchange bank services
No.
Bank service
Description
Client
sends
Client
receives
Same-day
execution
possible until
1
DTA
Multiple payment order, multiple booking and display
07:00
2
DTA without electronic
signature
Multiple payment order, to be approved separately,
multiple booking and display
07:00
3
DTA express
Multiple payment order, multiple booking and display
12:00
4
DTA dispo
Individual payment order, individual booking and
display
14:00
5
DTA single
Multiple payment order, individual booking and display
07:00
6
DTA single express
Multiple payment order, individual booking and display
12:00
7
DTA test
Test payment
8
DTA processing log
Banking confirmation at file and payment level
9
LSV
+/BDD
Collection order
10
LSV+ without electronic
signature
Collection order, to be approved separately
11
LSV
+test
Test collection
12
LSV
+processing log
Banking confirmation at file and collection level
13
BESR
BESR credit advice
14
MT940
End-of-day account statement for Credit Suisse
15
MT942
Intraday account statement
Provisional bookings (non-binding)
for Credit Suisse
16
E-Documents
Bank records and documents electronically as a PDF
file
17
Credit transfer
Credit transfer in accordance with the Swiss ISO
20022 payments standard, in pain.001 format
See chapter 7.3.3
18
SEPA direct debit
Collection order in accordance with SEPA direct
debits, in pain.008 format
19
Payment status report
Payment status report in accordance with the Swiss
ISO 20022 payments standard, in pain.002 format
3.
Formats: File-Naming Conventions
When data is sent to, or delivered from, Direct Exchange, the following naming conventions must be
adhered to for automatic further processing:
Table 2: Overview of file naming conventions
No. Bank service
Description
Directory File name
Extension for
transmission Extension
1
DTA
Multiple payment order,
multiple booking and
display
Incoming
DTAS_<contract>_<date>_<time>
TMP
TXT
2
DTA without
electronic
signature
Multiple payment order,
to be approved
separately, multiple
booking and display
Incoming
DTAO_<contract>_<date>_<time>
TMP
TXT
3
DTA express
Multiple payment order,
multiple booking and
display
Incoming
DTAE_<contract>_<date>_<time>
TMP
TXT
4
DTA dispo
Individual payment
order, individual booking
and display
Incoming
DTAD_<contract>_<date>_<time>
TMP
TXT
5
DTA single
Multiple payment order,
individual booking and
display
Incoming
DTAN_<contract>_<date>_<time>
TMP
TXT
6
DTA single
express
Multiple payment order,
individual booking and
display
Incoming
DTAX_<contract>_<date>_<time>
TMP
TXT
7
DTA test
Test payment
Incoming
DTAT_<contract>_<date>_<time>
TMP
TXT
8
DTA processing
log
Banking confirmation at
file and payment level
Outgoing
Collective file: VPDTA_<contract>
One-time original file:
VPDTA_<contract>_<date>_<time>
TMP
XML
9
LSV
+/BDD
Collection order
Incoming
LSVS_<contract>_<date>_<time>
TMP
TXT
10 LSV+ without
electronic
signature
Collection order, to be
approved separately
Incoming
LSVO_<contract>_<date>_<time>
TMP
TXT
11 LSV
+test
Test collection
Incoming
LSVT_<contract>_<date>_<time>
TMP
TXT
12 LSV
+processing
log
Banking confirmation at
file and collection level
Outgoing
Collective file: VPLSV_<contract>
One-time original file:
VPLSV_<contract>_<date>_<time>
TMP
XML
13 BESR
BESR credit advice
Outgoing
Collective file: BESR_<contract>
One-time original file:
BESR_<contract>_<date>_<time>
No. Bank service
Description
Directory File name
Extension for
transmission Extension
14 MT940
End-of-day account
statement for Credit
Suisse
Outgoing
Collective file: MT940_<contract>
One-time original file:
MT940_<contract>_<date>_<time>
TMP
TXT
15 MT942
Intraday account
statement
Provisional bookings
(non-binding) for
Credit Suisse
Outgoing
Collective file: MT942_<contract>
One-time original file:
MT942_<contract>_<date>_<time>
TMP
TXT
16 E-Documents
Bank records and
documents
electronically as PDF
Outgoing
E-Documents (PDFs)
Collective file: EDOCS_<contract>
One-time original file:
EDOC_<contract>_<date>_<time>
Metadata
Collective file:
edoc_metadata_<contract>
One-time original file: edoc_
metadata_<contract>_<date>_<time>
TMP
ZIP
Metadata:
XML
17 Credit transfer
Credit transfer in
accordance with the
Swiss ISO 20022
payments standard, in
pain.001 format
Incoming
PN1_<contract>_<date>_<time>
TMP
XML
18 SEPA direct debit Collection order in
accordance with SEPA
direct debits, in
pain.008 format
Incoming
SDDE_<contract>_<date>_<time>
TMP
XML
19 Payment status
report
Payment status report
in accordance with the
Swiss ISO 20022
payments standard, in
pain.002 format
4.
Data Exchange/Communication
The client has one directory each provided for delivering and collecting files.
4.1
Delivery of Files to “Eingang” Directory
The file delivered by the client must have the extension “.TMP”. Once file transfer is complete, the client
must rename the same file with the extension “.TXT”. This ensures that processing is triggered correctly.
Definition of placeholders:
<contract>
6–7 digit Direct Exchange contract number
<date>
Date of delivery in format YYYYMMDD
<time>
Time of delivery in format hhmmss
Definition of file types:
*.TMP
File extension during delivery (file transfer)
*.TXT
File extension for automatic processing
Documents that do not correspond to the naming conventions will be rejected. The client is responsible for
ensuring that no files with duplicate names are delivered (e.g. see time details in the file name). Direct
Exchange cannot tell if a file has been overwritten.
Since the processing transfers and removes the delivered files from the “Eingang” directory, the files are
no longer visible to the client.
Where DTA files are concerned, both the diskette format and the magnetic tape format are supported.
Please note that the debit account number must be in Multicash or IBAN format.
4.2
Collection of Account Information in “Ausgang” Directory
Information for the services BESR, MT940, MT942, processing logs DTA, LSV+, and e-documents is
provided in two file types in each case:
(a) A collective file with a fixed name. It contains the complete cumulated current information and remains
in the directory until collected by the client.
(b) In addition, the data from each new updated delivery is made available to the client as backup and also
made available as separate files (one-time original file). These files are automatically deleted after 60 days.
The files delivered by the client must have the extension “.TMP”.
The client is responsible for deleting the collective files once the transfer is complete.
Definition of placeholders:
<contract>
6–7 digit Direct Exchange contract number
<date>
Date of delivery in format YYYYMMDD
<time>
Time of delivery in format hhmmss
Definition of file types:
*.TMP
File extension during collection (file transfer)
5.
Establishing a Connection
5.1
Process
The Direct Exchange connection is established within the framework of an IT project paid for on a time
and materials basis. This is commissioned by the responsible IT unit of the client. Technical implementation
on the bank server side is carried out by Fides Treasury Services, a subsidiary of the Credit Suisse Group.
A project kick-off meeting is held to determine the services to be provided by the various partners involved.
Project start
To permit the implementation to be effected efficiently, the client should appoint an IT project manager,
responsible for technical coordination on the client side. A preliminary meeting together with the client IT
project manager lays down the general technical requirements (e.g. IP address, type of connection and
encryption desired). These are defined in a document that includes the following points:
Direct Exchange contract number (predefined by Credit Suisse)
Full company name (Department)
Client contact person for initial technical clarification (internal or external; IT project manager,
responsible for technical coordination and forwarding of information on the client side)
Credit Suisse contact person
Fides Treasury Services contact person
Fixed IP addresses for the connection to be established
Preferred connection type (FTP, etc.)
Technical information on the type of connection chosen by the client (FTP Client, Nodes, MQ Queue
set, certificate type, etc.)
Information on the type of encryption desired (See table in Section 5.2)
Project realization
As soon as the general technical requirements are defined, the handover to Fides Treasury Services takes
place. Fides organizes a kick-off meeting for project commencement and further planning.
Establishment of the connection is then generally carried out as follows:
Establishment of a VPN (Virtual Private Network) if desired
Establishment of actual connection
Testing of delivery and collection by client
Determination of correct functioning
Project conclusion meeting: A debriefing form must be completed at this meeting. Amongst other
things, it contains the type of connection and encryption chosen.
Operation
5.2
Encryption
The kind of encryption is determined by the client and may consist of a software or hardware solution.
Credit Suisse recommends that individual data packets are encrypted before being transmitted via a
communication protocol, to eliminate unauthorized access. The sender and the recipient always remain
unencrypted.
Figure 1: Overview of communication type and software encryption
Communication type
Software encryption
FTP
MQ
Fileact
SWIFT
Other type of communication
6.
E-Documents
6.1
Introduction
E-documents are digitally signed bank records that are delivered electronically. They are identical to the
paper versions. For example, payment-related debit advices, account statements, and fund settlements
can be sent as e-documents.
The key benefits of e-documents for you, the client:
As the records are not sent by post, they are often available more quickly.
Using less paper helps to protect the environment
The digital signature confirms that the electronic documents were created by Credit Suisse and that
they have not been altered.
Large selection of documents available
Further information can be found at
www.credit-suisse.com/edocuments
6.2
Overview of E-Document Services via Direct Exchange
A new directory is being set up in Direct Exchange, via which e-documents can be retrieved.
In addition to the e-documents in PDF format, a separate XML file of metadata from the PDFs is also
delivered. This metadata contains useful information on the e-documents which can be used for a search,
or with which your software can assign the e-documents to individual users or accounts, for example.
6.3
Download Steps for E-Documents
The following steps for downloading e-documents are possible, depending on the software used.
Downloading of the e-documents and XML file via a new “E-documents” session
Allocation and granting of user rights in the software
Checking of digital signature and storing of the verification document
Archiving of e-documents: Electronic archiving – as required by law – using automated processes
spares you the previously time-consuming archiving of paper documents and saves HR and archiving
costs.
Overview of e-documents, search function.
The following points should be noted regarding downloads:
E-documents are downloaded as PDF files with accompanying XML file containing metadata
Once the PDFs and XML file have been retrieved, they are deleted from the Direct Link server. I.e.
they must be saved by the client to be retained.
We recommend a regular download of e-documents.
Availability: E-documents become ready for delivery every hour between 5 a.m. and 6 p.m. The
greatest volume is to be expected in the morning. During end-of-quarter processing, there may be a
delay in bank records becoming available, owing to the high volume of data.
User Rights
Credit Suisse activates e-documents for each Direct Exchange user contract. Thus, e-documents can be
received via the Direct Exchange interface for as many accounts and safekeeping accounts as wished.
The access rights must be set up through the client’s own software.
Checking of Digital Signatures
All Credit Suisse e-documents bear digital signatures. The digital signature forms part of the PDF
document. A digital signature confirms the following:
1. The documents were issued by Credit Suisse.
2. The documents have not been altered.
The signature can be checked by the software. You can find more information on digital signatures at
www.credit-suisse.com/edocuments
under Digital Signature.
6.4
File Names
The name of the PDF will contain a three-digit serial number:
<pdf_name>_<3-digit-running-number>.pdf; the file name for each individual e-document is thus unique. The first document to be
downloaded will be given the serial number 000. The number will increase by 1 for each subsequent
download.
The metadata file will be called: edoc_metadata_<contract>_<date>_<time>.xml, in the collective file
metadata file edoc_metadata_<contract>.xml.
6.5
Metadata
6.5.1
Separate XML File
E-documents are always made available as PDF files. Alongside the actual business data (PDF files), an
XML file is sent for each transport (successful transmission of PDFs) containing the metadata from all the
PDFs being delivered. The XML file contains references to the e-documents in question as well as
metainformation. You can find the name of the XML file in section 6.4.
6.5.2
Structure of the XML File
The XML file is structured as follows:
6.5.3
Included Metadata
The XML file contains the following metainformation for each e-document. Further metadata may be
added in future, e.g. the IBAN number.
Metadata on the E-Document
No. Field Name
Mandatory
Status
Brief
Description
Explanation
Possible Values/
Field Formats
Attributes
1
XC101_RECIP_CIFNR
Y
Recipient CIF
associated with
the document
“Mailbox”
083501234561
CHAR(12)
2
XC101_DOC_TYP
Y
Document Type
(Four char code
which uniquely
identifies the
document type in
EOS
1)
DIT Number
3006
CHAR(4)
3
XC101_DOC_TRG_FRMT Y
In future, documents
possible in other
formats than PDF
CHAR(3)
4
XC101_APPL_ID
Y
Application ID
Possibility for
Software to group
into payments,
securities etc.
BE01, WS80, AIS etc.,
see chapter 10
CHAR(8)
5
XC101_DATE_BEVENT
Y
Business Event
Date
Booking date
dd.mm.yyyy
DATE
6
XC101_TS_INREP
Y
Timestamp which
shows when
document was
inserted into EOS
repository
2008-09-02-02.29.10.668640
TIMESTMP
7
XC101_IS_ORIGINAL
Y
Flag showing if
original or copy.
Only possible
values are Y/N
Y or N
CHAR(1)
8
XC101_IS_SIGNED
Y
Flag indicating
whether document
has digital
signature or not.
Only possible
values are Y/N
Software can make a
check of the
signature
Y or N
CHAR(1)
9
XC101_DOC_LANG_COD Y
Document
Language code
1, 2, 3, 4 for D, F, I, E
respectively.
CHAR(1)
No. Field Name
Mandatory
Status
Brief
Description
Explanation
Possible Values/
Field Formats
Attributes
10 XC101_OWNER_CIFNR
Y
Owner CIF
number
083501234561
CHAR(12)
11 XC101_TYP_RELATION
Y
Type of account
number, e.g
account, depot or
Money market
Depot, Account or
CIF
65,66,67 for CIF, Depot
or Konto account
CHAR(2)
12 XC101_TYP_BU_RENUM Y
Account Number/
Deposit No/CIF
No
Value in this field
depends upon
XC101_TYP_RELAT
ION
0040012340560002
CHAR(20)
13 XC101_CURRENCY
N
Currency
ISO currency code
CHAR(3)
14 XC101_AMOUNT
N
Amount
21.20
DEC(31,8)
15 XC101_DATE_VALUE
N
Date associated
with the amount
and currency
value date (only if
amount and currency
available)
dd.mm.yyyy
DATE
16 XC101_HAS_DOC_SUP
N
Flag indicating if
there is any
enclosures
associated with
this document
For Marketing
documents
Y or N
CHAR(1)
17 XC101_DOC_FILENAME Y
Download File
Name, including
three-digit
sequence number
PDF name
123456-12-
1_name_yyyy-mm-dd.123.pdf, e.g.
123456-12-1_extract_of_account_20
08-10-23.123.pdf
VC(254)
18 XC101_IS_IMPORTANT
N
Flag which
highlights the
document in
docbox. Only
possible values are
Y/N
Y or N
CHAR(1)
19 XC101_UUID_DOC_C
Y
Document unique
identifier
Unique ID of each
Document
9E8D04B0-813711DC-8004CF02-EC1A2094
CHAR(35)
Metadata on the Enclosures
If field 16 “XC101_HAS_DOC_SUP” contains a “Y”, an enclosure is being delivered along with the
e-document. Although there are further metadata on the enclosure, only the following are relevant:
No. Field Name
Mandatory
Status
Brief
Description
Explanation
Possible Values/
Field Formats
Attributes
1
XC109_SUP_FILENAME
N
Enclosure file name
in PDF format.
Test_Enclosure1.pdf
VARCHAR(254)
6.6
Available Documents
The various e-documents can be classified as follows:
Application ID (Metadata field 4 “XC101_APPL_ID”):
−
AIS/IPC: Statements of investments, performance reports
−
Bonus Points
−
Mortgages
−
Marketing
−
WS80: Securities
−
XBS: Account Documents
−
ZV: Payment Transactions
Document type/DIT number (metadata field 2 “XC101_DOC_TYP”): The DIT number can be used to
assign the e-document to the appropriate area such as Payment Transactions or Mortgages.
Document groups: Every DIT number is assigned to a document group.
Section 10 contains a detailed listing of the feeder applications, document group names and document
types. These tables can also be obtained from Credit Suisse in electronic form.
7.
Formats
7.1
DTA Payment Orders
The DTA format is described in the SIC documentation under “DTA Standards and Formats” (www.sic.ch).
7.2
LSV+ Collections
Details on LSV+ collections can be found in the LSV
+technical documentation or the SIC documentation
on LSV
+(www.sic.ch).
7.3
Credit Transfers
The Credit Transfer pain.001 format in accordance with the Swiss ISO 20022 payments standard is
described in the SIC documentation under "Implementation Guidelines for Credit Transfers"
(www.iso-payments.ch). The features specific to Credit Suisse are outlined in the chapters that follow.
7.3.1
Referencing between pain.001 and pain.002
At Credit Suisse, referencing of payments from pain.001 to pain.002 is completed on the basis of field
2.29 <InstrId>.
7.3.2
Salary and Pension Payments
In accordance with ISO 20022, a marker can be entered in field 2.15 <Cd> to indicate salary or pension
payments using the values "SALA" and "PENS". As the booking and display type in other fields (see
chapter 7.3.3) can be managed flexibly and in a differentiating manner, field 2.15 has no influence on
processing at Credit Suisse. For this reason, the "true" value is used for salary payments in field 2.3
<BtchBookg> and the "CND" value is used in field 2.20 <Prtry>. These values effect a global debit with a
global debit display.
7.3.3
Type of Booking, Type of Display, and Deadlines for Submission
The type of booking, type of display, and deadlines for submission can all be managed flexibly in pain.001
at B level to suit client requirements.
Table1: Type of Booking, Type of Display, and Deadlines for Submission for Credit Suisse
Type of booking
Field 2.3 <BtchBookg>
Priority
Field 2.7
<InstrPrty>
Display management
Field 2.20 <Prtry>
Booking
Display
Deadline for
submission
blank
STANDARD or blank
blank
Multiple booking
Multiple display
07:00
blank
STANDARD or blank
NOA
Multiple booking
No display
07:00
blank
STANDARD or blank
SIA
Individual booking Individual display
07:00
blank
STANDARD or blank
CND
Multiple booking
Multiple display
07:00
blank
STANDARD or blank
CWD
Multiple booking
Document list
07:00
blank
HIGH
blank
Multiple booking
Multiple display
12:00
blank
HIGH
NOA
Multiple booking
No display
12:00
blank
HIGH
SIA
Individual booking Individual display
14:00
blank
HIGH
CND
Multiple booking
Multiple display
12:00
blank
HIGH
CWD
Multiple booking
Document list
12:00
false
STANDARD or blank
blank
Multiple booking
No display
07:00
false
STANDARD or blank
NOA
Individual booking No display
07:00
false
STANDARD or blank
SIA
Individual booking Individual display
07:00
false
STANDARD or blank
CND
Multiple booking
Multiple display
07:00
false
STANDARD or blank
CWD
Multiple booking
Document list
07:00
false
HIGH
blank
Multiple booking
No display
12:00
false
HIGH
NOA
Individual booking No display
14:00
false
HIGH
SIA
Individual booking Individual display
14:00
false
HIGH
CND
Multiple booking
Multiple display
12:00
false
HIGH
CWD
Multiple booking
Document list
12:00
true
STANDARD or blank
blank
Multiple booking
Multiple display
07:00
true
STANDARD or blank
NOA
Multiple booking
No display
07:00
true
STANDARD or blank
SIA
Individual booking Individual display
07:00
true
STANDARD or blank
CND
Multiple booking
Multiple display
07:00
true
STANDARD or blank
CWD
Multiple booking
Document list
07:00
true
HIGH
blank
Multiple booking
Multiple display
12:00
true
HIGH
NOA
Multiple booking
No display
12:00
true
HIGH
SIA
Individual booking Individual display
14:00
true
HIGH
CND
Multiple booking
Multiple display
12:00
7.4
SEPA Direct Debit
The pain.008 format for SEPA direct debits is described in the SIC documentation under "Implementation
Guidelines for SEPA Direct Debits". (www.iso-payments.ch)
7.5
Payment Status Report
The pain.002 format for the payment status report is described in the SIC documentation under
"Implementation Guidelines for Credit Transfers" and under "Implementation Guidelines for SEPA Direct
Debits". (www.iso-payments.ch)
7.6
Account Statement (MT940 and Provisional Bookings/Intraday (MT942)
The formats for account statements and provisional bookings/Intraday of Credit Suisse accounts are
described in sections 7.6.1 through 7.6.4.
7.6.1
Credit Suisse Account Statement (MT940)
Table 3: Structure of Credit Suisse account statement (MT940)
Contents
Format
Example
SWIFT header
{1:F01CRESCHZZ080A0000000000}{2:I940X N2}{4:
Reference no.
16x
:20:XBS/050614/0001
Account no.
35x
:25:4835/1234567-89
[or IBAN on request]
Sequence no.
5n[/5n]
:28C:9/1
Opening balance
1!a6!n3!a15d
:60F:C050808GBP1375,57
Transaction details
26!n[4!n]2a[1!a]15d
1!a3!c16x[//16x][34x]
:61:0508080808D50,50NTRFNONREF//3M80-0806-80-004
Information to account
holder
36 * 65x
:86:1019?33 Mr. John Test 36, Sackville Garden GB - Brighton?60Booking: CS
client – Bank account (SWIFT case without expenses)?23Barclays Bank PLC
Head Office 54 Lombard Street GB-London EC3P 3AH
Final balance (booked) 1!a6!n3!a15d
:62F:C050808GBP479,24
Final balance (value
balance)
1!a6!n3!a15d
:64:C050808GBP3845,64
Balance with post-value 1!a6!n3!a15d
:65:C050809GBP5570,99
:65:C050810GBP53570,99
SWIFT tail
-}
2
Field 61: see section 8.4.4
3Field 86: see section 8.4.5
7.6.2
Credit Suisse Provisional Bookings/Intraday (MT942)
Table 4: Structure of Credit Suisse provisional bookings/Intraday (MT942)
Contents
Format
Example
SWIFT header
{1:F01CRESCHZZ080A0000000000}{2:I942X N2}{4:
Reference no.
16x
:20:XBS/050614/0001
Account no.
35x
:25:4835/1234567-89
[or IBAN on request]
Sequence no.
5n[/5n]
:28C:9/1
Indicator for amount
limit
3!a[1!a]15d
:34F:GBP0,
Date/time indicator
6!n4!n1!x4!n
:13D:0508080751+0200
Transaction details
46!n[4!n]2a[1!a]15d
1!a3!c16x[//16x][34x]
:61:0508080808D50,50NTRFNONREF//3M80-0806-80-004
Intraday
Information to account
holder
56 * 65x
:86:1019?33 Mr. John Test 36, Sackville Garden GB -
Brighton?60Booking: CS client – Bank account (SWIFT case without
expenses)?23Barclays Bank PLC Head Office 54 Lombard Street
GB-London EC3P 3AH
Intraday
Transaction details
46!n[4!n]2a[1!a]15d
1!a3!c16x[//16x][34x]
:61:050808D50,50NTRFNONREF//3M80-0806-80-004
Provisional
bookings
Information to
account holder
56 * 65x
:86:1019
Provisional
bookings
SWIFT tail
-}
The provisional bookings (non-binding) are placed after the Intraday and have no booking date in field 61.
7.6.3
Structure of Field 61 (Credit Suisse)
Table 5: Structure of transaction details
Sub-field Sub-field Contents
1
6!n
Value date (YYMMDD)
2
[4!n]
Booking date (MMDD) [with booking date for Intraday, without for provisional bookings]
3
2a
Debit/Credit (D or C)/for cancellation, Reversal of Debit (RD) or Reversal of Credit (RC)
4
[1!a]
Third character of currency code
5
15d
Amount
6
1!a3!c
N plus business case identification (S plus message type for SWIFT)
7
16x
Client reference, if available (from “Additional supplier text”)
8
[//16x] CS reference (edited order number)
9
[34x]
Additional explanations and/or client references (if too little space in sub-field 7)
4
