Guides · Updated 2026-10-18
Charge bearer SLEV in SEPA credit transfers
In a SEPA credit transfer the charge bearer (ChrgBr), when given, must be SLEV ("following service level"). SHAR, DEBT and CRED are valid ISO 20022 codes but not allowed in SEPA, and the guidelines recommend giving the charge bearer once at payment information level.
The rule
Both rules are based on EPC132-08 2025 v1.0, section 2.1.1, items 2.75 and 2.98.
- SEPA-SCT-CHRGBR-001BLOCKERCharge bearer must be SLEV. When the charge bearer is given for a SEPA credit transfer, only SLEV (following service level) is allowed.
- SEPA-SCT-CHRGBR-002INFOCharge bearer recommended at payment information level. The guidelines recommend specifying the charge bearer at payment information level rather than per transaction.
Where SHAR usually comes from
Check which payment method and format configuration produced the file: a configuration shared with non-SEPA payments, where other charge bearer codes are allowed, is a frequent source. Setting the charge bearer to SLEV for the SEPA payment method fixes it.
Download a synthetic file with SHAR to see the finding.
Questions
Is the charge bearer mandatory in a SEPA pain.001?
BankLint checks the value when it is given: it must be SLEV. The guidelines recommend specifying it at payment information level rather than per transaction.
Validate a pain.001 fileFree, no account needed, files are not stored.