3. Back Office not designed to
connect to SWIFT
Discrepancy between internal
message formats and SWIFT
formats
Yearly Standards updates to be
applied to applications
Multiple applications, multiplied
complications
Involvement of more than one
vendor and team
SWIFT
Clients
Service
Providers
Typical integration challenges
Solving your integration challenges – 23 April 2015 3
4. Connecting your back office to SWIFT can be very complex and requires specific expertise
Interfaces
Messaging
services
A secure
network
Applications
Reference
data
Standards
Integrating your back office with SWIFT…
Sounds easy ?
Solving your integration challenges – 23 April 2015 4
7. Solving your integration challenges – 23 April 2015
Integration Domain
Interface can be adapted to customer needs
Specialized integration skills required, available from SWIFT
Highly flexible and based on standard integration modelling
Faster to adapt and lower TCO compared to back-office
change process
Powerful solution to replace costly legacy systems
Product Domain
Out of the box product that can be configured to customer needs
Quick deployment and time-to-market to start adding value to business lines
All functions available at fingertips
New product release required for new functions
7
Alliance family overviewFeatures
Network
Communication
Messaging
Interface
Integration
capabilities
MarketSimple Medium Complex
Integration
Platform
Alliance
Access
Integration
Platform
Alliance
Access
Alliance
Lite2
Alliance
Lite2
Alliance
Messaging
Hub
Alliance
Messaging
Hub
Alliance
Gateway
Alliance
Gateway
Alliance
Gateway
Alliance
Gateway
ARGARG
Other
Gateway
Other
Gateway
SWIFT
Integration
Layer
SWIFT
Integration
Layer
10. Getting more out of your messaging interface
10
Alliance Access
Application
Interface
Integration Platform
IPLAInternal API
FIN
Interface
SWIFTNet
Interface
SWIFTNet
Message store Message queuesMessage routing
Validation Transformation
Application1
Application2
proprietary format
SWIFT format
Connectors
Enrichment
Alliance
Gateway
Solving your integration challenges – 23 April 2015
Alliance Integration Platform
Overall Architecture
IPLA
13. SWIFT Integration Layer (SIL)
Overall architecture
13
Transformation
Connectivity
Format Support
SWIFT format
or Proprietary format
SWIFT format
or Proprietary format
SWIFT format
or Proprietary format
New
SWIFT Integration Layer
New
New
Solving your integration challenges – 23 April 2015
14. IPLA
– Fully embedded in Alliance Access
– Seamless interaction with Alliance
Access routing rules
– Benefits from Access operations,
maintenance, backup, resilience
– GUI based configuration and
transaction monitoring via Web
Platform
– Search message capabilities via Web
Platform.
IPLA and SWIFT Integration Layer
One product – 2 ways to deploy
SWIFT Integration Layer
– Provides integration solutions for
both Lite2 and Alliance Access
– Independent from Alliance Access and
main message flow
– Lightweight footprint for powerful
integration
– Connectivity to Alliance Access using
Message Partners (AFT, SOAPHA,
MQHA)
– Flexible setup: Different OS than
Alliance Access, can be hosted on
the same machine or a different one
than Alliance Access
14Solving your integration challenges – 23 April 2015
17. 17
Out of the box with IPLA
Core functionality:
- Compression/decompression logic
- Message headers applied to payload
- Signature generation and verification
- Oversize and time-out management
Advanced functionality requiring tailored
integration development:
- Bulking/debulking
- Paginated responses
- Transformation to/from ISO20022
Out of the box with IPLA
Core functionality:
- Compression/decompression logic
- Message headers applied to payload
- Signature generation and verification
- Oversize and time-out management
Advanced functionality requiring tailored
integration development:
- Bulking/debulking
- Paginated responses
- Transformation to/from ISO20022
Connector for T2S
Straightforward connectivity to T2S
Solving your integration challenges – 23 April 2015
18. 18
Connector for Sanctions
The most flexible way to integrate with Sanctions
Solving your integration challenges – 23 April 2015
InterfaceAlliance
Access
Connector
for
Sanctions
Back Office
Sanctions
Screening
FINInterface
Back Office
SWIFT
/other network
Current Copy option
Connector option
SWIFT
Transaction to be screened
“Good” transaction
“Rejected” transaction
19. 19
Connector for T2
T2 & E1/S1 “like for like approach”
Solving your integration challenges – 23 April 2015
Concepts
– Usage guidelines ‘ISO 20022 for High-Value Payments’
– Restricts the ISO 20022 standards to the business functionality (like-for-
like) available in the corresponding MT standards
Enables the development of an ‘automated’ mapping package
MT/MX
mapping
package
T2 example
pacs.
008
009
010
camt.054
MT 950
MX ACK
002
003
xsys.
SWIFT
Backoffice
MT
103(+)
202 (COV)
204
MT 950
MT ACK
012
019
MT
MT 900
910
High-Value Payments usage guidelines
‘Like-for-like’
Technical header equivalence
Between MT and MX
HVP
Converter
20. 20
HVP
Converter
MI
Over
ISO 20022
MXMT
MT format
Alliance
Access
B/O
MX
HVP
Converter
MI
Over
ISO 20022
MT
MT format
Alliance
Access
B/O
MX
The main purpose of HVP Converter is to shield a back-office from migrating to MX (ISO 20022)
MT-MX transformations made according HVP T2 specifications
Auditing messages content before and after transformations
/
Lite2
Provide HVP Converter for Lite2 customers
Mediating FIN protocol to InterAct for making ISO
20022 messaging ideally completely transparent for
FIN aware back-office
Connector for T2
T2 & E1/S1 “like for like approach”
Solving your integration challenges – 23 April 2015
23. Project management
Knowledge transfer and formal training
Functional
Analysis
Technical
Design
Develop-
ment
Test Go Live Care
Advise on appropriate
integration product and
required effort
Zooming in on the Integration part
Across project lifecycle
Solving your integration challenges – <<date>>Solving your integration challenges – 23 April 2015 23
24. Solving your integration challenges – 23 April 2015 24
Custom Code Maintenance
Package content
• Proactive check of impact on custom code
solution by annual SWIFT Release
• Proactive check of impact on custom code
solution by mandatory Alliance releases
• Availability of knowledgeable engineer on a 12 x
5 basis for issue investigation (SLA: availability
within max 1 day)
• Storage of golden copy of the custom code
solution and related documentation
• Attractive pricing
(without a CCM contract, support will be
charged at a premium rate)
25. Solving your integration challenges – 23 April 2015 25
Developer Seat
Supporting co-delivery
• SWIFT can offer Developer Seat
licenses for customers that want to
participate in the delivery or want to
further evolve the solution
• Developer Seat package consist of
• Developer Seat License
• Training
• Envelope of consulting days for
development assistance
• Review of coding best practices
• Project handover
26. Content
- Check if a MT940 is single-page or multiple page and if
all of the pages of a multiple page MT940 are received
- Process the MT940 and ensure that only complete
MT940 statement data per senders BIC, account,
currency code and statement date is passed to
Convertor (or IPLA).
- Transform the MT940’s into a single coherent unit that
represents the total daily activity in a cash account that
can be passed into a routine to further transform that
daily activity into any statement format (e.g. BAI2,
Excel).
Background
The 2,000 character message size restriction on SWIFT
requires many MT940 statements to be split among multiple
statement pages, each sent across the SWIFT network as a
separate message with a unique reference number. These
pages may not be delivered to the recipient in the order that
they are sent, and the delivery of each individual page is not
guaranteed as pages can NAK on SWIFT.
In order to correctly reconcile MT940 into a statement format,
clients require the re-assembling of all pages of an MT940
into a single coherent unit.
Re-usable components
MT940 aggregation
1
2
4
3
SWIFT Integration Layer
or
IPLA
Solving your integration challenges – 23 April 2015 26
27. Content
- Management of the typical FileAct flows (ingoing and
outgoing) between Corporates and their Correspondent
banks
- Customization through configuration
- Support for Multiple file formats towards different banks
(Routing)
- Logging of all transactions (monitoring)
- Optional components
- Validation of file content
- Transformation of file content
- MQ connectivity
- Formatting of authorization info (i.e. Txs Count)
Background
Corporates typically want to communicate with their
Correspondent banks via FileAct. While doing so they need
a number of functionalities such as calculation of transaction
count, a processing results report and flow type selection
based on MT, sender and Receiver BIC
Re-usable components
FileAct for Corporates
Bank A
SWIFT
SWIFT Integration
Layer
Bank B
Payments
File
Acknow-
ledgement
Report
File
Monitoring
1
2
3
Bank A or B ?
Corporate
Solving your integration challenges – 23 April 2015 27
29. Single point of contact for
SWIFT matters during the
complete project lifecycle
Access to Standards expertise
Successful delivery within
challenging timeframe
Competitive pricing
Fundsquare
Support for Funds Market Infrastructure using IPLA
End-to-end integration project
covering analysis, design,
building (incl. mappings),
installation, testing, go live and
project management
Largest IPLA implementation so
far
Premium support, remote
support and tailored support
contract for custom code
Interaction with many parties
involved (Bourse de
Luxembourg, Accenture, SWIFT,
TRACE, development partner)
Challenging fixed delivery
deadline
Different applications involved
(Altus Fund Management,
Finesti Funds database, Alliance
Access)
Conversion between MT and MX
Evolving requirements
The solutionThe challenges The benefits
Solving your integration challenges – 23 April 2015 29
30. The challenges
Hide T2S Protocol complexity
E.g.
- Selection of the service
- Compression of IA
Enrichment of messages in
order to comply with T2S
Computation of the T2S
signature
Handling of bulk messages
Minimise impact on the back
office
T2S itself is not live yet
Solution designed from
discussion with customer
Fully integrated into SAA
Flexible architecture
Short implementation
timeframe
Reduced operational risk
due to productised solution
Continuous support for
changes coming from T2S
Implementation of the C4T2S
using IPLA
Requirements definition
based on the T2S UDFS
Development of separate
modules to address typical
challenges
- Direct Payload used
Productised solution tailored
through services
3030
The solution The benefits
Solving your integration challenges – 23 April 2015
Banque de France
Technical connectivity to T2S
31. Efficient connections
between business controller
and various system
components through single
platform
Improved STP
Reduced operational risk
Standardisation on ISO
20022
3131
Implementation of Alliance
Integrator including:
Feasibility analysis
Requirements definition
Development of business
flows incl. transformation
and routing
Ongoing support to in-house
developers
Implementation of cutting edge
funds distribution hub
Automation of settlement
process
Many subsystems need to ‘talk’
to a central business controller
application
Translation between SWIFT
and proprietary formats
Reporting to authorities
The solutionThe challenges The benefits
“….”
Solving your integration challenges – 23 April 2015
ODIN, Norway
Standardisation on ISO20022
33. We advise on what we do best …
SWIFT: recognised
for operational
excellence across
the industry
Access to 1,800 +
SWIFT specialists
and strong partner
network
Growing team with
already more than
100 experts with
average seniority of
more than 10 years
1 , 0 0 0 + P R O J E C T S O V E R T H E L A S T 3 Y E A R S
3 , 0 0 0 + C U S T O M E R S U S I N G S W I F T S E RV I C E S
AV E R A G E S AT I S FA C T I O N R AT E A B O V E 4 . 4 / 5 . 0
Solving your integration challenges – 23 April 2015 33
34. • Already 50+ IPLA projects delivered in EMEA
over the last 3 years
• Comprehensive integration portfolio with
experienced consulting services
• Organisation: end-to-end projects
• Optimal sourcing model
• Trusted methodology
• No surprises thanks to upfront analysis
• Products fully supported by SWIFT
34
SWIFT is the perfect partner for solving your integration challenges
Differentiating factors
Solving your integration challenges – 23 April 2015
35. In case of further questions
Pieter Apers
SWIFT
Av Adèle 1
B-1310 La Hulpe
Belgium
+32 2 655 3576
+32 2 655 3752
+32 475 542 458
pieter.apers@swift.com
www.swift.com
T
F
M
W
E
Manager Integration Services
Consulting Services, EMEA
Solving your integration challenges – 23 April 2015 35
Imran Mirza
SWIFT
Av Adèle 1
B-1310 La Hulpe
Belgium
+32 2 655 3402
+32 497 657 549
imran.mirza@swift.com
www.swift.com
T
F
M
W
E
Integration
Product Management | Marketing