A CFO asks how much of a program's money is still free. The PMO's spreadsheet says $3.60M. Finance disagrees, because a $1.25M contract was signed last month and the work has not been delivered yet. Neither number is wrong. They answer different questions, and nobody agreed which question was being asked.
What Is Project Portfolio Financial Management?
Project portfolio financial management is the practice of planning, funding, tracking, and forecasting the money behind every project in a portfolio, so leaders can decide where to invest next. It is the financial side of project portfolio management.
Project financial management asks whether one project is within its budget. The portfolio view asks a wider question: given everything competing for the same money, are we funding the right work, and what will it all cost by the end?
The PMO is usually well placed to run this, because it sees across projects.
Who Is Responsible for Project Portfolio Financial Management?
Project portfolio financial management requires coordination between Finance, the PMO, project managers and organizational leadership. Each function has a different responsibility, but all contribute to maintaining financial visibility and ensuring investments remain aligned with organizational priorities.
| Role | Primary responsibility |
|---|---|
| CFO / Finance | Accounting policies, financial controls, financial reporting and ledger reconciliation |
| PMO Director | Portfolio financial governance, reporting standards and consolidated financial visibility |
| Project Manager | Maintaining project budgets, forecasts, commitments and cost reporting |
| Portfolio Manager | Evaluating funding allocation, portfolio financial performance and investment decisions |
| Project Sponsor | Approving the investment and remaining accountable for its business justification |
The important distinction is that the PMO provides portfolio-level governance and visibility, while Finance remains responsible for accounting policies and the official financial records.
Why Financial Management Matters at the Portfolio Level
A set of well-run projects can still add up to a badly run portfolio. Three problems only show up when you look across projects:
Project portfolio budgeting and multi-year funding
Project portfolio budgeting starts with a distinction that often gets blurred. A budget is what you plan to spend. Funding is the money actually authorized from a specific source. Long programs often get approved in total but funded one fiscal year at a time, which is common in public sector portfolios where money is appropriated annually.
Take a made-up Warehouse Automation Program, with $5.70M of planned spend across three fiscal years:
Illustrative example. A positive difference means under plan, a negative difference means over.
The program looks about 6% over in total, but the problem sits in FY2027, which is 25% over a year that has no funding yet. A multi-year view shows that while there is still time to act. It also forces three rules worth writing down:
- Carryover. Does the $0.05M not spent in FY2025 roll forward, or return to the pool? Finance should decide this before year end.
- Future-year status. Keep approved and not yet funded visibly separate. Capital project intake is a good place to set this up, before a project exists.
- Annual re-confirmation. Decide whether later years are funded automatically or reviewed again against the rest of the portfolio.
Project Budgets vs. Forecasts vs. Actual Costs
Most financial confusion in a portfolio comes from using these terms loosely. Each one answers a different question, so agree on the definitions before comparing any numbers:
| Figure | The question it answers | Example | Changes when |
|---|---|---|---|
| Approved budget | How much are we authorized to spend? | $6.00M | A formal change is approved |
| Baseline (BAC) | What are we measuring performance against? | $5.70M | Rarely, and only through change control |
| Committed costs | What have we legally or contractually promised? | $1.25M | A contract or purchase order is issued; the open commitment changes as goods and services are received, cancelled or amended |
| Actual costs | What has been incurred and recorded? | $2.10M | Costs are incurred and recorded |
| Forecast | What do we expect to spend, and when? | By period | Whenever the plan or estimate changes |
| Estimate at completion (EAC) | What will the whole thing cost by the end? | $6.05M | Actuals or the forecast change |
Warehouse Automation Program (illustrative)
What was approved
Where the money stands
Estimate at completion: $6.05M. That is $0.35M over the baseline, and $0.05M more than the reserve could cover.
Approved budget vs. baseline
These two get treated as the same number, and often they are not. In this guide, BAC always means Budget at Completion, the total of the cost baseline, and never the total authorized funding:
| Financial term | Amount | Meaning |
|---|---|---|
| Approved budget | $6.00M | Total authorized funding, including management reserve |
| Management reserve | $0.30M | Funding held for unforeseen work |
| Cost baseline (BAC) | $5.70M | Approved performance measurement baseline |
Project managers work to the baseline, and drawing on the reserve should need someone else's approval.
Freeze the baseline and change it only through an approved change request. A baseline that moves quietly every time the forecast moves can no longer show that anything went wrong.
Managing CAPEX and OPEX Across Projects
Capital expenditure (CAPEX) creates an asset that is recorded on the balance sheet and depreciated over time. Operating expenditure (OPEX) is charged to the income statement as it is incurred. The difference changes this year's reported profit, so CAPEX and OPEX management is rarely just a labeling exercise. Many organizations also hold separate budgets for each, and money cannot always move between them.
Whether a software purchase or implementation cost qualifies as CAPEX depends on the applicable accounting standards, the nature of the software rights and the organization's accounting policies. Finance should determine the appropriate treatment.
For organizations reporting under US GAAP, FASB ASU 2025-06 changes the capitalization guidance for internal-use software, including removing the previous project-stage approach. Capitalization is tied to management authorization and a funding commitment, provided the applicable probability and development criteria are met. It applies to annual periods beginning after December 15, 2027, and early adoption is permitted. Organizations using IFRS or other accounting frameworks must apply their own standards, such as IAS 38 under IFRS.
For the PMO, the practical habits are the same either way:
- Classify at the cost line, not the project. A single project usually holds both. Warehouse Automation is $4.60M CAPEX and $1.45M OPEX.
- Classify at intake. A split agreed before approval is far easier than a reclassification after the money is spent. It matters most on heavy asset work such as manufacturing capital projects.
- Make unclassified spend visible. Show it as its own figure, so someone resolves it, instead of letting it default to one side.
Tracking Committed Costs and Financial Obligations
A committed cost is money you have promised for goods or services not yet received, such as a signed contract, a purchase order, or a statement of work. This is the gap in the opening example. Comparing actuals with the baseline suggests $3.60M is left. Subtract the commitments and only $2.35M remains available, against $2.70M of work still to be contracted. The shortfall was there all along, but actuals alone could not show it.
- Move amounts as costs are incurred. As goods and services are received and costs are incurred, the corresponding amounts should move from open commitments into actual costs. Purchase orders, accruals and invoices should be reconciled with the organization's financial system to avoid double-counting costs.
- Know how firm each promise is. A contract with a cancellation clause is a different risk from a non-cancellable one, and it matters when budgets are cut.
- Check the ERP or procurement system. Purchase orders usually live there. Compare them with project budgets in each monthly close.
- Watch for work under way with no paperwork. A vendor working ahead of a signed contract is a commitment that no report will show.
Project Cost Forecasting and Estimate at Completion (EAC)
EAC is not another name for a forecast. Project cost forecasting uses three related figures:
Here, EAC is the $2.10M in actuals plus an ETC of $3.95M, which gives $6.05M.
There is more than one way to calculate it. Using an earned value of $1.95M, meaning the budgeted value of the work completed so far, the same program produces three answers:
The formula matters less than using one method consistently across the portfolio and refreshing it on a regular cycle. A forecast is also only as good as its staffing assumptions, so connect it to resource and capacity planning. If a team is reassigned or a contractor added, the forecast should move even though the approved budget has not.
Managing Budget Variances Across the Portfolio
Project budget variance analysis compares the baseline with the current EAC. Comparing the baseline with spend to date only tells you about the past, and a project that is simply running late can look under budget. Here is what the same check looks like across four projects:
Illustrative example. Variance = baseline - EAC, so a negative figure means an expected overrun.
The total says nothing is wrong. Two projects are a combined $0.65M over, and two others are $0.65M under. The underrun could be real savings, delayed work, or dropped scope. Only a project-level review can tell you which, and whether that money can actually cover the overruns.
Review variance in both dollars and percentages, since 10% of a small project may matter less than 3% of a large one. Agree thresholds in advance, and treat large underruns as seriously as overruns, because money held by a project that no longer needs it is money the portfolio cannot use elsewhere.
Financial controls and project budget tracking
Controls make the numbers trustworthy when someone challenges them later. Most portfolios need at least these:
Write these into your portfolio governance, and record the decisions they produce. A decision to accept an overrun can be perfectly sound, as long as you can later show who made it and why.
Financial Reporting for PMOs and Executives
Good project portfolio financial reporting gives each audience the level of detail it needs, built on the same figures:
Run this on a monthly rhythm. When finance and the PMO see the same figures, meetings can focus on what to do about them.
How PPM Software Improves Portfolio Financial Control
Spreadsheets can handle this for a handful of projects. They tend to strain once many project managers update forecasts each month and several groups need to trust one version. PPM software should hold the plan, the forecast, and the decision trail in one place, while your ERP remains the system of financial record. Here is how that works in Completix financial management, using the same example:
This project budget illustration uses the same financial figures as this article.
Budgets and EAC
Fiscal-year budgets can be set at portfolio and line-of-business level. EAC is calculated automatically, and resource allocation changes affect forecasts.
Funding
Funding envelopes hold CAPEX and OPEX by line of business. Requests can be made at an intake gate or on a project, and a funding manager approves each draw.
CAPEX, OPEX and reporting
Budget lines carry a category and cost type. The executive dashboard splits the two by fiscal year and exports to Excel.
Control
Locking financials as of a date needs lock permission, and changes keep a history. The Warning Center surfaces variances for people to review, and decides nothing itself.
PPM software complements an ERP or financial management system. It does not replace it:
In Completix, invoice approval happens in your ERP, and open purchase orders normally stay there too. Vendor quotes and invoices sit side by side for manual matching, and someone marks a cost to count toward the budget. Where an enterprise needs data exchanged with its ERP, that is a custom integration built around its data mapping.
Before you commit to a change, scenario planning lets you model a funding shift or a date push across budget, resources, and schedule together. That is where this discipline pays off: project investment management depends on knowing what the money is doing now, so that the next funding decision rests on numbers everyone trusts.