Senior Manager, Project Financial Controls
Solar Landscape · New York, NY · 1 mo ago
HybridInformation TechnologyFull-time
We need to output HTML fragment with sections only where there is real specific content. Must use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: About Us, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Benefits And Perks" heading? We'll use Benefits section. Must include only sections with real specific content. The posting includes About The Role (we can map to About the role heading). Responsibilities: there is a list of responsibilities under "Key Responsibilities" with subheadings like Financial Governance Framework, Budget Governance, Purchase Order & Invoice Controls, Forecasting Standards, Continuous Improvement. We need to output a
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: About Us, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Benefits And Perks" heading? We'll use Benefits section. Must include only sections with real specific content. The posting includes About The Role (we can map to About the role heading). Responsibilities: there is a list of responsibilities under "Key Responsibilities" with subheadings like Financial Governance Framework, Budget Governance, Purchase Order & Invoice Controls, Forecasting Standards, Continuous Improvement. We need to output a - for any list of duties/requirements/benefits. Should we break each responsibility into list items? Probably each bullet under responsibilities. The text includes paragraphs describing each responsibility. We could treat each responsibility heading as a list item with sub-details maybe as nested? But spec: Use
- for any list of duties/requirements/benefits. So we need to produce a list for responsibilities. Could list each major responsibility as
- with the description inside. Could also include sub-bullets? Not required but could. Simpler: each responsibility as
- containing the paragraph(s). We'll need to preserve all substantive info, not summarize away detail. So we need to include the details within each
- . Could embed
inside
- . That's okay.
Requirements: The posting has "Qualifications And Experience". That likely maps to Requirements or Qualifications? There's both Requirements and Qualifications sections possible. We have qualifications listed: Bachelor's degree..., professional qualification..., significant experience..., experience designing..., strong understanding..., experience with ERP..., strong analytical..., ability..., demonstrated judgment... That's qualifications. Could treat as Requirements section. Also there may be Skills section? Not explicit but we could infer skills from qualifications. But we should not create sections without real specific content. The posting does not have a separate "Skills" heading; but we could put skills under Qualifications? However spec says use headings for Skills if posting has real specific content for it. There's no explicit skills list separate from qualifications; but we could treat the analytical, communication, stakeholder-management skills as skills. Might be better to put them under Qualifications. Since we have both Requirements and Qualifications headings allowed, we need to decide which to use. The posting has "Qualifications And Experience". That matches Qualifications heading. There's no separate "Requirements" heading besides that. So we will output a Qualifications section with the list.
Benefits: There's a "Benefits And Perks" section with list: Training / Professional development opportunities, 401(k) with 4% company match, Summer Fridays, Flexible remote/hybrid work options, Paid parental leave, Team lunches, events, and stocked kitchens, Modern, collaborative office spaces in Asbury Park, New York City, Boston, Chicago, and Baltimore, Medical, dental, and vision coverage, Company-paid life and long-term disability insurance. Also ADA Accommodation Statement (but that's boilerplate/EEO; we should remove). Also Salary will vary depending on location and job-related skills and experience. This is incentive-based position with potential to earn more. For part-time roles, compensation adjusted. This is Pay info? It mentions salary will vary, incentive-based, potential to earn more. That's not specific numbers; but it's still Pay info. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary will vary depending on location and job-related skills and experience; incentive-based position with potential to earn more; for part-time roles compensation adjusted. That's still Pay info albeit vague. Should we include Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, albeit not specific numbers. So we should include a Pay section with that info. However also rule: Prefer a few substantive sections over many thin ones. But we need to include Pay if there is content. We'll include Pay section with that info as a
.
Schedule: No mention of schedule (e.g., full-time, part-time, hours). There's mention of part-time roles compensation adjusted, but not schedule details. So we should not create Schedule section.
Now About the role: we have a paragraph about the role. We'll output that as
under About the role heading.
Now we need to ensure we don't include boilerplate like About Us, EEO, AI statement, ADA Accommodation Statement, etc. Also remove duplicated lines. Also remove "We may use artificial intelligence (AI) tools..." etc. Also remove "If you would like more information about how your data is processed, please contact us." Also remove "Salary will vary depending on your location and job-related skills and experience. This is an incentive-based position with the potential to earn more. For part-time roles, your compensation will be adjusted to reflect your hours." Actually that is Pay info; we keep it but maybe rephrase? We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that exact sentence? We can keep it as is inside Pay section
. It's okay.
Now we need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
The Senior Manager, Project Financial Controls establishes and maintains the financial governance framework for projects. This role defines financial control standards, approval requirements, documentation expectations, and escalation protocols, and monitors compliance across the project lifecycle. This role will also serve as a partner with corporate finance to support any project portfolio audit requirements. The Senior Manager provides independent oversight of project financial processes, including budgets, commitments, purchase orders, change orders, forecasts, invoices, and project closeout. The role partners closely with Project Management, Project Accounting, Procurement, Sub Contracting, Finance, and leadership to improve financial discipline, data quality, auditability, and decision-making.
Responsibilities
-
Financial Governance Framework: Define and maintain project financial control policies, standards, procedures, and guidance for projects; establish clear requirements for budget approval, commitment controls, change order management, forecasting, invoice validation, and financial closeout; maintain the project financial control framework and ensure it remains aligned with company policy, accounting requirements, and business objectives; define required documentation, evidence, approvals, and segregation of duties for key financial processes; maintain control calendars, compliance checklists, process maps, and control owners; identify control gaps and recommend process, system, or policy improvements; maintain and coordinate periodic review of the project Approval Authority Matrix for budgets & commitments; monitor whether approvals are obtained at the correct authority level and retained as auditable evidence; support periodic reviews of project financial compliance and readiness for internal or external audit.
-
Budget Governance: Define standards for budget development, completeness, consistency, approval, version control, and baseline management; work within existing project stage-gate process; monitor compliance with budget creation and approval requirements; establish requirements for budget changes, transfers, reallocations, contingency usage; define project financial closeout requirements, including budget freeze, purchase order closeout, final invoicing, unresolved commitments, documentation, and approvals.
-
Purchase Order & Invoice Controls: Monitor compliance with procurement and purchase order approval requirements; suggest improvements to governance requirements for purchase order creation, changes, blanket purchase orders, commitment changes, and closeout; establish enhanced review or escalation requirements for high-value, unusual, over-budget, or otherwise higher-risk commitments; monitor the purchase order and change-order logs for control exceptions, aging items, and unresolved approvals; support the definition of requirements for final billing and purchase order closeout; define documentation and process requirements for Change Orders; monitor compliance with change-order requirements and auditability of the approval process; review change-order trends, bottlenecks, aging, and recurring exceptions; define control requirements for invoice validation, matching, approval, exception handling, disputes, holds, and final invoicing; monitor compliance with requirements.
-
Forecasting Standards: Work closely with Project Accounting to establish project forecasting standards; produce clear guidance for incorporating exposures, pending buyouts, unbought scope, risks, and opportunities into project forecasts; set escalation thresholds for projected budget overages, deteriorating cost performance, or unsupported forecast assumptions; test forecast accuracy over time and identify recurring sources of forecast variance; audit forecasting practices for consistency, completeness, and adherence to approved standards; partner with Project Management and Project Accounting to improve the connection between project scope, schedule, commitments, risks, and cost forecasts.
-
Continuous Improvement: Perform periodic control reviews, sample testing, and targeted audits of project financial processes; track findings, corrective actions, owners, due dates, and remediation status; use control results to recommend training, system enhancements, process redesign, or changes to approval requirements; partner with Project Management, Project Accounting, Procurement, PMO, Finance, teams to clarify roles and improve end-to-end processes; work closely with PMO to translate control requirements into practical procedures and system-enabled workflows; support implementation of improved project financial controls and related change management; provide training and guidance to project teams on financial governance requirements; promote consistent financial practices across projects while allowing for documented, risk-based exceptions.
Qualifications
- Bachelor’s degree in Accounting, Finance, Business, Construction Management, or a related field
- Relevant professional qualification such as CPA, CMA, CFM, or equivalent experience preferred
- Significant experience in project controls, project accounting, financial controls, construction finance, capital projects, or a similar environment
- Experience designing, implementing, or monitoring financial controls across multiple projects
- Strong understanding of project budgets, commitments, purchase orders, change orders, forecasts, invoices, contingency, and financial closeout
- Experience with enterprise resource planning systems and project financial reporting tools; Microsoft Dynamics experience preferred
- Strong analytical, documentation, communication, and stakeholder-management skills
- Ability to challenge decisions constructively while maintaining effective working relationships
- Demonstrated judgment in assessing risk, materiality, exceptions, and escalation requirements
Benefits
- Training / Professional development opportunities
- 401(k) with 4% company match
- Summer Fridays
- Flexible remote/hybrid work options
- Paid parental leave
- Team lunches, events, and stocked kitchens
- Modern, collaborative office spaces in Asbury Park, New York City, Boston, Chicago, and Baltimore
- Medical, dental, and vision coverage
- Company-paid life and long-term disability insurance
Pay
Salary will vary depending on your location and job-related skills and experience. This is an incentive-based position with the potential to earn more. For part-time roles, your compensation will be adjusted to reflect your hours.
We must ensure no extra sections like Schedule. Also ensure we didn't include any boilerplate like About Us, EEO, AI statement, ADA, etc. We removed them.
Check that we preserved all substantive info: About the role paragraph, responsibilities details, qualifications list, benefits list, pay statement. Did we miss any? There's also "Key Interfaces" list: Project Management, Project Accounting, Procurement, Subcontracting, Corporate Finance, PMO, Internal or External Audit. That's substantive; should
- for any list of duties/requirements/benefits. So we need to produce a list for responsibilities. Could list each major responsibility as
- with the description inside. Could also include sub-bullets? Not required but could. Simpler: each responsibility as
- containing the paragraph(s). We'll need to preserve all substantive info, not summarize away detail. So we need to include the details within each
- . Could embed
inside
- . That's okay.
Requirements: The posting has "Qualifications And Experience". That likely maps to Requirements or Qualifications? There's both Requirements and Qualifications sections possible. We have qualifications listed: Bachelor's degree..., professional qualification..., significant experience..., experience designing..., strong understanding..., experience with ERP..., strong analytical..., ability..., demonstrated judgment... That's qualifications. Could treat as Requirements section. Also there may be Skills section? Not explicit but we could infer skills from qualifications. But we should not create sections without real specific content. The posting does not have a separate "Skills" heading; but we could put skills under Qualifications? However spec says use headings for Skills if posting has real specific content for it. There's no explicit skills list separate from qualifications; but we could treat the analytical, communication, stakeholder-management skills as skills. Might be better to put them under Qualifications. Since we have both Requirements and Qualifications headings allowed, we need to decide which to use. The posting has "Qualifications And Experience". That matches Qualifications heading. There's no separate "Requirements" heading besides that. So we will output a Qualifications section with the list.
Benefits: There's a "Benefits And Perks" section with list: Training / Professional development opportunities, 401(k) with 4% company match, Summer Fridays, Flexible remote/hybrid work options, Paid parental leave, Team lunches, events, and stocked kitchens, Modern, collaborative office spaces in Asbury Park, New York City, Boston, Chicago, and Baltimore, Medical, dental, and vision coverage, Company-paid life and long-term disability insurance. Also ADA Accommodation Statement (but that's boilerplate/EEO; we should remove). Also Salary will vary depending on location and job-related skills and experience. This is incentive-based position with potential to earn more. For part-time roles, compensation adjusted. This is Pay info? It mentions salary will vary, incentive-based, potential to earn more. That's not specific numbers; but it's still Pay info. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary will vary depending on location and job-related skills and experience; incentive-based position with potential to earn more; for part-time roles compensation adjusted. That's still Pay info albeit vague. Should we include Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about pay, albeit not specific numbers. So we should include a Pay section with that info. However also rule: Prefer a few substantive sections over many thin ones. But we need to include Pay if there is content. We'll include Pay section with that info as a
. Schedule: No mention of schedule (e.g., full-time, part-time, hours). There's mention of part-time roles compensation adjusted, but not schedule details. So we should not create Schedule section. Now About the role: we have a paragraph about the role. We'll output that as
under About the role heading. Now we need to ensure we don't include boilerplate like About Us, EEO, AI statement, ADA Accommodation Statement, etc. Also remove duplicated lines. Also remove "We may use artificial intelligence (AI) tools..." etc. Also remove "If you would like more information about how your data is processed, please contact us." Also remove "Salary will vary depending on your location and job-related skills and experience. This is an incentive-based position with the potential to earn more. For part-time roles, your compensation will be adjusted to reflect your hours." Actually that is Pay info; we keep it but maybe rephrase? We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that exact sentence? We can keep it as is inside Pay section
. It's okay. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft:
About the role
The Senior Manager, Project Financial Controls establishes and maintains the financial governance framework for projects. This role defines financial control standards, approval requirements, documentation expectations, and escalation protocols, and monitors compliance across the project lifecycle. This role will also serve as a partner with corporate finance to support any project portfolio audit requirements. The Senior Manager provides independent oversight of project financial processes, including budgets, commitments, purchase orders, change orders, forecasts, invoices, and project closeout. The role partners closely with Project Management, Project Accounting, Procurement, Sub Contracting, Finance, and leadership to improve financial discipline, data quality, auditability, and decision-making.
Responsibilities
- Financial Governance Framework: Define and maintain project financial control policies, standards, procedures, and guidance for projects; establish clear requirements for budget approval, commitment controls, change order management, forecasting, invoice validation, and financial closeout; maintain the project financial control framework and ensure it remains aligned with company policy, accounting requirements, and business objectives; define required documentation, evidence, approvals, and segregation of duties for key financial processes; maintain control calendars, compliance checklists, process maps, and control owners; identify control gaps and recommend process, system, or policy improvements; maintain and coordinate periodic review of the project Approval Authority Matrix for budgets & commitments; monitor whether approvals are obtained at the correct authority level and retained as auditable evidence; support periodic reviews of project financial compliance and readiness for internal or external audit.
- Budget Governance: Define standards for budget development, completeness, consistency, approval, version control, and baseline management; work within existing project stage-gate process; monitor compliance with budget creation and approval requirements; establish requirements for budget changes, transfers, reallocations, contingency usage; define project financial closeout requirements, including budget freeze, purchase order closeout, final invoicing, unresolved commitments, documentation, and approvals.
- Purchase Order & Invoice Controls: Monitor compliance with procurement and purchase order approval requirements; suggest improvements to governance requirements for purchase order creation, changes, blanket purchase orders, commitment changes, and closeout; establish enhanced review or escalation requirements for high-value, unusual, over-budget, or otherwise higher-risk commitments; monitor the purchase order and change-order logs for control exceptions, aging items, and unresolved approvals; support the definition of requirements for final billing and purchase order closeout; define documentation and process requirements for Change Orders; monitor compliance with change-order requirements and auditability of the approval process; review change-order trends, bottlenecks, aging, and recurring exceptions; define control requirements for invoice validation, matching, approval, exception handling, disputes, holds, and final invoicing; monitor compliance with requirements.
- Forecasting Standards: Work closely with Project Accounting to establish project forecasting standards; produce clear guidance for incorporating exposures, pending buyouts, unbought scope, risks, and opportunities into project forecasts; set escalation thresholds for projected budget overages, deteriorating cost performance, or unsupported forecast assumptions; test forecast accuracy over time and identify recurring sources of forecast variance; audit forecasting practices for consistency, completeness, and adherence to approved standards; partner with Project Management and Project Accounting to improve the connection between project scope, schedule, commitments, risks, and cost forecasts.
- Continuous Improvement: Perform periodic control reviews, sample testing, and targeted audits of project financial processes; track findings, corrective actions, owners, due dates, and remediation status; use control results to recommend training, system enhancements, process redesign, or changes to approval requirements; partner with Project Management, Project Accounting, Procurement, PMO, Finance, teams to clarify roles and improve end-to-end processes; work closely with PMO to translate control requirements into practical procedures and system-enabled workflows; support implementation of improved project financial controls and related change management; provide training and guidance to project teams on financial governance requirements; promote consistent financial practices across projects while allowing for documented, risk-based exceptions.
Qualifications
- Bachelor’s degree in Accounting, Finance, Business, Construction Management, or a related field
- Relevant professional qualification such as CPA, CMA, CFM, or equivalent experience preferred
- Significant experience in project controls, project accounting, financial controls, construction finance, capital projects, or a similar environment
- Experience designing, implementing, or monitoring financial controls across multiple projects
- Strong understanding of project budgets, commitments, purchase orders, change orders, forecasts, invoices, contingency, and financial closeout
- Experience with enterprise resource planning systems and project financial reporting tools; Microsoft Dynamics experience preferred
- Strong analytical, documentation, communication, and stakeholder-management skills
- Ability to challenge decisions constructively while maintaining effective working relationships
- Demonstrated judgment in assessing risk, materiality, exceptions, and escalation requirements
Benefits
- Training / Professional development opportunities
- 401(k) with 4% company match
- Summer Fridays
- Flexible remote/hybrid work options
- Paid parental leave
- Team lunches, events, and stocked kitchens
- Modern, collaborative office spaces in Asbury Park, New York City, Boston, Chicago, and Baltimore
- Medical, dental, and vision coverage
- Company-paid life and long-term disability insurance
Pay
Salary will vary depending on your location and job-related skills and experience. This is an incentive-based position with the potential to earn more. For part-time roles, your compensation will be adjusted to reflect your hours.
We must ensure no extra sections like Schedule. Also ensure we didn't include any boilerplate like About Us, EEO, AI statement, ADA, etc. We removed them. Check that we preserved all substantive info: About the role paragraph, responsibilities details, qualifications list, benefits list, pay statement. Did we miss any? There's also "Key Interfaces" list: Project Management, Project Accounting, Procurement, Subcontracting, Corporate Finance, PMO, Internal or External Audit. That's substantive; should