swiss iso 20022 harmonization for software vendors credit ... · pdf fileswiss iso 20022...

Swiss ISO 20022 Harmonization

for Software Vendors

Credit Suisse Best Practice Guide

Public

CREDIT SUISSE (Switzerland) Ltd., Software Partner Management

April 2018

(content subject to change) Best Practice Guide 2/77 April 2018

Client support for pain.001 will peak in 2Q 2017. Flatten that peak by switching Credit Suisse clients to pain.001 earlier. Contact [email protected] to discuss your options.

Introduction

Top 7 General Swiss Payment Standards ISO 20022 Issues

ISO 20022 is a new complex standard to all market participants, interpretation mismatches can cause problems

Test with all financial institutions important to you. See pages 59-76 for Credit Suisse details.

There’s no way around ISO 20022...

The QR-bill will replace ISR/IS due to money laundering regulations. Only native ISO 20022 can transfer the required data easily, restraining “DTA to pain.001” converters. Also, QR-bill debit notes will only be available in ISO 20022. All other payment types are also being switched to ISO 20022.

Master data is as important as formats, it must be up to date and structured

Financial institutions will increase matching of creditor master data. This data will increasingly be transmitted in a structured form. Therefore your software must be able to provide this data in a structured way. See page 30 for details.

Advice steering is more than nice to have

ISO 20022 provides electronic and paper advice steering per payment order. Offer this option to your clients, particularly to avoid wrong reporting for salary payments. Implement all 5 combinations with Swiss Business Rules terminology. See pages 20-22 for details.

... but don’t feel forced to use intermediate formats

V11 and LSV have intermediate ISO 20022 formats which can be avoided with many financial institutions. See page 8 for details.

Migrate your clients early

Keep to the standard Don’t use AOS as standard for all financial institutions. See next page for major format traps.

mailto:[email protected]


Introduction

Top 5 Format Traps

Don’t allow several currencies per B-Level

Issue Reference

Swiss Business Rules Version 2.6.2 Chapter 4.3.1

Comment

Credit Suisse and other banks do not provide this AOS* for collective booking. This AOS will be discontinued in November 2018 anyway. In addition, Credit Suisse recommends one currency per B-Level for single booking. See page 38 for details

SALA is not sufficient for salary payments, implement advice steering

Swiss Business Rules Version 2.6.2 Chapter 4.11 and 4.7

SALA has no effect on the type of processing and advices. Advice steering has to be implemented instead. See pages 20-22 for details.

Don’t allow Payment Type Information on several levels

Swiss Business Rules Version 2.6.2 Chapter 4.5.2.2

Instruction Priority (HIGH), Service Level (SEPA), Local Instrument (e.g. CH01) and Category Purpose (SALA) have to be in the same level (B or C). See page 37 for details.

Avoid payments grouping version «separate», use «mixed» instead

Swiss Business Rules Version 2.6.2 Chapter 4.2

In pain.001, the B-Level controls the booking method, the C-Level controls the transactions (payments). If you choose the grouping version «separate», every transaction (C-Level) will be in one B-Level. In practice, this makes collective bookings impossible. Use «mixed» instead.

CH03 is not payment type 3

Swiss Implementation Guidelines for pain.001 Version 1.7.2 Chapter 2.2.1

Local Instruments CH01, CH02 and CH03 mark Swiss inpayment slips. CH03 is for payment type 2.2, not 3. See pages 28 and 31 for details.

* Additional Optional Service


Agenda

Framework

Formats

Use Cases

Test Procedure

Page 5

Page 11

Page 23

Page 58


Agenda

Framework

Formats

Use Cases

Test Procedure

Page 11

Page 23

Page 58


Framework: Credit Suisse Client Channel Functionality

Overview of Connectivity Portfolio

Direct Business, Direct and Direct Net

Software

Content offering

File transfer method

Installation reusability

Clients

Manual/automated

log-in & file transfer

Direct Link Direct Exchange

Manual

Internet web browser

Corporate and private

Operating systems Any

Login manual, upload/ download automated

Dedicated third-party software vendors

Any

Automated


Corporate

Microsoft Windows

Any third-party software vendor

Any

No pain.002, reduced camt

Full range

HTTPS HTTPS Intersys SFTP or FTPS

N/a CS clients Yes No, individual configuration

ISO 20022 impact on

connectivity

Platform update at Credit Suisse New platform at Credit Suisse

Migration impact

on client connectivity

None Silent migration. Additional log-in method.

Silent migration Attended migration, changing credentials M

igra

tio

n

Tra

nsm

issio

n

Tech

no

log

y

User

Syste

m

Tech

no

log

y

Ch

annel

Ch

ara

cte

ristics

No pain.002, no CGI, no EPC, reduced camt


Any

EBICS

Yes

Attended migration, changing credentials

No CGI, no camt

SWIFT FileAct

Dedicated third-party software vendor

Any

FileAct

Yes

Migrated

Advantage

Restriction

Neutral attribute

Legend:

GUI

(browser-based) DXI

(Service Interface)

Content offering

Clients Corporate (Direct Business and Direct Net) Private (Direct and Direct Net)

Corporate

No pain.002, no CGI*, no EPC*, reduced camt

Full range No pain.002, no CGI, no EPC, reduced camt

No CGI, no camt

Additional security SecureSign SecureSign No No Electronic Distributed Signature (EDS/VEU)

No

* Direct


Direct Link

EBICS Intersys

ISO 20022

Test Platform

SWIFT FileAct Direct Exchange

SFTP

Direct Business, Direct

and Direct Net

GUI DXI

pain.001

pain.008

pain.002

camt.052

camt.053

camt.054

Debit/Credit

camt.054

ISR

SIC

EPC

CGI

SIC

EPC

SIC

EPC

CGI

SIC

CGI

SIC

CGI

SIC

CGI

SIC

CGI

Yes Yes

Yes No

Yes No

Yes Yes

No Yes

Yes Yes

Yes No

Yes No

Yes No

No Yes

Yes No

No Yes

4Q 2018 No

No 4Q 2018

Yes No

No Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

No

Examples

Examples

Examples

Examples

No

No

No

No

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

4Q 2018

4Q 2018

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

Yes

4Q 2018

4Q 2018

Yes

Yes

Yes

No

No

No

No

No

Yes, without details*

No

No

No

No

Yes*

No

Yes**

Yes**

Yes, without details*

No

No

Available now

Restriction

Available in the future

Legend:

Framework: Credit Suisse Client Channel Formats

Overview of Format Portfolio per Channel

Message Market

Practice

* only Direct Business, not Direct Net and Direct; activation of full camt.053 details via Electronic Banking Desk 0800 88 11 88 ** only Direct Business and Direct Net, not Direct


Framework: Credit Suisse Client Format Strategy

Overview of ISO 20022 Format Portfolio

MT101

LSV Unknown yet, stay currently with LSV pain.008 CH-TA*

camt.053/camt.052

camt.054 QR

ISR V11 camt.054 ISR Stay with V11 until ISR is discontinued

MT940/MT942

camt.054 Debit/Credit

pain.001 DTA

Message Type Old Format Intermediate Format New Format Target

Credit Transfer

Direct Debit

Reporting

* not offered by Credit Suisse

Phase-out format

Target format

Obsolete format**

Legend:

** other financial institutions may require these intermediate formats


Framework: Migration Timetable (1/2)

Credit Suisse Formats and Connectivity

Format discontinued by Swiss financial marketplace

Format expected to be discontinued by Swiss financial marketplace New formats

Old formats

2018 2019 2020

1Q

Credit Transfer

2Q

1Q

3Q

4Q

2Q

2Q

4Q

1Q

3Q

4Q

3Q

Direct Link / Direct Exchange

Direct / Direct Business / Direct Net


Direct Business / Direct Net

Direct Debit




pain.001 SIC

DTA & DTA Protocol

pain.008 & pain.002 SDD SIC/EPC

LSV / LSV Protocol (HTML/XML)

Direct Link / Direct Exchange pain.002 SIC/EPC/CGI

Direct Link / Direct Exchange pain.001 EPC/CGI

Direct Business / Direct Net (only GUI, not DXI)

2021 2022

2Q

2Q

4Q

1Q

3Q

4Q

3Q

1Q

Direct Link* / Direct Exchange pain.002 for LSV

* EBICS only


2018 2019 2020

1Q

2Q

1Q

3Q

4Q

2Q

2Q

4Q

1Q

3Q

4Q

3Q

2021 2022

2Q

2Q

4Q

1Q

3Q

4Q

3Q

1Q

Framework: Migration Timetable (2/2)

Credit Suisse Formats and Connectivity

camt.052 SIC/CGI Direct Link / Direct Exchange

camt.053 SIC/CGI Direct Link / Direct Exchange

