EngineeringDynamics 365

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.

Cohash Enterprise Platforms Practice November 2026 13 min read 9 chapters 3-question check
part 11 of 12 · Running enterprise platforms well
01 Field Service 02 Legacy F&Olink retiring 03 28 Feb 2027 04 ProjectOperations

the 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.

in plain wordsDeadline: 28 February 2027

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 it like this

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.

who should care
  • 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
chapter 01

Why it matters to you

28 Feb 2027Last day for the old Field Service integration with finance and operations
2 integrationsThe dual-write integration and the Data Integrator templates both end then
No migrationMicrosoft says the new integration doesn't support migrating from the old one
8.8.142.0Minimum Field Service version for the replacement

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.

what changesSame work in the field, a new route to the ledgerTechnicians keep working in Field Service. What changes is the path a used part or an hour takes to reach Finance.
  1. 01 Work order done

    A technician marks the parts and services on the job as Used, and logs time against it.

  2. 02 Old route

    The legacy integration wrote item, expense and hours journals straight onto a project in Finance through dual-write.

  3. 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.

  4. 04 Project Operations

    Now each work order links to a project. Used lines become Material Usage Logs, then journal lines, then approved actuals.

  5. 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.

chapter 02

What's going away and what replaces it

The two old integrations and the new one

removedThe dual-write integration

The dual-write integration that wrote work order transactions into project journals in Finance. Gone after February 28, 2027.

removedData Integrator templates

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.

deprecatedInstall toggle hidden

From Field Service 8.8.139.398 you can't switch the old integration on in an environment that never had it.

newField Service and Project Operations integration

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.

newTime entries flow to projects

Technicians' time now goes to Project Operations too, from package 2.1.3488.3. Someone approves it there before it turns into cost.

enhancedMonitoring dashboards

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.

tableOld against new, line by line. Most surprises sit in the fees and discounts rows
TopicLegacy F&O integrationProject Operations integration
Available until28 February 2027Current, generally available since 30 January 2026
Route to FinanceDual-write straight into project journalsProject Operations actuals, then integration journals
Where work orders sit financiallyMain project with a subproject per work orderA project or project task you link the work order to
FeesFee journals didn't align to Field ServiceFees aren't transferred from Field Service
DiscountsNot covered in Microsoft's articleDiscount percentages only. Amounts convert, with possible rounding
Time from techniciansHours journals from work order servicesTime entries priced and approved in Project Operations
Licence noteNot covered in Microsoft's articleThe installing user needs a Project Operations licence
Version floorField Service 8.8.124.20, Finance 10.0.39 builds or laterField Service 8.8.142.0, Project Operations 4.162.0.0

How we got here

  1. 1 Dec 2025
    Retirement notice

    The end date shows up on the Field Service deprecations page. Anyone who read it had fifteen months' notice.

  2. 30 Jan 2026
    Replacement goes GA

    The Project Operations route goes GA. If you started a rollout after this, you probably never touched the old link.

  3. 30 Apr 2026
    Package 1.1.3384.2

    Better traceability from actuals back to work orders, and clearer inventory screens when Finance owns stock.

  4. 20 Jul 2026
    Package 2.1.3488.3

    Work orders can now hang off a single project task. Technician time flows across as well.

  5. 28 Feb 2027
    Old integrations end

    Both old routes stop. Anything still relying on them stops posting to Finance.

chapter 03

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.

tablePick your setup by the apps you already license. Whether Finance is in the mix decides who owns stock
Apps you runWhat you getWho owns stock and invoicing
Field Service, Project Operations, Finance and Supply Chain ManagementThe full chain from work order to project to posted invoiceFinance owns stock and accounting. Field Service inventory is switched off
Field Service, Finance and Supply Chain Management, no Project Operations usersA small set of Project Operations forms inside Field Service. The installing user needs a Project Operations licenceFinance, through the integrated model
Field Service and Project Operations, no FinanceProject Operations Core handles project financials and invoicing. Microsoft says this can feed other ERPsField Service stays the system of record for stock
side by sideTwo ways to reach the same deadline
Wait for February
  • 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
Plan it this quarter
  • 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.

tableWhat usually decides the effort
FactorWhy it matters
Which old integration you runData Integrator users are moving from sales orders to projects, which is a process change, not only a configuration one
Fees and discount amountsFees 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 entitiesWork orders only sync when the service account's company matches the lines, same as before
Mobile offline customisationsThe integration installs its own offline profiles, which override the out-of-the-box ones
Custom fields on work ordersMicrosoft says the new integration supports schema extensibility, but each custom field still needs mapping and testing
chapter 04

