This transaction is used to import information from the SWIFT Relationship Management Application (RMA) to address static data by making direct use of the XML file provided by SWIFT. This file contains information on the BICs used to exchange messages.

The SWIFT authenticator in the addresses (more precisely, in the PTM table) is updated using information provided in the SWIFT file. In business transactions, this authenticator controls whether SWIFT messages can be exchanged with a particular addressee.

All the authenticators stored in the addresses are checked and compared with the information from the RMA file.

If there is no entry in the RMA file on the address, the authenticator is set to 'not connected'. If there is no address for an entry in the RMA file, the entry is simply ignored. In all other cases, the status contained in the RMA file is transferred to the address.

The transaction uses the status details contained in the import file. According to SWIFT RMA documentation, possible options include:

• Enabled: the authorisation is in use
• Rejected: the authorisation is not in use because it was not acceptable when it was sent by the correspondent BIC
• Revoked: the authorisation is not in use because the correspondent BIC has revoked the issuance of the authorisation
• Deleted: the authorisation is not in use because the own BIC has decided that it does not want to use this authorisation to send traffic.

If the status is 'Enabled', the authenticator in the address is set to 'authenticated'. In all other cases, the authenticator in the address is set to 'not connected'.

As we do not yet know how SWIFT RMA provides information on restricting the service to certain permitted message types, the application currently does not automatically support this information.

If the transaction is used, any other automatic import process into the SWIFT authenticator may have to be suppressed from other address interfaces.

Import