Direct Business**

camt.054 ISR SIC Direct Link / Direct Exchange

Direct Business

V11 Direct Link / Direct Exchange


MT940 Direct Link / Direct Exchange


MT942 Direct Link / Direct Exchange


Direct Business

camt.054 QR SIC

Reports

camt.054 QR CGI Direct Link / Direct Exchange

* Available from introduction of QR-bill ** Without details

camt.054 ISR CGI Direct Link / Direct Exchange

camt.054 Debit/Credit SIC/CGI Direct Link / Direct Exchange

*

*

*


Agenda

Framework

Formats

Use Cases

Test Procedure

Page 5

Page 23

Page 58


Formats: Credit Transfer

pain.001 Credit Transfer Initiation

pain.008 pain.001 pain.002

camt.053 camt.052 camt.054

pain.001.001.03 (SIC: pain.001.001.03.ch.02)

Use flavor SIC as it covers all Swiss payments and all CS channels

Clients can use Swiss CGI if you already use CGI in other countries

camt control can be done in pain.001, details see page 20-22 (some banks ignore this camt control) SALA flag in pain.001 without effect, details see page 35/36 (some banks still use the SALA flag as an AOS) Master data should be sent in a structured way, details see page 38

MT101 for single payments (SWIFT FIN or Fides)

Timing

DTA

pain.001

Name Market Scheme Payments

SIC Switzerland 1.7.2 SIX** All (domestic e.g. ESR & x-border e.g. SEPA) EPC Euro Currency 7.0 EPC SEPA CGI (CH) World with Swiss specialties (e.g. ISR) 14.10.2010 All (domestic e.g. ESR & x-border e.g. SEPA)

Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Business GUI DXI only SIC SWIFT FileAct

Best Practice

Caution

Alternative practice

Alternative formats

Channels

Flavors

Version

*

Possible data reduction due to data conversion *

Timing

CS ISO offering

CS ISO offering recommendation

CS ISO offering alternative

CS Non-ISO alternative

Please consider this

CS legacy offering

2017 2018 2019 2020 2021

Scheme 1.8 planned 4Q18 **


Formats: Direct Debit

pain.008 Direct Debit



pain.008.001.02 (SIC: pain.008.001.02.chsdd.02)

Use SIC or EPC for SEPA Direct Debit (SDD). Use LSV until its future use and timeline is defined.

None, pain.008 CH-TA not part of the Credit Suisse offering

No official recommendation on whether to use SIC or EPC for SDD Final future standard LSV yet to be defined

None, eBill planned to have the same format as Direct Debit

LSV

pain.008 SDD


SIC Euro Currency 2.3 SIX SEPA (Core & B2B) EPC Euro Currency 2017 V1.0 EPC SEPA (Core & B2B) CHLS Switzerland Upcoming Former LSV+ and BDD

Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Business GUI/DXI SWIFT FileAct

Best Practice

Caution


Channels

Flavors

Version

Timing

Alternative formats

CS ISO offering





CS legacy offering

2017 2018 2019 2020 2021


Formats: Status Report

pain.002 Status Report



pain.002.001.03 (SIC: pain.002.001.03.ch.02)

Same flavor as the pain.001 or pain.008 triggering the pain.002

Not available via Direct Business and Direct Net (status indication in the GUI only) Partially accepted: only incorrect parts are reported SIC includes positive and negative status reports, EPC only includes negative status reports Positive status reports are only transmission confirmations, not execution confirmation


SIC Switzerland 1.0 SIX All (domestic e.g. ESR & x-border e.g. SEPA) EPC Euro Currency 7.0 EPC SEPA CGI (CH) World with Swiss specialties 30.11.2009 All (domestic e.g. ESR & x-border e.g. SEPA)

Direct Link EBICS Direct Link Intersys only SIC Direct Exchange Direct Business GUI/DXI SWIFT FileAct

Flavors

Version

Direct Business no file download but status indication in the Direct Business GUI

pain.002 for all banks instead of different proprietary protocol formats Benefit

Timing same as the pain.001 or pain.008 triggering the pain.002

Caution

Channels

Best Practice

CS ISO offering



Benefit



Formats: Reporting

camt.053 Account Statement (End of Day)



camt.053.001.04 (for SIC) and camt.053.001.02 (for CGI)

camt.053 SIC without details is CS default


Some banks may use V2 (camt.053.001.02) for SIC until switching to V4 Oversteering of account default booking by using pain.001 tags

MT940

Name Market Scheme Report Types

SIC Switzerland 1.5.1 SIX* Account Statement CGI (CH) World 30.11.2009 Account Statement

Direct Link EBICS Direct Link Intersys Direct Exchange Direct Business GUI/DXI no details SWIFT FileAct

Best Practice

Caution


Alternative formats

Channels

Flavors

Version

End of day Periodicity

With details Without details

Details

MT940

camt.053 Tests

Timing

CS ISO offering





CS legacy offering

2017 2018 2019 2020 2021

Scheme 1.6 planned 4Q18 *


Formats: Reporting

camt.052 Account Report (Intraday)




camt.052 SIC Movement Report 2-hourly is CS default


Some financial institutes may use V2 (camt.052.001.02) for SIC

MT942

Name Market Scheme Report Types

SIC Switzerland 1.5.1 SIX* Account Statement CGI (CH) World 30.11.2009 Account Statement

Direct Link EBICS Direct Link Intersys Direct Exchange Direct Business GUI/DXI SWIFT FileAct

Best Practice

Caution


Alternative formats

Channels

Flavors

Version

Intraday fixed, hourly or 2-hourly, from 7 a.m. to 6 p.m. End of day (Balance Report)

Periodicity

Account Report – Balance Report Balances Account Report – Movement Report Balances + Movements Batch booking no details, single booking with details

Details

MT942

camt.052 Tests

Timing

Periodicity

CS ISO offering





CS legacy offering

2017 2018 2019 2020 2021



Formats: Reporting

camt.054 Debit/Credit Notification




Select the report types and details you need for your desired notification/matching functionality.

camt.054 SIC Debit/Credit Notification event-based & camt.054 SIC ISR/LSV are CS default.

camt.054 QR planned for QR-bill based on camt.054 ISR Credit Notification camt.054 Debit Notification is controlled by pain.001 tags, see page 20-22 for details; not supported by all Swiss banks PostFinance uses additional and different report types

E-Documents/MT900 Confirmation of Debit and MT910 Confirmation of Credit in SWIFT

Name Market Scheme

SIC Switzerland 1.5.1 SIX* CGI (CH) World 30.11.2009

Direct Link EBICS Direct Link Intersys Direct Exchange Direct Business GUI/DXI only ISR/LSV SWIFT FileAct

Best Practice

Caution

Alternative formats

Channels

Flavors

Version

Intraday fixed, hourly or 2-hourly, from 7 a.m. to 6 p.m. Intraday event-based, if booking took place, from 7 a.m. to 6 p.m. End of day (ISR/LSV)

Periodicity

According to account default Oversteer account default with pain.001 tags

Details

Report Types (also see next page)

Debit/Credit Notification

ISR/LSV Credit Notification

External Collective Booking Notification (for camt.053)

ZED V11 ISR/LSV

camt.054 Tests

Timing

CS ISO offering





CS legacy offering

2017 2018 2019 2020 2021



Formats: Reporting

camt.05x Subscriptions Related to Bookings



Date Bookings

July 14

Incoming Payment Single Booking CHF 20

July 15

camt.054

Credit/Debit

camt.052

e.g. every 2 hrs camt.053

20

Outgoing Payment Single Booking CHF 10

Incoming ISR Payments Collective Booking* CHF 60

camt.054

ISR/LSV

* One booking per subscriber number and product (ISR/LSV)

July 16

Outgoing Payments Collective Booking CHF 50

10

60

50

140

With Details. Example page 76: CAMT054-08.

With details Example page 76: CAMT054-07.

With details. Example page 76: CAMT054-05.

Details according to pain.001 advice steering. Example page 76: CAMT054-06.

30

2 hours

2 hours

2 hours

With amounts. Examples page 73.

0 With amounts. Examples page 73.

50 With amounts. Examples page 73.

camt.054

for camt.053

Details according to account default and pain.001 advice steering. Examples pages 74/75.

50 With Details**

AcctSvcrRef (camt.053) Ntfctn Id (camt.054) see page 55 MsgId (camt.053 C-Level)

MsgId (camt.054 A-Level) see page 49

AcctSvcrRef (camt.053) Ntfctn Id (camt.054)

** Also issued when camt.053 entry includes details (pain.001 advice steering CWD or empty)

18:00

One camt.054 per booking except for collective credits

One camt.054 per collective ISR or LSV credit

One camt.054 per collective debit (in combination with camt.053)


Formats: Reporting

