Extended Validation of MX Messages
Extended, or non-schema validation, ensures that SWIFT MT and MX messages comply with SWIFT Standards. Use
SWIFT Module to perform extended validation when the XML schema does not validate the document completely. To perform non-schema validation on an MX message, run the
wm.unifi.validation:validateMXMsg service in
Designer.
You can also perform individual validation tasks, such as BIC validation, or IBAN validation only.
![*](icon_task_xpe.png)
To perform an individual validation task
1. Start Integration Server and Designer.
3. In Designer, run the SWIFT Module built-in service that performs the individual validation task you want as follows:
Run this service... | To validate that... |
| The following data types exist in the BIC directory (ISO 9362) on SWIFTNet: ![*](chapterTOC_bullet.png) XML elements of type BIC (data type: BICIdentifier) ![*](chapterTOC_bullet.png) XML elements of type BIC or BEI (data type: AnyBICIdentifier). |
| XML elements of type BEI (data type: BEIIdentifier) exist in the BEI list on SWIFTNet. |
| The following data types exist in Currency Code ISO 4217: ![*](chapterTOC_bullet.png) XML elements of type ActiveCurrency (data type: ActiveCurrencyCode) ![*](chapterTOC_bullet.png) XML elements of type ActiveOrHistoricCurrency (Data type: ActiveOrHistoricCurrencyCode). ![*](chapterTOC_bullet.png) XML elements containing an amount and a currency (Data type: ActiveCurrencyAndAmount and ActiveOrHistoricCurrencyAndAmount). Also verifies that the number of digits in the amount is as specified by ISO 4217 for that specific currency. |
| Country codes (data type: CountryCode) exist in ISO 3166. |
| IBAN identifiers (data type: IBANIdentifier) match the IBAN structure as specified by ISO 13616 (which contains the country code, the specified number of digits, and the basic bank account number). |