1. Incentage puts you on top of your financial messaging operations.
XML Processing for T2S
Christian Kurmann
Christian Kurmann, Enterprise Architect Incentage for almost 10 years
Incentage has implemented the T2S projects at SIS Swiftzerland and VP Securities of Denmark, both in production.
The Incentage software is used to create valid ISO20022 messages for the network from internal data which can be COBOL, PL1, old ISO15022 or internal XML messages.
Generated messages are fully tracked and monitored within Incentage Web Gui where they can also be edited and manually created.
Incentage AG, Switzerland

2. MX Messages are like teenagers.
They’re new and loud and need attention and monitoring.
And while they may all look quite similar they all have their very own problems.
But the most important point; They are our Future.

3. urn:iso:std:iso:20022:tech:xsd:sese.024.001.03 MessageType sese.024
Naming
XML MX
sese
urn:iso:std:iso:20022:tech:xsd:sese
MessageType
sese.024
sese
urn:swift:xsd:sese
Complications begin with names.
It is important to note that only the full xml namespace uniquely distinguishes ISO20022 messages. (urn:iso:std:20022:tech:xsd:sese )
Sources for these definitions are the iso20022.org page or SWIFT MyStandards.
Services are used on the SWIFT Network and define a collection of ISO20022 messages for a specific business area (swift.if.ia are FUNDs messages). Customers can register thier own services on the swift network (vp.services was registered by VP Securities of Denmark). This is required because many ISO20022 messages do not currently have a service on which they can be sent ofer the Swift network in. (All messages can be sent via FileAct of course)
Service
swift.if.ia
vp.services
t2s, t2s!px, t2s!pe

4. <AppHdr xmlns:Ah="urn:swift:xsd$ahV10"> <MsgRef> </MsgRef> <CrDate> T15:50:00</CrDate> </AppHdr>
Header
<AppHdr xmlns="urn:iso:std:iso:20022:tech:xsd:head "> <Fr> <FIId> <FinInstnId> <Othr> <Id>cn=funds,ou=abcdchzz,o=swift</Id> </Othr> </FinInstnId> </FIId> </Fr> <To> <FIId> <FinInstnId> <Othr> <Id>cn=funds,ou=dcbadeff,o=swift</Id> </Othr> </FinInstnId> </FIId> </To> <BizMsgIdr> </BizMsgIdr> <MsgDefIdr>setr </MsgDefIdr> <BizSvc>swift.if.ia</BizSvc> <CreDt> T15:50:00</CreDt> </AppHdr>
Document
A Service defines not only the ISO20022 messages to use (these are stored in the document section) but also specify a header section. Currently two headers are used. $ahv10 and head
A business message for T2S or for FUNDs, sent via the SWIFT network, must include the correct header.
However the header and document are actually two seperate messages which are on the same level. As such they need a surrounding XML envelope to become valid XML.