camt.054 Manual Upload of ZIPped ISR Files

Direct Business

Direct Business

camt.054 ISR

Oct 15, 201x Download 1 file

CS client

= user

Import 1 file

Payment

Software

Situation 1: One camt.054 ISR ready for download

Situation 2: Several camt.054 ISR ready for download in a ZIP file

Problem: if the CS client unzips the file and uploads the camts manually, he might miss a file or upload a file twice.

Therefore please make sure to support at least one of the following options:

Payment

Software

Payment

Software

Import Oct 19, 201x

… then the user imports 1 ZIP file

Oct 16, 201x Oct 16, 201x

Download 1 ZIP file…

Oct 19, 201x

Option 1

Option 2

… then the user unzips… … and can mark all

files for import

Option 3

… and has to upload

one file after another…

… but then

the software needs

a duplicate and maybe

missing file check!



… then the user unzips…

camt.054 ISR

Oct 16, 201x

camt.054 ISR

Oct 17, 201x

camt.054 ISR

Oct 18, 201x

ZIP File



Payment

Software

Analogously for camt.053


Formats: Reporting

Advice Steering1 with pain.001 Tags: All Cases



Payment Information +Debtor Account ++Type +++Proprietary

Payment Information +Batch Booking

False True/Empty

NOA Single booking

camt.053 with details

No camt.054

Batch booking

camt.053 no details

No camt.054

SIA Single booking



Batch booking camt.053 details as account default camt.054 with details (CWD)

CND Single booking camt.053 with details

camt.054 with details (SIA)

Batch booking

camt.053 no details

camt.054 no details

CWD Single booking camt.053 with details

camt.054 with details (SIA)

Batch booking



Empty Single booking camt.053 with details camt.054 with details

Batch booking camt.053 details as account default camt.054 with details

Bold: Recommended settings Out of 15 debit advice combinations, only 5 are recommended Your software should be able to control these, e.g. by one dropdown menu Red: Recommended settings for salary payments to allow confidentiality Salary payments should only allow these settings, e.g. by ticking a checkbox Grey: Not recommended (may be rejected by other banks)

Credit Suisse

Account Defaults

camt in General

In order to receive camt.053/ 052/054, Credit Suisse clients have to subscribe to them for each of their accounts. It is not possible to order non-subscribed camts via pain.001.

camt.053

Default booking type is always batch booking, and for the subscription, the clients have to choose between with details or no details. Both can be over-ridden with pain.001 tags for particular instructions.

camt.052 Details are the same as for camt.053, unless camt.053 follows account default, then camt.052 is with details.

camt.054

Default is always with details! This can be overridden with CND or NOA.

1 No ordering of non-subscribed camt.052, camt.053 and camt.054 via pain.001 tags.


B-Level CHF 50

C-Level CHF 20

C-Level CHF 30

FALSE SIA

Formats: Reporting

Advice Steering1 with pain.001 Tags: Useful Cases

B-Level CHF 50

C-Level CHF 20

C-Level CHF 30

Document pain.001

FALSE NOA

B-Level

C-Level CHF 20

Document camt.053

C-Level CHF 30

B-Level CHF 50

C-Level CHF 20

C-Level CHF 30

TRUE NOA

Document pain.001

B-Level

Document camt.053

C-Level CHF 50

D-Level

Document pain.001

B-Level

C-Level CHF 20

Document camt.053

D-Level Trx Details

C-Level CHF 30

D-Level Trx Details

B-Level CHF 50

C-Level CHF 20

C-Level CHF 30

Document pain.001

TRUE CND

B-Level

C-Level CHF 50

Document camt.053

D-Level

B-Level CHF 50

C-Level CHF 20

C-Level CHF 30

Document pain.001

TRUE CWD

B-Level

C-Level CHF 50

Document camt.053

D-Level Trx Details CHF 20


B-Level

C-Level CHF 50

D-Level

Document camt.054

B-Level

C-Level CHF 20

D-Level Trx Details

Document camt.054

B-Level

Document camt.054

C-Level CHF 30

D-Level Trx Details



1 No ordering of non-subscribed camt.053 and camt.054 via pain.001 tags.

B-Level

Document camt.054

C-Level CHF 50



D-Level Trx Details

D-Level Trx Details


Formats: Reporting

All Formats

Output

Input

False

True

or

Empty

camt.053

Account Statement

camt.054

Debit Advice

Paper /E-Document

Account Statement

Direct Business GUI

Page «Bookings»

MT940

Account Statement

SIA

CWD

CND

NOA

NOA

Amounts + Details in 1 camt.053

Sum

Sum



No advice

Sum


No advice

Sum

Amounts + Details in 1 document



Paper/E-Document

Debit Advice

No advice

Sum

Amounts + Details in 4 documents

No advice


Web-based Files Paper/E-Documents (PDF)

Account Default

Account Default

Empty Amounts + Details in 4 camt.054


Amounts, Details as AD* in 1 camt.053

Amounts, Details as AD* in 4 documents

Empty As AD*: Sum or A+D** in 1 camt.053

Account Default

Account Default


B-Level: Sum

Batch Booking

Proprietary

C-Level: Amount

C-Level: Amount

C-Level: Amount

C-Level: Amount

pain.001

B-Level: Sum

Batch Booking

Proprietary

C-Level: Amount

C-Level: Amount

C-Level: Amount

C-Level: Amount

pain.001

B-Level: Sum

Batch Booking

Proprietary

C-Level: Amount

C-Level: Amount

C-Level: Amount

C-Level: Amount

pain.001

Sum

Amounts + Details

Sum

Amounts + Details in 1 MT940

B-Level: Sum

Batch Booking

Proprietary

C-Level: Amount

C-Level: Amount

C-Level: Amount

C-Level: Amount

pain.001

B-Level: Sum

Batch Booking

Proprietary

C-Level: Amount

C-Level: Amount

C-Level: Amount

C-Level: Amount

pain.001

B-Level: Sum

Batch Booking

Proprietary

C-Level: Amount

C-Level: Amount

C-Level: Amount

C-Level: Amount

pain.001

* Account Default ** Amounts + Details




Agenda

Framework

Formats

Use Cases

Test Procedure

Page 5

Page 11

Page 58


PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW1 (14)

Salary (20)

Domestic (12)

ACCP (35)

Type 1

Chapter 2.2

ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)

Internal (64) External (65)

Type 1 Chapter 2.2

DD Core (44) DD B2B (45) SDD Core (42) SDD B2B (43)

Payment slips and their replacement pain.001

Bank payments pain.001

Special payments pain.001

Status reports pain.002

Advices camt.054

Statements camt.053/052

Direct debit pain.008

Use Cases

Remarks

Payment Type

Swiss Usage Guide

camt.053/MT940 descriptions always include camt.052/MT942

Only bank formats are depicted, not PostFinance formats

ISR (40/41)

1 “Rest of the World”.


Use Cases: Credit Transfer

All Format Changes for Credit Transfer PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


DTA

Pro

toco

l

V1

1

MT9

40

A10

Orange/Red Payment Slip

MT9

40

A11

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

New Payment Slip

cam

t.05

4

cam

t.05

3

pacs.008

or Invoice or Invoice

Old formats and lasting formats New formats

Debtor Creditor

Debtor Bank Clearing Creditor Bank

ISR (40/41)


Layout example

Create pain.001

Use Cases 10/11/15: Inpayment Slips PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented

Payment Slip Variants

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

Payment Slip / QR-Bill

cam

t.05

4

cam

t.05

3

Create pain.001 from Payment Slip

pacs.008

ISR (German ESR, French BVR, Italian PVR). Orange inpayment slip with reference number. Currently in use, see page 27 for details.

IS (German ES, French BV, Italian PV). Red inpayment slip. Currently in use, see page 28 for details.

QR-bill Will replace ISR and IS, see page 29 for details.

ISR (40/41)

or QR-Bill


Create pain.001

Use Case 10: Orange Inpayment Slip PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 1 Chapter 3.1


1

2

4

3

1

2

3

4

4 3 2

CHF or EUR

ISR participant number

ISR reference

CH01 (= Type 1)

TRF or TRA

See Impl. Guidelines for alternatives

Notes:

Only one currency per B-Level

For Instruction Priority HIGH and/or

Category Purpose SALA,

CH01 has to be in B-Level

ISR participant number must have 9

characters, e.g. 01-2654-0 or

010026540, but not 0126540 (missing

dashes) or 000126540 (additional

zeros in front of first number block

instead of in front of the second one)

ISR (40/41)

Real name, no code

Mandatory

Recommended

Optional

Dependent

Source: Swiss Usage Guide for ISO 20022 Messages, Version 1.2 by SIX Interbank Clearing Ltd

Please for all pain.001:

Also use +Initiating Party

++Name

