Opinion

Opinion

Court
District Court, S.D. California
Filed
Jul 17, 2024
Cited by
0 cases
Authority
More cited than 41.5%

The opinion

1

2

3

4

5

6 UNITED STATES DISTRICT COURT

7 SOUTHERN DISTRICT OF CALIFORNIA

8

9 ALEJANDRA RODRIGUEZ, an Case No.: 23-CV-2236 JLS (JLB)

individual; AL ALLAL, an individual,

10

ORDER GRANTING IN PART AND

Plaintiffs,

11 DENYING IN PART DEFENDANTS’

v. MOTION TO DISMISS PORTIONS

12

OF PLAINTIFFS’ FIRST AMENDED

PROFIT SHARING PLAN II

13 COMPLAINT

ADMINISTRATIVE COMMITTEE (a

14 business entity form unknown), AS PLAN

(ECF No. 21)

ADMINISTRATOR OF THE

15

TORRENCE’S FARM IMPLEMENTS

16 PROFIT SHARING PLAN II; KIRK

HESTER; KIMBERLY HESTER-WAKE;

17

and DOES 1 through 10, inclusive,

18

Defendants.

19

20 Presently before the Court is Defendants PROFIT SHARING PLAN II

21 ADMINISTRATIVE COMMITTEE (the “Committee”), Kirk Hester (“Hester”), and

22 Kimberly Hester-Wake’s (“Hester-Wake”) (collectively, “Defendants”) Motion to Dismiss

23 Portions of Plaintiffs’ First Amended Complaint (“Mot.,” ECF No. 21) and Memorandum

24 of Points and Authorities (“Mem.,” ECF No. 21-1) in support thereof. Plaintiffs Alejandra

25 Rodriguez (“Rodriguez”) and Al Allal (“Allal”) (collectively, “Plaintiffs”) filed an

26 Opposition (“Opp’n,” ECF No. 22) to the Motion, to which Defendants filed a Reply

27 (“Reply,” ECF No. 25). The Court then took the Motion under submission without oral

28 argument on March 14, 2024. ECF No. 23. Having carefully considered the First

1 Amended Complaint (“FAC,” ECF No. 18), the Parties’ submissions, and the law, the

2 Court GRANTS IN PART AND DENIES IN PART Defendants’ Motion.

3 BACKGROUND

4 In this case, two former employees accuse the administrator of their employee

5 benefit plan of failing to comply with the federal Employee Retirement Income Security

6 Act (“ERISA”).

7 Until March 2020, Rodriguez and Allal worked for Torrence’s Farm Implements

8 (“Torrence’s Farm”), a privately held California corporation that sold and maintained

9 tractors until it ceased operations following its acquisition by a competitor. FAC ¶¶ 4–6.

10 While employed at Torrence’s Farm, both Rodriguez and Allal enrolled in the

11 “TORRENCE’S FARM IMPLEMENTS PROFIT SHARING PLAN II (the “Plan”), which

12 provides retirement benefits “funded through discretionary contributions by” Torrence’s

13 Farm. Id. ¶¶ 6, 10–12.1 The Plan designates the Committee as its administrator, and Hester

14 and Hester-Wake served (at least, at one time) as (1) officers, directors, or employees of

15 Torrence’s Farm and (2) individual members of the Committee. Id. ¶¶ 6–8.

16 Plaintiffs’ accusations focus on three actions Defendants allegedly failed to

17 complete. First, the provision of required annual statements. Plaintiffs contend that

18 because the Plan (1) provides them each with their own account but (2) does not allow

19 them to direct the investment of account assets, the Committee must provide them “a

20 pension benefit statement at least once each calendar year” pursuant to 29 U.S.C.

21 § 1025(a). Id. ¶ 24. Defendants, however, have not provided either Plaintiff with a pension

22 benefit statement since 2017. Id. ¶¶ 15, 20, 25.

23 Second, responses to requests for information. Hester allegedly informed Rodriguez

24 in early 2020 that the Plan “would be paying out all of the vested profits-sharing money in

25 April of that year.” Id. ¶ 16. On March 27, Rodriguez then requested “her Profit-Sharing

26

27 1 Rodriguez joined the Plan in 2001. FAC ¶¶ 13–14. Allal, by contrast, joined the plan in 1996, received

28 a full payout of his vested pension in 2018, but nevertheless continued to participate in the plan until 2020.

1 Statements” from Hester and Hester-Wake, who informed her they would provide “an

2 update the following week.” Id. ¶ 17. This story repeated on April 9, when Rodriguez

3 again requested her profit-sharing statements and again secured the promise of an update.

4 Id. In May, however, radio silence commenced. Hester and Hester-Wake ignored emails

5 from Rodriguez “requesting her account statements” on May 11, 19, and 25. Id.

6 Approximately two years passed, apparently without action from either side.

7 Id. ¶ 18. Then, Rodriguez asked her financial advisor Greg Kolodi (“Kolodi”) to secure

8 her pension benefit statements. Id. “From March to May 2022, . . . Kolodi made numerous

9 requests and demands for information from . . . Defendants, but no information was ever

10 provided.” Id. Per Rodriguez, Defendants were required, again by 29 U.S.C. § 1025, to

11 provide her with the pension benefit statements upon request. Id. ¶ 28.

12 Finally, a decision on Rodriguez’s loan request. Plaintiffs allege that, “[p]ursuant to

13 the terms of the Plan,” beneficiaries may obtain a loan upon written request. Id. ¶ 34. In

14 need of funds for her daughter’s medical care, Rodriguez “submitted a loan application to”

15 Hester and Hester-Wake on September 10, 2019. Id. Defendants, however, never

16 responded to the request. Id. ¶ 35. Plaintiffs contend this failure violates 29 U.S.C. § 1133.

