SPM - Budget allocation at project level and portfolio level how both works in new next experience

[MANISHAIDHA]

We are working with client to propose SPM PPM process. In that we are not able to give them understanding how exactly project and portfolio level budgeting happens.

1) Project level budget allocation - Under project workspace , we have Financials. In that Project manager will update cost plan.

Then portfolio manager will come and update budget and click on approved button .

Questions - How portfolio manager will get trigger to update budget. there is no specified flow is there, its seems all budget update and approve on one screen without any trigger point.

2) Portfolio leve budget allocation - there are Investment portal was there which is legacy one . Another is investment funding portal is there (which will also going to be legacy). But Servicenow purposing to utilize strategic workspace. But we are not able to understand how portfolio level budget will get distributed on project and demand level. There is no simplified way where we can showcase this function. As per check we can user Portfolio planning and scenario planning , there also its not straight forward. Strategic workspace is not under scope for our phase. How we can showcase portfolio level budget here. 

If any ServiceNow SPM expert can please help here. 

[Naveen20 · Accepted solution]

1. Project-Level Budget Approval — The Trigger Gap

You're right that OOTB there's no formal approval workflow or notification trigger for the portfolio manager. A budget is essentially an approved cost plan — the PM creates the cost plan, and then it gets approved to become the budget. But the "Approve" action on the Financials tab is role-gated (portfolio manager role), not workflow-driven.

Here's how to position this for your client:

The OOTB process is: PM updates cost plan → Portfolio Manager opens the same Financials tab in Budget vs. Forecast display mode → reviews variance → clicks Approve. In this mode, the Budget field is editable and available to roles such as Portfolio Manager who have access to approve budgets for work items. The funding user can enter the budget for a time period against an expense or cost type and formally approve it.

For the trigger/notification gap, the recommended approach from the community is to configure a Flow Designer flow where the PM raises a Project Change Request with the reason and amount, and on approval the budget gets updated and a financial baseline is captured. This gives you the audit trail, notification, and governance your client likely expects. You'd build a simple flow: cost plan updated beyond threshold → notification to portfolio manager → PM submits change request → approval updates budget.

2. Portfolio-Level Budget Distribution

This is where ServiceNow's roadmap has been evolving rapidly. Here's the current state:

• Investment Portal — legacy, classic UI only.
• Investment Funding — not yet compatible with the new Flexible Budget Allocation in Next Experience. ServiceNow has been working to bring this forward.
• Strategic Planning Workspace (SPW) with Scenario Planning — this is now ServiceNow's recommended path. Scenario Planning with Financials was released in the May 2025 store release (Xanadu compatible), enabling organizations to simulate investment strategies, align them with financial constraints, and maximize portfolio value within the strategic planning process.

The key capability you're looking for is: approved scenario values automatically update the approved budget on work items (projects/demands), including clearing budget from de-prioritized items, and optionally converting in-plan demands with budget approval to projects.

Since your client has Strategic Workspace out of scope for this phase, here are your practical options:

• Option A — Use Investment Funding (classic experience) for portfolio-level top-down/bottom-up allocation now, with a roadmap to migrate to SPW in a future phase. With Investment Funding you can allocate budget at portfolio, project, and demand levels, and also request additional funds following a bottom-up approach. Yes it's being sunset, but it still works and gives you a clean demo story.

• Option B — Use the new Flexible Budget Allocation at the project/demand level directly from Project Workspace (available since August 2024 store release). This lets you do granular budget entry by cost type at individual work item level, but you lose the portfolio-level "envelope" distribution view. You'd pair this with PA dashboards to show aggregated portfolio spend.

• Option C — Position SPW Scenario Planning as Phase 2 and for Phase 1, show the client the Investment Funding flow as "current state" with a clear migration path. This is what most implementation partners are doing right now given the transition period.

My recommendation for your client demo: Go with Option A (Investment Funding) for portfolio-level distribution since it's the most complete and demo-friendly flow today, combined with the new Financials display modes in Project Workspace for project-level budget tracking. Document the SPW migration as a Phase 2 item. For the approval trigger gap, propose a lightweight Flow Designer solution — it's a small config effort that adds significant governance value.

[MANISHAIDHA]

Thank you so much Naveen, it's helpful for our roadmap.