Using SWIFTNet

Edit online

Sterling B2B Integrator supports the use of Society for Worldwide Interbank Financial Telecommunications (SWIFT), a standard for the financial industry from SWIFT™ that uses the SWIFTNet transport protocol to enable real-time store-and-forward financial messaging through the InterAct and FileAct file protocols.

The SWIFT standards data dictionary is optionally installed from the Deployment > Standards page. It supports all SWIFT Standards Release messages loaded in the standards database. The SWIFT standards data dictionary also contains the special exception and code word validations, and the codes words and qualifiers necessary for the validation of the ISO 15022 messages (500 series). This information is used to automatically generate the translator_swift.properties.in file, which is used by the translator to perform the validations.

Note: You can create a map for all SWIFT Standards Release messages through the IBM® Sterling B2B Integrator Map Editor. All messages are validated by the Sterling B2B Integrator for syntax (that is, field types, field lengths, and so forth). All SWIFT message are validated for syntax and semantics.

The following messages are supported with both inbound and outbound syntax validation and semantic validation (that is, validating the message rules) of the messages between the Sterling B2B Integrator and SWIFT:

  • All SWIFT 2005 message types
  • All SWIFT 2006 message types
  • All SWIFT 2007 message types
  • All SWIFT 2008 message types
  • All SWIFT 2009 message types
  • All SWIFT 2010 message types
  • All SWIFT 2011 message types
  • All SWIFT 2012 message types
  • All SWIFT system messages (Category 0 messages)
  • SWIFT MX Funds (versions 3.0, 4.0, 4.1, and 4.4) and Funds Rulebook (version 4.0, 4.1, and 4.4)
  • SWIFT MX Alternative Funds (version 4.1) and Alternative Funds Rulebook (version 4.1)
  • SWIFT MX Fund Processing Passport (versions 4.2 and 4.3) and Funds Rulebook (versions 4.2 and 4.3)
  • SWIFT MX Cash Reporting (versions 1.0, 3.0, 3.1, 3.2, 4.0, and 5.0) and the Cash Reporting Rulebook (versions 3.1, 4.0, and 5.0)
  • SWIFT MX Cash Management version 4.0 (Standards Release November 2008) and 4.0 (Standards Release July 2009)
  • SWIFT MX Transaction Reporting (version 1.0)
  • FpML (version 1.0)
  • SWIFT MX Exceptions & Investigations (versions 1.0, 1.1, and 1.2)
  • SWIFT MX Trade Services (versions 1.0 and 2.0)
  • SWIFT MX Bulk Payments (versions 2.0 and 2.1)
  • SWIFT SCORE (versions 2.0, 2.5, and 2.6)
  • SWIFT Proxy Voting (versions 1.0, 1.1, and 1.2)
  • SWIFT MX eMandate (version 1.0)
  • SWIFT MX Corporate Actions (versions 1.0, 1.1, and 1.2)
  • SWIFT MX Collateral Management (version 1.0)
  • SWIFT MX Clearing (versions 1.0 and 2.0)
  • SWIFT MX SCORE (versions 2.5 and 2.6)
  • ISO 20022 messages
  • MQHA Delivery Notification Reconciliation
  • ISO 20022 Basic Application Header
  • XML Format 2 Header (version 2.0.3)

Additionally, the Sterling B2B Integrator allows you to create maps to support the translation of market practices, and provides the following two Market Practices:

  • Germany: MT515: Trade Confirmation (Broker to Asset Manager)
  • United States: MT536: ISITC-IOA: Statement of Transactions

For Market Practices, the SWIFT standard validations are performed unless the Market Practice has customized a particular validation (for example, restricting a code word validation list). Market Practice code word and qualifier validations are maintained in property files separate from the SWIFT standard property files. By keeping the Market Practices you create separate, we can deliver updates to the SWIFT standard without overwriting your custom-implemented Market Practices. Similarly, semantic validation rules for Market Practices are stored in an extended rule library separate from the library that implements the SWIFT standard semantic validation rules. Please note that the standard property files and semantic validation rules are used when the implemented Market Practice does not override them.

Sterling B2B Integrator also supports and maintains SWIFT System Messages (MT category 0; for example, MT096 FIN Copy to Server Destination Message) which relate to the sending or receiving of messages used to customize your FIN operating environment, including SWIFT user-to-user messages (MT categories 1-9), User-to-SWIFT messages (for example, Delivery Notifications, Retrievals, and so forth), and SWIFT-to-user messages (for example, Retrieved Messages, Non-Delivery Warnings, and so forth).

In addition, support for SWIFT requires you to create inbound and outbound SWIFT envelopes. You must also create a business process or processes to order the flow of the Sterling B2B Integrator activities so you can accomplish your business objectives with SWIFT.

For more information on the SWIFT standard, access this web site:

http://www.swift.com