swift webinar automate universal confirmations for all

SWIFT Webinar

Automate Universal Confirmations

for all Financial institutions

September 2020

SWIFT Universal Confirmations – Automated Channels - Please do not share with third parties without SWIFT's prior consent, Sept 2020 2

Agenda

Q&A

How to plan your project to automate confirmations

4 channels to automate confirmations

Introduction – Universal Confirmations

What is the best channel for you?

Universal Confirmations is a mandatory requirement as from November 2020 (SR 2020)

All FIN users(*) (gpi and non-gpi banks) must comply with the

Universal Confirmations mandate in November 2020 and

provide a status to the Tracker for all received MT 103


* User categories Supervised Financial Institutions and Payments System Participants receiving MT 103

The compliancy to the FIN Universal Confirmations for MT 103

Rulebook will be visible to the Community starting 1 June 2021

(for gpi and non-gpi members).

https://www.swift.com/standards/standards-releases/release-highlights

Standards

Releases

https://www2.swift.com/go/book/book200561

https://www.swift.com/standards/standards-releases/release-highlights


More info on :

swift.com/confirmKey elements of the Rulebook Eligible FIN users will be required to provide a confirmation to the

Tracker on the outcome of their SWIFT customer payments

Applies to FIN Users* receiving MT 103.

* Note : category SUPE and PSPA

Mandatory confirmations will require to provide status

originator BIC, amount, currency and date/time of credit to

the beneficiary account or rejected payment.

Recommendation to provide confirmation as of date of receipt of payment,

or 2 business days, at the latest, after its value date (also for future value

date).

Recommended status updates: the status pending or transferred payments outside

of FIN are also available as (interim) confirmation

Financial institutions (8-character BIC) are measured on both mandatory and

recommended status compliance to confirm at least 80% of all their weekly

inbound MT 103

Confirmations are available to previous agents in the payments chain.

All FIN users receiving MT 103 will be measured for timely provision of confirmations as of Q2

2020, and performance will become available to all counterparties as of 1 June 2021

2

Yes YesYes Yes YesNo

*since DEC 2019 for gpi members and since MAY 2020 for non-gpi members

!

http://www.swift.com/confirm


There will be different channels to help banks generate confirmations

Options to provide confirmations

Any

SWIFT User

MT 103

MT 199

Payment system

CSV

SWIFT XML ISO - postponed

PaymentStatus API

SWIFT

Interface

Payments

Tracking

SWIFT

Tracker

Automated

Manual

Basic Tracker

WebAccess

CSV

Microgateway or API SDK

6

SWIFT Basic Tracker

SWIFT Universal Confirmations – Automated Channels - Please do not share with third parties without SWIFT's prior consent, Sept 2020

Basic

Tracker

Track Payments

Manual status updates Check adherence

Free of charges, preprovisioned and LIVE

https://www.swift.com/our-solutions/global-financial-messaging/payments-cash-management/the-basic-tracker/how-to-get-started


Agenda

Q&A






There will be different channels to help banks generate confirmations

Options to provide confirmations

Any

SWIFT User

MT 103

MT 199

Payment system

CSV


PaymentStatus API

SWIFT

Interface

Payments

Tracking

SWIFT

Tracker

Basic Tracker

WebAccess

CSV



Automated channels

Any

SWIFT User

MT 103

MT 199

Payment system

CSV


PaymentStatus API

SWIFT

Interface

Payments

Tracking

SWIFT

Tracker

Basic Tracker

WebAccess

CSV

1



Universal Confirmation of credit to the account of the beneficiary customer

Example of the confirmation through MT 199

Documentation

Early business validation

Implementation

Test Plan

Universal Confirmations rulebook

MyStandards samples

• Requires RMA with TRCKCHZZ

• Send a request to the Tracker BIC.

• Once approved you will receive an authorisation request

that you will need to approve.

Self-Test Guide


https://www2.swift.com/mystandards/#/search!usageguideline?q=universal


11SWIFT Universal Confirmations – Automated Channels - Please do not share with third parties without SWIFT's prior consent, Sept 2020



MT 103 MT 199Sender: ABCDGB22 Sender: WXYZUS33

Receiver:WXYZUS33 Receiver: TRCKCHZZ

{121:21b671f2-c0c8-4d78-8f98-981fbcb85248} {121:21b671f2-c0c8-4d78-8f98-981fbcb85248}

:20:ABCD12345WXYZ

:23B:CRED

:32A:191201USD480,

:33B:USD500,

:50F:/FR7613825002000877673388926

1/Jean Jacques

2/Chaussee de Paris 25

