Compliance
Sending to hard places, legally: sanctions and OFAC for missions
One transfer to the wrong party can carry a penalty larger than your annual budget — and “I assumed the bank handled it” is not a defense. What sanctions compliance actually asks of a mission.
The transfer that looked routine, to a party you didn’t screen.
The scenario
A mission wires funds to a long-standing local partner to run a food program. Routine — they’ve done it for years. What no one on the team checked is whether anyone newly added to that partner’s organization, or the vendor they pay downstream, appears on a sanctions list. They assumed the bank was screening for that. Sometimes the bank is. Sometimes it isn’t — and either way, the legal responsibility never left the mission.
This is the uncomfortable part of moving money to hard places: U.S. sanctions law applies to you, the organization sending the funds, not only to your bank. A single transfer that touches a sanctioned party — even unknowingly, even for humanitarian ends — can trigger a penalty that dwarfs a year’s budget, plus the reputational damage of the headline.
The exposure most missions underestimate
Where sanctions liability actually sits
| Who’s responsible | Who assumes it | |
|---|---|---|
| Screening the recipient | You (the sender) | “The bank” |
| Screening downstream vendors | You | No one |
| Keeping evidence you screened | You | No one |
Sanctions law follows the sender. Where a mission assumes the bank has it covered, the liability quietly stays home.
The instinct, understandably, is to avoid hard places altogether — but that abandons exactly the people a mission exists to serve. The workable answer is not avoidance; it’s screening. Every party you pay, and ideally the parties they pay, checked against the current sanctions lists before the money moves, with a record that you did so.
Done by hand, that’s impractical for a small finance team — the lists change constantly and names transliterate a dozen ways. Done well, it’s automatic: screening runs on every transfer, flags what needs a human look, and keeps the evidence trail that turns “we tried” into “we complied.”
There’s also a licensing dimension worth knowing exists: for genuine humanitarian work, regulators provide general licenses and exemptions that make lawful transfers possible even into heavily sanctioned areas. Using them requires knowing they exist and documenting that you qualify — which is its own reason to work with partners who live in this world.
The takeaway: “we didn’t know” and “we assumed the bank checked” are not defenses. If you can’t show how every transfer is screened and how you’d prove it, that gap is sitting on your organization — not your bank’s.
Sanctions law follows the sender. “We assumed the bank handled it” has never once been a defense.
Where SNDR fits
SNDR screens every transfer against current sanctions lists through its regulated partners, flags what needs review, and keeps the evidence trail — so a mission can serve hard places and prove, at any moment, that it did so lawfully.