As field service operations grow more complex, so does the need for a clear connection between what’s happening on-site and what’s happening in finance. If your business runs maintenance, repairs, or service visits in the field, there’s often a disconnect between your technicians in the field and the people invoicing customers back in the office.
With the 2025 release of Business Central, Microsoft now supports integrating Dynamics 365 Field Service directly with Business Central’s Service Management functionality. The goal: make sure that every service visit, product used, or repair logged by a technician can flow cleanly into your inventory, costing, and invoicing workflows without duplication or manual effort.
Let’s break down how this works and what’s needed to make it happen.
What This Integration Solves
The main reason for enabling this integration is to track the real-time impact of service work on both inventory and customer billing. When a technician uses materials or completes services in the field, those actions need to result in financial postings and (eventually) invoices — not just internal notes.
By linking Business Central to Field Service, you allow:
- Work orders in Field Service to generate service orders in BC
- Materials marked as “used” to drive consumption in BC
- Invoice posting in BC to update the original work order in Field Service
- Inventory availability in BC to reflect demand created by work orders
This kind of integration is key if you want one version of the truth — and to reduce manual re-entry between service and finance.
Requirements to Use This Integration
This is not available in all editions of Business Central. You’ll need:
- A Premium license for Business Central (because Service Management is a premium-only feature)
- Your company settings in BC set to use the “Premium” experience
- An active instance of Dynamics 365 Field Service
Once you have that in place, integration becomes a matter of setup and alignment.
Enabling the Integration
There are a couple of ways to set it up — either using the built-in assisted setup or going directly to the integration settings page. In both cases, you’ll need to choose the type of integration you want:
- Project: connects Field Service to the Jobs module
- Service: connects Field Service to Service Management (what we’re focused on here)
- Both: if your company uses both jobs and service features
Choosing “Service” or “Both” unlocks several new connections behind the scenes.
What Gets Linked Between the Systems
When the integration is active, Business Central will start syncing with Field Service in specific ways. These include:
- Work order details like customer and billing account
- Products and services used in the field
- Customer assets or items being serviced
- Quantities for shipment, consumption, and invoicing
Once a technician marks a line item as “used” in Field Service, that usage is passed into a service order line in Business Central. When the service order is posted in BC, the invoice is generated, inventory is updated, and that same work order in Field Service is updated with what was invoiced or consumed.
Inventory Availability and Planning
There’s also an optional setting that allows Field Service demand to influence inventory availability in Business Central. If enabled, any reserved materials in a work order are considered part of gross requirements in BC. This helps the planning engine recognize demand created in the field and adjust replenishment accordingly.
Key Considerations
A few things to keep in mind:
- Service Order Type in Business Central becomes a required field once this integration is enabled. This aligns with the required Work Order Type in Field Service.
- Only COGS and invoicing logic native to BC is used. If you have unique service costing or third-party integrations, you may need to customize.
- Inventory planning will improve with this setup, but only if your product and location mapping between systems is clean.
Final Thoughts
This integration brings much-needed alignment between service operations and finance. If your team currently tracks field work in one tool and billing in another — with manual steps in between — this feature could save hours per week and reduce errors dramatically.
It’s especially useful for service-based organizations that already run on the Microsoft stack and want to centralize their operations. Once enabled, Field Service becomes more than a technician tool — it becomes part of your company’s financial backbone.
If you’re exploring how this fits your environment or what steps are required, feel free to reach out or drop a comment.
Dynamics Decoded 
Leave a comment