Check what you have before you plan

A half-day inventory of your environment

  1. 01
    Find 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.

  2. 02
    Look 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.

  3. 03
    Check 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.

  4. 04
    Count 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.

  5. 05
    Read 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.

  6. 06
    Name 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.

chapter 05

What to do now, by role

Who does what before 28 February 2027

Business owner or CFOthis week
  • 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.
Dynamics admin or partnerthis month
  • 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.
Finance and project accountingthis month
  • 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.
Field service operationsthis quarter
  • 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.
chapter 06

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

Before: the legacy integration

Field Service writes straight into Finance project journals through dual-write.

Before: the legacy integration Field Service writes straight into Finance project journals through dual-write. 01 · FIELD SERVICE 02 · INTEGRATION 03 · FINANCE AND SCM used lines journals on project stock levels Work order products and services F&O transactions log sync status Dual-write core and extended maps Virtual tables inventory on hand Main project subproject per work order Item, expense, hoursjournals posted in Finance © Cohash · cohash.com
01 · FIELD SERVICE02 · INTEGRATION03 · FINANCE AND SCM Work order: products and services Work order products andservices F&O transactions log: sync status F&Otransactionslog sync status Dual-write: core and extended maps Dual-write core and extendedmaps Virtual tables: inventory on hand Virtual tables inventory on hand Main project: subproject per work order Main project subproject perwork order Item, expense, hours journals: posted in Finance Item, expense,hours journals posted in Finance used lines journals stock levels © Cohash · cohash.com
after

After: Field Service and Project Operations

Project Operations sits in the middle. Finance receives approved actuals.

After: Field Service and Project Operations Project Operations sits in the middle. Finance receives approved actuals. 01 · FIELD SERVICE 02 · PROJECT OPERATIONS 03 · FINANCE AND SCM revisions usage approval transfer post Work order linked to project or task Revision line flow runs every minute Material Usage Logs then journal lines Approved actuals and proforma invoices Integration journals Project Operations toFinance Ledger and invoice stock owned by Finance © Cohash · cohash.com
01 · FIELD SERVICE02 · PROJECT OPERATIONS03 · FINANCE AND SCM Work order: linked to project or task Work order linked to projector task Revision line flow: runs every minute Revision lineflow runs every minute Material Usage Logs: then journal lines Material UsageLogs then journal lines Approved actuals: and proforma invoices Approvedactuals and proformainvoices Integration journals: Project Operations to Finance Integrationjournals Project Operationsto Finance Ledger and invoice: stock owned by Finance Ledger andinvoice stock owned byFinance usage transfer © Cohash · cohash.com

Durable fixes, each tied to this change

  1. 01
    Install 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.

  2. 02
    Watch 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.

  3. 03
    Keep 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.

  4. 04
    Lock down approvals

    If you don't auto-approve, give the project approval role to a small group. Approved actuals are what reach the ledger.

  5. 05
    Test 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.

chapter 07

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
chapter 08

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

01 Work order 02 Call-out fee 03 New pricing 04 Actuals post
scenario 01High risk
A services firm on the dual-write integration
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.
01 Work order 02 Sales ordertemplate 03 Project andcontract 04 Invoice
scenario 02High risk
An equipment maker on the old templates
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.
01 Newenvironment 02 Togglemissing 03 ProjectOperations 04 Finance
scenario 03Low risk
A new rollout that never had the old link
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.
chapter 09

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.

key takeaways

What to take from this

  1. 01

    Both old routes from Field Service to Finance stop after February 28, 2027. Check which one you run.

  2. 02

    The replacement runs through Project Operations, and Microsoft doesn't support migrating from the old integration.

  3. 03

    You uninstall the legacy integration first, so book the cutover right after a period close.

  4. 04

    Fees don't transfer, discount amounts become percentages, and agreements can't link to tasks. Find them before you test.

  5. 05

    Install with a team-owned account licensed for Project Operations and Power Automate, and watch the monitoring dashboards.

fact-checked November 2026 against vendor and official documentation · where to go next
  1. How Cohash delivers Microsoft Dynamics 365: scope, roles and architecture
  2. How Cohash delivers Dynamics 365 Finance & Operations: scope, roles and architecture
  3. Hire vetted Microsoft Dynamics 365 engineers
  4. Dynamics 365
  5. Book a 30-minute working session with a senior engineer
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.

next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it