pacs.003ISO 20022

pacs.003 — FI to FI Customer Direct Debit

Carries an inter-PSP customer direct-debit collection from the creditor side toward the debtor side under an applicable scheme or clearing profile. It describes the collection obligation; customer debit and settlement are separate events.

DIRECTION: Sent by the creditor agent, directly or through a clearing and settlement mechanism, toward the debtor agent.

Version + profile: pacs.003 is a message-family identifier, not a complete version. The numeric .001.xx definition and field rules depend on the scheme, service, usage guideline, and implementation version named in each context; sample namespaces show only the illustrated version.

Contributor Shubham Mathure18 July 2026

DOMAIN + EDITORIAL AUDITAudited 2026-07-18 for payment logic, source scope, technical writing, and Payments Signal voice — see the method.

EVIDENCE AT ARM'S REACH

IMPLEMENTATION RESOURCES

Start with the exact message version, then apply the scheme or network profile that governs your implementation.

An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.

XSD + definitionBase ISO 20022current

ISO 20022 message definitions and XSDs

Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.

Owner: ISO 20022 Registration Authority
Checked: 2026-07-12
Access: Official page · Public official catalogue; select the required message version before downloading.

OPEN OFFICIAL SOURCE

RulebookSEPA SDD Corecurrent

SEPA Direct Debit Core rulebook

The controlling scheme rules for mandates, collections, R-transactions, timelines, and consumer refund rights.

Owner: European Payments Council
Version: 2025 version 1.1 (EPC016-06)
Checked: 2026-07-13
Access: Official page · Public EPC document page; use the version effective for the collection date.

OPEN OFFICIAL SOURCE

Usage guidelineSEPA SDD Corecurrent

SEPA Direct Debit Core implementation guidelines and XSDs

Customer-to-PSP and Inter-PSP SDD Core profiles. EPC XSD technical validation subsets express guideline restrictions but are not production artefacts or proof of complete scheme compliance.

Owner: European Payments Council
Version: 2025 version 1.0
Checked: 2026-07-19
Access: Official page · Public EPC scheme page with owner-hosted guideline and XSD downloads.

OPEN OFFICIAL SOURCE

RulebookSEPA SDD B2Bcurrent

SEPA Direct Debit B2B rulebook

The business-to-business mandate, debtor-bank checking, collection, exception, and refund-right rules.

Owner: European Payments Council
Version: 2025 version 1.1 (EPC222-07)
Checked: 2026-07-13
Access: Public download · Public owner-hosted EPC PDF; confirm the effective version before implementation.

DOWNLOAD FROM OWNER

Usage guidelineSEPA SDD B2Bcurrent

SEPA Direct Debit B2B implementation guidelines and XSDs

Customer-to-PSP, Inter-PSP, and e-mandate profiles. EPC XSD technical validation subsets express guideline restrictions but are not production artefacts or proof of complete scheme compliance.

Owner: European Payments Council
Version: 2025 version 1.0
Checked: 2026-07-19
Access: Official page · Public EPC scheme page with owner-hosted guideline and XSD downloads.

OPEN OFFICIAL SOURCE

Teaching sampleScheme-neutral teachingcurrent

pacs.003 FI-to-FI direct-debit collection — raw XML

A fictional SDD Core inter-PSP collection derived from a pain.008. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.

Owner: Payments Signal
Version: pacs.003.001.11
Checked: 2026-07-19
Integrity: crc32:051e41e4
Access: Payments Signal download · Original fictional teaching sample; no login required.

DOWNLOAD

Field matrixBase ISO 20022current

pacs.003 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:fa395f36
Access: Payments Signal download · Original, source-backed teaching asset; no login required.

DOWNLOAD

Profile packSEPA SDD Corecurrent

SEPA direct-debit implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

Owner: Payments Signal
Checked: 2026-07-19
Integrity: crc32:458732a2
Access: Payments Signal download · Original generated teaching pack; no login required.

DOWNLOAD

WHO IS INVOLVED

Creditor agentValidates the creditor instruction and originates the inter-PSP collection under the scheme profile.
Debtor agentApplies debtor-side controls and posts, rejects or returns the collection as the rules permit.

KEY FIELDS

Curated teaching subset. The applicable SDD implementation guidelines define field requirements, sequence rules, reason codes, timing and R-transaction handling.