17 Id.

18 Plaintiffs filed this action in the Central District of California on October 6, 2023.

19 ECF No. 1. The Parties stipulated to transfer to this District on December 6, 2023, and the

20 case fell to the undersigned the next day. ECF Nos. 14, 17. Plaintiffs then filed the FAC

21 on January 19, 2024. In it, Plaintiffs bring three causes of action: (1) failure to provide

22 account statements pursuant to 29 U.S.C. §§ 1132(c), 1025(a); (2) failure to provide

23 requested documents pursuant to 29 U.S.C. §§ 1132(c), 1025(a); and (3) failure to respond

24 to a request for benefits as required by 29 U.S.C. § 1133. FAC at 7–9. They seek statutory

25 damages of $100 per day since October 6, 2020, under their first cause of action and $100

26 per day since March 27, 2020, under their second. Id. at 10. They also request an order

27 requiring Defendants to (1) provide yearly benefit statements to both Plaintiffs and (2)

28 review Rodriguez’s request for a loan and award her all benefits due. Id. Finally, Plaintiffs

1 hope to recoup reasonable attorney’s fees and costs. Id.

2 LEGAL STANDARD

3 Federal Rule of Civil Procedure 12(b)(6) permits a party to raise by motion the

4 defense that the complaint “fail[s] to state a claim upon which relief can be granted.” A

5 court evaluates whether a complaint states a cognizable legal theory and sufficient facts in

6 light of Federal Rule of Civil Procedure 8(a), which requires a “short and plain statement

7 of the claim showing that the pleader is entitled to relief.” Although Rule 8 “does not

8 require ‘detailed factual allegations,’ . . . it demands more than an unadorned, the-

9 defendant-unlawfully-harmed-me accusation.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009)

10 (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 544, 555 (2007)). In other words, “a

11 plaintiff’s obligation to provide the ‘grounds’ of his ‘entitle[ment] to relief’ requires more

12 than labels and conclusions, and a formulaic recitation of the elements of a cause of action

13 will not do.” Twombly, 550 U.S. at 555 (alteration in original) (quoting

14 Fed. R. Civ. P. 8(a)).

15 To survive a motion to dismiss, “a complaint must contain sufficient factual matter,

16 accepted as true, to ‘state a claim to relief that is plausible on its face.’” Iqbal, 556 U.S.

17 at 678 (quoting Twombly, 550 U.S. at 570). A claim is facially plausible when the facts

18 pleaded “allow[] the court to draw the reasonable inference that the defendant is liable for

19 the misconduct alleged.” Id. That is not to say that the claim must be probable, but there

20 must be “more than a sheer possibility that a defendant has acted unlawfully.” Id. Facts

21 “‘merely consistent with’ a defendant’s liability” do not demonstrate a plausible

22 entitlement to relief. Id. (quoting Twombly, 550 U.S. at 557).

23 Review under Rule 8(a) requires a context-specific analysis involving a court’s

24 “judicial experience and common sense.” Id. at 679. A court must “accept[] all factual

25 allegations in the complaint as true and constru[e] them in the light most favorable to the

26 nonmoving party.” Skilstaf, Inc. v. CVS Caremark Corp., 669 F.3d 1005, 1014 (9th Cir.

27 2012). That said, the Court need not accept as true “legal conclusions” contained in the

28 complaint. Iqbal, 556 U.S. at 678.

1 If a complaint does not state a plausible claim for relief, a court should grant leave

2 to amend unless it determines that no modified contention “consistent with the challenged

3 pleading could . . . cure the deficiency.” DeSoto v. Yellow Freight Sys., Inc., 957 F.2d 655,

4 658 (9th Cir. 1992) (quoting Schreiber Distrib. Co. v. Serv-Well Furniture Co.,

5 806 F.2d 1393, 1401 (9th Cir. 1986)). “The Ninth Circuit has instructed that the policy

6 favoring amendments ‘is to be applied with extreme liberality.’” Abels v. JBC Legal Grp.,

7 P.C., 229 F.R.D. 152, 155 (N.D. Cal. 2005) (quoting Morongo Band of Mission Indians v.

8 Rose, 893 F.2d 1074, 1079 (9th Cir. 1990)).

9 DISCUSSION

10 Defendants’ Motion targets Plaintiffs’ second and third causes of action. Defendants

11 first contend Plaintiffs’ second claim (1) is untimely, (2) improperly relies on requests

12 made by third parties, (3) duplicates Plaintiffs’ first claim, and (4) impermissibly targets

13 Hester and Hester-Wake. Turning to Plaintiffs’ third claim, Defendants argue 29 U.S.C.

14 § 1133 does not contain a private right of action. In the alternative, Defendants suggest (1)

15 Rodriguez failed to exhaust the Plan’s administrative remedies and (2) a loan request does

16 not qualify as a “claim for benefits” under ERISA. The Court will address each claim, and

17 each argument, in turn.

18 I. Refusal to Provide Requested Information (Claim II)

19 ERISA provides a private right of action to recover statutory damages from a plan

20 administrator who either refuses to supply requested information or fails to provide an

21 annual report in complete form. 29 U.S.C. § 1132(a)(1)(A), (c)(1). That said, an

22 administrator need only comply with a request for information if “such administrator is

23 required by [the relevant] subchapter to furnish” the information in question. See id.

24 A. Statute of Limitations

25 The Parties agree that a three-year statute of limitations applies to Rodriguez’s claim

26 for statutory damages under 29 U.S.C. § 1132(c)(1). See Mem. at 3 (citing Cal. Civ. Proc.

27 Code § 338(a)); Opp’n at 3 (citing Stone v. Travelers Corp., 58 F.3d 434, 437–38 (9th Cir.

28 1995)). And a claim under 29 U.S.C. § 1132(c)(1) accrues, for purposes of the statute of

