pacs.009

pacs.009 is the ISO 20022 message called the Financial Institution Credit Transfer. One financial institution sends it to another, directly or through a payment system, to move funds where the debtor and creditor are themselves financial institutions. Banks use it to settle foreign exchange and money market deals, transfer liquidity between their own accounts, fund nostro accounts and, in a special form, to move the funds behind a customer payment. In SWIFT cross-border traffic it replaces the MT202 general financial institution transfer and the MT202 COV.

The message belongs to the "pacs" business area of ISO 20022. It is the bank-to-bank counterpart of pacs.008, which carries payments for customers, and its status can be reported with a pacs.002. It is one of the main MX messages in correspondent banking.

Common uses include:

• Treasury settlement. Paying the proceeds of foreign exchange trades, interbank loans and deposits, and other deals between banks, often priced at an interbank rate.
• Liquidity management. Moving funds between a bank's accounts at different correspondents or central banks to cover expected payments, part of managing intraday liquidity.
• Cover payments. Moving the funds that settle a customer payment when the customer's details are sent separately in a pacs.008.
• RTGS transfers. Interbank payments between participants in real-time gross settlement systems such as the US Fedwire Funds Service, CHAPS and T2.

Under SWIFT's cross-border usage guidelines, pacs.009 is used in more than one form. The core form is a straightforward bank-to-bank transfer, equivalent to the MT202. The COV form is used for cover payments and contains an extra block, the underlying customer credit transfer, which carries key details of the original customer payment, including the debtor, the creditor and their agents.

The COV form exists because of transparency concerns. In the past, banks sometimes sent a customer payment's details directly to the beneficiary's bank while moving the funds through correspondents with an MT202 that named only the banks involved. The correspondents in the middle could not see who the real payer and payee were, which made sanctions screening and anti-money laundering checks impossible. After high-profile cases of sanctions evasion, SWIFT introduced the MT202 COV in 2009, requiring the underlying customer details to travel with the cover. The pacs.009 COV continues that rule, supporting wire transfer transparency requirements.

Like other pacs messages, a pacs.009 has a group header with a message identifier, creation time, number of transactions and settlement information. Each credit transfer transaction block contains:

• Identification. Instruction, end-to-end and transaction identifications and a unique end-to-end transaction reference.
• Settlement details. The interbank settlement amount, currency and date, and optional settlement time instructions, such as a deadline by which the payment must settle.
• Parties. The debtor institution, the creditor institution and any agents or intermediaries between them, identified mainly by Business Identifier Codes.
• Underlying customer credit transfer. In the COV form only, the details of the customer payment being covered.

Because both debtor and creditor are financial institutions, the message is simpler than a pacs.008 in most respects, with little or no remittance information except in the COV form.

In correspondent banking, a payment between two banks without a direct relationship can move through a chain of correspondents. When the cover method is used, the ordering bank sends the pacs.008 directly to the beneficiary's bank and sends a pacs.009 COV through its correspondent, which passes the funds along to the beneficiary bank's correspondent. The beneficiary bank matches the two messages, usually by their references, before crediting the customer. Each bank in the cover chain screens the underlying customer details.

The migration of cross-border payments from MT to ISO 20022 began in March 2023, with a coexistence period running to November 2025, and the pacs.009 took over the role of the MT202 family across SWIFT. Banks needed to update treasury, liquidity and sanctions systems so that they could create, read and screen the new message correctly. A recurring issue is the correct choice between the core and COV forms: using the core form for a cover payment breaks transparency rules, and supervisors and correspondents expect banks to have controls that prevent it.