05.07.2014 Views

Litigating California Wage & Hour and Labor Code Class Actions

Litigating California Wage & Hour and Labor Code Class Actions

Litigating California Wage & Hour and Labor Code Class Actions

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Recent court decisions have begun to flesh out the meaning of the phrase “knowing <strong>and</strong> intentional”<br />

in the context of Section 226. These cases, however, do not provide clear guidance as to the lower<br />

threshold for the “knowing <strong>and</strong> intentional” st<strong>and</strong>ard, because the defendants in these cases were<br />

alleged to have been aware that their wage statements were not in compliance <strong>and</strong> to have done<br />

nothing to fix them.<br />

Although recent developments have further clarified the definition of “injury,” we expect<br />

interpretations of Section 226 to still vary from one judge to another, especially with respect to the<br />

definition of “knowing <strong>and</strong> intentional.”<br />

X. <strong>California</strong> Minimum <strong>Wage</strong> Claims<br />

In Armenta v. Osmose, Inc., 223 the Second District Court of Appeal held that employees who<br />

alleged that their employer had failed to pay them for certain hours they worked off-the-clock had<br />

violated the state minimum wage laws with respect to every hour they worked but were not paid.<br />

The employer defended the claim with the argument that the employees’ average hourly pay for the<br />

workweek was greater than the minimum wage, which defeated any claim for minimum wage under<br />

the federal “averaging method” for determining minimum wages. 224 The Armenta court, however,<br />

rejected the averaging method <strong>and</strong> instead adopted the position set forth in a DLSE Opinion Letter<br />

that <strong>California</strong> requires that the minimum wage be paid for each <strong>and</strong> every hour worked.<br />

Accordingly, regardless of the total compensation an employee earns during a week, or even during<br />

a single day, if there are hours the employee has worked for which the employee was paid less<br />

than the minimum wage, then the employer has violated <strong>Labor</strong> <strong>Code</strong> Section 1194 by failing, for the<br />

hours in question, to pay minimum wage. 225<br />

Interestingly, a federal district court in <strong>California</strong> previously had expressly rejected the DLSE’s<br />

position, holding that the FLSA’s averaging method applied to claims under <strong>California</strong> minimum<br />

wage law as well. 226 The Armenta court rejected the federal court’s conclusion, reasoning that<br />

<strong>California</strong> intended its minimum wage law to be more protective than the FLSA’s minimum wage<br />

law, <strong>and</strong> that part of this greater protection is a requirement to pay minimum wage for “all hours<br />

223<br />

224<br />

225<br />

226<br />

intentional); Mutec v. Huntington Mem’l Hosp., LASC Case No. BC 288727 (LA Superior Court, Mar. 10, 2006) (Hon.<br />

Tricia Ann Bigelow) (granting summary adjudication against claim for penalties where employer did not know that its<br />

pay stubs violated Section 226(a)). But see Heritage Residential Care, Inc. v Division of <strong>Labor</strong> St<strong>and</strong>ards Enforcement,<br />

192 Cal. App. 4th 75, 88 (2011) (defendant’s “good faith mistake of law” that employees who lacked Social Security<br />

numbers were not required to be provided with wage statements was not an “inadvertent” mistake, such as a clerical<br />

error would be).<br />

135 Cal. App. 4th 314 (2006).<br />

Armenta, 135 Cal. App. 4th at 319.<br />

Id. at 324-25.<br />

Medrano v. D’Arrigo Bros. Co., 336 F. Supp. 2d 1053 (N.D. Cal. 2004).<br />

Seyfarth Shaw LLP | www.seyfarth.com <strong>Litigating</strong> <strong>California</strong> <strong>Wage</strong> & <strong>Hour</strong> <strong>Class</strong> <strong>Actions</strong> (12th Edition) 53

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!