Business Central for Facility Management: What It Does and Where It Stops

There is a recurring conversation I have with facility-management leaders, and it usually starts the same way. The finance team has chosen Microsoft Dynamics 365 Business Central as the company's ERP, someone has seen the demo, and now the question lands on the FM side of the house: since we are paying for Business Central anyway, can we just run maintenance and operations out of it too? It is a fair question, and the answer is more useful than a simple yes or no. Business Central is genuinely excellent at a large part of what an FM business does. It is also, by design, not a computer-aided facility management or maintenance management system, and pretending otherwise leads to painful implementations and frustrated engineers. My job here is to draw that line precisely, from the perspective of someone who spends his working life on both sides of it.

The message up front: Business Central is an ERP, and a very good one. It runs the money, the contracts, the procurement and the fixed-asset ledger of a facility-management business with real strength. What it does not do, and was never built to do, is run the day-to-day operational spine of facilities: work orders, planned preventive maintenance, asset condition, SLA-driven reactive jobs and mobile field execution. For that you pair Business Central with a dedicated CAFM or CMMS. The winning architecture is not one system doing everything, it is two systems each doing what they are best at, joined cleanly at the seam.

1. What facility management actually needs from its systems

Before judging whether any product fits facility management, you have to be honest about what facility management actually is, because it spans two very different kinds of work. There is the business of running an FM company or department, which is finance, commercial and administrative, and there is the operational reality of keeping buildings and assets working, which is engineering and field execution. A good systems landscape has to serve both, and most arguments about Business Central go wrong because people only picture one half.

On the operational side, facility management needs to handle a large and continuous flow of work. A helpdesk or portal takes in reactive requests, a broken air handling unit, a blocked drain, a lift out of service, and those requests have to become work orders with priorities, response and resolution targets, assigned engineers, parts, and a closure record. Alongside that reactive flow sits planned preventive maintenance, the scheduled inspections and servicing that keep assets healthy and keep the operation compliant with statutory obligations. Underneath both sits the asset register: every piece of plant and equipment, its location in a building hierarchy, its maintenance history, its condition and its criticality. And increasingly the engineer doing the work is on a phone or tablet in a plant room, not at a desk, so mobile execution is not a nice-to-have, it is the core interface.

On the business side, facility management needs everything any service company needs. It has to invoice clients, often against complex contracts with monthly service charges plus variable additional works. It has to buy materials and subcontracted services, control cost against budget, pay suppliers, run payroll and account for the whole thing to a standard an auditor will accept. It has to manage its own fixed assets and depreciation. And it has to report, both to internal management and to clients who want to see that they are getting what they pay for.

The mistake is treating these as one problem. They are two problems that meet at specific, well-defined points: when operational work generates cost, consumes stock or becomes billable to a client. Understanding where those meeting points are is the whole key to designing the systems landscape correctly, and it is the lens I will use for the rest of this guide.

2. What Business Central does well for an FM business

Let me give Business Central full credit before I describe its limits, because the credit is genuinely deserved. As the financial and commercial engine of a facility-management business, Business Central is a strong, mature, well-supported platform, and for a growing FM company outgrowing entry-level accounting software it is a natural fit. Here is where it earns its place.

• Finance and the general ledger: this is Business Central's heart. A proper double-entry general ledger, multi-dimensional analysis so you can slice cost and revenue by contract, site, department or cost centre, budgeting, bank reconciliation and a full audit trail. For an FM business that needs to know profitability per contract rather than just overall, the dimensions capability alone is worth a great deal.
• Procurement and purchasing: purchase requisitions, purchase orders, approval workflows, goods receipt, vendor management and three-way matching of order, receipt and invoice. Facility management buys a constant stream of materials and subcontracted services, and Business Central handles that procurement cycle properly, with the controls a finance team expects.
• Accounts payable and receivable: supplier invoice processing and payment runs on one side, client invoicing and credit control on the other. This is bread-and-butter ERP and Business Central does it well.
• Contracts and recurring billing: FM revenue is heavily contract-based, and Business Central can model recurring service charges, escalations and scheduled billing, so the predictable monthly invoicing runs cleanly.
• Projects and jobs: the project management, or jobs, module lets you track a defined piece of work, a fit-out, a major additional works package, a mobilisation, against a budget, capturing labour, materials and costs and comparing planned to actual. For the larger, discrete pieces of FM work this is a genuinely useful tool.
• Fixed assets: a complete fixed-asset register with acquisition, depreciation across multiple books, revaluation and disposal. For the accounting treatment of the company's own capital assets this is exactly what you want.