1 limitations, where “the plaintiff knows or has reason to know of the injury which is the

2 basis of the action.” Beserra v. Albertsons Cos., No. EDCV20573PSGSPX, 2020 WL

3 13348402, at *8 (C.D. Cal. Aug. 19, 2020) (quoting Santoyo v. Kraft Foods Glob., Inc.,

4 No. 1:07CV937DLB, 2008 WL 552443, at *3 (E.D. Cal. Feb. 26, 2008)); cf. also Wetzel

5 v. Lou Ehlers Cadillac Grp. Long Term Disability Ins. Program, 222 F.3d 643, 649 (9th

6 Cir. 2000) (holding, albeit with respect to a claim for denied benefits, that “an ERISA cause

7 of action accrues either at the time benefits are actually denied or when the insured has

8 reason to know that the claim has been denied” (citations omitted)).

9 1. Timeliness

10 Where a § 1132(c)(1)(B) claim is concerned, determining the date of accrual is

11 simple. A plaintiff has reason to know the plan administrator has denied their request for

12 information once thirty days have passed without a response. See, e.g., Brown v. Rawlings

13 Fin. Servs., LLC, 868 F.3d 126, 128 (2d Cir. 2017) (“Because [§ 1132(c)(1)] required

14 Backus as plan administrator to respond to the [July 2014] request within thirty days,

15 Brown’s claim accrued in August 2014.”); Reynolds v. Merrill Lynch Basic Long Term

16 Disability Plan, No. CIV. 15-00109 JMS, 2015 WL 3822319, at *2 (D. Haw. June 19,

17 2015) (collecting cases reaching the same conclusion).

18 Here, the applicable three-year statute of limitations bars claims arising out of

19 requests submitted on or before early September 2020. Rodriguez filed suit on October 6,

20 2023. So, Rodriguez cannot bring § 1132(c) claims that accrued prior to October 6, 2020;

21 i.e., claims stemming from requests for information Rodriguez submitted more than thirty

22 days prior to October 6. Unfortunately for Rodriguez, therefore, claims arising from her

23 March 27, 2020, April 9, 2020, or May 2020 requests are time-barred.

24 2. Equitable Estoppel

25 Plaintiffs suggest that Defendants should be equitably estopped from invoking the

26 statute of limitations defense because they allegedly assured Rodriguez—once in March

27 and once in April—that they would provide her an “update.” See FAC ¶¶ 17, 29. These

28 “two years of false promises and assurances,” per Plaintiffs, rendered it reasonable for

1 Rodriguez to (1) wait two years before asking her financial advisor to renew her request

2 for documents and (2) wait another year and a half before filing suit. Opp’n at 4–5.

3 The Court is unpersuaded. A defendant may be equitably estopped from relying on

4 a statute of limitations defense when it “takes active steps to prevent a plaintiff from suing

5 on time, as by promising not to plead the statute of limitations.” Cada v. Baxter Healthcare

6 Corp., 920 F.2d 446, 450–51 (7th Cir. 1990). This doctrine, “sometimes called fraudulent

7 concealment,” asks whether a plaintiff actually and reasonably relied on the defendant’s

8 conduct or representations. Huseman v. Icicle Seafoods, Inc., 471 F.3d 1116, 1121–22 (9th

9 Cir. 2006). Here, equitable estoppel is unavailable for one simple reason—Rodriguez’s

10 alleged reliance on Defendants’ promises was not reasonable.

11 Defendants’ promises appear to have ceased in May of 2020—approximately two

12 years before Rodriguez renewed her document request and approximately 3.5 years before

13 Plaintiff sued. See FAC ¶ 17. The Court does not see how Defendants’ initial promises of

14 an update could have duped Rodriguez, when faced with Defendant’s repeated failure to

15 answer her May emails, into waiting multiple years before taking further action. So, even

16 if Defendants’ assurances justified some form of equitable relief until they ceased, they do

17 not excuse Rodriguez’s post-assurance delay. Cf. Huseman, 471 F.3d at 1121–22

18 (affirming denial of equitable tolling because the plaintiff’s alleged reliance was not

19 reasonable).

20 Though the Court could stop there, the Court will pause to address a common

21 misconception apparent in Defendants’ brief. The Reply equates equitable estoppel with

22 equitable tolling. See, e.g., Reply at 2 (“The statute of limitations applicable to the second

23 cause of action should not be tolled.” (capitalization altered)). These two doctrines,

24 however, are distinct. Lukovsky v. City & Cnty. of San Francisco, 535 F.3d 1044, 1051

25 (9th Cir. 2008).

26 Plaintiffs do not here seek equitable tolling, and for good reason. Generally, “a

27 litigant seeking equitable tolling bears the burden of establishing two elements: (1) that he

28 has been pursuing his rights diligently, and (2) that some extraordinary circumstances stood

1 in his way.” Kwai Fun Wong v. Beebe, 732 F.3d 1030, 1052 (9th Cir. 2013) (en banc)

2 (quoting Credit Suisse Sec. (USA) LLC v. Simmonds, 566 U.S. 221, 227 (2012)), aff’d and

3 remanded sub nom. United States v. Wong, 575 U.S. 402 (2015). The first element inquires

4 as to “whether the plaintiff was ‘without any fault’ in pursuing his claim.” Id. (quoting

5 Fed. Election Comm’n v. Williams, 104 F.3d 237, 240 (9th Cir. 1996)). Here, Rodriguez

6 does not explain why it was reasonable for her, based on assurances allegedly provided in

7 March and April of 2020, to refrain from taking any further action until March of 2022.

