What CFOs Should Be Asking About Project Financial Visibility Right Now

TL;DR

Most CFOs have strong visibility into their organization’s operational finances. Fewer have the same visibility into their project portfolio’s financial performance, where a growing share of capital is being deployed. This post gives CFOs seven diagnostic questions to assess their current project financial architecture, a scoring framework to interpret the answers, and a prioritized action plan based on where they land.

There is a conversation that happens regularly in finance leadership teams, usually triggered by a project overrun, an audit finding, or a board question that takes longer than it should to answer. It goes something like this.

The CFO asks why a capital project is over budget. The PMO leader explains that costs increased due to vendor disputes and scope additions. The CFO asks when this became apparent. The PMO leader says the full picture only emerged at month-end close. The CFO asks why nobody flagged it sooner. The PMO leader explains that the finance team books costs against cost centers, and the project team tracks spend against work packages, but nobody owns the translation between the two until month-end. By the time a vendor invoice moves from approval to posting to reporting, three weeks have passed, and the project dashboard is still showing the committed budget, not what’s actually been spent.

The CFO nods and moves on. Because this is the same answer they got last quarter. And the quarter before that.

This is an architecture problem. The financial information needed for a CFO to maintain adequate governance over a project portfolio is produced by systems that do not communicate in real time. By the time the CFO sees the numbers, the decisions that determine them have already been made.

According to PMI research, poor project financial visibility contributes to between $300 billion and $600 billion wasted annually on IT projects in North America. The CFOs whose organizations contribute to that figure are not negligent. They are operating with an architectural blind spot that most of their peers share.

This post gives you the questions to diagnose whether your organization has that blind spot, and what to do about it.

“Management is doing things right; leadership is doing the right things.”

Peter Drucker

 

Key Takeaways

• Most CFOs have strong operational financial visibility and a significant project financial blind spot. The blind spot is architectural, not attentional. It is caused by systems that do not communicate in real time, not by insufficient effort.
• Project financial governance is harder than operational financial governance because projects are unique, commitments precede transactions by weeks or months, and financial information is split between two systems designed for different purposes.
• The seven diagnostic questions reveal the specific gaps in your project financial architecture: audit trail quality, reconciliation burden, payment dispute awareness, committed spend visibility, deduction tracking, proactive exception management, and treasury integration.
• A score of zero to two means an architecture review is overdue. A score of three to five means you are managing risks you cannot fully see. A score of six to seven means your current architecture is performing well and needs active maintenance.
• The highest-impact immediate action for most organizations is implementing real-time commitment tracking from the purchase order date. This closes the committed but uninvoiced visibility gap that makes cash flow forecasting systematically inaccurate.
• According to Forrester, the standard for project financial management integration is solutions that reduce complexity, not add it. That standard should guide every investment decision in this space.

“Risk comes from not knowing what you’re doing.”

Warren Buffett

 

Why Project Financial Governance Is Harder Than Operational Financial Governance

CFOs are trained to manage operational finances. Revenue, cost of goods, operating expenses, working capital, tax liabilities. These flows are relatively predictable, managed through well-established accounting systems, and visible through standard management accounts.

Project finances are different in three important ways.

Projects are temporary, unique, and non-repeating. Unlike operational costs that follow predictable patterns, every project has a different cost structure, vendor mix, and financial risk profile. The patterns that make operational financial control intuitive do not apply.

Project financial commitments precede project financial transactions by weeks or months. When a purchase order is raised on a project, a financial commitment exists that is not yet visible in the accounts payable system. When work is authorized verbally or through a change order, cost exposure exists before any invoice has been raised. Operational finance rarely has this gap between commitment and transaction.

Project financial information exists in two systems that were not designed to communicate. The project planning and tracking system holds budget positions, commitment data, and earned value calculations. The ERP holds invoices, payment records, and general ledger entries. In most organizations these two systems exchange data periodically, not continuously. The result is that the CFO’s view of project finances is always somewhat out of date, and the degree to which it is out of date varies with the complexity and pace of the project portfolio.

