Skip to content
All insights
ComplianceNovember 16, 2026 · 8 min read

OFAC voluntary self-disclosure: what to do when a sanctions breach is found after the payment settled

An OFAC voluntary self-disclosure halves the base penalty, and stops counting once somebody else reports first. The test, the lookback and the sequence.

By Jay Kambo
Illustration — OFAC voluntary self-disclosure: what to do when a sanctions breach is found after the payment settled
Key takeaways
  • A disclosure is voluntary only if the firm gets there first. Under 31 CFR Part 501 Appendix A it is not voluntary once OFAC or another agency has learned of the apparent violation from another source, including a third party under its own duty to report.
  • The credit is large and mechanical. In each branch of the egregiousness matrix in the Enforcement Guidelines the base penalty is halved where there was a voluntary self-disclosure.
  • A blocked property report under 31 CFR 501.603 is mandatory and due within ten business days. Filing it on time discloses nothing, because it is not a voluntary self-disclosure.
  • The lookback is now ten years. Legislation enacted in April 2024 extended the limitation period for violations of the International Emergency Economic Powers Act, and OFAC's September 2024 interim final rule matched the record retention rule to it.
  • Notify early and briefly, then report fully. The initial notice is a timestamp and the full account is the substance, and nothing requires the review to be finished before the notice goes in.

A sanctions breach is rarely found when it happens. It surfaces weeks later, in a screening tuning review, a payout partner's question, or a new list entry that matches a client already on the books. The payment has settled. The money has moved. What the firm decides next matters more than the breach itself, because an OFAC voluntary self-disclosure is the largest piece of credit in the enforcement framework. It stops being available the moment somebody else tells OFAC first.

This article sets out what a voluntary self-disclosure is, when a disclosure stops being voluntary, what it changes about the penalty, how far back the review must reach, the sequence that leaves usable evidence, and what an on-chain settlement leg adds. It describes a regulatory process, not legal advice.

What is an OFAC voluntary self-disclosure, and what is it not?

A voluntary self-disclosure is a self-initiated report to OFAC of conduct that appears to have breached a sanctions programme the agency administers. OFAC calls that conduct an apparent violation. Civil liability is strict, so intent is not an element. A firm can breach a prohibition in good faith, with a screening engine that ran and a reviewer who cleared the hit for a reason that looked sound. The question in an enforcement review is rarely whether the breach happened. It is what the firm knew, when it knew it, and what it did next.

Three filings get confused with one another, and they answer to different rules. A blocked property report under 31 CFR 501.603 is due within ten business days of blocking, and a rejected transaction report under 31 CFR 501.604 runs on the same mandatory clock. A suspicious activity report goes to FinCEN and never reaches OFAC. A voluntary self-disclosure is separate from all three. Filing a blocked property report on time does not disclose the apparent violation that produced the block, and a firm that assumes otherwise has disclosed nothing.

When does a disclosure stop being voluntary?

The Economic Sanctions Enforcement Guidelines at 31 CFR Part 501 Appendix A set the test, and it is narrower than most policies assume. A disclosure is voluntary only when the firm notifies OFAC before the agency, or another agency, has learned of the apparent violation elsewhere. It is not voluntary when a third party under its own duty to report has already reported it, nor when the notice adds nothing to what OFAC already holds, nor if the firm then declines to cooperate.

That makes the clock real. A correspondent bank that rejects the payment may file its own report the same week. A payout partner answering its regulator may name the counterparty. An employee may call a hotline. None of that is in the firm's control. The credit for disclosure decays from the day of discovery, so the decision to notify should not wait for the review to finish.

What does a voluntary self-disclosure change about the penalty?

OFAC's response runs along a scale. The agency may take no action, send a cautionary letter, issue a finding of violation, impose a civil monetary penalty, settle, or refer the matter for criminal prosecution. It can also compel documents by administrative subpoena under 31 CFR 501.602. Where a case lands on that scale is a judgement, and the Guidelines say how it is reached.

The first split is egregiousness. The Guidelines weigh whether the conduct was wilful or reckless, whether managers knew, how much the programme objectives were harmed, and whether the firm had a sanctions compliance programme at all. The second split is the disclosure. In each branch of that matrix the base penalty is halved where there was a voluntary self-disclosure. For a non-egregious case the base is measured from the transaction value, subject to a cap per violation. For an egregious case it is measured against the applicable statutory maximum.

Eleven general factors, labelled A to K in Appendix A, then move the number up or down. Two reward work done before the breach: the quality of the compliance programme, and the remedial response. Two reward work done after it: cooperation with OFAC, including whether the firm agreed to toll the limitation period, and the deterrent effect of the outcome. OFAC's May 2019 framework document names the five components it expects in a programme, which are management commitment, risk assessment, internal controls, testing and auditing, and training. It also lists the root causes it keeps seeing, and a disclosure that names its own root cause in those terms reads very differently from one that does not.

