Archive for the ‘OFAC’ Category


Dec

20

Credit Bureaus and Merchants Point Fingers at Each Other over SDN Issues


Posted by at 10:35 pm on December 20, 2012
Category: OFAC

Finger PointingAn article that appeared yesterday on Yahoo News details the war between merchants, consumers and credit bureaus when credit bureaus supply information to merchants indicating that the merchant’s customer is on the Office of Foreign Assets Control’s List of Specially Designated Nationals and Blocked Persons, more commonly known as the SDN list. We’ve discussed the issue before but there are a number of names on the SDN list that are common names that are likely shared by a large number of people and the bad guy. The credit bureaus have been sending reports to their customers that indicate hits based on the name alone, without respect to other information in the SDN listing such as date of birth,  leading to consumers being denied credit or services.

Not surprisingly, when denied consumers howl, the credit bureaus say it is the merchant’s obligation to determine if the customer is one the SDN list, and the merchants and customers are saying it’s the credit bureau’s obligation to do further investigation before simply sending the name match as part of its report. Moreover, some credit bureaus are claiming that the OFAC information isn’t part of the credit report, but a separate product, and is therefore not subject to the Fair Credit Reporting Act.

In one case, Cortez v. Transunion, 617 F. 3d 688 (3d Cir. 2010), the Third Circuit sent such an argument packing, holding that the FCRA does apply to the OFAC information and that Transunion breached its duty under the act by failing to maintain adequate procedures to guarantee the accuracy of the reports it supplies to merchants and lenders. The Court also held that Transunion violated its obligations under the FCRA to provide, upon request, a notice to the consumer of the OFAC information and the opportunity to contest it. Since the consumer has no right, at least according to OFAC, to have OFAC clarify that he or she is on the SDN list, it becomes doubly important that consumers at least have the right to contest the appearance of the misleading OFAC information on their credit reports.

I can’t post something on this new story without commenting on this passage early on the story:

Lenders are supposed to check the list each time they receive a new application for credit and face steep penalties of up to $10 million if they don’t. The rule went into effect in 2003 as part of the USA Patriot Act’s broader efforts to kneecap terrorists’ ability to finance a life in the U.S.

To state that the obligation to check the SDN list was first imposed in 2003 by the PATRIOT Act is, of course, utter hogwash. Everyone has been required to check the SDN list for long before that or face penalties if they engaged in transactions with persons or entities on the list. The article is presumably referring to section 326 of the PATRIOT Act, which required Treasury to adopt rules for financial institutions compelling them to adopt a procedure to determine customer identity and to check that identity against the SDN list and similar government lists. Section 326, which applies only to financial institutions, thus, requires those institutions to establish procedures to fulfill their existing obligations to check these lists, an obligation that has been in place for financial institutions and all U.S. persons since at least 1994.

Permalink Comments (1)

Bookmark and Share


Copyright © 2012 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)

Dec

6

Standard Chartered Says It Will Settle Fed Charges on Iran for $330 Million


Posted by at 11:57 pm on December 6, 2012
Category: Iran SanctionsOFAC

Standard CharteredDuring a call today with financial journalists, the Finance Director of Standard Chartered Bank stated that he expected the bank to settle for $330 million federal charges that it violated U.S. sanctions on Iran. Although this settlement has not been announced by the Office of Foreign Assets Control (“OFAC”), the statement by a senior official of the bank suggests that such a settlement must be close even if final documents have yet to be inked by all involved. This would be on top of the $340 million which Standard agreed to pay the New York Department of Financial Services in connection with the banks transactions with Iran.

I criticized the NYDFS action because it included transactions that were perfectly legal under OFAC’s “U-Turn” exception prior November 2008. However, it seemed clear that the bank continued to process U-Turn transactions with Iran even after OFAC eliminated that exception. The U-Turn transaction exception, until it was eliminated, permitted a U.S. bank to clear certain dollar transactions involving Iran by foreign non-Iranian banks. Thus, the federal charges against Standard, which did not attempt to penalize transactions permitted under federal law at the time, are on a completely different footing than the State charges which covered, at least in part, transactions that were permitted under the Iran regulations.

Permalink Comments Off on Standard Chartered Says It Will Settle Fed Charges on Iran for $330 Million

Bookmark and Share


Copyright © 2012 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)

Dec

3

I Hate Snakes (And So Does The Pentagon)


Posted by at 8:53 pm on December 3, 2012
Category: Iran SanctionsOFAC

