Robert Kragen v. Experian Information Solutions, Inc. et al

Filing 36

ORDER GRANTING 22 DEFENDANT EXPERIAN'S MOTION TO DISMISS FIRST AMENDED COMPLAINT WITH LEAVE TO AMEND. Signed by Judge Beth Labson Freeman on 3/23/2017. Amended Pleadings due by 4/13/2017. (blflc1S, COURT STAFF) (Filed on 3/23/2017)

Download PDF
1 2 UNITED STATES DISTRICT COURT 3 NORTHERN DISTRICT OF CALIFORNIA 4 SAN JOSE DIVISION 5 ROBERT KRAGEN, 6 Case No. 16-cv-04644-BLF Plaintiff, 7 v. 8 EXPERIAN INFORMATION SOLUTIONS, INC., et al., 9 Defendants. 10 ORDER GRANTING DEFENDANT EXPERIAN’S MOTION TO DISMISS FIRST AMENDED COMPLAINT WITH LEAVE TO AMEND [RE: ECF 22] United States District Court Northern District of California 11 Plaintiff Robert Kragen sues Defendants Experian Information Solutions, Inc. (“Experian”) 12 13 and Citigroup, Inc. (“Citigroup”) for violations of the Fair Credit Reporting Act (“FCRA”), 15 14 U.S.C. § 1681 et seq., and the California Consumer Credit Reporting Agencies Act (“CCRAA”), 15 California Civil Code § 1785.25(a). Experian moves to dismiss Plaintiff’s first amended 16 complaint (“FAC”) pursuant to Federal Rule of Civil Procedure 12(b)(6) for failure to state a 17 claim upon which relief may be granted. For reasons discussed below, the motion is GRANTED 18 WITH LEAVE TO AMEND. I. 19 BACKGROUND1 Plaintiff filed for Chapter 13 bankruptcy protection on October 22, 2011 and his plan was 20 21 confirmed on December 9, 2015. FAC ¶¶ 93, 97, ECF 17. On February 10, 2016, Plaintiff 22 “ordered a three bureau report from Experian, Inc. to ensure proper reporting by Plaintiff’s 23 creditors.” Id. ¶ 98. He alleges that this report (“February 2016 Credit Report”) included twelve 24 different tradelines containing inaccurate, misleading, or incomplete information. Id. ¶ 99. 25 Plaintiff neither attaches a copy of the February 2016 Credit Report nor provides specifics 26 regarding the alleged inaccuracies contained therein. Id. He asserts only that “multiple trade lines 27 1 28 Plaintiff’s factual allegations are accepted as true for purposes of the motion to dismiss. See Reese v. BP Exploration (Alaska) Inc., 643 F.3d 681, 690 (9th Cir. 2011). 1 continued to report Plaintiff’s accounts with past due balances, inaccurate balances, in collections, 2 with late payments and/or charged off. Some accounts even failed to register that Plaintiff was 3 making payments on the account through Plaintiff’s Chapter 13 plan.” Id. Plaintiff disputed the inaccurate tradelines via certified mail sent to three different credit 4 5 reporting agencies (“CRAs”), Experian, Equifax, Inc., and TransUnion, LLC on June 1, 2016. Id. 6 ¶ 100. Each CRA received Plaintiff’s dispute letter and in turn notified the entities that had 7 furnished the disputed information (“furnishers”) by means of automated credit dispute 8 verifications (“ACDVs”). Id. ¶ 102. Plaintiff ordered a second three bureau report from Experian on August 4, 2016 (“August 10 2016 Credit Report”). Id. ¶ 103. Plaintiff alleges that “the inaccuracies had not been updated or 11 United States District Court Northern District of California 9 removed.” Id. ¶ 104. Plaintiff also alleges that “Plaintiff’s Experian score dropped by 88 points,” 12 which “was well below what accurate credit reporting industry standards would project.” Id. ¶ 13 104, 105. Plaintiff further alleges that Citigroup’s report of past due balance did not comport with 14 industry standards, and that as of August 4, 2016, he owed only $568.22 while Citigroup reported 15 the account with a balance of $42,751. Id. ¶ 106. 16 Plaintiff filed this action on August 12, 2016, asserting violations of the FCRA and 17 CCRAA against Experian, Citigroup and JP Morgan Chase Bank, N.A. Compl., ECF 1. Experian 18 moved to dismiss Plaintiff’s complaint on September 13, 2016. Instead of opposing Experian’s 19 motion, Plaintiff filed the operative FAC against the same defendants. Plaintiff subsequently 20 dismissed JP Morgan Chase Bank, N.A. Experian now moves to dismiss the FAC. 21 22 II. LEGAL STANDARD “A motion to dismiss under Federal Rule of Civil Procedure 12(b)(6) for failure to state a 23 claim upon which relief can be granted ‘tests the legal sufficiency of a claim.’” Conservation 24 Force v. Salazar, 646 F.3d 1240, 1241-42 (9th Cir. 2011) (quoting Navarro v. Block, 250 F.3d 25 729, 732 (9th Cir. 2001)). When determining whether a claim has been stated, the Court accepts 26 as true all well-pled factual allegations and construes them in the light most favorable to the 27 plaintiff. Reese v. BP Exploration (Alaska) Inc., 643 F.3d 681, 690 (9th Cir. 2011). However, the 28 Court need not “accept as true allegations that contradict matters properly subject to judicial 2 1 notice” or “allegations that are merely conclusory, unwarranted deductions of fact, or 2 unreasonable inferences.” In re Gilead Scis. Sec. Litig., 536 F.3d 1049, 1055 (9th Cir. 2008) 3 (internal quotation marks and citations omitted). While a complaint need not contain detailed 4 factual allegations, it “must contain sufficient factual matter, accepted as true, to ‘state a claim to 5 relief that is plausible on its face.’” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. 6 Corp. v. Twombly, 550 U.S. 544, 570 (2007)). A claim is facially plausible when it “allows the 7 court to draw the reasonable inference that the defendant is liable for the misconduct alleged.” Id. 8 III. DISCUSSION The FAC contains two claims, one for violation of the FCRA (Claim 1) and the other for 9 violation of the CCRAA (Claim 2). Although the label of the CCRAA claim indicates that it is 11 United States District Court Northern District of California 10 asserted against “Defendants,” it is clear from the body of the FAC that the CCRAA claim is not 12 asserted against Experian. FAC ¶¶ 135-144. Accordingly, this order addresses only the FCRA 13 claim. 14 Plaintiff’s FCRA claim against Experian is subheaded “Failure to Reinvestigate Disputed 15 Information.” Id. ¶¶ 119-120. Plaintiff alleges that after he “disputed the accounts mentioned 16 above” – which the Court takes to mean the twelve unspecified tradelines in the February 2016 17 Credit Report referenced earlier in the FAC – Experian was required to conduct a reasonable 18 investigation and to delete any information that was not accurate. Id. ¶ 121. Plaintiff claims that 19 each CRA was required to “send all relevant information via an ACDV to the furnishers which 20 they did not do.” Id. ¶ 122. Plaintiff alleges generally that Experian “failed to conduct a 21 reasonable investigation and failed to correct the misleading and or inaccurate statements.” Id. ¶ 22 123. Plaintiff asserts that “any basic investigation would have uncovered that certain DFs [data 23 furnishers] were not following credit reporting industry standards.” Id. ¶129. 24 Experian moves to dismiss the FCRA claim on three grounds. First, Experian asserts that 25 Plaintiff has not alleged facts showing that Experian’s credit reporting was inaccurate. Second, 26 Experian argues that Plaintiff has not alleged facts showing an entitlement to damages under the 27 FCRA. And third, Experian asserts that Plaintiff has not alleged any facts showing that Experian’s 28 response to his dispute letter was improper. 3 1 A. Inaccuracy 2 Experian argues that Plaintiff’s claim fails because he has not alleged facts showing that 3 Experian’s credit reporting was inaccurate. If a consumer disputes “the completeness or accuracy 4 of any item of information,” a CRA must “conduct a reasonable reinvestigation to determine 5 whether the disputed information is inaccurate and record the current status of the disputed 6 information, or delete the item.” 15 U.S.C. § 1681i(a)(1). In addition, the CRA must provide 7 notification of the dispute to the furnisher of the information. 15 U.S.C. § 1681i(a)(2). The Ninth Circuit has observed that “[a]lthough the FCRA’s reinvestigation provision, 15 9 U.S.C. § 1681i, does not on its face require that an actual inaccuracy exist for a plaintiff to state a 10 claim, many courts, including our own, have imposed such a requirement.” Carvalho v. Equifax 11 United States District Court Northern District of California 8 Info. Servs., LLC, 629 F.3d 876, 890 (9th Cir. 2010).2 “Thus, even if a . . . CRA fails to conduct a 12 reasonable investigation or otherwise fails to fulfill its obligations under the FCRA, if a plaintiff 13 cannot establish that a credit report contained an actual inaccuracy, then the plaintiff’s claims fail 14 as a matter of law.” Doster v. Experian Info. Sols., Inc., No. 16-CV-04629-LHK, 2017 WL 15 264401, at *3 (N.D. Cal. Jan. 20, 2017) (internal quotation marks and citation omitted). In Carvalho, the Ninth Circuit noted that it previously had “explained that an item on a 16 17 credit report can be ‘incomplete or inaccurate’ within the meaning of the FCRA’s furnisher 18 investigation provision, 15 U.S.C. § 1681s-2(b)(1)(D), ‘because it is patently incorrect, or because 19 it is misleading in such a way and to such an extent that it can be expected to adversely affect 20 credit decisions.’” Carvalho, 629 F.3d at 890 (quoting Gorman v. Wolpoff & Abramson, LLP, 584 21 F.3d 1147, 1163 (2009)). The Ninth Circuit went on to affirm “‘the maxim of statutory 22 construction that similar terms appearing in different sections of a statute should receive the same 23 interpretation,’” id. (quoting United States v. Nordbrock, 38 F.3d 440, 444 (9th Cir. 1994)), and to 24 25 26 27 28 2 Carvalho involved claims asserted under the CCRAA, not the FCRA. See Carvalho, 629 F.3d at 881. However, in discussing the scope of the CCRAA, the Ninth Circuit drew heavily on cases construing the FCRA, see id. at 889-91, and numerous courts have relied on Carvalho’s explication of FCRA requirements when addressing FCRA claims, see, e.g., Artus v. Experian Info. Sols., Inc., No. 5:16-CV-03322-EJD, 2017 WL 346022, at *3 (N.D. Cal. Jan. 24, 2017); Jaras v. Experian Info. Sols., Inc., No. 16-CV-03336-LHK, 2016 WL 7337540, at *4 (N.D. Cal. Dec. 19, 2016). 4 1 cite with approval a First Circuit case, Chiang, which the Ninth Circuit summarized as “deeming 2 the term ‘inaccurate’ in section 1681i(a) to be ‘essentially the same’ as the term ‘incomplete or 3 inaccurate’ in section 1681s-2(b),” id. (citing Chiang v. Verizon New Eng. Inc., 595 F.3d 26, 37 4 (1st Cir. 2010)). Relying on Carvalho, district courts have “applied this ‘patently incorrect or 5 materially misleading’ standard to claims arising under various provisions of the FCRA that 6 involve the accuracy of information.” Prianto v. Experian Info. Sols., Inc., No. 13-CV-03461- 7 TEH, 2014 WL 3381578, at *3 (N.D. Cal. July 10, 2014). In particular, courts in this district have 8 applied the “patently incorrect or materially misleading” standard to the inaccuracy requirement 9 under § 1681i. See, e.g., Banneck v. HSBC Bank USA, N.A., No. 15-cv-02250-HSG, 2016 WL 10 United States District Court Northern District of California 11 12 13 3383960, at *6 (N.D. Cal. June 20, 2016); Prianto, 2014 WL 3381578, at *3. Plaintiff argues that he has alleged inaccuracies in his credit reports under the above standards. The Court disagrees based upon the following pleading deficiencies. 1. Allegations Regarding Three Bureau Reports 14 Perhaps the most obvious deficiency in Plaintiff’s allegations against Experian is his 15 failure to allege that the claimed inaccuracies in two different “three bureau report[s]” were 16 reported by Experian rather than one of the other CRAs. FAC ¶¶ 98, 103. 17 Plaintiff alleges that after his Chapter 13 plan was confirmed, he ordered the February 18 2016 Credit Report and discovered that “multiple trade lines continued to report Plaintiff’s 19 accounts with past due balances, inaccurate balances, in collections, with late payments, and/or 20 charged off. Some accounts even failed to register that Plaintiff was making payments on the 21 account through his Chapter 13 plan.” Id. ¶¶ 97-99. These allegations neither identify Experian as 22 the reporting entity nor identify any particular past due balances or other tradelines in the February 23 2016 Credit Report that were inaccurate. 24 Plaintiff argues that he “explains exactly what was inaccurate about certain data furnishers’ 25 reporting”, and that “[p]aragraphs 106 - 107 of Plaintiff’s FAC highlighted the inaccuracies and 26 problematic tradelines.” Pl.’s Opp. at 4, ECF 24. However, paragraphs 106-107 of the FAC refer 27 to the August 2016 Credit Report. Deficiencies in the allegations regarding the contents of the 28 February 2016 Credit Report – the report that Experian allegedly failed to reinvestigate upon 5 1 receipt of Plaintiff’s dispute letter – cannot be cured by allegations regarding the later August 2 2016 Credit Report. Moreover, Plaintiff does not allege that the asserted inaccuracies in the 3 August 2016 Credit Report were reported by Experian rather than another CRA. FAC ¶¶ 106-107. 4 In order to make out an FCRA claim against Experian, Plaintiff must allege with 5 specificity that Experian reported one or more items of information that were patently incorrect or 6 materially misleading. Other courts in this district have dismissed FCRA claims based upon 7 alleged inaccuracies in three bureau reports where no specificity is provided as to which CRA 8 reported the inaccuracies in question. See, e.g., Doster, 2017 WL 264401, at *6 (“Plaintiff’s FAC 9 makes only general and unspecified allegations that her credit report, which was a three-bureau credit report, contained inaccuracies and that the CRAs reported misleading and inaccurate 11 United States District Court Northern District of California 10 information, but the FAC does not allege any conduct that is specific to Experian.”). 12 13 14 15 Accordingly, the allegations of the FAC are insufficient to make out a claim of inaccurate reporting by Experian. 2. Reporting After Confirmation of Chapter 13 Plan More fundamentally, to the extent that Plaintiff claims that it was inaccurate for Experian 16 to report delinquencies or past due balances after plan confirmation, that theory of liability has 17 been rejected by courts in this district and other districts within the Ninth Circuit. See, e.g., Artus 18 v. Experian Info. Sols., Inc., No. 5:16-CV-03322-EJD, 2017 WL 346022, at *5 (N.D. Cal. Jan. 24, 19 2017) (collecting cases); Doster, 2017 WL 264401, at *6 (“[A]s a matter of law it is not 20 misleading or inaccurate to report a delinquent debt during the pendency of a bankruptcy.”); 21 Polvorosa v. Allied Collection Serv., Inc., No. Case No. 2:16–CV–1508 JCM (CWH), 2017 WL 22 29331, at *3 (D. Nev. Jan. 3, 2017) (“[R]eporting delinquencies during the pendency of a 23 bankruptcy or during a bankruptcy’s automatic stay is not itself a violation of the FCRA.”). 24 Plaintiff argues that these decisions are based upon a misunderstanding of bankruptcy law 25 because they fail to recognize that a bankruptcy court’s order confirming a Chapter 13 plan 26 constitutes a binding final judgment regarding the rights and obligations of the debtor and his or 27 her creditors. Pl.’s Opp. at 7, EFC 39. According to Plaintiff, because a confirmed plan modifies 28 the original debts, any post-confirmation reporting of pre-confirmation delinquencies or balances 6 1 2 is inaccurate. Id. 7-8. It is true that “[t]he provisions of a confirmed plan bind the debtor and each creditor.” 11 U.S.C. § 1327(a). Thus a creditor seeking payment on a debt is entitled only to those payments 4 provided for under the plan, and “any issue decided under a plan is entitled to res judicata effect.” 5 In re Blendheim, 803 F.3d 477, 486 (9th Cir. 2015). However, the Court declines to make the 6 logical leap urged by Plaintiff that these authorities, governing the relationships between parties to 7 a bankruptcy action, make it a violation of the FCRA to report a historically accurate pre- 8 confirmation debt or delinquency. Regardless of how the rights and obligations of the parties to a 9 bankruptcy are modified by a Chapter 13 plan, the original debt did exist prior to confirmation and 10 Plaintiff has cited no authority suggesting that bankruptcy proceedings “erase” that historical fact 11 United States District Court Northern District of California 3 for purposes of the FCRA. 12 Plaintiff’s reliance on In re Luedtke, No. 02-35082-svk, 2008 WL 2952530 (Bankr. E.D. 13 Wis. July 31, 2008), is misplaced. In Luedtke, the bankruptcy court concluded that a creditor 14 whose claim was modified by a Chapter 13 confirmation order had violated that order by 15 continuing to report the original debt to CRAs. Id. at *6. The court suggested that in addition to 16 seeking sanctions for violation of the confirmed plan, the debtor also could have sought relief 17 under the FCRA. Id. In making that suggestion, the bankruptcy court appeared to assume that the 18 creditor’s reporting of the original debt would have constituted an inaccuracy under the FCRA. 19 Id. at *5. That view, expressed in dicta by a bankruptcy court outside the Ninth Circuit almost a 20 decade ago, has not been adopted by the courts in this district. In fact, it appears that Luedtke has 21 been cited by only one other court, which found the decision to be irrelevant to its determination 22 whether the plaintiff had pleaded a viable FCRA claim. See Wylie v. TransUnion, LLC, No. 3:16- 23 CV-102, 2017 WL 835205, at *5 n.6 (W.D. Pa. Mar. 2, 2017) (“[T]he question before the Court is 24 whether Defendants reported accurate information, not whether Defendant violated the bankruptcy 25 code.”) (internal quotation marks and citation omitted). 26 Moreover, with respect to the many debtors who fail to make all required plan payments, 27 the original debt terms ultimately are reinstated. See Blendheim, 803 F.3d at 487. Indeed, 28 historically accurate debts may be reported even after discharge, so long as the credit report 7 1 indicates that the debts were discharged in bankruptcy. See Mortimer v. Bank of Am., N.A., No. C- 2 12-01959 JCS, 2013 WL 1501452, *9-11 (N.D. Cal. Apr. 10, 2013) (furnisher’s reporting that the 3 debt had been delinquent during the pendency of the bankruptcy was historically accurate and thus 4 not actionable under the FCRA where report also indicated that the debt had been discharged in 5 bankruptcy). 6 Plaintiff’s counsel argued at the hearing that allowing reporting of pre-confirmation delinquencies or balances after a Chapter 13 plan has been confirmed will deprive debtors of 8 significant benefits that they expect to obtain through Chapter 13 bankruptcy. That issue is one 9 for Congress to resolve, not this Court. The Court’s task in evaluating Plaintiff’s FAC is to 10 determine whether the facts alleged therein make out a plausible claim that Experian’s credit 11 United States District Court Northern District of California 7 reporting was inaccurate. The Court simply is not persuaded that the reporting of a delinquency or 12 past due balance after plan confirmation is per se inaccurate under the FCRA. 13 However, there appears to be an open question whether such reporting could satisfy the 14 inaccuracy requirement if unaccompanied by any indication that the consumer is in bankruptcy. 15 See Devincenzi v. Experian Info. Sols., Inc., No. 16-CV-04628-LHK, 2017 WL 86131, at *7 (N.D. 16 Cal. Jan. 10, 2017) (declining to decide whether allegations that the “credit report contained no 17 indication at all that the debts were the subject of a pending bankruptcy . . . would be sufficient to 18 state a claim” but granting plaintiff leave to attempt to assert FCRA claim based on that theory). It 19 is this Court’s view that it may well be possible for a plaintiff to allege facts showing that the 20 reporting of a pre-confirmation delinquency is materially misleading absent any reference to a 21 pending Chapter 13 bankruptcy, at least where a confirmed plan governs the timing and amounts 22 of post-confirmation payments on the debt. Plaintiff, however, has not alleged whether or not the 23 reports in question contained information regarding his bankruptcy. 24 3. Metro 2 Format 25 In addition to his theory of FCRA liability based on the effect of plan confirmation, 26 Plaintiff asserts a related theory based on industry standards regarding credit reporting. He 27 devotes 35 of the FAC’s 144 paragraphs to a tutorial on industry standards and in particular the 28 “Metro 2 format” adopted by the Consumer Data Industry Association (“CDIA”). See FAC ¶¶ 378 1 71. According to Plaintiff, “Metro 2 provides instruction on what updates must be made when a 2 bankruptcy is filed,” and deviation from the Metro 2 format is inaccurate or misleading. See Pl.’s 3 Opp. at 3, ECF 24. The Ninth Circuit has not spoken on the effect of the Metro 2 format, if any, 4 on the obligations of CRAs and furnishers under the FCRA. However, district courts within the 5 Ninth Circuit overwhelmingly have held that a violation of industry standards is insufficient, 6 without more, to state a claim for violation of the FCRA. See, e.g., Doster, 2017 WL 264401, at 7 *5 (collecting cases); Mestayer v. Experian Info. Sols., Inc., No. 15-CV-03645-EMC, 2016 WL 8 7188015, at *3 (N.D. Cal. Dec. 12, 2016). 9 The out-of-district cases cited by Plaintiff do not persuade this Court to take a contrary view. In Dreher v. Experian Info. Sols., Inc., No. 3:11-CV-00624-JAG, 2013 WL 2389878, at *7 11 United States District Court Northern District of California 10 (E.D. Va. May 30, 2013), the district court held that industry standards could be considered at the 12 summary judgment stage as part of the totality of evidence regarding the reasonableness of 13 Experian’s failure to identify the main source of disputed information. That ruling does not 14 advance Plaintiff’s argument that deviation from Metro 2 constitutes a per se inaccuracy under the 15 FCRA. In Nissou-Rabban v. Capital One Bank (USA), N.A., No. 15CV1675 JLS (DHB), 2016 16 WL 4508241, at *5 (S.D. Cal. June 6, 2016), the district court held that the plaintiff had alleged a 17 claim under the FCRA where she alleged that Metro 2 was Synchrony’s chosen method of 18 reporting and that Synchrony’s deviation from Metro 2 might be misleading to such an extent as to 19 affect credit decisions. Courts in this district have found such allegations to be insufficient. See, 20 e.g., Mestayer, 2016 WL 7188015, at *3 (credit report that deviated from Metro 2 was not 21 misleading where report disclosed bankruptcy); see also Doster, 2017 WL 264401, at *5 22 (collecting cases). This Court finds the latter decisions to be better reasoned and therefore 23 concludes that allegations that a credit report deviated from the Metro 2 format is insufficient, 24 without more, to state a claim under the FCRA. 25 The Court does not mean to suggest that Metro 2 is wholly irrelevant to the evaluation of a 26 claim asserted under the FCRA. It may be that allegations of deviations from the Metro 2 format 27 could bolster other allegations of inaccuracy or be relevant to allegations of negligence on the part 28 of the reporting entity. However, Plaintiff’s reliance on Metro 2 as an independent source of 9 1 liability under the FCRA is unavailing. 2 B. Damages 3 In addition to arguing that Plaintiff has failed to allege facts sufficient to show actual 4 inaccuracy in reporting, Experian asserts that Plaintiff has failed to allege facts sufficient to entitle 5 him to recovery of damages. The FCRA creates a private right of action for willful or negligent 6 noncompliance with § 1681i. 15 U.S.C. §§ 1681n & o; Gorman, 584 F.3d at 1154. If a failure to 7 comply with § 1681i is willful, the plaintiff may recover either actual damages or statutory 8 damages between $100 and $1,000, as well as any appropriate punitive damages. 15 U.S.C. § 9 1681n(a). If a failure to comply with § 1681i is negligent, the plaintiff is limited to recovery of “any actual damages sustained by the consumer as a result of the failure.” 15 U.S.C. § 11 United States District Court Northern District of California 10 1681o(a)(1). Experian contends that Plaintiff has not alleged facts showing entitlement to 12 recovery under either theory. 13 1. Willfulness 14 A defendant acts “willfully” for purposes of the FCRA if the defendant knowingly or 15 recklessly disregards its statutory duties. Safeco Ins. Co. of Am. v. Burr, 551 U.S. 47, 57-58 16 (2007). “[A] company subject to FCRA does not act in reckless disregard of it unless the action is 17 not only a violation under a reasonable reading of the statute’s terms, but shows that the company 18 ran a risk of violating the law substantially greater than the risk associated with a reading that was 19 merely careless.” Id. at 69. Thus a plaintiff seeking to recover damages under a willfulness theory 20 “must allege, at a minimum, that the defendant’s reading of the FCRA is ‘objectively 21 unreasonable.’” Kirchner v. Shred-it USA Inc., No. 2:14-1437 WBS, 2014 WL 6685210, at *1 22 (E.D. Cal. Nov. 25, 2014) (quoting Safeco, 551 U.S. at 69). 23 As discussed above, Plaintiff has not sufficiently alleged that Experian’s reporting 24 contained an actual inaccuracy. Even had he done so, he has not alleged any facts showing that 25 such inaccuracy was the result of Experian’s knowing or reckless disregard of its statutory duties. 26 Plaintiff argues in his opposition that Experian recklessly disregarded its statutory duties by failing 27 to reinvestigate Plaintiff’s dispute or correct the alleged inaccuracies as prescribed by industry 28 standards, when it knew that the disputed report deviated from Metro 2. Pl.’s Opp. at 10-11, ECF 10 1 24. However, as discussed, deviation from the Metro 2 format alone is insufficient to state a 2 violation of the FCRA. 2. 3 4 Negligence In order to recover under a negligence theory, Plaintiff must plead and prove actual 5 damages resulting from Experian’s violation of the FCRA. 15 U.S.C. § 1681o(a)(1). Plaintiff’s 6 FCRA claim against Experian is based on his allegations that after Plaintiff disputed information 7 in the February 2016 Credit Report, Experian failed to reinvestigate. See FAC ¶¶ 120-134. 8 However, he does not allege facts showing that he suffered any damages flowing from that failure. 9 See id. In opposition to Experian’s motion, Plaintiff argues that “Plaintiff has paid Plaintiff’s counsel several thousand dollars to reorganize and repair his credit under Chapter 13”; “Plaintiff 11 United States District Court Northern District of California 10 has also incurred a substantial [sic] in attorney’s fees in attempting to correct the inaccuracies on 12 his credit report”; and “Plaintiff cannot and continues to be unable to apply for credit because his 13 score remains extremely low.” Pl.’s Opp. at 11, ECF 24. The Court questions whether these 14 allegations are sufficient to plead damages recoverable under the FCRA. However, the Court need 15 not resolve that question, as Plaintiff has not included any of these allegations in his FCRA claim 16 against Experian. 17 18 Accordingly, the FAC is subject to dismissal on the ground that Plaintiff has failed to allege facts showing an entitlement to damages. Lack of Factual Allegations re Experian’s Response to Dispute Letter 19 C. 20 Experian’s final argument is that Plaintiff has not provided any factual basis for his 21 allegation that Experian’s response to his dispute letter was inadequate. The Court agrees. 22 Plaintiff alleges that after he disputed the February 2016 Credit Report, Experian was 23 required to conduct a reasonable investigation and to delete any information that was not accurate. 24 FAC ¶ 121. Plaintiff then claims that each CRA is required to “send all relevant information via 25 an ACDV to the furnishers which they did not do.” Id. ¶ 122. When a consumer disputes 26 information on a credit report, the CRA must provide notification of the dispute to the furnisher of 27 the information. 15 U.S.C. § 1681i(a)(2). Thus an allegation that Plaintiff disputed a particular 28 account reported in the February 2016 Credit Report, and that Experian failed to notify the 11 1 furnisher of the disputed information, would state a claim under the FCRA, assuming that all other 2 pleading requirements regarding inaccuracy and damages were satisfied. However, as discussed 3 above, Plaintiff’s allegations regarding the asserted inaccuracies in the February 2016 Credit 4 Report do not identify any particular account or item of information from Experian. Allegations 5 that Experian failed to notify the unidentified furnishers of unidentified information regarding 6 unidentified accounts are insufficient to make out a plausible claim that Experian violated its 7 obligations under the FCRA. Moreover, elsewhere in the FAC Plaintiff alleges that “each CRA 8 received Plaintiff’s dispute letter and in response sent Plaintiff’s dispute to each DF via an 9 ACDV.” FAC ¶ 102. Based on that allegation, it would appear that Experian did satisfy its 10 United States District Court Northern District of California 11 notification obligations under the FCRA. Plaintiff’s conclusory allegations that Experian “failed to conduct a reasonable 12 investigation,” Id. ¶ 123, likewise are inadequate to state a claim under the FCRA. See O’Connor 13 v. Capital One, N.A., No. CV 14-00177-KAW, 2014 WL 2215965, at *7 (N.D. Cal. May 29, 14 2014) (No FCRA claim stated where plaintiff “fails to offer any factual allegations supporting his 15 contention that Defendant’s investigation of his disputed account was unreasonable”). 16 D. 17 In deciding whether to grant Plaintiff leave to amend his pleading, the Court must consider 18 the factors set forth by the Supreme Court in Foman v. Davis, 371 U.S. 178 (1962), and discussed 19 at length by the Ninth Circuit in Eminence Capital, LLC v. Aspeon, Inc., 316 F.3d 1048 (9th Cir. 20 2003). A district court ordinarily must grant leave to amend unless one or more of the Foman 21 factors is present: (1) undue delay, (2) bad faith or dilatory motive, (3) repeated failure to cure 22 deficiencies by amendment, (4) undue prejudice to the opposing party, and (5) futility of 23 amendment. Eminence Capital, 316 F.3d at 1052. “[I]t is the consideration of prejudice to the 24 opposing party that carries the greatest weight.” Id. However a strong showing with respect to 25 one of the other factors may warrant denial of leave to amend. Id. 26 Leave to Amend The first factor (undue delay), second factor (bad faith), and fourth factor (undue 27 prejudice) do not weigh against granting leave to amend at this time, although the Court may well 28 have a different view in the event that Plaintiff’s counsel fails to address the deficiencies 12 1 addressed herein and persists in submitting pleadings consisting primarily of copy-and-paste 2 boilerplate allegations. The third factor (failure to cure deficiencies) weighs slightly against 3 granting leave to amend, as Plaintiff previously amended his pleading. However, the present order 4 represents the first detailed guidance that Plaintiff has received from the Court. Finally, with 5 respect to the fifth factor (futility of amendment), the Court has grave reservations whether 6 Plaintiff will be able to state a viable FCRA claim against Experian. However, because it is not 7 clear that Plaintiff cannot do so, the Court will grant him leave to amend. If Plaintiff chooses to amend his FCRA claim against Experian, he shall allege with 8 9 specificity what reporting is attributable to Experian and shall either attach a copy of each report or allege the offending tradelines verbatim. Failure to do so will be deemed an admission that 11 United States District Court Northern District of California 10 Plaintiff is incapable of pleading specific facts giving rise to liability under the FCRA. 12 IV. ORDER 13 (1) Experian’s motion to dismiss the FAC is GRANTED WITH LEAVE TO AMEND; 14 (2) Any amended pleading shall be filed on or before April 13, 2017; and 15 (3) Leave to amend is limited to the FCRA claim discussed in this order; Plaintiff 16 may not add new claims or parties without express leave of the Court. 17 18 19 20 Dated: March 23, 2017 ______________________________________ BETH LABSON FREEMAN United States District Judge 21 22 23 24 25 26 27 28 13

Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.


Why Is My Information Online?