Troubleshooting
Problem
Customer site has an issue with the network validation service wm.fin.doc.nov15.cat3:MT300NetworkValidationRules, specifically for the SWIFT MT300 messages.
The network validation service wm.fin.doc.nov15.cat3:MT300NetworkValidationRules doesn't seem to be working as expected.
Customer site not sure if this service has all the network validation rules as defined/specified in the SWIFT User handbook.
Not sure if they've been implemented or not, but while testing MT300 messages they found one of the fields of MT300 message (i.e. Field "22C: Common Reference") is not getting validated against the network validation rules as defined/specified in the SWIFT User handbook.
According the SWIFT’s User handbook, below are the network validated rules for field 22C:
(Error code(s): T95) -- This field consists of the party prefix and party suffix (from the ISO Business Identifier Code) of both the
Sender and the Receiver of the MT 300.
(Error code(s): T96) -- These codes must appear in alphabetical order (letters take precedence over numbers).
(Error code(s): T22) -- Party Suffix 1 and Party Prefix 2 are separated by four digits, which must consist of the rightmost non-zero
digit of field 36 in sequence B, preceded by the three digits to the left of it. If there are no digits to the left of it,
the space must be zero filled .
Customer site uses SWIFT’s several message categories like category1, category2, category3, category5 and category 9 and they're wanting to know if all the network validation rules have been implemented for all other messages types or categories as defined/specified in the SWIFT User handbook.
Also, they would like to understand if there is any way to find out if all the network rules, according to SWIFT’s User handbook , have been covered/implemented or not.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
19 March 2025
UID
ibm17191853