Director of Accounts Payable

We need to output HTML fragment with sections: About the role? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections when posting has real specific content. Must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the posting: It includes About Us, Company Overview, About this Role, Position Summary, Key Responsibilities (with subpoints), Preferred Qualifications, Key Skills & Attributes, Work Environment / Physical Requirements, Benefits. We need to map to headings: About the role (maybe combine About Us and Position Summary?), Responsibilities (Key Responsibilities), Requirements (maybe Preferred Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (Key Skills & Attributes), Benefits (Benefits), Pay (if any mention of pay? Not present), Schedule (if any mention? Not present). So we should not include Pay or Schedule sections because no specific content. We need to include sections only when posting has real specific content. So we will have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also Work Environment? Not in list of allowed headings; we could maybe include under Skills? But we must stick to allowed headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying these are examples; we could also include other headings? Probably we should stick to these. Work Environment not listed; maybe we can omit or include under Skills? Better to omit if not matching allowed headings. But we need to preserve all substantive information; if we omit Work Environment, we lose info. However we could incorporate that info into Skills or Responsibilities? Not ideal. Perhaps we can include a section "Work Environment" as a heading even though not in examples? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are typical but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Could interpret that we should use those headings when applicable; but we could also add other headings if needed. However they say "Prefer a few substantive sections over many thin ones." So we could combine Work Environment into Skills or Responsibilities? Might be okay to add a Work Environment section as

Work Environment

. But the instruction didn't forbid other headings; just gave examples. Safer to include Work Environment as a section. Also we need to remove duplicated lines, boilerplate like Equal Opportunity Employer etc. Also remove navigation etc. We need to preserve all substantive info: About Us, Company Overview, About this Role, Position Summary, Key Responsibilities (with bullet points), Preferred Qualifications, Key Skills & Attributes, Work Environment / Physical Requirements, Benefits. We need to format as HTML:

About the role

then maybe a

summarizing About Us, Company Overview, About this Role, Position Summary? But we should not invent or summarize away detail; we need to preserve ALL substantive information. That means we need to keep the text as is, not summarizing. However we can keep paragraphs (

) containing the original prose. We can split into multiple

elements. We must not repeat the job title as a heading. The job title is "Director of Accounts Payable". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the Equal Opportunity Employer section and any duplicated lines (like "We are an Equal Opportunity Employer, including disability and protected veteran status." etc). Also remove "All qualified applicants will receive consideration..." etc. Also remove "We offer our team members competitive pay and benefits, rewarding work, growth opportunities, and a constructive and collaborative work environment." That's substantive? It's about benefits and work environment; maybe keep as part of About the role or Benefits. It's not boilerplate; it's part of company overview. Keep. We need to preserve all substantive info; so we keep that sentence. Now structure:

About the role

Summit Line Construction, a subsidiary of Quanta Services, Inc. (NYSE: PWR), is one of North America's premier utility construction companies. Headquartered in Heber City, Utah, we offer powerline and substation construction and maintenance services in a variety of utility markets. Like many Quanta operating companies, Summit Line continues to experience significant growth. As our national operations expand, we seek motivated individuals to join the team! Company Overview Summit Line Construction is headquartered in Heber City, Utah with additional Utah locations in Sandy and Provo. You can also find our offices in Northern California, Reno, Las Vegas and Phoenix with project locations across the western region. We offer our team members competitive pay and benefits, rewarding work, growth opportunities, and a constructive and collaborative work environment. Position Summary The Director of Accounts Payable will lead and grow Summit Line's AP function, currently a team of approximately 10, with plans for continued expansion as the company scales. This role owns the end-to-end AP process - including high-volume invoice processing, PCard administration, vendor management, and month-end close activities - while driving process improvement, automation, and stronger internal controls. The ideal candidate is a hands-on people leader who thrives in a fast-growing environment, is passionate about developing their team, and is eager to modernize and scale AP operations to keep pace with the business. This role will report at our Headquarters location in Heber City, UT.

That seems to combine About Us, Company Overview, About this Role, Position Summary. It's a bit long but preserves all info. Next

Responsibilities

Then we need to list the bullet points from Key Responsibilities. The original has subheadings: Team Leadership & Development, AP Operations Management, Process Improvement & Automation, Controls, Compliance & Reporting, Cross-Functional Collaboration. Each with bullet points. We should preserve them as

• . We can keep the subheadings as maybe or just part of
• text. Since we must not invent headings beyond allowed, we can embed subheadings inside
• as plain text. Thus:

  Responsibilities

  • Team Leadership & Development Lead, mentor, and develop a team of AP professionals (currently ~10, growing), including hiring, training, performance management, and career development Build a strong team culture centered on accuracy, accountability, and continuous improvement Establish clear roles, workflows, and career paths as the team scales with company growth Serve as a resource and escalation point for complex AP issues and team questions
  • AP Operations Management Oversee the end-to-end accounts payable process, including invoice receipt, coding, approval routing, and payment processing for a high volume of transactions each month Manage the corporate PCard program, including transaction review, reconciliation, policy compliance, and cardholder support Ensure timely, accurate processing of vendor invoices and employee expense/PCard transactions in accordance with company policy Oversee vendor master data integrity, W-9/1099 compliance, and vendor relationship management Manage AP-related month-end close activities, including accruals, reconciliations, and reporting deadlines
  • Process Improvement & Automation Continuously evaluate and improve AP processes, controls, and policies to support a rapidly growing, multi-region organization Partner with IT/Systems teams on AP-related system implementations, upgrades, and integrations within JD Edwards (JDE) and related tools Establish and monitor KPIs/metrics for AP performance (e.g., invoice cycle time, on-time payment rate, exception rates)
  • Controls, Compliance & Reporting Design and maintain strong internal controls over the AP and PCard processes to mitigate risk and support audit readiness Ensure compliance with company policy, GAAP, and applicable regulatory requirements Prepare and present AP performance reporting and metrics to finance leadership Support internal and external audit requests related to AP and PCard activity
  • Cross-Functional Collaboration While honoring the controls in place and maintaining integrity, strive to get to “yes” Partner with Regional Controllers, Regional VPs, Procurement, and Operations teams to ensure smooth invoice and payment workflows across all regions Act as a key liaison between AP and project management teams Support broader finance department initiatives and special projects as needed
  But note we need to avoid duplication: The original bullet points had line breaks; we combined them. Ensure we didn't lose any info. Let's verify each bullet: Team Leadership & Development: - Lead, mentor, and develop a team of AP professionals (currently ~10, growing), including hiring, training, performance management, and career development - Build a strong team culture centered on accuracy, accountability, and continuous improvement - Establish clear roles, workflows, and career paths as the team scales with company growth - Serve as a resource and escalation point for complex AP issues and team questions AP Operations Management: - Oversee the end-to-end accounts payable process, including invoice receipt, coding, approval routing, and payment processing for a high volume of transactions each month - Manage the corporate PCard program, including transaction review, reconciliation, policy compliance, and cardholder support - Ensure timely, accurate processing of vendor invoices and employee expense/PCard transactions in accordance with company policy - Oversee vendor master data integrity, W-9/1099 compliance, and vendor relationship management - Manage AP-related month-end close activities, including accruals, reconciliations, and reporting deadlines Process Improvement & Automation: - Continuously evaluate and improve AP processes, controls, and policies to support a rapidly growing, multi-region organization - Partner with IT/Systems teams on AP-related system implementations, upgrades, and integrations within JD Edwards (JDE) and related tools - Establish and monitor KPIs/metrics for AP performance (e.g., invoice cycle time, on-time payment rate, exception rates) Controls, Compliance & Reporting: - Design and maintain strong internal controls over the AP and PCard processes to mitigate risk and support audit readiness - Ensure compliance with company policy, GAAP, and applicable regulatory requirements - Prepare and present AP performance reporting and metrics to finance leadership - Support internal and external audit requests related to AP and PCard activity Cross-Functional Collaboration: - While honoring the controls in place and maintaining integrity, strive to get to “yes” - Partner with Regional Controllers, Regional VPs, Procurement, and Operations teams to ensure smooth invoice and payment workflows across all regions - Act as a key liaison between AP and project management teams - Support broader finance department initiatives and special projects as needed Our combined li includes all points, though we merged some sentences without punctuation; but we kept the content. It's okay. Next

  Requirements

  and

  Qualifications

  . The posting has "Preferred Qualifications What You'll Bring" with three bullet points. Also there may be "Key Skills & Attributes". We need to decide mapping: Requirements could be the Preferred Qualifications? Qualifications maybe also Preferred Qualifications? But we have both headings; we could split: Requirements = Preferred Qualifications (experience), Qualifications = maybe also Preferred Qualifications? That would duplicate. Better to assign Requirements = Preferred Qualifications (experience), Qualifications = maybe also Preferred Qualifications? Not ideal. Perhaps we treat Requirements as the "Preferred Qualifications" and Qualifications as the "Key Skills & Attributes"? But Skills heading exists separately. So maybe: - Requirements: Preferred Qualifications (ex