Dynamics 365 Project Operations, Explained for SMEs
Dynamics 365 Project Operations is Microsoft's application for project-based organizations, unifying sales, resourcing, delivery, and finance in one system. This guide covers what it does, how it is priced at $135 per user/month, how it handles project planning, resource management, time and expense, proforma and customer invoicing, and work in process (WIP), and how to decide whether it fits your SME versus the lighter Business Central Projects module.
What Dynamics 365 Project Operations actually is
Dynamics 365 Project Operations is the application Microsoft built specifically for project-based organizations, such as consulting, professional services, and any business that sells, staffs, delivers, and bills work as projects. Microsoft's product overview describes it as bringing sales, resourcing, project management, and finance teams together in a single application, and it evolved from the earlier Dynamics 365 Project Service Automation (PSA), which reached end of life in March 2025 (Microsoft, Project Operations product page; Microsoft Learn, PSA overview).
The reason it exists as a separate application, rather than as a module inside Business Central, is depth. Project Operations adds specialized capabilities that a general ERP does not ship with: project-based sales management with multidimensional pricing, Universal Resource Scheduling that is shared with Dynamics 365 Field Service, Microsoft Project for the Web as the planning engine, subcontracting with three-way match invoicing, and flexible proforma and customer-facing invoicing. Where Business Central Projects is project accounting bolted to an ERP ledger, Project Operations is a full front-to-back project business application (Microsoft Learn, Universal Resource Scheduling overview).
It is sold as part of the Dynamics 365 family, runs on Microsoft Dataverse, and in its Integrated deployment connects to Dynamics 365 Finance for full GL accounting, revenue recognition, and WIP. Flectic implements it alongside Business Central and Odoo, and we are explicit about which platform is the right fit for a given SME, because the wrong choice here is expensive. For the lighter project-accounting path, see our Business Central Jobs & Projects guide.
Dynamics 365 Project Operations pricing
Project Operations is licensed at $135.00 per user per month, paid yearly, with a free trial available, according to the official Microsoft pricing page. That base license covers the front-office project lifecycle end to end: deal management, work planning, resourcing, project execution, subcontracting, and billing and proforma features (Microsoft, Project Operations pricing page).
Specifically, the base license covers deal management (multiple contract types, lead-to-contract, CPQ for services), work planning (scheduling, Gantt and Kanban, estimates and budgets, templates), resourcing (skills management, requests, booking reconciliations, workforce planning), project execution (time, expense, and material usage, mobile apps, policies and rules, budget tracking and earned value), subcontracting (capacity planning, vendor onboarding, goods and services delivery, three-way match invoicing), and billing and proforma features (unbilled and billed backlog, not-to-exceed limits, invoice review, edits, and adjustments).
The budget line item that catches SMEs off guard is AI. Microsoft markets agents for time, expense, and approvals on the product page, and the pricing page confirms those agents run on a pay-as-you-go plan using Copilot Credits. Copilot Credits are sold pay-as-you-go or via prepaid Commit Units, require an Azure subscription, and are not included in the base Project Operations license. Plan for that cost separately, because the agent features are marketed prominently but metered independently (Microsoft, Project Operations pricing page).
| License / add-on | List price | What it covers |
|---|---|---|
| Project Operations (per user) | $135/user/month, billed yearly | Deal management, work planning, resourcing, execution, subcontracting, billing and proforma; free trial available |
| Copilot Credits (AI agents) | Pay-as-you-go or prepaid Commit Units | Agents for time, expense, and approvals, plus custom Copilot Studio agents; Azure subscription required |
| Attached Dynamics 365 Finance (Integrated deployment) | Priced separately | Customer-facing invoicing, revenue recognition, WIP accounting, expense management with OCR; required for full financial close |
| Project Operations Core (lite, with Finance) | Bundled entitlement scenario | Front-office only: opportunity through proforma invoicing, suited to use with a third-party ERP |
Project planning with Microsoft Project for the Web
Project planning in Project Operations uses Microsoft Project for the Web as its scheduling engine. Work is decomposed through work breakdown structures (WBS) that break a project into tasks, and each task carries scheduling detail: predecessors, effort estimates, and dependencies. The same structure supports Gantt and Kanban views, plus estimates and budgets that roll up to the project level, and reusable project templates.
Cost estimation is multidimensional. The WBS captures estimated cost and revenue across labor, materials, expenses, and fees, so a project manager can model a fixed-price engagement, a time-and-materials engagement, or a mixed contract on the same planning surface. This is a meaningful step up from generic task lists, because the estimates flow directly into resourcing, billing, and earned-value tracking without re-keying.
For SMEs already in the Microsoft ecosystem, the Project for the Web foundation is a practical advantage: the planning surface is familiar to anyone who has used Microsoft Project, and it shares a data model with the rest of Project Operations, so a change to a task propagates to resource assignments, cost estimates, and the billing backlog without integration work.
Resource management and Universal Resource Scheduling
Resource management in Project Operations covers skills management, resource requests, bookings and assignments, booking reconciliations, workforce planning, and utilization insights. The underlying engine is Universal Resource Scheduling (URS), the same scheduling platform that Dynamics 365 Field Service uses, which means a project-based business that also runs field work can schedule on one system instead of two (Microsoft Learn, Universal Resource Scheduling overview).
Booking fulfillment runs in either Central mode, where a resource manager fulfills requests from a central team, or Hybrid mode, where project managers hold some booking authority. The choice matters for governance: Central mode concentrates control with resourcing and is typical for larger professional-services teams; Hybrid mode distributes booking decisions and suits smaller, flatter teams. Either way, booking reconciliations keep assignments aligned with confirmed bookings so utilization reporting stays accurate.
Workforce planning extends this to capacity: it surfaces resource demands against available capacity over a horizon, so a services director can see where the firm is over- or under-sold months ahead, not just this week. For an SME where a few unbilled consultants materially affect margin, that forward view is often the highest-ROI part of the license.
Time, expense, and material usage
Project execution captures time, expense, and material usage against the project and task structure from the WBS. Time entries carry the project, task, role, and billing type; expenses carry categories, receipt capture, and policy validation; material usage records consumables and billable items as they are applied. Mobile apps let consultants and field staff enter time and expenses from the job, with offline support for areas without coverage.
Policies and rules validate entries before they hit actuals: approvers, cost limits, not-to-exceed checks, and required fields are enforced at submission. Budget tracking and earned-value reporting pull from the same actuals, so a delivery lead sees utilization, cost-to-complete, and margin in one view rather than reconciling spreadsheets. This is the operational layer that the BC Jobs module approximates with journal lines; Project Operations makes it the system of record.
For SMEs considering where AI cost lands, this is also where the Copilot agents sit. The time, expense, and approvals agents run on Copilot Credits and are designed to reduce the manual overhead of chasing submissions, grouping expenses, and routing approvals, which is the part of professional-services delivery that consumes the most non-billable time.
Proforma invoicing, customer invoicing, and WIP
Invoicing in Project Operations splits cleanly into proforma and customer-facing invoicing. Proforma invoices are the operational documents a project manager or engagement owner reviews before anything hits the ledger: they pull from billed and unbilled backlog, respect not-to-exceed limits, and support review, edits, and adjustments. Customer-facing invoicing is the financial document posted to the ERP for revenue recognition.
In the Lite and default deployments, Project Operations handles proforma invoicing and the customer invoice is produced by a connected ERP, which is why the deployment choice drives finance scope. In the Integrated deployment with Dynamics 365 Finance, the same data flows through to the GL, accounts receivable, revenue recognition, and WIP accounting without re-keying (Microsoft, Project Operations pricing page).
WIP, or work in process, is the accounting for costs incurred on a project before they are invoiced or recognized as revenue. For fixed-price engagements, WIP methods determine how cost is capitalized and recognized as the project completes; for time-and-materials work, WIP tracks unbilled effort. SMEs running project accounting inside Business Central should compare the WIP methods carefully, because BC Jobs and Project Operations handle WIP at different depths, and the right answer depends on contract mix and revenue-recognition requirements. See our Business Central Jobs & Projects guide for the BC side of that comparison.
Deployment types: Lite, default, and Integrated
Microsoft offers Project Operations in deployment types that determine financial depth, and the choice is structural, not cosmetic. The Lite deployment (Project Operations Core) handles opportunity through proforma invoicing on Dataverse and is suited to organizations that run a third-party ERP for finance. The default deployment covers the front-office lifecycle including subcontracting and three-way match invoicing. The Integrated deployment connects to Dynamics 365 Finance for full GL, revenue recognition, and WIP (Microsoft, Project Operations product page).
Why the split exists: a project-based business that already runs Sage, NetSuite, or another ERP for finance may want Project Operations for delivery and resourcing without ripping out the GL, and the Lite deployment exists for that case. A business that wants a single Microsoft stack uses the Integrated deployment with Finance, because dual-write keeps the two systems in sync without custom integration.
For an SME, the practical implication is that the $135/user/month license is not the whole cost picture. The Lite deployment keeps finance in a separate system; the Integrated deployment adds Finance licensing on top. That is the conversation to have before a license commitment, not after, and it is why a platform-neutral scoping across Dynamics 365 and Odoo matters for project-based SMEs.
Project Operations vs Business Central Projects: which SMEs need which
The most common scoping question for project-based SMEs is whether to run Dynamics 365 Project Operations or the Business Central Projects module (formerly Jobs). The honest answer is that they serve different depths of project work, and the decision rests on contract complexity, resourcing sophistication, and whether finance and delivery need to be one system.
Business Central Projects is the right fit when projects are primarily an accounting exercise: you need job ledger lines, WIP methods, job planning lines, and invoicing tied to the BC general ledger, and your resourcing is light. It is included with the BC license an SME likely already holds, which keeps cost predictable. Project Operations is the right fit when delivery itself is the business: multidimensional pricing, Universal Resource Scheduling, earned-value tracking, subcontracting, and proforma-to-customer invoicing across complex contract types.
A useful proxy: if the person buying the system is the head of delivery or a services director, Project Operations is usually in scope. If the buyer is the CFO or controller and projects are a finance workflow, BC Projects is usually enough. Flectic scopes both Dynamics 365 and Odoo for project-based SMEs across Canada, the UK, and the US, and we will tell you plainly when BC Projects, Odoo, or a third-party tool is the better fit than Project Operations.
| Dimension | Project Operations | Business Central Projects |
|---|---|---|
| Primary buyer | Services / delivery leader | CFO / controller |
| Depth | Full front-to-back project business application | Project accounting module in the BC ERP |
| Scheduling engine | Universal Resource Scheduling (shared with Field Service) | Job planning lines, no URS |
| Invoicing | Proforma plus customer-facing; multidimensional pricing | Job invoicing and WIP tied to BC GL |
| Finance scope | Lite (third-party ERP), default, or Integrated with Finance | Native to BC ledger |
| Typical SME fit | Consulting, professional services, mixed contract types | Lighter project accounting, single-ERP SMEs |
Frequently asked questions
How much does Dynamics 365 Project Operations cost per user?
Dynamics 365 Project Operations is $135 per user per month, billed yearly, with a free trial, according to the official Microsoft pricing page. AI agents for time, expense, and approvals run on Copilot Credits, which are metered separately and require an Azure subscription, so they are not included in the base license.
Is Dynamics 365 Project Operations the same as the Business Central Projects module?
No. Business Central Projects (formerly Jobs) is a project-accounting module inside the BC ERP, tied to the BC general ledger. Project Operations is a standalone application for project-based organizations, with Universal Resource Scheduling, multidimensional pricing, subcontracting, and proforma-to-customer invoicing. BC Projects suits lighter project accounting; Project Operations suits services-led businesses with complex contracts.
What replaced Dynamics 365 Project Service Automation (PSA)?
Dynamics 365 Project Service Automation evolved into Dynamics 365 Project Operations. PSA reached end of support on October 1, 2024 and end of life in March 2025, and existing PSA customers migrate to Project Operations, which runs on Microsoft Dataverse and adds finance integration through Dynamics 365 Finance in its Integrated deployment.
Do Project Operations Copilot agents require Copilot Credits?
Yes. Microsoft markets agents for time, expense, and approvals on the Project Operations product page, and the pricing page confirms those agents run on a pay-as-you-go plan using Copilot Credits. Copilot Credits are billed through an Azure subscription either pay-as-you-go or as prepaid Commit Units, and are separate from the $135 per user per month base license.
Which deployment of Project Operations should an SME choose?
It depends on finance scope. The Lite deployment (Project Operations Core) handles opportunity through proforma invoicing and suits SMEs running a separate third-party ERP for finance. The Integrated deployment connects to Dynamics 365 Finance for full GL, revenue recognition, and WIP. A platform-neutral scoping across Dynamics 365 and Odoo before commitment is the cheapest way to get this decision right.
Does Flectic implement Project Operations for SMEs?
Flectic implements Dynamics 365 Project Operations alongside Business Central and Odoo for project-based SMEs across Canada, the UK, and the US. We are explicit about when BC Projects, Odoo, or Project Operations is the right fit, and we use AI-assisted delivery to scope and implement faster. Book an ERP Readiness Call for a platform-neutral recommendation.
Book an ERP Readiness Call
Get a platform-neutral scoping across Dynamics 365 Project Operations, Business Central Projects, and Odoo from a partner that implements all three. We will map your contract mix, resourcing depth, and finance scope to the right deployment and license mix, flag the Copilot Credits and Finance attach costs up front, and lay out a phased rollout plan designed to deliver up to 3x faster. 30 minutes, SME-focused, remote-first across Canada, the UK, and the US.
Sources
- Dynamics 365 Project Operations is licensed at $135 per user per month, paid yearly, with a free trial; AI agents run on a pay-as-you-go plan using Copilot Credits that require an Azure subscription. — https://www.microsoft.com/en-us/dynamics-365/products/project-operations/pricing (verified high)
- Project Operations brings sales, resourcing, project management, and finance together in a single application; agents simplify project spend for time, expense, and approvals; deployment types include Lite and Integrated with Finance. — https://www.microsoft.com/en-us/dynamics-365/products/project-operations (verified high)
- Dynamics 365 Project Service Automation evolved into Dynamics 365 Project Operations; PSA reached end of life in March 2025. — https://learn.microsoft.com/en-us/dynamics365/project-operations/psa/overview (verified high)
- Universal Resource Scheduling is the Dynamics 365 scheduling solution shared across Project Operations and Field Service, using common concepts of organizational units, roles, skills, and resources. — https://learn.microsoft.com/en-us/dynamics365/common-scheduler/schedule-anything-with-universal-resource-scheduling (verified high)
- The Expense Agent (preview) groups related expense lines into reports by project or trip and auto-generates expense reports in Project Operations. — https://learn.microsoft.com/en-us/dynamics365/project-operations/expense/expense-agent-overview (verified high)
- Project Operations 2025 release wave 1 introduced Copilot capabilities and agent-led time, expense, and approvals features, with deployment types spanning Lite, default, and Finance-integrated scenarios. — https://learn.microsoft.com/en-us/dynamics365/release-plan/2025wave1/finance-supply-chain/dynamics365-project-operations/planned-features (verified high)