In banking, RMA stands for Relationship Management Application, a filtering service built into the SWIFT network that lets a bank control which other financial institutions are allowed to send it messages. Before any payment instruction, trade finance document, or other SWIFT message reaches the receiving bank, RMA checks whether the sender has been pre-approved. If there is no active authorization in place, the message is rejected at the SWIFT gateway before it ever touches the bank’s back-office systems.
What RMA Does on the SWIFT Network
SWIFT connects thousands of financial institutions, and without a filter any member could send messages to any other member. That would open the door to unsolicited instructions capable of triggering automated fund transfers or overwhelming clearing systems. RMA closes that door by requiring bilateral consent before two institutions exchange traffic. Each bank defines exactly which counterparties have permission to send it messages, and the SWIFT gateway enforces those rules automatically.1Swift. RMA and RMA Plus: Managing Correspondent Connections
Two things follow from that design. Compliance teams do not have to screen every inbound transmission by hand, because unauthorized messages never arrive. And every incoming instruction is tied to a verifiable record showing both parties agreed to communicate, which gives auditors a clean trail back to an approved relationship.
SWIFT’s Customer Security Controls Framework also requires that the data flowing between the RMA application and the messaging interface be protected for confidentiality, integrity, and mutual authentication, which guards against scenarios where someone tries to spoof headers or inject instructions into the data flow between SWIFT components.2SWIFT Knowledge Centre. Swift Customer Security Controls Framework v2024 Detailed Description
What a Bank Controls With an RMA Authorization
An RMA authorization is not a blanket “yes.” SWIFT organizes financial messages into numbered categories (Categories 1 through 9), each covering a different type of transaction. Category 1 handles customer payments and checks. Category 7 covers documentary credits and guarantees.3SWIFT. Category 7 – Documentary Credits and Guarantees For Standards MT November 2023 – Message Reference Guide When two banks set up an RMA, they choose which categories to open with each other.
A bank might authorize Category 1 messages with a counterparty for payment processing while blocking Category 7 if it does not handle trade finance with that institution. The point is to prevent the bank from receiving instructions its back-office software is not set up to process, which could otherwise cause errors, delays, or unintended financial exposure.
Banks can also grant temporary test-message permissions so counterparties can verify software integrations without moving real funds or triggering regulatory reporting. Those test authorizations stay isolated from financial ledger systems.
RMA Plus for Finer Control
Standard RMA filters at the category level. RMA Plus goes further and lets a bank approve or block individual message types within a category. A bank could permit one specific payment notification message type, for example, while blocking others in the same category.1Swift. RMA and RMA Plus: Managing Correspondent Connections That granularity is useful for institutions operating in specialized markets, such as trade finance or securities settlement, where only a narrow set of message types is relevant.
How Two Banks Open an RMA Connection
Nothing technical happens first. The institution’s compliance department runs due diligence under anti-money laundering and know-your-customer rules: verifying the counterparty’s identity, screening the name against sanctions and watchlists, and assessing the risk profile of the proposed relationship. In the United States, this work also satisfies obligations under the Bank Secrecy Act.
At a minimum, the bank collects the counterparty’s name, address, and SWIFT Business Identifier Code (BIC), then reviews ownership structure and the regulatory environment of the institution’s home jurisdiction. SWIFT’s KYC Registry centralizes much of this information so banks are not relying solely on documents exchanged bilaterally.4Central Bank of the UAE (CBUAE). Annex 4: SWIFT and Non-Customer RMA Relationships
Once compliance signs off and a correspondent banking agreement is in place, the technical team sends a digital authorization request through the bank’s SWIFT interface, selecting the message categories it wants to exchange and transmitting the request to the counterparty’s BIC.5IBM. SWIFTNet Import RMA Service The receiving institution reviews the request through its own SWIFT console and decides whether to accept, modify, or reject the proposed terms. If accepted, SWIFT records the bilateral agreement and updates routing permissions so messages can flow between the two banks.
Keeping RMA Authorizations Clean
An RMA is not a set-it-and-forget-it arrangement. SWIFT defines an inactive authorization as one where no traffic has been exchanged in the last 12 months, and it offers an RMA Usage Review service that gives banks a comprehensive file listing all counterparties, the volume and direction of traffic, and when the last transaction occurred.6SWIFT. RMA Usage Review and Removal Service
Dormant connections are a security concern because they are approved pathways no one is actively watching. If a dormant counterparty’s systems are compromised, the unused RMA could become a channel for fraudulent messages. Regular pruning of inactive authorizations is treated as a baseline practice for reducing operational and compliance risk.
Some terminations are not optional. Under U.S. law, a bank that receives written notice from the Secretary of the Treasury or the Attorney General directing it to terminate a correspondent relationship with a foreign bank must close the accounts within 10 business days.7Federal Reserve. Summons or Subpoena of Foreign Bank Records; Termination of Correspondent Relationship
Why Regulators Care About RMA
RMA records are part of the broader correspondent banking compliance framework, not a standalone IT setting. The FFIEC requires banks to apply ongoing, risk-based procedures to each foreign correspondent account, designed to detect and report suspected money laundering and to include periodic reviews confirming that account activity is consistent with the stated purpose of the relationship.8FFIEC. Due Diligence Programs for Correspondent Accounts for Foreign Financial Institutions
Review frequency scales with risk. Higher-risk correspondent accounts, such as those in jurisdictions with weaker anti-money laundering regimes, warrant more frequent and thorough review. Examiners evaluate whether a bank’s policies, procedures, and internal controls are adequate and may request independent testing or audit reports.9FFIEC BSA/AML InfoBase. Assessing Compliance with BSA Regulatory Requirements – Due Diligence Programs for Correspondent Accounts for Foreign Financial Institutions Banks that cannot show adequate documentation or monitoring face regulatory criticism and potential enforcement, which is why RMA record-keeping is treated as a compliance priority rather than a back-office housekeeping task.