Swift for Corporates -

Onboarding Guide

Status: September 2024, Version 1.2

Content

Content
1 General information 4
1.1 Swift for corporates 4
1.1.1 MA-CUG 4

1.1.2 SCORE 4

1.2 Communication channels 5

1.2.1 Swift FIN 5

1.2.2 Swift FileAct 5

1.2.3 Store-and-forward 5

1.2.4 Real-time 5

2 Requirements 6
2.1 Contracts and forms 6
2.1.1 Swift Framework Agreement 6

2.1.2 Swift SCORE Agreement 6

2.1.3 Documentary foreign business 6

2.1.4 Swift FIN order sheets 6

2.1.5 Swift FileAct order sheets 7

2.1.6 Further regulations 7

2.2 Technical requirements 7

2.2.1 Connection to Swift/IT infrastructure 7

2.2.2 BIC 7

2.3 Connection to DZ BANK 8

2.3.1 RMA exchange 8

2.3.2 Setting up to test 8

2.3.3 Technical accessibility and operating hours 8

3 Format overview 8
3.1 General information on specifications 8
3.1.1 ISO 20022 8

3.1.2 MT messages 9

3.2 Supported formats 11

Onboarding Guide 3

General information

4 Test concept 12
4.1 Test scenarios 12
4.1.1 Swift FIN 13

4.1.2 Swift FileAct 13

4.1.3 Validation of file contents 14

5 Further information 14

Imprint 15
Onboarding Guide 4

General information

1 General information

This document is intended for corporate customers exchanging messages with DZ BANK AG (hereinafter
referred to as DZ BANK) via the Swift network. It contains general information about Swift and DZ BANK's
related services. Further information can be accessed via the links provided in this manual.
Essential additions to all message standards and formats offered by Swift can be found in the documents
deposited on Swift.com, including the "Swift User Handbook" and the "Service Description".
DZ BANK is not bound by this manual. DZ BANK reserves the right to amend this manual at any time
without prior notice. This Onboarding Guide has been prepared with the utmost care. Nevertheless, errors
and inaccuracies may occur. DZ BANK accepts no legal responsibility or liability whatsoever for any errors or
their consequences.
No part of this Onboarding Guide may be reproduced or transmitted in any form or by any means,
electronic or mechanical, without the prior written permission of DZ BANK.

1.1 Swift for corporates

The Society for Worldwide Interbank Financial Telecommunication (Swift) is an international cooperative of
financial institutions and the world's leading provider of secure financial messaging services between
banks, brokerage firms, exchanges and other financial institutions. Swift uses its proprietary platform,
which has proven to be highly secure and resilient since its inception. Swift enables the financial industry
and other affiliated members to process messages in an automated and standardised manner. The platform
has an availability of 99.99% in continuous operation (24/7/365).
Swift serves the financial industry in a variety of business areas, including financial messaging, treasury
disposition, payments and cash management, trade finance, trade confirmation (foreign exchange and
securities), messaging settlement, corporate actions, and securities trading and pre-trading.
For global corporates with accounts at multiple banks around the world, international payments and
recurring bulk or high value transactions, Swift provides a single, international standard communication
channel.

1.1.1 MA-CUG
A Member Administered Closed User Group (MA-CUG) is a member-managed service operated by Swift
since 2001. It enables corporate customers to exchange pre-defined messages with their partner banks via
the Swift network. Banks and corporates can belong to any number of different MA-CUGs. In an MA-CUG,
a corporate client connects directly to the bank (one-to-one relationship). For example, MA-CUGs are
suitable for the use of messages that are not permitted in the SCORE model.
DZ BANK does not manage MA-CUGs, but supports corporate customers connecting via SCORE.

1.1.2 SCORE
The SCORE (Standardised Corporate Environment) access model is used for data exchange between the
corporate customer and DZ BANK. Thanks to its uniform rules and multilateral relationships, SCORE has
become the global standard for communication between financial institutions and corporate clients.
In a user group centrally managed by Swift, all corporate customers connected to SCORE can communicate
with all financial institutions connected to the network and use their Swift services. Direct participation in
Onboarding Guide 5

