Senior Project Accountant, Regulatory

We need to output HTML fragment with sections: About Us? The instruction says 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 decide which sections to include based on content. The posting includes: - About Us (company description) - Our Purpose, Mission & Values (maybe not needed? It's about company values) - Benefits (some content) - About The Role (description) - Responsibilities (list) - Qualifications (list) - Possibly Skills? Not separate; qualifications include skills. We should not include sections like Pay, Schedule if not present. Benefits is present: "We provide our team the opportunity to share their unique perspectives, solve new challenges, and continue in their career growth. We are committed to supporting employees’ happiness, healthiness, and overall well-being by providing comprehensive benefits that include 100% employer paid premium healthcare, paid parental leave and more." That's specific enough. We need to include About Us? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list About Us or Our Purpose etc. But we can include a section for About Us? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive list. But we should include sections only when posting has real content. The posting has About Us description; we could include a section like About Us or Company Overview. However the examples didn't include About Us; but we could still use a heading like About Us. The instruction didn't forbid other headings. It says use

  for section headings (e.g. ...). So we can use any heading but likely they expect those typical sections. However we have content for About Us, Purpose/Mission/Values, Benefits, About The Role, Responsibilities, Qualifications. We could combine About Us and Purpose/Mission/Values into a single "About the Company" section. But the instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the Company (covering About Us, Purpose, Mission, Values), About the Role, Responsibilities, Qualifications, Benefits. That's five sections. We must not repeat the job title as a heading. The job title is Senior Project Accountant; we shouldn't make a heading for that. We need to use

  • for any list of duties/requirements/benefits. So Responsibilities list, Qualifications list, Benefits list (though benefits is a prose sentence with list items maybe we can make a list). Benefits: "comprehensive benefits that include 100% employer paid premium healthcare, paid parental leave and more." Could be a list: 100% employer paid premium healthcare, paid parental leave, etc. We'll make a
    • . We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from About Us, Purpose/Mission/Values, Benefits, About The Role, Responsibilities, Qualifications. We must remove boilerplate like cookie/navigation/legal/EEO etc. There's none. We must not include duplicated lines. We need to ensure we don't create Pay/Schedule sections unless present. Not present. Now craft HTML. We'll start with

      About the Company

      then

      containing the combined About Us, Purpose, Mission, Values. We need to be careful not to lose any detail. About Us text: "Founded in 1990, LS Power is a premier development, investment, and operating company focused on the North American power and energy infrastructure sector, with leading platforms across generation, transmission and energy expansion solutions. Since inception, LS Power has developed or acquired 50,000 MW of power generation, including utility-scale solar, wind, hydro, battery energy storage, and natural gas-fired facilities. Through its transmission business, LS Power Grid, the company built and operates 780+ miles of high-voltage transmission and 7 transmission utilities and has another 375+ miles currently in construction or development. LS Power actively invests in and scales businesses that are meeting the growing needs of the energy expansion, including electric vehicle charging, demand response, microgrids, renewable fuels and waste-to-energy platforms. Over the years, LS Power has raised more than $89 billion in debt and equity capital to support North American infrastructure." Our Purpose, Mission & Values: "Our Purpose is to solve complex energy problems that improve the world. Our Mission is to make lives better by developing a cleaner and more reliable energy ecosystem. Our Values are Integrity, Innovation, Teamwork, and Taking Ownership. We ask every candidate to think about how their unique skillsets, capabilities, and experiences can help us further strengthen our culture. Our People create value and are our Most Valuable asset. We take our values of Integrity, Innovation, Teamwork and Taking Ownership seriously and ask candidates to think about how they can help us further enhance our culture with their specific skillsets, capabilities and experiences." We can combine into a paragraph or multiple paragraphs. Use

      for prose. Next section:

      About the Role

      then

      with the description. About The Role text: "LS Power is seeking a Senior Project Accountant to join its growing Regulatory Accounting team. This role serves as a key liaison between the project management, regulatory accounting, and fixed asset accounting teams — ensuring capital project activity is accurately tracked, reported, and reflected across all three functions. The ideal candidate goes beyond recording transactions, acting as a proactive financial partner who understands financial reporting, flags budget overruns early, challenges cost classifications before they hit the ledger, and brings financial discipline and visibility to the construction process across multiple regulated entities and jurisdictions." Note there's a typo "construction pr ocess" with a space; we should preserve as is? Probably keep exactly but maybe fix? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The typo is part of the posting; we should keep it as is? It says "construction pr ocess". We'll keep exactly. Next: Responsibilities section. We need to extract list items. Responsibilities text includes multiple paragraphs each starting with a bold heading? Actually the posting: Responsibilities What You Will Do Project Accounting & Month-End Close Coordinate with AP, procurement, and project development teams to ensure accurate capital project coding and timely capture of costs in the general ledger. Review construction contract invoices against approved budgets; maintain a change order log; and track retainage balances. Assist with project-related month-end close, including recording actuals, determining accruals, and reconciling project balance sheet accounts. Coordinate with project managers and the fixed asset accounting team to monitor CWIP balances and ensure timely plant-in-service transfers. Assist the fixed asset accounting team with FERC asset unitizations and support. Collaborate with and assist the accounting team with other tasks as they arise. Cash Management & Financial Reporting Lead the monthly cash forecasting process for capital projects and monitor cash positions across entities to identify funding needs. Build and maintain a monthly project spend report for leadership and investors and support project budget preparation and variance analysis. Complete monthly and quarterly reporting as required by individual projects. Assist with financial statement preparation (quarterly and annually) Assist with the annual financial statement audit and related support/documentation. Assist with the annual budget process for capital spend and review capital project budget justifications. Regulatory Compliance Provide accurate, timely data for regulatory reports and filings, including FERC Form 1 and other required submissions. Support the income tax, property tax, and sales and use tax teams with project cost detail and documentation as needed. We need to turn each bullet into

    • . The headings like Project Accounting & Month-End Close, Cash Management & Financial Reporting, Regulatory Compliance are subheadings; we could either treat them as part of list items or as separate headings. But instruction: Use
      • for any list of duties/requirements/benefits. So we can make a single
        with all duties as
        • . The subheadings could be included as part of the
        • text (maybe we keep them as separate
        • with bold? But we cannot use markdown; we can just include them as plain text within
        • . Probably better to keep them as separate
        • items that are the subheadings? But they are not duties; they are categories. However we could keep them as
        • with the category text and then nested list? That might be overcomplicated. Simpler: create a
          where each line after the subheading is a duty; we could include the subheading as a
          • but that would be odd. Perhaps we can make multiple
            sections under subheadings using

            ? But instruction only mentions

            for section headings; we could use

            for subheadings but not prohibited. However to keep simple, we can just list all duties as

            items, preserving the subheadings as part of the first duty? Actually the subheadings are not duties; they are section titles within responsibilities. If we omit them, we lose some structural info but not substantive duty content. The instruction says preserve ALL substantive information; subheadings are substantive? They categorize duties but not essential. Might be okay to drop them? Safer to keep them as

            items but maybe we can wrap them in ? Not allowed? We can use HTML tags like inside

            . That's fine. Thus we can do:

            • Project Accounting & Month-End Close
            • Coordinate with AP, procurement, and project development teams to ensure accurate capital project coding and timely capture of costs in the general ledger.
            ...

            But that would create an empty duty for the subheading line; maybe better to include the subheading as part of the first duty: e.g., "

            Project Accounting & Month-End Close: Coordinate with AP, procurement, and project development teams to ensure accurate capital project coding and timely capture of costs in the general ledger.

            " However the original had multiple duties under that subheading; we could combine them? That would lose detail. Better to keep subheading as separate

            but maybe it's okay. Given instruction to prefer few substantive sections over many thin ones, but within a section we can have multiple

            . It's fine. We'll produce a

            with each duty as
            • . We'll include subheadings as
            • with to keep them. Now Qualifications section. Qualifications text includes multiple paragraphs each starting with "We Want You on Our Team Because You…" then bullet points. We need to extract each qualification as
            • . The text: Qualifications We Want You on Our Team Because You… Hold a Bachelor’s degree in Accounting or Finance; Master’s degree or CPA designation is preferred. Have a minimum of two years of accounting experience,