8 See FAC ¶ 17. This unexplained, near two-year wait precludes equitable tolling. See Smith

9 v. Davis, 953 F.3d 582, 601 (9th Cir. 2020) (en banc) (denying equitable tolling where a

10 habeas petitioner waited 364 days after the cessation of extraordinary circumstances to file

11 his petition).

12 3. 2022 Requests

13 Not content to rest on their laurels, Defendants also suggest the statute of limitations

14 bars claims arising from Rodriguez’s 2022 requests. This is true, per Defendants, because

15 the statute of limitations for all requests commences thirty days from the date of the earliest

16 submitted request. Mem. at 4–5 (citing Stone, 58 F.3d at 439).

17 Here, Defendants’ luck runs out. First, though one could read Stone to support

18 Defendants’ contention, the court in Stone did not consider this specific issue. Second,

19 most (if not all) courts to confront this question have allowed claims stemming from later

20 requests to proceed, even when claims associated with earlier requests are time barred.2

21 Finally, the Court sees little reason to immunize a plan administrator from its continuing

22

23

24

2 See, e.g., Brown, 868 F.3d at 128 (setting accrual date thirty days from the plaintiff’s “last request for

information” (emphasis added)); Beserra, 2020 WL 13348402, at *8 (declining to apply statute of

25 limitations despite evidence that the defendant’s failure to respond began in 2003, as it was “possible that

[the p]laintiff’s claim relie[d] on the [d]efendants’ failure to provide or denial of information within the

26 three-year limitation period” nonetheless); Cleary v. Boeing Co. Emp. Health & Welfare Benefits Plan

(Plan 503), No. 11-CV-00403-WJM-BNB, 2013 WL 3943633, at *13–16 (D. Colo. July 31, 2013)

27

(assessing merits of claims tied to later requests after dismissing claims stemming from earlier requests as

28 time-barred).

1 statutory obligation merely because it neglected that obligation in the past. The Court will

2 not, therefore, dismiss claims stemming from Rodriguez’s 2022 requests for information

3 as time barred. If Plaintiffs otherwise state a claim with respect to those requests, Plaintiffs

4 may seek statutory damages beginning thirty days from the earliest such request.

5 B. Duplicative Relief

6 Defendants next argue that Plaintiffs’ second claim should be dismissed as

7 duplicative of Plaintiffs’ first claim. Though the Court declines to adopt much of

8 Defendants’ reasoning, the Court agrees that Plaintiffs’ second claim—at least, as currently

9 pleaded—should be dismissed.

10 Plaintiffs’ first two causes of action both flow from alleged violations of 29 U.S.C.

11 § 1025(a). See FAC ¶¶ 24, 28. That statute reads, in relevant part, as follows:

12 The administrator of an individual account plan . . . shall furnish

a pension benefit statement . . . (ii) at least once each calendar

13

year to a participant or beneficiary who has his or her own

14 account under the plan but does not have the right to direct the

investment of assets in that account, and (iii) upon written

15

request to a plan beneficiary not described in clause . . . (ii).

16

17 29 U.S.C. § 1025(a)(1)(A).3

18 Plaintiffs base their first claim on Defendants’ failure to provide pension benefit

19 statements on an annual basis, FAC ¶¶ 21–26, and their second on Defendants’ failure to

20 provide those same pension benefit statements—this time, in response to Rodriguez’s

21 requests, id. ¶¶ 27–30. They derive this two-pronged approach from the two-pronged

22 remedy contained within 29 U.S.C. § 1132(c)(1). The first cause of action stems from

23 § 1132(c)(1)(A), which allows for statutory damages against administrators who “fail[] to

24 meet the requirements of . . . section 1025(a),” e.g., by failing to provide pension benefit

25

26

3 Per the FAC, the Plan provides individual accounts to each participant, but does not allow participants

27

to manage the investments in those accounts. FAC ¶ 24. Though the FAC elsewhere suggests that the

28 Plan is a “Defined Contribution Plan,” id. ¶ 6, Paragraph 24 appears to clarify that the Plan is an individual

1 statements on an annual basis. 29 U.S.C. § 1132(c)(1)(A). The second, by contrast, flows

2 from § 1132(c)(1)(B), which provides for identical statutory damages against

3 administrators who “fail[] or refuse[] to comply with a request for any information which

4 such administrator is required by this subchapter[4] to furnish to a participant or

5 beneficiary” Id. § 1132(c)(1)(B) (emphasis added). Per Plaintiffs, because § 1025(a)

6 requires Defendants to provide pension benefit statements, and Rodriguez requested those

7 statements, Defendants are liable under subsection (c)(1)(B) in addition to subsection

8 (c)(1)(A).

9 Plaintiffs’ theory begs a crucial question—is a plan administrator required, by

10 § 1025, to provide a pension benefit statement upon request? Cf. Michael v. La Jolla

11 Learning Inst., Inc., No. 17-CV-934 JLS (MDD), 2018 WL 11483057, at *4 (S.D. Cal.

12 June 21, 2018) (dismissing the plaintiff’s § 1132(c)(1)(B) claim because the regulation

13 upon which the plaintiff relied “does not expressly provide a right for a participant to

14 request information”). Plaintiffs derive their right to request, without analysis, from

15 § 1025. This derivation does not withstand scrutiny.

16 The plain text of § 1025 does not require Defendants to provide pension benefit

17 statements whenever requested. True, § 1025 creates such a requirement respecting

18 participants in defined benefit plans. See 29 U.S.C. § 1025(a)(1)(B)(ii) (requiring

19 administrators to furnish a pension benefit statement “to a participant or beneficiary of the

20 plan upon written request”); Bafford v. Admin. Comm. of Northrop Grumman Pension

