SEPA field too long: name, remittance information or reference
Last updated: 28 October 2026
A name, a description or a reference that exceeds its maximum length gets the file rejected or the text cut off by the bank. Some limits are in the schema, one only in the SEPA rules. Upload the file below to see which fields are too long and by how much.
Check your file for fields that are too long
Choose fileChecking is free. Repair if needed: €14.95 excl. VAT per file.
Our server checks your file in memory only, never saves it to disk and deletes it after 30 minutes at the latest.
- Error
- Length error (XSD or EPC rule)
- Where
- Nm, Ustrd, EndToEndId
- Repair
- Shortened automatically, except the mandate reference
What the error message looks like
Length errors are reported in English, in the bank portal, in the status file pain.002 and by the software that validates the file. Validators state the actual length and the maximum: libxml2 writes “[facet 'maxLength'] The value has a length of '151'; this exceeds the allowed maximum length of '140'.”, Xerces “cvc-maxLength-valid: … is not facet-valid with respect to maxLength '140'”.
XML schema validator (libxml2, for example xmllint and many online validators)
27: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}Ustrd': [facet 'maxLength'] The value has a length of '151'; this exceeds the allowed maximum length of '140'.
21: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}EndToEndId': [facet 'maxLength'] The value has a length of '38'; this exceeds the allowed maximum length of '35'.
Java validators (Xerces)
cvc-maxLength-valid: Value 'Contributie maart 2030 voor het seniorenlidmaatschap …' with length = '151' is not facet-valid with respect to maxLength '140' for type 'Max140Text'.
Your bank (status report pain.002)
CH16ElementContentFormallyIncorrect
In the status report, banks put the reason in the Rsn/Cd field. Online banking often shows a translation of it. CH16 means the content of a field is formally incorrect, which here means too long.
Our check
- The name is longer than 70 characters; the EPC allows 70.
- The value of <Ustrd> (remittance information) is too long (maximum 140 characters).
- The value of <EndToEndId> (end-to-end reference (EndToEndId)) is too long (maximum 35 characters).
Cause
The SEPA rules set three limits that matter in practice. A name (Nm) may have 70 characters under the EPC rules. The remittance information (Ustrd) may have at most 140 characters, and only one Ustrd is allowed. References such as MsgId, PmtInfId, EndToEndId and MndtId may have at most 35.
The name is the tricky one. The ISO schema of pain.008.001.08 allows 140 characters for Nm, so a validator does not complain about a name of 76 characters. Banks follow the EPC limit of 70 and may cut the name off or reject the file.
The example shows how this happens: the description lists the period, the membership type, every component of the fee and a member number at the end, 151 characters in all. The EndToEndId is built from readable text and reaches 38 characters instead of a short code.
How to fix it by hand
The best result is shortening the text yourself, so the important part stays. Cutting off simply removes the end, and that may be exactly what the debtor needs to recognise the payment, such as a member number.
- Look up the field the message names and count its characters.
- Shorten the remittance information to 140 characters or fewer, using abbreviations and keeping identifying details such as a member or invoice number.
- Shorten names to 70 characters, for example by abbreviating the legal form.
- Keep references at 35 characters or fewer; prefer a short code over descriptive text.
Before
<PmtId>
<EndToEndId>E2E-2030-0001-CONTRIBUTIE-MAART-SENIOR</EndToEndId>
</PmtId>
...
<RmtInf>
<Ustrd>Contributie maart 2030 voor het seniorenlidmaatschap inclusief zaalhuur,
materiaalbijdrage, bondscontributie, verzekering en clubblad, lidnummer 004417</Ustrd>
</RmtInf>After
<PmtId>
<EndToEndId>E2E-2030-0001-SENIOR</EndToEndId>
</PmtId>
...
<RmtInf>
<Ustrd>Contributie 03/2030 senioren incl. zaalhuur, materiaal, bond, verzekering, clubblad, lid 004417</Ustrd>
</RmtInf>The example shows a manual correction. The description is rewritten with abbreviations and keeps the member number 004417 at the end; the EndToEndId is shortened to a meaningful code. Truncation would have dropped the end, member number included.
How the tool repairs it
The check reports each field that is too long, including names over 70 characters that a schema validator lets through. The repair shortens names to 70 characters, merges several descriptions into one field of up to 140 characters and shortens the EndToEndId to 35 characters. As the change report shows, it truncates: the reference in the example becomes E2E-2030-0001-CONTRIBUTIE-MAART-SEN.
The mandate reference is never shortened, because it must stay identical to the signed mandate. Every change appears in the change report.
What the repair writes in the change report:
- Name shortened to 70 characters (was 76).
- Remittance information merged into one field of up to 140 characters: …
- Transaction reference (EndToEndId) E2E-2030-0001-CONTRIBUTIE-MAART-SENIOR → E2E-2030-0001-CONTRIBUTIE-MAART-SEN.
The tool cannot tell which part of a text matters most to you. If the end of a description carries important information, shorten it yourself in your software and check the file again.
Related pages
- SEPA mandate reference – what to do when the mandate reference itself is too long.
- Invalid characters – the other rule that applies to references.
- XML schema error – the general schema message, of which maxLength is one variant.
- All SEPA file errors – overview of all rejections on submission.
Frequently asked questions
How long may a name be in a SEPA file?
70 characters under the EPC rules. The ISO schema of pain.008.001.08 allows 140, which is why a validator does not report a longer name.
How long may the remittance information be?
At most 140 characters, in a single Ustrd field.
And references such as EndToEndId?
At most 35 characters, as for MsgId, PmtInfId and MndtId.
Why is my mandate reference not shortened?
It must stay identical to the signed mandate. Change it in your software and pass it on as a mandate amendment.
Sources
- European Payments Council: SDD Core Customer-to-PSP Implementation Guidelines 2025 – fields, lengths and the SEPA character set for direct debit files
- European Payments Council: 2025 SDD Core Rulebook, version 1.1 – rules of the SEPA Core scheme, including the earliest collection date
- ISO 20022: External Code Sets – the list of reason codes such as AM10, FF01 and CH16 used in status reports