Validation
ISO 20022 and MT compliance validator - All semantic rules prevent NAKs before transmission
Checks that an MT or ISO 20022 message is standard compliant.
What's included?
- SWIFT format validation rules, including message structure, fields and semantics (network rules)
- Validation for all message categories in the MT (ISO 15022) and MX (ISO 20022) standards
- BICs and IBAN validation
- ACK/NAK generation
- MX (ISO 20022) cross-element and externalized ISO codes validation
- CBPR+ schemas and UG validation
- SCORE SWIFT for corporates validation for MT798 subtypes
- Support for custom rules and custom XSD schemas
A secure choice to reduce costs by preventing NAKs and rejections, and to reduce efforts in your yearly standards maintenance.
Main Features
Simple API
Validating a message is as simple as instantiating the validation engine, passing the message to validate and verifying 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 validation usage scenarios.
The engine can then be tweaked for performance or to support custom constraints and validation exceptions.
Multilanguage
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.
BIC validation
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.
Why Choose Prowide Validation?
Prevent costly payment rejections with pre-transmission compliance verification
Eliminate NAK Rejections: Catch SWIFT network validation failures before transmission. Reduce rejection-related costs by 90% and avoid correspondent bank fees.
99.9%+ Accuracy: Updatable BIC directory, and yearly SWIFT rulebook releases ensure validation against current network standards. No stale reference data.
Real-Time Verification: Sub-second validation response for message structure and cross-field logic. Integrate into payment workflows without latency impact.
Reduce Manual Review: Automated compliance checks eliminate repetitive operations staff verification. Free teams to focus on exception handling and customer service. Streamline STP flows.
Comprehensive Coverage: Structure validation, network validation rules, SWIFT-specific field constraints, and cross-field dependencies. Single validation call replaces multiple in-house checks.
Audit Confidence: Detailed validation reports provide evidence trail for compliance audits. Demonstrate due diligence in payment processing controls.
Frequently Asked Questions
What is the Prowide Integrator Validation module?
Component of Prowide Integrator that validates MT and MX messages for SWIFT compliance: structure, fields, semantics, BICs, IBANs. Generates ACK/NAK. Not sold separately.
Can I purchase the Validation module separately?
No. Part of Prowide Integrator single license with SDK, Translations, and MyFormat.
What validation rules are covered?
Structure, field formats, semantic rules (network validation), BIC/IBAN, MX cross-element validation, ISO codes, CBPR+ schemas/UG, SCORE MT798 subtypes. Custom rules and XSD schemas supported.
Does validation support multiple languages?
Yes. Error descriptions in English, Spanish, Italian, Russian. Each error includes SWIFT code, message location (MT field/MX xpath), and business description.
How does BIC validation work?
BICImport tool imports SWIFT BIC directory into internal database. Validation engine checks BICs against this database for existence and validity.
How is the validation module kept current with SWIFT standards?
Yearly SRU updates delivered 6 months before go-live. Prevents NAKs and rejections from standard changes.
What's the cost of building validation in-house vs licensing?
In-house validation requires reverse-engineering SWIFT standards documentation and implementing hundreds of semantic rules per message category. This typically takes 6-12 months of development time, plus ongoing maintenance for yearly SRU updates. Licensing provides production-ready validation maintained by domain experts, allowing your team to focus on business logic instead of standards compliance.
Technical Specifications
Requirements
- Part of: Prowide Integrator
- Java: 11 or higher (any distribution)
- Standards: ISO 15022, ISO 20022
- Database: Optional (for BIC directory)
Validation Coverage
- Structure validation (all MT/MX)
- Field format validation
- Semantic rules (network validation)
- BIC and IBAN validation
- CBPR+ schemas and usage guidelines
- SCORE (MT798 subtypes)
Key Features
- ACK/NAK generation
- Custom validation rules support
- Custom XSD schemas support
- Multilingual error messages (EN, ES, IT, RU)
- Configurable validation pipeline
- SWIFT error codes included
Updates & Maintenance
- SRU Updates: Yearly, 6 months in advance
- Included in: Integrator maintenance
- License: Single Integrator license
- Support: Professional assistance available