Brief
A block opens an account
Rejecting and freezing as two endings for one refused payment
Bottom line
A sanctions program tends to treat refusal as one outcome. The regimes treat it as two. Where a designated person holds an interest in the money, the firm freezes it and becomes its custodian: the balance stays on the firm’s books, earns interest, keeps receiving credits, resists debits, outlives the customer relationship, and generates a report every year until a licence releases it. Where a prohibition reaches the transaction while the money itself carries no designated interest, the firm declines and returns it, files one report in the United States, and the matter closes. The two endings share a screen, a decision, and a disappointed customer, and they share little else. A ledger with one failed state represents the second outcome correctly and the first one hardly at all.
1. Two endings for one refusal
OFAC states the division plainly. Its Frequently Asked Question 36 explains that a transaction is rejected rather than blocked where the transaction falls under a prohibition while no blocked person holds an interest in it: the firm declines to process it, and it goes back to the originator. Blocking applies where a blockable interest exists, and FAQ 32 describes what follows from that. The funds go into an interest-bearing account on the firm’s own books, and only OFAC-authorized debits may be made from it.
The Russia program supplies a working example of each. A payment in which a person blocked under Executive Order 14024 holds an interest is blocked. A payment caught by Directive 2 under the same order, the correspondent and payable-through account prohibition, is rejected: OFAC’s FAQ 967 tells US financial institutions to reject such transactions unless OFAC exempts or authorizes them, and describes the directive as imposing that rejection duty in place of blocking sanctions.
The same division runs through the other two regimes under different vocabulary. The United Kingdom’s asset freeze in regulation 11 of the Russia (Sanctions) (EU Exit) Regulations 2019 holds the funds of a designated person, while regulation 17A on correspondent banking relationships and the processing of payments, and regulation 18A on financial services relating to foreign exchange reserve and asset management, prohibit activity that leaves the firm holding nothing afterward. In the Union, Article 2(1) of Regulation 269/2014 freezes a listed person’s funds, while Article 5b(1) of Regulation 833/2014 prohibits accepting deposits above EUR 100 000 per credit institution from Russian nationals, natural persons residing in Russia, and entities established there. A deposit above that cap has to go back. A deposit belonging to a listed person has to stay. The cap reads nationality and residence, which are two of the three attributes A passport answers one question keeps apart, and the freeze reads an ownership chain, which is the arithmetic in One cap table, several answers.
Those are two different questions arriving at the same alert queue, which opened on a name match whose quality One person, several spellings treats as a design decision rather than a vendor default. The answer to the first question then determines which of two legal objects the firm creates in the next minute.
2. What binds, and what advises
Read by layer, as From rule to workflow uses the word:
- Law. 31 CFR 501.603 requires a report within 10 business days from the date property becomes blocked, and an annual report, due by September 30, covering all blocked property held as of June 30. 31 CFR 501.604 requires any US person who rejects a transaction to report it within 10 business days, stating the legal authority for the rejection and attaching copies of the payment instructions. 31 CFR 587.203 requires blocked funds to sit in a blocked interest-bearing account in the United States, earning a commercially reasonable rate, which the section defines as the rate currently offered to other depositors on deposits of comparable size and maturity. Regulation 70 of the Russia Regulations obliges a relevant firm to inform the Treasury as soon as practicable once it knows or has reasonable cause to suspect that it holds funds or economic resources for a person subject to the prohibitions, and, where it has so reported and still holds them, to report their nature and amount each year by 30 November as at 30 September. Article 8(1) of Regulation 269/2014 requires any natural or legal person to supply information on frozen funds to the competent authority of the Member State where they are resident or located within two weeks of acquiring it.
- Guidance. OFAC’s FAQs 32, 36, and 967 draw the line between the two outcomes and describe what each one obliges. OFSI’s notice for the annual frozen assets review sets the current return at 30 November 2026 and addresses it to everyone holding or controlling a designated person’s funds, which reaches wider than the defined class of relevant firms. The Financial Conduct Authority’s May 2026 findings describe what weak freezing looks like in supervised firms. Guidance of this kind binds nobody by itself, and it is the clearest available statement of what each regulator expects to see.
- Policy. Which of the firm’s own debits are suppressed against a frozen balance and which are escalated; who holds authority to authorize a return; whether a frozen customer keeps access to statements and support; whether the firm records a refusal in the same form everywhere, including the regimes that ask for no filing. Each of those is risk appetite, and belongs in writing with an owner and a reason.
- Convention. One transaction status reading “failed”, and one account status reading “closed”, applied by whoever worked the alert. This is the layer the piece argues against, because a single word is being asked to carry two legal outcomes with opposite consequences.
3. The report follows the outcome
| Regime | When the money goes back | When the money stays | What comes round again |
|---|---|---|---|
| United States | a report to OFAC within 10 business days under 31 CFR 501.604 | a report within 10 business days of the property becoming blocked, under 31 CFR 501.603 | an annual report by September 30 on holdings as of June 30 |
| United Kingdom | regulation 70(1), where the firm knows or has reasonable cause to suspect a designated person or a breach | notice to the Treasury as soon as practicable under regulation 70(1ZA) | a report by 30 November under regulation 70(1ZB), on holdings as at 30 September |
| European Union | Article 8(1), under the general duty to supply information facilitating implementation | information on the frozen funds to the competent authority, within two weeks of acquiring it | Member State practice, with the listed person separately reporting its own funds under Article 9(2) |
Three things follow from reading the columns across.
The United States is the only one of the three that reports the act of refusing as such. The United Kingdom and Union duties attach to knowledge, to suspicion, and above all to holdings, which means a UK or Union firm with an immaculate record of returned payments has satisfied a duty that was mostly about something else. A firm operating in all three places needs a rejection record anyway, because the US filing demands the legal authority relied on and the original instructions, and reconstructing either one a week later costs far more than capturing it at the moment of refusal.
A block, by contrast, recurs. Each regime builds in an annual beat: September 30 in the United States, 30 November in the United Kingdom, and in the Union a cycle the competent authority runs, with Article 9(2) separately obliging the listed person to report its own funds within six weeks of listing. The object the firm created on a Tuesday afternoon reports itself for as long as it exists.
And the Union’s duty reaches backward. Beyond the funds now frozen, Article 8(1) asks for information the firm holds on funds belonging to a listed person that were moved, transferred, altered, accessed, or otherwise dealt with in the two weeks preceding the listing. A firm reading that provision for the first time discovers it owes an account of payments it already completed, lawfully, before anybody knew a listing was coming. The data to answer it had to exist in advance, which makes it a storage decision taken long before the sanctions question arrives. It has the shape of the problem in Knowledge arrives after the payment, where a finding lands once the money has already moved, with the difference that what it triggers here is a report rather than a hold.
4. A frozen balance keeps running
The intuition behind “frozen” is a thing held still. The texts describe something closer to a live account under restriction.
It earns. 31 CFR 587.203 requires the funds to be placed in a blocked interest-bearing account, at a commercially reasonable rate, with any instrument capped at 180 days’ maturity. The interest itself is blocked, so the balance grows while staying immobile.
It receives. Article 7(1) of Regulation 269/2014 permits a financial or credit institution to credit a frozen account with funds a third party transfers to a listed person, provided the additions are frozen too, and it obliges the institution to inform the competent authority about any such transaction without delay. Article 7(2) does the same for interest and other earnings, for payments due under contracts or obligations that arose before the listing date, and for payments under judicial, administrative, or arbitral decisions. Incoming money reaches a frozen account by design, each arrival enlarges the custody, and in the Union each arrival is reportable on its own.
It attracts the firm’s own debits. This is where the Financial Conduct Authority found the damage. Its May 2026 findings list the management of frozen assets among the most common root causes of reported sanctions breaches, alongside due diligence, alert management, and transaction and name screening. The section on asset freezing describes arrangements that were weak and procedures that were insufficiently documented, accounts left under no appropriate restriction while a potential match was being investigated, and an absence of service level agreements governing how quickly an account gets frozen. Among the reported breaches it cites firms failing to maintain frozen assets properly, where internal transactions moved funds or applied charges to accounts.
That last phrase deserves its own sentence. The likeliest source of a prohibited debit against a frozen balance is the firm itself, through a fee schedule or a sweep or a chargeback that posts automatically on a calendar of its own. A maintenance fee charged to a frozen account needs its own permission, and A licence leaves the proof with the firm describes what that permission costs to rely on.
- A prohibition reaches the payment
- An outcome chosen: returned to the originator, or frozen on the firm's books
- A frozen balance opened, with every credit, accrual, and attempted debit recorded against it
- Each report filed on the schedule its regime sets, for as long as the balance exists
- Release on a licence, or on a delisting
5. The exit a block forecloses
Closing the account and sending the balance back is the standard answer to a customer a firm decides to stop serving. Applied to frozen funds, that sequence is the prohibited act itself: a debit from a blocked account calls for authorization, and the UK and Union equivalents call for a licence or a derogation. The Financial Conduct Authority names the omission in terms, listing among poor practices a failure to take account freezing obligations into account when a client is offboarded over potential sanctions concerns.
Offboarding is therefore a product flow with a sanctions precondition, and the precondition has to be checked inside the flow rather than beside it. The customer relationship ends while the custody relationship begins, and the second one has the longer life. Years later the firm still holds the money, still reports it annually, and still answers for every entry posted against it, long after the account stopped appearing in any commercial review. Whoever runs that balance needs the written brief that A human in the loop needs a job description asks for, since by then the people who froze it have moved on.
A worked hypothetical
The following scenario is hypothetical and is included only to illustrate the framework. The companies and people below are invented.
A payments platform runs three entities: one in the United States, one in the United Kingdom, and one established in a Member State. A corporate customer, Meridian Freight, holds a balance with all three. On a Tuesday the parent of Meridian’s majority shareholder is designated, and the ownership arithmetic carries the block down to Meridian itself.
Four things are in flight.
- An outbound payout to a supplier. Meridian holds the interest, so each entity freezes the funds rather than returning them. The US entity moves the balance into a blocked interest-bearing account and files within 10 business days. The UK entity notifies the Treasury as soon as practicable. The Union entity sends the competent authority the frozen-funds information inside two weeks.
- An inbound card settlement, already in the clearing cycle. It lands in a frozen balance, where it stays, frozen in its own right, and increases a figure the firm now owes an account of every year. For the Union entity the credit carries a duty of its own, since Article 7(1) asks the institution to tell the competent authority about the transaction without delay.
- A wire from an unrelated customer to a bank covered by Directive 2. Nobody blocked holds an interest in that money, so the US entity rejects it, returns it, files the reject report with the authority and the original instructions, and the matter closes the same week. One screen produced both outcomes within an hour of each other.
- The monthly platform fee, scheduled for the first. It is a debit against a frozen balance posted by the firm’s own billing service, which knows about invoices and knows nothing about designations.
Ten days on, the offboarding automation picks Meridian up as a sanctions exit and queues the closing balance for return to the customer’s external bank account, which is the one debit the freeze most clearly forbids. The queue is held because a reviewer happens to recognize the name. The control the firm actually needed was a precondition inside the closure flow, which would have held the queue on its own, whoever happened to be reading.
The Union entity then works through the second limb of Article 8(1) and finds a payout it completed four days before the designation. The payment was lawful when it was made and is reportable now, and the only reason the firm can describe it is that the ledger kept the counterparty, the amount, and the date in a form somebody could query.
Eleven months later Meridian is still a customer in every sense that costs the firm money and in no sense that earns it any: a balance under restriction, an annual return, an interest accrual, and a named person who answers for all three.
6. Failure modes, and the measures that expose them
- One status for both outcomes. Measure the share of refusals carrying a recorded legal authority and a recorded outcome. A population where the outcome field holds one value is reporting a control that exists in name.
- The firm debiting its own frozen balances. Count debits attempted against frozen balances by originating system, and how many posted. The interesting number is the count by system, since it names which team owns the next fix.
- A slow freeze. Measure elapsed time from the decision to the restriction taking effect in every system able to move the money, rather than to the flag being set on the customer record. This is the gap the Financial Conduct Authority found firms leaving unmeasured.
- An unreported credit. Count arrivals into frozen balances against the notifications they generated, in each regime that asks for one. A frozen balance whose credit count and notification count agree is a balance somebody is actually running.
- A missed recurrence. Track each annual return against the balances open on its as-at date, and treat a balance released during the year as an item the return still has to explain.
- An exit that releases funds. Count closures initiated on accounts carrying a frozen balance and record the stage at which each one stopped. A closure stopped by a person is a near miss; a closure stopped by the flow is a control.
- Unreconstructable rejections. Sample rejected transactions and attempt to rebuild the filing from stored data alone. Whatever a reviewer has to ask a colleague for is a field the system should have kept.
What this changes operationally
A sanctions owner maps each prohibition the firm is subject to onto the outcome it produces, a return or a freeze, and publishes that mapping with a date and an owner, which is what From recurring question to durable control asks of any decision that recurs.
A product lead gives the ledger a frozen state that is live and restricted, separate from returned and separate from closed, and puts the freeze check inside the closure and payout flows rather than beside them.
A data engineer stores the legal authority and the outcome beside each refusal, keeps the counterparty, amount, and date queryable far enough back to answer a look-back that arrives after the fact, and records every credit, accrual, and attempted debit against a frozen balance.
An operations lead files each report inside its own window, holds a calendar for the annual returns in each regime the firm touches, and treats a posted debit against a frozen balance as an incident rather than a correction.
A finance lead treats a frozen balance as a long-lived liability with an interest obligation attached, and plans for an account that earns, receives, and reports for years with no commercial relationship behind it.
Limitations
This concerns control design and evidence for the two outcomes a sanctions refusal produces. It offers no view on whether any particular transaction should be returned or frozen, which is a question for counsel against the current text and the facts, and it describes no institution’s program. Which regimes bind a firm turns on where its entities are established and where its business is done. Designations, directives, and licences change often, so the examples here hold as of the dates given.
The three-way contrast describes the default architecture of each regime. Member State practice under Regulation 269/2014 varies, including on how holdings are reported after the initial submission, and a firm has to record which practice applied to each balance. Regimes beyond these three, the parallel measures on Belarus, and the sectoral programs that produce rejections on grounds other than a designation, raise the same structural question and are left aside. Crypto custody adds a further wrinkle, since the asset sits at an address rather than in an account, and the duties described here were drafted for the account.
Primary sources
- US Department of the Treasury, OFAC. 31 CFR 501.603, on reports of blocked property, including the 10 business day initial report and the annual report due September 30 covering holdings as of June 30; 31 CFR 501.604, on reports of rejected transactions, including the 10 business day deadline and the required contents.
- US Department of the Treasury, OFAC. Russian Harmful Foreign Activities Sanctions Regulations, 31 CFR Part 587, in particular 31 CFR 587.203 on the holding of blocked funds in interest-bearing accounts.
- US Department of the Treasury, OFAC. Frequently Asked Questions 32 (how to block an account or funds transfer), 36 (what rejecting a transaction means and when it applies), and 967 (Directive 2 under Executive Order 14024, the correspondent and payable-through account prohibition).
- United Kingdom. The Russia (Sanctions) (EU Exit) Regulations 2019, regulation 11 (asset-freeze), regulation 17A (correspondent banking relationships and processing payments), regulation 18A (financial services relating to foreign exchange reserve and asset management), and regulation 70, paragraphs (1), (1ZA), (1ZB), and (2).
- HM Treasury, Office of Financial Sanctions Implementation. Annual frozen asset review and reporting form, for the review running to 30 November 2026.
- Council of the European Union. Council Regulation (EU) No 269/2014: Article 2 (the freeze and the prohibition on making funds available), Article 7 (crediting of frozen accounts, and the duty to inform the competent authority without delay), Article 8 (information on frozen funds and the two-week look-back), and Article 9(2) (reporting by the listed person), in the consolidated text of 24 February 2025.
- Council of the European Union. Council Regulation (EU) No 833/2014, Article 5b, in the consolidated text of 24 July 2026.
- Financial Conduct Authority. Sanctions systems and controls in our firms: our findings (May 28, 2026), section 6.1 on the most common root causes of reported breaches and section 6.12 on asset freezing and licence compliance.