Gartner’s 2024 research defines Project Portfolio Management tools as designed to support the selection, planning, and execution of work packages with financial capabilities focused on strategic alignment. That design standard produces systems that are excellent at portfolio-level investment decisions and poor at real-time financial governance of project execution. The CFO who expects their Project Portfolio Management platform to provide operational financial control is expecting something the tool was not designed to deliver.

Seven Questions Every CFO Should Ask Right Now

These questions are diagnostic. Each one has a right answer, a wrong answer, and a clear implication for action. Score yourself as you go: one point for each answer that matches the “what good looks like” description, zero for each wrong answer.

Question 1: Can I trace any dollar from budget approval through payment execution in a single query?

Why it matters: If a board member or auditor asks you to demonstrate full financial traceability on any capital project today, how long would it take? If the answer requires pulling data from two or more systems and reconciling them manually, your audit trail is assembled after the fact rather than maintained continuously.

Wrong answer: “We would need to pull the project data from the Project Portfolio Management platform and the payment data from the ERP and match them up. That usually takes a day or two.”

What good looks like: You open a single dashboard in your project financial management system, enter the project and the cost line, and see the complete chain: budget approval, commitment, invoice, payment, and any deductions or adjustments. The audit trail exists in real time without manual assembly.

Question 2: What percentage of my month-end close effort is spent reconciling project and ERP financial data?

Why it matters: Every hour spent reconciling two systems that should agree is an hour not spent analyzing the financial information those systems contain. Reconciliation effort is a direct measure of integration quality. High reconciliation effort signals an architectural problem, not a process problem.

Wrong answer: “Our finance team spends most of the first week of the month reconciling project costs between the two systems. It is one of our biggest bottlenecks.”

What good looks like: Month-end project financial close requires minimal reconciliation because the Project Portfolio Management platform and ERP maintain consistent data throughout the period. Variances are investigated for business reasons, not system reasons.

Question 3: When a payment dispute arises on a project, how quickly does the project manager know?

Why it matters: A payment dispute that is invisible to the project team is an authorization risk. The project manager may continue to commit additional resources and scope with a vendor whose invoice is already in dispute, compounding the financial exposure. The delay between dispute occurrence and project team awareness is a measure of how disconnected your financial systems are.

Wrong answer: “The project manager usually finds out at month-end when the reconciliation flags the unpaid invoice, or when the vendor calls to chase payment.”

What good looks like: The project manager is notified of a payment dispute within hours of it being logged in the AP system, directly within their project management interface, before they authorize any additional work with the affected vendor.

Question 4: How much of my project portfolio’s approved budget is currently committed but not yet invoiced?

Why it matters: Committed but uninvoiced spend represents financial exposure that does not appear in accounts payable, does not appear in cost-to-date reports, and does not appear in standard management accounts. It is real financial commitment that is invisible to conventional financial reporting. If you cannot answer this question quickly, your cash flow forecasting for the project portfolio is materially incomplete.

Wrong answer: “We do not have a reliable view of committed but uninvoiced spend. We know what has been invoiced and what has been paid, but the gap in between is harder to see.”

What good looks like: You can pull real-time committed spend across the entire project portfolio, broken down by project, cost category, and vendor, within minutes. This number feeds directly into your cash flow forecast and treasury planning.

Question 5: Are financial deductions such as penalties, refunds, and adjustments recorded at the project level or only in the ERP?

Why it matters: Financial deductions affect the net cost of a project. If they are recorded only in the ERP and not visible in the project financial view, the project budget shows gross invoiced amounts while actual cash outflow is lower. This produces budget variance analysis that is systematically inaccurate because it compares gross commitments to gross actuals without reflecting the net financial position.

Wrong answer: “Deductions go through the ERP as credit notes or adjustments. The project team sees the original invoice amount in their system and the net amount only shows up after month-end reconciliation.”

What good looks like: All financial deductions are recorded at the project and cost category level in the project management system, visible to project managers in real time. Net spend is the primary financial metric, not gross invoiced amounts.

Question 6: If a project financial problem emerged today, how would I find out about it?

Why it matters: This question tests whether your financial governance is proactive or reactive. In a proactive system, financial exceptions are surfaced automatically to the right people at the point they occur. In a reactive system, financial problems are discovered through periodic reporting cycles, variance analysis, or escalation from project managers who noticed something unexpected.

