Payroll Supervisor

We need to output HTML fragment with sections: About Us? Actually we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting: It includes "About Us", "Why Work for CS Contract Solutions?", "What we offer", "Our Core Values", "Position summary", "Key responsibilities", "Required qualifications", "Competencies and work environment", "Schedule and setting". Also there is mention of "Competitive base pay", "Comprehensive health, dental, and vision package", "401(k)", "Ongoing training and development", "Opportunities for career growth and advancement", "A dynamic and supportive work environment". So Benefits section can be derived from "What we offer". Pay: "Competitive base pay" is mentioned but not specific amount; we should not create Pay section unless posting actually states them. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive base pay" but that's vague; is that considered stating them? It says "Competitive base pay" - that is a statement about pay, albeit not a number. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive base pay". So we could include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might combine Benefits and Pay? But they are separate headings. We could include Benefits section with the list: Competitive base pay, Comprehensive health, dental, and vision package, 401(k), Ongoing training and development, Opportunities for career growth and advancement, A dynamic and supportive work environment. Pay section maybe just "Competitive base pay". But that seems thin. Better to combine into Benefits? But the instruction says use headings for Benefits, Pay, Schedule. If we include Pay, we need actual content. It says "Competitive base pay". That's content, albeit vague. We'll include it. Schedule: "Schedule and setting: On-site in Bedford, NH. Standard business hours, with extended hours around payroll deadlines, quarter-end, and year-end." So we have schedule content. Thus we can have sections: About Us (maybe not a standard heading but we could use About the role? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings, but we can also use other headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings where appropriate. For "About Us" we could use About the role? But the posting has "About Us" describing company. Could map to "About the role"? Not exactly. However we could treat "About Us" as a section heading but not in the list; but instruction says use those headings for section headings (e.g. ...). It may be okay to use other headings as long as they are

  . Safer to map to given headings: About the role (maybe we can put company overview there). Responsibilities (Key responsibilities). Requirements (maybe Required qualifications). Qualifications (maybe Competencies and work environment? Actually Qualifications could be required qualifications). Skills (maybe competencies). Benefits (What we offer). Pay (Competitive base pay). Schedule (Schedule and setting). We'll avoid thin sections: maybe combine Qualifications and Skills? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for each. We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities we should list each duty as
  • . For Required qualifications we list each as
  • . For Benefits we list each as
  • . For Skills maybe list competencies as
  • . For Schedule we can just put

    . We must not repeat job title as heading. Not needed. We must not include boilerplate like EEO etc. Not present. We need to preserve all substantive information. So we need to include all details from the posting. Let's extract content: About Us: "CS Contract Solutions, LLC. is a leading telecommunications vendor in the United States. One of our specialties is long-term, project-based staffing solutions. Our network spans 24 states, employing over 350 technicians, engineers, and construction specialists for both outside and inside plant projects. Our team works diligently to uphold our standard of excellence." Why Work for CS Contract Solutions?: "At CS Contract Solutions, our mission is to empower our employees to deliver exceptional results through innovation, collaboration, and unwavering commitment to excellence as we work together to build out the nation's fiber optic networks of tomorrow. We strive to cultivate a culture that fosters creativity, integrity, and continuous learning." What we offer: list: Competitive base pay, Comprehensive health, dental, and vision package, 401(k), Ongoing training and development, Opportunities for career growth and advancement, A dynamic and supportive work environment. Our Core Values: list: Honesty and Integrity, Attitude over skills, Courage in Communication, The 3 Es: Effort, Energy, and Execution, Keep Your Axe Sharp. Position summary: "The Payroll Supervisor owns the accurate, on-time processing of weekly payroll for approximately 1,000 employees across 36 states and supervises a team of payroll specialists. This role reports to the Controller and works closely with Operations, HR, and Accounting. It is accountable for payroll accuracy, tax and wage-and-hour compliance, and the controls that keep payroll data clean and auditable." Key responsibilities: list of duties: - Payroll processing: Run the full weekly payroll cycle: timecard import, review, adjustments, approvals, funding, and distribution. Audit gross-to-net results, overtime, shift differentials, per diems, and retroactive pay before release. Process off-cycle checks, terminations, and final pay within state-required deadlines. Review new hires, rate changes, and terminations for correct set-up and effective dates. - Compliance and tax: Ensure compliance with FLSA, state wage-and-hire rules, and local pay-frequency and pay-stub requirements. Oversee federal, state, and local payroll tax deposits, filings, and registrations in new jurisdictions. Administer garnishments, child support orders, and levies; respond to agency notices. Manage unemployment claims data, workers' compensation payroll reporting, and audit requests. - Team supervision: Supervise, train, and schedule the payroll team; set coverage so no cycle depends on one person. Review specialists' work, set accuracy and turnaround standards, and handle performance reviews. Serve as the escalation point for pay disputes from employees and field managers. - Systems and reporting: Maintain payroll and timekeeping system configuration, including pay codes, deductions, and earnings rules. Reconcile payroll to the general ledger, bank activity, and quarterly 941s; support month-end close. Document procedures and drive automation that reduces manual entry and rework. Required qualifications: list: - Five or more years of full-cycle payroll experience, including at least two years leading or supervising others. - Multi-state payroll experience, including state tax registration and reciprocity rules. - Working knowledge of FLSA, overtime calculation, wage payment and final-pay rules. - Hands-on experience with ADP Workforce Now and strong Excel skills (pivot tables, lookups). - Demonstrated accuracy under deadline and sound judgment with confidential compensation data. Competencies and work environment: list? It says: "The job rewards precision and steadiness. Payroll runs on a fixed calendar, and the supervisor is the person who makes the deadline hold. Detail orientation, with a habit of reconciling rather than assuming. Clear written and verbal communication with employees who are asking about their pay. Discretion with compensation, banking, and personal data. Comfort improving a process rather than repeating it manually." We can treat these as competencies/skills. Schedule and setting: "On-site in Bedford, NH. Standard business hours, with extended hours around payroll deadlines, quarter-end, and year-end." Now we need to produce HTML with

    headings and appropriate content. We need to decide which headings to use. Let's map: - About Us -> maybe "About the role" but we could also use "About Us" as heading; but instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to use those exact headings where applicable. For company overview, we could use "About the role" but that's weird. However we could treat "About Us" as "About the role"? Not ideal. Maybe we can omit About Us section? But we must preserve ALL substantive information. So we need to include it somewhere. Could we put it under a

    without heading? The instruction says use

    for section headings, but doesn't say every piece must be under a heading. We could have a leading

    for About Us without heading. That might be acceptable. However they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies if we have a section heading, we should use

    . But we could have a paragraph without heading. I'd include a heading "About the company" maybe not in list but still

    . I think it's okay to use a heading not in the list as long as it's

    . The examples are just examples. So we can use

    About Us

    . Similarly for Why Work for CS Contract Solutions? maybe we can incorporate into About Us or separate. But we could combine. Better to follow the spirit: Use headings for major sections: About Us, Why Work Here, What we offer (Benefits), Core Values, Position summary, Key responsibilities (Responsibilities), Required qualifications (Requirements/Qualifications), Competencies (Skills), Benefits (What we offer), Pay, Schedule. But we must avoid thin sections. Benefits we have list; Pay we have just "Competitive base pay" which is thin but we could incorporate into Benefits. Actually Benefits already includes Competitive base pay as first item. So we could omit separate Pay section. Schedule we have content. Thus sections: About Us, Why Work Here, Core Values, Position summary, Responsibilities, Requirements, Skills, Benefits, Schedule. But we need to map to allowed headings: About the role (maybe About Us), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no Qualifications separate from Requirements; we could treat Required qualifications as Requirements.