Payroll Administrator
LRS · Rosemont, IL · 1 mo ago
Human Resources$32.69–$36.06/hrFull-time
We need to output HTML fragment with sections: headings using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to extract content.
The posting includes:
- Intro about LRS (company description) maybe "About the role"? Actually "About the role" could be the description of the role. The intro about LRS could be considered "About the role"? Might be better as "About the role" includes description of company and role purpose.
- Responsibilities: list of duties: preparing and processing weekly payrolls, employee setup and terminations, maintenance of employee records, support Payroll Manager, respond to inquiries, process weekly payroll for 2,200+ employees, review time entries, process LOA payments, audit payroll data, calculate and report monthly union contributions, maintain knowledge of CBAs, monitor payroll operations for tax and union compliance, respond to wage garnishments etc, assist with other payroll related projects.
- Knowledge And Skill Requirements: list of skills/knowledge: understanding of federal, state and local wage and hour laws, FLSA, tax regulations, garnishment rules; knowledge of benefits impact; awareness of laws affecting compensation classifications; ADP Lyric Time & Attendance experience preferred; exposure to union payroll environment a plus; proficient in MS Word and Excel (Vlookup & pivot tables); detail-oriented; ability to adapt; strong problem solving, organizational, communication, interpersonal skills; ability to work independently and as part of team; high level of integrity; confidentiality.
- Education & Experience: Bachelor’s degree preferred, or equivalent combination; Minimum of 3 years of payroll processing experience using major payroll software such as ADP, Paylocity, Paycom, Paycor, Workday, or Paychex.
- Physical Demands & Work Environment: prolonged sitting, use hands, talk/hear, occasionally stand/walk, occasionally lift up to 30 pounds, ability to read data, typical office environment, moderate noise, climate-controlled, potential for remote/hybrid, may lift up to 30 pounds, travel limited.
- Pay: "$32.69-36.06" (likely hourly rate). So we have Pay section.
- Schedule: Not explicitly mentioned. No schedule info. So we should not include Schedule section.
- Benefits: Not mentioned. No benefits. So skip Benefits.
- Qualifications: Could combine Education & Experience and maybe Knowledge And Skill Requirements? But we have separate sections: Qualifications could be Education & Experience. Requirements could be Knowledge And Skill Requirements. Or we could treat Knowledge And Skill Requirements as Skills. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping.
Typically:
- About the role: company overview and role purpose.
- Responsibilities: list of duties.
- Requirements: maybe "Knowledge And Skill Requirements" (skills needed).
- Qualifications: Education & Experience.
- Skills: maybe overlapping but we could put specific technical skills like ADP Lyric, MS Excel, etc. But we already have them in Requirements. To avoid duplication, we could put Requirements as "Knowledge And Skill Requirements" and Qualifications as "Education & Experience". Skills maybe not needed if we already covered. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include sections we have content for: About the role, Responsibilities, Requirements, Qualifications, Pay. Possibly Skills if we have distinct content not already covered. But we could also merge Skills into Requirements. Safer to include Requirements and Qualifications, and maybe Skills if we have distinct content like "ADP Lyric Time & Attendance experience is preferred", "Exposure to union payroll environment a plus", "Must be proficient in Microsoft Word and Excel (Vlookup & pivot tables)". Those are skills. Could put them under Skills. Then Requirements could be more about understanding laws etc. But the posting lumps them together under "Knowledge And Skill Requirements". Might be better to treat that as Requirements (knowledge) and Skills (technical). However we need to avoid duplication.
Let's parse:
Knowledge And Requirement list includes:
- Understanding of federal, state and local wage and hour laws, including FLSA, tax regulations and garnishment rules.
- Knowledge of how benefits such as health insurance, 401K, PTO impact payroll.
- Awareness of laws affecting employee compensation and classifications such as exempt versus non-exempt, independent contractors, etc.
- ADP Lyric Time & Attendance experience is preferred.
- Exposure to union payroll environment a plus.
- Must be proficient in Microsoft Word and Excel (Vlookup & pivot tables).
- Detailed-oriented with ability to perform with a high degree of accuracy.
- Quickly and easily adapt to change and shifting priories with enthusiasm.
- Strong problem solving, organizational, communication, and interpersonal skills required.
- Ability to work independently and as part of a team in a deadline-driven and fast paced environment.
- High level of integrity with the ability to maintain complete confidentiality.
That's a mix of knowledge and skills. Could be considered Requirements.
Education & Experience:
- Bachelor’s degree preferred, or equivalent combination of education and relevant experience.
- Minimum of 3 years of payroll processing experience using a major, payroll software such as ADP, Paylocity, Paycom, Paycor, Workday, or Paychex.
That's Qualifications.
Thus we can have:
- About the role: company intro + role purpose (first paragraph).
- Responsibilities: bullet list of duties.
- Requirements: knowledge and skill requirements (the list).
- Qualifications: education & experience.
- Pay: salary range.
We'll not include Benefits, Schedule.
Now we need to format as HTML fragment: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to extract content.
The posting includes:
- Intro about LRS (company description) maybe "About the role"? Actually "About the role" could be the description of the role. The intro about LRS could be considered "About the role"? Might be better as "About the role" includes description of company and role purpose.
- Responsibilities: list of duties: preparing and processing weekly payrolls, employee setup and terminations, maintenance of employee records, support Payroll Manager, respond to inquiries, process weekly payroll for 2,200+ employees, review time entries, process LOA payments, audit payroll data, calculate and report monthly union contributions, maintain knowledge of CBAs, monitor payroll operations for tax and union compliance, respond to wage garnishments etc, assist with other payroll related projects.
- Knowledge And Skill Requirements: list of skills/knowledge: understanding of federal, state and local wage and hour laws, FLSA, tax regulations, garnishment rules; knowledge of benefits impact; awareness of laws affecting compensation classifications; ADP Lyric Time & Attendance experience preferred; exposure to union payroll environment a plus; proficient in MS Word and Excel (Vlookup & pivot tables); detail-oriented; ability to adapt; strong problem solving, organizational, communication, interpersonal skills; ability to work independently and as part of team; high level of integrity; confidentiality.
- Education & Experience: Bachelor’s degree preferred, or equivalent combination; Minimum of 3 years of payroll processing experience using major payroll software such as ADP, Paylocity, Paycom, Paycor, Workday, or Paychex.
- Physical Demands & Work Environment: prolonged sitting, use hands, talk/hear, occasionally stand/walk, occasionally lift up to 30 pounds, ability to read data, typical office environment, moderate noise, climate-controlled, potential for remote/hybrid, may lift up to 30 pounds, travel limited.
- Pay: "$32.69-36.06" (likely hourly rate). So we have Pay section.
- Schedule: Not explicitly mentioned. No schedule info. So we should not include Schedule section.
- Benefits: Not mentioned. No benefits. So skip Benefits.
- Qualifications: Could combine Education & Experience and maybe Knowledge And Skill Requirements? But we have separate sections: Qualifications could be Education & Experience. Requirements could be Knowledge And Skill Requirements. Or we could treat Knowledge And Skill Requirements as Skills. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide mapping.
Typically:
- About the role: company overview and role purpose.
- Responsibilities: list of duties.
- Requirements: maybe "Knowledge And Skill Requirements" (skills needed).
- Qualifications: Education & Experience.
- Skills: maybe overlapping but we could put specific technical skills like ADP Lyric, MS Excel, etc. But we already have them in Requirements. To avoid duplication, we could put Requirements as "Knowledge And Skill Requirements" and Qualifications as "Education & Experience". Skills maybe not needed if we already covered. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can include sections we have content for: About the role, Responsibilities, Requirements, Qualifications, Pay. Possibly Skills if we have distinct content not already covered. But we could also merge Skills into Requirements. Safer to include Requirements and Qualifications, and maybe Skills if we have distinct content like "ADP Lyric Time & Attendance experience is preferred", "Exposure to union payroll environment a plus", "Must be proficient in Microsoft Word and Excel (Vlookup & pivot tables)". Those are skills. Could put them under Skills. Then Requirements could be more about understanding laws etc. But the posting lumps them together under "Knowledge And Skill Requirements". Might be better to treat that as Requirements (knowledge) and Skills (technical). However we need to avoid duplication.
Let's parse:
Knowledge And Requirement list includes:
- Understanding of federal, state and local wage and hour laws, including FLSA, tax regulations and garnishment rules.
- Knowledge of how benefits such as health insurance, 401K, PTO impact payroll.
- Awareness of laws affecting employee compensation and classifications such as exempt versus non-exempt, independent contractors, etc.
- ADP Lyric Time & Attendance experience is preferred.
- Exposure to union payroll environment a plus.
- Must be proficient in Microsoft Word and Excel (Vlookup & pivot tables).
- Detailed-oriented with ability to perform with a high degree of accuracy.
- Quickly and easily adapt to change and shifting priories with enthusiasm.
- Strong problem solving, organizational, communication, and interpersonal skills required.
- Ability to work independently and as part of a team in a deadline-driven and fast paced environment.
- High level of integrity with the ability to maintain complete confidentiality.
That's a mix of knowledge and skills. Could be considered Requirements.
Education & Experience:
- Bachelor’s degree preferred, or equivalent combination of education and relevant experience.
- Minimum of 3 years of payroll processing experience using a major, payroll software such as ADP, Paylocity, Paycom, Paycor, Workday, or Paychex.
That's Qualifications.
Thus we can have:
- About the role: company intro + role purpose (first paragraph).
- Responsibilities: bullet list of duties.
- Requirements: knowledge and skill requirements (the list).
- Qualifications: education & experience.
- Pay: salary range.
We'll not include Benefits, Schedule.
Now we need to format as HTML fragment: use for each section heading, then content:
for prose,
- for lists.
We must not repeat job title as heading. The job title is "Payroll Administrator". Not to be used as heading.
We must not include Job ID etc.
We must remove boilerplate like EEO etc. Not present.
We need to preserve all substantive information. Ensure we don't lose any details.
Let's extract the About the role content: The first paragraph(s) before responsibilities: "LRS is the industry leader in providing innovative and environmentally responsibly waste and recycling solutions. Our team delivers exceptional service and value through relentless commitment to customer satisfaction and preservation of the environment. Through our safe and innovative approach to waste diversion, LRS thrives on the passion and innovation of our employees to preserve and sustain the beauty of the towns, neighborhoods and communities that we serve. We are excited to hire candidates that align with our Vision and Values: To become the safest, most innovative waste recycler in the world by redefining the way the world views waste. Live Safety Serve With PassionInnovate RelentlesslyEngage With IntegrityBuild CommunityBe Accountable, The Payroll Administrator is responsible for preparing and processing weekly payrolls accurately and on time."
Wait that last sentence seems to start responsibilities. Actually the responsibilities start after that sentence. The "The Payroll Administrator is responsible for preparing and processing weekly payrolls accurately and on time." is part of responsibilities. So About the role should be everything before that sentence: up to "Be Accountable". Let's cut before "The Payroll Administrator is responsible". So About the role text:
"LRS is the industry leader in providing innovative and environmentally responsibly waste and recycling solutions. Our team delivers exceptional service and value through relentless commitment to customer satisfaction and preservation of the environment. Through our safe and innovative approach to waste diversion, LRS thrives on the passion and innovation of our employees to preserve and sustain the beauty of the towns, neighborhoods and communities that we serve. We are excited to hire candidates that align with our Vision and Values: To become the safest, most innovative waste recycler in the world by redefining the way the world views waste. Live Safety Serve With PassionInnovate RelentlesslyEngage With IntegrityBuild CommunityBe Accountable"
Note there is a missing space before "Live". We'll keep as is.
Now Responsibilities: list of duties after that sentence. Let's extract from "The Payroll Administrator is responsible for preparing and processing weekly payrolls accurately and on time." through to "Assist with other payroll related projects as assigned or required."
We need to break into bullet points. The responsibilities are a long sentence with many clauses separated by periods. Let's split:
- preparing and processing weekly payrolls accurately and on time.
- employee setup and terminations
- on-going maintenance of employee records including pay rate updates and preparation of union reporting
- supports the Payroll Manager in the development, implementation and maintenance of payroll policies, procedures, and related documentation
- Respond to employee and manager inquiries submitted through the ticketing system, ensuring timely resolution within established Service Level Agreements (SLAs) and payroll processing timelines.
- Process weekly payroll for approximately 2,200+ employees across multiple pay groups, including salary, hourly-union, and hourly-non-union employees.
- Review employee time entries for accuracy and compliance with applicable labor laws and union regulations.
- Process Leave of Absence (LOA) payments and apply various union-related deductions as required.
- Audit payroll data to identify and resolve discrepancies prior to final submission.
- Calculate and report monthly union contributions; ensure timely and accurate payment processing in accordance with union-specific schedules and requirements.
- Maintain up-to-date knowledge of all Collective Bargaining Agreements to ensure proper payroll execution and union payment compliance.
- Monitor payroll operations to ensure adherence to federal, state, and local tax regulations, as well as union-related requirements.
- Respond to and process wage garnishments, tax levies, court-ordered deductions, bankruptcies, and employment verifications in compliance with legal requirements.
- Assist with other payroll related projects as assigned or required.
We need to ensure we keep all details.
Now Requirements (Knowledge And Skill Requirements) list:
- Understanding of federal, state and local wage and hour laws, including FLSA, tax regulations and garnishment rules.
- Knowledge of how benefits such as health insurance, 401K, PTO impact payroll.
- Awareness of laws affecting employee compensation and classifications such as exempt versus non-exempt, independent contractors, etc.
- ADP Lyric Time & Attendance experience is preferred.
- Exposure to union payroll environment a plus.
- Must be proficient in Microsoft Word and Excel (Vlookup & pivot tables).
- Detailed-oriented with ability to perform with a high degree of accuracy.
- Quickly and easily adapt to change and shifting priories with enthusiasm.
- Strong problem solving, organizational, communication, and interpersonal skills required.
- Ability to work independently and as part of a team in a deadline-driven and fast paced environment.
- High level of integrity with the ability to maintain complete confidentiality.
Note there is a typo "priories". We'll keep as is.
Now Qualifications (Education & Experience):
- Bachelor’s degree preferred, or equivalent combination of education and relevant experience.
- Minimum of 3 years of payroll processing experience using a major, payroll software such as ADP, Paylocity, Paycom, Paycor, Workday, or Paychex.
Now Pay: "$32.69-36.06". Likely hourly rate. We'll put in
$32.69-36.06 per hour
maybe. But we should preserve exactly as posted: "$32.69-36.06". We'll just output that. Now we need to output HTML fragment only. Structure:About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Pay
$32.69-36.06
Make sure no extra whitespace at start/end. Check for any duplicated lines: we must not repeat content