SWIFTNet Syntax Validation

SWIFT field tag syntax validation is defined in the Sterling B2B Integrator Map Editor and stored in the translator_swift_<year>.properties file. This properties file contains the validation syntax for the field tags, as defined by the SWIFT standards (for example, field 73 is 35x[‘CRLF'35x]0-5), and may not be edited. The validation syntax for any given record is displayed in the Field Syntax parameter on the SWIFT Record Properties dialog box (SWIFT Validation tab). This parameter is automatically populated when you create a map using the SWIFTNet standards data dictionary. The convention of the syntax conforms exactly to the SWIFT documentation.

SWIFT also uses special validation functions such as <CUR>, <SWIFTBIC>, and <NON-SWIFTBIC>, which are components of a field tag. Each of these special functions has an expanded syntax that is validated by the translator. When these special validation functions are used, the special function syntax is displayed in the Field Syntax text box on the SWIFT Record Properties dialog box. The currency (<CUR>) and sender/receiver addresses (<SWIFTBIC>, <NON-SWIFTBIC>) must also be validated against legal code word lists. These code lists are defined in the SWIFT standards data dictionary and used by the Sterling B2B Integrator.

If WebSphere® Transformation Extender is installed and integrated with Sterling B2B Integrator, you also have the option of using WebSphere Transformation Extender for the translation and compliance checking of WebSphere Transformation Extender maps.