Relationship list

The relationship list displays information about and lets you manage the authorisations of your business relationships. A business relationship is established as soon as an authorisation is created for a particular combination of own BIC, correspondent BIC, and service.

1: The FTM SWIFT title bar. If the Relationship Management Application encounters an error, this area is overlaid with a message that describes the error.
2: The user ID of the current user.
3: Links to display information about the product, return to the Home screen, display help information for the current page, or log out.
4: Refresh button to retrieve the most current data from the authorisation list.
5: Filter pane to reduce the listed relationships by defining filter criteria.
6: A field that indicates the number of displayed relationships, the total number that meet the current filter criteria, and the total number viewable by the user. In addition, the number of the first displayed relationship is shown. This number can be changed to navigate to another relationship.
7: The button to create a new authorisation.
8: Buttons to navigate through the pages of the current result set. The number of displayed relationships can be changed between 20, 50 and 100.
9: Status of an authorisation. A separate line in the list is available for current and pending authorisations.

Table 1 describes the information displayed for each relationship:

Table 1. Relationship information
Column	Description
Own BIC	The BIC of your financial institution. This is the local counterpart of the authorisation¹.
Cor BIC	The BIC of the correspondent. This is the remote counterpart of the authorisation¹.
Service	The name of the SWIFT service to which the authorisation refers.
¹ If reference data is available, and if a BIC in the Own BIC or Cor BIC column is not among those listed in the reference data, that is a strong indication that the BIC might be stale. Such a BIC is flagged with the symbol.

Table 2 describes the information displayed for each authorisation:

Table 2. Authorisation information
Column	Description
Type	The type of the authorisation: toSnd An authorisation to send, that is, an authorisation that authorizes your own BIC to send messages to the correspondent BIC. toRcv An authorisation to receive, that is, an authorisation that authorizes your own BIC to receive messages from the correspondent BIC. If an authorisation is locked by a user, it is flagged with the following symbol: "lock" symbol
Auth status	The status of the authorisation. Which statuses an authorisation can have depends on its type: toSnd An authorisation to send can have one of the following statuses: PendAcc You received an authorisation to send (or an update for an authorisation to send) but have not yet accepted or rejected it. Enabled You accepted the authorisation to send and it is now active. Revoked The authorisation to send is inactive because the correspondent revoked it. Deleted The authorisation to send is inactive because you deleted it. PendDel The delete operation is pending. toRcv An authorisation to receive can have one of the following statuses: Enabled The authorisation to receive is active. Revoked The authorisation to receive is inactive because you revoked it. PendDel The delete operation is pending.
Validity start	The date from which the authorisation is valid.
Validity end	The date up to which the authorisation is valid.
Permissions	The symbol in this column indicates whether permissions are set for the authorisation: Permissions are set for this authorisation. Permissions are set for this authorisation. Changes are pending for this authorisation, and changes to its permissions are among the pending changes.
Proc status	The processing status of the authorisation. Depending on the type of authorisation, this can be one of: Imported authorisation indicator The following symbols apply to imported authorisations: The current version of the authorisation was imported into RMA from a distributed Relationship Management Application. For an authorisation for the swift.fin!p service, one or both master BICs have not yet been specified. Change status For the pending version of an authorisation, the processing status is the change status: Draft The authorisation was saved as a draft, but not yet submitted. PendApp1 The pending version requires approval by a relationship approver. PendApp2 The pending version was approved, but requires additional approval by a second relationship approver. Refused The pending version was refused by a relationship approver.