3/FR/Paris

:52A:SOGEFRPP

:59F://CH456782

1/Amazon

3/US/New York

:71A:SHA

:71F:USD20,

:20:WXYZ9876TRCK

:21:ABCD12345WXYZ

:79://1912011123-0500

//ACCC

//WXYZUS33

//USD470,

Mandatory status

Confirmed ACCC

Rejected RJCT

1. UETR

2. Date/time of credit

3. Payment status: confirmed or rejected

4. Credited amount & currency after

deducts

1

3

2

4

A mandatory status

cannot be modified after

it has been accepted by

the Tracker

12SWIFT Universal Confirmations – Automated Channels - Please do not share with third parties without SWIFT's prior consent, Sept 2020



MT 103 MT 199Sender: ABCDGB22 Sender: WXYZUS33

Receiver:WXYZUS33 Receiver: TRCKCHZZ

{121:21b671f2-c0c8-4d78-8f98-981fbcb85248} {121:21b671f2-c0c8-4d78-8f98-981fbcb85248}

:20:ABCD12345WXYZ

:23B:CRED

:32A:191201USD480,

:33B:USD500,

:50F:/FR7613825002000877673388926

1/Jean Jacques

2/Chaussee de Paris 25

3/FR/Paris

:52A:SOGEFRPP

:59F://CH456782

1/Amazon

3/US/New York

:71A:SHA

:71F:USD20,

:20:WXYZ9876TRCK

:21:ABCD12345WXYZ

:79://1912011123-0500

//ACSP/G001

//WXYZUS33/CRAGBICXXX/CLRG/FDW

//EUR445,/SHA

//EXCH//USD/EUR/0,91

//:71F:EUR10,

Payment transferred

via Fedwire

Recommended status

Transferred ACSP/G001

Pending ACSP/G002More info will follow

Pending ACSP/G003Missing documents

Pending ACSP/G004Waiting for funds

1

3

2

4

After “Pending”, a final

status must always be

sent as soon as

available



Exception handling (same logic applies to API and CSV payment confirmations)

MT 103

MT 199

SWIFT

Interface

MT 199

Basic Tracker

WebAccess

Payments

Tracking

SWIFT

Tracker

NAK

MT 199

MT 199

Alert

MT 199

rejected by

Tracker

MT 199

manually

repaired

Update payment in

Basic Tracker

Analyse root cause

- Identify payment UETR

- Lookup error code in

Universal Confirmations

rulebook

Repair MT 199

and resend

• In case of MT 199 NAK

• In case of MT 199 rejected by Tracker

1

2a

2b

FIN

Any

SWIFT User

Payment system



Exception handling (same logic applies to API and CSV payment confirmations)

MT 103

Any

SWIFT User

MT 199

Payment system

SWIFT

Interface

MT 199

Basic Tracker

WebAccess

Payments

Tracking

SWIFT

Tracker

NAK

MT 199

MT 199

Alert

MT 199

rejected by

Tracker

MT 199

manually

repaired

Update payment in

Basic Tracker

Analyse root cause

- Identify payment UETR

- Lookup error code in


rulebook

Repair MT 199

and resend

• In case of MT 199 NAK

• In case of MT 199 rejected by Tracker

1

2a

2b

FIN

DEBAUS33

DELIGHTFUL BANK USA

CALIFORNIA / UNITED STATES

Universal Confirmations rulebook Basic Tracker Operations GuideUniversal Confirmations SWIFTSmart Trainings



Automated channels

Any

SWIFT User

MT 103

MT 199

Payment system

CSV


PaymentStatus API

SWIFT

Interface

Payments

Tracking

SWIFT

Tracker

Basic Tracker

WebAccess

CSV

2


SWIFT Universal Confirmations – Automated Channels - Please do not share with third parties without SWIFT's prior

consent, Sept 2020

17

swift.com ISO 20022 Programme

New availability dates

and updated trck format

will be communicated

end 2020

https://www.swift.com/standards/iso-20022-programme/timeline?tl=en#topic-tabs-menu


Automated channels

Any

SWIFT User

MT 103

MT 199

Payment system

CSV


PaymentStatus API

SWIFT

Interface

Microgateway

or API SDK

Payments

Tracking

SWIFT

Tracker

Basic Tracker

WebAccess

CSV

3


Automated channels

Any

SWIFT User

MT 103

MT 199

Payment system

CSV


PaymentStatus API

SWIFT

Interface

Payments

Tracking

SWIFT

Tracker

Basic Tracker

WebAccess

CSV

3


1. UETR or TRN (field 20 of MT 103)

