pacs008 logo pacs008
See it live ›

pacs.009.001.10 | Financial Institution Credit Transfer | pacs008

Last reviewed

pacs.009.001.10 — Financial Institution Credit Transfer

Field Value
ISO name FinancialInstitutionCreditTransferV10
Registration status Registered
Year 2019
Version 10

Overview

The pacs.009 message moves funds between banks on their own behalf. It supports funding, cover payments, and liquidity management.

Reviewed 23 March 2026. ISO catalogue date: 2025-02-27.

Key data elements

  • GrpHdr — Group Header with message identification and settlement information.
  • CdtTrfTxInf — Credit Transfer Transaction Information with interbank settlement amount.
  • Dbtr / DbtrAgt — Debtor institution and its agent identification.
  • Cdtr / CdtrAgt — Creditor institution and its agent identification.
  • IntrBkSttlmAmt — Interbank Settlement Amount in the settlement currency.

Business context

  • Used for bank-to-bank own-account transfers and cover payments.
  • Supports liquidity management between correspondent banks.
  • Carries the cover leg of customer credit transfers.
  • Supports treasury and funding operations.
Key data elements and business context
Key data elements Business context
GrpHdr — Group Header with message identification and settlement information Used for bank-to-bank own-account transfers and cover payments
CdtTrfTxInf — Credit Transfer Transaction Information with interbank settlement amount Supports liquidity management between correspondent banks
Dbtr / DbtrAgt — Debtor institution and its agent identification Carries the cover leg of customer credit transfers
Cdtr / CdtrAgt — Creditor institution and its agent identification Supports treasury and funding operations
IntrBkSttlmAmt — Interbank Settlement Amount in the settlement currency The debtor bank sends pacs.009 to the creditor bank to transfer its own funds. In cover flows, pacs.009 carries the funding leg while pacs.008 carries the customer instruction on a separate path.

CBPR+ and scheme context

  • Replaces MT202 and MT202COV for institution-to-institution transfers.
  • Cover-method flows pair pacs.009 with the underlying pacs.008 instruction.
  • Structured party data and LEI identification matter more often.
  • SWIFT gpi also covers pacs.009.

Message flow

The debtor bank sends pacs.009 to the creditor bank to transfer its own funds. In cover flows, pacs.009 carries the funding leg while pacs.008 carries the customer instruction on a separate path.

Version commentary

ISO 20022 last updated this business area on 2025-02-27. This site documents pacs.009.001.10. The latest catalogue version is pacs.009.001.12.

Use this page for the version that pacs008 implements today, and review the newer catalogue version for roadmap planning.

Version-diff table

Version history and implementation guidance
Version range Why it matters Implementation takeaway
pacs.009.001.10 Current implementation in pacs008 Matches the current project support for FI credit transfer flows.
pacs.009.001.11-12 Later catalogue revisions Important for roadmap planning in correspondent and cover-payment environments.

Scheme-specific notes

  • In CBPR+, pacs.009 carries bank-to-bank credit transfers and cover-payment legs. See the roadmap PDF and CBPR+ pacs.009 material.
  • For cover method, read pacs.009 with the related customer leg in pacs.008. See Swift's pacs.008/pacs.009 cover-method page.
  • This message is outside the SCT and SCT Inst customer credit-transfer rulebooks, so SEPA customer-payment rules do not carry over unchanged.

When to use this message

Use pacs.009 for bank-to-bank credit transfers, especially treasury, funding, and cover-payment legs.

When not to use this message

Do not use pacs.009 when the business transaction still belongs in pacs.008.

Implementation notes

  • Separate cover-payment logic from customer-payment logic.
  • Apply strict controls to value date, settlement amount, and liquidity booking.
  • Prioritise bank identifiers and chain transparency.

Common failure modes

  • Confusing own-account transfers with customer transfers.
  • Losing the relationship between cover and underlying customer flows.
  • Underestimating the impact of correspondent chain changes on settlement.

Worked XML fragment

<FICdtTrf>
  <GrpHdr>
    <MsgId>FICT-2026-0005MsgId>
  GrpHdr>
  <CdtTrfTxInf>
    <PmtId><InstrId>COVER-8841InstrId>PmtId>
    <IntrBkSttlmAmt Ccy="USD">25000.00IntrBkSttlmAmt>
    <Dbtr><Nm>Originating BankNm>Dbtr>
    <Cdtr><Nm>Cover BankNm>Cdtr>
  CdtTrfTxInf>
FICdtTrf>

Field commentary

  • InstrId: Use a funding-leg identifier that still links back to any customer flow.
  • IntrBkSttlmAmt: Own-account and cover flows need strict treasury controls on amount and date.
  • Dbtr / Cdtr: These are institution parties, not retail customer roles.

Decision flow

Is this own-account bank movement or a cover leg?
Yes -> Use pacs.009.
No -> Is it a customer payment instruction?
Yes -> Consider pacs.008 instead.
No -> Check whether treasury or settlement operations own the case.

Compare pacs.009 vs pacs.008

Comparison of pacs.009.001.10 and pacs.008
Dimension pacs.009.001.10 Comparison message
Primary purpose Institution-own-account credit transfer or cover leg Customer credit transfer
Business owner Treasury / correspondent / funding operations Customer-payment operations
Typical pairings pacs.002, pacs.004, and linked pacs.008 flows pacs.002, pacs.004, pacs.007, pacs.028
Wrong assumption to avoid That it is just a more technical pacs.008 That it can carry institution funding flows cleanly

Implementation FAQ

When should I choose pacs.009 over pacs.008?

Choose pacs.009 for own-account transfers and cover legs; choose pacs.008 for customer-credit-transfer instructions.

Why is pacs.009 often harder to reconcile than expected?

Because banks must preserve the relationship between treasury funding, correspondent legs, and any linked customer payment.

Primary references

Related messages

Message type Description Overview
pacs.008.001.13 FI to FI Customer Credit Transfer The pacs.008 message is the main customer credit-transfer instruction between banks. It carries party, amount, and remittance data.
pacs.002.001.12 FI to FI Payment Status Report The pacs.002 message reports the status of an earlier payment instruction. It tells another institution whether the payment was accepted, rejected, pending, or settled.
pacs.010.001.05 Financial Institution Direct Debit The pacs.010 message lets one financial institution debit another institution's own account. It is for bank-to-bank collections, not customer direct debits.