Skip to content
SEPA RR04

Regulatory reason

Category: Regulatory R-type: Reject / Return

SCT

Applies

SCT Inst

Applies

SDD Core

Applies

SDD B2B

Applies

Retryable

No — compliance review required

Generated by

Debtor bank, beneficiary bank, or the compliance function in the payment chain.

ISO 20022 definition

Regulatory Reason.

Typical cause

Sanctions screening hit, AML block, or another regulatory hold on either side of the transaction — the reason is not further specified.

What to do about it

Do not retry without compliance review and escalation. RR04 in particular may reflect a sanctions hit or AML flag — treat as a compliance case, not a retriable technical failure.

Rulebook note

Shared across SCT, SCT Inst, and SDD. The least specific of the four RR codes — used as a catch-all where the bank cannot or will not disclose the exact regulatory trigger.

Confidence: high. Sourced from PaymentBrief's SEPA R-transaction reference article, cross-verified against ISO 20022 external code sets and EPC guidance documents. Reason-code applicability and timing windows vary by rulebook version and bank handling — verify against your bank or PSP before acting.

Full reference

SEPA Return and Reject Codes: The R-Transaction Reference

Related codes

RR01

Missing debtor account or identification

RR02

Missing debtor name or address

RR03

Missing creditor name or address