+++Contact Details


Create pain.001

Use Case 11: Red Inpayment Slip Manual PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 2.2 Chapter 3.3


CHBCC

IID

1

8

4

2

5

6

3

7

6

1

TRA or TRF

Manual entry into

your software by

using these fields

ISR (40/41)

3

3

3

3

2

5

6

CHF or EUR

Bank’s Postal Account Number

CH02 (=Type 2.1) or CH03 (=Type 2.2)

3

4

7

See Impl. Guidelines for alternatives


Mandatory

Recommended

Optional

Dependent

Notes:


For Instruction Priority HIGH and/or

Category Purpose SALA,

CH03 has to be in B-Level

CH03 requires Creditor Agent


ISR (40/41)

Create pain.001

Use Case 15: QR-Bill PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter


Source: Swiss Implementation Guidelines, Version 1.7.2 / 1.8

by SIX Interbank Clearing Ltd

CHF or EUR

Mandatory

Recommended

Optional

Dependent

Notes:

Very new spec, subject to change!


QR Elements Ustrd without Ref:

pain.001 tag RmtInf > Ustrd

QR-IBAN

QR Reference

IBAN

Name

StrtNm

BldgNb

QR Elements

PstCd

TwnNm

Ctry

Name

Amt Ccy

Name

StrtNm

BldgNb

PstCd

TwnNm Ref

Ustrd

Tp

C +Remittance Information ++Structured +++Creditor Reference Information ++++Type +++++Code Or Proprietary ++++++Proprietary

QRR

C +Remittance Information ++Structured +++Creditor Reference Information ++++Reference

C +Remittance Information ++Structured +++Additional Remittance Information

Additional information for reconciliation. Recommendation: Use Syntax Definition by SWICO.



++Name

+++Contact Details

Use once

QR Elements

http://www.swico.ch/de/dienstleistungen/qr-rechnungen





ISR (40/41)

Create pain.001

Use Case 15: QR-Bill vs. ISR PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter


Caution 2: Changes for Debtor Grouping

To date, V11 files have been created for each internal ISR subscriber number at Credit Suisse. Multiple subscriber numbers could relate to one bank account. In the future, the camt.054 for the QR-bill will be created for each QR-IBAN. Since each bank account can have only one QR-IBAN, it is not possible to continue the previous setup involving bank accounts with multiple subscriber numbers.

Clients who still wish to group their accounts receivable when payment is received must do this with multiple QR-IBANs, and therefore with multiple bank accounts.

Alternatively, the accounts receivable software can choose to distinguish between accounts receivable groups using the reference numbers and can map these groups accordingly. For the latter, as was already the case at PostFinance, the first six positions are now at your disposal, thereby making a total of 26 positions in the 27-digit reference number; old subscriber numbers can therefore continue to be used.

Caution 1: Creditor Data Must Match the Bank’s Master Data

The procedure for the QR-bill is the first to have been aligned with current Swiss money laundering provisions from the outset. As a result, financial institutions will increasingly check whether the names and addresses of the accounts payable that appear on the QR-bill match the corresponding bank master data.

For payees, this is easy to see when creating a QR-bill.

However, for payers, this process becomes problematic if an accounts payable module does not draw on the information given on the bill but rather on out-of-date master data when the payer comes to settle the QR-bill. For payments via ISR, this issue has so far been of no significance due to this data not being transmitted.


Create pain.001

Use Cases 12/13/14: Bank Payments PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3/4/5/6 Chapter


To be considered New file format pain.001 instead of DTA Booking control needs to be implemented Notification control needs to be implemented

Common Mistake: CH03 Is Not Payment Type 3

Please note that Payment Type 3 transactions must not contain a Local Instrument. Local Instrument CH03 is not Payment Type 3 (domestic credit transfer in CHF or EUR) but Payment Type 2.2 (IS, red two-stage inpayment slip in CHF or EUR):

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

Invoice or

cam

t.05

4

cam

t.05

3

Create pain.001 from invoice

or accounting voucher

pacs.008

accounting voucher

ISR (40/41)

Source: Swiss Implementation Guidelines, Version 1.7.2 / 1.8 by SIX Interbank Clearing Ltd


Create pain.001

Use Case 12: Domestic Bank Payment PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3/4 Chapter 3.4


ISR (40/41)

Type 3: CHF or EUR

Type 4: not CHF or EUR


Mandatory

Recommended

Optional

Dependent

Notes:




++Name

+++Contact Details


Create pain.001

Use Case 13: SEPA X-Border Payment PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 5 Chapter 3.6


TRA or TRF

SEPA

ISR (40/41)

EUR

Swiss Implemen-

tation Guidelines

recommend

<AdrLine> and

<Ctry>. CS strongly

encourages to

include Postal

Address, if possible

in the structured

way as some SEPA

countries seem

to consider it

mandatory.

Mandatory

Recommended

Optional

Dependent


Notes:


For Category Purpose SALA,

SEPA has to be in B-Level



++Name

+++Contact Details


Create pain.001

Use Case 14: Other X-Border Payment PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 6 Chapter


TRA or TRF

ISR (40/41)

Bahnhofplatz

1

98765

Neustadt

DE

Mandatory

Recommended

Optional

Dependent


Notes:




++Name

+++Contact Details

SELDDENN001 See Impl. Guidelines

for alternatives

Swiss Implemen-

tation Guidelines

recommend

<AdrLine> and

<Ctry>. CS strongly

encourages to

include Postal

Address, if possible

in the structured

way as some SEPA

countries seem

to consider it

mandatory.


Create pain.001

Use Case 20: Salary Payment PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter 3.5


To be considered New file format pain.001 instead of DTA Booking steering needs to be implemented Advice steering needs to be implemented

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3

Create pain.001 for salary payment

pacs.008

ISR (40/41)

Caution: SALA flag has no effect on booking and advices in Swiss pain.001 Salary payments must have: Batch Booking TRUE or empty and Debtor Account >Type>Proprietary CND or NOA

What happens without TRUE or CND/NOA? camt.053 default account setting is always batch booking, so the client will receive batch booking (unless the pain.001 is set to batch booking FALSE) camt.054 default account setting is always with details, so for salary payments details have to be stopped with CND or NOA!


Create pain.001

Use Case 20: Salary Payment PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter 3.5


Batch Booking has to be TRUE or empty

SALA has no impact on the salary payment processing

Advice control has to be CND or NOA

ISR (40/41)

Mandatory

Recommended

Optional

Dependent


Notes:




++Name

+++Contact Details


pain.001 in General

Payment Type Information PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter 3.5


ISR (40/41)

Local Instrument

Instruction Priority

Service Level

Category Purpose

HIGH (Express payment between noon and cut-off time)

SEPA (Payment Type PT 5)

SEPA (Payment Type 5)

CH01 (PT 1), CH02 (PT 2.1),

CH03 (PT 2.2)

CH01 (PT 1), CH02 (PT 2.1),

CH03 (PT 2.2)

SALA (Salary payment, has no effect on

advice steering)

Combinations should be on B-Level.

If on both Levels, B-Level is rejected.

SALA ()

SALA + CH01 currently

rejected, being fixed.

Payment Type Information B-Level C-Level

Payment Type Information on B-Level and

Purpose SALA on C-Level is possible.


pain.001 in General

Important Issues to Consider PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter 3.5



pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3

pacs.008

ISR (40/41)

Structured Master Data and Addresses

Master data as source for all pain.001 payment instructions have to be very structured to avoid rejected files (pain.002 status RJCT). Credit Suisse encourages to use structured pain.001 tags instead of unstructured ones whenever possible, also for addresses. For foreign payments, the Swiss Implementation Guidelines recommend the use of unstructured address information, but particularly for payment type 5, recommendation of structured address information is under investigation. Structuring the customer’s data before the customer creates pain.001 files is crucial. Therefore Credit Suisse suggests offering your clients data cleansing before they go live with pain.001. This should include consistent use of the IBAN.

Do Not Allow Multiple Currencies in One B-Level

Index 4.3.1 of the Swiss Business Rules include an Additional Optional Service (AOS) to create more than one B-Level for each currency. Credit Suisse and other banks do not include this AOS, i.e. one B-Level for each currency will be mandatory for collective booking

to avoid reconciliation problems caused by making the same reference appear several times in the resulting camt.05x. Credit Suisse also states that one B-Level per currency is recommended for single booking to avoid cutoff time problems. Structuring data is one major principle of ISO 20022, therefore this should not be compromised by mixing instructions which have to be processed differently in the financial markets.


pain.001 in General

Other Issues to Consider PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type 3 Chapter 3.5



pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3

pacs.008

ISR (40/41)

Recommendations Recommendations are not mandatory, but there is always a reason why they are not only classified as optional Therefore Credit Suisse strongly encourages to implement not only mandatory elements, but also recommended ones