2. Payment status: confirmed or

rejected

3. Credited amount & currency

4. Date/time of credit



Example of the confirmation through CSV

Documentation


Test Plan

swift.com CSV format specification

MyStandards Readiness Portal CSV samples

• Requires RMA with TRCKCHZZ

• Send a request to the Tracker BIC.

• Once approved you will receive an authorisation request

that you will need to approve.

Self-Test Guide

Configure your application to generate the CSV

along the day or

as part of end of day processing

Implementation

Note1

2


https://www2.swift.com/mystandards/#/portal/_0XiGIAYYEeqfBNFoKPbuGw





“BSC-CSV1”, [“UETR”] (UUIDv4Identifier)/[TRN], “Related_Reference” (16x), ”DateTime”(YYMMDDHHMM±HHMM), ”Status_Code”(ACCC or RJCT),

[“Reason Code”], “StatusOriginator” (4!a2!a2!c[3!c]), “Currency”(3!a), “Amount”(15d)

"BSC-CSV1","21b671f2-c0c8-4d78-8f98-981fbcb85248","ABCD12345WXYZ","1912011623+0100","ACCC",,"WXYZUS33",“USD",“470,"

1 32 4

CSV format for mandatory status

CSV sample

Mandatory status

Confirmed ACCC

Rejected RJCT

A mandatory status

cannot be modified after

it has been accepted by

the Tracker




CSV format for recommended status

CSV sample

Recommended status

Transferred ACSP/G001

Pending ACSP/G002More info will follow

Pending ACSP/G003Missing documents

Pending ACSP/G004Waiting for funds

“ADV-CSV2”, [“UETR”] (UUIDv4Identifier), [“Service Type Identifier”] (001, 005), “Related_Reference” (16x), ”DateTime”(YYMMDDHHMM±HHMM),

”Status_Code” (ACCC, ACSP, RJCT, RETN), [“Reason Code”], “StatusOriginator” (4!a2!a2!c[3!c]), [”ForwardedToAgent”] (4!a2!a2!c[3!c]),

[”SettlementMethod”] (INGA,INDA, COVE, CLRG), [”ClearingSystem”], “Currency”(3!a), “Amount”(15d),

[“ChargeCode”] (OUR, BEN, SHA), [“Original_Curency”] (3!a), [”Target_Currency”] (3!a), [”Exchange_Rate”] (12d), [”Deduct”] (3!a15d) (repetitive)

“ADV-CSV2”,“21b671f2-c0c8-4d78-8f98-81fbcb85248“,”001”,“ABCD12345WXYZ”,”1912011623+0100”,”ACCC”,,”WXYZUS33”,,,,”USD”,”470,0”,,,,,”USD10,”,”USD20,”

After “Pending”, a final

status must always be

sent as soon as

available




Additional features in Alliance Access/Entry

No UETR in CSV? Use the Transaction Reference :20: of the original MT 103

Alliance will find back your MT 103 and retrieve its UETR

"BSC-CSV1","21b671f2-c0c8-4d78-8f98-981fbcb85248","ABCD12345WXYZ","1912011623+0100","ACCC",,"WXYZUS33",“USD",“470,“

Use instead

"BSC-CSV1",,"ABCD12345WXYZ","1912011623+0100","ACCC",,"WXYZUS33",“USD",“470,"

MT 103Sender: ABCDGB22

Receiver:WXYZUS33

{121:21b671f2-c0c8-4d78-8f98-981fbcb85248}

:20:ABCD12345WXYZ

:23B:CRED

:32A:191201USD480,

:33B:USD500,

:50F:/FR7613825002000877673388926


Batch Confirmations use case:

A bank receives 100 MT 103 messages

Payment system generates CSV files with 90 lines

Interface processes the file and updates the Tracker via MT 199

Questions:

How to inform the Tracker about the 10 payments under investigation by sanctions?

What happens if the Tracker rejects the status updates?

100 MT 103 received in SWIFT Interface

10 are investigated by sanction filter

90 are processed by payment system

Alliance Access/Entry


Batch Confirmations – happy path processing workflow

Payments

Tracking

SWIFT

Tracker

Payment system

WebAccess

Basic Tracker

CSV split in individual

lines, each reconciled

with the received MT 103

100 MT 103 received

Credit Confirmation

created for each line

and Tracker updated

via MT 199

FIN

10 MT 103

investigated by

sanctions filter

Payment system

generates CSV

files with 90 lines

2

1

4 5

6

90 Payment statuses

successfully updated

in Tracker

7

Verify payment

status in Basic

Tracker

