Enabling MX compliance checking on Sterling B2B Integrator

If a WebSphere Transformation Extender map is specified in the SWIFT envelope, the specified map is used only for translation. Compliance checking is handled separately. This documentation provided here describes how to enable the pack’s MX validation for the Generic Enveloping and Generic Deenveloping services.
  1. On the SWIFT envelope, set the attribute, Compliance Check message to Yes.
  2. Set the attribute, Use WebSphere Transformation Extender compliance checking to Yes.
  3. Set the WebSphere Transformation Extender compliance checking options, based upon your preferences:
    • Validate BIC addresses
    • Validate IBAN data
    • Validate currency codes
    • Validate amount and the number of decimal digits
    • Validate country codes
    Note: Validation for BIC, currency, and country codes are made against the Sterling SWIFT code lists. If the default SWIFT code lists versions have zero entries, the validation defaults against the following repository files that come with the SWIFT components: bic.xml and currencycodedecimals.xml