At a glance

  • Microsoft’s original integration between Dynamics 365 Field Service and its finance apps won’t be available after Feb 28, 2027.
  • The replacement runs through Dynamics 365 Project Operations and adds review steps between the finished job and the posted invoice.
  • Microsoft’s setup guide says to uninstall the old integration first, so the move is a one-way cutover.
  • Leaders who budget it this year choose the billing rules and the cutover date themselves.

If your technicians’ hours and parts reach Dynamics 365 Finance through Microsoft’s original Field Service integration, that connection has an end date. Microsoft Learn states it won’t be available after February 28, 2027. The capability moves to the Field Service and Project Operations integration.

Five months is enough time to do this well, once.

The deadline is a finance question first

The old link is how a closed work order turns into cost, inventory, and revenue.

Each part used on a job creates an item journal line on a project in Finance. Each service hour creates an hours journal line. Supply Chain Management is the system of record for inventory.

When the link stops, field work stops reaching the ledger on its own. The work gets done, and the invoice waits. Your CFO sees that as unbilled work at month-end.

The group affected is closed, too. Since Field Service release 8.8.139.398, environments that don’t already run the old integration can’t install it. Everyone still on it has the same deadline.

The replacement changes how work becomes an invoice

In the new model, every work order links to a project in Project Operations, which Microsoft describes as the financial container. When a technician marks a part or service as used, the system records it as a material usage log.

From there the path has more stops. Usage logs become project journal lines, which someone reviews and approves.

Approved lines become project actuals. Actuals produce draft proforma invoices, which are reviewed and confirmed.

With Finance connected, Finance then posts the customer invoice and recognizes the revenue. Technician time follows Project Operations pricing and approval rules.

Microsoft made this Field Service and Project Operations connection generally available at the end of January 2026. On Sept 23, 2026, it added work orders created from, or linked to, project tasks, also generally available.

Two settings in the new model are billing policy

Who approves field usage. Microsoft’s setup offers an auto-approve option.

Turn it on, and usage from the field becomes actuals without review. Turn it off, and someone in finance approves each batch before it can be billed.

One choice favors speed to invoice; the other favors control.

Where price and cost come from. By default, price comes from the price list on the work order and cost from the work order itself. You can switch both to the project contract’s sales price list and the cost price list.

That decides which team owns a price change.

Your CFO and your VP of Service should make these two calls together, in writing, before anyone configures them.

Start with a list of what the old link does today

What we call the integration inventory is a list of everything the old link does for you today, including what your team built around it. It’s the first document to write, because the workarounds are what break at cutover.

Microsoft’s own page lists the old link’s limits, and each one hints at a workaround worth finding.

Fee journals don’t align to Field Service transactions. Discount fields on work order lines don’t sync.

Inventory reservations and batch or serial tracking dimensions aren’t supported. If your team solved any of these with a custom step, a report, or a manual journal, write it down.

Add the legal entities on the link, the reports that read its journals, and who fixes a failed sync today. That list becomes your test plan.

Put three items in this year’s budget

Licenses, checked early. The person who installs the new package needs at least one Project Operations license. The package runs a recurring Power Automate flow under that user, which must be licensed too.

Check the rest of your users against Microsoft’s licensing guide before you commit a date.

A test on your real work. Replay a closed month of work orders, parts, hours, and invoices through the new path in a sandbox. Compare the result with what Finance posted.

Demo data won’t show you the workaround you forgot.

Time for the people whose day changes. Project accountants and billing staff gain a review step they didn’t have. Technicians may notice changes too, because the package installs mobile offline profiles that override the standard ones.

Schedule the cutover around your month-end close

Feb 28, 2027 is a month-end. If your February close runs into the first days of March, the old link is gone halfway through it. Plan to run the new path in a sandbox against real data, then cut over after a clean month-end, well before the last week of February.

During the parallel month, reconcile the two paths line by line. The controller signs off on the switch.

For your IT team: the facts to plan against

The new integration needs Field Service version 8.8.142.0 or later and Project Operations version 4.162.0.0 or later. To connect Finance, configure dual-write with the Project Operations maps and enable one Dataverse virtual entity for on-hand inventory.

Microsoft supports three shapes. The full one runs Field Service, Project Operations, Finance, and Supply Chain Management. A lighter one runs Field Service with Finance and Supply Chain Management, using Project Operations forms embedded in Field Service. The third runs Field Service with Project Operations and no Microsoft finance app.

Some service businesses face a different decision

This deadline applies only to Microsoft’s own integration. If Field Service reaches your ledger through a partner product or a custom build, check with its owner; your date may be different.

If Field Service feeds a finance system other than Dynamics 365, the third shape, with no Microsoft finance app, may be your route, with your own link repointed. And the old link never covered legal entities that use Project Operations’ own resource and non-stocked integration. Those entities bill another way today, so map them separately.

What finance and service leaders should do this quarter

Confirm whether you’re on the old link. If you don’t know yet, ask IT one question: does the Finance and Operations integration appear in Field Service settings? The answer sets your plan.

Write the integration inventory before the new design. List what the link does, what your team built around it, and who fixes it when it fails.

Decide the two billing policies together. Approval of field usage and the source of price and cost belong to the CFO and the VP of Service.

Budget the test, the licenses, and the training this fiscal year. A parallel month on real work is the cheapest insurance you can buy here.

Pick a cutover date after a clean close. Don’t let Feb 28 choose it for you.

How we know this

This guide comes from Ludia’s Field Service and Finance delivery and Microsoft’s published documentation, checked Sept 29, 2026. Retirement date, the release that closed new installs, how the old link posts journals, and its limits: Microsoft Learn, Field Service integration with finance and operations applications (updated Sept 2026). How the new path turns work into invoices, and the three supported shapes: Microsoft Learn, Field Service integration with Project Operations overview. Versions, licensing notes, uninstalling the old link, approval and pricing settings, and mobile profiles: Microsoft Learn, Set up Field Service integration with Project Operations. General availability at the end of January 2026: Microsoft Dynamics 365 blog, Managing complex service work with financial clarity (June 2, 2026). Work orders from project tasks: Microsoft Dynamics 365 blog, Build the future of agentic ERP (Sept 23, 2026). Microsoft updates these pages continuously, so check them again before you set dates.