Foreign investments in the infrastructure sector throughout South America is the subject of the newly released ABA Business Law Section book (entitled Foreign Investment in South America: A Comprehensive Guide to Infrastructure and the Legal Environment), which enters the conversation at the right moment: when the majority of the countries in that region are encouraging investments in order to modernize their social-economic environment and foster development.
The Brazilian Constitution of 1988 established a new scenario for Brazilian socioeconomic development. Since 1988, the Brazilian legal framework has strongly fostered national and international companies’ investment in infrastructure through concessions and the privatization of several sectors—logistics, electric power, sanitation, oil and gas, mining, and telecommunications, among others.
In 2004, the PPP Act (Law 11,079) created new possibilities for private investment in infrastructure through public-private partnerships. The PPP Act establishes general rules for the bidding process and contracting out with private partners at both national and sub-national levels, in accordance with the Public Procurement Act (Law 8,666/1993). Among its features, the PPP Act allows public administration entities to assume long-term commitments, including the payment of subsidies to the private partner, with the overall objective of increasing efficiency.
With a favorable economic scenario, as from 2007, the federal government has launched public-private investment programs directed at socioeconomic development. The Development Furthering Program (Programa de Aceleração do Crescimento or PAC) and the Logistics Investments Program (Programa de Investimento em Logística or PIL) were extremely important in promoting good planning and proper execution of large works in social infrastructure, urban energy, and logistics in Brazil, all contributing to speedy, sustainable development.
In 2016, Law 13,334 introduced the Investment Partnership Program (Programa de Parceria de Investimentos or PPI), which aims to expand interaction between the state and the private sector through partnership agreements in order to implement public infrastructure projects and other privatization measures. The PPI does not create new modalities of public procurement, but only encourages and facilitates infrastructure projects with the use of contractual modalities that involve intensive and long-term investments, which are legally classified as “partnerships.”
The PPI’s purposes include: (i) increasing investment opportunities, creating jobs, and stimulating technological and industrial development in line with the country´s social and economic development goals; (ii) ensuring the enhancement and expansion of public services and infrastructure projects at a reasonable cost to users; (iii) promoting full and fair competition for the provision of services; (iv) ensuring stability and legal certainty on agreements with minimal government intervention in businesses and investments; (v) strengthening the state’s regulatory role as well as the autonomy of the regulatory agencies.
When the government identifies a project as qualified for the PPI, it should then be addressed as national priority. The agencies and other administrative entities involved should then guarantee that the actions necessary to the structuring, release, and execution of the project occur efficiently and economically.
As noted in December 2017, of the 145 projects eligible under the PPI, 70 assets have already been auctioned. It corresponds to the 48% execution of the schedule established by the federal government. Their estimate of investments with public sale is BRL 142 billion; with concessions, it is BRL 28 billion.
The Brazilian socioeconomic scenario is attractive for the Brazilian Development Bank (BNDES), which finances not only large-scale projects, but also small and medium-sized companies, individuals, and public entities. BNDES is the main funding agent for infrastructure projects. In 2016, BNDES launched BNDES Finem, a long-term financing project which may encourage greater participation from the private financial sector and capital market in infrastructure works considered a priority for the PPI, most of which are related to sanitation, logistics, urban mobility, energy, telecommunications, or oil and gas.
There are other financing sources available via state-owned banks and some national and international commercial banks, as well as some private equity firms focused on long-term investments. Debentures are also used to facilitate corporate funding for infrastructure projects.
Law 12,431/2011 introduced new debenture rules to encourage the private sector to finance long-term infrastructure projects, specifically in logistics and transport, urban mobility, energy, telecommunications, broadcasting, sanitation and irrigation. One of the most important changes was reducing tax on the income from debentures issued by Special Purpose Entities (Sociedade de Propósito Específico or SPE) companies organized to conduct infrastructure investment projects or projects for intensive economic production in research, development, and innovation considered a priority by the Brazilian government; these are known as infrastructure debentures. Infrastructure debentures may be issued on the local market, ‘packaged’ in depositary receipts, and traded (with a tax reduction) in the international secondary market directly by foreign investors.
Additionally, the government extended the same tax benefit to investment funds backed by infrastructure debentures. According to Law 12,431/2011, the tax benefit applies to income from investments in infrastructure debentures issued by an SPE or by companies that hold a concession, permission, or authorization to execute infrastructure projects or intensive economic production in research, development and innovation deemed to be federal priorities.
The Brazilian government also attempts to support innovation in order to raise productivity and competitiveness and to create wealth for Brazil. Law 10,973/2004, known as the Innovation Act, aims at incentivizing Brazil’s technological and industrial development by enabling strategic partnerships between universities, technological institutes and companies that all share the pursuit of knowledge as a central element. The recently enacted Law 13,243/2016 amended Law 10,973/2004 with the purpose of fostering research and scientific and technological development by encouraging partnerships between public and private sectors, as well as at reducing the red tape that interferes with investment in the relevant sectors.
Among other things, the new framework creates the concept of Scientific, Technological and Innovation Institutions (ICTs) which can be established as public entity or non-profit private entity incorporated under Brazilian law. The articles of association for an ICT include scientific or technological research or development of new products, services or processes in their purposes.
The federal government also establishes tax incentives for legal entities that develop technological innovation in the Brazilian territory. Through Law 11,196/2005, known as Lei do Bem or Law of Goodness, companies, universities and research institutes are granted several tax incentives to maximize their work in research and development (R&D), such as the reduction of 20.4% to 34% in corporate income tax charged for R&D expenditures and the reduction of 50% of the fiscal year tax on the acquisition of assets designated for R&D, among others.
In light of this, it is possible to conclude that Brazilian legal framework has been quite favorable to public and private investments in several sectors of infrastructure, which are essential for the country’s sustainable development by creating jobs and increasing people’s income.
Effective settlement agreements convert the risks, delays, and expenses of lawsuits into solutions that the parties choose for themselves. Many settlement agreements are reached as the product of mediation, a process that helps parties transform misunderstanding into understanding, conflict into resolution, and the stress of litigation into freedom from worry. Settlement agreements do not instantly spring into being, however, fully formed and ready to be enforced. Moreover, many issues can be addressed in an effective settlement agreement only with advance preparation. Unfortunately, many attorneys who would not dream of showing up unprepared for trial will arrive at a mediation without having done their homework. Betsy A. Miller and David G. Seibel report in “Untapped Potential: Creating a Systemic Model for Mediation Preparation” in Volume 64 of Dispute Resolution Journal (2009) that one survey of experienced litigators found that “[a]lmost none said they spend more than an hour or two to prepare specifically for the mediation process.” Yet, lack of preparation to draft an agreement may doom the agreement for lack of necessary information, such as who should sign the agreement, what the jurisdiction requires for a valid agreement, and what terms are unlawful or otherwise unavailable. The importance of preparation for success in resolving a legal dispute warrants the following tips for how to prepare to write an effective settlement agreement.
Research potential terms of a settlement agreement. Understanding possible settlement options may itself facilitate agreement in allowing for creativity within the limits of the law. Begin by identifying the terms that have the potential to help resolve the particular case to be mediated. For example, insured claims resolved by settlement agreement tend to involve payment in exchange for release of legal liability. For cases such as these, a minimum of preparation requires consideration of whether payment will be made as a lump sum, in a series of payments, or via annuity. In addition, the scope of the release must be considered—whether it extends only to known claims or includes unknown claims, encompasses only claims made, or includes claims that could have been asserted.
Discuss possible solutions to the legal dispute with clients before the mediation. One exhaustive survey of commercial settlement agreements discussed in Settlement Agreements in Commercial Disputes: Negotiating, Drafting and Enforcement by Richard A. Rosen et. al (Aspen 2015) concluded that “there is no such thing as a ‘boiler plate’ settlement agreement.” In other words, there is no one-size-fits-all solution that can be used to settle cases. For this reason, attorneys must engage their clients in discussions about possible solutions to their legal conflict as part of their work in preparing clients for mediation. Sophisticated business people and frequent mediation participants might have specific terms and proposals they expect to include in a final agreement. Institutional clients might provide settlement agreements they have used in the past to help with preparations.
Gather the necessary documents. Before the mediation session, gather all potentially applicable insurance policies, medical bills, liens, statements of fees and costs associated with the litigation, and any other document bearing on the ultimate value of a settlement agreement. For a breach of contract claim, gather not only the primary contract, but also any subcontracts and side agreements. Read these documents with an eye toward settlement by watching for fee-shifting provisions, indemnification clauses, and subrogation agreements.
Ascertain the exact legal claims and parties. In protracted litigation, it may have been a long time since anyone read the operative legal complaint or cataloged which claims actually remain pending. With surprising regularity, even the attorneys of record have a mistaken understanding of the exact scope of pending causes of action. Rather than guessing, attorneys should review the operative complaint to determine the existing causes of action and exact identity of the parties to the lawsuit. Attorneys should pay attention to claims that could be, but have not yet been, asserted in order to determine the appropriate scope of a release of liability in a settlement agreement.
Prepare in advance for any transfer of property. If the legal dispute involves claims over property such as a house, a business entity, or negotiable instruments, preparation often means obtaining an appraisal to determine the value of the property. Documents establishing title, possession, or a leasehold also may be necessary to write an agreement that properly refers to the property to be transferred. Some transfers of property, such as out-of-state real property, may require substantial investigation to determine condition, valuation, and requirements for transfer.
Determine the type of the release needed. Consider the procedural posture of the legal dispute. If a lawsuit has not yet been filed, a covenant not to sue might make most sense to prevent further conflict. If the settlement agreement is to address ongoing litigation, a release of liability and a plan for dismissal of the case is likely more appropriate. Releases come in many permutations: releases of only claims made, releases of claims made and those that could have, but have not yet, been asserted, releases based on known facts only, releases of known and unknown claims, and more.
Lay the groundwork to settle an insured claim. Insurance is a strange product. The buyer pays in hopes of never using it. The seller hopes to never pay on it. Even so, insurance policies play an integral part of many settlement agreements. The potential applicability of insurance coverage to a legal claim can make finalizing a settlement easier in some respects and more difficult in others. The availability of insurance proceeds to fund or contribute to a settlement increases the likelihood that the parties can agree on an amount to be paid for release of the legal claims. However, the world of insurance comes with its own set of rules, procedures, and timelines that vary from insurer to insurer. It is too late to begin pondering insurance coverage at the end of a mediation session. Preparation for an insured claim settlement agreement should begin at least two to three months before any mediation begins.
Determine whether the case involves, or even potentially involves, any payments by Medicare to the injured party. If the case to be settled involves any claims for medical expenses, attorneys must consider the possibility that Medicare has a claim to at least part of the settlement proceeds. Medicare, which pays medical expenses for qualifying elderly and disabled individuals, is considered to be a “secondary payer.” This means that Medicare can recover any payments it has made from a “primary” payer, such as automobile or liability insurance as well as the proceeds of a settlement agreement. See 42 U.S.C. § 1395y(b)(2)(A); see also Taransky v. Sec’y of U.S. Dept. of Health & Human Serv., 760 F.3d 307 (3d Cir. 2014). The consequences of misjudging the amount of settlement funds to set aside for Medicare can be dire if the plaintiff is cut off from further Medicare payments (and thus medical care) until the reimbursement is made. Conversely, when Medicare is not reimbursed by the plaintiff, the defendant is liable for double damages plus interest, even if the defendant has fulfilled the terms of the settlement by paying the plaintiff.
Consider whether confidentiality will likely be a term. Confidentiality regarding a settlement agreement’s terms or very existence requires careful thought about which communications are to be restricted and which are to be allowed. Parties may agree that their private conflict should not be shared with outsiders or on social media, but the parties may need carve-outs to allow them to comply with applicable statutes, regulations, and court orders requiring disclosure. Carve-outs are often framed to include spouses and tax advisors. To be sure, discouraging breach of confidentiality is a delicate balancing act. An insufficient penalty will not incentivize compliance, whereas an excessive penalty will not be enforced by the courts. Thus, the scope and penalty should be carefully considered ahead of time along with the possible tax consequences that apply upon inclusion of a confidentiality provision.
Write a rough draft before the negotiations or mediation commence. Given that a blank page can be a formidable opponent for any writer, attorneys may wish to begin by surveying settlement agreements in similar cases. If the current case lies in an area of law in which the attorney frequently practices, the attorney may have comparable settlement agreements from which to draw. However, attorneys must resist the temptation to automatically cut-and-paste their way into new agreements without critically evaluating whether old boilerplate remains legally valid and is factually applicable to the case being settled. Ideally, the process of preparing to draft potential settlement terms generates ideas for workable solutions as well as revealing issues that must be resolved in order to end the conflict. At the very least, a carefully prepared draft will help avoid the risk of omitting important terms or including void terms.
Preparation is tremendously important to drafting an effective settlement agreement. Effective settlement agreements help parties move beyond the wrongs of the past and into a future in which their expectations and obligations are known, and where the parties are absolved of the litigation resolved in the agreement.
As litigators are aware, the cost of discovery is a significant component of the cost of litigation, a fact the U.S. Supreme Court noted in 2007 in Bell Atlantic Corp. v. Twombly, 550 U.S. 544, 559 (2007), when it stated that “the threat of discovery expense will push cost-conscious defendants to settle even anemic cases . . . .” Given the rapid expansion of the volume of electronic data in our society, it is no surprise that both the discovery of electronically stored information, or “e-discovery,” and disputes relating to e-discovery can further exacerbate the burdensome cost of litigation. When resolving e-discovery disputes, the parties must weigh the relevance, proportionality, cost, and accessibility of information. At least one court has commented that weighing these factors and working out the practical, technical method of producing the relevant electronic records “is a cooperative undertaking, not part of the adversarial give and take.” In re: Seroquel Prods. Liab. Litig., 244 F.R.D. 650, 660 (M.D. Fla. 2007). Given the number of complex factors that must be balanced and the substantial risk to the parties arising from an adverse e-discovery ruling, more parties are turning to mediation to resolve e-discovery disputes. Mediation can provide a forum for litigants to explore potential alternatives to cost-effectively exchange information relevant to the underlying litigated dispute. By mediating e-discovery issues, litigants can limit the time and cost associated with seeking judicial intervention, control the cost of electronic discovery, maintain confidentiality, and avoid potential adverse results, such as sanctions.
In the e-discovery arena, mediation can be used either to create a mediated e-discovery plan or to resolve underlying disputes regarding electronically stored information. A skilled mediator who is knowledgeable about e-discovery can facilitate the negotiation and resolution of complicated e-discovery issues without judicial intervention. Further, by eliminating acrimonious discovery battles, mediating e-discovery disputes can also improve the prospect of settlement of the underlying litigation.
Who Should Participate? The success of any mediation depends upon the participation of those persons whose input or consent is needed to reach an agreement. This is certainly true of mediations of e-discovery disputes. In addition to the decision makers for the respective parties and litigation counsel, e-discovery mediations should include IT personnel or other technical consultants who have knowledge of the parties’ electronically stored information systems. The participation of IT personnel and/or IT consultants who are familiar with the litigants’ electronic systems and capabilities is key to successful e-discovery mediation.
Preparation for e-Discovery Mediation. Electronic information can take many forms, including active data, inactive data, metadata, deleted data, ghost data, legacy data, archived data, and back-up data. In advance of e-discovery mediation, it is imperative that counsel becomes familiar with the type of information stored and how it is stored, preserved, retrieved, and produced, as well as the cost of producing it. In addition, counsel should become familiar with the inventory of storage devices used by the client, the location and ownership of those devices, the client’s retention policies, and any automatic deletion procedures that may need suspending. Counsel should also become familiar with the client’s data mapping and systems mapping.
Mediation Statement. The parties should prepare a confidential mediation statement and deliver it to the mediator well in advance of the mediation. The mediation statement should include the following:
the identity of the persons who will attend the mediation, including all IT representatives and whether the IT representatives are employees of the litigant or hired consultants, and if the IT representative is a hired consultant, the scope and nature of the consultant’s engagement with the litigant;
a candid discussion of potential issues identified by counsel, including potential spoliation issues, cost concerns, timing issues, and specific privilege concerns;
a candid assessment of the technological capacity of both the litigant and counsel’s law firm together with any proposed solutions to obvious deficiencies in their respective capacities;
a disclosure of whether any depositions of corporate representatives have been taken regarding electronically stored information, and if any such depositions have been taken that elicited testimony regarding electronically stored information that would help the mediator understand the electronic landscape, a notation of any relevant testimony and copies of relevant portions of the deposition transcripts; and
if the specific purpose of the e-discovery mediation is to resolve disputes arising from discovery requests already propounded in the litigation, a summary of the specific disputes and copies of the discovery requests, responses and objections, motions to compel, relevant scheduling orders, and related documents.
Issues to be Addressed Through Mediation. Although the issues to be addressed through e-discovery mediation will vary with the procedural posture of the litigation and the specifics of the dispute at hand, the issues likely to be addressed through e-discovery mediation include:
the scope of reasonably accessible electronic data to be preserved and reviewed;
the search parameters to be used to locate electronic data;
the method of review to be employed;
the data format for preservation and production;
the time and manner of production;
the procedures for handling inadvertently produced privileged information;
the potential need for protective orders;
the methodologies to evaluate compliance with any e-discovery plan or mediated e-discovery agreement; and
the mechanism and protocol to enforce any mediated e-discovery plan or mediated e-discovery agreement.
The outcome of e-discovery mediation, e.g., an agreed e-discovery plan or an agreement resolving objections to propounded discovery requests, should be reduced to writing and signed by all parties and counsel according to the appropriate rules governing mediation in the jurisdiction of the litigation.
E-discovery mediation can provide litigants with a confidential venue to efficiently manage the discovery of electronically stored information. Mediation can help parties control e-discovery costs, maintain confidentiality, and avoid potential adverse results, such as the imposition of sanctions. Although mediation will not eliminate all e-discovery disputes, it is a tool to reduce or eliminate e-discovery motion practice that should not be overlooked.
In Law vs. Zemp, 362 Or. 302 (Jan. 11, 2018), the creditor Robert Law held an Oregon judgment against the debtor Ronald Zemp. The creditor moved for the entry of a charging order against Zemp’s interests in four limited partnerships and a limited liability company (the companies) in which Zemp was the general partner of the partnerships and manager of the LLC.
The form of the charging order proposed by the creditor contained, in addition to the typical language of such orders that placed liens on Zemp’s interests, five additional provisions as follows:
The companies were to make no loans.
The companies were to make no capital acquisitions without the approval of the creditor or the court.
The companies were not to sell or modify any interests without the approval of the creditor or the court.
The companies were to provide lots of information to the creditor, including their partnership or operating agreements, federal and state income tax returns, balance sheets, etc.
The companies were to provide financials to the creditor within 30 days of the close of each accounting period.
None of these was expressly authorized by Oregon partnership and LLC law, which merely provides—as nearly all such statutes do—that the court may charge (lien) a debtor’s interest in such companies until the judgment has been paid in full, and until that time the creditor is only to be considered a voluntary assignee of the interests, which carries almost no other rights than the lien rights.
Zemp didn’t defend against the creditor’s motion, but the companies appeared and asserted various objections. First, the companies claimed that Zemp held no interest in the companies. Second, the companies claimed that the five ancillary provisions mentioned above were not authorized by Oregon law and would adversely affect the companies’ operations.
The creditor made various arguments of his own, including that Zemp in fact controlled the companies and was operating them as a “class asset protection program” rather than as bona fide commercial enterprises.
The trial court overruled the companies’ first objection that Zemp had no interest, and then granted the charging order with four of the ancillary provisions, leaving out only the one that required the companies to provide various information and tax returns to the creditor.
Making its way up to the Oregon Court of Appeals, the issue in the case was whether the ancillary provisions allowed by the trial court were proper. The higher court noted that although the ancillary provisions were not provided by Oregon’s partnership and LLC laws, there existed a general statute that allows a court to “make all other orders, directions, accounts and inquiries the judgment debtor might have made or that the circumstances of the case might require.”
Under this general statute, the Oregon Court of Appeals held as to the four partnerships that the trial court had the power to order the companies to disclose financial information because Zemp himself (as general partner or manager) had that power. Given that Zemp did not have the unilateral power to make loans, capital acquisitions, or change the interests, however, those provisions were improper. Even as to the last point, the court remanded the case back to the trial court to determine whether those provisions were necessary to ensure the companies’ compliance with the charging order.
As to the LLC, the court held that relying upon the general statute was not permissible because the Oregon LLC Act did not have a provision that incorporated it by reference (unlike the Oregon Limited Partnership Act). Therefore, all the ancillary provisions were improper as to the LLC.
The court’s ruling satisfied neither the creditor nor the companies, so everybody appealed the decision to the Oregon Supreme Court.
Oregon’s highest court first set out a lengthy review of the history of Oregon’s partnership and LLC acts, particularly as they related to charging orders. The court noted that charging orders exist to prevent “an obvious invasion of the rights and interests of nondebtor partners and resulted in disruption of the partnership business and, often, a forced dissolution of the partnership,” which would occur if the creditor simply levied on a debtor’s interest, as happens with corporate shares.
Against this historical backdrop, the court then looked at the particular issues in this case, beginning with the ancillary provisions as directed to Zemp’s four partnerships.
The companies argued that ancillary provisions should not be allowed at all with the partnerships because (their argument distilled to its essence) the general statute allowing courts to make additional provisions to effectuate their orders had been superseded by the specific charging order provisions of the Limited Partnership Act, i.e., they argued the “General Rule,” which is that “general rules are generally inapplicable.”
The court didn’t buy the argument that the Oregon legislature intended to cut out the general statute when it enacted Oregon’s partnership laws. To the contrary, the drafters of Oregon’s ULPA anticipated that supporting law could come from other provisions of Oregon law. That the charging order remedy is supposed to be the “exclusive remedy” under Oregon’s statute didn’t change that.
Yet, even the general statute had its limitations, and as applied here it meant that ancillary provisions could be included so long as they did not unduly interfere with the business of the partnerships. The key here is balancing the rights of the creditor, the partnership, and the nondebtor partners. Thus:
What that standard means, as a practical matter, is that, if a court has reason to believe that the charging order by itself cannot effectively convey to the judgment creditor the debtor-partner’s right to distributions and profits—as might happen, for example, if the limited partnership exists only to shelter assets from creditors and has no business that will generate distributions or profits in the ordinary sense of the words, or has been structured in or operated in such a way as to allow money to be transferred to the debtor-partner or his or her agents through a mechanism other than formal distribution or profit sharing—the court may issue ancillary orders that will ensure that the charge on the judgment creditor’s share is not evaded. And while the court would be expected to craft its orders, if possible, to avoid interference in the partnership’s management, there may be circumstances in which it is not possible to effectuate the goal of charging the judgment creditor’s share of distributions and profits without some degree of interference in the business. As long as the order effectuates a reasonable balance between the two objectives, it would be authorized.
This brought the court to Zemp’s LLC. The court noted the difference identified by the Oregon Court of Appeals, which was that Oregon’s partnership law made a reference to the general statute, but the Oregon LLC Act did not. Here, the creditor made the quite rational argument that courts have inherent powers to do certain things to effectuate their orders. The Oregon Supreme Court agreed, noting the necessity of such powers to balance the interests of the creditor, the LLC, and the nondebtor members.
Having recognized the power of the courts to issue ancillary provisions to effectuate a charging order through a very long and well-researched discussion, the court then turned to whether the particular ancillary provisions in this case were appropriate.
The court thought not, largely because there was no record evidence that the provisions were necessary—the only proof the creditor offered was that Zemp owned the interests without providing further evidence that these ancillary provisions were necessary:
The court could not determine, on the basis of that evidence alone, that the ancillary orders were so crucial to the effectiveness of the remedy that the court sought to provide (i.e., access to the debtor-partner’s or debtor-member’s distributional interest in the partnership or limited liability company) and their effect on the companies’ management was so that incidental that, on balance, the orders were justified. It follows that none of the challenged ancillary orders were authorized.
Thus, the decision of the Oregon Court of Appeals was reversed and the case remanded back to the trial court for “further proceedings,” presumably to allow the parties to come forward with evidence as to whether the ancillary provisions were justified by the evidence.
Analysis
The issue of what ancillary provisions may be inserted by a creditor into a proposed charging order and approved by the court has long bedeviled practitioners. There is no express guidance on the issue in the so-called harmonized acts (UPA, ULPA, ULLCA, and their revisions), which has caused the courts to address the issue ad hoc and therefore has led to problems. The laws and procedural rules of not one state requires a particular form of charging order, and there is nothing like an “official form” for a charging order such as those which are appended to the Federal Rules of Civil Procedure. Very simply, drafting a charging order is very much a task of making it up as one goes, and there was no good guidance as to which ancillary provisions were acceptable and which were not.
Now we know the answer: A particular ancillary provisions is allowable so long as (1) the need for the provision is well-supported by record evidence; and (2) the provision strikes an appropriate balance between the competing needs of the creditor, the company, and the nondebtor partners or members. Simply filing a bare motion for a charging order accompanied by an elaborate proposed charging order will no longer suffice; instead, if a creditor wants the charging order to say much more than that a lien is created upon the debtor’s distributional interest, the creditor must prove up the need for those provisions.
Note that information rights, i.e., ordinarily financial information about the company, should almost never be permitted. The reason here is that if the debtor has access to the financial information, then the creditor can compel that information from the debtor without having to bother the company about it. This should be particularly true in a case like this where the debtor is a general partner or managing member. Only if there is relevant information that the debtor is not entitled to it should the court consider whether the compel the company to provide the information.
Otherwise, there is not much more to say simply because the Oregon Supreme Court has just said it.
The red flags of foreign investment—purposeful obfuscation and lack of a legitimate business purpose—are prominent in today’s media. Advisors of lower-market private equity funds must find the cacophony of public condemnation and scrutiny surrounding the Panama Papers and the more recent Paradise Papers disconcerting. Should advisors of lower-market funds be concerned about money laundering? Does a lower-market fund even have an obligation to adopt an anti-money-laundering program (AML program)? For purposes of this article, a “lower-market fund” shall be deemed to have less than $25 million in assets under management and is exempt from the Investment Company Act of 1940, and in connection with its offering did not utilize the services of either a broker or an investment adviser registered with the Securities and Exchange Commission (SEC).
The answer to the first question is simple. Money laundering is a crime under federal and state law, each of which provides for civil and criminal prosecution as well as significant penalties. Advisors to lower-market funds therefore have reason to be concerned. The answer to the second question requires a more thorough analysis.
Money Laundering Defined
Money laundering involves the purposeful concealment of the true origin of the proceeds of illegal activities and occurs when money from illegal activity is moved through the financial system in a manner to make those illegal funds appear to have been derived from legitimate sources. Money laundering involves three stages: placement, layering, and integration. “Placement” occurs when the cash is first placed into the financial system. “Layering” involves the creation of complex layers of financial transactions following the placement stage in order to distance the illegal proceeds from, and to hide, their criminal source. “Integration” occurs when the illegal funds, the true source of which has been obfuscated as a result of the “layering” process, now appear to be derived from a legitimate source.
Federal Law
The initial, primary deterrent to money laundering was the Currency and Foreign Transactions Reporting Act of 1970, commonly known as the Bank Secrecy Act (the BSA), at 31 U.S.C. § 5311, et seq. The BSA established the framework for anti-money-laundering (AML) obligations imposed on specified “financial institutions.” In addition, with the adoption of the U.S. Money Laundering Control Act of 1986, as amended, 18 U.S.C. §§ 1956, 1957 (MLCA), money laundering became a criminal offense under federal law. More recently, the federal authorities, particularly the U.S. Treasury (the Treasury), were provided additional weapons in the war on money laundering following the adoption of the Patriot Act (full name the Uniting and Strengthening America by Providing Appropriate Tools Required to Intercept and Obstruct Terrorism Act of 2001). Section 361 of the Patriot Act also created the Financial Crimes Enforcement Network (FinCEN) as a bureau within Treasury. As noted on its website, “FinCEN’s mission is to safeguard the financial system from illicit use and combat money laundering and promote national security through the collection, analysis, and dissemination of financial intelligence and strategic use of financial authorities.”
Title III of the Patriot Act gave the Treasury the authority to impose significant AML requirements on “financial institutions.” Specifically, section 352 of the Patriot Act requires financial institutions to establish and implement an AML program and grants the authority to the Secretary of the Treasury (the Treasury Secretary), after consultation with the appropriate “Federal functional regulator” (as defined in section 509 of the Gramm-Leach-Bliley Act), to implement, administer, and enforce compliance with the BSA and all associated regulations, including prescribing minimum standards for AML programs required by the BSA. In 2014, the Treasury Secretary officially delegated to the director of FinCEN the authority to implement, administer, and enforce compliance with the BSA and all associated regulations under Treasury Order 180-01 (July 1, 2014).
Section 5312(a)(2)(Y) of the BSA authorizes the Treasury Secretary (i.e., the Director of FinCEN by delegation) to include additional types of businesses or persons in the definition of “financial institution” subject to the purview of the BSA so long as the Treasury Secretary (or the Director of FinCEN by delegation) determines that such businesses or persons are engaged in an activity similar to, related to, or that is a substitute for any of the “financial institutions” that are currently subject to the AML requirements imposed by the BSA. Thus, the director of FinCEN, as chief enforcement officer of the BSA, has broad latitude and discretion in enforcing the BSA and establishing its jurisdiction. As of the beginning of 2018, however, the director of FinCEN has not added any additional businesses or persons to the definition of “financial institutions” subject to the BSA. This should not be interpreted to mean that FinCEN has been idle. Acting under this delegated authority, FinCEN has issued regulations requiring financial institutions subject to the BSA to keep records, adopt and implement customer due diligence policies, and file reports on financial transactions in order to ensure that their operations comply with the BSA and to otherwise assist the authorities with the investigation and prosecution of money laundering and other financial crimes.
In addition, FinCEN has targeted two groups in particular since its establishment: (1) investment advisers registered with the SEC pursuant to the Investment Adviser Act of 1940, as amended (RIAs), and (2) loan and finance companies. FinCEN proposed in 2003 to amend the BSA regulations to require RIAs to establish AML programs, to establish minimum requirements for such programs, and to delegate FinCEN’s authority to examine RIAs for compliance with these AML requirements to the SEC at 68 Fed. Reg. 23646-23653 (May 5, 2003). FinCEN later withdrew its 2003 proposal after concluding, among other reasons, that RIAs already had to conduct financial transactions for their clients through financial institutions subject to the BSA regulations at 73 Fed. Reg. 65568-65569 (Nov. 4, 2003), and therefore they were not entirely outside the then-current BSA regulatory regime. Undaunted, FinCEN again proposed in September 2015 rules that would require RIAs to adopt and implement AML policies in order to comply with the BSA, but to date those proposed rules have not been adopted.
The other group that has come under FinCEN scrutiny is “loan or finance companies,” which ironically is already a grouping included in the definition of “financial institutions” subject to the BSA regulations. However, as even FinCEN has noted, the term “loan or finance companies” is not defined in any BSA regulation or FinCEN rules and has no legislative history. FinCEN partially addressed this definitional gap in 2002 by temporarily exempting loan and finance companies (and certain other categories of BSA-defined “financial institutions”) from having an obligation to establish AML programs under the BSA at 67 Fed. Reg. 21110-21112. In addition, FinCEN further addressed this definitional gap in February 2012 when it issued a final rule at 77 Fed. Reg. 8148-8160 defining nonbank residential mortgage lenders and originators (RMLOs) as “loan and finance companies” for purposes of the BSA, thereby subjecting them to the AML requirements of the BSA.
More important for lower-market funds, however, is what else FinCEN disclosed in its 2012 final rule; FinCEN noted that:
the term “loan or finance company” “can reasonably be construed to extend to any business entity that makes loans to or finances purchases on behalf of consumers and businesses [emphasis added]” (i.e., not just consumer transactions, but also commercial transactions); and
“the term ‘loan or finance company’ should be limited, at this time, to RMLOs, and that AML program and SAR requirements should be applied first to these businesses [i.e., RMLOs], and later—as part of a phased approach—applied to other consumer and commercial loan and finance companies [emphasis added].”
Therefore, even though lower-market funds are generally not required at this time to adopt an AML program because they do not currently fall within the definition of “loan or finance companies” for purposes of the BSA, FinCEN was very clear in 2012 that this is subject to change in the future.
FinCEN’s recent efforts to enforce the BSA have also gone beyond simply targeting RIAs and RMLOs. In May 2016, FinCEN issued final rules under the BSA at 81 Fed. Reg. 29398-29458 to clarify the customer due diligence requirements for “covered financial institutions,” which includes banks, brokers or dealers in securities, mutual funds, and futures commission merchants and introducing brokers in commodities. The 2016 final rules contain explicit customer due diligence requirements for those covered financial institutions and include a new requirement that such institutions identify and verify the identity of beneficial owners of legal entity customers, subject to certain exclusions and exemptions. The deadline for covered financial institutions to comply with these final rules is May 11, 2018.
Finally, FinCEN was particularly active in August 2017 when it issued:
(i) A Geographic Targeting Order (GTO) requiring U.S. title insurance companies to identify the natural persons behind shell companies purchasing high-end residential real estate in seven metropolitan areas. A GTO is an order issued by FinCEN under the BSA that imposes additional recordkeeping or reporting requirements on financial institutions or other businesses in a specific geographic area—in this instance, U.S. title insurance companies. The major U.S. geographic areas included in this GTO were the following: (1) all boroughs of New York City; (2) Miami-Dade County, Broward County, and Palm Beach County; (3) Los Angeles County; (4) three counties comprising part of the San Francisco area (San Francisco, San Mateo, and Santa Clara counties); (5) San Diego County; and (6) the county that includes San Antonio, Texas (Bexar County). However, most lower-market funds do not serve as title insurance companies, due in large part to the increase in federal consumer protection laws for residential mortgage loans following the adoption in July 2010 of The Dodd-Frank Wall Street Reform and Consumer Protection Act (Pub. L. 111–203, H.R. 4173). Consequently, lower-market funds are generally not impacted by these GTOs.
(ii) An advisory encouraging (but not requiring) real estate brokers, escrow agents, title insurers, and other real estate professionals to voluntarily report suspicious transactions involving real estate purchases and sales.
Conclusion
Even though there is generally no AML program requirement currently imposed on lower-market funds, presumably competent and risk-adverse advisors to lower-market funds desire to avoid any involvement in money-laundering activities. So how do advisors to these funds protect themselves against money laundering? The answer is that they typically only seek (or maybe more aptly only have available) funding from either “family and friends” or from someone with whom one of the founders has a “preexisting, substantial relationship.” In other words, most lower-market funds have (consciously or unconsciously) their own unofficial “know-your-investor” policy in place.
Depending on the circumstances, however, more substantial policies and procedures may be warranted. In some instances, it may be prudent for an advisor to a lower-market fund to adopt and implement a formal AML program, which should include, at a minimum, the following:
the development of written internal policies, procedures, and controls commensurate with the level of risk and reasonably designed:
to identify and verify the investor; to identify and verify any beneficial ownership; to corroborate that the prospective investor has the requisite financial circumstances and sophistication; to corroborate that the prospective investor qualifies as an accredited investor; to corroborate that the lower-market fund or person acting on its behalf has sufficient information to make these determinations; and to corroborate that the lower-market fund or person acting on its behalf has made these determinations; and
to allow the advisor to the lower-market fund to understand the true nature and purpose of each investor’s investment in that fund, including policies and procedures to detect and cause the reporting of suspicious transactions subject to 31 U.S.C. § 5318(g) (and the implementing regulations thereunder);
the appointment of an AML compliance officer who is knowledgeable and competent on the regulatory requirements;
an ongoing AML training program; and
an independent audit function (generally done on an annual basis) to test the fund’s AML program.
In conclusion, a lower-market fund generally has no legal obligation to adopt and implement any specific AML program, but prudent advisors to such funds will ensure that their funds adopt and implement appropriate procedures and controls to avoid becoming an unwitting accomplice to money-laundering activities.
U.S. patent laws bar patentability of an invention if it was “on sale” more than one year before a patent application is filed, but what if the invention was on sale in a nonpublic way? For decades, courts have held that even so-called secret sales of an invention may still trigger a bar to patentability. In 2011, however, the American Invents Act (AIA) modified patent laws in a way that many argued precluded secret sales from serving as a bar to patentability.
In May 2017, the Federal Circuit partly addressed this dispute in Helsinn Healthcare S.A. v Teva Pharmaceuticals USA, Inc., concluding that even after the enactment of the AIA, if the existence of the sale is public, the details of the invention need not be publicly disclosed in the terms of sale for the sale to bar patentability. In other words, the Federal Circuit determined that the AIA did not change how secret sales are evaluated as bars to patentability. Helsinn petitioned the Federal Circuit for a rehearing of the issue, but it denied Helsinn’s request on January 16 of this year. Helsinn must now petition for review by the U.S. Supreme Court if it wishes to further challenge the ruling.
The January 16 denial of rehearing was accompanied by a concurring opinion from Judge Kathleen O’Malley, which addressed what she considered “mischaracterizations” in Helsinn’s petition and in amici briefs. Judge O’Malley rejected the contention that the Federal Circuit concluded that all public sales will trigger the on-sale bar: “All that our panel opinion held was that the particular agreement at issue triggered the on-sale bar, in part—but not exclusively—because it was made public.” Judge O’Malley also noted that although the court concluded that the particular transaction in Helsinn triggered an on-sale bar, it did not hold that all supply-side arrangements for future sales will trigger a bar. Judge O’Malley also rejected Helsinn’s legislative-interpretation argument that the AIA changed decades of law regarding on-sale bars.
Although the Federal Circuit has ruled that secret sales may still trigger an on-sale bar, an open question remains whether an entirely secret sale, the existence of which is not even public, can trigger an on-sale bar. Moreover, if Congress intended for the AIA to change the law surrounding secret sales, as some argue, then either the Supreme Court must intervene, or Congress must modify the statute.
Companies both large and small enter new ventures all the time. Netflix was originally a DVD delivery service, Amazon sold only books until 1998, and Pixar Animation was only a computer engineering and special-effects company for more than a decade. When businesses diversify, they may seek to insulate an established line of business from the liabilities of a new venture by forming separate, wholly owned subsidiaries. Nearly all of us assume that the enterprise will be responsible for the obligations of a single subsidiary only under the most extraordinary circumstances.
Successful actions against a parent for the obligations of a subsidiary, so-called veil piercing, are relatively rare due to the high bar required by most jurisdictions. In a seminal case on the matter, Pauley Petroleum Inc. v. Continental Oil Co., the Delaware Supreme Court rejected an argument that Continental Oil, a Delaware corporation, and its Mexican subsidiary should be treated as the same legal entity:
There is, of course, no doubt that upon a proper showing corporate entities as between parent and subsidiary may be disregarded and the ultimate party in interest, the parent, be regarded in law and fact as the sole party in a particular transaction. This, however, may not be done in all cases. It may be done only in the interest of justice, when such matters as fraud, contravention of law or contract, public wrong, or where equitable consideration among members of the corporation require it, are involved.
239 A.2d 629, 633 (Del. 1968). The Delaware Supreme Court did more than announce Delaware’s high standard for veil-piercing claims, however. It applied Delaware law to the question of whether a shareholder would be responsible for the obligations of a Mexican entity with statutory limited liability.
This may surprise transactional lawyers, most of whom assume, as they were likely taught in law school, that the law of the jurisdiction in which an entity is formed (or whose “corporate veil” is to be pierced) governs a veil-piercing action. This is commonly referred to as the “internal affairs” doctrine, recognized by the Supreme Court in CTS Corp. v. Dynamics Corp. of America, 481 U.S. 69 (1987), and cited in the Restatement (Second) of Conflict of Laws. Under the internal affairs doctrine, Delaware law would apply to the determination of whether to “pierce the veil” of a wholly owned subsidiary formed in Delaware, but Mexican law would apply to the potential liability of an equity owner of a business entity organized in Mexico.
Judicial consideration of choice of law is rare in veil-piercing cases, but a brief survey leads to the discovery that state courts often apply their own local laws, regardless of where the subject entities are formed. For example, the Court of Appeals of Maryland (where the authors of this article practice) applied Maryland law, without discussion, to analyze whether to pierce the veil of a New Jersey corporation in Hildreth v. Tidewater Equipment Co., Inc., 838 A.2d 1204 (Md. 2003). In addition, the California Court of Appeal, Second District, applied California law in a veil-piercing claim involving a Delaware parent and two foreign, wholly owned subsidiaries (one formed in the Netherlands, and the other in Bermuda) in Toho-Towa Co., Ltd. v. Morgan Creek Productions, Inc., 159 Cal. Rptr. 3d 469 (Cal. Ct. App. 2013).
Although apparently briefed on the choice of law, the U.S. District Court for the District of Delaware in Mobil Oil Corp. v. Linear Films, Inc. declined to “launch into a protracted choice of law analysis” and decided to analyze the applicable veil-piercing claims under Delaware law (the parent’s state of incorporation), rather than Oklahoma law (the subsidiary’s state of incorporation). 718 F. Supp. 260, 268 (D. Del. 1989). Moreover, the Delaware District Court has determined that Delaware courts considering a parent entity’s liability for the actions of its subsidiary entity “have applied Delaware law, even in the case of foreign subsidiaries.” Japan Petroleum Co. (Nigeria) Ltd. v. Ashland Oil, Inc., 456 F. Supp. 831, 840 n.17 (D. Del. 1978). In Ademiluyi v. PennyMac Mortgage Investment Trust Holdings I, LLC, after raising the choice of law issue without briefing from the parties, the U.S. District Court for the District of Maryland concluded that Maryland law applies to veil-piercing cases brought in Maryland courts, regardless of the jurisdiction of formation of any of the entities in question. 929 F. Supp. 2d 502 (D. Md. 2013).
Although many courts and practitioners assume that choice of law is unimportant because the standard for veil piercing is relatively uniform across U.S. jurisdictions, this assumption may lead to unpleasant surprises. Delaware courts generally require plaintiffs to establish fraud, injustice, or a public wrong. Texas, which has adopted a statutory standard for veil piercing for limited liability companies, requires “actual fraud” and a “direct personal benefit” to the member of a limited liability company. Maryland is even more difficult: in at least one case, a court applying Maryland law refused to disregard the corporate separateness of an entity whose only corporate formality was filing articles of incorporation. Gordon v. SS Vedalin, 346 F. Supp. 1178 (D. Md. 1972).
Other states, such as California, impose lower burdens on plaintiffs seeking recovery from a corporate parent, applying an “alter ego” analysis of elements such as capitalization of the entity, its failure to follow corporate formalities, and the overlapping of corporate records or personnel. Indeed, Stephen B. Presser, a professor at Northwestern University School of Law, has described the veil-piercing process under California law in section 2:5 of his book Piercing the Corporate Veil as “relatively easy . . . particularly in the case of individually-owned corporations.”
This means that businesses relying on the legal separateness of a wholly owned subsidiary to limit intracompany liabilities should be formed and operated in an effort to limit the potential for veil piercing not only in the state of formation, but also in the jurisdictions in which the subsidiary may become subject to claims. If a subsidiary is potentially subject to claims in a state such as California that imposes an “alter ego” or “instrumentality” theory of veil piercing, it should have a legal right to use the assets utilized in its business, enter into agreements in its own name, and observe all (or at least most) organizational formalities. In addition, parent entities may want to consider taking steps such as entering into shared services agreements regarding enterprise-wide tasks (such as human resources, accounting, or IT); accounting for enterprise-wide cash management with appropriate credits and debits between parent and subsidiary; and ensuring that the subsidiary is adequately capitalized against foreseeable liabilities, including being a named insured on the enterprise’s general liability policies. Where an enterprise has extreme liability concerns, avoiding structures such as member-managed LLCs may be advisable to minimize the appearance that a subsidiary is a mere instrumentality of its parent.
Lawyers and their clients are constantly working together to ensure that risks are predictable and manageable. Veil-piercing claims are never the first item on a client’s mind when discussing a new venture, but where separate subsidiaries are formed with the goal of minimizing risk, parties should consider the laws of jurisdictions where the subsidiary may be subject to claims in addition to where it is organized. With proper planning, wholly owned subsidiaries and their parents should be able to rebuff veil-piercing claims in even the most hostile legal environments.
Early into the Obama Administration, the U.S. Customs and Border Protection (CBP) and Immigration and Customs Enforcement (ICE)—both agencies within the Department of Homeland Security (DHS)—adopted policies to search, sometimes seize, and review the content of electronic devices at U.S. border crossings. Since the inception of the program, the numbers of these searches have steadily increased from approximately 8,500 in 2015; 19,000 in 2016; and 30,000 in 2017. To put these numbers into context, however, even this dramatic increase accounts for only 0.007 percent of the 397 million travelers (including both U.S. and foreign nationals) who crossed the border during the 12-month period ending September 30, 2017, according to a recent article. As reported elsewhere, over 80 percent of devices searched belonged to foreigners or legal permanent residents.
These searches and seizures are carried out without a warrant or any individualized suspicion—much less probable cause—that a traveler has done anything wrong. On the other hand, these searches have been instituted to vindicate national security concerns. Thence arises the delicate constitutional question of balancing that governmental interest against individual rights. Some courts have permitted routine border searches of travelers’ computers and other electronic devices as an exception to the Fourth Amendment prohibition against warrantless searches without probable cause. See, e.g., United States v. Cotterman, 709 F.3d 952, 960–61 (9th Cir. 2013) (en banc); Abidor v. Napolitano, 990 F. Supp. 2d 260, 277–82 (E.D.N.Y. 2013). Nevertheless, even in Cotterman, the Ninth Circuit concluded, en banc, that an intrusive forensic search of a computer hard drive is not “routine” and therefore requires reasonable suspicion to be constitutionally permissible. 709 F.3d at 960–68.
Electronic devices belonging to lawyers raise additional concerns—namely, the attorney-client privilege, the work product doctrine, and the confidentiality of lawyer and client communications (as required by Model Rule of Professional Conduct 1.6) to the extent that any information protected by any or all of these is maintained on any such electronic devices.
Recent Litigation Challenging Border Searches
On September 13, 2017, a lawsuit was filed in Boston against the federal government nominally on behalf of 11 travelers whose smartphones and other electronic devices were searched without a warrant at the U.S. border. The real proponents of the litigation, as made clear on the website of the American Civil Liberties Union (ACLU), are the ACLU, the Electronic Frontier Foundation, and the ACLU of Massachusetts. The named plaintiffs are 10 U.S. citizens and one permanent resident who come from different geographic locations and disparate backgrounds. Defendants are the leaders of DHS, CBP, and ICE. Alasaad v. Duke, No. 1:17-cv-11730-DJC (D. Mass., filed Sept. 13, 2017).
The case seeks to expand into the realm of border searches in the Supreme Court’s ruling in Riley v. California, 134 S. Ct. 2473 (2014), which recognized a significant privacy interest in digital data and held that police may not conduct warrantless searches of the cell phones of the people they arrest. The complaint in Alasaad also challenges prolonged confiscations—which sometimes last for weeks or months at a time—of travelers’ electronic devices without probable cause.
On December 15, the government moved to dismiss the complaint for lack of standing. The argument is that plaintiffs assert merely a general risk of injury from the remote possibility that their electronic devices may be searched in the future, and that the assertion that the government has retained information from electronic devices is conclusory and based on no factual allegations in the complaint that would support such a conclusion. Opposing the motion in a January 26 filing, plaintiffs argue that they have standing because of the substantial risk of future injury, and independently that standing exists to seek “expungement” of information retained by the government from prior unlawful searches. As of this writing, no decision on the motion has yet been issued.
Recent Revisions to CBP Policy
On January 4, 2018, CBP issued a revised policy governing border searches of electronic devices. As it affects issues of privilege, section 5.2 of the new policy represents a distinct improvement over the previous policy (though probably not yet sufficient to be completely satisfactory to the ABA):
When examining data on a device, CBP officers are now required by section 5.1.2 of the new policy to avoid accessing data stored remotely (e.g., in the Cloud) when they conduct device searches. To accomplish this, that section provides that the officers will either request that the traveler disable connectivity to any network (e.g., by placing the device in airplane mode), or they will themselves disable network connectivity where warranted by national security, law enforcement, officer safety, or other operational considerations. Note also that if a device is encrypted, section 5.3.1 of the revised policy requires travelers to unlock or decrypt their electronic devices and/or provide their device passwords to border agents.
CBP officers must now consult with the CBP Associate/Assistant Chief Counsel’s Office before searching devices allegedly containing privileged or work product protected information. (Section 5.2.1 of the prior policy required such consultation only when (A) the devices contained materials that appeared to be “legal in nature” or that were claimed to be protected by the privilege or work product and (B) the border officer suspected that the material “may constitute evidence of a crime or otherwise pertain to a determination within the jurisdiction of CBP.”).
CBP officers and lawyers are now required to seek clarification from the individual asserting the privilege as to the specific files, attorney or client names, or other particulars that may assist the agency in identifying the privileged information, and requires CBP to segregate the privileged materials from the other materials on the device and ensure the privileged materials are handled appropriately, all through the use of a filter team consisting of legal and operational representatives of the agency.
Any privileged materials that are copied by CBP must be destroyed at the end of the review process, unless the materials indicate an imminent threat to homeland security, or copies of the materials are needed to comply with a litigation hold or other requirement of law.
The new policy distinguishes a “basic search” of an electronic device, which may be conducted with or without suspicion, from an “advanced search” (defined as one in which an officer connects the device to external equipment to review, copy, and/or analyze its contents), which may only be conducted if there is reasonable suspicion of unlawful activity or a national security concern. Although not explicit in the new policy, this particular requirement may be a reaction to federal court decisions such as Cotterman, holding that an intrusive “forensic search” of a computer hard drive is not “routine” and requires reasonable suspicion to be constitutionally permissible.
Note that CBP’s revised policy (section 2.7) expressly does not apply to searches by ICE, even when CBP transfers devices to ICE for a search.
As of this writing, ICE has not revised its own policy, so its prior policy remains in force. ICE’s policy authorizes searches of electronic devices with or without individualized suspicion and, unlike CBP’s revised policy, does not contain enhanced protection or consultation procedures for information claimed to be privileged or confidential and does not prohibit Cloud searches.
Pertinent Ethical Obligations
Lawyers should consider whether consenting to a device search by a CBP or ICE agent is compatible with their professional responsibilities. Obviously, a lawyer must advise such agents of the existence of any privileged material on the device in question. In addition, key provisions of the Model Rules of Professional Conduct are summarized below in chronological order. Be sure to consult the versions of these rules in each jurisdiction in which you are admitted to practice.
Competence. Model Rule 1.1 imposes the requirement of competence. Comment [8] adjures lawyers to “keep abreast of changes in the law and its practice, including the benefits and risks associated with relevant technology . . . .” Moreover, a 2011 formal opinion of the Standing Committee on Ethics and Professional Responsibility (the Ethics Committee) observes that implicit in the obligation of competence is acting “competently to protect the confidentiality of clients’ information . . . .”
Communicating with Clients. As a general proposition, Model Rule 1.4 requires a lawyer to keep clients informed about the status of their matters, as well as about any matters as to which informed consent (as defined in Model Rule 1.0(e)) is required. Explaining to clients the risks of search of electronic devices containing their confidential or privileged information and obtaining informed consent in advance is, for a lawyer planning cross-border travel, a possible solution. It is not necessarily a reliable solution, however, because some clients might not consent and, even for those that do, questions could arise later about the adequacy of the lawyer’s explanation of the risks involved. In the absence of any such client consent, if information relating to a representation is disclosed during a border search, the lawyer should ascertain whether the rules in the jurisdictions where the lawyer is admitted require advising the affected client. Note in this regard a 2017 opinion of the New York City Bar Association (the NYCBA Opinion), which concludes that the lawyer must inform affected clients about such disclosures.
Confidentiality. Model Rule 1.6 is the most important ethical requirement in this context. Paragraph (a) prohibits revealing “information relating to the representation of a client unless the client gives informed consent, the disclosure is impliedly authorized in order to carry out the representation or the disclosure is permitted by paragraph (b).” We have already discussed informed consent, and it’s extremely unlikely that border inspection disclosures would ever be “impliedly authorized” within the contemplation of the rule. Paragraph (b) does permit (but does not mandate) disclosure “to the extent the lawyer reasonably believes necessary” under specified circumstances, including (b)(6), “to comply with other law.” The phrase “other law” generally refers to statutory or regulatory requirements, such as the requirement of the Internal Revenue Code that cash transactions over $10,000 be reported to the I.R.S.
Comment [12] tells us, somewhat unhelpfully, that whether such “[other] law supersedes Rule 1.6 is a question of law beyond the scope of these Rules.” Regulations and official policies of a federal agency normally preempt inconsistent state law, so the odds are that the border search policies of CBP and ICE do, in fact, supersede Rule 1.6(a), but no ethics opinion has as yet so concluded, and no court has as yet so ruled. Comment [12] goes on to say that when disclosure is required by “other law,” “the lawyer must discuss the matter with the client to the extent required by Rule 1.4.” That is fine in the context of a court order or a subpoena, where there is time and opportunity for such consultation, but barring advance consent under Rule 1.4, it is unlikely as a practical matter that the lawyer whose electronic devices are searched or impounded at the border will be able to consult any client. A 2016 Ethics Committee opinion deals with disclosure under Model Rule 1.6(b)(6) in the context of a subpoena or court order and takes the position that when a client is not available for consultation, a lawyer must (i) assert all reasonable claims against disclosure and seek to limit the subpoena or other initial demand on any reasonable ground, and (ii) consistent with the language in the chapeau of 1.6(b), reveal information only to the extent reasonably necessary.
More specific advice is provided in the border search setting by the NYCBA Opinion. Acknowledging that Rule 1.6(b)(6) “permits a lawyer to comply with a border agent’s demand, under claim of lawful authority, for an electronic device containing confidential information during a border search,” including a demand that the attorney unlock the device to facilitate such a search, the opinion cautions that “compliance is not ‘reasonably necessary’ unless and until an attorney undertakes reasonable efforts to dissuade border agents from reviewing clients’ confidential information or to persuade them to limit the extent of their review.” If confidential client information is, in fact, disclosed during a border search, the NYCBA Opinion requires that “the attorney must inform affected clients about such disclosures pursuant to Rule 1.4.”
Rule 1.6(c) applies to “inadvertent or unauthorized disclosure of, or unauthorized access to” confidential client information. Given the requirements of competence in Model Rule 1.1, disclosure to border agents pursuant to established CBP and ICE policies cannot be regarded as “inadvertent” but will almost always be “unauthorized” by the client. Comment [18] says these kinds of disclosures are not a violation of 1.6(c) “if the lawyer has made reasonable efforts to prevent the access or disclosure.” What constitutes reasonable efforts in this unusual, compulsory context is not completely clear, but Comment [18] identifies certain factors to be considered:
the sensitivity of the information, the likelihood of disclosure if additional safeguards are not employed, the cost of employing additional safeguards, the difficulty of implementing the safeguards, and the extent to which the safeguards adversely affect the lawyer’s ability to represent clients (e.g., by making a device or important piece of software excessively difficult to use).
As food for thought, note also that certain clients, particularly sophisticated clients, may require their lawyers to employ special security measures beyond what the rule itself would require.
Supervisory Responsibilities. Even law firm partners who are not crossing borders with electronic devices are not off the hook. For lawyers who exercise, either individually or together with law firm colleagues, managerial authority in the firm, Model Rule 5.1 requires them to “make reasonable efforts to ensure” that supervised lawyers “conform to the Rules.” Model Rule 5.3 contains similar requirements with respect to employed, retained, or associated nonlawyers (e.g., paralegals). Taken together, these provisions suggest that law firms put in place policies addressing the efforts junior lawyers and nonlawyer legal professionals working for the firm should make to preserve client confidential information when traveling with electronic devices.
Some Concluding Observations
Uncertainties abound here. For one thing, the statistics at the beginning of this article show that the likelihood a lawyer’s electronic devices will be searched or seized is quite low. (Recall that Comment [18] to Rule 1.6 identified as a factor in assessing the reasonableness of safeguards the likelihood of disclosure if those safeguards are not employed). For another, it is entirely possible—at least under the recently revised CBP policy—that advising a border agent of the existence of confidential or privileged information on a device will be sufficient to cause them to segregate any such information from examination.
Pace such palliatives, the cost of additional safeguards is quite low (another factor identified in Comment [18]), and it is important for a lawyer to be fully prepared for such searches. The following are worthy considerations by any lawyer anticipating cross-border travel:
Consider whether it is necessary to bring with you any electronic device containing confidential or privileged information. (If you’re going on vacation, stop being a workaholic automaton and leave the device behind).
If you must bring one or more portable electronic devices along, make sure each one is thoroughly scrubbed of all privileged or confidential information. Merely deleting files may not be adequate to remove them completely. The device will still enable you to work on affected matters because it may be used from abroad to access confidential information remotely that is maintained on law office e-mail, databases, or in the Cloud without having the actual files stored on the device.
Consider acquiring an electronic device exclusively for use during foreign travel and avoid, to the maximum extent possible, placing confidential or privileged information thereon.
Merely encrypting privileged or confidential information on a device is no guarantee of its remaining confidential. Remember that border agents may demand that you provide password or other decrypting information, and failure to do so can lead to your device being seized and detained for a period of time.
Familiarize yourself in advance with the pertinent ethics rules and opinions of each jurisdiction in which you are admitted in order to ascertain whether you may ethically consent to a request (or demand) to inspect your device(s) and, if a device is inspected, whether you are required to advise each client whose information was subject to inspection.
If your client or any jurisdiction in which you are admitted requires you to take extra steps to safeguard the confidentiality of information on a portable electronic device, be sure you have fully complied with those requirements in advance of travel.
Finally, be cognizant of the location and content of all privileged and confidential information on each device you bring across the border, and be prepared when advising a CBP or ICE officer of the existence of privileged or confidential information to identify for the officer specific files or categories of files, names, phone numbers (in the case of a mobile phone), and e-mail addresses of clients or lawyers associated with confidential or privileged information on the device, and any other information that will help the officer segregate such information.
In addition to serving as BLT’s managing editor for Ethics & Professional Responsibility, the author is the Business Law Section’s liaison to the ABA Border Search Task Force that was organized in 2017 by former ABA President Linda Klein. He also currently serves on the Standing Committee on Ethics and Professional Responsibility. The views expressed herein are, however, entirely the author’s own.
The term “legacy systems” plays an increasing role in business risk management. Legacy systems commonly refer to outdated computer systems, networks, programming languages, or software. The definition of “legacy system” is subjective because these systems may vary in outdatedness. For example, hardware has age limits, and software ceases to be updated and becomes incompatible with new operating systems. Computer systems are often acquired, built, and implemented at various points throughout a company’s history. Furthermore, changes in business practices may render once acceptable systems obsolete by demanding new abilities from unchangeable software.
Regardless of their limitations, legacy systems continue to play a key role in companies of all sizes. Dealing with legacy systems is about balancing business goals, legal liabilities, technology, and user needs. Although some believe that IT staff should be responsible for this balancing act, lawyers play a crucial role because technology issues affect a company’s overall risk management. This article aims to provide guidance for lawyers in assessing risks associated with legacy systems.
Identify the System
The initial consideration with any legacy system is to identify the type of system a company utilizes:
Is the system a commercial, off-the-shelf solution?
Is it a custom-built solution?
What type of code is utilized in the system?
Who originally built the system, and are they still in existence?
Determining the type of system used will provide key information to assess whether that system is still viable, and what risks exist in the current network infrastructure.
Identify Roles and Responsibilities
Next, the contracts that govern the use and maintenance of the system should be located and reviewed to understand the responsibilities of the parties. It may be difficult at times to locate these documents, especially for a system that may be decades old. Furthermore, maintenance of a system should be assessed from both a technological and contractual perspective. Who is responsible for ensuring that updates, patches, and any other changes are implemented in a timely manner?
The Equifax breach exemplifies the importance of system patches. Access to Equifax’s systems and the data of approximately half the U.S. population resulted from Equifax’s failure to implement a patch that was available two months before the infiltration. Another example is The Royal Bank of Scotland and the NatWest system failure in 2013. Customers were unable to access accounts, use debit or credit cards, or make online payments on Cyber Monday—a failure that RBS officials admittedwas a result of decades-old systems and a failure to maintain those systems.
Keep It or Replace It
In some cases, the original designers of these systems have either moved on to other companies or retired from the workforce, without leaving sufficient documentation to provide guidance to those that remain. If your IT team does not understand a system, how can it protect and evolve it to meet the needs of the business? This inevitably begs the question: Is the system so old that it cannot even be maintained?
Legacy systems may incorporate old code and software that a modern workforce is unable to support. In some instances, the coding language is so archaic that it is no longer taught in school. For example, COBOL, a programming language used in many legacy mainframe systems including that of the banking industry, is used only to maintain existing applications and is not commonly taught anymore. These systems can become so outdated that they are unable to scale to encompass new tasks and technologies, which in turn becomes an inhibitor to innovation and evolution within a company.
The Importance of System Architecture
Many companies rely on multiple systems that are cobbled together without a clear system architecture. To resolve operational issues that may arise, IT might develop patchwork solutions that inadvertently create security vulnerabilities and further add layers of complexity. The pitfalls of complexity are exemplified by the cyber attacks on the U.S. Office of Personnel Management (OPM). OPM was infiltrated in two separate incidents: (1) the hackers gained access to OPM’s system for almost two years before OPM became aware; and (2) the second incident lasted for approximately one year before becoming known. OPM’s complex structure, combined with poor cyber hygiene and outdated security technology, contributed to the delay in realizing the unauthorized access.
System complexity creates issues with system recovery and redundancy. These incremental enhancements balloon into a nightmare that traps companies as prisoners in their own legacy systems. IT management quickly morphs into risk management, continually requiring that the company maintain a record of these risks and develop internal solutions to minimize those risks.
Even if these systems are not complex, they still suffer from a lack of developer familiarity with the system as well as a lack of documentation regarding the overall software architecture. Without continuity in the workforce to provide for an exchange of information as new employees take over management of these operations, there is little to no guidance available to keep these systems running.
Cybersecurity Risks
All these factors contribute to growing vulnerabilities associated with legacy systems from a legal, technological, and operational perspective. Given that systems integrate with interdependent systems, it is challenging to create automatic protections from new threats. Furthermore, patching is more difficult because it is not simply pushing a patch out to one system. If the technology team does not or cannot understand a network’s infrastructure, it is difficult to implement a patch to the system. In some cases, system developers do not provide continued maintenance and support, so patches are not even available to fix known security or design flaws. For example, Microsoft announced in 2016 that it would no longer support Windows XP. Security protocols should be uniform and integrated across all systems, but with no clear system architecture, this task can become seemingly impossible.
In certain industries, the risks may be even higher. Two recent regulatory changes that may impact the use of legacy systems are the New York Department of Financial Services Cybersecurity Regulation, 23 NYCRR 500 (DFS Regulation), and the forthcoming European Union’s General Data Protection Regulation (GDPR). Both regulations demand higher standards for data protection and security, requiring that companies not only understand their systems, but in some cases proactively redesign those systems if they don’t comply.
In the United States alone, numerous states are considering changes to cybersecurity and data privacy laws that will strain these legacy systems even further beyond their capabilities. Many states, including Delaware, South Dakota, and Colorado, have proposed legislation in the last six months (in response to the Equifax breach) that would shorten the timeframe for notifying citizens of data breaches and expand the definition of what constitutes a breach that requires notification. These proposed regulatory changes would necessitate that companies have a strong knowledge of their systems, the data maintained in those systems, and system access points in order to efficiently determine whether unauthorized access occurred. Legacy systems pose significant hurdles to compliance because of their complex structure, which may make complying with these proposed regulations more difficult.
The Growing Role of a Lawyer
As these legacy systems continue to hit boundaries, and maintenance becomes harder because of age and the lack of an informed workforce to maintain these systems, companies must critically assess next steps. Companies should begin by creating a comprehensive plan of action. They must bring together an interdisciplinary team to assess the legacy system’s long-term viability, the company’s need for the system, and the appropriate plan of action to address the vulnerabilities and risks within that system. Input should be received from all sectors of an organization (legal, IT, marketing, security, privacy, financial, etc.) throughout the entire process.
The legal liabilities play a pivotal role in that analysis: if the creator of a legacy system is no longer in existence or has strategically decided not to maintain a system, what happens in the event of a breach? Who is held responsible for a system vulnerability? It is important that the contractual relationships among the system providers, either in a legacy system or newer systems, are clearly understood and considered in the plan of action.
Legacy systems play a pivotal role in business. Migrating these legacy systems to newer technologies involves a delicate balance between an expensive overhaul of an entire system and incremental fixes. Ultimately, a company must assess its current environment to determine whether the vulnerabilities and risks, to the extent they are even known or can be discovered, can be sustained by the company or whether the technology’s lifecycle has run its course. Technology continues to evolve at an unprecedented rate, and companies must critically assess their situation. Lawyers must be prepared to delve deeply into these issues with their clients to understand both the legal liabilities that attach to these legacy systems and the risks associated with migrating to new systems.
I would like to thank Conor Gilsenan for reviewing and providing insight into this article.
In a rare loss by an audit firm in a case involving financial-crisis-era fraud, an Alabama federal court recently held accounting giant PricewaterhouseCoopers (PWC) liable to the Federal Deposit Insurance Corporation (FDIC) for its failure to detect a $2 billion fraud. Judge Barbara Jacobs Rothstein’s December 28, 2017 liability opinion in The Colonial Bancgroup, Inc., et al. v. PricewaterhouseCoopers LLP, et al. departed from the typical rule that because receivers like the FDIC stand in the shoes of their debtors, they can only recover where the debtor itself could recover—which excludes cases where the debtor has “unclean hands.” Instead, and despite undisputed evidence of Colonial Bancgroup’s fraud, the court applied Alabama state law to view the FDIC, a government entity, as different from a normal successor-in-interest, and granted the receiver’s claim.
Since the U.S. Supreme Court’s decision in O’Melveny & Myers v. FDIC, 512 U.S. 79, 114 S. Ct. 2048 (1994), there has been no question that state law governs claims brought by the FDIC as a receiver. In light of this fact, the decision in Colonial Bancgroup is instructive. It shows that this area of law is unsettled, and that auditors may face greater potential liability in states like Alabama, where friendly state laws could allow courts to permit the FDIC (and its sister entity, the National Credit Union Administration) to pursue lawsuits against them related to failed banks and credit unions.
Suing Auditors Is Often a Losing Proposition
The law generally insulates auditors from civil liability for losses stemming from their alleged failure to detect frauds committed by their clients, including financial institutions.
First, under the law of many states, privity requires that a third-party plaintiff have more than de minimis direct contact with the auditor as a precondition to recovery.[1] Given that this rarely occurs, the doctrine of privity generally functions as a bar to suits by third parties against auditors for professional negligence before even reaching the question of whether the auditor’s failure to exercise due care caused significant injury to the putative plaintiffs.[2] Whether the third-party plaintiff is a shareholder in a bankrupt company, an investor who entrusted that company with his or her funds, or an unrelated victim of the underlying fraud, those parties rarely will be permitted to pursue the auditor for its negligence.
Second, even when a company itself is badly damaged (or even bankrupted) by a fraud, courts will bar a suit by the company itself against the auditors under the doctrine of in pari delicto (literally, “in equal fault,” such that the position of the defending party is the stronger one)[3] because a fraud committed by the company’s own management or employees is imputed to the company. The theory, to put it simply, is that a company that destroys itself through fraud should not be permitted to lay the burden of that misconduct on a third party.[4]
These rules form a formidable pair of obstacles that seemingly foreclose any such claims against an auditor whose negligence fails to discover devastating fraud. Third parties without a direct relationship with the auditor (and whose reliance is not foreseeable by the auditor) may not assert such a claim due to lack of privity, but the auditor’s client—the company—is barred from the claim because of its own imputed participation in the fraud.
The Colonial Bancgroup Litigation
Notwithstanding this legal backdrop, the Colonial Bancgroup litigation demonstrates that auditors are not entirely immune from civil liability, particularly in situations where there have been substantial losses to the public at large.
The Colonial Bancgroup litigation arose from a massive fraud that led to the failing of Colonial, a national bank that was a fully owned subsidiary of the Colonial Bancgroup (CBG).[5] When the FBI raided Colonial in August 2009, it was one of the 25 largest banks in the United States. Ten days later, Alabama banking regulatory authorities closed Colonial and appointed the FDIC as its receiver. CBG filed for Chapter 11 bankruptcy protection 11 days later.
Colonial’s failure was the result of a fraud perpetrated by Taylor, Bean & Whitaker Mortgage Corporation (TBW), the largest customer of Colonial’s Mortgage Warehouse Lending Division (MWLD), and several of Colonial’s employees. Colonial’s MWLD provided short-term funding to mortgage originators like TBW to enable such companies to originate and fund mortgage loans until those loans could be sold to third-party investors such as Freddie Mac and Ginnie Mae. Between 2002 and 2009, TBW and some of Colonial’s employees engaged in a multifaceted fraud that disguised TBW’s failure to repay Colonial’s short-term funding. By the time the fraud was discovered in 2009, it had grown to $2.3 billion.
During this period, PWC acted as outside auditor for CBG and because it performed the audit on a consolidated basis, that audit included Colonial.
The Colonial failure cost the FDIC’s deposit insurance fund $2.3 billion, and the FDIC was appointed receiver for the bank.[6] CBG and the FDIC each sued PWC, alleging that PWC breached the professional and contractual duties it owed CBG and Colonial, thereby allowing the fraud to go undetected. Both lawsuits also state claims against Crowe Horwath LLP, who acted as CBG’s internal auditor during the years that Colonial was victimized by the fraud and who also failed to detect the fraud. CBG’s and the FDIC’s claims against PWC and Crowe were consolidated, and the parties proceeded through discovery and pretrial motions. Ultimately, the claims against PWC and against Crowe were bifurcated, and the case was also bifurcated with respect to liability and damages.
Following the liability portion of the PWC bench trial,[7] the district court issued its findings and rulings on December 28, 2017. In a lengthy written decision, the court found that CBG could not hold PWC liable because the wrongful conduct of Colonial’s employees was imputed to Colonial and then to CBG based on its control over Colonial. On the other hand, the court found that PWC was liable to the FDIC for its negligence in failing to detect the massive, long-running fraud. In other words, the FDIC was treated differently than Colonial (and CBG), even though the FDIC (as a receiver) was stepping into the shoes of Colonial.
The court found that under Alabama law, PWC owed a duty to both CBG and Colonial to exercise reasonable care in performing its audits of CBG—a proposition that PWC did not dispute. The court then found that PWC breached those professional obligations by failing to plan and perform its audit to detect fraud, and by failing to obtain sufficient audit evidence regarding the particular types of transactions through which the fraud was executed.
In the bench trial, PWC witnesses acknowledged that PWC had an obligation to design its audits to detect fraud, and the court noted that in deposition testimony in the case brought by TBW’s trustee, PWC engagement partners, audit managers, and audit staff repeatedly admitted that PWC did not design its audit procedures to do so. Based on that testimony, the court concluded that PWC had failed to design its audits to detect fraud, and that PWC thereby violated applicable auditing standards.
The court also credited the plaintiffs’ assertion that PWC should have—but failed to—physically inspect the mortgage loan documents that were associated with the bank’s transactions with TBW, and which were supposed to be held by Colonial until it was paid its interest in the transaction. In doing so, it rejected PWC’s argument that even if it had attempted to inspect the underlying loan documents, it would not have uncovered the fraud because the fraudsters would have created fake documents. “This, of course, is something that we will never know,” the court observed. “However, what we do know is that . . . one of the key fraudsters . . . testified that if PWC had asked to see even just ten loan files, ‘[t]he jig would be up.’” In addition, PWC’s comparison of different management reports—to make sure the numbers matched—reflected insufficient “professional skepticism,” and PWC had missed certain red flags (like transaction dates that were illogical) that should have alerted it to the need to physically inspect the underlying documents. To the court, PWC’s decision to base its conclusions on TBW’s representations about the underlying assets instead of conducting its own investigation was “quintessentially the same as asking the fox to report on the condition of the hen house.”[8]
Why the FDIC Could Assert Colonial’s Claim
The FDIC faced legal hurdles in attempting to assert claims against PWC because it was stepping into the shoes of parties that would presumably be barred from asserting such claims. If the FDIC were viewed as asserting Colonial’s claims against its auditor, the doctrine of in pari delicto would presumably bar the claims because Colonial’s management and employees were complicit with (or even responsible for) the fraud. In addition, if the FDIC were viewed as asserting claims on behalf of the bank’s depositors (whom it has made whole through its insurance function), the depositors’ lack of privity with PWC would operate as a bar to the claims.
Nevertheless, the district court reached a different conclusion.[9] The starting point for the court’s analysis was that receiverships are governed by state law, and that Alabama law generally does not permit receivers to stand in a better position than the failed institutions they represent. In finding that the FDIC should not be so limited, the court relied in part on a 1991 Alabama Supreme Court case holding that the Resolution Trust Corporation—a federal receiver with substantive duties that mirror those of the FDIC—was not subject to punitive damages based on the misdeeds of the failed institution it inherited. There, the state high court reasoned that the imputation of wrongdoing to receivers is tempered by equitable principles:
A receiver operates for the benefit of creditors, unsecured depositors and the federal tax payer. However, punitive damages are imposed to punish the wrongdoer and to deter others. Where the wrongful party is in receivership and the damages are to be paid by innocent creditors, punitive damages create an inequitable result and are therefore improper. [The bank] no longer exists and cannot be punished. . . . Imposing punitive damages against RTC would not accomplish the purposes which punitive damages are meant to serve.[10]
According to Judge Rothstein, the same logic compelled a liability finding in Colonial Bancgroup. The court found that the purpose of in pari delicto would not be served by using it to bar claims by the FDIC. To further buttress this conclusion, the court relied on a Ninth Circuit decision involving the FDIC that helps to differentiate the FDIC from Colonial itself:
A receiver . . . does not voluntarily step into the shoes of the bank; it is thrust into those shoes. It was neither a party to the original inequitable conduct nor is it in a position to take action prior to assuming the bank’s assets to cure any associated defects or force the bank to pay for incurable defects. This places the receiver in stark contrast to the normal successor in interest who voluntarily purchases a bank or its assets and can adjust the purchase price for the diminished value of the bank’s assets due to their associated equitable defenses. In such cases, the bank receives less consideration for its assets because of its inequitable conduct, thus bearing the cost of its own wrong.[11]
What Comes Next?
Although Judge Rothstein’s opinion was limited to Alabama law and her prediction of how the state’s supreme court would view cases brought by the FDIC, it was also motivated by public-policy concerns that could have broader application. It is difficult to predict whether the decision and those public-policy issues will encourage other courts to permit the FDIC to assert claims against auditors.
One reason for this is that there are significant differences among how states treat receivers.[12] Consider as an example how Colonial Bancgroup might have been decided if the audit had taken place in New York. As in Alabama, the general rule under New York law is that the “liquidator . . . ‘stands in the shoes’ of the insolvent, gaining no greater rights than the insolvent had.”[13] For this reason, under New York law, the receiver of a bankrupt corporation can be barred by the in pari delicto doctrine from bringing claims against service providers to the corporation.[14]
In the past, some New York trial courts refused to impute knowledge of corporate wrongdoing to court-appointed receivers who are “innocent successors” to the corporation. These decisions draw upon federal cases, and the same public policy rationales that motivated the decision in Colonial Bancgroup.[15] Consistent with this line of cases, in a 1996 decision, a federal district court interpreting New York law found that the FDIC was not subject to an in pari delicto defense that could have been raised against the failed bank.[16]
However, those decisions pre-date the most recent New York Court of Appeals decision on imputation and inpari delecto: Kirschner v. KPMG LLP, 15 N.Y.3d 446, 938 N.E.2d 941 (2010). In that case, the court found that the primary, and arguably lone, exception to the general rule imputing an agent’s knowledge to his principal is the “adverse interest” exception, which applies only when the agent has “totally abandoned his principal’s interests” and is “acting entirely for his own or another’s purposes.” Where both the agent/employee and the corporation benefit, the exception does not apply.[17] In reaching this decision, the court reasoned that public-policy goals would not be served by exposing corporate auditors to additional liability:
The derivative plaintiffs caution against dealing accounting firms a “get-out-of-jail-free” card. But as any former partner at Arthur Andersen LLP—once one of the “Big Five” accounting firms—could attest, an outside professional (and especially an auditor) whose corporate client experiences a rapid or disastrous decline in fortune precipitated by insider fraud does not skate away unscathed. In short, outside professionals—underwriters, law firms and especially accounting firms—already are at risk for large settlements and judgments in the litigation that inevitably follows the collapse of an Enron, or a Worldcom or a Refco or an AIG-type scandal. . . . It is not evident that expanding the adverse interest exception or loosening imputation principles under New York law would result in any greater disincentive for professional malfeasance or negligence than already exists. Yet the approach advocated by the Litigation Trustee and the derivative plaintiffs would allow the creditors and shareholders of the company that employs miscreant agents to enjoy the benefit of their misconduct without suffering the harm.[18]
Although the decision does not directly apply to the FDIC, the court’s public-policy analysis differs significantly from that of Judge Rothstein. The Kirschner court’s skepticism that frauds can be deterred by expanding civil liability for auditors suggests that Colonial Bancgroup may have been decided differently if New York law had governed the FDIC’s claims against PWC.
Conclusion
The decision in Colonial Bancgroup demonstrates that auditors face difficulties in evaluating their potential liability for audits of banks and credit unions. In the event that a bank or credit union fails, and the auditor was unable to detect the underlying fraud for some period of time, that auditor may be held responsible for a massive amount of losses. Ultimately, the auditor’s liability in such a situation may turn on the vagaries of state laws governing receivership and how courts view the costs and benefits of holding auditors accountable for frauds perpetrated by others.
[1] There are circumstances in which an auditor may be liable to a third party when it has conducted work specifically for the benefit of that third party, but there are few cases finding a factual basis for such liability. Instead, the requirement of privity otherwise generally bars such claims. See, e.g. CRT Inves., Ltd. v. BDO Seidman, LLP, 85 A.D.3d 470, 472, 925 N.Y.S.2d 439 (1st Dep’t 2011) (finding complaint failed to plead claim for negligence) (citing Sec. Pac. Bus. Credit v. Peat Marwick Main & Co., 79 N.Y.2d 695, 706, 586 N.Y.S.2d 87 (1992)).
[2]See, e.g., In re Adelphia Commc’ns Corp. Secs. & Derivative Litig., slip op., 2014 WL 6982140, at *9 (S.D.N.Y. Dec. 10, 2014) (barring claim for negligence against auditor in absence of privity) (citing Guy v. Liederbach, 501 Pa. 47, 459 A.2d 744, 750 (Pa. 1983)); In re MF Global Holdings Ltd. Inv. Litig., 998 F. Supp. 2d 157, 187–88 (S.D.N.Y. 2014) (holding negligence claim requires under New York law showing of “near privity”) (citing Credit Alliance Corp. v. Arthur Andersen Co., 65 N.Y.2d 536, 493 N.Y.S.2d 435 (1985)); Bily v. Arthur Young & Co., 3 Cal. 4th 370, 406, 834 P.2d 745, 767 (1992) (barring investors claims for negligence against auditor of bankrupted company).
[3] The leading case on the doctrine is Cenco, Inc. v. Seidman & Seidman, 686 F.2d 449 (7th Cir.), cert. denied, 459 U.S. 880 (1982).
[4] For example, in Colonial Bancgroup, the bankruptcy trustee for the failed bank’s parent company sought to recover damages from PricewaterhouseCoopers for its negligence but was barred from doing so under the in pari delicto doctrine. See Colonial Bancgroup, Case No. 2:11-cv-00746-BJR-TFM, Order on the Liability Phase of the PWC Bench Trial, Doc. 798 (M.D. Ala. Dec. 28, 2017).
[5] This description of the facts is taken from the court’s findings issued following the liability phase of the bench trial in that case. See id.
[6] The court’s ultimate decision reduced the potential damages to an estimated $1.4 billion after determining that a related breach by Bank of America of its custodial obligations to Colonial Bank was not foreseeable by the auditor.
[7] Certain of the claims for which the plaintiffs had the right to a jury trial are to be tried separately to a jury. The Crowe bench trial was scheduled to commence after the conclusion of the PWC bench trial, although it was subsequently rescheduled for later in the proceedings.
[8] The court was also critical of PWC for failing to understand how certain of the transactions were supposed to work. One PWC auditor admitted that understanding these transactions was “above his paygrade,” and PWC ultimately assigned the evaluation of these transactions (a $589 million asset) to a college intern. PWC’s failure to understand this class of transactions was compounded by its failure to examine physically the actual documentation that underlay each transaction and constituted the collateral at issue. “Instead,” the court noted, “PWC chose to rely on . . . the college intern[‘s] assessment that it was not necessary to inspect the . . . collateral because ‘PWC feels that the collateral for these [transactions] is adequate.’”
[9] This issue was addressed in the context of the FDIC’s motion for partial summary judgment on the defendants’ affirmative defenses. See generally Colonial Bancgroup, Case No. 2:11-cv-00746-BJR-TFM, Order Granting in Part and Denying in Part FDIC’s Motion for Partial Summary Judgment on Defendants’ Affirmative Defenses, Doc. 720 (M.D. Ala. Aug. 18, 2017).
[10]Id. at 7–8 (quoting Resolution Tr. Corp. v. Mooney, 592 So. 2d 186, 190 (Ala. 1991)).
[11]Id. at 10–11 (quoting FDIC v. O’Melveny & Myers, 969 F.2d 744, 751–52 (9th Cir. 1995)).
[12] Judge Rothstein recognized as much in her opinion, in which she stated that there are countervailing opinions from other jurisdictions, but she was not persuaded by the reasoning of these courts. Id. at 11, n.2.
[13]In the Matter of Liquidation of Union Indem. Ins. Co. of N.Y., 89 N.Y.2d 94, 109, 651 N.Y.S.2d 383, 674 N.E.2d 313 (1996) (quoting Stephens v. Am. Home Assurance Co., 811 F. Supp. 937, 947 (S.D.N.Y.1993), vacated & rem’d on other grounds, 70 F. 3d 10 (2d Cir.1995).
[14]See, e.g., Cobalt Multifamily Inv’rs I, LLC v. Shapiro, 857 F. Supp. 2d 419, 431 (S.D.N.Y. 2012).
[16] FDIC v. Abel, 1996 WL 520906, at *1 (S.D.N.Y. Sept. 12, 1996) (“Because the FDIC is acting on behalf of the depositors and creditors . . . that defense cannot succeed.”).