SEPA-SCT-RMTINF-007: RF creditor reference without issuer ISO

The creditor reference looks like an RF Creditor Reference (ISO 11649), but the reference type does not name ISO as its issuer. The guidelines make the issuer mandatory for a reference governed by a known institution, and name ISO for RF references.

Why it matters

Banks generally process the payment, but the creditor's bank may not recognise the reference as RF and the payee may have to reconcile it by hand.

How to fix it

Add Issuer ISO to the creditor reference type (Tp/Issr) when the reference is an RF Creditor Reference.

Example

Synthetic XML fragments.

<CdtTrfTxInf>
  …
  <CdtrAcct>…</CdtrAcct>
  <RmtInf>
    <Strd>
      <CdtrRefInf>
        <Tp>
          <CdOrPrtry>…</CdOrPrtry>
        </Tp>
        <Ref>RF18539007547034</Ref>
      </CdtrRefInf>
    </Strd>
  </RmtInf>
</CdtTrfTxInf>

<CdtTrfTxInf>
  …
  <CdtrAcct>…</CdtrAcct>
  <RmtInf>
    <Strd>
      <CdtrRefInf>
        <Tp>
          <CdOrPrtry>…</CdOrPrtry>
          <Issr>ISO</Issr>
        </Tp>
        <Ref>RF18539007547034</Ref>
      </CdtrRefInf>
  …
</CdtTrfTxInf>

Try it with a synthetic example

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

• An RF creditor reference (ISO 11649) with type SCOR but no issuer: accepted, with an INFO that the issuer should be ISO (pack v4). PASS · Download · Validate it

Explained in

• SEPA Credit Transfer rules for pain.001.001.09

Related rules: Remittance information

• SEPA-SCT-RMTINF-001: Either structured or unstructured remittance, not both
• SEPA-SCT-RMTINF-002: Only one remittance information occurrence allowed
• SEPA-SCT-RMTINF-003: Creditor reference type must be SCOR
• SEPA-SCT-RMTINF-004: Creditor reference needs both type and reference
• SEPA-SCT-RMTINF-005: Structured remittance longer than 140 characters
• SEPA-SCT-RMTINF-006: Issuer ISO needs an RF creditor reference

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