SWIFT Interfaces

Swiss Business Forum

Alain Drese

18 March 2015

Drivers for Change

• Increased complexity of requirements

• Increased automation of the workflow and processes

• Cost management and flexibility

• Globalisation continues at a pace

• Reliance on software and technology

ISO 20022 adoption

200 initiatives Under discussion > planned > rollout > live

90 countries

Europe Asia Pacific

Americas Middle East & Africa

ISO 20022 Payments

Securities

Trade Services 51% Foreign Exchange

42%

4% 2% 1%

Cards

A bank’s ISO 20022 landscape..

Your participation to

Market

Infrastructures

2017 2016 2015 Step2

EURO1/

STEP1

Baltic CSDs

ACH CENIT (CO)

Securities

2018

& beyond

Your customers

(corporates and banks)

2016 2017 2015 2018

& beyond

Payments

Is your messaging infrastructure ready to process 20022 standards ?

From an operational perspective as good as what you do for FIN today ?

SWIFTAlliance Portfolio

SWIFT Alliance family

Alliance

Access

Alliance

Lite2

Base Setup

Parameterization

Configuration

Alliance

Messaging

Hub

Customization

Simple Medium Complex

Capabilities

Complexity

Alliance Remote Gateway

(ARG) Alliance Lifeline

Alliance Lite2 Alliance Lite2

For Business Applications

SWIFT Cloud Portfolio

1300+ customers

Alliance Remote Gateway

Alliance Lifeline

Lite2 for Business Applications

Alliance Lite2

Alliance Lite

Cloud portfolio distribution - 2014

Reporting and Printing

Usability Features

Multi- Windows Single session

Multiple parallel views

Monitoring Statistics dashboard

Configurable view

Release 7.1 coming soon

SWIFT Alliance Access

MyStandards

Alliance Access 7.1 Obtaining business usage guidelines from MyStandards

Before (current behaviour)

• All fields shown

After (with injected business usage guidelines)

• Fields specified in usage guidelines shown

Alliance Access 7.1

Alliance Access 7.1 Hide fields removed via the business usage guideline

Alliance Access 7.1 Display reduced choice form the business usage guideline

AMH as an integration platform

Other

networks

Core

Banking

Systems

Payment

Systems

Fund

Management

Systems

AMH

Inte

rna

l

Ex

tern

al

SWIFT readiness – AMH 3.3

• AMH3.3 released June 2015 supports the new ISO20022

requirements

– New formats:

– Manual entry based on SIC-provided XSD’s

– Metadata enrichment based on payload elements

– Address-book updates of BICs and BCs

SWIFT readiness – AMH 3.3

– Support for defaulted values in the payload (creation date and

currency)

– Specific business logic

• Camt.019 – influence clearing day and settlement cycle activities

• Pacs.002 and camt.025 – messages are reconciled with the original sent

payload and might affect the original payment lifecycle

• Auto-Generation of pacs.002 for incoming traffic

• Auto-Generate of camt.008 (message cancellation for pacs.008 or pacs.009)

– Technical duplication check support. Different algorithm for

different message types

– Validation of payload according to SIX XSD

– SIX Backup - generate SIXBackup & MiniSIC containing XML

messages

ISO 20022 Business

Application Readiness

ISO 20022 Adoption Summary of potential back office integration models

MI

over

ISO 20022 MX

B/O

MT or Internal

formats

SWIFT

Interface

MX

generation

B/O is adapted to

fully adopt MX MX

B/O stays MT based.

MT/MX mapping is

handled in separate

middleware

MT/MX

mapping

package

MI

Over

ISO 20022 MX MT

MT format

Middleware

SWIFT

Interface B/O

MX

MT/MX

mapping

package

MI

Over

ISO 20022 MT

MT format

SWIFT Interface B/O

MX

B/O stays MT based.

MT/MX mapping is

handled by the

SWIFT interface

ISO 20022 Adoption Impact of integration models on manual message creation

MI

over

ISO 20022 MX

B/O

MT or Internal

formats

SWIFT

Interface

MX

generation

B/O is adapted to

fully adopt MX

MX

MX

B/O stays MT based.

MT/MX mapping is

handled in separate

middleware

MT/MX

mapping

package

MI

Over

ISO 20022 MX MT

MT format

Middleware

SWIFT

Interface B/O MX

MX

MT/MX

mapping

package

MI

Over

ISO 20022 MT

MT format

SWIFT Interface B/O MT

MX

B/O stays MT based.

MT/MX mapping is

handled by the

SWIFT interface

MX

ISO 20022 for High-Value Payments SWIFT provided mapping package

MI

over

ISO 20022 MX

B/O

MT or Internal

formats

SWIFT

Interface

MX

generation

B/O is adapted to

fully adopt MX

MX

MX

B/O stays MT based.

MT/MX mapping is

handled in separate

middleware

MT/MX

mapping

package

MI

Over

ISO 20022 MX MT

MT format

Middleware

SWIFT

Interface B/O MX

MX

MT/MX

mapping

package

MI

Over

ISO 20022 MT

MT format

SWIFT Interface B/O MT

MX

B/O stays MT based.

MT/MX mapping is

handled by the

SWIFT interface

MX

IPLA

based

Alliance Access

SIL

Alliance Access, AMH

Other interface vendors ?

What about Services

Coffee Break

…11:15 am