Add to that inventory and warehouse management for the stores function, Power BI integration for reporting, and a place in the wider Microsoft 365 and Power Platform ecosystem, and you have a serious commercial backbone. If your question is purely whether Business Central can run the finance, procurement, billing and accounting of a facility-management business, the answer is an unqualified yes, and it will do it well. If you are still weighing that broader ERP decision itself, I have written separately on whether Business Central is right for your organization.

3. The gap: BC is an ERP, not a CAFM or CMMS

Here is where I have to be direct, because it is the single point most vendors and enthusiastic implementers gloss over. Business Central is an enterprise resource planning system. Its worldview is transactions, ledgers, documents and financial value. A CAFM (computer-aided facility management) or CMMS (computerised maintenance management system) has a fundamentally different worldview: assets, their condition over time, maintenance tasks, and the field workflow that keeps them running. These are not the same problem with different labels. They are different problems that happen to touch at the point where operational work becomes cost.

Think about what a CMMS is optimised for that an ERP is not. It carries a deep asset hierarchy, a site containing buildings containing floors containing rooms containing systems containing individual assets, each with its own maintenance history and condition. It generates and schedules planned preventive maintenance from asset attributes and calendars, spinning up thousands of recurring work orders automatically. It applies failure codes and captures downtime so reliability can be analysed. It runs an SLA engine that measures response and resolution against contractual targets and escalates when they are at risk. It puts a stripped-down, offline-capable interface in the hand of an engineer standing in a plant room. Business Central does none of these as native, purpose-built functions, because it was never meant to.

The honest limitation: you can absolutely bend Business Central to hold a list of assets and even to raise something you call a work order using the service or jobs modules. What you cannot easily do is replicate the operational depth of a real CAFM: the PPM scheduling engine, the asset condition and criticality model, the SLA clock, the mobile-first field experience and the reliability analytics. Every team I have seen try to force full FM operations into Business Central ends up building an expensive, brittle custom layer that a purpose-built CAFM would have delivered out of the box, and their engineers quietly go back to spreadsheets.

None of this is a criticism of Business Central. A screwdriver is not a poor hammer, it is simply not a hammer. The error is in the expectation, not the product. Once you accept that Business Central is the financial and commercial system and a CAFM or CMMS is the operational system, the whole design becomes clear and both tools get to be excellent at what they are for.

4. Work orders, PPM and asset maintenance: why FM needs a dedicated tool

Let me go deeper on the operational functions specifically, because this is where the daily reality of facility management lives and where the gap matters most. If you strip everything else away, the operational job of facility management is to manage work against assets, reactively and preventively, and to do it at volume, on time, and with a record you can trust. A dedicated CAFM or CMMS is built around exactly this, and the differences from an ERP are not cosmetic.

The work order is a different object. In a CMMS a work order is a living operational record: it carries a priority, an SLA target with a running clock, an assigned engineer or team, the asset it relates to, the fault and failure codes, the parts requested and consumed, labour time, before-and-after notes and photos, and a closure and sign-off. It moves through operational states that engineers and supervisors understand. In Business Central the nearest equivalents, service orders or job tasks, are built around commercial and financial tracking, not this operational lifecycle, and they lack the priority, SLA and field-execution machinery that make a maintenance work order actually usable at the front line.

Planned preventive maintenance is an engine, not a calendar. A real CAFM generates PPM automatically from asset data: apply a maintenance regime to an asset class and the system produces the recurring work orders, on the right frequency, with the right task lists and safety requirements, across thousands of assets, and it reforecasts as assets are added, moved or retired. It also drives statutory and compliance inspections, which in facility management are not optional. Business Central has recurring documents and can schedule jobs, but it has no native PPM generation engine tied to an asset hierarchy and maintenance regimes. Building one inside it is a large custom development that never quite matches a product designed for the job.

Assets carry condition and criticality, not just cost. The CMMS asset record is about reliability: condition, criticality ranking, maintenance history, mean time between failures, warranty status and the failure analysis that drives maintenance strategy. The Business Central fixed-asset record is about the balance sheet: cost, depreciation and net book value. Both are legitimate views of the same physical asset, but they answer different questions, and the operational questions are the ones an engineer and a maintenance manager ask every day.