21 Plan, 101 F.4th 641, 650–51 (9th Cir. 2024). But where individual account plans such as

22 Rodriguez’s are concerned, an administrator need only provide pension benefit statements

23 “upon written request to a plan beneficiary not described in clause (i) or (ii).” 29 U.S.C.

24 § 1025(a)(1)(A)(iii) (emphasis added). And, unfortunately for Rodriguez, she qualifies as

25 a clause (ii) beneficiary, i.e., someone “who has . . . her own account under the plan but

26 does not have the right to direct the investment of assets in that account.” Id.

27

28

1 § 1025(a)(1)(A)(ii); FAC ¶ 24. So, § 1025 only entitles Rodriguez to a pension benefit

2 statement once annually—not whenever she requests one.

3 Section 1025(b) reinforces this understanding. It imposes a “[l]imitation on [the]

4 number of statements” clause (a)(1)(A)(iii) and (b)(1)(B)(ii) plan participants may receive

5 upon request—“[i]n no case . . . more than [one] statement . . . in any [twelve]-month

6 period.” 29 U.S.C. § 1025(b). This limitation demonstrates that § 1025’s “upon written

7 request” subsections were not intended to provide a free-floating right to request pension

8 benefit statements, but instead to ensure that all participants receive a pension benefit

9 statement at least once each calendar year. Because § 1025(a)(1)(A)(ii) guarantees this

10 right for Rodriguez, she does not need—and therefore the statute does not grant her—the

11 ability to secure pension benefit statements upon request.

12 Plaintiffs respond only that their § 1132(c)(1)(B) claim should survive because

13 Federal Rule of Civil Procedure 8(a)(3) allows them to plead inconsistent theories in the

14 alternative. In so arguing, Plaintiffs fail to recognize the nature of their claim’s flaw. Their

15 claim does not fail because it conflicts with another claim; instead, it fails because it relies

16 on a theory belied by the relevant statutory language.

17 As § 1025 does not require plan administrators to furnish pension benefit statements

18 to participants upon request—and the FAC references no other provisions within the

19 relevant Subchapter as a source for such a requirement—the Court will dismiss Plaintiffs’

20 second cause of action for failure to state a claim under which relief may be granted.5,6

21 / / /

22

23 5 The Parties spill considerable ink discussing whether Plaintiffs’ second cause of action survives based

24 on 29 U.S.C. § 1024(b)(4). See Mem. at 7–10; Opp’n at 7–8. It is axiomatic, however, that a brief in

opposition cannot amend a complaint. Apple Inc. v. Allan & Assocs. Ltd., 445 F. Supp. 3d 42, 59 (N.D.

25 Cal. 2020). And here, the FAC relies solely on 29 U.S.C. § 1025 to support its second cause of action.

FAC ¶ 28. If Plaintiffs indeed wish to bring a cause of action based in § 1024(b)(4), they must amend

26 their pleading to incorporate that theory. Defendants may then renew any arguments for dismissal

grounded in § 1024(b)(4).

27

28

6 As the Court dismisses Plaintiffs’ second cause of action on this ground, it need not address whether

1 C. Written Authorization

2 Defendants’ final argument with respect to claim two focuses on requests made by

3 Kolodi—Rodriguez’s financial advisor. Section 1132(c)(1)(B), when articulating its

4 disclosure-upon-request requirement, refers only to the “requesting participant or

5 beneficiary.” 29 U.S.C. § 1132(c)(1)(B). So, per Defendants, a plan administrator need

6 respond only to requests made by participants or beneficiaries—not by persons, like

7 financial advisors, who happen to represent plan participants. Defendants thus suggest

8 Plaintiffs cannot state a claim with respect to Kolodi’s requests unless they allege Kolodi

9 submitted written authorization to act on Rodriguez’s behalf.

10 Defendants’ argument appears to present an issue of first impression in the Ninth

11 Circuit. Many courts analyzing a similar question, however, have coalesced around the

12 following view: plan administrators must respond to requests made by participants,

13 beneficiaries, or their attorneys, but need not answer requests by other third parties unless

14 accompanied by written authorization.7 District courts that have adopted this approach

15 dismiss complaints that fail to allege the requesting third party submitted a signed

16 authorization.8 In the Court’s view, however, this approach requires some important

17 modifications.

18

19 7 See Anderson v. Flexel, Inc., 47 F.3d 243, 249 (7th Cir. 1995) (concluding the defendant “did not have

20 to respond” to a request made by a beneficiary’s family member, but recognizing a presumption that an

attorney “has the authority to act on behalf of the person he represents”); Daniels v. Thomas & Betts Corp.,

21 263 F.3d 66, 77 (3d Cir. 2001) (recognizing that a plan administrator bears no duty to respond to a

document request submitted by a third party, but creating an exception for requests submitted by an

22 attorney “when the administrator has no reason to question the attorney’s authority”); Moothart v. Bell,

21 F.3d 1499, 1503 (10th Cir. 1994) (“An attorney . . . is entitled to request plan information on behalf of

23

the participant if the request is clear and puts the administrator on notice of the information sought.”).

24

8 See Barix Clinics of Ohio, Inc. v. Longaberger Fam. of Cos. Grp. Med. Plan, 459 F. Supp. 2d 617, 625

25 (S.D. Ohio 2005) (“[I]t would be unfair to penalize an administrator for failing to disclose plan documents

to a third party who has not informed the administrator of its status as an assignee and putative

26 beneficiary.”); Sanctuary Surgical Ctr., Inc. v. UnitedHealth Grp., Inc., No. 10-81589-CIV, 2013 WL