Key fields of pacs.003
FIELD	NAME	PRESENCE	WHAT IT MEANS
`GrpHdr/MsgId`	Message identification	MANDATORYBase ISO 20022 pacs.003 message definition	Unique identifier for the inter-PSP collection message.
`GrpHdr/IntrBkSttlmDt`	Interbank settlement date	CONDITIONALRequired by the applicable clearing or scheme profile when settlement date is carried	Date assigned to the inter-PSP settlement obligation.
`DrctDbtTxInf/PmtId/EndToEndId`	End-to-end identification	MANDATORYBase ISO 20022 pacs.003 transaction	Creditor reference carried from the customer initiation for reconciliation.
`DrctDbtTxInf/IntrBkSttlmAmt`	Interbank settlement amount	MANDATORYBase ISO 20022 pacs.003 transaction	Amount and currency forming the inter-PSP collection obligation.
`DrctDbtTxInf/DrctDbtTx/MndtRltdInf/MndtId`	Mandate identification	MANDATORYDirect-debit scheme profile	Reference to the mandate supporting the collection.
`DrctDbtTxInf/CdtrAgt`	Creditor agent	MANDATORYBase ISO 20022 pacs.003 transaction	PSP acting for the creditor.
`DrctDbtTxInf/DbtrAgt`	Debtor agent	MANDATORYBase ISO 20022 pacs.003 transaction	PSP expected to debit the debtor account or return the collection.
`DrctDbtTxInf/RmtInf`	Remittance information	OPTIONALBase ISO 20022 pacs.003 transaction	Reference helping the debtor and creditor identify the underlying bill.

FIELD BY FIELD — FULL STRUCTURE

The whole pacs.003 laid out as a parent-child tree: every field in its nesting, with a sample value and what it means. Expand a branch to drill in. Values are fictional (SYNTHETIC / TRAINING ONLY); this is a curated practitioner view, not the full schema.

