Field Service's link to Finance ends in February 2027: plan the move to Project Operations
Field Service's built-in link to Finance, and the old Data Integrator templates, stop after February 28, 2027. The replacement goes through Project Operations and there's no migration path, so treat it as a rebuild and book a cutover window now.
part 11 of 12 · Running enterprise platforms wellthe ideaField work still reaches Finance. It just goes through Project Operations now
after reading, you can- Work out which Field Service to Finance link you actually run. It decides how big the move is
- Pick a Project Operations setup that fits the licences you already pay for. Whether Finance is in the mix decides who owns stock
- Plan a cutover that doesn't leave work orders unbilled at month end
Microsoft is retiring the built-in link between Dynamics 365 Field Service and its finance and operations apps. After February 28, 2027 it won't be available, and there's no upgrade button to the replacement. If work orders post to Finance or Supply Chain Management today, plan the move to the Field Service and Project Operations integration now and book the cutover before the end of February.
The bridge that turns field work into invoices and stock movements is being replaced
Field Service is where your technicians get their jobs, log the parts they used and record their hours. Finance and Supply Chain Management are where that work becomes cost, stock and an invoice. Today a Microsoft integration carries each used part and each hour from the work order into journals in Finance. Microsoft is retiring that integration, and an older set of Data Integrator templates that did a similar job, on the same date. The replacement sends the same work through Dynamics 365 Project Operations first. Every work order hangs off a project, and Project Operations turns the field data into actuals and invoices.
Think of a builder's site office that has phoned the day's materials straight through to the accounts team for years. The firm is closing that phone line. From now on every job sheet goes to a project manager's desk first, gets checked against the job's budget, and only then reaches accounts. The work on site is the same. The route to the money changes, and someone has to set up the new desk.
- Field Service teams posting to Finance or SCM
- Anyone still on the Data Integrator templates
- Finance teams who invoice field work
- Dynamics admins and partners
Why it matters to you
When this link stops, technicians can still close jobs. What stops is the money side. Used parts don't reduce stock in Supply Chain Management, hours don't land as project cost, and billing waits until someone keys the work in by hand. Month-end close is usually where it shows first.
The part people miss is a single line in the limitations on Microsoft's known-issues page for the new integration: it doesn't support migration from the legacy one. So this is a reimplementation with a fixed end date. You uninstall the old integration, install the new one, link work orders to projects and test the postings again.
Microsoft has already closed the door behind it. Since Field Service 8.8.139.398 the Install Finance and Operations toggle doesn't appear in environments that never had the integration. Environments that already run it can keep it until the deadline.
-
01 Work order done
A technician marks the parts and services on the job as Used, and logs time against it.
-
02 Old route
The legacy integration wrote item, expense and hours journals straight onto a project in Finance through dual-write.
-
03 Retires 28 Feb
Microsoft switches that route off at the end of February 2027, along with the old Data Integrator templates. Nothing posts through it after that.
-
04 Project Operations
Now each work order links to a project. Used lines become Material Usage Logs, then journal lines, then approved actuals.
-
05 Finance posts
Approved actuals cross to Finance as integration journal lines. Finance posts the ledger entries and the customer invoice.
For the engineers: the new flow runs on Material Usage Logs. When a work order product or service is set to Used, the system prices and costs it, in Field Service by default or from Project OperationsdefinitionThe Dynamics 365 app that runs project money. Each work order now hangs off a project in it, and that's where cost and revenue get worked out. price lists if you change the setting, and writes a log. That log becomes project journal lines, approval turns them into actualsdefinitionThe approved cost and revenue records on a project. They're what feeds invoices and, with Finance connected, the ledger., and actuals feed proforma invoices. With Finance connected, Project Operations Integration journal lines carry the approved amounts across, and Finance handles subledger, revenue recognition and the posted invoice.
What's going away and what replaces it
The two old integrations and the new one
The dual-write integration that wrote work order transactions into project journals in Finance. Gone after February 28, 2027.
Older setups use these to sync work orders, agreements, stock and projects between Field Service and Supply Chain Management. They stop on the same day, whether you're in the cloud or on-premises.
From Field Service 8.8.139.398 you can't switch the old integration on in an environment that never had it.
Work orders link to projects or project tasks. Field data flows to Project Operations as estimates, usage and actuals, and on to Finance if you connect it.
Technicians' time now goes to Project Operations too, from package 2.1.3488.3. Someone approves it there before it turns into cost.
Two dashboards show work order lines stuck before a usage log, an approval or an actual, plus failed background jobs.
The dual-writedefinitionThe sync Microsoft uses to keep Finance and Dataverse, the database under Field Service, in step. The old integration sat on top of it. integration is the one most Finance customers set up. It made Supply Chain Management the system of record for stock and hid Field Service's own inventory screens. It also built a main project in Finance with a subproject per work order. None of that structure carries over. The new model puts Project Operations in the middle as the financial container.
The Data Integrator templatesdefinitionPrebuilt sync jobs, like Work orders to Sales orders, that some older setups still run. They stop on the same day. are older still. One of them, Work orders to Sales orders, turned work orders into sales orders in Supply Chain Management. If you're on that, the jump is bigger, because the new world bills through projects rather than sales orders. Expect to rethink the billing process along with the plumbing.
| Topic | Legacy F&O integration | Project Operations integration |
|---|---|---|
| Available until | 28 February 2027 | Current, generally available since 30 January 2026 |
| Route to Finance | Dual-write straight into project journals | Project Operations actuals, then integration journals |
| Where work orders sit financially | Main project with a subproject per work order | A project or project task you link the work order to |
| Fees | Fee journals didn't align to Field Service | Fees aren't transferred from Field Service |
| Discounts | Not covered in Microsoft's article | Discount percentages only. Amounts convert, with possible rounding |
| Time from technicians | Hours journals from work order services | Time entries priced and approved in Project Operations |
| Licence note | Not covered in Microsoft's article | The installing user needs a Project Operations licence |
| Version floor | Field Service 8.8.124.20, Finance 10.0.39 builds or later | Field Service 8.8.142.0, Project Operations 4.162.0.0 |
How we got here
- 1 Dec 2025Retirement notice
The end date shows up on the Field Service deprecations page. Anyone who read it had fifteen months' notice.
- 30 Jan 2026Replacement goes GA
The Project Operations route goes GA. If you started a rollout after this, you probably never touched the old link.
- 30 Apr 2026Package 1.1.3384.2
Better traceability from actuals back to work orders, and clearer inventory screens when Finance owns stock.
- 20 Jul 2026Package 2.1.3488.3
Work orders can now hang off a single project task. Technician time flows across as well.
- 28 Feb 2027Old integrations end
Both old routes stop. Anything still relying on them stops posting to Finance.
Your options, side by side
Microsoft's replacement comes in three shapes, depending on which apps you license. Pick the shape before anyone installs anything, because it decides who owns stock and where invoices come from.
| Apps you run | What you get | Who owns stock and invoicing |
|---|---|---|
| Field Service, Project Operations, Finance and Supply Chain Management | The full chain from work order to project to posted invoice | Finance owns stock and accounting. Field Service inventory is switched off |
| Field Service, Finance and Supply Chain Management, no Project Operations users | A small set of Project Operations forms inside Field Service. The installing user needs a Project Operations licence | Finance, through the integrated model |
| Field Service and Project Operations, no Finance | Project Operations Core handles project financials and invoicing. Microsoft says this can feed other ERPs | Field Service stays the system of record for stock |
- Nobody checks which integration is actually installed
- Fees vanish and discount amounts turn into percentages after cutover. Finance finds out at close
- The old integration is uninstalled with failed transactions still in its log
- Whoever clicked Install owns the flow, and nobody wrote that down
- The integration swaps in its own offline profiles. Technicians find out on the job
- Find out which integration you actually run. Then choose where you're going
- Pull a list of fees, which won't carry over, and discount amounts, which get converted. Agreements tied to tasks go on it too
- Fix or resync failed legacy transactions first. Nobody wants to chase them after uninstall
- Install with an account your team owns, licensed for Project Operations and Power Automate
- Test the offline profiles on real devices in a sandbox first
There's a fourth path: build your own integration and keep it. Some teams with heavy customisation will look at it. It means owning every mapping and every Field Service and Finance update yourself, so price that support honestly before you choose it over Microsoft's supported route.
| Factor | Why it matters |
|---|---|
| Which old integration you run | Data Integrator users are moving from sales orders to projects, which is a process change, not only a configuration one |
| Fees and discount amounts | Fees don't transfer, and discount amounts are converted to percentages with possible rounding. Both need checking in pricing or in Project Operations |
| Number of legal entities | Work orders only sync when the service account's company matches the lines, same as before |
| Mobile offline customisations | The integration installs its own offline profiles, which override the out-of-the-box ones |
| Custom fields on work orders | Microsoft says the new integration supports schema extensibility, but each custom field still needs mapping and testing |
Check what you have before you plan
A half-day inventory of your environment
- 01Find the integration
In Field Service Settings, open the Features tab. If Finance and Operations Integration is on, you're on the legacy dual-write integration.
- 02Look for Data Integrator projects
Ask whoever set up the environment about Data Integration projects that use Field Service templates, such as Work orders to Sales orders.
- 03Check versions
Note the Field Service and Project Operations versions in each environment. The replacement needs 8.8.142.0 and 4.162.0.0 or later.
- 04Count what won't carry over
Pull work order lines that use fees or discount amounts, and agreements tied to project tasks. Those need a new design.
- 05Read the transaction log
In Field Service, go to the Settings area and open finance and operations transactions. Fix or resync anything failed or unsynchronized before cutover.
- 06Name the owners
Write down who owns the integration in Field Service, in Project Operations and in Finance. You'll need all three in the same room.
What to do now, by role
Who does what before 28 February 2027
- Ask IT one question: does Field Service work post to Finance today? If yes, this is yours.
- Pick the cutover window: after a period close, well before February 28.
- Approve the Project Operations licence for the installing account and any project managers who need it.
- Confirm which legacy integration is installed and record versions in every environment.
- Build the new integration in a sandbox: dual-write map versions, stocked products, the ProjInventOnHandEntity virtual entity, then the package.
- Check the recurring cloud flow is on and owned by a team account.
- Settle where prices and costs come from before you test. Field Service sets them unless you switch it to Project Operations.
- Make a call on auto-approval. Leave it off and someone has to review every Material Usage Log.
- Redesign the charges that relied on fees, and check how discount amounts look once they become percentages.
- Test the integration's offline profiles on technicians' devices before go-live.
- Create bookable resources for everyone who edits work order lines, with Company set when Finance is connected.
- Train dispatchers to link each work order to the right project or task. A job with no project has nowhere to post.
Make the new setup last
The new integration adds moving parts the old one didn't have. A Power Automate flow runs every minute to process work order revision lines, and it runs under the user who installed the package. Approvals sit between field usage and the ledger. Each is a place where postings can quietly stall, so give each one an owner and a check.
Before: the legacy integration
Field Service writes straight into Finance project journals through dual-write.
After: Field Service and Project Operations
Project Operations sits in the middle. Finance receives approved actuals.
Durable fixes, each tied to this change
- 01Install with a team account
The package's flow runs as the installing user, who also needs a Project Operations licence. Use a named service or team account your admins own, so the flow doesn't hang on one person.
- 02Watch the dashboards weekly
Work Order Products and Work Order Services monitoring dashboards show lines missing a usage log, an approval or an actual. Someone should clear them before month end.
- 03Keep company alignment strict
Lines won't sync while the service account's company doesn't match. Build incident types per company and don't mix companies on one work order.
- 04Lock down approvals
If you don't auto-approve, give the project approval role to a small group. Approved actuals are what reach the ledger.
- 05Test every Field Service update
Run a work order through to a posted actual in a sandbox after each Field Service, Project Operations or Finance update. It's quicker than chasing a stuck close.
If it goes wrong
When work orders stop reaching Finance after the cutover
Most problems show up as lines that never become actuals. The dashboards tell you where each one stopped, so start there before you change any settings.
- 01Find where it stoppedfirst hour
- Open the two monitoring dashboards first. A stuck line only shows up in the stage where it first went wrong.
- Check the revision line flow is on. If changes don't produce estimates or actuals, Microsoft points there first.
- 02Fix the common causesfirst day
- Company mismatch between the service account and the lines: correct the record, then let it resync.
- Stocked products won't approve? Microsoft's fix is to set Background Approval Threshold above zero in Project Operations parameters, then approve again.
- 03Protect the closefirst day
- List work orders completed since cutover with no actuals. Those are the ones finance will miss.
- Hold invoices for those jobs until actuals exist, rather than keying them twice by hand.
- 04Decide on rollbackfirst week
- Don't count on reinstalling the legacy integration. Since 8.8.139.398 its install toggle only shows where it's already installed, so plan to fix forward.
- Write down which settings changed and when, so the second attempt doesn't repeat the first.
- 05Learn from itthis month
- Put a test work order on the checklist for every update. Run it all the way to a posted actual.
- Review who owns the flow, the approvals and the dashboards, and fix any gaps.
What this looks like in practice
The companies below are made up. Each is a setup you could find in a Field Service estate today, so use them to check your own.
Three estates you might recognise
- the setup
- A building services company runs Field Service with Finance and Supply Chain Management. Parts come out of SCM warehouses, and a call-out fee goes on most work orders.
- what happens
- Their plan is a quick swap in February. The sandbox test shows the call-out fees never arrive in Project Operations, since the new integration doesn't move fees.
- what to do
- Find every fee and discount amount now, redesign them in pricing, and cut over after the January close.
- the setup
- A manufacturer still uses the Data Integrator template that turns work orders into sales orders in Supply Chain Management. Service billing has run that way for years.
- what happens
- The template stops on February 28. Billing in the new setup runs through projects, so their sales-order process has nothing to map onto.
- what to do
- Treat it as a billing redesign. Decide how service work maps to projects and contracts, then build the integration on that design.
- the setup
- A utility contractor is starting Field Service this year alongside Finance. Its partner looks for the Install Finance and Operations toggle and can't find it.
- what happens
- That's expected on Field Service 8.8.139.398 and later. There's nothing to migrate, which is the easy case.
- what to do
- Skip the old link entirely and set up the Project Operations integration. Pick the deployment model first, and install it with a licensed team account.
How Cohash helps
We check which integration your environment runs, list what won't carry over, and rehearse the cutover in a sandbox until a work order posts cleanly to Finance. Then we run the real cutover in your window. The Dynamics 365 page covers our wider CRM and Field Service work, and the Finance and Operations page covers the ERP side. You can bring in Dynamics engineers for the build, or start with an assessment if you'd like a second opinion on scope first.
What to take from this
- 01
Both old routes from Field Service to Finance stop after February 28, 2027. Check which one you run.
- 02
The replacement runs through Project Operations, and Microsoft doesn't support migrating from the old integration.
- 03
You uninstall the legacy integration first, so book the cutover right after a period close.
- 04
Fees don't transfer, discount amounts become percentages, and agreements can't link to tasks. Find them before you test.
- 05
Install with a team-owned account licensed for Project Operations and Power Automate, and watch the monitoring dashboards.
01When does Field Service stop posting to Finance the old way?
The old link goes after February 28, 2027, and so do the Data Integrator templates. Microsoft wants you on the Field Service and Project Operations integration by then.
02Can we just migrate the old integration?
Not directly. Microsoft's known-issues page says the new integration doesn't support migration from the legacy one. You uninstall the old integration, set up the new one and link work orders to projects.
03Do we need Project Operations licences for everyone?
Not necessarily. Microsoft says the user who installs the integration needs a Project Operations licence, and so does anyone managing project tasks in Project Operations. The flow it installs also needs Power Automate licensing.
04Will technicians notice anything?
Mostly no. They keep working in Field Service. Watch two things: the integration installs its own mobile offline profiles, which override the standard ones, and work orders now need to be linked to a project.
05Which system owns inventory after the move?
It depends on the model. With Finance connected, Finance is the system of record and Field Service inventory management is switched off. With Project Operations Core and no Finance, Field Service keeps owning stock.
06What doesn't carry over to the new integration?
Fees don't transfer, and estimated discounts aren't supported. Agreements can't link to project tasks either. Discount amounts get converted to percentages, so expect small rounding differences.
07What happens to our open legacy transactions?
Microsoft doesn't describe a handover, so don't leave any. Before you uninstall, fix or resync anything failed in the finance and operations transactions log, and cut over right after a period close.
Three questions, about a minute
Pick an answer and we'll tell you if it's right, and why it is or isn't. The score stays in this browser.
-
Q1Your environment runs the legacy Field Service integration with Finance. What's the supported way to the new one?
show the answer
C. Uninstall the legacy integration, then set up the Project Operations integration Microsoft's known-issues page says migration from the legacy integration isn't supported, and the setup page lists uninstalling it as a prerequisite. So it's a fresh setup with a planned cutover.
-
Q2Your work orders carry a call-out fee. What happens to it in the new integration?
show the answer
B. It isn't transferred from Field Service Microsoft lists fee synchronization from Field Service to Project Operations as unsupported, even though Project Operations has fees. Plan a different way to charge them.
-
Q3A partner can't find the Install Finance and Operations toggle in a brand-new environment. Why?
show the answer
C. Since Field Service 8.8.139.398 it only shows where the integration is already installed Microsoft hid the toggle for environments that never had the integration. New rollouts go straight to the Project Operations integration.