149356, at *11 (S.D. Fla. Jan. 14, 2013) (finding the plaintiffs “fail[ed] to state a plausible claim . . . under

27

§ 1132(c)(1)([B])” because the plaintiffs did not make a request “supported by a signed authorization from

28 the relevant patient(s)”); Outpatient Specialty Surgery Partners, Ltd. v. Unitedhealthcare Ins. Co., No.

1 Allowing plan administrators to entirely ignore document requests conflicts with the

2 purpose underlying ERISA’s disclosure requirements. In Bartling v. Fruehauf Corp., the

3 Sixth Circuit initially upheld plan administrators’ right to refuse to disclose any

4 documents—even to attorneys—absent written authorization from a participant or

5 beneficiary. 29 F.3d 1062, 1072 (6th Cir. 1994). Eleven years later, however, the Sixth

6 Circuit substantially cabined Bartling, for reasons that are worth reproducing in substantial

7 part:

8 As the Supreme Court noted in Firestone Tire & Rubber

Co. v. Bruch, 489 U.S. 101, 118 (1989) (quoting H.R.Rep. No.

9

93–533, p. 11 (1973)), “Congress’ purpose in enacting the

10 ERISA disclosure provisions” was to “ensur[e] that ‘the

individual participant knows exactly where he stands with

11

respect to the plan.’” . . .

12 In Bartling, we held that a plan administrator could not be

required under 1024(b) of ERISA to disclose pension benefit

13

information to a non-participant (even the attorney of a

14 participant) without first receiving written authorization from the

participant. 29 F.3d at 1072. We note that the factual

15

circumstances of Bartling are quite different from those

16 presented by this case, principally because the actions of the

defendant in Bartling can be described as forthright and non-

17

evasive. In Bartling, after receiving an attorney request for

18 pension benefits information on behalf of several participants,

the defendants furnished much of the information requested . . . .

19

At the same time, the defendants informed plaintiff’s counsel that

20 individual benefits computations would not be provided without

authorizations from the plan participants. . . . Bartling affirmed

21

the right of the plan administrator to seek a written authorization

22 whenever any non-participant, even a participant’s attorney,

requested benefits information.

23

In contrast to the behavior of the defendant in Bartling,

24 Glidden’s handling of the request by Murphy’s attorney . . . can

only be described as entirely inappropriate. Glidden did not

25

inform Murphy’s attorney that the information would not be

26 provided without a signed authorization; rather, it simply ignored

the request for almost four months.

27

Pension plan administrators who treat our decision in

28 Bartling as a license to simply disregard a written request for

1 ptheants icoans eb eannedfi tsm iinsfuonrdmeartsitoann d. . t.h beoirt ho mbliisgcaotniosntrsu eu tnhdee hr oEldRinIgS Aof.

2

Again, ERISA disclosure requirements exist to help ensure that

3 participants have access to information about their pension plans.

As the Third Circuit has cogently observed, “the objective of [the

4

ERISA disclosure requirements] would be ill served . . . by

5 permitting administrators to refuse to respond with no indication

that authori[zation from the participant] is even an issue.”

6

Daniels v. Thomas & Betts Corp., 263 F.3d 66, 77 (3rd Cir.

7 2001).

What Bartling says is that a plan administrator may require

8

written authorization from a plan participant before satisfying a

9 non-participant’s request for benefits information. Not

inconsistent with that rule, we hold that a plan administrator is

10

not entitled to ignore a request for pension benefits information

11 made by an attorney on behalf of a participant . . . . Instead, a

plan administrator must either provide the requested information

12

directly to the plan beneficiary [or] inform the attorney that the

13 information will be released upon the receipt of an authorization

signed by the plan participant.

14

15 Minadeo v. ICI Paints, 398 F.3d 751, 757–58 (6th Cir. 2005) (footnotes omitted and

16 emphasis added). The Court finds Minadeo persuasive and extends it to requests made by

17 a financial advisor.

18 To be sure, Minadeo involved a request made by an attorney. Id. But Minadeo’s

19 logic applies with equal force to requests made by non-attorney third parties—particularly,

20 those with a plausible relationship to a plan participant.9 See id. n.4 (“[T]he purposes of

21 ERISA are not served when a plan administrator simply ignores a non-participant’s request

22 for information, without asking for an authorization to be provided.” (emphasis added)).

23

24

9 The Court is not inclined to engage in attorney exceptionalism when defining an ERISA plan

25 administrator’s disclosure obligations. True, attorneys (1) must be admitted by state bars, (2) are bound

to comply with ethical codes, and (3) serve as their clients’ fiduciaries. But many financial advisors are

26 subject to similar commitments. See, e.g., SEC v. Duncan, No. 3:19-CV-11735-KAR, 2021 WL 4197386,

at *1 (D. Mass. Sept. 15, 2021) (“[The d]efendant had fiduciary obligations to his clients that were

27

mandated by the SEC and by Ausdal’s Compliance Policies & Procedures Manual and Code of Ethics.”).

28 If plan administrators must respond to requests from the former, they should also respond to requests from

1 There is a world of difference between empowering plan administrators to deny potentially

2 suspect requests and granting plan administrators license to entirely ignore potentially

3 meritorious requests. Though Defendants seek a holding that would allow the latter, the

4 Court will not acquiesce. Instead, the Court holds as follows: plan administrators need not

5 provide documents absent written authorization. But if they completely ignore a request

6 for information made by a financial advisor on a participant’s behalf, they risk § 1132(c)

7 statutory damages.

8 The Court is not concerned this holding will subject plan administrators to a flood

9 of statutory damages. This is true for one simple reason—statutory damages under

10 29 U.S.C. § 1132(c)(1)(B) may be imposed only at the discretion of the presiding court.

