Loancare LLC v. Dimont & Associates, LLC

District Court, S.D. New York·Decided July 7, 2023·No. 1:22-cv-09286·Unknown

Opinion

VIA ECF 570 Lexington Avenue 8th Floor Honorable Judge Jesse M. Furman New York, NY 10022 United States District Court USA ee oe enn York t +1 212.252.0004 nited States Courthouse f +1 212.832.4920 AO Centre Street New York, NY 10007 kennedyslaw.com t +1 646 625 3995 Martin. West @kennedyslaw.com 5 July 2023

Re: Loancare LLC v. Dimont & Associates, LLC 22-cv-09286-JMF-SLC Dear Judge Furman, We represent Dimont & Associates, LLC (“Dimont’) in this matter and write in response to Plaintiff Loancare LLC’s (“Loancare”) letter dated June 29, 2023 and to cross-move for a discovery extension. Put simply, this matter presents exceptional circumstances that warrant an extension of the presently set discovery deadlines because, despite the parties’ diligent efforts, it is impossible for Dimont to review Loancare’s 1.5 million document production (estimated to be approximately 15 million pages of documents)! and prepare Dimont’s witnesses for depositions in time for the August 1, 2023 contention interrogatory deadline. Accordingly, Dimont respectfully requests a three month extension to the current discovery deadlines. Some background regarding this dispute is helpful to understand the present situation. Loancare has filed this claim against Dimont seeking to recover damages it allegedly sustained for Dimont’s improper processing of over 20,000 loan reimbursement claims, some for as little as $.01.

' This presumes that Loancare’s 1.5 million documents are responsive and not simply an improper document dump. While Dimont believes that this production was what Loancare referred to as the “fat file” which comprises all of the documents related to each individual reimbursement request in dispute, it is simply too early in the review process to make this determination.

Kennedys

These claims allegedly arise from Loancare’s relationship with Dimont under which Loancare contracted with Dimont to have Dimont prepare and submit loan reimbursement requests for federally-backed home loans that had gone into foreclosure. In additional to the loan holder being entitled to recover the loan principal from the respective federal agency, the loan holder would also be entitled to recover other expenses related to the foreclosure process, including property inspections, lawn care, utilities, maintenances, state and local taxes, and related interest. Loancare required Dimont to perform this work through various cloud-based software programs that Loancare had put in place. This is important as it relates to Loancare’s letter because it means that, with some limited exceptions, Dimont did not maintain local copies of the supporting claim documents or the claims it was submitting to the federal agencies. Those records could only be accessed through Loancare’s cloud-based systems. After Loancare began making demands for payment on Dimont related to the present dispute, Dimont employees began reviewing the disputed claims and working with Loancare to determine whether, in fact, there were mistakes made on these claims. After several exchanges between Loancare and Dimont where Dimont demonstrated that a significant portion of the disputed claims were, in fact, properly processed and submitted, Loancare terminated Dimont’s access to the cloud-based systems and Dimont was then unable to further access or review the claims to make determinations about the validity of the disputes. Practically speaking, what this means is that from the middle of 2022 until Loancare’s 1.5 million document production,” Dimont has been unable to make determinations as the validity of the, now, 20,000 claims upon which Loancare seeks to recover. These are the specific documents that Dimont utilized in filing the reimbursement requests to the respective federal agencies. Thus, under circumstances where cloud-based systems were not used, Dimont would have had local access to these records and would have been able to prepare its defense over the last several months since the complaints were filed instead of having to wait for Loancare’s production. Instead, Dimont is now only just able to begin doing so.

* To provide some additional context as to how voluminous this production is, Kennedys preferred e-discovery vendor advised that across all of Kennedys US offices, Kennedys has approximately 7TB of data uploaded and Loancare’s production here was 2.7TB—over one-third of the total data. Furthermore, the transfer of this data is not a matter of simply dragging and dropping folders, the simple transfer of the files takes days. And, quotes regarding the costs to host this data have exceeded $65,000 per month with some vendors.

2 of 4

Kennedys

Moreover, in light of the voluminous records in this case, and in an attempt to mitigate litigation costs and time, Dimont proposed an early settlement in this matter and the Court referred this case to Magistrate Judge Cave in March 2022. (ECF No. 42.) Magistrate Judge Cave held a conference with the parties on March 14, 2023 and scheduled a settlement conference for June 8, 2023, with the parties to exchange high level discovery before the conference in an effort to facilitate settlement discussions. (ECF No. 47.) In discussions between counsel, Dimont advised Loancare that it would require proof of payment of damages by Loancare to evaluate Loancare’s claim. In advance of the settlement conference, Dimont made a production on May 19, 2023 containing, in pertinent part, the results of the audits that Dimont completed prior to being disconnected from accessing the claim records. Loancare produced no documents with the exception of those attached to its settlement statement (a declaration under Fed. R. Civ. P. 408 and a preliminary expert report, also under Fed. R. Civ. P. 408). Because the damages documentation had not been produced, the session was not particularly productive and Magistrate Judge Cave scheduled another settlement conference session for July 5, 2023, with the understanding that Loancare would produce documents regarding its damages in advance of that date so that Dimont could make a proper evaluation of Loancare’s claim. (ECF No. 53.) Following receipt of Loancare’s production, Dimont attempted a targeted review of the production to find and review the damages documentation in Loancare’s production. During the meet and confer on June 27, 2023, Loancare advised that the damages documentation had still not produced and would be forthcoming. It was not until July 3, 2023 that Loancare produced documentation allegedly evidencing proof of damages in the form of a spreadsheet. In light of the last minute production, Magistrate Judge Cave set a third settlement conference for July 27, 2023. So, to be clear, Dimont has been diligent in moving this case forward with a goal toward reaching an efficient and inexpensive resolution of this matter. That being said, there have been delays in preparing Dimont’s full production of electronically stored information. This 1s largely because Dimont’s loan processing division is no longer extant as it has largely been transitioned to co-defendant Investor Claims Solutions, LLC (“ICS”) and due to some technological issues with respect to how Dimont backed up its emails. Of the 21 deposition notices served on Dimont

3 Dimont has not had sufficient time to review, understand, and analyze this spreadsheet.

3 of 4

Kennedys

by Loancare, only three of the individuals are still affiliated with Dimont. As discussed in Loancare’s letter, during the meet and confer, Dimont advised that it would make the initial production of its electronically stored information by July 14, 2023.

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

Loancare LLC v. Dimont & Associates, LLC, (S.D.N.Y. 2023).

Loancare LLC v. Dimont & Associates, LLC (Loancare LLC v. Dimont & Associates, LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.