Oxus CobraLike Indiana Jones, I hate snakes, and so doing this post (and especially the picture at the right) was a bit unsettling, but the story was just too good to pass up. According to an article in today’s Wall Street Journal (subscription required), the Pentagon is buying snake bite drugs from Iran. Apparently Afghanistan is crawling with venomous snakes (like the Oxus cobra pictured on the right), and Iran’s Razi Vaccine & Serum Research Institute is one of the few manufacturers and purveyors of the anti-venin needed to combat snake bites in Afghanistan. Indeed, DoD medical guidance explicitly states that the Razi vaccines “should be the first line of antivenin therapy.”

My, oh my, what a mess. After being contacted by the Wall Street Journal reporters in connection with the story, Pentagon lawyers are apparently trying to figure out whether these purchases violate U.S. sanctions against Iran. (Some free advice for those lawyers: the answer is yes.) And OFAC says it’s working with DoD to “confirm the details of these purchases to ensure compliance” with the U.S. embargo on Iran.

Don’t expect to see DoD paying a fine to OFAC (although the schadenfreude of such an outcome is hard to deny). Individual government employees involved in the anti-venin deals might be slightly more nervous, although one could imagine the intensity of the backlash against OFAC for even issuing a warning letter to military personnel who were, after all, just trying to save our troops, even if they were violating federal law and endangering national security in the process. (The money paid to Razi — $35,650 according to the WSJ — was almost certainly the last $30,000 standing between Iran and the bomb.)

The best part of the story is the reaction of Hadi Zareh, lead researcher in Razi’s antivenin department. He said:

We make this to save lives, and it doesn’t matter if the person is Iranian or Afghan or American. We are happy to hear we have saved a person’s life, even an American soldier.

He went on to say, however, that U.S. sanctions were making it more difficult for Iran to produce the drug saving American lives in Afghanistan, noting that the sanctions were making it “very difficult to buy chemical products for the laboratories and some of the equipment that we need.”

It’s funny how the Iran sanctions might be an economic version of “friendly fire.”

Permalink Comments (2)

Bookmark and Share


Copyright © 2012 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)

Nov

15

Diamonds Are An Ogre’s Best Friend


Posted by at 2:13 pm on November 15, 2012
Category: OFACZimbabwe Sanctions

Robert Mugabe
ABOVE: Robert Mugabe

A report in the Zimbabwe Herald, the state-owned mouthpiece for the Mugabe dictatorship, provides an entertaining, if somewhat fictive, account of the recently concluded Zimbabwe Diamond Conference in Victoria Falls. The purpose of the conference was to provide some support for the diamond industry in Zimbabwe which, although free of Kimberly Process Certification issues, is severely crippled by economic sanctions imposed by the U.S. Office of Foreign Assets Control against the Mugabe regime.

The pro-Mugabe news outlet had this to say:

KIMBERLEY Process Certification Scheme chairperson Mrs Gillian Milovanovic yesterday came under fire from delegates attending the inaugural Zimbabwe Diamond Conference here for failing to protect Zimbabwe’s diamond industry from America. Delegates expressed concern that Zimbabwe’s diamond sector continues to face obstacles despite the country receiving the KP’s nod to trade its gems.

They unanimously agreed that the American approach towards Zimbabwe’s gems sought to promote conflict diamonds.

During an open session, delegates said Mrs Milovanovic, who is American, should recuse herself from chairing the KP because she was failing to protect Zimbabwe from America’s Office of Foreign Assets Control sanctions.

This blog has noted before that the Kimberly Process certification and OFAC sanctions against the Zimbabwe Mining Development Corporation (“ZMDC”), which has a monopoly on sales of Zimbabwe diamonds, deal with completely separate issues.

The Kimberly Process certification is limited to finding that the certified diamonds are not conflict diamonds, which are defined as ‘“rough diamonds used by rebel movements or their allies to finance conflict aimed at undermining legitimate governments.” Obviously, Zimbabwe diamonds aren’t being used to undermine a legitimate government; indeed, they are being used to prop up the existing dictatorial regime in Zimbabwe.

The OFAC sanctions, however, arise not from any insurgency or rebel conflict in Zimbabwe. Instead, they are premised on human rights abuses by the Zimbabwe dictatorship. In the case of ZMDC, OFAC sanctions are presumably a response to documented reports of torture and forced labor in the diamond fields run by ZMDC.

Just because something isn’t a conflict diamond under the Kimberly Process, doesn’t mean it isn’t a blood diamond.

[For extra added amusement, unrelated to export issues, look carefully at the caption to the picture illustrating the Herald story.]

Permalink Comments (2)

Bookmark and Share


Copyright © 2012 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)

Oct

11

Executive Order on Foreign Subs in Iran Issued


