pacs.009.001.10 — Financial Institution Credit Transfer
Overview
The pacs.009 message moves funds between financial institutions 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 | 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 institution sends pacs.009 to the creditor institution 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 are used more often.
- SWIFT gpi covers pacs.009 for correspondent-banking transparency.
Message flow
The debtor institution sends pacs.009 to the creditor institution 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 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 institution-to-institution credit transfers and cover-payment legs. See the roadmap PDF and CBPR+ pacs.009 material.
- For cover method, analyse pacs.009 together with the related customer leg in pacs.008. See Swift's pacs.008/pacs.009 cover-method training 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 institution-to-institution 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 institution 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 behavior.
Worked XML fragment
xml
<FICdtTrf>
<GrpHdr>
<MsgId>FICT-2026-0005</MsgId>
</GrpHdr>
<CdtTrfTxInf>
<PmtId><InstrId>COVER-8841</InstrId></PmtId>
<IntrBkSttlmAmt Ccy="USD">25000.00</IntrBkSttlmAmt>
<Dbtr><Nm>Originating Bank</Nm></Dbtr>
<Cdtr><Nm>Cover Bank</Nm></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
text
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 -> Validate whether treasury or settlement operations own the case.Compare pacs.009 vs pacs.008
Implementation FAQ
When should I choose pacs.009 over pacs.008?
Choose pacs.009 for institution-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 institutions must preserve the relationship between treasury funding, correspondent legs, and any linked customer payment.
Primary references
- ISO 20022 message definitions catalogue for
pacs.009.001.10 - Swift CBPR+ ISO 20022 usage-guidelines announcement
- Swift CBPR+ migration roadmap PDF
- Swift CBPR+ pacs.009 overview
- Swift CBPR+ cover-method pacs.008/pacs.009 guidance