Rule reference · SEPA Credit Transfer scheme rules · Service level
SEPA-SCT-SVCLVL-002: Only one service level occurrence allowed
The ISO 2019 message allows several service levels, but SEPA allows only one occurrence.
| Severity | BLOCKER Blocker: the run fails |
|---|---|
| Status | Requirement of the guidelines |
| Applies to | pain.001.001.09, SEPA Credit Transfer |
| Elements checked | /Document/CstmrCdtTrfInitn/PmtInf/PmtTpInf/SvcLvl /Document/CstmrCdtTrfInitn/PmtInf/CdtTrfTxInf/PmtTpInf/SvcLvl |
| Source | EPC132-08 2025 Version 1.0, section 2.1.1, items 2.8 and 2.85 |
| Rule pack | sepa.sct.pain001.v09 v1, effective 2025-10-05 |
Why it matters
Multiple service levels are outside the SEPA core subset.
How to fix it
Remove additional service level entries.
Try it with a synthetic example
These files are synthetic test data from BankLint's test corpus. Download one, or validate it directly.
- Two SvcLvl occurrences (ISO 2019 allows many, SEPA one). FAIL · Download · Validate it
Related rules: Service level
- SEPA-SCT-SVCLVL-001: Service level code must be SEPA
- SEPA-SCT-SVCLVL-003: Service level is recommended
Validate a pain.001 fileFree, no account needed, files are not stored.