General information

Swift is mandatory for corporate customers to use SCORE. At least one live BIC (Business Identifier Code) is
required. This BIC can be used to connect subsidiaries and affiliates.

1.2 Communication channels

Various services/channels can be used for the technical transmission of messages between corporate clients
and financial institutions.

1.2.1 Swift FIN

Swift FIN is the standard for the exchange of individual financial messages. The message types are stand-
ardised and messages are exchanged via the BIC. Swift validates the message format against the document
and data structure specifications.
Swift FIN is the central store-and-forward service for message processing. FIN enables Swift participants
worldwide to exchange financial data in a secure, fast, and reliable manner.
All Swift participants connect to FIN via a SwiftNet connection. Each Swift participant is responsible for its
own connection to the FIN service within the Swift specifications. The Swift Participant's responsibility in-
cludes the purchase, installation, configuration, security, use and (where applicable) maintenance of appro-
priate equipment, facilities and services required to access the FIN service.
Because FIN is the primary channel for the exchange of individual messages, it is of great importance to
corporate customers in their communication with financial institutions.
DZ BANK offers message exchange via Swift FIN for a wide range of message types. Detailed information
can be found in the following sections.

1.2.2 Swift FileAct

Communication via Swift FileAct allows the transfer of any file between Swift participants. The content of
the files is not checked by Swift. Swift FileAct guarantees secure transmission over SwiftNet in both real-
time and store-and-forward modes. For corporate customers, transferring files via FileAct is an essential
way to exchange the financial messages included under SCORE with financial institutions when it is not
possible or desirable to act on an individual transaction basis.
DZ BANK offers message exchange via Swift FileAct for a wide range of message types. Detailed infor-
mation is provided in the following sections.
Message exchange takes place via the DN (Distinguished Name), further information can be found in the
Swift FileAct Order Sheet.

1.2.3 Store-and-forward
In store-and-forward mode, messages are exchanged between Swift participants regardless of their geo-
graphical location and time zone. The sender can send the message at any time because the receiver does
not need to be online to receive the message. The message is received as soon as the recipient is available.

1.2.4 Real-time
With real-time data transmission, the sender reaches all recipients who are online at the time of transmis-
sion. It is an efficient way to exchange data.
Onboarding Guide 6

Requirements

2 Requirements

To use the Swift service at DZ BANK, the following requirements are necessary.

2.1 Contracts and forms

2.1.1 Swift Framework Agreement

To use Swift's services, a connection to Swift is required. Full connectivity involves signing a framework
agreement with Swift that covers services, tariffs, and technical set-up. Different types of access to Swift
are available, depending on the type of business. Swift will advise the corporate customer as to which op-
tions are available for their business.
To connect to DZ BANK, the customer is required to provide information about access and onboarding to
Swift, as well as the information regarding the Test and Live BIC.

2.1.2 Swift SCORE Agreement

DZ BANK's services are available through Swift SCORE by signing a one-off master agreement with DZ
BANK. The framework agreement can be obtained from your relationship manager.

2.1.3 Documentary foreign business

To use the services of DZ BANK within the scope of foreign documentary business, the one-off conclusion
of the "Framework Agreement for the Electronic Exchange of Data in the Field of Foreign Documentary
Transactions" with DZ BANK is required.
The framework agreement can be obtained from your relationship manager.

2.1.4 Swift FIN order sheets

To use the message exchange via Swift FIN with DZ BANK, it is necessary to commission the service.
The order forms for commissioning payment transaction services or the link to the order forms are available
on the DZ BANK homepage for:
a. payment transactions:
 MT101 (sending and receiving)
b. foreign documentary business:
 MT798 Framework Agreement on Electronic Data Interchange in the Field of Settlement of Foreign
Documentary Transactions, with risk information on foreign documentary business
c. account information:
 MT940 (sending)
 MT942 (sending).
You can obtain this information from your relationship manager.
Onboarding Guide 7

Requirements

2.1.5 Swift FileAct order sheets