8

Payment system

processes 90

payments

3

Sanctions

MT 199CSV

FIN



Batch Confirmations – sanction team reports which payments are

under investigationPayments

Tracking

SWIFT

Tracker

Payment system

WebAccess

Basic Tracker100 MT 103 received

10 MT 103

investigated by

sanctions filter

1

FIN

MT 199

Sanction filter

generates CSV

files with 10 lines

Generate CSV for

each payment

on-hold

2

Update payments

in Basic Tracker

1

2 options to update the Tracker: manually in Basic Tracker or automated via CSV (or MT 199)

CSV

FIN


10 payments are investigated in sanction filter: update them in Basic Tracker

1 2

3

27

Select “On Hold”

List of

payments not

yet confirmed

Basic Tracker


4 5

10 payments are investigated in sanction filter: update them in Basic Tracker

List of

payments on

hold

28

Basic Tracker


Batch Confirmations use case:

A bank receives 100 MT 103 messages

Payment system generates CSV files with 90 lines

Interface processes the file and updates the Tracker via MT 199

Questions:

How to inform the Tracker about the 10 payments under investigation by sanctions?

What happens if the Tracker rejects the status updates?

100 MT 103 received in SWIFT Interface

10 are investigated by sanction filter

90 are processed by payment system

Batch Confirmations – 90 payments updated and 5 rejected by Tracker



SWIFT

Tracker

Payment system

CSV split in individual

lines, each reconciled

with the received MT 103

100 MT 103 received

FIN

Payment system

generates CSV

files with 90 lines

1

4 5

85 Payment statuses


in Tracker

5 rejected by Tracker

6Payment system

processes 90

payments

3

5 payment

updates

rejected by

TrackerMT 199

Alert MT 199

CSV

Payments

Tracking

FIN



Batch Confirmations – 5 payment updates rejected by Tracker

SWIFT

Tracker

WebAccess

FIN

85 Payment statuses


in Tracker

5 rejected by Tracker

Tracker Alert

In case MT 199 or

API calls are invalid,

Tracker sends alert

back (as MT 199 or

in API response)

MT 199

invalid

MT 199

manually

repaired 5 payment

updates

rejected by

Tracker

Repair MT 199

and resend

2b

Analyse root cause

Identify payment UETR

Lookup error code in


rulebook

1

Update payments

in Basic Tracker

2a

MT 199

Alert MT 199

MT 199

Basic Tracker

Payments

Tracking


Automated channels

Any

SWIFT User

MT 103

MT 199

Payment system

CSV


PaymentStatus API

SWIFT

Interface


Payments

Tracking

SWIFT

Tracker

Basic Tracker

WebAccess

CSV

4



Example of the confirmation through API

Documentation


Test Plan

SwaggerHub domain: https://app.swaggerhub.com/apis/SWIFT-API/

https://developer.swift.com

Use the data model code from

swaggerhub / SWIFT SDK and

integrate in your application

Optional:install and configure the

gpi Connector

Self-Test Guide

SWIFT Consulting available to

answer all your questions

PaymentStatus API

{

"payment_status_request": {

"from": "WXYZUS33",

"update_payment_scenario": "CCTR",

"uetr": "21b671f2-c0c8-4d78-8f98-981fbcb85248",

"instruction_identification": "ABCD12345WXYZ",

"payment_status": {

"originator": "WXYZUS33",

"funds_available": "2019-12-01T16:23:00",

"transaction_status": {

"status": "ACCC"

},

"return": false,

"confirmed_amount": {

"currency": "USD",

"amount": "470"

}

}

}

}

1

3

2

4

Implementation

Note RESTful Web services

JSON data format

https://app.swaggerhub.com/apis/SWIFT-API/

https://developer.swift.com/



Agenda

Q&A






consent, Sept 2020

35

Which confirmation channel is best for me?

• Limited volume

• Adapt Operators’

daily tasks

• Compliance to

Universal

Confirmations

Basic Tracker

• Reuses existing

FIN rails

• Supplier already

compliant with

Universal

Confirmations

• Many payment

systems support

CSV

• Supplier already

supports posting

in CSV export file

MT 199 CSV format

• Postponed to

2021

XML trck.001.001.01

• Lean and real-

time update to

Tracker

• IT knowledgeable

in API

development

API

Straight-through-processingManual

Go to https://www.swift.com/confirm

Select the ‘Get started today’ button

+

https://www.swift.com/confirm


consent, Sept 2020

36

Where can I find all the information?

Go to https://www.swift.com/confirm

Select the ‘Get started today’ button

Basic Tracker