Field execution is the primary interface. In modern FM the engineer works from a mobile device, often offline in a basement plant room or a remote site, scanning an asset QR code, seeing its history, completing a checklist, recording parts and closing the job on the spot. Purpose-built CAFM and CMMS products lead with this experience. It is not something you replicate convincingly inside a general-purpose ERP client. I have written more specifically on this operational integration in the Business Central and CMMS integration guide and on the asset side in Business Central for asset management.

Put simply, the operational spine of facility management is high-volume, real-time, asset-centric and field-first, and that is precisely the shape of a CAFM or CMMS and precisely not the shape of an ERP. This is the strongest single reason facility management keeps a dedicated operational tool even when Business Central is already in place.

5. The right architecture: Business Central plus a CAFM/CMMS

Once you accept the division of labour, the target architecture almost designs itself. Business Central is the system of record for finance, procurement, contracts and the fixed-asset ledger. The CAFM or CMMS is the system of record for assets, work orders, PPM and field operations. They are connected by a deliberate integration at the small number of points where operational events have financial or commercial consequences. Neither tries to be the other, and each one stays the authoritative source for the data it owns.

In practice the integration seam carries a manageable set of flows. Material and stock consumption on a work order in the CMMS needs to hit inventory and cost in Business Central. Subcontractor and additional-works cost captured against a job flows through to accounts payable and to the client billing that Business Central produces. Purchase requests raised operationally against a work order become purchase orders in the ERP procurement cycle. Completed billable works flow from the operational system into the invoicing engine. And the master data that both systems share, sites, cost centres, suppliers, has one authoritative source that the other consumes, so you never maintain two divergent copies by hand.

The design principle that keeps this clean: each data domain has exactly one owner. Business Central owns the financial truth. The CAFM owns the operational truth. The integration moves facts across the boundary, it does not create a second version of them. The moment two systems both claim to own assets, or both claim to own cost, you get reconciliation pain forever. One owner per domain, a clean seam between them, and disciplined master-data governance is what separates an FM systems landscape that works from one that generates monthly arguments between finance and operations.

The connection itself is not exotic. Business Central exposes a modern web API and works naturally with the Power Platform, and most established CAFM and CMMS products have integration capabilities of their own, so the flows above are built with standard interfaces rather than fragile custom hacks. The engineering is real but well understood. I have laid out the full pattern, the data flows, the sequencing and the pitfalls, in the CAFM and Business Central integration guide, which is the companion piece to this article and the place to go when you move from deciding the architecture to building it.

6. Managing FM contracts, billing and cost control in Business Central

Contract and revenue management is one of the areas where Business Central genuinely shines for facility management, so it deserves its own section. Facility-management revenue is characteristically a blend of predictable and variable. There is the base contract, a monthly or quarterly service charge for the agreed scope, and there are the extras: additional works, projects, call-outs and consumables outside the base scope. A good FM finance system has to bill both cleanly and show profitability per contract, and this is squarely in Business Central's strength.

For the recurring element, Business Central models scheduled and recurring billing, so the base service charge invoices automatically on the agreed cycle, with escalations applied when a contract's annual uplift falls due. For the variable element, the jobs and projects module captures the cost and revenue of a specific piece of additional work, and when that work is billable it flows to a sales invoice. Crucially, the dimensions capability lets you tag every transaction, cost and revenue alike, to a contract, a site and a cost centre, so at any moment you can see the margin on each contract rather than just the overall company result. For an FM business where one contract can be quietly loss-making while the portfolio looks healthy, that visibility is worth a great deal.

Cost control follows the same logic. Every purchase order, subcontractor invoice, stock issue and labour cost that carries the right dimension code rolls up against the contract or project it belongs to, and against its budget. Business Central's budgeting and the comparison of actual to committed to budgeted spend is exactly the discipline an FM operation needs to stop cost leaking away on a fixed-price contract. Where the operational detail lives in the CAFM, the work order that consumed the parts, the engineer hours on the job, the integration carries the financial consequence across so the ERP holds the complete cost picture without anyone rekeying it.

The nuance worth stating: Business Central gives you the commercial and financial view of the contract, the money in and the money out, extremely well. What it does not give you is the operational service view, whether you actually met the SLAs the contract promised, how many reactive jobs breached, what the PPM completion rate was. That service-performance picture lives in the CAFM and feeds your client reporting and your KPI framework. The two views together tell the full story of a contract; either one alone tells half of it. For the operational half, see the facility management KPI framework.

7. Fixed assets in BC versus physical asset and maintenance management

