What the SEPA components contain

The WebSphere Transformation Extender SEPA components contain the following principal components:

• ISO 20022 (UNIFI) message schemas for credit transfer and direct debit (.xsd files) and theWebSphere Transformation Extender type trees for credit transfer and direct debit formats. The type trees are generated using the WebSphere Transformation Extender Schema Importer.
• Additional validation maps used to validate the general usage rules as defined in the EPC rule books and the EBA STEP2 rule book.
• Example converter maps for the following domestic credit transfer and direct debit messages:
  • United Kingdom - BACS, see Domestic format for the United Kingdom.
  • Germany - DTAUS, see Domestic format for Germany.
  • France - MINOS and CFONB, see Domestic format for France.
  • Italy - SIA Rete Interbacarria (RNI), see Domestic format for Italy.
• WebSphere Transformation Extender type trees for the SWIFNet FIN MT 1nn message, as well as the WebSphere Transformation Extender transformation maps used to convert between SEPA formats and the SWIFTNet FIN MT101 MT102, MT102+, MT103 and MT103+ messages.
• z/OS example with sample JCL for a SEPA passthrough map. SeeRunning SEPA on z/OS.
• Reference data templates (bic.xml, and currencycodedecimals.xml files).
• Euro Banking Associations (EBA) schema based type trees.
• A bundle example that shows how to bundle SEPA data in EBA STEP2 message format.
• An example validation map that uses the European Payments Council (EPC) and the Technical Validation Subset (TVS) schemas for the relevant payments clearing and settlement messages, that use native schema mapping. These maps can be used as a replacement for the main validation maps to improve performance, since these maps use the EPC schema subset of the ISO20022 schema.