Santander SEPA XML Guide: EndToEndId Length and Character-Set Warnings

Santander's profile shares its core configuration with BBVA — both are Spanish AEB/CSB-34 legacy banks that moved to pain.001.001.03 with a forced salary category for payroll runs — but the validator applies two Santander-specific warnings on top of that shared baseline.

What the implemented Santander profile writes and checks

Common warnings and the direct fix

• SAN_001: EndToEndId Length. A warning rather than a hard failure — but keep your end-to-end reference at 16 characters or fewer where possible, since a longer value is more likely to be truncated or rejected further down Santander's processing chain even if this validator lets it through.
• SAN_002: Santander Charset. Accented characters, punctuation beyond a plain space, and non-Latin scripts in the creditor name will trigger this warning. Santander's Spanish legacy heritage (AEB/CSB-34) makes this stricter than the ISO 20022 default; simplify the name field rather than assuming UTF-8 will pass through untouched.

Prepare Excel without creating a repair queue

1. Keep end-to-end references short and numeric/alphanumeric — under 16 characters — rather than embedding a long invoice description.
2. Strip accents and special punctuation from creditor names before upload; a plain alphanumeric name with spaces clears SAN_002 cleanly.
3. Select Santander when generating for payroll runs — the forced salary category applies automatically and does not need a separate mapping choice.