This is the section where the two worldviews collide most visibly, and getting it straight prevents a great deal of confusion. Both Business Central and a CMMS talk about assets, but they mean genuinely different things, and once you see the distinction you stop expecting either one to do the other's job.

Business Central's fixed-asset module is a financial construct. An asset there is a capitalised item on the balance sheet with an acquisition cost, one or more depreciation books, a net book value, a location for accounting purposes, and a disposal record. It answers accounting and tax questions: what is this asset worth on the books today, what depreciation posts this period, what is the gain or loss on disposal. It is precise, auditable and exactly right for the finance function. I have covered its detail separately in Business Central fixed assets management.

A CMMS or CAFM asset is an operational and engineering construct. The same chiller that is one line on the fixed-asset ledger is, in the maintenance system, a node in a location hierarchy with a full maintenance history, a PPM regime, a criticality ranking, condition readings, failure codes, warranty tracking and a running record of every work order ever raised against it. It answers reliability questions: how often does this fail, what does it cost to maintain, is it approaching end of life, does its criticality justify a condition-monitoring program. These are questions the finance ledger cannot answer and was never meant to.

The two even count differently. Finance often capitalises at a level that suits depreciation, one HVAC system, while operations tracks maintenance at a far more granular level, each individual air handling unit, pump and control valve within that system. A single fixed asset in Business Central can correspond to dozens of maintainable assets in the CAFM. Trying to force one register to serve both purposes either starves finance of the granularity operations needs, or drowns finance in operational detail it does not want. The clean answer is two registers, each at its natural level of detail, linked where a physical asset needs to be traceable across both, with the CAFM as the authoritative source for the physical and maintenance view and Business Central authoritative for the financial view.

8. Reporting across finance and operations

Reporting is where the two-system architecture proves its worth, and also where it demands a little discipline. Facility-management leaders and their clients want answers that cut across both worlds. What did this contract cost us and did we hit the SLAs. What is our PPM completion rate and what did the reactive backlog cost. Which assets consume the most maintenance spend and are approaching replacement. None of those questions can be answered from finance data alone or from operational data alone. They need both, joined up.

Each system reports superbly within its own domain. Business Central, through Power BI and its financial reporting, gives you contract profitability, budget variance, aged receivables and the full commercial picture. The CAFM gives you SLA performance, PPM compliance, work-order throughput, backlog, and asset reliability. The powerful reporting, and the reporting that FM clients increasingly expect, comes from combining the two: overlaying maintenance cost from the ERP onto asset reliability from the CAFM, or setting SLA achievement from operations next to contract margin from finance.

Because Business Central sits inside the Microsoft data ecosystem and most CAFM products expose their data through APIs or a database, the practical approach is to bring both into a common analytics layer, typically Power BI or a small data warehouse, where the shared keys, contract, site, cost centre, asset, let you join operational and financial facts into a single view. This is exactly why the master-data governance I stressed earlier matters so much: if a site or a cost centre is coded consistently in both systems, cross-domain reporting is straightforward, and if it is not, you spend your life reconciling instead of analysing. Consistent shared keys are the unglamorous foundation that makes joined-up FM reporting possible.

The honest caution here is not to try to make one system the single reporting tool for everything. Business Central is not the place to build operational maintenance dashboards, and the CAFM is not the place to build financial statements. Let each report its own domain natively, and build the cross-domain view in an analytics layer above both. That keeps each system doing what it is good at and gives leadership the combined picture without forcing either tool out of its lane.

9. Best-fit: which FM businesses run well on this model

The Business-Central-plus-CAFM model is not equally right for everyone, and part of being honest is saying where it fits well and where it might be overkill. The shape and scale of the FM operation decide how much of this architecture you actually need.

Where the full two-system model fits best. A mid-sized to large FM service provider, or a substantial in-house FM department, managing multiple contracts or sites, a real asset base, statutory maintenance obligations, and a field workforce, is the natural home for this architecture. These operations have the transaction volume and financial complexity to justify Business Central as the ERP, and the operational volume, asset count and SLA pressure to require a dedicated CAFM. For them, trying to run everything from one system fails in both directions, and the clean split with a good integration is clearly the right answer. If they are also running Business Central for the finance function already, adding a CAFM and integrating it is the highest-return move available.