To use Swift FileAct messaging with DZ BANK, a Swift FileAct order form is required for each IBAN to be
included. You can obtain the order form, including the applicable special conditions, from your relationship
manager.

2.1.6 Further regulations

In addition, DZ BANK's General Terms and Conditions and other special terms and conditions apply, which
are available at https://www.dzbank.de/content/dzbank/de/home/footer/agb-sonderbedingungen.html.

2.2 Technical requirements

2.2.1 Connection to Swift/IT infrastructure

The corporate customer can choose from a number of different approaches to connect to Swift. The corpo-
rate client has the following options for a connection via a:

- service bureau

- Swift Cloud connection

- Lite 2 Business Application (L2BA)

- direct/on-premises connection.
For more information on connectivity options, please visit swift.com or contact your local Swift representa-
tive. Swift also helps corporate customers to determine the best connectivity option. DZ BANK will provide
a contact if required.

2.2.1.1 Recommendation letter

At the start of the Swift onboarding process, the corporate customer must provide Swift with a recommen-
dation letter. If needed, DZ BANK can help you with that requirement.

2.2.2 BIC
Swift participants receive a unique identifier from Swift in the form of an 8-digit or 11-digit Business Identi-
fier Code (BIC).

DZ BANK BICs Production Test

GENODEFF GENODEF0
GENODEDD GENODED0
Onboarding Guide 8

Format overview

2.3 Connection to DZ BANK

2.3.1 RMA exchange

The Relationship Management Application (RMA) is an important part of Swift security. It is used to man-
age business relationships between Swift participants. The application or platform defines the types of mes-
sages that can be exchanged (i.e. sent and/or received) between Swift participants. This prevents unwanted
message exchange and reduces operational risk.
The recording of data in the RMA for a new corporate customer connection takes place with the exchange
of RMA keys before the start of test and production operations.
DZ BANK exchanges RMA keys for at least the following BICs:

- GENODEFF

- GENODEDD.
Depending on the type of message, other RMA keys may need to be exchanged. If necessary, DZ BANK will
provide information on this before the start of production.

2.3.2 Setting up to test

Each Swift participant must have a functioning Swift test environment with its own Swift test identifier
("Test BIC") for the execution of tests. It is not possible to submit messages with a production Swift identi-
fier to the test environment.
We recommend that Swift participants test all required message types in the test environment before going
live.
Further information on running tests with DZ BANK can be found can be found in Section 4 below.

2.3.3 Technical accessibility and operating hours

Technical operating hours are set out in the Special Terms and Conditions for all Payment Services to Busi-
nesses, available at https://www.dzbank.de/content/dzbank/de/home/footer/agb-sonderbedingungen.html.

3 Format overview

3.1 General information on specifications

3.1.1 ISO 20022

3.1.1.1 DK standard
DZ BANK accepts data formats that comply with the specifications of the German banking industry (DK).
The valid specifications can be downloaded from https://www.ebics.de/de/datenformate.

3.1.1.2 CGI in SEPA payments

To provide DZ BANK's corporate customers with up-to-date solutions and enhanced options for modern
SEPA payment transactions, DZ BANK supports the harmonised CGI standard. The specifications and an
Onboarding Guide 9

Format overview

XSD
("validation scheme") are available for download at firmenkunden.dzbank.de/formatwizard

3.1.1.3 CGI in international payments

DZ BANK supports the harmonised CGI standard to provide DZ BANK's corporate customers with up-to-
date solutions and enhanced options for modern international payment transactions. Please contact your
relationship manager who can provide you with the specifications for CGI AZV.

3.1.2 MT messages
The following sections describe in detail only those message types that are most commonly used between
corporate customers and DZ BANK. More detailed information on these and all available message types can
be obtained directly from Swift.

3.1.2.1 Swift MT header

Each Swift message has a unique header. This header is required for all message types, regardless of
whether the message is transmitted via Swift FIN or Swift FileAct.
Using the Swift FIN MT101 message as an example, the assignment of the header appears as follows:
{1:F01GENODEFFCXXX00000000} {2:I101RZBAATWWXXXXN} {3:} {4:
GENODEFFXXX
RZBAATWWXXX
101
}
The message consists of a total of four segments:
1. Basic Header Block
2. Application Header Block
3. User Header Block
4. Text Block (MUG Block).

