Project Accountant I

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Intro paragraph: "As the Project Accountant, you will play a key role..." That's about the role. Could be "About the role" section. - "What You Bring: Must Haves:" list of qualifications. Also "Nice To Haves:" additional qualifications. Could be under "Requirements" or "Qualifications". We'll need to decide. - "What You Will Do:" list of duties. That's responsibilities. - "What We Offer:" benefits list. That's Benefits. - Also pay range: "The rate for this position generally ranges between $60,000 to 72,000 annually." That's Pay. - Schedule? Not mentioned. No schedule info. So we should not include Schedule. - Also maybe "Qualifications" could be separate from Requirements? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We have: - About the role: intro paragraph. - Responsibilities: "What You Will Do:" list. - Requirements/Qualifications: "What You Bring: Must Haves:" plus maybe Nice To Haves. - Skills: maybe we could extract skills like Advanced proficiency in Microsoft Excel, analytical, organizational, problem-solving, communication, etc. But we could also put them under Requirements. - Benefits: "What We Offer:" list. - Pay: salary range. We should not repeat job title as heading. We must not include boilerplate like EEO, etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We need to use

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

  for prose. We need to ensure we don't create sections with filler text. Let's extract content precisely. Intro paragraph: "As the Project Accountant, you will play a key role in managing the full project accounting lifecycle. From initial project setup through closeout, you will oversee the financial management of projects, ensuring accurate budgeting, billing, revenue recognition, forecasting, financial reporting, and compliance with contractual requirements. You will work closely with Project Managers, Operations, and Finance leadership to monitor project financial performance, identify opportunities to support profitability, and ensure financial accuracy and integrity throughout the project lifecycle. Your attention to detail and ability to collaborate across teams will be critical to the overall success of each project." That's prose; put in

  . Next: "What You Bring: Must Haves:" then list: - Bachelor's degree in Accounting, Finance, Business Administration, or a related field. - Minimum of 3 years of project accounting experience. - Demonstrated experience managing projects through the full life cycle, from project setup to project closeout. - Strong understanding of project accounting principles, budgeting, forecasting, billing, and revenue recognition. - Experience working with ERP/accounting systems. - Advanced proficiency in Microsoft Excel. - Excellent analytical, organizational, and problem-solving skills. - Strong verbal and written communication skills. - Ability to manage multiple priorities in a fast-paced environment. Then "Nice To Haves:" list: - Experience in engineering, construction, professional services, or project-based environments. - Knowledge of contract management and project financial controls. - Experience with percentage-of-completion and other project revenue recognition methods. We could combine Must Haves and Nice To Haves under a single "Requirements" section, maybe with subheadings? But we only allowed headings from list; we could still include

  for Requirements and then inside have two

  maybe with a note? But we must not invent headings not in list? The instruction: "use

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

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings where appropriate. We can also use other headings if they match? Probably safer to stick to those examples. We have content for About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. We could also have Skills section: we could extract skills like Advanced proficiency in Microsoft Excel, analytical, organizational, problem-solving, communication, etc. But those are already in Must Haves. Could put them under Skills. But we need to avoid thin sections. Perhaps better to have Requirements (including Must Haves and Nice To Haves) and Skills separate? Might be thin. Let's decide: Use About the role, Responsibilities, Requirements, Benefits, Pay. Under Requirements we can include both Must Haves and Nice To Haves as separate lists maybe with a note? But we need to use

  • for any list. We could have two
    under Requirements, maybe with a

    indicating "Must Haves:" and "Nice To Haves:" but that would be prose inside the section. That's okay. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO statement, unsolicited resumes, etc. Also remove "What Does It Look Like Working Here?" (that's fluff but maybe considered boilerplate? It's about culture; could be considered substantive? It's not required but maybe we can keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "What Does It Look Like Working Here?" is not exactly boilerplate but could be considered fluff; but it's not EEO. It's about company values. Might be considered substantive? The instruction says prefer a few substantive sections over many thin ones. This section is thin and not required. Likely we should drop it as it's not essential. Also the "CPL is an Equal Opportunity Employer..." is EEO boilerplate, drop. Also the unsolicited resumes part is boilerplate, drop. Thus final sections:

    About the role

    As the Project Accountant, you will play a key role in managing the full project accounting lifecycle. From initial project setup through closeout, you will oversee the financial management of projects, ensuring accurate budgeting, billing, revenue recognition, forecasting, financial reporting, and compliance with contractual requirements. You will work closely with Project Managers, Operations, and Finance leadership to monitor project financial performance, identify opportunities to support profitability, and ensure financial accuracy and integrity throughout the project lifecycle. Your attention to detail and ability to collaborate across teams will be critical to the overall success of each project.

    Responsibilities

    • Set up new projects in the accounting system and ensure accurate financial data.
    • Review contracts and project terms to ensure compliance with company policies and customer agreements.
    • Develop and maintain project budgets, forecasts, and cost projections.
    • Monitor project performance, costs, revenue, and profitability.
    • Prepare and process customer billings in accordance with contract terms.
    • Manage revenue recognition and ensure compliance with accounting standards.
    • Track accounts receivable, support collections efforts, and resolve billing issues.
    • Prepare monthly project financial reports, variance analyses, and forecasts.
    • Collaborate with Project Managers to identify financial risks and opportunities.
    • Process project modifications, change orders, and contract amendments.
    • Perform project closeout activities, including final billing, reconciliations, and documentation.
    • Support internal and external audits as needed.

    Requirements

    Must Haves:

    • Bachelor's degree in Accounting, Finance, Business Administration, or a related field.
    • Minimum of 3 years of project accounting experience.
    • Demonstrated experience managing projects through the full life cycle, from project setup to project closeout.
    • Strong understanding of project accounting principles, budgeting, forecasting, billing, and revenue recognition.
    • Experience working with ERP/accounting systems.
    • Advanced proficiency in Microsoft Excel.
    • Excellent analytical, organizational, and problem-solving skills.
    • Strong verbal and written communication skills.
    • Ability to manage multiple priorities in a fast-paced environment.

    Nice To Haves:

    • Experience in engineering, construction, professional services, or project-based environments.
    • Knowledge of contract management and project financial controls.
    • Experience with percentage-of-completion and other project revenue recognition methods.

    Benefits

    • Healthcare for you and your family: Medical, Dental & Vision insurance
    • Single HDHP Medical plan with 100% paid premium
    • Health Savings Account (HSA) with employer match
    • Medical and Dependent Care Flexible Spending Accounts
    • FREE Life Insurance and AD&D Insurance
    • Voluntary Life Insurance for you and your family
    • FREE Short-Term and Long-Term Disability Insurance
    • PTO + Sick Time + 8 Holidays per year
    • Retirement Savings Plan with contribution from CPL to grow your retirement funds
    • Internal Mobility & Career Advancement
    • Licensure Assistance
    • Additional benefits available to FT Employees Working 40+ Hours/Week:
    • Tuition Assistance: You may be eligible for continuing education assistance
    • Student Loan Assistance Program: CPL will contribute up to $100/month for 5 years ($6,000 total) toward student loan debt
    But note: nested
    inside
    is not valid HTML; we should avoid nesting. Better to keep as separate
    items with dash? Could keep as separate
    • with text containing sub-benefits. Simpler: keep as flat list, each benefit as
    • . The "Additional benefits available to FT Employees Working 40+ Hours/Week:" could be a
    • with subtext? Might be okay to keep as
    • and then include the two sub-benefits as separate
    • items but preceded by a note? Could just list them as separate items. Thus:
    • Additional benefits available to FT Employees Working 40+ Hours/Week: Tuition Assistance: You may be eligible for continuing education assistance; Student Loan Assistance Program: CPL will contribute up to $100/month for 5 years ($6,000 total) toward student loan debt
    But that loses some detail. Better to keep as two separate
    • items but maybe preceded by a

      note? However instruction: Use

      • for any list of duties/requirements/benefits. So we can have a
        for benefits; each benefit as
        • . We can include the two extra benefits as separate
        • items. Thus:
        • Tuition Assistance: You may be eligible for continuing education assistance (available to FT Employees Working 40+ Hours/Week)
        • Student Loan Assistance Program: CPL will contribute up to $100/month for 5 years ($6,000 total) toward student loan debt (available to FT Employees Working 40+ Hours/Week)
        That seems fine. Now Pay section:

        Pay