pacs.010.001.05 — Financial Institution Direct Debit

ISO name	FinancialInstitutionDirectDebitV05
Registration status	Registered
Year	2019
Version	5

Overview

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.

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

Key data elements

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

Business context

• Supports bank-to-bank direct-debit collection.
• Used for fees, margin calls, and similar obligations.
• Needs a bilateral agreement between the banks.
• Often sits in treasury or liquidity operations.

Key data elements	Business context
GrpHdr — Group Header with message identification and settlement information	Supports bank-to-bank direct-debit collection
DrctDbtTxInf — Direct Debit Transaction Information with collection amount	Used for fees, margin calls, and similar obligations
Cdtr / CdtrAgt — Creditor institution and its agent identification	Needs a bilateral agreement between the banks
Dbtr / DbtrAgt — Debtor institution and its agent identification	Often sits in treasury or liquidity operations
IntrBkSttlmAmt — Interbank Settlement Amount in the settlement currency	The collecting bank sends pacs.010 under a bilateral agreement. The receiving bank checks the request and either settles or rejects it.

CBPR+ and scheme context

• It maps older interbank direct-debit processing into ISO 20022.
• It follows the same structured party-data rules as other pacs messages.
• Bank identifiers such as BIC and LEI still need validation.
• It appears in wider ISO 20022 migration plans.

Message flow

The collecting bank sends pacs.010 under a bilateral agreement. The receiving bank checks the request and either settles or rejects it.

Version commentary

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

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.010.001.05	Current implementation in pacs008	Reference point for institution direct-debit support in the current project.
pacs.010.001.06	Later catalogue revision	Review before adopting newer infrastructure requirements.

Scheme-specific notes

• pacs.010 is not part of the SCT or SCT Inst credit-transfer rulebooks, so credit-transfer rules do not carry over here.
• Use this page as a guide for bank-to-bank direct-debit scenarios, not as a substitute for market-scheme documentation.

When to use this message

Use pacs.010 when one bank must debit another bank's own account.

When not to use this message

Do not use pacs.010 for customer direct debits or credit transfers.

Implementation notes

• Keep bilateral approval rules outside the message.
• Treat own-account debits as high-control flows.
• Design status and exception handling with the collection flow.

Common failure modes

• Treating pacs.010 as the debit mirror of pacs.009.
• Not storing the bilateral approval context.
• Ignoring downstream status and exception flows.

Worked XML fragment

<FIDrctDbt>
  <GrpHdr>
    <MsgId>FIDD-2026-0012</MsgId>
  </GrpHdr>
  <DrctDbtTxInf>
    <PmtId><InstrId>COLL-4500</InstrId></PmtId>
    <IntrBkSttlmAmt Ccy="EUR">1250.00</IntrBkSttlmAmt>
    <Cdtr><Nm>Collecting Institution</Nm></Cdtr>
    <Dbtr><Nm>Debited Institution</Nm></Dbtr>
  </DrctDbtTxInf>
</FIDrctDbt>

Field commentary

• InstrId: Use an identifier that links back to the bilateral collection arrangement.
• IntrBkSttlmAmt: Institution direct-debit amounts often need clear bilateral tolerance controls.
• Cdtr / Dbtr: Capture institutional roles clearly. This is not a retail-customer debit model.

Decision flow

Need a bank-to-bank direct-debit message?
Yes -> Use pacs.010.
No -> Need a customer direct-debit flow?
Yes -> Consider pacs.003 instead.
No -> Re-check whether the case is really a credit transfer.

Implementation FAQ

Is pacs.010 common in retail payment products?

Usually no. It fits bank-to-bank direct-debit scenarios better than standard retail products.

What should teams design first?

Start with approval rules, bilateral controls, and exception handling before finalising XML templates.

Primary references

• ISO 20022 message definitions catalogue for pacs.010.001.05
• Swift CBPR+ ISO 20022 usage-guidelines announcement
• Swift CBPR+ migration roadmap PDF

Related messages

Message type	Description	Overview
pacs.009.001.10	Financial Institution Credit Transfer	The pacs.009 message moves funds between financial institutions on their own behalf. It supports funding, cover payments, and liquidity management.
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.003.001.09	FI to FI Customer Direct Debit	The pacs.003 message executes a customer direct debit between financial institutions. It lets the creditor bank collect funds from the debtor bank.