Document—The root of an ISO 20022 message — the business payload, which a Business Application Header (head.001) accompanies as a separate document.
- FIToFICstmrDrctDbt—
  - GrpHdr—Group header — data that applies to the whole message: its identity, when it was created, how many transactions it carries, and shared settlement data.
    MsgIdDEMO-PACS003-001MandatoryUnique identifier for the inter-PSP collection message.
    Use case
    Quoted when a status report or return refers back to this whole message; changes at every interbank hop.
    Example
    DEMO-PACS008-001
    CreDtTm2026-07-18T08:05:00ZMandatoryCreation date and time — when this message was created (a UTC timestamp), separate from when the payment is executed.
    Use case
    A processing timestamp for the message — distinct from the requested execution or settlement date.
    Example
    2026-07-12T09:01:00Z
    NbOfTxs1Number of transactions the message carries — a control total the receiver checks against the transactions it finds.
    Use case
    The receiver counts the transactions it parsed and rejects the whole message if the tally disagrees.
    Example
    <NbOfTxs>2</NbOfTxs>
    CtrlSum480.00Control sum — the total of all instructed amounts, a second control the receiver reconciles.
    Use case
    A second integrity check alongside NbOfTxs — the summed amounts must equal this figure.
    Example
    <CtrlSum>2500.00</CtrlSum>
    IntrBkSttlmDt2026-07-21ConditionalDate assigned to the inter-PSP settlement obligation.
    Use case
    The value date the settlement actually lands — what a treasury desk reconciles its nostro against.
    Example
    <IntrBkSttlmDt>2026-07-13</IntrBkSttlmDt>
    SttlmInf—Settlement Information — how the interbank settlement of the payment is to happen.
    SttlmMtdCLRGSettlement Method — how interbank settlement happens for this payment.
    Use case
    Tells the receiver whether the money settles on an account they service (INDA/INGA), through a clearing system (CLRG), or via a separate cover (COVE).
    Example
    <SttlmMtd>CLRG</SttlmMtd>
    Codes
    see codes →
  - DrctDbtTxInf—
    PmtId—Payment Identification — the set of references that identify this payment along the chain.
    InstrIdDEMO-SDD-INSTR-001Instruction Identification — a point-to-point reference between the two agents exchanging this message; not carried end to end.
    Use case
    A reference for the immediate hop only — useful for a query between two adjacent banks, but it does not survive the next leg.
    Example
    DEMO-INSTR-001
    Watch out
    Don't rely on it for end-to-end reconciliation — that is what EndToEndId (and the UETR) are for.
    EndToEndIdDEMO-SDD-E2E-001MandatoryCreditor reference carried from the customer initiation for reconciliation.
    Use case
    The reference the beneficiary matches to an invoice and ops teams use to correlate status reports and returns.
    Example
    DEMO-E2E-001
    Watch out
    Filling it with 'NOTPROVIDED' wastes the single best reconciliation field in the chain.
    TxIdDEMO-SDD-TX-001Transaction Identification — an interbank reference for this transaction, assigned by the first instructing agent.
    Use case
    The interbank handle a return (pacs.004) or status report (pacs.002) quotes to point at the original transaction.
    Example
    DEMO-TX-001
    PmtTpInf—Payment Type Information — how the payment should be handled: its service level, local instrument, category purpose, and priority.
    SvcLvlchoice—Service Level — the rulebook or agreed service under which the payment runs (e.g. a SEPA scheme).
    CdSEPAService-level code — the 4-letter code naming the scheme/service (e.g. SEPA).
    Use case
    Set SEPA for a euro retail payment; SDVA to ask for same-day value.
    Example
    SEPA
    Codes
    see codes →
    LclInstrmchoice—Local Instrument — a further, community- or scheme-specific qualifier of how the payment is cleared (e.g. an instant variant).
    CdCORELocal-instrument code — the 4-letter code for the clearing variant (e.g. INST).
    Use case
    INST with service level SEPA marks a SEPA Instant payment.
    Example
    INST
    Codes
    see codes →
    SeqTpRCURSequence Type — identifies the collection's place in the mandate sequence, such as one-off or recurring, under the applicable scheme profile.
    IntrBkSttlmAmt480.00Ccy=EURMandatoryAmount and currency forming the inter-PSP collection obligation.
    Use case
    The figure that moves between the banks — after any deducted charges, so it can differ from what the customer instructed.
    Example
    <IntrBkSttlmAmt Ccy="EUR">1250.00</IntrBkSttlmAmt>
    DrctDbtTx—
    MndtRltdInf—
    MndtIdDEMO-MANDATE-001MandatoryReference to the mandate supporting the collection.
    DtOfSgntr2026-01-10Date of Signature — the date recorded for the debtor's signing of the mandate.
    CdtrAgt—MandatoryPSP acting for the creditor.
    FinInstnId—Financial Institution Identification — how a bank is identified, usually by its BIC.
    BICFIDEMODEFFXXXBusiness Identifier Code (financial institution) — the 8- or 11-character BIC naming a bank.
    Use case
    The primary way a bank is identified across the chain; 8 characters for the institution, 11 to name a branch.
    Example
    DEMODEFFXXX
    Cdtr—MandatoryCreditor — the party being paid: the beneficiary.
    NmAsha TradersName — the free-text name of a party.
    Use case
    The name screening and verification-of-payee compare against; quality here directly affects whether a payment clears.
    Example
    <Nm>Demo Trading Ltd</Nm>
    Watch out
    A creditor name that doesn't match the account holder can trigger a name-check warning or return.
    DbtrAgt—MandatoryPSP expected to debit the debtor account or return the collection.
    FinInstnId—Financial Institution Identification — how a bank is identified, usually by its BIC.
    BICFIDEMOGB2LXXXBusiness Identifier Code (financial institution) — the 8- or 11-character BIC naming a bank.
    Use case
    The primary way a bank is identified across the chain; 8 characters for the institution, 11 to name a branch.
    Example
    DEMODEFFXXX
    Dbtr—MandatoryDebtor — the party whose account is debited: the payer.
    NmRiya ExampleName — the free-text name of a party.
    Use case
    The name screening and verification-of-payee compare against; quality here directly affects whether a payment clears.
    Example
    <Nm>Demo Trading Ltd</Nm>
    Watch out
    A creditor name that doesn't match the account holder can trigger a name-check warning or return.
    DbtrAcct—Debtor Account — the account to debit; in SEPA an IBAN.
    Idchoice—Identification — a party or account identifier; for a party this is a choice of organisation id or private id.
    IBANGB33BUKB20201555555555International Bank Account Number — the standardised account identifier used across SEPA and beyond.
    Use case
    Encodes country, bank, and account with a checksum, so a typo usually fails validation before it leaves.
    Example
    DE02120300000000202051
    RmtInf—OptionalReference helping the debtor and creditor identify the underlying bill.
    UstrdDEMO INVOICE 480Unstructured — free-text remittance information (e.g. an invoice note); readable but not machine-parseable.
    Use case
    Fine for a human-read note; SEPA allows one occurrence of up to 140 characters.
    Example
    <Ustrd>DEMO INVOICE 1001</Ustrd>
    Watch out
    This text is screened — careless free text ('payment for Iran project') creates sanctions alerts that stop clean payments.