Unique IDs

Create unique IDs like MsgId, PmtInfId and InstrId to facilitate file processing and support InstrId is only recommended, but as mentioned above strongly encouraged by Credit Suisse IDs are used in telephone support, so please avoid complicated and long combinations of upper and lower case IDs

Initiating Party Name The Name of the Initiating Party should be the actual name of the party sending the payment order to the bank, not a code Contact Details Please use the Initiating Party Contact Detail tags Name and Other to list the name and the version of your software, this will help to support our mutual customers considerably


Match pain.002 with pain.001

Use Cases 35–39: Status Report PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter 3.5


To be considered New file format pain.002 instead of bank-proprietary transaction protocol pain.002 only negative details No execution information Status should be indicated in your software (with Direct Link, Direct Exchange, or SWIFT connectivity only)

Available Status Categories

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3


pacs.008

Accepted (Use Case 35) Syntax/semantics ok across all levels

ACCP

PART

RJCT

ACWC

C

Accepted with Change (Use Case 37) Not used at Credit Suisse ACCP with status code used instead

Partially Accepted (Use Case 38) At least 1 B-level was incorrect (at least 1 correct) or at least 1 C-level in 1 B-level was incorrect (at least 1 correct)

Rejected (Use Case 39) Group Status: whole message rejected. A-level not correct or all B- or C-levels are incorrect. PmtInf: all transactions in the corresponding B-level rejected

ISR (40/41)



Use Case 35: Status Report ACCP PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter 3.1.3


ISR (40/41)




Use Case 37: Status Report ACWC PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Appendix B2


Practice Not used at Credit Suisse, ACCP is used instead Execution date modification by the bank is indicated by Status Reason Code DT06 As a difference to the production system, ACWC is used in the ISO 20022 Test Platform

ISR (40/41)




Use Case 38: Status Report PART PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Appendix


ISR (40/41)

Examples The Credit Suisse ISO 20022 Test Platform features several PART examples Please find an overview of the best practice examples in this guide from page 63 The ISO 20022 Test Platform can be accessed via credit-suisse.com/iso20022test

https://iso20022test.credit-suisse.com/?locale=en





Use Case 39: Status Report RJCT PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Appendix B3


Example: Error at A-Level

Message submitted twice by the debtor Example: Error at B-Level

Debtor’s account is blocked Example: Error at C-Level

ISR reference number check digit incorrect

ISR (40/41)



Matching in General

Debtor Side and Creditor Side PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

Paym

ent O

rde

r

P2

P: M

sgId

/Pm

tInfId

/InstrId

E

2E

: EndToE

ndId

/Rm

tInf

Point-to-Point and End-to-End References

Point-to-point references are transmitted between the sender and receiver of a payment phase (bank to client, bank to bank, or bank to client).

End-to-end-references are transmitted between the debtor and the creditor, e.g. the ISR reference.

However, the following issues have to be considered: Sta

tem

en

t/A

dvic

e

E2

E: E

ndToE

ndId

/Rm

tInf

Sta

tem

en

t/A

dvic

e

P2

P: M

sgId

/Pm

tInfId

/InstrId

E

2E

: EndToE

ndId

/Rm

tInf

pacs.008

EndToEndId/RmtInf

Invoice

RmtInf (EndToEndId)

Creditor Reconciliation

The EndtoEndId is often unknown to the creditor, so the RmtInf is important for his reconciliation.

Debtor Reconciliation (also see pages 50-51)

The EndtoEndId is compulsory and is defined as major reconciliation ID for the debtor side. But there are at least three exceptions:

When your software allows to enter an EndToEndId created by the creditor, this ID might not be unique, so you might also use the InstrId for the reconciliation on the debtor side

The EndtoEndId is not included in the camt.05x for collective booking without details, so for collective bookings the PmtInfId should be used by the debtor as it is also transmitted in the case of CND or NOA.

For individual booking and NOA, all references are missing in the camt.05x, so use name/amounts/etc. for reconciliation

Debtor Side CreditorSide


Match camt.054 with pain.001

Use Cases 46–49 PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter 3.5


To be considered New file format camt.054.001.04.ch Preparsing to reveal message type: debit/credit notification, ISR credit notification, LSV credit notification, external batch booking notification Could be end of day, depending on the report type (e.g. ISR end of day) Could be intraday, depending on the report type (e.g. ISR every 2 hours)

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3


pacs.008

Available Booking and Advice Categories in pain.001

TRUE/FALSE/ empty

No Advice

(Use Case 46)


NOA

FALSE Individual Advice

(Use Case 47) SIA

TRUE/empty Collective Advice

without Details

(Use Case 48)

CND

TRUE/empty Individual Advice

(Use Case 49) CWD

ISR (40/41)


Debtor Side Creditor Side



Use Cases 48 for Salary Payments PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter 3.5


To be considered SALA flag has no effect on booking and advices in Swiss pain.001 Salary payments must have Batch Booking TRUE (or empty) and Debtor Account > Type > Proprietary CND

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3


pacs.008

ISR (40/41)

Available Booking and Statement Categories in pain.001

TRUE/FALSE/ empty

No Advice

(Use Case 46)


NOA


FALSE Individual Advice

(Use Case 47) SIA

TRUE/empty Collective Advice

without Details

(Use Case 48)

CND

TRUE/empty Individual Advice

(Use Case 49) CWD




Use Case 64: Internal Batch Booking

PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter 3.5


To be considered New file format camt.053.001.04 instead of MT940

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3

Match camt.053 (with details)

with pain.001

pacs.008

ISR (40/41)

FALSE NOA

FALSE SIA

TRUE/empty NOA OR CND

TRUE/empty CWD

Single Booking

without Details

Single Booking

with Details

Batch Booking

without Details

Batch Booking

with Details

Available Booking and Statement Categories in pain.001






Use Case 65: External Batch Booking

PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter 3.5


ISR (40/41)

To be considered New file format camt.053.001.04 instead of MT940 Details can be “outsourced” to camt.054.001.04

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

cam

t.05

4

cam

t.05

3

Match camt.053 with reference

to camt.054 with pain.001

pacs.008

camt.053

One reference per <Ntry> to one camt.054 in <AddtInfInd><MsgId>

camt.054

One reference per file to one camt.053 in <GrpHdr><MsgId>

…

…

Source: Credit Suisse ISO 20022 Test Platform



Matching References

camt.05x PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

Batch

booking

= true

Batch

booking

= false

CND/

NOA

pain.001 camt.052/camt.053/camt.054

CWD

MsgId PmtInfId

MsgId PmtInfId InstrId EndToEndId

NOA

SIA MsgId PmtInfId InstrId

(optional)

EndToEndId (mandatory)

Point to point IDs End to end ID

Amount, name…

Identify the pain.001’s A-Level

Identify the pain.001’s B-Level

Identify the pain.001’s C-Level

Recommended for reconciliation

Recommended for reconciliation if used

Also included in camt.053

1 2

3

3

4



Matching References

X-Format PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

What Relationship Do References from Different Formats Have to Each Other?

During a transitional period, companies will use both ISO 20022 and old formats. The assignment of references between the formats takes place as follows:

Remarks about MT101

:20: Sender Reference :21R: Customer Specified Reference :21: Transaction Reference :70: Remittance Information

* If ≤ 16 characters, then Subtag 7, otherwise Subtag 9 ** If no InstrId available in payment order, then also in field :61: Subtag 7 or 9

Type of

Reference

For (Level) Payment Order Statement/Advice

pain.001 MT101 DTA camt.05x MT940 Paper/PDF

Point-to-Point

(P2P)

File (A) MsgId :20: File name MsgId - -

Instruction (B) PmtInfId :21R: - PmtInfId :61: subtag 7 or 9* :86: trigger tag ?21

-

Transaction (C) InstrId - Output sequence # InstrId -

End-to-End

(E2E)

End-to-End-Info EndToEndId :21: - EndToEndId :86: trigger tag ?22** EndToEndId

Remittance-Info RmtInf :70: 70: RmtInf :86: trigger tag ?60 RmtInf

Remarks about Paper/PDF

RmtInf/EndToEndId with single booking. Remarks about MT940

:61: Details of the Transaction :86: Info to Account Holder ?21 Your Reference ?22 Client Reference ?60 Reason for payment PmtInfId with batch booking InstrId/EndToEndId/RmtInf with single booking



Match camt.054 with ISR/QR-bill

Use Cases 40/41 PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

To be considered Solution for collective booking of ISR credits (standard case, recommended) New file format camt.054 instead of V11 Recommendation: switch from V11 to camt.054 when changing to QR-bill

Reconciliation Data

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

Payments Slip or QR-bill

cam

