Rejection is declining and returning a transaction that touches a sanctions concern but does not require blocking, so the funds are not processed yet are not held either. It differs from blocking, where property is frozen and reported, and choosing the wrong action is a common, costly mistake.
What is rejection, in plain English?
Rejection is one of the two core outcomes when a payment hits a sanctions concern. Instead of moving the money forward, the institution declines the transaction and returns it to where it came from. The funds are not processed, but they are also not frozen, so control of the money goes back to the sender rather than being locked up.
Rejection applies when the prohibition bars the dealing but does not require you to hold the property. Whether rejection or blocking is correct depends on the specific prohibition, the parties involved, and the jurisdiction whose rules govern the payment. It is a legal determination, not a system default, which is why the same alert can demand different actions in different regimes.
Even though the money leaves, a rejection is not a silent drop. It still carries recordkeeping obligations, and in some regimes reporting obligations too. Operators have to document what was rejected, why, and under which authority, so the decision holds up under examination.
Rejection vs blocking
What changes | Rejection | Blocking |
What happens to funds | Returned to the sender, not processed. | Frozen and held; sender loses control. |
Trigger | Prohibited dealing that does not require holding property. | Property of a blocked person or subject to a freeze. |
Reporting | Recordkeeping, and reporting in some regimes. | Formal blocking report to the regulator, typically within days. |
Cost of getting it wrong | Over-rejecting disrupts legitimate flows. | Under-blocking lets frozen funds flow back out. |
How a rejection decision gets made
- Alert — Screening flags a nexus. A transaction hits a name, country, or instrument tied to a sanctions concern.
- Analyze — Identify the prohibition. The analyst pins down which authority applies, who the parties are, and what exactly is barred.
- Decide — Block or reject. If the rules require holding property, block. If they only bar the dealing, reject and return.RejectReturn fundsSend the payment back, keep the record.BlockFreeze and reportHold the funds and file the blocking report.
- Record — Document and report. Log the action and rationale; file any reporting the regime requires for rejections.
What it looks like in practice
In practice
A cross-border wire references a shipping route through a comprehensively embargoed country, but none of the named parties are on a blocking list. Screening raises an alert. The analyst determines the prohibition bars processing the payment but does not make the funds blockable property under the applicable authority.
The bank rejects the wire, returns it to the originating institution with a rejection notice, and records the reason and legal basis. Had the analyst treated this as a blockable case and frozen it, the bank would have held funds it had no authority to freeze; had it processed the wire anyway, it would have breached the embargo.
Why the choice matters
Rejection and blocking are not interchangeable, and picking the wrong one cuts both ways. If you reject when the rules required blocking, you hand control of funds you were supposed to freeze back to the sender, who simply reroutes them. That is a substantive sanctions failure, not a paperwork slip.
Go the other way and over-block, and you freeze money you had no authority to hold, exposing the institution to claims from customers and correspondents and tying up funds that should have moved. The correct action depends on the precise prohibition, so the value sits in the analyst's ability to read the specific authority rather than reaching for a default response.
What to watch in the data
- Default-action bias. Teams that always reject, or always block, are not reading the specific prohibition and will get cases wrong in both directions.
- Silent drops. A rejected payment that leaves no record fails the recordkeeping obligation even if the return was correct.
- Missed reporting. Some regimes require reporting on rejections, not just blocks; skipping it is a common oversight.
- Reroute after return. Funds returned by rejection that come back through a different route or party may signal evasion, not a clean decline.
- Jurisdiction mismatch. Applying one regime's block-or-reject logic to a payment governed by another regime produces the wrong action.
Quick questions
What is the core difference between rejection and blocking?
Rejection returns the funds to the sender without processing them; blocking freezes the funds so no one can move them. Blocking removes the money from circulation, while rejection just refuses to handle the transaction.
How do I know which one applies?
It depends on the specific prohibition, the parties, and the jurisdiction. If the funds are property of a blocked person or subject to a freeze, you block; if the dealing is barred but the property is not blockable, you reject.
Do I still have to keep records for a rejected transaction?
Yes. Rejections carry recordkeeping obligations, and some regimes require reporting the rejection as well. You cannot simply drop the payment without documenting what happened and why.
What is the danger of rejecting when I should have blocked?
You return control of the funds to the sender, who can send them again by another route. Money you were legally required to freeze flows back out the door, which is a serious sanctions breach.
Is rejection an admission that a transaction was suspicious?
Not necessarily. Rejection is a sanctions action tied to a specific prohibition. It is separate from suspicious activity reporting, though the same underlying facts may also warrant a review for a SAR.
Go deeper
- OFAC, US Treasury ↗ — Administers US sanctions programs, the SDN list, and licensing.
- European Banking Authority ↗ — EU banking regulator. Strong Customer Authentication under PSD2 and AML guidance.