Sources for the field structure4

Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pain/pacs/camt message-definition elements
Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Official requirement
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group) · cross-border agent chain and structured-data usage
Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-18
Full guidelines require MyStandards access. Public guidance states that after 14 November 2026 fully unstructured addresses are removed for in-scope CBPR+ traffic, with explicit message exceptions including admi.024, camt.025, camt.052, camt.053, camt.054 and camt.060.
Official requirement
Swift Standards MT (annual standards releases) ↗ — Swift · FIN block structure
Defines the MT message standards (including MT101, MT103, MT202/202 COV, and the MT9xx statement messages) exchanged over the Swift FIN network, maintained through annual standards releases. · Checked 2026-07-18
Full field-level specifications live in the Swift Knowledge Centre User Handbook behind a swift.com login. Coexistence for in-scope FI-to-FI payment instructions ended on 22 November 2025, but treatment differs by MT: some instructions are NAKed and selected messages can enter temporary, chargeable contingency conversion. Reporting, initiation, investigations and correspondence follow separate roadmaps.
Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
This site's own simplified teaching models. · Checked 2026-07-12
What this simplifies: One-line plain-language descriptions of the commonly-populated elements — a practitioner view, not the authoritative ISO 20022 / MT schema, which defines many more optional elements.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

COMMON ERRORS

Applying SDD B2B mandate-check and refund rules to a Core collection.Consequence: The debtor is given the wrong control or refund outcome.Avoid it: Carry the scheme identifier and route each transaction through the correct Core or B2B rules.
Calling a pacs.003 message proof that the debtor was debited.Consequence: Operations closes the collection before posting, settlement and possible R-transactions are known.Avoid it: Reconcile the instruction, customer posting, settlement and any return, refund or reversal separately.

USAGE CONTEXTS

SEPA Direct Debit CoreCarries the inter-PSP collection under the current EPC SDD Core profile.
SEPA Direct Debit B2BUses a separate scheme profile with a debtor-bank mandate-check obligation and different refund rights.

SEE IT IN A PLAYABLE FLOW

Sources for this reference3

Official requirement
ISO 20022 Catalogue of messages ↗ — ISO 20022 Registration Authority · pacs.003 FIToFICustomerDirectDebit message definition
Defines the current versions of all ISO 20022 message definitions, including the pain, pacs, and camt messages taught on this site. · Checked 2026-07-12
Each message set is described by a Message Definition Report; earlier versions remain available in the ISO 20022 messages archive.
Scheme-specific rule2025 v1.1 (EPC016-06)
2025 SEPA Direct Debit Core rulebook version 1.1 (EPC016-06) ↗ — European Payments Council · SDD Core inter-PSP collection process
Rules of the SEPA Direct Debit Core scheme: mandates, collection lifecycle, timelines, R-transactions, and refund rights. · Effective 2025-10-05 · Checked 2026-07-13
Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
This site's own simplified teaching models. · Checked 2026-07-12
What this simplifies: One transaction and a compact field subset; CSM and scheme implementation detail is omitted.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.

pacs.003 — FI to FI Customer Direct Debit

IMPLEMENTATION RESOURCES

ISO 20022 message definitions and XSDs

SEPA Direct Debit Core rulebook

SEPA Direct Debit Core implementation guidelines and XSDs

SEPA Direct Debit B2B rulebook

SEPA Direct Debit B2B implementation guidelines and XSDs

pacs.003 FI-to-FI direct-debit collection — raw XML

pacs.003 field matrix

SEPA direct-debit implementation pack

WHO IS INVOLVED

KEY FIELDS

FIELD BY FIELD — FULL STRUCTURE

COMMON ERRORS

USAGE CONTEXTS

SEE IT IN A PLAYABLE FLOW

Discuss this learning page

Public discussion

IMPLEMENTATION RESOURCES

ISO 20022 message definitions and XSDs

SEPA Direct Debit Core rulebook

SEPA Direct Debit Core implementation guidelines and XSDs

SEPA Direct Debit B2B rulebook

SEPA Direct Debit B2B implementation guidelines and XSDs

pacs.003 FI-to-FI direct-debit collection — raw XML

pacs.003 field matrix

SEPA direct-debit implementation pack

WHO IS INVOLVED

KEY FIELDS

FIELD BY FIELD — FULL STRUCTURE

COMMON ERRORS

USAGE CONTEXTS

SEE IT IN A PLAYABLE FLOW

RELATED MESSAGES

LEARN THE CONTEXT

Discuss this learning page

Public discussion