t.05

4

cam

t.05

3

Match camt.054 ISR/QR

with Payment Slip / QR-bill

pacs.008

ISR

IS

QR-bill

<CrdtRefInf><Ref>

12345

</Ref></CrdtRefInf>

12345

Amount, address data etc.

Layout example

<CrdtRefInf><Ref>

12345

</Ref></CrdtRefInf>

Creditor Side Debtor Side


Match camt.053 with ISR/QR-bill

Use Cases 40/41 PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

To be considered Solution for single booking of ISR/QR-bill credits

Reconciliation Data

pain

.00

1

pain

.00

2

cam

t.05

4

cam

t.05

3

pacs.008

Payments Slip or QR-bill

cam

t.05

4

cam

t.05

3

Match camt.053

with Payment Slip / QR-bill

pacs.008

ISR

IS

QR-bill

<CrdtRefInf><Ref>

12345

</Ref></CrdtRefInf>

12345

Amount, address data etc.

Layout example

<CrdtRefInf><Ref>

12345

</Ref></CrdtRefInf>



Match Reporting with ISR

ISR Reference Availability PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

Collective booking (standard) camt.053 no details (standard) No (Referencing see next page)

Yes

(Referencing see next page) camt.053 with details

Single booking camt.053 no details (standard) Yes No


To be considered ISR collective booking is part of Credit Suisse’s ISR standard offering. Details (ISR references) will be provided in a V11 file or camt.054 ISR. Like this, the V11 or camt.054 ISR can be used by the debtor accounting software, the camt.053 by the financial accounting software. ISR single booking will result in details (ISR references) in the MT940 or camt.053 file. Booking takes place immediately. This should only be used when explicitly required by the software as many ISR credits will blow up the camt.053 file. Both ISR collective and single booking will oversteer the camt.053 detail subscription for ISR credits. For ISR collective and single booking examples, please see chapter Test Procedures.

Subscription ISR details (ISR reference)

ISR camt.053 Included in Account Statement

MT940 or camt.053

ISR Credit Advice available as V11 or camt.054 ISR



Match Collective Booking with Details

ISR Referencing in Detail

PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


ISR (40/41)

MT940 V11 :61:1801301801C98763,45 :86:1024

00201009521796037499000000000600001341100000475000000000000180130180130180130 999010095217999999999999999999999999999000009876345000000000002170621000000000000000000

camt.054 ISR :86:1024?051234567890ABCDEFG

<Ntfctn> <Id>1234567890ABCDEFG</Id> </Ntfctn>

camt.053 V11 <Amt Ccy=«CHF»>98763.45</Amt> <BookgDt> <Dt>2018-01-30</Dt> </BookgDt> <ValDt> <Dt>2018-01-30</Dt> </ValDt>

00201009521796037499000000000600001341100000475000000000000180130180130180130 999010095217999999999999999999999999999000009876345000000000002170621000000000000000000

camt.054 ISR <AcctSvcrRef> 1234567890ABCDEFG </AcctSvcrRef>

<Ntfctn> <Id>1234567890ABCDEFG</Id> </Ntfctn>

Reporting Message Type Combination Reporting Message Referencing (Value Date + Amount or Order Reference)

Account Statement ISR Credit Advice Account Statement ISR Credit Advice

Remarks The reference between the daily account statement collective booking ISR credit and the ISR credit advice is ensured by a 17-digit order reference MT940 EPC (Extended Product Code) for ISR collective credits is 1024, camt.053 Bank Transaction Code (BTC, BkTxCd) is PMNT RCDT VCOM



Use Cases: Direct Debit

All Format Changes for Direct Debit PART (38)

IS (11) ISR (10) QR (15)

SEPA (13) ROW (14)

Salary (20)

Domestic (12)

ACCP (35) ACWC (37)

NOA (46) SIA (47) CND (48)

RJCT (39)

CWD (49)


Type Chapter


V

11

MT9

40

A10

MT9

40

A11

pacs.008

cam

t.05

4

cam

t.05

3

pacs.008

Invoice

pacs.003 pacs.003

Invoice

Old formats and lasting formats New formats

Debtor Creditor

Debtor Bank Clearing Creditor Bank

ISR (40/41)

A10 A11

LS

V

Pro

toco

l

cam

t.054

cam

t.05

3

pain

.008

pain

.002

Cases will be published by the time the pain.008 LS specifications are published.


Bank Transaction Code

Most Common BTCs for Payments Used by Credit Suisse

Domain Family Sub Family D/C Booking Transaction Type (SPS** pain.001 Payment Type)

PMNT ICDT AUTT Automatic transfer Debit Collective Any*

BOOK Internal book transfer Single Bank-internal account transfer

DMCT Domestic credit transfer Domestic IS (2) or credit transfer in CHF/EUR (3)

VCOM CT with agreed commercial info Domestic ISR (1)

ESCT European SEPA credit transfer Crossborder SEPA (5)

XBCT Crossborder credit transfer Crossborder non SEPA (6) or domestic non CHF/EUR (4)

RRTN Reversal due to payment return Return or reject

IDDT PMDD Payment direct debit Domestic direct debit LSV

RCDT BOOK Internal book transfer Credit Single Bank-internal account transfer

DMCT Domestic credit transfer Single Domestic IS or credit transfer in CHF/EUR

VCOM CT with agreed commercial info Single or collective Domestic ISR

ESCT European SEPA credit transfer Single Crossborder SEPA

XBCT Crossborder credit transfer Single Crossborder non SEPA or domestic non CHF/EUR

RRTN Reversal due to payment return Single Return or reject

RDDT PMDD Payment direct debit Collective Domestic direct debit LSV

Without SEPA Direct Debit Without checks

* Current code is PMNT ICDT OTHR ** Swiss Payment Standards by Six Interbank Clearing SIC


Agenda

Framework

Formats

Use Cases

Test Procedure

Page 5

Page 11

Page 23


Agenda

Test Procedure

Test Cases: Files as Best Practice Examples

Payment Type 1

Payment Type 2

Payment Type 4

Payment Type 5

Payment Type 6

SEPA-DD

Payment Type 3

Payment Type 8

camt.052

camt.053

camt.054

List of Compatible Software

Example Page

Conditions to Join the List

Introduction

Testing Principles


Test Cases

Testing Principles

The primary tool for ISO 20022 testing with Credit Suisse is the ISO 20022 Test Platform. It targets software manufacturers and Credit Suisse clients. The ISO 20022 Test Platform can be accessed at credit-suisse.com/iso20022test The fact sheet can be found at credit-suisse.com/softwarepartner We suggest testing in two general stages 1. Free testing:

Upload and download as many test files as possible with random creditors and debtors from your software.

2. Uploads for the Credit Suisse List of Compatible Software: Once all your tests have been successfully run, please make another test run for all the payment types for which you would like to declare compatibility with Credit Suisse in our List of Compatible Software. Report your uploads to [email protected].

https://credit-suisse.com/iso20022test



https://credit-suisse.com/softwarepartner








Example Page

General: Information provided by you

Channels: Implemented and tested with CS, contact [email protected] for details

pain.001 SIC normal:

Pass POS tests with payment types 1, 2.1, 2.2, 3, 4, 5 and/or 6

pain.001 SIC salary: Pass test with payment type 3 incl. batch booking true and CND/NOA pain.008 SIC/EPC:

Pass test

pain.002: Test at your own discretion camt.05x:

Test at your own discretion

Restrictions: Not provided payment types will be listed as footnote






Conditions to Join the List

Pu

blicatio

n

To get

an entry for…

General

Channels

Do the following steps…

pain.002

Include this information in your questionnaire to [email protected]

Contact [email protected] to report your intention to provide direct connectivity to Credit Suisse

Implement and test the new channel, when finished contact the Software Partner Team again

Import the files created by the ISO 20022 test platform (If your software does not create pain.001 files, you can import the camts created by uploading the best practice test cases)

After successful tests, include information about successful tests in your questionnaire to [email protected] camt.05x

pain.001 SIC

salary

pain.001 SIC

normal

pain.008 SIC/EPC

Create one file or several files with example payments for each payment type and upload it/them to the test platform.

Contact [email protected] to report the upload.

Create one file with a payment type 3 example including batch booking = true and CND/NOA. Upload it to the test platform.


Create one file as an example. Upload it to the test platform.





















Test Cases (1/14)

Best Practice Files

BP01-POS ISR payments with ISR number

A correct file is submitted with two B-Levels, each with five ISR payments. The first instruction (B-Level) contains payments in CHF and has a technically correct ISR subscriber number starting with 01. The second instruction contains payments in EUR and also has a technically correct ISR subscriber number, but this one starts with 03. The file should be processed without errors and warnings. A pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/VCOM is entered as BkTxCd in the transaction details.