11 See, e.g., Brooks v. Metrica, Inc., 1 F. Supp. 2d 559, 568 (E.D. Va. 1998) (“Once it is

12 determined that a defendant has violated the strictures of ERISA, the amount of the

13 statutory penalty to be imposed, if any, is left to the discretion of the court.” (emphasis

14 added)); Paris v. F. Korbel & Bros., 751 F. Supp. 834, 840 (N.D. Cal. 1990) (noting courts

15 may reduce statutory damages based on “mitigating factor[s]” such as “good faith” and

16 “lack of actual harm”). If indeed a plan administrator declines to answer a third-party’s

17 request in good faith, the reviewing court can take that into account.

18 With the applicable standard determined, the Court turns to Plaintiffs’ allegations.

19 The FAC states that Rodriguez authorized Kolodi to “request account statements

20 from . . . Defendants,” that Kolodi “made numerous requests and demands for information

21 from . . . Defendants,” and that “no information was ever provided.” FAC ¶ 18. Plaintiffs

22 nowhere allege (1) that Kolodi submitted to Defendants a written authorization to act on

23 Rodriguez’s behalf nor (2) that Defendants ignored Kolodi’s requests. Absent allegations

24 such as the above, Plaintiffs have not stated a claim under 29 U.S.C. § 1132(c)(1)(B) with

25 respect to Kolodi’s requests.

26 D. Individual Defendants

27 “Under 29 U.S.C. § 1132(c), only the plan ‘administrator’ can be held liable for

28 failing to comply with . . . reporting and disclosure requirements.” Cline v. Indus. Maint.

1 Eng’g & Contracting Co., 200 F.3d 1223, 1234 (9th Cir. 2000) (citing Moran v. Aetna Life

2 Ins. Co., 872 F.2d 296, 299 (9th Cir. 1989)). Relying on Cline, Defendants contend the

3 only proper defendant here is the Committee—not its members. Defendants thus ask the

4 Court to dismiss Hester and Hester-Wake from the action.

5 Plaintiffs respond that because Hester and Hester-Wake “have been the point of

6 contact for Plaintiffs to answer questions regarding the Plan and present themselves as

7 being in control of the Plan’s financial affairs,” they believe Hester and Hester-Wake are

8 “the actual or de facto Plan administrator[s].” Opp’n at 10. Plaintiffs, however, cite no

9 authority in support of their position. Id.

10 Hester and Hester-Wake do not qualify as plan administrators under ERISA. A

11 plan’s “administrator” is, at first blush, “the person specifically so designated by the terms

12 of the instrument under which the plan is operated.” Moran, 872 F.2d at 299 (quoting 29

13 U.S.C. § 1002(16)(A)). Other persons can qualify as an administrator only if (1) “an

14 administrator is not so designated” and/or (2) “a plan sponsor cannot be identified.” Id.

15 (quoting 29 U.S.C. § 1002(16)(A)). The Court, moreover, must rigidly adhere to this

16 statutory definition; the Ninth Circuit limits administrator liability “to the targets expressly

17 identified by Congress in Section 1002(16).” Id. Because § 1002(16)(A) contemplates

18 that a plan will have only one administrator—and here, Plaintiffs allege that the Committee

19 is said administrator, FAC ¶ 6—Hester and Hester-Wake do not qualify as plan

20 administrators. Therefore, Plaintiffs cannot hold Hester or Hester-Wake liable under

21 § 1132(c).

22 Plaintiffs’ “de facto administrator” theory cannot salvage their case. Though the

23 First and Eleventh Circuits recognize such a theory, see Law v. Ernst & Young, 956 F.2d

24 364, 374 (1st Cir. 1992); Hamilton v. Allen-Bradley Co., 244 F.3d 819, 824 (11th Cir.

25 2001), those cases cannot be reconciled with Moran. See Rodriguez v. Reliance Standard

26 Ins. Co., No. C 03-04189 CRB, 2004 WL 2002438, at *2–3 (N.D. Cal. Sept. 8, 2004)

27 (distinguishing Law and Hamilton and noting their holdings are inconsistent with both

28 Moran and the approaches of the Sixth, Fourth, and D.C. Circuits); Talbot v. Reliance

1 Standard Life Ins. Co., 790 F. App’x 129, 130 (9th Cir. 2020) (“[T]his court has long

2 rejected Talbot’s theory that RSLIC can be deemed a de facto administrator.” (citing Sgro

3 v. Danone Waters of N. Am., Inc., 532 F.3d 940, 945 (9th Cir. 2008))). So, it matters not

4 whether Hester or Hester-Wake engaged in conduct one might expect from a plan

5 administrator.

6 This conclusion, however, does not justify dismissing Hester and Hester-Wake from

7 the action. At risk of spoiling what lies ahead, Plaintiffs’ third cause of action relies on

8 29 U.S.C. § 1132(a)(3), the plain text of which does not limit liability to administrators.

9 As Defendants have not argued that Hester and Hester-Wake are improper defendants

10 under this separate provision, Hester and Hester-Wake will remain in the action.

11 II. Improper Denial of Benefits (Claim III)

12 In their third claim, Plaintiffs contend that by failing to respond to Rodriguez’s loan

13 request, Defendants violated two statutory provisions. Plaintiffs first note that 29 U.S.C.

14 § 1133(1) requires plans to “provide adequate notice in writing to any participant or

15 beneficiary whose claim for benefits under the plan has been denied.” Second, Plaintiffs

16 contend Defendants’ radio silence violated 29 U.S.C. § 1133(2), which mandates that plans

17 give participants a reasonable opportunity to appeal benefits denials. Defendants object to

18 this cause of action on three grounds, which the Court will address seriatim.

19 A. Independent Cause of Action

20 Defendants first argue that because 29 U.S.C. § 1133 “does not act as a civil

