SWIFT MT & ISO 20022 Standards Compliance
Six layers of standards checking
Structure Validation
Verifies mandatory sequences and fields are present, correctly ordered, and within allowed repetition limits. Detects missing blocks, invalid sequence nesting, and structural errors.
Format & Field Validation
Checks each field against its format specification: mandatory components, allowed character sets, maximum lengths, valid qualifiers, and option letter constraints.
Semantic Rules
Applies the full set of SWIFT network validation rules: cross-field dependencies, conditional requirements, and business logic constraints specific to each message type.
Reference Data
Validates BIC codes against the SWIFT BIC directory, loaded with the BICImport tool. Checks IBAN structure and check digits, ISO country and currency codes, and SWIFTRef data: IBAN Plus, Participants, LEI, SSI, BIC Plus, and national ID directories.
Usage Guidelines
For MX messages, validates against market practice usage guidelines: CBPR+ schemas, regional clearing rules, and restricted code sets that go beyond base ISO 20022 schemas.
Custom Rules
Add your own institution-specific validation rules on top of the standard checks. Enforce internal policies, counterparty-specific requirements, or additional business constraints.
MT Message Validation
MX Message Validation
CBPR+ and regional clearing compliance
ISO 20022 usage guidelines add market-practice restrictions on top of the base schemas. The most significant is CBPR+, which governs ISO 20022 payment messages on the SWIFT network. Prowide validates against the latest CBPR+ version.
Regional clearings define their own MX usage guidelines, each with specific schema restrictions, code sets, and field rules. Prowide supports validation for 15+ regional clearings. Translators per clearing are listed on the ISO 20022 migration page.
CBPR+ Payment Messages
Restricted schemas and usage rules for pacs.008, pacs.009, pacs.004, camt.056, and other CBPR+ message types.
Regional Clearing Guidelines
T2, LYNX, CHATS, RITS, MEPS+/SCRIPS, FISC, EBA, Fedwire, SIC, and more, each with their own MX flavors and rules.
Translation Compliance
When translating between MT and MX, the output is validated against the target format's usage guidelines as well as the base schema.
Intelligent Variant Detection
Automatic detection of which usage guideline applies to a given message, based on the message context and clearing destination.
Compliance enforced in the flow, not reported after the fact
In the Messaging Hub, validation is an action in the ECA workflow engine. It runs on outbound messages before they reach the dispatcher and on inbound messages as they arrive.
Messages that fail are held rather than delivered. Each is tagged with the rules it broke and routed to a review queue in the operator GUI. Operators see the specific errors and repair the message in place, with field-level validation guiding the correction.
Every outcome lands in the message audit trail, under role-based permissions and 4-eyes authorization where you require it.
Validated before delivery
Outbound messages are checked before the dispatcher sends them, so you avoid the repair cycle and delayed settlement a rejection causes.
Checked on arrival
Inbound messages are validated as they enter, so malformed counterparty traffic is caught before it reaches your back-office systems.
Policy per flow
Choose block-and-queue or warn-and-continue per message flow, with dry-run testing before rules go live.
Auditable end to end
Validation results, repairs, and releases recorded in the message audit trail with role-based access and 4-eyes authorization.
Orchestrating your AML and sanctions screening
Prowide validates messages against standards. It does not run AML, sanctions, or PEP screening, and it does not maintain watchlists or name-matching algorithms. Your screening platform owns that decision.
The Messaging Hub runs the workflow around it. Screening is a step in the ECA workflow engine, using the same condition filters as your routing: BIC patterns, message types, currencies, amount ranges, and field-level matching. The Hub calls the screening system, parks the message until a verdict comes back, and routes on the outcome. Rules can be tested with dry-run mode before activation.
The outcome lands in the same message record and audit trail as validation, with one operator inbox.
Message reaches the screening step
ECA conditions select which messages are screened, by direction, message type, counterparty BIC, currency, amount threshold, or any field-level criteria
External screening system is called
A Custom Action invokes your AML platform over whichever interface the vendor exposes
Message is held pending the verdict
Nothing leaves the institution while screening is outstanding
Routing follows the outcome
Clear results continue to delivery. Hits and inconclusive results go to a review queue in the operator GUI
Compliance officer decides
Release, reject, or repair from the Hub UI, under role-based permissions and 4-eyes authorization, with every action audited
Owns the screening decision
Owns the message workflow around it
Yearly SRG updates, delivered before you need them
SWIFT publishes a new Standards Release Guide (SRG) every year, typically with a November go-live date. Each SRG can add semantic rules, modify validations, introduce message types, and update code sets.
Building this validation in-house can take 6-12 months of development, and every SRG restarts the cycle. With Prowide, the update arrives as a library update with new rules and updated reference data included.
Prowide delivers SRG updates 6 months before the go-live date, so your team can integrate, test, and certify before the changes take effect on the network.
SWIFT publishes SRG specification
New rules, modified validations, updated code sets, and message changes are documented
Prowide implements and tests
Full rule implementation with regression testing across all message categories
Early release delivered (6 months ahead)
Updated library available for integration and testing in your environment
Your team integrates and certifies
Deploy the update through your standard change management process
SRG goes live on SWIFT network
Your validation engine is already current
Available in Integrator and Messaging Hub
Prowide Integrator
The Validation module is a Java library that you integrate into your own applications. Call the validation engine from your code, get structured results, and handle errors in your own way.
Prowide Messaging Hub
Validation runs automatically on every message flowing through the Hub -- outbound messages are validated before delivery, inbound messages are checked on arrival. Non-compliant messages are flagged for operator review.