The Illinois Wage Payment and Collection Act: Some Basics

time clockThere seems to be an almost palpable out-of-sight, out-of-mind dynamic at play when an employee is either fired or quits.  This often results in the employer not compensating the departed employee for pre-departure/firing services. This post attempts to provide some basics on the Illinois Wage Payment and Collection Act, 820 ILCS 115/1 et seq. (the Wage Payment Act), a powerful tool for former employees who want to get paid.  For a more detailed treatment of the Wage Payment Act in the context of  departing corporate executives and managerial employees, please see the Novack and Macey firm’s excellent article at:

The Wage Payment Act requires every employer to pay full and “final compensation” to separated employees no later than the next regularly scheduled payday. 820 ILCS 115/5. “Final compensation” broadly includes wages, salaries, earned commissions and bonuses and the monetary equivalent of earned but unused vacation and any other compensation owed pursuant to an employment contract or agreement between the 2 parties. 820 ILCS 115/2.

To establish a Wage Payment Act claim, a plaintiff must show (1) that the defendant was an “employer” under the Act; (2) the parties entered into an “employment contract or agreement”; and (3) the plaintiff was due “final compensation”. Catania v. Local 4250/5050 of the Communications Workers of America, 359 Ill.App.3d 718 (1st Dist 2005).

The Wage Payment Act defines “employer” and “employee” broadly.  820 ILCS 115/2.  “Employer” includes any person or business entity, including employment placement agencies.  “Employee” means an individual “permitted to work by an employer in an occupation”.  Id.  Caselaw extends the Act’s coverage to executives and corporate management personnel.

 Independent contractors are generally not covered by the Wage Payment Act.  820 ILCS 115/2.  The Act specifically states that “employee” does not include an individual: (1) who is free from employer direction and control; (2) who physically works outside the confines of the employer’s office location(s) or performs work outside the usual course of employer’s business; and (3) who is in an independently established trade, occupation, profession or business.  Id. 

In Illinois, an independent contractor is defined by the level of control over the manner of work. Horwitz v. Holabird & Root, 212 Ill.2d 1, 11 (2004); Petrovich v. Share Health Plan of Illinois, Inc., 188 Ill.2d 17, 31 (1999)(independent contractor factors).

Both State and Federal Illinois cases have held that an “employment agreement” under the Wage Payment Act is broader than a formal contract.  Practically speaking, this means the contract or agreement being sued upon doesn’t have to be in writing or even have valid consideration: all that’s required is “mutual assent” between the parties.  See Landers-Scelfo v. Corporate Office Sys. Inc., 356 Ill.App.3d 1060, 1067 (2nd Dist. 2005); Wharton v. Comcast, N.D.Ill., 12 C 1157 (December 6, 2012).

In Wharton, a class action filed by Comcast employees, the Northern District denied Comcast’s 12(b)(6) motion to dismiss plaintiffs’ Wage Payment Act claims.  The plaintiffs alleged that Comcast failed to pay overtime and for pre-shift and post-shift work as required by Federal law and Comcast’s employee handbook.  The Court held that even though Comcast’s employee handbook had multiple disclaimers (to paraphrase: “this is not a contract”) and gave Comcast the unilateral right to discontinue or change the handbook at its pleasure, the plaintiffs still pled evidence of “mutual assent” to the handbook’s terms.  Wharton, p. 8.

As a consequence, the Northern District held that Comcast’s employee handbook – despite its disclaimers – vested the plaintiffs with enforceable Wage Payment Act rights (at least enough to survive a motion to dismiss).  Id.

Other key Wage Payment Act provisions include (1) corporate officers or agents who “knowingly permit” a violation of the Act, are subject to personal liability (820 ILCS 115/13); (2) employee damages include unpaid compensation plus 2% of unpaid amount per month and attorneys’ fees.  820 ILCS 115/14; and (3) the employee can – instead of filing suit – lodge a clam with the Illinois Dept. of Labor.  820 ILCS 115/11.  In the latter scenario, the claimant must file within one year after the wages or final compensation are due.  Id.  This does not preclude the employee from later pursuing a civil suit in the Circuit Court in the County where the Act violation occurred.

Other than the 1 year reference in Section 11 for asserting a Dept. of Labor Claim, the Wage Payment Act is silent on a limitations period.  Code Section 13-206 provides for a 10 year limitations period for claims based on the Act.  735 ILCS 5/13-206.


The Wage Payment Act is a powerful enforcement tool for departed employees who are owed money by their erstwhile employers.  The Act broadly applies to all types of compensation agreements and provides for recovery of the employee’s attorneys’ fees.  Commercial litigators should have a working knowledge of the Act’s contours, exceptions and key terms.

