<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Before You Name Your Kid, Check the SDN List</title>
	<atom:link href="http://www.exportlawblog.com/archives/136/feed" rel="self" type="application/rss+xml" />
	<link>http://www.exportlawblog.com/archives/136</link>
	<description>Latest News on DDTC, BIS, OFAC, and other export law matters</description>
	<lastBuildDate>Fri, 10 Feb 2012 10:06:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Daniel Garcia</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-35130</link>
		<dc:creator>Daniel Garcia</dc:creator>
		<pubDate>Mon, 22 Jun 2009 04:09:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-35130</guid>
		<description>My name is Daniel Garcia. Most of the time the OFAC list is a minor inconvenience but sometimes it is very irritating. Paypal put a hold on my account twice. In both cases it was without warning and I had to send them scans of bill statements and photo ID. In both cases it put my business on hold until the matter was sorted out. I have no idea why they needed to do this more than once and I&#039;m beginning to think it will probably happen every year.

In any evet I created a facebook group &quot;Daniel Garcias who don&#039;t like the OFAC SDN list&quot;

http://www.facebook.com/home.php#/group.php?gid=101114445317&amp;ref=nf</description>
		<content:encoded><![CDATA[<p>My name is Daniel Garcia. Most of the time the OFAC list is a minor inconvenience but sometimes it is very irritating. Paypal put a hold on my account twice. In both cases it was without warning and I had to send them scans of bill statements and photo ID. In both cases it put my business on hold until the matter was sorted out. I have no idea why they needed to do this more than once and I&#8217;m beginning to think it will probably happen every year.</p>
<p>In any evet I created a facebook group &#8220;Daniel Garcias who don&#8217;t like the OFAC SDN list&#8221;</p>
<p><a href="http://www.facebook.com/home.php#/group.php?gid=101114445317&amp;ref=nf" rel="nofollow">http://www.facebook.com/home.php#/group.php?gid=101114445317&amp;ref=nf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-1655</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 18 Apr 2007 03:18:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-1655</guid>
		<description>does this also apply to air travel?  my name IS Daniel Garcia and i ALWAYS get &quot;chosen&quot; as the passenger that has to get felt up before i board a plane.</description>
		<content:encoded><![CDATA[<p>does this also apply to air travel?  my name IS Daniel Garcia and i ALWAYS get &#8220;chosen&#8221; as the passenger that has to get felt up before i board a plane.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FormerOFAC</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-1433</link>
		<dc:creator>FormerOFAC</dc:creator>
		<pubDate>Thu, 29 Mar 2007 20:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-1433</guid>
		<description>What OFAC won&#039;t do (at least in my experience) is provide a &quot;comfort letter&quot; to clear someone whose identity has been confused with an actual SDN.  On the one hand, this can be an issue if someone has a name similar to an SDN and wants to avoid future run-ins with banks, etc.  But the rationale makes sense; i.e., OFAC is not in a position to prove negatives and it is bad practice to &quot;bless&quot; people, not to mention that OFAC simply doesn&#039;t have the resources to divert to whitelists.  So as AnotherFormerOFAC noted (trying to guess who you are...), someone who has been negatively affected by a false hit can petition to have funds released on a case by case basis.  Handling blocked funds cases was my first gig at OFAC, and I actually designed the form used on the website because the prior practice was to accept requests in any form, which slowed the process down considerably.  In any case, the SDN process is far from perfect--no arguments there--but IMO (and I am admittedly biased) OFAC administers it in a reasonable and thoughtful manner, all things considered.  Finally, I enjoy the blog and its irreverent style, a la the BSA Aerospace Export Control Update.  Keep tipping those sacred cows....</description>
		<content:encoded><![CDATA[<p>What OFAC won&#8217;t do (at least in my experience) is provide a &#8220;comfort letter&#8221; to clear someone whose identity has been confused with an actual SDN.  On the one hand, this can be an issue if someone has a name similar to an SDN and wants to avoid future run-ins with banks, etc.  But the rationale makes sense; i.e., OFAC is not in a position to prove negatives and it is bad practice to &#8220;bless&#8221; people, not to mention that OFAC simply doesn&#8217;t have the resources to divert to whitelists.  So as AnotherFormerOFAC noted (trying to guess who you are&#8230;), someone who has been negatively affected by a false hit can petition to have funds released on a case by case basis.  Handling blocked funds cases was my first gig at OFAC, and I actually designed the form used on the website because the prior practice was to accept requests in any form, which slowed the process down considerably.  In any case, the SDN process is far from perfect&#8211;no arguments there&#8211;but IMO (and I am admittedly biased) OFAC administers it in a reasonable and thoughtful manner, all things considered.  Finally, I enjoy the blog and its irreverent style, a la the BSA Aerospace Export Control Update.  Keep tipping those sacred cows&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AnotherFormerOFAC</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-1430</link>
		<dc:creator>AnotherFormerOFAC</dc:creator>
		<pubDate>Thu, 29 Mar 2007 14:38:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-1430</guid>
		<description>Whoever suggested the lack of recourse for someone whose name is a false positive is off base.  First, if funds get blocked on that basis, recourse is under 31 CFR §501.806 (&quot;Procedures for unblocking funds believed to have been blocked due to mistaken identity.&quot;)  Second, if other action has been taken because of mistaken identity, the Compliance Hotline (800-540-6322) can be used to clear up the false match.  Those on the hotline are, as FormerOFAC notes, patient and eager to assist.

Challenging the designation is usually not the appropriate recourse, since in most cases the bad guy whose designation caused the false name match is still a bad guy whose assets should still be blocked.  (As noted, if the designation itself is wrong, the actual designee can provide information to challenge the designation under 31 CFR §501.807.)  Finally, if it&#039;s laziness or ignorance in dealing with the SDN List that created a company&#039;s wrongful denial action, the possibility of a discrimination claim against the company is also out there.  The amount of information available on a terrorist, narcotics trafficker, or representative of a target government or group is not always adequate.

OFAC has done a reasonable job of fighting such designations. For example, it did not simply adopt the UN&#039;s lengthy list of Taliban names, many of them single, common Muslim first names, virtually all of which have hopelessly inadequate identifying information.  Recognizing that this would simply have resulted in &quot;false hit paralysis&quot; and widespread discrimination, the U.S. Government simply named the Taliban as a group and Mullah Omar as the sole identified individual.</description>
		<content:encoded><![CDATA[<p>Whoever suggested the lack of recourse for someone whose name is a false positive is off base.  First, if funds get blocked on that basis, recourse is under 31 CFR §501.806 (&#8220;Procedures for unblocking funds believed to have been blocked due to mistaken identity.&#8221;)  Second, if other action has been taken because of mistaken identity, the Compliance Hotline (800-540-6322) can be used to clear up the false match.  Those on the hotline are, as FormerOFAC notes, patient and eager to assist.</p>
<p>Challenging the designation is usually not the appropriate recourse, since in most cases the bad guy whose designation caused the false name match is still a bad guy whose assets should still be blocked.  (As noted, if the designation itself is wrong, the actual designee can provide information to challenge the designation under 31 CFR §501.807.)  Finally, if it&#8217;s laziness or ignorance in dealing with the SDN List that created a company&#8217;s wrongful denial action, the possibility of a discrimination claim against the company is also out there.  The amount of information available on a terrorist, narcotics trafficker, or representative of a target government or group is not always adequate.</p>
<p>OFAC has done a reasonable job of fighting such designations. For example, it did not simply adopt the UN&#8217;s lengthy list of Taliban names, many of them single, common Muslim first names, virtually all of which have hopelessly inadequate identifying information.  Recognizing that this would simply have resulted in &#8220;false hit paralysis&#8221; and widespread discrimination, the U.S. Government simply named the Taliban as a group and Mullah Omar as the sole identified individual.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clif Burns</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-1429</link>
		<dc:creator>Clif Burns</dc:creator>
		<pubDate>Thu, 29 Mar 2007 13:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-1429</guid>
		<description>FormerOFAC:  I agree with you completely.  The problem is not just the vagueness of the list, but the refusal of some people to take even minimal steps to verify a hit or use common sense.   The risk, of course, in failing to do that is that the company that simply refuses to do business with a hit without some checking risks a claim of discrimination as well.</description>
		<content:encoded><![CDATA[<p>FormerOFAC:  I agree with you completely.  The problem is not just the vagueness of the list, but the refusal of some people to take even minimal steps to verify a hit or use common sense.   The risk, of course, in failing to do that is that the company that simply refuses to do business with a hit without some checking risks a claim of discrimination as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mous, anony</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-1428</link>
		<dc:creator>mous, anony</dc:creator>
		<pubDate>Thu, 29 Mar 2007 13:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-1428</guid>
		<description>Really?  If it&#039;s really me on the list, I can challenge, but if its a false positive, I have no recourse?  Wow.</description>
		<content:encoded><![CDATA[<p>Really?  If it&#8217;s really me on the list, I can challenge, but if its a false positive, I have no recourse?  Wow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FormerOFAC</title>
		<link>http://www.exportlawblog.com/archives/136/comment-page-1#comment-1426</link>
		<dc:creator>FormerOFAC</dc:creator>
		<pubDate>Thu, 29 Mar 2007 11:50:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.exportlawblog.com/archives/136#comment-1426</guid>
		<description>I worked at OFAC for several years, and for a while I was a compliance officer manning the hotline, which mostly consisted of working through suspected false hits with banks from big to small, from New York money center institutions to community banks.  To be fair, with the often sketchy details given for SDNs, there were a lot of hits that were tough and I had a lot of patience for the folks who had to deal with the process (and the bureaucracy).  But some were just absurd -- my best was a hit on East Palestine, Ohio.  Um, it&#039;s not the PLO, buddy.  Still, with a private sector mentality even then I tried to be patient and clinical, and educate callers on best practices for screening.  Yes, OFAC needs to do a much better job with the SDN list.  I&#039;ve heard and seen many horror stories.  But it takes two to tango.  Instead of cursing the obvious darkness, some people need to light a candle and use a bit of common sense.  On a positive note, now that I&#039;m in-house handling trade compliance, I am unusually sensitive to all sides of the story.  Just my two cents....</description>
		<content:encoded><![CDATA[<p>I worked at OFAC for several years, and for a while I was a compliance officer manning the hotline, which mostly consisted of working through suspected false hits with banks from big to small, from New York money center institutions to community banks.  To be fair, with the often sketchy details given for SDNs, there were a lot of hits that were tough and I had a lot of patience for the folks who had to deal with the process (and the bureaucracy).  But some were just absurd &#8212; my best was a hit on East Palestine, Ohio.  Um, it&#8217;s not the PLO, buddy.  Still, with a private sector mentality even then I tried to be patient and clinical, and educate callers on best practices for screening.  Yes, OFAC needs to do a much better job with the SDN list.  I&#8217;ve heard and seen many horror stories.  But it takes two to tango.  Instead of cursing the obvious darkness, some people need to light a candle and use a bit of common sense.  On a positive note, now that I&#8217;m in-house handling trade compliance, I am unusually sensitive to all sides of the story.  Just my two cents&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