Posted by at 8:58 pm on October 11, 2012
Category: Iran SanctionsOFAC

Iranian proliferationThe recently passed Iran Sanctions, Accountability, and Human Rights Act of 2012 eliminated a loophole that permitted foreign subsidiaries of U.S. companies to trade with and in Iran as long as no U.S. persons were involved in the transaction. On October 9, the White House released the Executive Order required under the act implementing its provisions. Not surprisingly, the Executive Order mostly parrots ITRSHRA (pronounced eye-TRASH-rah”), but it does manage to clarify one matter and muddle up another.

So let’s start with what it clarifies. Section 218(d) of ITRSHRA provided an exemption for penalties if the foreign subsidiary was divested within 180 days from the passage of the act. There was some thought that this might mean that the foreign subsidiary could stop the business in Iran within the 180-day period and then avoid penalties even without divestment. That is not the case under the Executive Order. If your foreign subsidiary was doing business with Iran on October 9, 2012, or after, you have until February 6, 2013, to divest that subsidiary in order to avoid the penalties provided under the act.

Now for what gets muddled. Under Section 218(b) of ITRSHRA, any foreign entity owned or controlled by a U.S. person is forbidden from engaging in any transaction with “the Government of Iran or any person subject to the jurisdiction of the Government of Iran” if such transaction would violate U.S. sanctions on Iran if engaged in by a U.S. person. The concept of a “person subject to the jurisdiction of Iran” is not found in the existing sanctions regulations and executive orders. These generally prohibit dealings with the Government of Iran (anywhere in the world) or with Iran (meaning with private citizens and non-governmental entities in Iran.) So the executive order defines “person subject to the jurisdiction of Iran” as follows:

a person organized under the laws of Iran or any jurisdiction within Iran, ordinarily resident in Iran, or in Iran, or owned or controlled by any of the foregoing.

Now part of that definition is not problematic. Current regulations would prohibit dealings with persons and businesses while they are in Iran, but this definition also captures Iranian corporations and Iranian residents while they are outside Iran. Under current law, U.S. persons (as opposed to the foreign subsidiaries of U.S. persons covered by ITRSHRA) can deal with non-governmental and unblocked Iranians and Iranian corporations outside Iran provided that those dealings do not result in the export of goods or services back into Iran.

Under the Executive Order, however, it would appear that U.S. foreign subsidiaries can’t deal with private unblocked Iranians and Iranian corporations anywhere in the world whether or not those dealings would lead to the export of good or services back to Iran or the Government of Iran. So if a U.S. subsidiary owned a cab company in Baghdad, it could not pick up any Iranian and give them a ride, even though Yellow Cab in DC can pick up an Iranian and drive him from his hotel to the Washington Monument or wherever else he wants to go.  There is, however, no evidence that Congress intend to impose stricter sanctions on U.S. subsidiaries overseas with respect to Iranians outside Iran than it imposed on domestic U.S. corporations.  Instead, Congress’s intent was clearly to make the same prohibitions applicable both to overseas subsidiaries and their domestic U.S. parent companies.

Perhaps  this conundrum is solved by the part of the new prohibition that says that the transaction is prohibited “if that transaction would be prohibited” by current orders and regulations “if the transaction were engaged in by a United States person or in the United States.”   To try to determine what this means, lets take as an example Section 560.204, which prohibits the exportation of “goods, technology, or services to Iran or the Government of Iran.” Now if you say that this means that no transaction is prohibited unless it involves persons in Iran or the Government of Iran, then there was no need for a definition of “person subject to the jurisdiction of Iran,” particularly where that definition includes a broader classes of entities such as private Iranian corporations outside Iran.  Even so, it seems that this reading is more consistent with Congress’s intent.

Alternatively, you could try to make sense of this restriction to transactions that would be prohibited to U.S. persons is by saying that it means that the transaction isn’t subject to one of the existing exemptions in the regulations such as the informational exception. In that case, the restriction would mean that a foreign subsidiary of a U.S. company in France can sell a pre-existing book or DVD to an Iranian travelling in France but couldn’t sell him a pair of pants.  This interpretation leads to a result that it is hard to imagine was intended by Congress.

Presumably OFAC is going to amend its regulations to take the new executive order into account. Let’s hope that OFAC recognizes the existence of these two conflicting interpretations and clarifies in its Regulations which one is correct . Let’s also hope that one day the Cubs will win the World Series.

Permalink Comments Off on Executive Order on Foreign Subs in Iran Issued

Bookmark and Share


Copyright © 2012 Clif Burns. All Rights Reserved.
(No republication, syndication or use permitted without my consent.)