Account Information Test Data Service

Account Information Test Data Service
SEPA Test & Migration Suite
SEPA test files for further processing in your systems (MT94X, DTI, CAMT)
The Account Information Test Data Service checks applications that currently process Commerzbank cash
management information for the changes that accompany SEPA payment transactions.
1. General
1.1
Overview
1.2
Functionality
● Provision of electronic account statements and transaction data for existing accounts with
fictitious SEPA transactions to test further processing procedures in electronic banking systems and other systems (e.g. financial accounting)
● The format of the test data corresponds to the live cash
management information, i.e. balance, transactions, account statement and breakdown of
bulked payment transactions
● The test data consists of “classical” DTAUS and SWIFT-FIN
formats as well as ISO/XML formats (camt.05x)
● If required, data for virtual accounts and transactions with varying originators and recipients
can be created
● As all relevant types of SEPA transactions are mapped, transactions that are atypical for
your accounts may be included
● A range of account information files are possible:
Corporate Banking
1 February 2014
-
SWIFT MT940 (STA) files
-
SWIFT MT942 (VMK) files
-
SDD-DTI (payment information block, direct debits)
-
SCT-DTI (payment information block, credits)
-
ISO CAMT account information
Corporate Banking | Account Information Test Data Service
1 February 2014 | Page 2
● Originator data is adapted to your Commerzbank accounts (enables realistic testing of fur-
ther processing)
1.3
Benefits
● No need for adjustments to the test files
● No follow-up work after the introduction of SEPA
2. Details
2.1
Procedure
● Agreement of the required account information types (MT940, MT942, SDD-DTI, SCT-DTI,
ISO CAMT) and the individual
master data of the test files (account holder, account number
and bank code)
● Address data is also additionally required for CAMT files (street, house number, postcode
and town/city)
● Provision of the required data as an archive in ZIP format
2.2
Format description
Archive content for the classical formats:
Formats MT940, MT942, DTI
Archive file TESTER_20.03.2013.zip
Content:
mt940_kontoauszug_20.03.2013.sta
(account statements in MT940 format)
mt942_umsatzanzeige_20.03.2013.vmk
(transaction overview in MT942 format)
gvc194_20.03.2013_.dti
(breakdown of payment information block in DTA-DTI-SCT
format)
gvc195_20.03.2013_.dti
(breakdown of payment information block in DTA-DTI-SDD
format)
Archive content for ISO/XML formats:
ISO/XML formats CAMT.052/053/054
Archive file TESTER_20.03.2013.zip
Content:
2013-03-20-C52-<IBAN>-EUR-<lfd. Nr. 6stellig>.xml
(transaction overview in XML format camt.052; content
equivalent to MT942)
2013-03-20-C53-<IBAN>-EUR-<lfd. Nr. 6stellig>.xml
(account statement in XML format camt.053; content
equivalent to MT940)
2013-03-20-C54-<IBAN>-EUR-<lfd. Nr. 6stellig>.xml
(breakdown of payment information block in XML format
camt.054; content equivalent to DTA-DTI)
Corporate Banking | Account Information Test Data Service
2.3
Posting scenario
1 February 2014 | Page 3
A posting for each of the 22 SEPA transaction codes (GVC = Geschäftsvorfallcodes) set out
below is contained the test files. The following applies:
● The following special cases are only included subject to agreement:
-
Postings with virtual accounts
-
Postings with varying originators/recipients
● The bulked payment transactions for transaction codes 194 and 195 comprise three or two
single postings for each of which a DTI file exists in the test data
The following table shows all transactions supplied.
The names of the DTI files with the single postings for payment information blocks contain the
corresponding transaction codes:
● Transaction code 194
- file gvc194_Datum.dti
● Transaction code 195
- file gvc195_Datum.dti
Overview of the SEPA transactions contained in the test files:
Transactions
Trans.
code
Direct Debit (single posting – debit, B2B)
104
Direct Debit (single posting – debit, Core)
105
Direct Debit (debit; return debit, B2B)
108
Direct Debit (debit; return debit, Core)
109
Credit Transfer (single posting – debit)
116
Credit Transfer (single posting – debit, donation)
119
Credit Transfer (single posting – credit, wages credit, salary credit, pension credit)
153
SEPA Credit Transfer (single posting – credit, capital-forming payments)
154
Credit Transfer (single posting – credit, remittances of public treasuries)
156
Credit Transfer returns (credit) for undeliverable remittance (return remittance)
159
Credit Transfer (single posting – credit)
166
Credit Transfer (single posting – credit, donation)
169
SEPA Direct Debit presentation (single posting – credit, Core)
171
Direct Debit (single posting – credit, B2B)
174
Credit Transfer online (single posting – debit)
177
Direct Debit (credit; re-credit, Core)
181
SEPA Direct Debit (credit; re-credit, B2B)
184
Credit Transfer (payment information block – debit)
191
Direct Debit (payment information block – credit, Core)
192
Credit Transfer (payment information block – credit) breakdown of bulk posting into three single credit
postings in DTI file “gvc194_20.03.2013.dti”
194
Direct Debit (payment information block – debit, Core) breakdown of bulk posting into two single direct debit
postings in DTI file “gvc195_20.03.2013.dti”
195
Direct Debit (payment information block – credit, B2B)
196
Corporate Banking | Account Information Test Data Service
2.4
Format variantes
1 February 2014 | Page 4
If required, the test data may be produced with virtual accounts and/or varying
originators or recipients.
Virtual accounts are mapped as follows:
Classical formats
Formats MT940 (STA) and MT942 (VMK) can contain
virtual accounts in field 86 in sub-fields 10 (key ?70,
followed by the name of the account holder) and
11 (key ?71, followed by VKTO (virtual account) and
BLZ (bank code).
ISO/XML formats
In CAMT.053 (C53) in sections
<Ntry> .. <RltdPties> .. <Dbtr> and <Cdtr>
For example:
<NtryDtls>
<TxDtls>
<RltdPties>
<Dbtr><Nm>MUSTERMANN VIRT</Nm></Dbtr>
<DbtrAcct><Id><Othr>
<Id>50040060/5534567820</Id>
</Othr></Id></DbtrAcct>
<Cdtr><Nm>VIRT TESTKONTO</Nm></Cdtr>
<CdtrAcct><Id><Othr>
<Id>20040000/200080000</Id>
</Othr></Id></CdtrAcct>
..
</NtryDtls>
Varying originators/recipients are mapped as follows:
Classical formats
Formats MT940 (STA) and MT942 (VMK) may contain
varying originators/recipients in field 86 in the sub-fields
with keys ?20 to ?29, whereby ABWA+ denotes a varying
originator, and ABWE+ a varying recipient.
Corporate Banking | Account Information Test Data Service
1 February 2014 | Page 5
ISO/XML-Formate
In CAMT.053 (C53) in sections
<UltmtDbtr> (varying originator) and
<UltmtCdtr> (varying recipient)
For example:
<PmtInf>
..
<DrctDbtTxInf>
..
<UltmtDbtr>
<Nm>Test Miete</Nm>
</UltmtDbtr>
3. Liability
The bank shall be liable for acts for which it is at fault. If the customer has contributed to the occurrence of a loss through
acts for which the customer is at fault, the principles of contributory negligence shall be used to determine the extent
to which the bank and the customer shall each bear the loss. Any damage claims by the customer shall be limited to the
amount of 1 million Euro. Any claims for consequential damage shall be limited to a maximum of 12,500 Euro. These
limitations of the amount recoverable in liability claims shall not apply in the event of wilful conduct or gross negligence
on the part of the bank.
Components of the Commerzbank SEPA Test & Migration Suite
● IBAN Master Data Service
Converts your account number and bank code master data into IBAN and BIC for nine countries
● Account Validation Service
Checks the master data of your business partners who have a Commerzbank account
● Account Information Test Data Service
SEPA test files for further processing in your systems (MT94X, DTI, CAMT)
● Format Checking Service
Tests your SEPA files (PAIN.001, PAIN.008)
● DTAUS Conversion Service of ComTS (credits and direct debits)
Converts DTAUS files to SEPA
● DTAUS Conversion Simulation Service
Checks your existing payment transactions for SEPA compatibility