1. Basic Header Block

{1:F01GENODEFFCXXX00000000}; the specification contains exactly 29 characters.

Block Name This is the first character in the block, in this case a
1.
Application name Indicates the application for transmission, in this
case FIN = F.
Service description Describes the field of application, where 01 stands
for FIN and 21 for Acknowledgement (ACK) or
Negative Acknowledgement (NAK).
Onboarding Guide 10

Format overview

LT (logical terminal) Address System addition to the BIC, e.g. X, A-D; this adds
one character to the BIC and displays it with 12
digits.

2. Application Header Block

{2:I101RZBAATWWXXXXN}

Block Name This is the first character in the block, in this case a
2.
Input/ Output Distinguish whether it is an input or a dispatch:
I = Input
O = Output.
Message type Indicates the message type, in this case 101.
Identification of the counterparty BIC of the counterparty, including LT address and
branch identifier, 12 digits.
Message priority U - Urgent
N - Normal
S - System

3. User Header Block

This is an optional block for corporate customers. We recommend that you do not use this block.

4. Text Block (MUG Header)

{4:
GENODEFFXXX
RZBAATWWXXX
101
}

Block name This is the first character within the block, in this
case a 4.
Identification of the counterparty BIC of the sender.
Identification of the counterparty BIC of the recipient.
Message type Indicates the message type, in this case 101.
Onboarding Guide 11

Format overview

This is an optional block for corporate customers.

General notes
When assigning the headers, the following should be considered:

- If the Basic Header and the MUG Header are used in parallel, the information in the Basic Header
takes precedence

- If only the MUG header is used, the Basic Header is generated from the data

- Care must be taken to ensure that the sender and receiver BICs are not identical.

3.2 Supported formats

DZ BANK mainly supports the following message types in exchanges with customers. If you would like to
exchange other message types, please contact us.

SWIFT FIN CORPORATE CLIENT TO DZ DZ BANK TO CORPORATE

BANK CLIENT
CATEGORY 1 MT101 Request for Transfer MT199 Free Format Message
MT199 Free Format Message
CATEGORY 3 MT300 Foreign Exchange MT300 Foreign Exchange
Confirmation Confirmation
MT320 Fixed Loan / Deposit MT320 Fixed Loan / Deposit
Confirmation Confirmation
MT399 Free Format Message MT399 Free Format Message
CATEGORY 5 MT535 Statement of Holdings
CATEGORY 7 MT798 “trade envelope” MT789 “trade envelope”
CATEGORY 9 MT999 Free Format Message MT940 Customer Statement
Message
MT942 Interim Transaction
Report
MT999 Free Format Message

SWIFT FILEACT CORPORATE CLIENT TO DZ DZ BANK TO CORPORATE

BANK CLIENT
ISO20022 Pain.001 Pain.002
Onboarding Guide 12

Test concept

SWIFT FILEACT CORPORATE CLIENT TO DZ DZ BANK TO CORPORATE

BANK CLIENT
Pain.008 Camt.052
Camt.053
MT MT101 Request for Transfer MT940 Customer Statement
Message
MT789 “trade envelope”
MT942 Interim Transaction
Report
MT999 Free Format Message
MORE Data formats compliant with the Data formats compliant with the
DK standard DK standard

3.2.1.1 MT101
The Swift MT101 message is a transfer request (also known as RfT = Request for Transfer) sent by a com-
pany to a third-party bank. The message triggers transactions on the third-party account by the originator,
which are then executed by the third-party bank.
A format specification can be provided by DZ BANK.

3.2.1.1 MT940, MT942

The Swift MT940 message is the electronic account statement. It contains the transactions and the account
balance. The file is generated daily at the end of the day when transactions have taken place and is auto-
matically sent to the corporate customer.
The Swift MT942 message is an electronic transaction report. It contains the transactions and the account
balance. The file is generated several times a day as transactions take place and is automatically sent to the
corporate customer.