21 enforcement section,” “Plaintiffs’ third cause of action is improperly brought.” Mem. at

22 10. Defendants are correct that § 1133 does not contain a private right of action. See

23 Ingersoll-Rand Co. v. McClendon, 498 U.S. 133, 144 (1990) (emphasizing 29 U.S.C.

24 § 1132(a) constitutes “the exclusive remedy for rights guaranteed under ERISA.”).

25 Defendants fail to recognize, however, that 29 U.S.C. § 1132(a)(3) allows a plan

26 participant or beneficiary to “enjoin any act or practice which violates any provision of

27 [Subchapter I],” to “obtain other appropriate equitable relief” to “redress such violations,”

28 or “to enforce any provisions of [Subchapter I].” As 29 U.S.C. § 1133 falls within

1 Subchapter I, Plaintiffs may sue to require Defendants to comply with § 1133’s

2 requirements. See Downtown L.A. Ambulatory Surgical Ctr., LLC v. Conn. Gen. Life Ins.

3 Co., No. CV183592DMGAGRX, 2019 WL 2902493, at *4 (C.D. Cal. Mar. 29, 2019).

4 Defendants’ first argument thus does not justify dismissal.

5 B. Administrative Exhaustion

6 Defendants’ next contention can be dispensed with easily. Defendants argue that

7 “Rodriguez has . . . failed to exhaust all available administrative remedies under the Plan

8 prior to bringing the third cause of action.” Mem. at 11. But where a plaintiff files “a

9 timely claim under 29 U.S.C. § 1132(a)(3) to enforce the notification and review

10 requirements of § 1133,” “the exhaustion of internal dispute procedures [is]

11 not . . . required.” Chuck v. Hewlett Packard Co., 455 F.3d 1026, 1035 (9th Cir. 2006).

12 Plaintiffs’ third cause of action belongs in federal court.

13 C. Is a Loan a “Benefit?”

14 Finally, Defendants argue that a loan request is not a claim for benefits under ERISA.

15 Per Defendants, Rodriguez can only seek “unpaid or owing employee or employer

16 ‘contributions’ []or ‘assets’,” not loans. Mem. at 10–11.

17 Defendants’ argument is remarkably underbaked. They (1) cite no statutory or

18 regulatory provision adopting the narrow definition of “benefits” that they propose and (2)

19 present no precedent that directly supports their understanding.10 Though Defendants rely

20 on Leister v. Dovetail, Inc., that case found only that with respect to a specific 401(k) plan,

21 the plaintiff’s “benefits” were “the assets that would have been in her 401(k) account.”

22 546 F.3d 875, 881 (7th Cir. 2008). It nowhere held that ERISA’s definition of “benefits”

23 is limited solely to assets or contributions.

24 Instead, both the plain meaning of the term “benefit” and ERISA’s statutory

25 provisions suggest that loans can qualify as benefits if the relevant plan so provides. First,

26 ERISA expressly allows covered plans to make loans to participants or beneficiaries.

27

28

1 29 U.S.C. § 1108(b)(1). Second, ERISA’s enforcement provision, when discussing

2 “benefits,” refers to “the terms of [the participant’s] plan.” 29 U.S.C. § 1132(a)(1)(B).

3 Finally, Merriam-Webster defines “benefit,” in relevant part, as “financial help in time of

4 sickness, old age, or unemployment,” “a payment or service provided for under an annuity,

5 pension plan, or insurance policy,” or “a service (such as health insurance) or right (as to

6 take vacation time) provided by an employer in addition to wages or salary.” Benefit,

7 Merriam-Webster, https://www.merriam-webster.com/dictionary/benefit (last visited July

8 11, 2024) (emphasis added). It follows that a “benefit,” where ERISA is concerned, is a

9 payment or service (such as a loan) to which plan participants are entitled based on their

10 plan’s terms.

11 That leaves but one question: does the Plan entitle its participants to loans?

12 Defendants suggest it does not. At this stage, however, it is not Defendants’ suggestions

13 that matter, but instead the FAC’s allegations. And the FAC could not be more clear:

14 “Pursuant to the terms of the Plan, loans are available to Participants. The Plan sets forth

15 the procedure for claiming such benefit, which includes submitting a written request for

16 the loan.” FAC ¶ 34. Plaintiffs have thus plausibly alleged that Defendants violated 29

17 U.S.C. § 1133 by failing to respond to Rodriguez’s loan application.

18 CONCLUSION

19 For the foregoing reasons, the Court GRANTS IN PART AND DENIES IN PART

20 Defendants’ Motion to Dismiss (ECF No. 21). The Court DISMISSES Plaintiffs’ second

21 cause of action for failure to state a claim. Defendants’ Motion is otherwise DENIED.

22 If Plaintiffs believe that they can, consistent with this Order, supplement their second

23 cause of action such that it states a claim, Plaintiffs MAY FILE an amended complaint

24 within fourteen (14) days of the date of this Order.

25 / / /

26 / / /

27 / / /

28 / / /

1 If Plaintiffs so file, Defendants SHALL RESPOND within the time set by Federal

2 || Rule of Civil Procedure 15. If Plaintiffs elect not to file an amended complaint, however,

3 || Defendants’ answer is due fourteen (14) days from the expiration of Plaintiffs’ deadline.

4 IT IS SO ORDERED.

5 ||Dated: July 17, 2024 paca Le moe aitid-

6 on. Janis L. Sammartino

United States District Judge

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

This is a copy of a public record, reproduced as it was published. It is not legal advice, and it may not be the version a court would rely on. Check the official source before you cite it.

A word about cookies

We need a few to keep you signed in and the library working. The rest help us see which pages people use and where they get stuck. They stay off unless you say yes.