Ultimate debtor and ultimate creditor in pain.001 (payments on behalf of)

In a pain.001 the debtor (Dbtr) is the party whose account is debited and the creditor (Cdtr) the party whose account is credited. The ultimate debtor (UltmtDbtr) is the party that owes the money when that is not the debtor, and the ultimate creditor (UltmtCdtr) the party the money is due to when that is not the creditor. Both are optional; in SEPA their names are limited to 70 characters.

The parties in a pain.001#

All five use the same party structure (PartyIdentification135 in pain.001.001.09, PartyIdentification32 in .03): Nm, PstlAdr, Id, CtryOfRes and CtctDtls, each optional in the schema.

The ultimate debtor can be given once for a payment information block or in each transaction. The schema allows both positions and the SEPA guidelines state no preference, so check with your bank which level it reads.

Names: 70 characters in SEPA#

Every party name is Max140Text in the schema. The SEPA guidelines limit each one to 70 characters (items 1.7, 2.22, 2.68, 2.101, 2.117 and 2.149). BankLint checks them in three rules:

• SEPA-SCT-NAME-001BLOCKERInitiating party name longer than 70 characters. SEPA limits party names to 70 characters (ISO 20022 allows 140), counted as written, spaces included.
• SEPA-SCT-NAME-002BLOCKERDebtor name longer than 70 characters. SEPA limits debtor and ultimate debtor names to 70 characters (ISO 20022 allows 140), counted as written, spaces included.
• SEPA-SCT-NAME-003BLOCKERCreditor-side name longer than 70 characters. SEPA limits the creditor name, the ultimate debtor name given at transaction level and the ultimate creditor name to 70 characters (ISO 20022 allows 140), counted as written, spaces included.

The character set rules also cover the ultimate debtor name in a transaction and the ultimate creditor name (SEPA-SCT-CHARSET-001, SEPA-SCT-CHARSET-002); see SEPA character set.

Identification: organisation or private person#

Under Id a party is identified either as an organisation (OrgId) or as a private person (PrvtId). In the schema, OrgId holds at most one AnyBIC, at most one LEI and any number of Othr; PrvtId holds at most one DtAndPlcOfBirth and any number of Othr. Each Othr has an Id of up to 35 characters and optionally a scheme name (SchmeNm, a code from the ISO 20022 external code set or a proprietary value) and an issuer (Issr). The SEPA guidelines restrict the choice:

The 2025 guidelines changed the debtor and ultimate debtor rule to "and/or" "to be able to comply with the new Funds Transfer Regulation (FTR)", according to their change history. BankLint’s SEPA rules do not check party identification; the schema alone allows several Othr. Which identification your bank expects for the parties you pay on behalf of is a question for your bank.

Example#

Synthetic Corp Example AG holds the debited account and initiates the file. It pays an invoice owed by Synthetic Retail Example GmbH, given as ultimate debtor for the whole block. The money goes to the account of Example Collections Delta BV, for Example Supplier Alpha GmbH as ultimate creditor. The file is synthetic, validates against the pain.001.001.09 schema and passes BankLint’s SEPA rules.

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pain.001.001.09">
  <CstmrCdtTrfInitn>
    <GrpHdr>
      <MsgId>MSG-2026-0002</MsgId>
      <CreDtTm>2026-10-16T09:00:00</CreDtTm>
      <NbOfTxs>1</NbOfTxs>
      <CtrlSum>1250.00</CtrlSum>
      <InitgPty>
        <Nm>Synthetic Corp Example AG</Nm>
      </InitgPty>
    </GrpHdr>
    <PmtInf>
      <PmtInfId>PMTINF-0002</PmtInfId>
      <PmtMtd>TRF</PmtMtd>
      <NbOfTxs>1</NbOfTxs>
      <CtrlSum>1250.00</CtrlSum>
      <PmtTpInf>
        <SvcLvl>
          <Cd>SEPA</Cd>
        </SvcLvl>
      </PmtTpInf>
      <ReqdExctnDt>
        <Dt>2026-10-20</Dt>
      </ReqdExctnDt>
      <Dbtr>
        <Nm>Synthetic Corp Example AG</Nm>
        <PstlAdr>
          <TwnNm>Musterstadt</TwnNm>
          <Ctry>DE</Ctry>
        </PstlAdr>
      </Dbtr>
      <DbtrAcct>
        <Id>
          <IBAN>DE50100000000000000001</IBAN>
        </Id>
      </DbtrAcct>
      <DbtrAgt>
        <FinInstnId>
          <BICFI>TESTDEFFXXX</BICFI>
        </FinInstnId>
      </DbtrAgt>
      <UltmtDbtr>
        <Nm>Synthetic Retail Example GmbH</Nm>
        <Id>
          <OrgId>
            <Othr>
              <Id>SUBSIDIARY-0042</Id>
            </Othr>
          </OrgId>
        </Id>
      </UltmtDbtr>
      <ChrgBr>SLEV</ChrgBr>
      <CdtTrfTxInf>
        <PmtId>
          <EndToEndId>E2E-INV-2001</EndToEndId>
        </PmtId>
        <Amt>
          <InstdAmt Ccy="EUR">1250.00</InstdAmt>
        </Amt>
        <Cdtr>
          <Nm>Example Collections Delta BV</Nm>
        </Cdtr>
        <CdtrAcct>
          <Id>
            <IBAN>NL84TEST0000000022</IBAN>
          </Id>
        </CdtrAcct>
        <UltmtCdtr>
          <Nm>Example Supplier Alpha GmbH</Nm>
        </UltmtCdtr>
        <RmtInf>
          <Ustrd>Invoice INV-2001</Ustrd>
        </RmtInf>
      </CdtTrfTxInf>
    </PmtInf>
  </CstmrCdtTrfInitn>
</Document>

Order matters: in the payment information block UltmtDbtr comes after DbtrAgt and before ChrgBr; in a transaction UltmtCdtr comes after CdtrAcct. An element in the wrong place fails the schema (BNK-ISO-001).

What BankLint compares in regression testing#

In a Flow, BankLint compares each new file with the bank-accepted baseline. For the parties it compares only whether they are given and how they are identified, never names or identifiers:

BankLint treats the ultimate debtor as a configuration signal and the ultimate creditor as depending on the payees in each run. See payment-file regression testing.

Questions

When do I need an ultimate debtor?#

When the party that owes the money is not the holder of the debited account, for example a group company whose invoice is paid from another company’s account. It is optional in the schema and in SEPA; your bank may have its own requirements.

Is the initiating party the same as the debtor?#

It can be. ISO 20022 defines the initiating party as either the debtor or the party that initiates the credit transfer on behalf of the debtor.

How long can the ultimate debtor and ultimate creditor names be?#

70 characters in a SEPA credit transfer (items 2.68, 2.101 and 2.149); the ISO 20022 schema allows 140.

Can I give the ultimate debtor at both levels?#

The schema allows an ultimate debtor in the payment information block and in each transaction, and the SEPA guidelines state no preference. Check with your bank which level it reads.

Validate a pain.001 fileFree, no account needed, files are not stored.

More guides

• Verification of Payee and bulk payment files→
• pain.001.001.03 vs pain.001.001.09: what changed and how to migrate→
• pain.001 references: MsgId, PmtInfId, InstrId, EndToEndId and UETR→
• Batch booking in pain.001: one debit or one per payment→
• SEPA and non-SEPA payments in one pain.001 file→

All guides