LOUIS DREYFUS COMMODITIES SUISSE, SA v. FINANCIAL SOFTWARE SYSTEMS, INC.

CourtDistrict Court, E.D. Pennsylvania
DecidedFebruary 27, 2020
Docket2:14-cv-05995
StatusUnknown

This text of LOUIS DREYFUS COMMODITIES SUISSE, SA v. FINANCIAL SOFTWARE SYSTEMS, INC. (LOUIS DREYFUS COMMODITIES SUISSE, SA v. FINANCIAL SOFTWARE SYSTEMS, INC.) is published on Counsel Stack Legal Research, covering District Court, E.D. Pennsylvania primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
LOUIS DREYFUS COMMODITIES SUISSE, SA v. FINANCIAL SOFTWARE SYSTEMS, INC., (E.D. Pa. 2020).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF PENNSYLVANIA

LOUIS DREYFUS COMMODITIES SUISSE, SA, Plaintiff, CIVIL ACTION NO. 14-5995 v.

FINANCIAL SOFTWARE SYSTEMS, INC., Defendant.

PAPPERT, J. February 27, 2020

MEMORANDUM The Court previously granted summary judgment in favor of Louis Dreyfus Commodities Suisse, SA, recognizing as valid a foreign judgment against Financial Software Systems, Inc (“FSS”). (ECF Nos. 39 and 40.) Judgment was affirmed by the Third Circuit. Louis Dreyfus Commodities Suisse, SA v. Fin. Software Sys., Inc., 703 F. App’x 79, 80 (3d Cir. 2017). Since then, seeking to execute the judgment, Dreyfus has conducted post-judgment discovery. Two post-judgment motions are now before the Court. The first is Dreyfus’s motion seeking to compel FSS to produce further documents in aid of execution of the judgment (ECF No. 106) which FSS opposes. (ECF No. 125.) Dreyfus has replied to FSS’s opposition. (ECF Nos. 148 and 149). The second is FSS’s motion for a protective order seeking to preclude the production of documents by Branch Banking and Trust Company (“BB&T”) (ECF No. 153) which Dreyfus opposes. (ECF No. 154). The Court grants Dreyfus’s motion in part and denies FSS’s motion. I A With respect to Dreyfus’s motion, Federal Rule of Civil Procedure 69 provides that “[i]n aid of the judgment or execution, the judgment creditor . . . may obtain discovery from any person – including the judgment debtor – as provided in these rules