Wrong answer: “Honestly, we usually find out through the monthly close process or when a project manager flags something. There is no systematic early warning mechanism.”

What good looks like: Your project financial management system flags financial exceptions automatically: invoices that have been in dispute for more than a defined number of days, commitments that have exceeded approved budget positions, payments that are at risk of triggering contractual penalties. These alerts reach the right people without waiting for a reporting cycle.

Question 7: Can my treasury team see real-time project portfolio cash flow commitments for forecasting?

Why it matters: Capital projects represent significant and irregular cash outflows. If your treasury team is forecasting from actual payment records rather than committed spend schedules, they are working from data that is systematically behind reality. The gap between committed and invoiced spend is the forecasting blind spot that produces cash flow surprises.

Wrong answer: “Treasury uses the ERP payment records for cash flow forecasting. They get a download from the project team each month but it does not always match the ERP data and they do not fully trust either number.”

What good looks like: Your treasury team has access to a real-time view of project portfolio cash flow commitments by period, drawn directly from the project financial management system. This feeds their liquidity forecasting without manual data extraction or reconciliation.

What Your Score Means

Add up your score from the seven questions. Each question where your answer matched the “what good looks like” description is worth one point.

Your Score	What It Means	Priority Action
0 to 2	Your project financial architecture has significant structural gaps. Financial information is arriving too late for effective governance, and your organization is absorbing costs that proactive visibility would prevent. An architecture review is overdue.	Conduct a formal project financial architecture assessment within the next quarter. Identify your highest-value, highest-complexity projects and prioritize visibility improvements there first.
3 to 5	Your project financial governance is partial. You have some of the right structures but significant gaps remain, particularly in real-time payment visibility and proactive exception management. You are managing risks you cannot fully see.	Define which gaps are most costly to your organization based on project complexity and governance requirements. Build a roadmap to close them in priority order over the next 12 months.
6 to 7	Your project financial architecture is performing well. Your focus should be on maintaining integration quality as your project portfolio grows and complexity increases, and on ensuring your governance structures scale with the portfolio.	Invest in monitoring and exception management to ensure your current architecture remains effective as project volume and complexity grow. Review integration depth annually against governance requirements.

Most CFOs who complete this assessment score between two and four. That score is not a reflection of financial management competence. It is a reflection of how most project financial management architectures have been built historically: sufficient for the governance requirements of the time they were designed, and increasingly inadequate for the governance requirements of today.

A Prioritized Action Plan for CFOs

The diagnostic questions identify the problem. The action plan determines what to do about it. Here is how to sequence the work based on governance impact.

Time Horizon	CFO Priority Action	What Success Looks Like
Immediate (0 to 90 days)	Map the information flow between your Project Portfolio Management platform and ERP for your three highest-value projects. Identify where the gaps are and what they are costing in reconciliation time and delayed visibility.	A documented inventory of integration gaps with an estimated cost of each gap in reconciliation effort and financial risk exposure.
Short term (90 to 180 days)	Implement commitment tracking from purchase order date across your project portfolio. This single change closes the largest visibility gap for most organizations: committed but uninvoiced spend.	Real-time view of total committed spend across the project portfolio, visible to both project managers and the treasury function, without manual data extraction.
Medium term (6 to 12 months)	Implement real-time invoice status integration between ERP and Project Portfolio Management platform. Project managers should see payment disputes and invoice status within hours, not weeks.	Average time from invoice dispute occurrence to project manager awareness reduces from weeks to hours. Authorization of additional work with disputed vendors stops occurring.
Strategic (12 to 24 months)	Evaluate whether your governance requirements have outgrown your current integration pattern. If your project portfolio complexity demands it, move from reconciliation-based integration toward real-time or project-controlled financial operations.	Month-end project financial close effort reduces materially. Audit trail for any project financial transaction is available on demand without manual assembly. Treasury cash flow forecasting uses real-time committed spend data.

Forrester research recommends that organizations look for project financial management solutions that include demand, resource, project, and cost management capabilities with integration designed to reduce complexity, not add it. The action plan above follows that principle: each step reduces the complexity of financial information management, not just the volume of data. Complexity reduction is the measure of whether an investment in project financial management is working.