Potential Issues
Examples of issues we have encountered during Live testing
Inboud MX to MT has can cause truncated data
When translating inbound MX (ISO 20022) to MT (SWIFT FIN format), some MX fields are larger than what MT allows. As a result, certain data gets truncated. TIP (Translation integration Platform) generates a truncation report within the translated inbound MT message.
MT103 - field 57D mapping to
Clearing System & Creditor Agent Account in pacs.008
Field 57D (Routing Code) in MT messages is mapped differently in MX based on its format.
e.g. If field 57D starts with //FW (fedwire) + 9 (member ID) digits, it gets mapped to the clearing system ID (USABA) and Member ID.
If field 57D starts with / + 9 digits member ID, it gets mapped to the creditor agent’s account.
Upgrade to SAA 7.7.50 to avoid time stamp validation error
During MT to MX translation, time stamps i.e. CRTDT is taken from server and populated in the MX.
MX definition specified milli seconds to 3 decimal places. However, SAA 7.6.x has known issue were
MX mail fails validation for messages intercepted for authorization. Therefore, it is highly recommended
to upgrade to SAA 7.7 to support ISO20022 program.
SttlmAcct translation to field 53B
Testing Settlement Method to 53B, please be aware of the subtle difference between INGA and INDA.
Services
Request Live demo
© 2025. powered by Netlink Testlabs.
Swift Vendor Certifications
Operational Swift ITB Stack
Swift Alliance Access + AMH
Swift Alliance Cloud Enablement
Swift Preval API
Swift Essentials
Swift Business Connect
ACV - Alliance Cloud Virtual
HSM IS6 to SA7 Migration
IS6 to SA7
SAA 7.7.50 Upgrade