4 Test concept

4.1 Test scenarios

As mentioned above, DZ BANK recommends that you test the connection or the format of the messages
and files before you start exchanging messages.
The first test refers to the test connection. In this case, send a payment file or a message via the test con-
nection or to the test BIC.
Please note: The results achieved in the test environment do not
guarantee the start of production and that no rights or obligations can be derived from them. We therefore
recommend that you carry out a series of penny tests on your production connection once you have
Onboarding Guide 13

Test concept

completed the tests in the test environment. For data protection reasons, we also recommend that you do
not use any personal data in your test files, or only use anonymised data.

4.1.1 Swift FIN

As explained in the introduction, the test connection must be checked at the beginning. To do this, send a
message from your test environment to DZ BANK's test BIC. If the test was successful, you will receive an
acknowledgement (ACK) or a rejection (NACK).
We recommend that you discuss the timing of the test with your relationship manager in advance so that
the test can be completed in a timely manner.
Production testing
Once testing is complete, we recommend that you run a penny test, i.e. an order with a small amount in
the pennies range. This is the same process as the test, but it takes place in the production environment.
The aim is to ensure that order processing works correctly in the production environment.
If the tests in the production environment are successful, the testing process is complete and the transition
to the production environment can take place.

4.1.2 Swift FileAct

Once the test connection has been tested as a whole, you can create a test file in the following format:
pain.001.
Please refer to the notes in Section 3.
It is possible to test formats for correct allocation before first dispatch. Please contact your relationship
manager if you require this service.
Please note that within the test environment there is no connection to the production environment, so it is
not possible to test, for example, a booking run.
Procedure and requirements:

1. You send (test) files with the same mapping and method that will be used in the production environ-
ment

2. You send (test) files that comply with the specifications given by DZ BANK, including the type of re-
quest. Checks are possible before the test begins.

3. The address is specified in the FileAct header as Swift.corp.fa!p to ensure that the message is sent to
the test environment and not the production environment:

- If the file delivery was successful, you will receive an ACK

- If the check of the connection and the order data was successful, you will receive a pain.002 with
the acknowledgement

- If there is a problem with the delivery, you will receive a NACK (Negative Acknowledgement). This
is not followed by a pain.002 message because the file was rejected at an early stage in the pro-
cessing chain
Onboarding Guide 14

Further information

- If the delivery was successful but the validation of the order data was negative, you will receive a
pain.002 with the reason for the rejection.

Production testing
Once testing is complete, we recommend that you run a penny test, i.e. a job with a small amount in the
pennies range. This is the same process as the test, but now in the production environment. The aim is to
ensure that the processing of orders works correctly in the production environment.
If the tests in the production environment are successful, the testing process is complete and the transition
to the production environment can take place.

4.1.3 Validation of file contents

DZ BANK's Test Centre, called Format Wizard, is available to check the content of message formats before
they are sent. The DZ BANK Format Wizard allows you to validate a file before the live system starts testing.
Once access has been set up, you can upload your files and receive a data validation including a validation
report. After testing, if required, pain.002 files can be generated from the uploaded file. The Format Wiz-
ard is available in German and English to DZ BANK's corporate customers.

5 Further information

DZ BANK Corporate Banking

DZ BANK Format Wizard
Swift.com (Swift for Corporates)
EBICS - Electronic Banking Internet Communication Standard
Swift.com CGI Market Practice
Onboarding Guide 15

Imprint

Imprint

DZ BANK AG

German Central Cooperative Bank,

Frankfurt on the Main

Republic Square

60325 Frankfurt am Main

Postal address

60265 Frankfurt am Main

Phone + 49 69 7447-01

Fax + 49 69 7447-1685

[email protected]

www.dzbank.de

Board of Directors:

Dr. Cornelius Riese, Vorstandsvorsitzender

Souâd Benkredda

Uwe Berghaus

Dr. Christian Brauckmann

Ulrike Brouzi

Johannes Koch

Michael Speth

Thomas Ullrich