Rule reference · SEPA Credit Transfer scheme rules · Identifiers

SEPA-SCT-ID-003: Payment information identification used twice

Two payment information blocks in this message have the same identification. ISO 20022 defines it as a unique identification of the block within the message.

Severity	WARNING Warning: the run needs review
Status	Recommendation, or depends on your agreement with the bank
Applies to	pain.001.001.09, SEPA Credit Transfer
Elements checked	/Document/CstmrCdtTrfInitn/PmtInf/PmtInfId
Source	EPC132-08 2025 Version 1.0, section 2.1.1, item 2.1 · Standards and sources
Rule pack	sepa.sct.pain001.v09 v3, effective 2025-10-05

Why it matters

Banks use it to report the status of each block; a duplicate may be rejected or make status reports ambiguous.

How to fix it

Check how payment information identifiers are generated (for example one per payment run and house bank account).

Example

Synthetic XML fragments.

Example that fails

<PmtInf>
  <PmtInfId>PMTINF-0001</PmtInfId>
  <PmtMtd>TRF</PmtMtd>
  <BtchBookg>true</BtchBookg>
  <NbOfTxs>2</NbOfTxs>
  <CtrlSum>200.50</CtrlSum>
  <PmtTpInf>…</PmtTpInf>
  <ReqdExctnDt>…</ReqdExctnDt>
  <Dbtr>…</Dbtr>
  <DbtrAcct>…</DbtrAcct>
  <DbtrAgt>…</DbtrAgt>
  <ChrgBr>SLEV</ChrgBr>
  …
</PmtInf>

Corrected

<PmtInf>
  …
  <BtchBookg>true</BtchBookg>
  <NbOfTxs>4</NbOfTxs>
  <CtrlSum>6460.44</CtrlSum>
  <PmtTpInf>…</PmtTpInf>
  <ReqdExctnDt>…</ReqdExctnDt>
  <Dbtr>…</Dbtr>
  <DbtrAcct>…</DbtrAcct>
  <DbtrAgt>…</DbtrAgt>
  <ChrgBr>SLEV</ChrgBr>
  <CdtTrfTxInf>
  …
</PmtInf>

Try it with a synthetic example

These files are synthetic test data from BankLint's test corpus. Download one, or validate it directly.

Two payment information blocks with the same identification: advisory WARNING (pack v3). REVIEW · Download · Validate it

Explained in

SEPA-SCT-ID-001: Reference or identifier violates SEPA character rules
SEPA-SCT-ID-002: Transaction reference violates SEPA character rules

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