Manual

MT 199 CSV format XML trck.001.001.01 API

Straight-through-processing

+

Basic Tracker setup + Universal Confirmations rulebook + FAQ

Basic Tracker Step by

Step Connection

Guide

Basic Tracker

Operations Guide

Universal

Confirmations rulebook

CSV format specifications

CSV Batch Confirmations

Workflow

Alliance Access 7.5 -

Message Management

Guide

Alliance Access 7.5 -

Configuration Guide

As from

SR 2021

API SwaggerHub

specification

SWIFT SDK

Self-test Guide Plan your project Validate your data Integration testing Exception handling 1 2 3 4

https://www.swift.com/confirm










https://app.swaggerhub.com/apis/SWIFT-API/


https://www.swift.com/our-solutions/global-financial-messaging/payments-cash-management/unlocking-payment-confirmations/frequently-asked-questions-about-universal-confirmations

https://www2.swift.com/myprofile/res/subjects/universal_confirmations/index.html


Agenda

Q&A





SWIFT Universal Confirmation– Please do not share with third parties without SWIFT's prior consent,

September 202038

Universal Confirmations timeline : what does it means for you

7

You have 12 weeks to be compliant and confirm

according to Universal Confirmations rules.

See Chapter 3.5 Universal Confirmations Score

of the Basic Tracker Operations Guide or

Knowledge Base TIP 5023986

SEPTEMBER 2020

NOVEMBER 2020

Universal Confirmation is a mandate part of SR2020.

See FIN Service Description section 21 : contractual

roles and responsibilities

If you are not compliant 2 weeks after SR2020, you*

will not have access to tracking features anymore.*non-gpi members

JUNE 2021

The Community will see if you are compliant with

the Universal Confirmations mandate

(scoring/color) and for how many weeks you are

in that status.

Webinar explaining scoring

Register here


https://supportkb.swift.com/Pages/f5e0f430-57a8-4d26-a1c1-c4a1799f2bee.aspx

https://www2.swift.com/knowledgecentre/publications/fin_sd/5.0?protected=true&reload-date=1590590561723

https://www.swift.com/news-events/webinars/the-basic-tracker_all-you-need-to-know

https://www.swift.com/news-events/webinars/universal-confirmations-final-countdown?utm_source=dem&utm_medium=email&utm_campaign=gpi&utm_content=The%2BUniversal%2BConfirmations%2Bdeadline%2Bis%2Bapproaching&utm_term=



consent, Sept 2020

39

Universal Confirmations timeline : what does it means for you Webinar explaining scoring

Register here

Sept 2020 Oct 2020 Nov 2020 Dec 2020

Number of

weeks

Color

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

22 Nov SR 2020

21 28 12 19 26 02 09 16 07 1414 05 21 2823

- Improvement period of 12 weeks -

07 30

SWIFTSmart :

Scoring explained in 10 min




https://swiftsmart.swift.com/Saba/Web_spf/EU1PRD0018/app/shared;spf-url=common%2Fleclassdetail%2Fregdw000000000633864

https://swiftsmart.swift.com/Saba/Web_spf/EU1PRD0018/app/shared;spf-url=common%2Fleclassdetail%2Fregdw000000000633864

40

Be ready to confirm in November 2020

November

2020

Getting

Started

• Decide which channel(s) you will use to confirm + set up access to the Basic Tracker


• Prepare your back office and operations teams for payment confirmations

• In case you use a third party application, engage with your

vendor. Provide your payment application vendor details

here, SWIFT will engage and support them to prepare for

universal confirmations

Vendor

• Start testing MyStandards Readiness Portal (MT 199, CSV)

• Use Developer Portal for the API

Test

Be ready • Go live in November 2020 with the Standards Release cutover

Operations

https://www.swift.com/our-solutions/global-financial-messaging/payments-cash-management/unlocking-payment-confirmations/is-your-vendor-gpi-compatible_?tl=en#topic-tabs-menu


Dedicated webinars for all SWIFT members

Payment confirmations

are essential for all

banks. We encourage

you to share the links

to register to our

webinars with any of

your counterparties.

Register here

+ dedicated webinars on Universal Confirmations (Basic Tracker & Score measurement) Register here



https://www.swift.com/news-events/webinars/four-easy-ways-to-automate-payment-confirmations



Questions and Answers

?SWIFT Universal Confirmations – Automated Channels - Please do not share with third parties without SWIFT's prior consent, Sept 2020 42

www.swift.com


consent, Sept 2020

www.swift.com/confirm

43

swift webinar automate universal confirmations for all

Documents