When Private Facebook Posts Come Back to Haunt You

To paraphrase that post-“Black Album” Metallica song (and a pretty tired proverb at that) – be careful what you wish for ’cause you just might get it.  I came across this gem recently courtesy of Eric Meyer’s (of Dilworth Paxson, LLP) informative and humorous employment blog:

The National Labor Relations Board (NLRB) recently issued an Advice Memorandum (see link below) recommending dismissal of an employee’s claim that her employer violated the National Labor Relations Act’s (NLRA) protected “concerted activity” sections when the employer fired the employee for making disparaging comments about the employer on Facebook.

The employee, who worked for Skinsmart – a dermatology clinic – was on a private Facebook “group message” with several former and current Skinsmar employees.  During the course of the exchange, the employee said, among other things, that a supervisor should “back the freak off”, the employer is “full of shit” and (the killer) “FIRE ME…..Make my day.”  The next day, one of the employees who participated in the Facebook exchange, showed the comments to the employer (with friends like these….).  The employer wasn’t amused and summarily fired the Facebooking (now former) employee.  (Somewhere Monsieur Eastwood is smiling.)  The employee, apparently having a change of heart, then lodged an unfair labor practice charge with the NLRB.

In recommending dismissal of the employee’s claim, the NLRB found that the employee’s inflammatory comments were akin to “griping” and were not protected group activity.  The NLRA specifically protects employees’ rights to organize and engage in concerted activity – so long as the activity involves shared concerns about working conditions or where the activity takes place in the context of preparing for group action or bringing group complaints to management’s attention.  Meyers Industries, 281 NLRB 882 (1986), NLRA §§ 7, 8(a)(1).  Here, the NLRB ruled that the employee’s request that her employer “fire her” and “make my day” was nothing more than unprotected individual griping and simply “reflected [the employee’s] personal contempt for her [employer].”  See Advice Memorandum, p. 3.

The take-away: First – be careful what you post on Facebook: you never know who is watching or who may “share” your impulsive (or not) posts; Second – if you are going to participate in a group message with current and/or former employees, your comments will only be protected if they truly involve working conditions or truly group complaints to be expressed to management; and Third – if you’re going to trash your employer, do it off-line.


Facebooking at Work: A Federal Offense? (With ‘Aarons Law’ Update)

Can surfing the Net on company time get you fired?  Perhaps.  Can it subject you to Federal criminal and civil penalties?  Not yet.  At least not in the  Tampa, Florida area.  Wendy Lee v. PMSI, 2011 WL 1742028 (M.D.Fla. 2011) illustrates a creative attempt to expand the reach of the Computer Fraud and Abuse Act (CFAA)(which, incidentally, will be the subject of some future posts).  The CFAA, codified at 18 U.S.C. s. 1030, is a criminal statute with a civil component. It provides a private civil cause of action for anyone who sustains damage or loss as a result of an unauthorized user hacking into a computer system who then destroys, erases or transfers computer data.  It also prohibits authorized users from accessing protected information and from exceeding the limits of their authorization.  In this latter context, the CFAA is typically used by an employer when a rogue employee or “insider” accesses private employer computer data and sends the data to a competitor.

In PMSI, the Plaintiff filed a Federal pregnancy discrimination suit against her employer.  The employer fired back with a counterclaim based on the CFAA – saying that the Plaintiff spent her workdays surfing the Internet and playing on Facebook.  So egregious was the Plaintiff’s personal computer use, that the employer asserted a CFAA violation claiming the Plaintiff violated her employer’s published computer/Internet use policy.

The Court dismissed the CFAA count and said that while Facebooking at work may be a fireable offense; it does not subject one to Federal criminal or civil liability.  The court gave a narrow reading to the CFAA and held that the statute did not apply to a private employee’s violation of an employer’s internet policy.  Otherwise, the court said, every employee across the land who used a company computer to send and receive personal e-mails or who surfed the Net for non-work reasons could potentially be subject to Federal liability.

So, for now, Tampa area office workers can safely surf the net on company time without being subject to CFAA liability.   Whether the same workers can be fired for violating an employer computer policy, is an issue for another day and perhaps another post.

Update (7.15.13):  Recently, some proposed changes to CFAA were introduced by Zoe Lofgren and Ron Wyden, democratic congressman and senator from California and Oregon, respectively.  These changes, known as “Aarons” law (named for the late internet activist Aaron Schwartz), are designed to narrow the reach of the CFAA so that the statute is only used to prosecute outside hackers, rather than criminalize every-day violations of private employer computer policies or Internet terms of use.  Some helpful links follow.