The Validation module adds the capability to validate that an MT or MX message is SWIFT standard compliant.
- Implements all SWIFT format validations rules, including semantics (network rules).
- Validates all message categories in the MT (ISO 15022) and MX (ISO 20022) standards.
- Includes BICs and country codes validations.
- Supports custom rules, it can thus be tailored to fit specific user groups restrictions as MA-CUGs or RTGS.
- Reduces costs, preventing NAKs and rejections.
Validate a message is as simple as instantiating the validation engine, pass the message to validate and verify the result list of validation problems. If the resulting list is empty the message is SWIFT standard compliant. This direct and default procedure can satisfy most of the validation usage scenarios.
The engine can be then twiked for performance or to support custom constraints and validation exceptions.
For each validation problem found, the SWIFT error code is provided (when available), the specific part of the message where the error is found (the MT field or the xpath in the MX), and the business-oriented description of the issue.
Out of-the-box error descriptions are included in English, Spanish, Italian and Russian.
Prowide Integrator includes the BICImport tool which enables to import a BIC text file from SWIFT's directory into an internal database. This database is then used by Integrator to check the existence of BICs while validating messages.
Latest SRU support
An yearly update is provided 6 months in advance of the SWIFT Standard Release go live date. Therefore, the module guarantees that applications build on top of it are always up to date when standards change.
The validation rules are classified in four groups and the engine will pass the message for each of the groups in a specific order: structure, fields, semantic and custom.
The process can be configured to return all errors, or for greater performance, to stop at the first error found. The configuration also allows bypassing specific rules.