RMA in banking stands for Relationship Management Application, SWIFT’s mandatory filter that lets a financial institution control which counterparties are allowed to send it messages over the SWIFT network.1Swift. Information Paper RMA and RMA Plus: Managing Your Correspondent Connections Introduced in 2009 as a replacement for the older Bilateral Key Exchange system, it works like a whitelist: if your bank hasn’t granted a specific institution permission, that institution’s messages never reach your processing systems. RMA is required for most SWIFT FIN messages that carry an end-to-end signature, which covers the vast majority of interbank payment traffic.
How the Filter Works
RMA sits between the SWIFT network and a bank’s core systems. When another institution sends a FIN message, the network checks whether a valid authorization exists between sender and receiver. If none is in place, the message is blocked at the sender level before it ever touches the receiving bank’s infrastructure.2Swift. RMA and RMA Plus: Managing Correspondent Connections Unwanted traffic is stopped before it can create operational risk or trigger fraudulent processing.
The system is strictly bilateral. Both institutions must independently agree to exchange messages. Neither side can force a connection, and both must actively confirm the relationship before any traffic flows. That mutual consent is what ties RMA directly to compliance obligations. The Wolfsberg Group recommends that institutions fold RMA due diligence into their broader financial crime, anti-money-laundering, and know-your-customer programs.1Swift. Information Paper RMA and RMA Plus: Managing Your Correspondent Connections
In practice, each authorization is a relationship decision, not an IT configuration task. Compliance teams weigh the counterparty’s risk profile, sanctions exposure, and internal risk appetite before granting access.
Standard RMA Versus RMA Plus
Standard RMA lets you decide which institutions can send you messages. Once you authorize a counterparty, they can send you any FIN message type your system supports.
RMA Plus narrows that aperture. It lets you specify exactly which message types each counterparty can send and receive.1Swift. Information Paper RMA and RMA Plus: Managing Your Correspondent Connections A bank might authorize a particular correspondent only for letters of credit while blocking payment instructions entirely. The practical effect: a compromised or rogue counterparty can only send the specific transaction types you’ve pre-approved. For banks with hundreds or thousands of correspondent relationships, that boundary is enforced at the network level rather than relying on internal controls to catch misrouted messages later.
What You Need to Set Up an Authorization
The Counterparty’s BIC
Every SWIFT-connected institution has a Business Identifier Code, either eight or eleven characters long, that serves as its unique address on the network.3Nasdaq CSD. Guidelines of Establishing RMA With Nasdaq CSD The eight-character version identifies the institution; the eleven-character version pinpoints a specific branch. BICs are published in the SWIFT Directory. Getting this code right is non-negotiable, because an incorrect BIC sends the authorization request to the wrong entity or fails outright.
Message Scope
You need to decide which categories of messages the relationship will cover. For legacy FIN messaging, most banks work with MT 1xx for customer payment transfers and MT 2xx for transfers between financial institutions, with Category 9 messages added where account statements and cash management reporting are involved.4SWIFT. SWIFT Compatible Application – Payments – Label Criteria 2022 With SWIFT’s migration to ISO 20022, your authorization also needs to cover the newer, data-rich structured formats you and your counterparty actually use.5Swift. ISO 20022: Standards
KYC Review
Before activating any authorization, compliance officers should review the counterparty’s profile in SWIFT’s KYC Registry. The registry collects standardized data from participating institutions, including proof of regulatory status, ownership structure, ultimate beneficial owner declarations, anti-money-laundering policies, and tax compliance documentation such as FATCA forms. This is where most institutions catch red flags. A bank that looks clean on paper but has opaque ownership or weak AML controls may not be worth the correspondent relationship.
The Authorization Exchange
The exchange follows a straightforward sequence. The initiating bank sends an authorization request through its SWIFT interface, specifying the counterparty’s BIC and the message categories or types being requested. The request travels across the SWIFT network and appears as a pending item in the counterparty’s RMA management portal.
The receiving institution reviews it against its own compliance findings and operational needs. If everything checks out, the counterparty accepts, and the system creates a reciprocal authorization linking both parties. This digital handshake generates an audit trail documenting when the relationship was established, by whom, and with what scope.2Swift. RMA and RMA Plus: Managing Correspondent Connections Once both sides confirm, the authorization flips to active, and live messaging can begin almost immediately.
If the receiving bank rejects the request, the initiator gets a notification and needs to resolve whatever compliance or data issue triggered it before trying again. Rejections aren’t unusual, especially when the requesting institution is unfamiliar or operates in a higher-risk jurisdiction.
What the ISO 20022 Migration Changed
SWIFT’s transition from legacy MT messages to the ISO 20022 standard has direct consequences for how banks configure RMA. The coexistence period for cross-border payment instructions ended on November 22, 2025, meaning all interbank payment instructions must now be exchanged in ISO 20022 format.6Swift. ISO 20022 for Financial Institutions: Navigating the End of Coexistence
Several legacy MT message types have been permanently retired. MT 102, MT 102 STP, MT 103 REMIT, MT 201, and MT 203 were all decommissioned as of November 2025 and are rejected by the network if sent.7Swift. CBPR+ Roadmap Beyond November 2025 An authorization that only permits legacy MT 102 traffic is now useless. Banks that still send MT messages where ISO 20022 equivalents exist will have those messages automatically converted by SWIFT’s contingency processing service, but conversion charges apply as of January 2026.6Swift. ISO 20022 for Financial Institutions: Navigating the End of Coexistence If you haven’t updated your RMA profiles to reflect ISO 20022 message types, you’re either paying conversion fees or failing to exchange messages at all.
Keeping Authorizations Current
Modifying What’s Already in Place
Relationships evolve, and permissions have to keep pace. Adding or removing specific message categories or ISO 20022 types requires updating the authorization through the SWIFT interface. Because the system is bilateral, changes need a fresh exchange so both parties stay in sync. A unilateral change on one side without the counterparty’s corresponding update creates a mismatch that will block legitimate traffic.
Periodic Reviews
Dormant authorizations are one of the most underappreciated risks in correspondent banking. A legacy RMA sitting untouched for years still provides a live channel into your bank’s systems, and that channel could be exploited if the counterparty’s security posture has deteriorated or the institution has since been sanctioned.1Swift. Information Paper RMA and RMA Plus: Managing Your Correspondent Connections SWIFT offers a usage review service that provides traffic data covering the prior twelve months, helping banks identify authorizations where no messages have actually been exchanged.8Swift. RMA Usage Review and Removal Service The Wolfsberg Group recommends folding these reviews into the broader customer due diligence cycle on a risk-based schedule rather than letting authorizations sit indefinitely.
Stopping or Deleting
When a relationship ends, the authorization must be formally terminated. SWIFT provides two options: a “stop” action suspends message traffic while preserving the authorization record, and a “delete” action removes the record entirely.2Swift. RMA and RMA Plus: Managing Correspondent Connections Both take effect immediately. Any messages sent by the former counterparty after revocation are automatically rejected. The choice depends on whether the bank anticipates resuming the relationship later; if not, deletion is the cleaner option.
Bootstrap Records
Bootstrap records are authorizations created locally without an exchange over the SWIFT network.9Swift. Swift Compatible Interface RMA Interface Conformance Statement They exist to support initial setup and migration scenarios, but they bypass the bilateral handshake that makes RMA trustworthy in the first place. A bootstrap authorization that lingers past its intended purpose creates an unvetted pathway into the bank’s messaging environment. Cleaning these out belongs in every periodic review.
SWIFT’s own guidance on new requests is blunt: approval needs to be appropriately controlled, and each authorization should be treated as a compliance event, not a routine IT task.1Swift. Information Paper RMA and RMA Plus: Managing Your Correspondent Connections The banks that get burned tend to be the ones that treat RMA management as an operations function disconnected from compliance oversight.