5. Incentage AG, Switzerland
Logical mapping FIN -> Interact Request using the Application Header AppHdrV1.0
<SwInt:Request> <SwInt:RequestHeader> <SwInt:Requestor>ou=abcdchzz,o=swift</SwInt:Requestor> <SwInt:Responder>ou=dcbadeff,o=swift</SwInt:Responder> <SwInt:Service>swift.if.ia</SwInt:Service> <SwInt:RequestType>setr </SwInt:RequestType> </SwInt:RequestHeader> <SwInt:RequestPayload> <AppHdr xmlns:Ah="urn:swift:xsd$ahV10"> <From> <Type>DN</Type> <Id>cn=funds,ou=abcdchzz,o=swift</Id> </From> <To> <Type>DN</Type> <Id>cn=funds,ou=dcbadeff,o=swift</Id> </To> <MsgRef> </MsgRef> <CrDate> T15:50:00</CrDate> </AppHdr> <Document xmlns:Doc="urn:swift:xsd:setr "> <SbcptOrdrV03> <MsgId> <Id> </Id> <CreDtTm> T18:13:51.0</CreDtTm> </MsgId> <PoolRef> <Ref>Ref0</Ref>
Swift Service directory
Sender
Transport
Receiver
Service
Message Type
User Reference
Bilateral or market practice agreements
Business Identifier
{1:F01ABCDCHZZAXXX }{2:I502DCBADEFFAXXXN}{3:{108:MYTRN}}{4:
:16R:GENL
:20C::SEME// …
Header
Example logical mapping of the old ISO15022 and the new ISO20022 messages in regard to network informations such as sender and receiver.
Please note that the ISO20022 message document section does not contain any of this information with the exception of an ID. (There are plans to move the ID to the header section)
The Header section defined by the Services contain TO and FROM but these do NOT contain the network sender / receiver information equivilents to the BICs in the ISO15022.
This means that there must be an additional envelope surrounding the payload header and document which also contains the sender and receiver information. The Envelope is however NOT defined by any ISO20022 standard and is specific to the various network interface software vendors (SAA, SAG, T2S Connector, WBIFN, SIA Colt, all have different envelopes.)
Document
Incentage AG, Switzerland

6. > 100 message types which can be downloaded from Swift MyStandards
T2S elements
Header
head (BAH)
Document
> 100 message types which can be downloaded from Swift MyStandards
These span the messages covering acmt, admi, camt, reda, semt and setr.
Available in multiple versions. Currently Version 2 is active. New Versions are already available. Versions are NOT mentioned within the message type name
Multiple message types contain the word DRAFT in the message type name. These are live and used in production and it is unclear if and when naming will change. (urn:eurosystem:xsd:DRAFT4reda )
In T2S the header element to use is the head The T2S guidelines also specify the exact fields to fill and expect in responses.
The T2S service specifies a list of over 100 ISO20022 messages. These are published on MyStandards.

7. SIA Colt, SWIFT T2S Connector
T2S Connections
SIA Colt, SWIFT T2S Connector
T2S Connector
RFH2 header
Header
Document
In case of the T2S connector, no envelope is used in the data communication. This means the data sent via MQ queue is NOT XML valid and needs special handling before XML parsing can begin. Sender and Receiver information must be passed to the interface inside an RFH2 header (this is a special IBM MQ queue storage section which is passed along with every sent message)
The RFH2 header also contains the routing and ID correlation information and is specified in the SWIFT T2S Connector documentation

8. T2S Processing pitfalls
Backend
Middleware
T2S Connector / SAA
T2S
There are a lot of possible problems with implementing T2S connectifiy. Here a small list:
Fileact monitoring. (Via admi response messages) The T2S connector bulks some messages into files before sending them out. It can be important to know which messages belong to which file as T2S will send responses to the Fileact and this must then be correlated to all the messages contained in the bulk.
Sequencing, T2S messages are sequenced. However Fileact deliveries be take a while to unpack on the T2S connector. This means other messages can overtake and the middleware may need to resequence.
Validation, Messages defined in T2S sometimes contain additional messages embedded inside the document which can make handling and validation tricky.
T2S connector sends data over MQ using MQ segmentation. This requires software capable of handling segmented data to correctly process the information.

9. Very large reda. 012 reports are common in T2S messaging
Very large reda.012 reports are common in T2S messaging. These can be maximum 32MB and we routinely get multiple of these every day.
It is important to have parallel processing streams setup for ISO20022 message handling to ensure that single big messages do not block the high speed processing channels you need to have in place for all the new query response messages.
These large messages also have a big impact on data storage and on the required settings of you messaging infrastructure such as Databases, MQ Queues etc.

10. Conclusion
Shield internal applications from external message formats via middleware
Consider sequencing. Ideally solve this in the target application
Split processing into multiple channels to handle large messages
Consider implementing monitoring
Build up ISO20022 experts.
Define an internal messaging wrapper for ISO20022

11. Transportwrapper Get it at www.incentage.com Or
We recommend the use of a dedicated transport wrapper for internal message communication concerning ISO20022 messages. For this purpose we have developed together with members of the swiss market practise group, a template that covers most requirements.
You are welcome to use this and adjust as required.
Regards Christian Kurmann
Get it at Or