or by the procedure for the state where the court is located.”1 Fed. R. Civ. P. 69(a)(2) (emphasis added). “[A]ll discovery procedures provided in the [Federal Rules of Civil Procedure] are available” in aid of execution on a judgment. Fed. R. Civ. P. 69 advisory committee’s note. Discovery under Federal Rule of Civil Procedure Rule 26(b)(1) must be “relevant” and “proportional” to the case’s needs. Fed. R. Civ. P. 26(b)(1). Rule 69 discovery “‘must be calculated to assist in collecting on a judgment.’” Haiying Xi v. Shengchun Lu, --- F. App’x ----, No. 18-3541, 2020 WL 751819 (3d Cir. Feb. 14, 2020) (quoting EM Ltd. v. Republic of Argentina, 695 F.3d 201, 207 (2d Cir. 2012). “Information that could not possibly lead to executable assets” is not relevant. Republic

of Argentina v. NML Capital, Ltd., 573 U.S. 134, 144 (2014). Also, the Court may limit discovery that is “unreasonably cumulative or duplicative, or can be obtained from some other source that is more convenient, less burdensome, or less expensive.” Fed. R. Civ. P. 26(b)(2)(C)(i). However, “‘an evasive or incomplete disclosure, answer or response’” to a Rule 69 discovery request “‘must be treated as a failure to disclose, answer, or respond,’” and supports a motion to compel. Xi, 2020 WL 751819, at *2 (quoting Fed. R.

1 Pennsylvania Rule of Civil Procedure 3117 also allows for discovery in aid of execution. Pa. R. Civ. P. 3117. “Discovery under Rule 3117 . . . is ‘pure discovery,’ intended as an ancillary aid in the discovery of assets.” PaineWebber, Inc. v. Devin, 658 A.2d 409, 412 (Pa. Super. Ct. 1995). It “allows a judgment creditor to obtain information necessary to locate any assets of the judgment debtor and begin the process of execution or attachment of that property.” Randall Mfg., LLC v. Pier Components, LLC, No. 14-346, 2017 WL 1519498, at *2 (M.D. Pa. Apr. 27, 2017). “[I]f the requested testimony or material is not relevant to the discovery of assets of the defendant,” the Court may restrict Rule 3117 requests for discovery. Paine Webber, 658 A.2d at 413. Civ. P. 37(a)(4)). B Because FSS has yet to satisfy the judgment against it, Dreyfus seeks information that will enable it to enforce and collect on the judgment. Dreyfus served

FSS with a supplemental request for production on July 5, 2018 seeking: certain “active contracts” between FSS and its customers, a June 20, 2018 accounts receivable list, the last invoices FSS supplied to customers on the accounts receivable list and copies of FSS “computerized books of account” described at Karen Cavanaugh’s deposition. (See Dreyfus Mot., ECF No. 106, Ex. A.) In August 2018, subject to broad objections that the requests were not relevant or proportional, “vague and ambiguous” and sought documents outside of FSS’s possession or control, FSS represented that it “w[ould] produce any agreements it currently has with its customers to provide services or license software to those customers at a mutually convenient date and location.”

(Dreyfus Mot., Ex. B, at 1-3.) It stated that it “w[ould] supplement the information contained in a document produced at FSS00000216 for a statement of accounts receivable as of February 28, 2017” with information for March 1, 2017 through June 30, 2018 and that it would do the same in response to the request for the FSS computerized books of account described at Cavanaugh’s deposition. (Id. at 3-4.) FSS also represented that it “w[ould] produce a copy of each invoice it issued for services rendered in June, 2018.” (Id. at 3.) Instead of producing the promised copies of its books of account, FSS “extracted and provided limited data” pertaining to its sales and service transactions. (Dreyfus Mot. at 5.) In addition, FSS substituted “invoice level information and customer information” for its requested contracts and invoices. (Id.) Unsatisfied with FSS’s supplemental discovery response, Dreyfus seeks to compel production of: (1) any agreements FSS had as of July 5, 2018 with its customers to provide services or license software to those customers . . . as well as any other contracts related to customers identified in the receivables list that FSS produced on

June 29, 2019; (2) addresses for the customers identified in the June 29, 2019 receivables list; (3) copies of invoices FSS issued for services it rendered to customers identified in the June 29, 2019 receivables list; (4) FSS’s full and complete books of account for 2018; and (5) a full and complete response to its Second Supplementary Post-Deposition Request for Production of Documents transmitted on July 2, 2019.2 (Dreyfus Mot. at ECF p. 1-2 (proposed order)). FSS responds that “in late June, 2019,” it “produced supplemental reports of its accounts payable and accounts receivable” for March 2017 through June 2019” and contends that the “[r]eports contain more than enough information for Plaintiff to

execute upon its judgment, including the names of customers and the amounts due from those customers.” (FSS Resp., ECF No. 125 at 1.) FSS argues that “the only purpose for broadly seeking all contracts, invoices, and books of account is to unreasonably harass, annoy, cause great expense to, and interrupt” its business operations. (Id.) It complains that requested information is not proportional to

2 Federal Rule of Civil Procedure Rule 37

Free access — add to your briefcase to read the full text and ask questions with AI

Related

NML Capital, Ltd. v. Republic of Argentina
695 F.3d 201 (Second Circuit, 2012)
Painewebber, Inc. v. Devin
658 A.2d 409 (Superior Court of Pennsylvania, 1995)

Cite This Page — Counsel Stack

Bluebook (online)
LOUIS DREYFUS COMMODITIES SUISSE, SA v. FINANCIAL SOFTWARE SYSTEMS, INC., Counsel Stack Legal Research, https://law.counselstack.com/opinion/louis-dreyfus-commodities-suisse-sa-v-financial-software-systems-inc-paed-2020.