Business Central integration

What it does

The Business Central integration couples Field Service work orders to Business Central's finance, inventory and service records through Dataverse integration table mappings. Work order products and services flow into project journal lines for posting, resources and warehouses sync both ways, and with the fuller option, service orders and work orders stay aligned as a single document in two systems.

Key facts

Two integration types: Project (the default) and Project and Service. The second is a package deal — you cannot integrate service management on its own, and turning it on also turns on the project integration.
Project and Service requires the Premium experience in Business Central, set in the User Experience field on the Company Information page. Service management features do not exist in Essential.
Prerequisites in Business Central are a Dataverse connection, Dynamics 365 Sales integration enabled, and the Field Service Integration app from Marketplace. The Business Central Virtual Table app is optional, and only needed for item availability.
Setup runs through an assisted setup guide — Set up integration to Dynamics 365 Field Service — which asks for the Project Journal Template and Batch, the Hours Unit of Measure used to convert Field Service durations into Business Central quantities, when work order products and services synchronise, and whether project journal lines post automatically.
Field Service users need the Business Central Field Service Integration security role on top of their standard roles, and an administrator has to add the appropriate column security profiles in Power Platform. Business Central users posting project journals need the Dynamics 365 Sales Integration permission set.
Three Field Service Settings changes are required: on the Purchase tab clear Use of Products Out of Stock; on the Work Order / Booking tab turn off Calculate Price and Calculate Cost, and set Work Order Invoice Creation to Never. Pricing and invoicing move to Business Central.
Project-type mappings installed are PJLINE-WORDERPRODUCT, PJLINE-WORDERSERVICE, PROJECTTASK, RESOURCE-BOOKABLERSC and LOCATIONS. The LOCATIONS mapping only appears if Location Mandatory is on in Business Central's Inventory Setup.
Project and Service adds SRVORDER, SRVORDERITEMLINE, SRVORDERLINE-ITEM, SRVORDERLINE-RESOURCE, SRVORDERLINE-SERVICE, SRVORDERTYPE and SVCITEM-CUSTASSET, and creates a Power Apps solution named Microsoft Dynamics 365 Business Central Field Service Integration (service).
Service management setup has hard requirements: Service Order Type Mandatory on, One Service Item Line/Order off, Archive Orders on, and a service order number series allowing Manual Nos. so Field Service work order numbers carry across.
Cancelled work orders are not synchronised. There's no Business Central equivalent status, and alignment is manual.
Virtual tables for item availability need Field Service and Business Central in the same tenant, and require synthetic relations built between CRM Product and FS Work Order Product and the Inventory Availability by Location virtual table.

When to use / skip

Use it where Business Central is genuinely the finance and inventory system of record and the client wants field work to post through to the general ledger without re-keying. That's a real and common shape: a mid-market service business running Business Central, buying Field Service for scheduling and mobile execution.

Skip it, or scope it down to the Project integration only, where the client bills in a way Business Central's service module doesn't match, or where they're on Essential and unwilling to move to Premium. Also think twice if the client wants Field Service to keep owning pricing — the integration expects the opposite, and fighting that produces two conflicting price sources and a monthly reconciliation exercise.

If Project Operations is also in play, stop and design the finance architecture properly. Field Service integrates with both, and running both against the same work orders is an architecture mistake rather than a configuration one.

Configuration decisions

Project only, or Project and Service — and whether the client will move to the Premium experience if the latter is wanted.
Whether work order products and services synchronise when lines are used or when the work order completes, and whether project journal lines post automatically or are reviewed first.
Which project journal template and batch receive the consumption, agreed with the finance team rather than assumed.
The Hours Unit of Measure used to convert booking durations into Business Central quantities — get this wrong and every labour posting is wrong by a constant factor.
Whether item availability from Business Central appears in Field Service, which pulls in the Virtual Table app, the same-tenant requirement, location-mandatory inventory and manually built synthetic relations.
Whether Business Central locations map to Field Service warehouses, which requires Location Mandatory and constrains how locations are set up.
How resources of type Person are matched to bookable resources — through email on the User Setup page and the Time Sheet Owner User ID on the Resource Card.

Gotchas

Turning off Calculate Price in Field Service removes the pricing fields and disables invoice generation entirely. That's intended here, but it surprises anyone who saw a Field Service demo with pricing on.
Leaving Use of Products Out of Stock set produces spurious out-of-stock warnings for products that Business Central knows are in stock.
Upgrading an existing integration can leave the RESOURCE-BOOKABLERSC mapping's Resource Type value missing User. If people-type resources aren't syncing, check that the value reads Generic|Account|Equipment|User.
Manual numbering on the service order number series is easy to overlook and blocks work-order-originated service orders outright.
Cancelled work orders leave an orphan on the Business Central side. Build a housekeeping process, because nobody notices until a period close.
Resource synchronisation filters on Business Central conditions — not blocked, no Use Time Sheet, hours as the unit of measure — so a resource that "should" sync usually fails one of those rather than the mapping.

Consultant notes

Get finance in the room for the assisted setup guide. Journal template, batch and posting timing are their decisions, and reversing them after live postings is painful.
Run a full synchronisation immediately after setup and read the synchronisation log properly. First-run failures are informative; later ones arrive as silent gaps.
Demo the round trip end to end — book, complete, consume, post, invoice — rather than the mappings.
Push back on requests to keep pricing in both systems. Pick one, and make Business Central the answer if this integration is in scope.
Before go-live, agree who owns the cancelled-work-order reconciliation and how often it runs. It's the one gap the product hands you deliberately.

Worth another look when Business Central moves to a new major version, or if the client's licensing shifts between Essential and Premium.