Where it can be lighter. A small FM business with a handful of contracts, a modest asset base and a small team may find that Business Central plus a lightweight or even spreadsheet-based operational process is enough at their stage, and a full CAFM would be more than they can absorb. The judgement is about operational volume and complexity, not company size in the abstract. When the number of assets, the PPM load and the SLA obligations are low, the operational gap in Business Central is small enough to manage around. As those grow, the gap widens and the case for a dedicated tool becomes compelling.

Where Business Central alone is a poor fit. An asset-heavy, compliance-heavy operation, think a large campus, a hospital estate, an industrial facility or a multi-site portfolio with thousands of maintainable assets and hard statutory obligations, will struggle badly if it tries to run operations from Business Central. The PPM volume alone overwhelms an ERP's model, and the compliance exposure of missing statutory inspections is too serious to manage in a system not built to schedule and track them. These operations need a real CAFM or CMMS from day one, with Business Central in its proper role behind it.

The pattern across all three is consistent. Business Central belongs in the finance and commercial role in essentially every case. Whether you also need a dedicated operational system, and how heavy it should be, scales with your asset count, your PPM and compliance load, and the size of your field operation. Size the operational tool to the operation, keep Business Central as the backbone, and you avoid both under-tooling a large operation and over-engineering a small one.

10. A practical path to a joined-up FM systems landscape

If you are staring at this decision now, the sequence matters as much as the destination. Here is the path I would advise an FM operation to follow, because the order in which you do this determines whether the result is coherent or a bolted-together mess.

• Step 1: map your work to the two domains. Before touching any software, write down what your operation actually does and sort each function into finance and commercial or operational and engineering. The list will make the boundary obvious and will surface the handful of points where the two domains meet. Those meeting points are your future integration.
• Step 2: settle Business Central in its proper role. If Business Central is your ERP, configure it to be excellent at finance, procurement, contract billing, cost control by dimension, and the fixed-asset ledger. Resist the temptation to stretch it into operations. Let it be the best commercial backbone it can be.
• Step 3: choose the operational system to fit your load. Select a CAFM or CMMS sized to your asset count, PPM volume, compliance obligations and field workforce. Let it own assets, work orders, PPM, SLAs and mobile execution. Buy the operational depth you need rather than trying to build it inside the ERP.
• Step 4: define the integration deliberately. Specify the small set of flows across the seam, stock and cost from work orders, subcontractor and additional-works cost, purchase requests, billable works, and shared master data, and assign a single owner to each data domain. Build the integration on the standard APIs both systems expose, not on fragile point hacks.
• Step 5: govern the master data. Establish one authoritative source for every shared entity, sites, cost centres, suppliers, assets, and keep the coding consistent across both systems. This is the least glamorous step and the one that most determines whether reporting and reconciliation are easy or painful.
• Step 6: build the cross-domain reporting last. Once both systems own their domains cleanly and share consistent keys, bring the data together in an analytics layer for the contract-and-service views leadership and clients want. Do this after the foundations are right, not as a way to paper over gaps in them.

Notice that most of the risk in this program is not technical, it is discipline: keeping the boundary clean, assigning single owners, governing master data. The technology to connect Business Central to a CAFM is well understood and available. What separates a joined-up landscape from a tangled one is the clarity of the design and the discipline to keep each system in its lane. Get the boundary right and everything downstream, integration, reporting, reconciliation, gets easier. Blur it and you spend years fighting the consequences.

Final thoughts

So, can Business Central run your facility-management operation? It can run the half it was built for superbly: the finance, the procurement, the contract billing, the cost control and the fixed-asset ledger. It cannot run the other half, the work orders, the planned preventive maintenance, the asset condition and criticality, the SLA clock and the field execution, because that half belongs to a computer-aided facility management or maintenance management system, and no amount of custom development turns an ERP into one convincingly. That is not a weakness in Business Central. It is simply the difference between two kinds of system that serve two kinds of work.

The operations that get this right stop asking one system to do everything and instead pair Business Central with a dedicated CAFM or CMMS, joined at the few points where operational events become financial facts, with one owner per data domain and disciplined master data underneath. That architecture lets finance have the commercial rigour it needs and lets engineers have the operational tool they need, and it gives leadership a combined view neither system could produce alone. If you are already committed to Business Central, that is good news: you have the right backbone, and the highest-return next move is to add the operational system it was never meant to be and connect the two well. When you are ready to design that connection, the CAFM and Business Central integration guide is where this article continues.

Related reading: CAFM and Business Central integration guide, Business Central and CMMS integration, Business Central for asset management, Business Central fixed assets management, FM KPI framework, Is Business Central right for your organization.