- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
3 weeks ago
Hey ServiceNow Community,
Managing project financials can get complicated quickly, especially when you are trying to balance the needs of project managers tracking everyday costs with portfolio managers who need to oversee high-level targets.
In my latest video walkthrough, I break down exactly how funding works at the foundational level in ServiceNow Strategic Portfolio Management (SPM). Specifically, we look at the bottom-level budget approval process on a Demand or Project level and how those numbers automatically roll up to the broader Portfolio.
Here is a breakdown of the core mechanics and key takeaways from the configuration walkthrough.
1. Building the Foundation: Cost Plans (CapEx vs. OpEx)
The financial lifecycle starts directly on the Demand record. Before any budget can be allocated, you have to build out your expected expenses using Cost Plans.
-
Flexible Cost Types: Out of the box, ServiceNow provides IT-centric cost types like hardware and software, but the platform allows you to configure any cost type your enterprise requires.
-
Multi-Currency & Unit Costs: Cost plans can be built in any currency, applying specific unit costs based on the resources you are utilizing.
-
The Fiscal Period Factor: Budgets are intrinsically tied to time. Understanding and setting up your enterprise's specific fiscal periods is foundational to ensure costs map correctly across the financial roadmap.
2. Tracking the Value: Monetary Benefit Plans
An architected financial solution doesn't just track what you spend; it tracks what you get back. By creating Monetary Benefit Plans directly on the Demand, you give business leaders a clear financial picture of the projected return on investment (ROI).
Both your planned costs and your benefit plans automatically roll up directly to the Portfolio level view.
3. The Portfolio Manager's Lens: Workbench & Approvals
When logged in as a Portfolio Manager (like Megan in our demo scenario), you don't have to hunt through individual records to make decisions.
-
The Demand Workbench: Using the quadrant view in the Demand Workbench, a portfolio manager can visually assess financial benefits versus risk to prioritize intake.
-
The Demand Budget Form: Once a demand is deemed viable, entering the correct fiscal year populates the right-hand side of the form, allowing the manager to officially approve and allocate the CapEx and OpEx budgets.
-
Execution vs. Approval: A key takeaway here is that having an approved budget is completely separate from being selected for execution. This allows organizations with multiple demands to approve funds but strategically prioritize what actually goes live first.
High-Level Portfolio Target Alignment
At the top of the chain, the Portfolio Manager sets a hard Portfolio Target budget. As demands are approved and their costs roll upward, the system automatically calculates your total planned costs against that target. This gives you real-time visibility into whether your portfolio is on track or moving toward over-allocation.
Check out the full step-by-step system walkthrough below to see these rollups and form behaviors in action!
Watch the complete demo here: ServiceNow SPM Financials Demo: Demand-Level Budget Approval & Portfolio Rollup
What does your organizational governance look like? Do you handle funding from the bottom-up like this, or do you prefer a top-down allocation model? Let's discuss in the comments!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi @Bill Martin Thank you for writing the above article on SPM Financials. It is very informative covering the financials process in detail.
While it correctly talks about the process, I have observed that you are covering the financials capability in classic demands and projects which are soon to be deprecated.
I recommend reviewing the new SPM Financials with flexible budget approval and granular portfolio rollups. You can get started with the following page - https://www.servicenow.com/community/spm-articles/quick-start-guide-for-financial-planning/ta-p/2959...
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi @Vinay3,
thanks for the great callout, and you're absolutely right. The walkthrough intentionally covers the classic demand/project financials flow because that's what most of the customers we work with are running today, but I should have flagged the direction of travel.
For anyone reading: the new SPM Financials experience (flexible budget approval and granular portfolio rollups) has been available since the August 2024 release and enhanced through subsequent releases, so it's the recommended path going forward.
One practical note for existing customers, since many are intentionally on N-1: the new experience is already available on Yokohama and Zurich, so most can start exploring it today without waiting for an upgrade. The classic capability is "being prepared for future deprecation" but remains supported.
On that point, do you happen to know if there is a hard end-of-support / deprecation date for the classic demand and project financials? I'd love to give existing customers an exact timeline so they can plan their migration proactively.
I'll also add a follow-up article mapping the classic flow shown here to its equivalent in the new Financials experience.
Thanks for the link, I'll point readers to it.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi @Bill Martin classic financials follows the same timeline as deprecation for the classic project workspace which is in Phase 2 of its deprecation lifecycle as of Australia release.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thanks @Vinay3,
Two clarifications:
1. What does "Phase 2" mean in practice - hidden/not installable for new instances but still supported for existing ones?
2. Is there a target release or date for final end-of-support? Many are on N-1 and need an exact milestone to plan migration.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi @Bill Its the final phase. After Australia release, the application is now treated as custom code. ServiceNow Technical Support is no longer obligated to provide bug fixes, security patches, or assistance for issues originating within it. Access to the application, existing resource plans and financials, and upgrades to new Now Platform releases all continue. What stops is new development, enhancements, bug fixes, and technical support.
You can review this article to learn more - https://www.servicenow.com/community/spm-articles/project-workbench-support-changes-from-the-austral...
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
In summary:
This article covers the classic demand/project financials flow.
As @Vinay3 noted, that capability is moving to the new financials experience (flexible budget approval and granular portfolio rollups).
- From the Australia release, classic financials and Project Workbench are treated as custom code.
- ServiceNow no longer provides bug fixes, security patches, or technical support for them.
- Existing projects, data, and financials remain in your instance, and platform upgrades continue.
- This applies whether or not you upgrade to Australia, so staying on N-1 does not preserve support.
- The recommended path is to migrate to the new Project Workspace. No new license is required.
Thanks @Vinay3 for the clarification and links.