Blocked vs Rejected Transactions Under Sanctions

When a payment hits a sanctions match, a compliance officer faces a decision that sounds simple but is legally loaded: do you block it or reject it? These are not synonyms. They are two distinct actions with different legal obligations, different handling of the money, and different reporting requirements. Choosing wrong — returning funds that should have been frozen, or freezing funds that should merely have been returned — can itself constitute a sanctions violation. Getting the distinction right is fundamental.

Blocking: freeze and hold

To block (or "freeze") a transaction means to stop it and retain the funds. The money does not go to the beneficiary and it does not go back to the sender. Instead, the institution places it into a segregated blocked account where it sits, frozen, until a licence or a change in the sanctions status permits its release. Blocking applies when a party to the transaction is a sanctioned person or entity whose property must be frozen — for example, someone on OFAC's Specially Designated Nationals (SDN) list. The legal theory is that the sanctioned party's property interest is captured and immobilised, denying them any benefit.

Blocking carries strict follow-on duties. In the US regime, blocked property must typically be reported to OFAC within a set period (historically within ten business days of blocking) and reported annually thereafter while it remains frozen. The funds sit in an interest-bearing blocked account and cannot be touched without authorisation.

Rejecting: refuse and return

To reject a transaction means to refuse to process it and return the funds to the sender or prior party, without holding them. Nothing is frozen. Rejection applies when a transaction is prohibited — perhaps it involves a sanctioned country or a prohibited activity — but there is no specific blocked person whose property interest must be seized. The institution simply declines to be the conduit and sends the money back where it came from. In the US, rejected transactions also carry a reporting obligation to OFAC, but the money is returned rather than retained.

The decision rule

The core question is whether a designated party's property interest is present in the transaction:

• If the transaction involves the property or interest of a specifically blocked person (such as an SDN), the funds must be blocked — you may not return them, because returning them would release a sanctioned party's property.
• If the transaction is prohibited for another reason — a comprehensively sanctioned jurisdiction, a banned good or service — but no blocked person's property is involved, it is generally rejected and returned.

This is why the two cannot be used interchangeably. Rejecting (returning) funds that legally had to be blocked would hand a sanctioned party their money — a serious violation. Blocking funds that only needed rejection wrongly freezes an innocent sender's money.

Why regimes differ

The block-versus-reject framework is most sharply codified in the US OFAC regime, but the underlying logic — freeze the property of designated persons, refuse prohibited dealings — appears across regimes including the UK and EU, which likewise require asset freezes for designated persons and prohibit dealings with sanctioned targets. The terminology and reporting mechanics vary, so a global firm must map each regime's rules rather than assume US definitions apply everywhere. What is constant is the principle that designated-person property is immobilised, not returned.

Operational implications

For payment operations, the practical consequences are concrete. Systems must be able to route a matched payment to a segregated blocked account, not just decline it. Staff must document why a given action was block versus reject, keyed to which list or provision was triggered. Reporting workflows must file the correct notice within the deadline. And crucially, screening must identify which element caused the match — a named SDN versus a jurisdiction — because that is exactly what determines the correct action. A match alert that does not tell the analyst why it fired makes the block-or-reject decision guesswork.

Key takeaways

• Blocking freezes and retains funds in a segregated account; rejecting refuses and returns them.
• Block when a designated person's property interest is present, such as an OFAC SDN.
• Reject when a transaction is prohibited but no blocked person's property is involved.
• Returning funds that should have been blocked, or freezing funds that only needed rejection, is a violation.
• Both actions carry reporting obligations, and systems must know why a match fired to choose correctly.