Business Central field service: connecting technicians to the back office

The two routes to Business Central field service

The first route stays inside the ERP. With Premium licenses, service orders, service items and contracts live in Business Central. Technicians open their orders in the mobile app. It is easy to run. You have no second system to buy or keep in step.

The second route adds Dynamics 365 Field Service. This separate Microsoft application is built for scheduling and mobile work. It offers a schedule board and a technician app that works offline. It also manages assets and work orders. Microsoft provides an integration, so Business Central stays the home of items, customers, inventory and invoices.

How to decide which Business Central field service route fits

Ask how dispatch happens today. Suppose a coordinator assigns a handful of jobs each morning, and technicians mostly have a signal. Then the built-in module is usually enough. However, you may balance many technicians across territories. You may reshuffle all day and work in remote sites. Then a scheduling product earns its place.

Licensing matters too. Dynamics 365 Field Service has its own license, per user. We set out both routes side by side with the license types involved. Then we point you to Microsoft's site for prices. So you compare on facts.

How the Business Central field service integration works

The integration runs through Dataverse, the data platform under Dynamics 365 apps. An assisted setup guide in Business Central connects the two. Integration table mappings decide which records are shared. Customers, items and resources stay in step. So a technician picks real parts with real numbers.

You can link work orders in Field Service to a project task in Business Central. Products and services the technician records as used arrive as project journal lines. You can post them to use up inventory and capture cost. Then Business Central raises the invoice. That keeps receivables and tax in one ledger.

What we set up for Business Central field service

For the built-in route, we configure service management and the mobile pages technicians use. For the connected route, we set up the Dataverse connection and run the assisted setup. We adjust the table mappings to your data. We also agree which system owns each field, so edits do not fight each other.

Either way, we test full scenarios in a sandbox. A call comes in. A job is scheduled. Parts are used. The customer is invoiced, and the cost shows on the right account. You receive a data ownership map and a list of synchronization jobs. You also get monitoring steps and guides for dispatchers and technicians.

What tends to go wrong with field service integration

Sync problems nearly always trace back to data. Duplicate customers cause trouble. So do items without a unit of measure mapping, and resources missing in one system. Records then fail with no warning. We clean master data first. Then we switch on sync in stages and watch the error list after each stage.

Inventory is the other risk. Technicians carry stock in vans. If van locations are not modeled in Business Central, usage posts against the wrong place, and counts drift. So we set up locations for vehicles where needed. We agree how replenishment transfers work. We also make sure parts used in the field reduce the correct stock.

Business Central field service: questions buyers ask

Is Dynamics 365 Field Service part of Business Central?

No. It is a separate Dynamics 365 application with its own license. Business Central includes a service management module in Premium. Microsoft supplies an integration that lets the two applications share customers, items and resources. It also passes work order usage back for invoicing.

Do we need Dataverse for the integration?

Yes. Field Service stores its data in Dataverse. Business Central connects to Dataverse through its standard integration framework. Setting up that connection is the first step. It also opens the door to Power Apps and Power Automate.

Where is the customer invoiced?

In Business Central. Usage recorded on a work order moves over as project journal lines. You post them and then invoice through the normal project and sales invoicing process. That keeps customer balances, sales tax and revenue in the ERP, where your accountants expect them.

Can technicians work without a signal?

The Dynamics 365 Field Service mobile app is designed to work offline. It synchronizes when a connection returns. The Business Central mobile app needs a connection. If your technicians often work out of coverage, that difference usually settles the choice of route.

Can we start with the built-in module and add Field Service later?

Many companies do. Starting inside Business Central builds clean equipment, customer and parts data. Any later scheduling tool will need that data. When the team outgrows the module, we plan the move. Open orders and contracts carry across in order.

Pages that go with field work

Field work draws on the service module, Dataverse and project posting. If you are weighing the two routes for Business Central field service, these pages add detail. Read them, then tell us how your technicians are dispatched today and whether they work out of signal. We will suggest which route to try first. For the product detail, see Business Central documentation on Microsoft Learn.