A voluntary self-disclosure is not an apology. It is evidence, filed by the only party that can still choose when it arrives.

How far back does the lookback have to reach?

Further than it used to. Legislation enacted in April 2024 extended the statute of limitations for civil and criminal violations of the International Emergency Economic Powers Act and the Trading with the Enemy Act from five years to ten. OFAC's September 2024 interim final rule followed, amending the record retention requirement in 31 CFR 501.601 to ten years, with the change taking effect in March 2025. A review that stops at five years now stops short of the exposure.

Scoping is the hard judgement. The review should reach every payment that shares the root cause, not only the payment that surfaced. If a list was loaded late, the scope is every payment screened against the stale list. If a beneficial owner was never identified, the scope is every payment for that client. Sampling is defensible where the population is large, provided the method is written down before the results are known.

Two mechanics matter while the review runs. Funds already blocked stay blocked, because returning them is itself a dealing in blocked property and needs a licence. And the review should run under counsel from the start, so privilege is available over the analysis, even though the underlying facts are not.

What does the disclosure sequence look like in practice?

The order is what produces usable evidence. Running it out of order usually destroys some.

  • Freeze the position first. Hold the funds, suspend the client relationship or the corridor that produced the breach, and stop the activity before anything else.
  • Preserve the record. Put a legal hold on the screening logs, the reviewer notes, the message files, the partner correspondence and the chain transaction references.
  • File the mandatory reports on their own clock. A blocked property report is due within ten business days under 31 CFR 501.603, and it is not a disclosure.
  • Notify OFAC early and briefly. An initial notice names the apparent violation, the programme involved, the dates, and the fact that a review is under way.
  • Scope the lookback in writing. Record the root cause, the population, the sampling method and the ten year reach before the first result is read.
  • Fix the control, not the case. A rules change, a list refresh schedule or a second reviewer is the part of the file that argues for mitigation.
  • File the full account. Set out what happened, the complete transaction schedule, the root cause in the terms of OFAC's 2019 framework, and the remediation with dates.
  • Keep the file for ten years. The retention period in 31 CFR 501.601 now matches the limitation period, so the evidence has to outlive the people who made it.

One point on sequencing is worth stating plainly. The initial notice and the full report are different documents, and treating them as one is how a firm loses the credit.

What does an on-chain settlement leg change about a sanctions breach?

It changes the evidence more than the duty. A stablecoin transfer is final in minutes and cannot be recalled by instruction, so the window in which a payment can be stopped sits before release rather than after it. That is a control design point, not a legal one. The prohibition is the same whether the value moved along a correspondent chain or across a public ledger.

Three practical differences follow. The counterparty address is a fact anyone can check, so a lookback over on-chain legs can be reconstructed rather than assembled from correspondent enquiries. A token issuer can freeze a balance independently of the firm, which can leave the firm reporting blocked property it does not control, and the report has to say so. And the firm's own records carry the whole burden for party data, because a public ledger carries none, so the pacs.008 and pacs.009 messages, the UETR and the Travel Rule payload are the only place the originator and beneficiary exist.

The conclusion for a payments team is unglamorous. Because the settlement leg is irreversible, screening, ownership analysis and beneficiary verification have to clear before release, and the proof that they did has to survive for ten years. A breach found later is a disclosure decision, and the quality of the file decides how it goes.

Where StableNet fits

StableNet, built by SpendTheBits, settles cross-border B2B payments for banks, credit unions, licensed money service businesses, exchange houses and remittance fintechs in regulated stablecoins, completing in minutes with on-chain auditability. Because the settlement leg is final, the controls run before release: KYB and KYC onboarding, KYT, sanctions and PEP screening, Travel Rule data under IVMS101, and a compliance workbench over all of it, written to a tamper-evident audit trail. Every transfer produces ISO 20022 messages, a pacs.008 for the customer credit transfer and a pacs.009 for the interbank leg, with pacs.004 for returns inside a head.001 envelope and a UETR end to end. That is the file a lookback reads from.

See it on your corridors

Book a working session and we’ll map StableNet’s compliance and settlement to one of your live payment flows.

FAQ

Common questions

No. Nothing requires a firm to tell OFAC about an apparent violation. Blocked property reports under 31 CFR 501.603 and rejected transaction reports under 31 CFR 501.604 are mandatory and run on a ten business day clock, but the disclosure of the underlying breach is a choice. The Enforcement Guidelines simply make it a very well rewarded one, and the reward disappears once OFAC learns of the matter from another source.