pain.002 ACCP

BP01-NEG ISR reference number incorrect

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the ISR reference number in the fifth payment of the first B-Level is abc555555555555555555555559 and is thus incorrect. In the pain.002, the A-Level and the second B-Level are partially accepted with PART, and only the affected C-Level is rejected with RJCT. The rejection only contains error code CH16 and the underlying element as an XML structure under OrgnlTxRef. The 9 correct transactions are booked with details in camt.053.

pain.002 PART

In the ISO 20022 Test Platform, you will find best-practice files as an example for the files created by your software. Positive cases include the code POS, negative cases are marked with the code NEG. Adapt the following examples to the test files created by your software. The test should follow the general idea of an example,

e.g. BP01-POS shall have two or more B-Levels with several (e.g. 5 as in the example) payments in each B-Level.

Payment type 1: ISR payments in CHF and EUR (orange payment slip)

Test needed for

list of compatible

software “pain.001

SIC normal”


Test Cases (2/14)

Best Practice Files

BP90-A-NEG Execution date too far in the past

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the execution date for the second B-Level is 2014-08-01 and is thus too far in the past. In the pain.002, the A-Level is partially accepted with PART, and only the affected B-Level is rejected with RJCT. The rejection only contains error code DT01. The 5 transactions of the correct B-Level are booked with details in camt.053.

pain.002 PART

BP90-C-NEG Execution date on a Sunday

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the execution date for the second B-Level is 2016-09-18 and thus falls on a Sunday. In the pain.002, the A-Level and the relevant B-Level are marked with ACCP (not ACWC). Error code DT06 is also provided for the B-Level. 2 x camt.053 are created, each with five transactions. The execution date for the second B-Level falls on the next bank working day.

pain.002 ACCP

BP90-B-NEG Execution date too far in the future

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the execution date for the second B-Level is 2018-08-01 and is thus too far in the future. In the pain.002, the A-Level is partially accepted with PART, and only the affected B-Level is rejected with RJCT. The rejection only contains error code DT01. The 5 transactions of the correct B-Level are booked with details in camt.053.

pain.002 PART

BP90-D-NEG No execution date provided

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the execution date for the second B-Level is empty. Since there is a schematic violation, the entire file is rejected. In the pain.002, the entire A-Level is rejected with error code FF01.

pain.002 RJCT


BP93-NEG

pain.002 PART

Test Cases (3/14)

Best Practice Files

BP91-NEG Control sum error (A level)

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the control sum (CtrlSum) is 3,000 instead of 30,000 and is therefore incorrect. In the pain.002, the entire A-Level is rejected with RJCT. The rejection only contains error code AM10. No camt.053 is generated.

pain.002 PART

Amount error (C level)

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the amount of the fifth payment in the second B-Level is 0 and is thus not permitted. In the pain.002, the A-Level and the second B-Level are partially accepted with PART, and only the affected C-Level is rejected with RJCT. The rejection only contains error code AM01 and the underlying element as an XML structure under OrgnlTxRef. The 9 correct transactions are booked with details in camt.053.

BP92-NEG Account number error (B level)

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the account number (DbtrAcct) in the second B-Level is CH7304835833740031000, and thus has an incorrect check sum. In the pain.002, the A-Level is partially accepted with PART, and only the affected B-Level is rejected with RJCT. The rejection only contains error code AC01. The 5 transactions of the correct B-Level are booked with details in camt.053.

pain.002 PART

BP94-NEG B level ID not unique within the file

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the ID of the second B-Level (PmtInfId) is the same as the ID of the first B-Level. In the pain.002, the entire A-Level is rejected with RJCT. The rejection only contains error code DU02. No camt.053 is generated.

pain.002 RJCT

pain.002 RJCT


Test Cases (4/14)

Best Practice Files

BP95-NEG Exchange rate information provided

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but an exchange rate (XchgRateInf) is specified for the first payment in the first B-Level, which is not permitted. In the pain.002, the A-Level and the first B-Level are partially accepted with PART, and only the affected C-Level is rejected with RJCT. The rejection only contains error code CH17 as per SIX's Implementation Guide and the underlying element as an XML structure under OrgnlTxRef. The 9 correct transactions are booked with details in camt.053.

pain.002 PART

BP96-NEG No initiating party provided

A file is submitted with two B-Levels, each with five ISR payments. The file is almost identical to BP01-POS, but the initiating party (InitgPty) is missing. Since there is a schematic violation, the entire file is rejected. In the pain.002, the entire A-Level is rejected with error code FF01.

pain.002 RJCT

BP02-POS IS payments

A correct file is submitted with two B-Levels, each with five single-level IS payments. The first instruction (B-Level) contains payments in CHF to post office account 70-4152-8. The second instruction contains payments in EUR, also to post office account 70-4152-8.

The file should be processed without errors and warnings. A pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/DMCT is entered as BkTxCd in the transaction details.

Payment type 2: IS payments in CHF and EUR (red payment slip)

pain.002 ACCP

Test needed for

list of compatible


SIC normal”


Test Cases (5/14)

Best Practice Files

Payment type 3: payments in CHF and EUR in Switzerland

BP03-A-POS IBAN payments

A correct file is submitted with two B-Levels, each with five IBAN payments. The first instruction (B-Level) contains payments in CHF to CS sample account CH5604835012345678009. The second instruction contains payments in EUR to CS sample account CH7304835833740032001. The file should be processed without errors and warnings. A technical pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/DMCT is entered as BkTxCd in the transaction details.

pain.002 ACCP

Test needed for

list of compatible


SIC normal”

BP03-B-POS Salary payments

A correct file is submitted with two B-Levels, each with five IBAN payments. The file is very similar to BP03 A POS, but also contains additional markings that the payments are salary payments. Credit Suisse does not change any of the processing if SALA or PENS is used. As a result, the collective entry is also selected as TRUE and the collective approval with no details (CND) is selected as recommended. The first instruction (B-Level) contains payments in CHF to CS sample account CH5604835012345678009. The entire B-Level is marked as an instruction with salary payments by selecting Category Purpose Code SALA in the instruction. The second instruction also contains payments in CHF to CS sample account CH5604835012345678009. The entire B-Level is marked as an instruction with pension payments by selecting Category Purpose Code PENS in the instruction. The file should be processed without errors and warnings. A technical pain.002 is generated with ACCP. The 5 transactions per instruction are listed as a collective booking with no details in the camt.053.

pain.002 ACCP

Test needed for

list of compatible


SIC salary”


Test Cases (6/14)

Best Practice Files

Payment type 4: payments in foreign currency (excl. EUR) in Switzerland

Domestic payments in USD

A correct file is submitted with two B-Levels, each with five domestic payments. The first and second instructions (B-Level) each contain payments in USD to CS sample account CH5604835012345678009. The file should be processed without errors and warnings. A pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/DMCT is entered as BkTxCd in the transaction details. Since the account currency was selected as USD, no foreign currency translation may occur.

BP05-A-POS SEPA foreign payments

A correct file is submitted with two B-Levels, each with five SEPA payments. Both instructions (B-Level) contain payments in EUR to sample account DE12500105170648489890. The file should be processed without errors and warnings. A technical pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/ESCT is entered as BkTxCd in the transaction details.

pain.002 ACCP

Payment type 5: SEPA transfer abroad

Test needed for

list of compatible


SIC normal”

BP04-POS

pain.002 ACCP

Test needed for

list of compatible


SIC normal”


Test Cases (7/14)

Best Practice Files

BP05-B-POS SEPA IBAN only

A correct file is submitted with two B-Levels, each with five SEPA payments. The file is almost identical with BP05-A-POS, but the Creditor Agent is missing (IBAN only). The file should be processed without errors and warnings. A technical pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/ESCT is entered as BkTxCd in the transaction details. The camt.053 has to be equal to the one resulting from BP05-A-POS, with the exception that there is no Creditor Agent.

pain.002 ACCP

BP05-A-NEG Currency different than EUR

A file is submitted with two B-Levels, each with five SEPA payments. The file is almost identical to BP05-POS, but the currency of the third payment in the first B-Level is CHF and is thus not permitted. In the pain.002, the A-Level and the first B-Level are partially accepted with PART, and only the affected C-Level is rejected with RJCT. The rejection only contains error code AM03 and the underlying element as an XML structure under OrgnlTxRef. The 9 correct transactions are booked with details in camt.053.

pain.002 ACCP

BP05-B-NEG No IBAN provided

A file is submitted with two B-Levels, each with five SEPA payments. The file is almost identical to BP05-POS, but in the fifth payment of the first B-Level, the creditor's account (CdtrAcct) is missing. In the pain.002, the A-Level and the first B-Level are partially accepted with PART, and only the affected C-Level is rejected with RJCT. The rejection only contains error code CH21. The 9 correct transactions are booked with details in camt.053.

