SEPA-SCT-RMTINF-005: Structured remittance longer than 140 characters

The tags and data inside the structured remittance information (without the Strd tags themselves) may be at most 140 characters long.

Why it matters

Structured remittance longer than 140 characters does not meet the SEPA format rule and may be rejected or truncated.

How to fix it

Send only the creditor reference (Tp and Ref) in the structured remittance, or use unstructured remittance for longer text.

Example

Synthetic XML fragments.

<RmtInf>
  <Strd>
    <CdtrRefInf>
      <Tp>
        <CdOrPrtry>
          <Cd>SCOR</Cd>
        </CdOrPrtry>
      </Tp>
      <Ref>RF18539007547034</Ref>
    </CdtrRefInf>
    <AddtlRmtInf>Synthetic remittance detail Synthetic remittance detail Synthetic remittance detail Synthetic remittance detail</AddtlRmtInf>
  </Strd>
</RmtInf>

<RmtInf>
  <Ustrd>Invoice INV-1001</Ustrd>
</RmtInf>

Try it with a synthetic example

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

• Structured remittance whose tags and data exceed 140 characters: BLOCKER (pack v3, item 2.166). FAIL · Download · Validate it

Explained in

• Remittance information in a SEPA pain.001 (Ustrd, Strd, RF)

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-006: Issuer ISO needs an RF creditor reference

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