Navarro v. Portfolio Recovery Associates LLC

District Court, D. Arizona·Decided September 16, 2019·No. 2:18-cv-02333·Unknown

Opinion

WO

James Navarro, No. CV-18-02333-PHX-JJT

Plaintiff, ORDER

v.

Portfolio Recovery Associates, LLC,

Defendant. At issue is Defendant’s Motion for Summary Judgment (Doc. 26, DMSJ), supported by Defendant’s Statement of Facts (Doc. 27, DSOF), to which Plaintiff filed a Response (Doc. 30) and Defendant filed a Reply (Doc. 36); and Plaintiff’s Motion for Summary Judgment (Doc. 28, PMSJ), supported by Plaintiff’s Statement of Facts (Doc. 29, PSOF), to which Defendant filed a Response (Doc. 32) and Plaintiff filed a Reply (Doc. 35). For the reasons that follow, the Court grants Defendant’s Motion and denies Plaintiff’s Motion. Plaintiff’s Complaint (Doc. 1) alleges a single violation of the Fair Debt Collection Practices Act (FDCPA), 15 U.S.C. §§ 1692 et seq. Before the Court are the parties’ cross motions for summary judgment. In 2017, Plaintiff obtained his credit report from the three major credit reporting agencies and noticed that Defendant, a debt collector and data furnisher, was reporting a delinquent account. Around December 6, 2017, Defendant received a letter1 stating that 1 It appears that Plaintiff did not actually send the letter himself. The letter was Plaintiff disputed the reported account. (PSOF, Ex. 1.) On December 27, Defendant electronically communicated to the credit reporting agencies an “XB” compliance code for Plaintiff’s account. (DSOF, Ex. E; Ex. B.) Data furnishers, such as Defendant, are required to use Compliance Condition Codes when communicating to the reporting agencies the status of accounts. An XB code signals to the agencies that the account is in dispute. (DSOF, Ex. B at 2.) Defendant, who reports to the agencies on the 8th and 27th of every month, again reported an XB code on January 8, 2018. (DSOF, Ex. E.) On January 11, Defendant sent Plaintiff a letter stating that it had completed its investigation into the dispute and determined that the reported account was valid. (DSOF, Ex. F.) It attached a copy of two statements reflecting a delinquent credit card account that Plaintiff had opened with Capital One Bank. Plaintiff admitted that he received this letter. (DSOF, Ex. D at 7.) Nothing in the record indicates whether Plaintiff followed up with Defendant or continued to dispute the debt. After completing its investigation in January, Defendant began submitting an “XC” compliance code to the credit reporting agencies. (DSOF, Ex. E; Ex. B.) An XC code informs the reporting agencies that the data furnisher has completed the investigation into the disputed account but that the consumer disagrees with the outcome of the investigation. Defendant continued to submit an XC code twice monthly until Plaintiff brought this lawsuit. (DSOF, Ex. E; Ex. B.) On July 2, 2018—three weeks before filing suit—Plaintiff entered into a payment plan with Defendant for the very debt that is the subject of this litigation.2 (DSOF, Ex. G.) Plaintiff pulled his credit report three days later and discovered that Experian was still reporting Plaintiff’s outstanding and past-due debt with Defendant. On July 25, the day he

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

Navarro v. Portfolio Recovery Associates LLC, (D. Ariz. 2019).

Navarro v. Portfolio Recovery Associates LLC (Navarro v. Portfolio Recovery Associates LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

First Nat. Bank of Ariz. v. Cities Service Co.
391 U.S. 253 (Supreme Court, 1968)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
Michael B. Selsor v. Stephen W. Kaiser
22 F.3d 1029 (Tenth Circuit, 1994)
Block v. City of Los Angeles
253 F.3d 410 (Ninth Circuit, 2001)
Taylor v. List
880 F.2d 1040 (Ninth Circuit, 1989)