pain.002 ACCP

pain.002 PART

pain.002 PART


Test Cases (8/14)

Best Practice Files

Payment type 6: all currencies (SWIFT)

BP06-POS Foreign payments in USD

A correct file is submitted with two B-Levels, each with five international payments. Both instructions (B-Level) contain payments in USD to sample account GB32ESSE40486562136016. The file should be processed without errors and warnings. A technical pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICDT/XBCT is entered as BkTxCd in the transaction details.

Since the account currency is CHF, a foreign currency translation must occur.

pain.002 ACCP

Test needed for

list of compatible


SIC normal”


Test Cases (9/14)

Best Practice Files

BP07-NEG

pain.002 RJCT

SEPA-DD payments with incorrect local instrument

A file is submitted with two B-Levels, each with five SEPA direct debits. The file is almost identical to BP07-POS,

but the local instrument of the second B-Level is B2C and is thus not permitted. Since there is a schematic violation, the entire file is rejected. In the pain.002, the entire A-Level is rejected with error code FF01.

SEPA-DD

BP07-POS SEPA-DD payments

A correct file is submitted with two B-Levels, each with five SEPA core direct debits (CORE). Both instructions (B-Level) contain direct debits in EUR that are drawn from sample account CH5604835012345678009. The file should be processed without errors and warnings. A technical pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/RDDT/ESDD is entered as BkTxCd in the transaction details.

Since the account currency was selected as EUR, no foreign currency translation may occur.

pain.002 ACCP

Test needed for

list of compatible


SIC/EPC”

SEPA-DD payments

SEPA-DD payments with incorrect local instrument


Test Cases (10/14)

Best Practice Files

A correct file is submitted with two B-Levels, each with five cheque payments. The first instruction (B-Level) contains domestic payments in CHF, the second instruction contains cross border payments in USD. A technical pain.002 is generated with ACCP as well as a camt.053, in which all 10 transactions are booked with details. PMNT/ICHQ/BCHQ is entered as BkTxCd in the transaction details.

BP08-POS Bank cheques in CHF and USD

BP08-NEG

pain.002 ACCP

pain.002 PART

Creditor Agent provided

A file is submitted with two B-Levels, each with five cheque payments. The file is almost identical to BP08-POS,

but the first payment in the second B-Level includes a Creditor Agent and is thus not permitted. In the pain.002, the A-Level and the second B-Level are partially accepted with PART, and only the affected C-Level

is rejected with RJCT. The rejection only contains error code CH17 and the underlying element as an XML structure under OrgnlTxRef. The 9 correct transactions are booked with details in camt.053.

Payment type 8: domestic and foreign payments with bank cheque


Test Cases (11/14)

camt Test Files (credit-suisse.com/iso20022test)

Example lists the balances resulting from 50 transactions

CAMT052-01 Account Report – Balance Report

Intraday Account Statements – camt.052

Example lists the balances resulting from 50 transactions plus the transactions themselves,

batch booking without details, single booking with details

CAMT052-02 Account Report – Movement Report





Test Cases (12/14)


Example lists the balances resulting from 14 transactions plus the transactions themselves:

Account Statements – camt.053

CAMT053-03 With Details

Direction Kind of Payment CHF Booking Details Bank Transaction Code5

Outgoing Payment Type 5 2.36 Single3 yes4, in NtryDtls PMNT ICDT ESCT

Payment Type 4 4.78 Collective1 yes2, in NtryDtls PMNT ICDT OTHR6


Payment Type 3 10.10 Single3 yes4, in NtryDtls PMNT ICDT DMCT

Payment Type 3 Salary 10.20 Collective1 yes2, in NtryDtls PMNT ICDT OTHR6

Account Transfer 100.00 Single yes, in NtryDtls PMNT ICDT BOOK


Incoming Domestic FX 2.80 Single yes, in AddtlNtryInf XTND NTAV NTAV7

Domestic CHF 3.00 Single yes, in NtryDtls PMNT RCDT DMCT

Crossborder SEPA 3.47 Single yes, in NtryDtls PMNT RCDT ESCT

Domestic CHF future value date 6000.00 Single yes, in NtryDtls PMNT RCDT DMCT

Reject 3997.25 Single yes, in NtryDtls PMNT RCDT RRTN

Crossborder non SEPA 2.75 Single yes, in AddtlNtryInf XTND NTAV NTAV7

ISR8 7761.35 Single yes, in NtryDtls PMNT RCDT VCOM

1 Chosen by client with BtchBookg true 5 on C-Level, see page 57 7 Planned: PMNT RCDT XBCT 2 Chosen by client with CWD 6 Planned: PMNT ICDT AUTT 8 Only 1 transaction 3 Chosen by client with BtchtBookg false 4 Chosen by client with SIA





Test Cases (13/14)


Example lists the balances resulting from 14 transactions plus the transactions themselves:

Account Statements – camt.053

CAMT053-04 Without Details (i.e. without collective booking breakdown)

Direction Kind of Payment CHF Booking Details7 Bank Transaction Code3

Outgoing Payment Type 5 2.36 Collective1 no2 PMNT ICDT OTHR4

Payment Type 4 4.78 Collective1 no2 PMNT ICDT OTHR4



Payment Type 3 Salary 10.20 Collective1 no2 PMNT ICDT OTHR4

Account Transfer 100.00 Single yes, in NtryDtls PMNT ICDT BOOK


Incoming Domestic FX 2.80 Single yes, in AddtlNtryInf XTND NTAV NTAV5

Domestic CHF 3.00 Single yes, in NtryDtls PMNT RCDT DMCT

Crossborder SEPA 3.47 Single yes, in NtryDtls PMNT RCDT ESCT

Domestic CHF future value date 6000.00 Single yes, in NtryDtls PMNT RCDT DMCT

Reject 3997.25 Single yes, in NtryDtls PMNT RCDT RRTN

Crossborder non SEPA 2.75 Single yes, in AddtlNtryInf XTND NTAV NTAV5

ISR6 7761.35 Collective no PMNT RCDT VCOM

1 Chosen by client with BtchBookg true 3 on C-Level, see page 57 5 Planned: PMNT RCDT XBCT 2 Chosen by client with CND 4 Planned: PMNT ICDT AUTT 6 Several transactions 7 camt.053 without details contain details anyway a) for all single bookings, b) for outgoing collective bookings with pain.001 account steering CWD, and c) for outgoing collective bookings without pain.001 account steering if account default for camt.053 is with details.





Test Cases (14/14)


Product name: camt.054 Debit/Credit Example of the result of a pain.001 payment order with batch booking false and advice steering SIA Example lists 1 outgoing payment in USD debited to a EUR account (payment type 4)

CAMT054-05 Debit Advice (Single)

Account Notification – camt.054

Product name: camt.054 Debit/Credit

Example of the result of a pain.001 payment order without batch booking and advice steering tags Example lists 5 outgoing ISR payments in CHF debited to a EUR account (payment type 1)

CAMT054-06 Debit Advice (Collective)

Product name: camt.054 Debit/Credit Example of an incoming domestic non-ISR payment

Example lists 1 incoming payment in CHF credited to a EUR account

CAMT054-07 Credit Advice (Single)

Product name: camt.054 ISR

Example of a daily collective advice for all incoming ISR payments Example lists all 5 incoming ISR payments in CHF on November 27, 2017

CAMT054-08 Credit Advice (Collective)

Batch Booking false

Advice Steering SIA

Batch Booking true

Advice Steering CWD





CREDIT SUISSE (Switzerland) Ltd.

P.O. Box

CH-8070 Zurich

credit-suisse.com

The information provided herein constitutes marketing material. It is not investment advice or otherwise based on a consideration of the personal circumstances

of the addressee nor is it the result of objective or independent research. The information provided herein is not legally binding and it does not constitute an

offer or invitation to enter into any type of financial transaction. The information provided herein was produced by Credit Suisse Group AG and/or its affiliates

(hereafter “CS”) with the greatest of care and to the best of its knowledge and belief. The information and views expressed herein are those of CS at the time

of writing and are subject to change at any time without notice. They are derived from sources believed to be reliable. CS provides no guarantee with regard to

the content and completeness of the information and does not accept any liability for losses that might arise from making use of the information. If nothing is

indicated to the contrary, all figures are unaudited. The information provided herein is for the exclusive use of the recipient. Neither this information nor any

copy thereof may be sent, taken into or distributed in the United States or to any U. S. person (within the meaning of Regulation S under the US Securities Act

of 1933, as amended). It may not be reproduced, neither in part nor in full, without the written permission of CS.

Copyright © 2018 Credit Suisse Group AG and/or its affiliates. All rights reserved. SIQ

B 2

0

4.2

018