Business Central for Asset Management: Financial Assets and the EAM Boundary

I have sat in a lot of rooms where the finance team and the operations team both used the phrase "asset management" and genuinely believed they were talking about the same thing. They were not. Finance meant the fixed asset register, the depreciation run and the audit trail behind the balance sheet. Operations meant the pumps, chillers, generators and handling equipment that have to keep running, with work orders, condition monitoring and spare parts behind them. Both are legitimate uses of the term. Both matter. But they are handled by different systems, owned by different departments, and confusing them is one of the most expensive misunderstandings in enterprise software selection. Business Central sits squarely on the finance side of that divide, and the goal of this guide is to be honest about exactly where its capability ends.

The message up front: Business Central is an excellent financial fixed-asset system. It handles acquisition, capitalization, depreciation, revaluation and disposal cleanly, inside your general ledger, with a full audit trail. What it is not is an enterprise asset management or maintenance system. It does not run work orders, condition monitoring, criticality ranking or maintenance lifecycle planning. If you need the operational side, you need a dedicated EAM or CMMS alongside Business Central, and the real skill is keeping the two registers aligned rather than pretending one tool does both jobs.

1. Two meanings of asset management: financial versus operational

The single most useful thing you can do before any system discussion is force the word "asset" to declare which meaning it intends, because the two definitions drive completely different requirements, owners and data.

Financial asset management is an accounting discipline. It treats an asset as a capitalized cost that must be recorded, depreciated over its useful life, revalued when policy or impairment requires it, and eventually disposed with a gain or loss posted to the ledger. The questions it answers are: what did we pay, what is it worth on the books now, how much depreciation hits this period, and what is our total capital position. The owner is finance. The system of record is the ERP, and in the Microsoft stack that is Business Central. The audience is the controller, the auditor and the tax authority.

Operational asset management, often formalized under the ISO 55000 family and delivered through EAM or CMMS software, is an engineering and reliability discipline. It treats an asset as a physical thing that has to perform a function safely and economically over its service life. The questions it answers are: how critical is this asset, what is its condition, what maintenance does it need and when, what has failed on it before, what does it truly cost to keep running, and when should we replace it. The owner is engineering, maintenance or facilities. The system of record is a CMMS or EAM. The audience is the maintenance planner, the reliability engineer and the operations manager.

The same physical chiller exists in both worlds simultaneously. In Business Central it is a fixed asset with a book value of a certain amount, a ten-year straight-line depreciation schedule and an accumulated depreciation balance. In an EAM it is a tagged asset with a location in the hierarchy, a criticality rating, a preventive maintenance schedule, a failure history and a running lifecycle cost. Neither record is wrong. They are two faces of one object, kept by two departments, for two purposes. The mistake is expecting a single system to hold both faces well, and that mistake is exactly what this guide exists to prevent. For how the operational hierarchy is designed, see the asset hierarchy design pillar.

2. What Business Central does for assets: the fixed assets module

Business Central ships with a genuinely capable Fixed Assets module, and it is worth being precise about what it covers, because a lot of the confusion comes from underestimating how much the financial side actually delivers. Within its own domain the module is mature and complete, and it manages an asset across its entire accounting lifecycle from acquisition to disposal.

The core capabilities, in the order an asset moves through them:

• Acquisition and capitalization: an asset is created as a fixed asset card, then acquired through a fixed asset journal or, more commonly, directly from a purchase invoice so the capitalized cost flows straight from procurement into the asset register with no rekeying. The acquisition cost, acquisition date and the general ledger accounts it posts to are all captured at this point.
• Depreciation books: each asset is linked to one or more depreciation books, which define the method, the useful life and the posting rules. Business Central supports multiple books in parallel, so you can run one book for statutory financial reporting and a separate book for tax, with different methods and lives, against the same physical asset. This multi-book capability is one of the module's genuine strengths.
• Maintenance cost registration (financial sense): the module includes a "maintenance" concept, but be careful, because this is a financial classification, not maintenance management. It records maintenance expenditure against an asset so you can see cumulative repair cost on the books. It does not schedule, plan or track the maintenance work itself. This is one of the most misread features in the whole module, and I will return to it in the boundary section.
• Revaluation, write-down and appreciation: adjustments to the carrying value of an asset are handled through dedicated posting types, keeping the book value aligned with accounting policy and impairment decisions.
• Disposal: when an asset is retired or sold, disposal posts the removal of cost and accumulated depreciation, calculates the gain or loss, and clears the asset from the active register, all inside the ledger with a full audit trail.

The structural strength here is integration with the general ledger. Because Fixed Assets is a native Business Central module rather than a bolt-on, every acquisition, depreciation run, revaluation and disposal posts directly to the ledger with no reconciliation gap between the asset register and the financial statements. For a finance team, that tight coupling is the whole point, and it is exactly what a standalone maintenance system cannot give you. For a deeper walkthrough of the module mechanics, see the Business Central fixed assets deep-dive.

3. Depreciation, revaluation and the accounting view

Depreciation is where the financial definition of asset management is at its most rigorous, and Business Central handles it thoroughly. I will keep this section deliberately brief because the mechanics are covered in detail in the fixed assets deep-dive, but the shape of the capability matters for understanding the boundary.

Business Central supports the standard depreciation methods a finance team expects: straight-line, declining balance, a combination of declining balance and straight-line, and user-defined methods for cases the built-ins do not cover. Depreciation is run periodically through a batch process that calculates the charge for each asset in each book and posts it to the ledger. Because the calculation is book-specific, the same asset can depreciate on a straight-line basis in the financial book and an accelerated basis in the tax book in the same period, which is precisely what multi-jurisdiction and tax-optimized reporting require.

Revaluation and impairment are handled through write-up and write-down postings, so when policy or an impairment test changes the carrying value, the adjustment is recorded cleanly and the depreciation base recalculates from the new value forward. Disposal closes the loop by posting the gain or loss and removing the asset from the active books.

Here is the important framing: every one of these operations is about the value of the asset on the books, not the condition of the asset in the field. Depreciation is a financial estimate of how cost is consumed over an assumed useful life. It has almost nothing to do with the actual physical state of the machine. An asset can be fully depreciated on the books, worth zero in accounting terms, and still be the most reliable, hardest-working machine in the plant. Conversely, an asset can sit near the top of its depreciation schedule, high book value, and be a maintenance nightmare that fails constantly. The accounting view and the operational reality are simply measuring different things, and that gap is the entire reason the operational world needs its own system. For a fuller treatment of the accounting mechanics, follow the fixed assets deep-dive.

4. Asset registers, categories and reporting in Business Central

Beyond the transactional lifecycle, Business Central gives you the structures to organize and report on the asset base, and these are the features that most closely resemble what people think of as an "asset register." Used well, they answer the finance and audit questions cleanly.

The organizing structures are:

• FA classes and subclasses: high-level groupings such as buildings, plant and machinery, vehicles, IT equipment. These drive how assets are categorized on financial reports and how depreciation policy is applied by class.
• FA locations: a field to record where an asset physically sits. This is useful for a stocktake and for basic accountability, but note that it is a flat attribute, a single location code on the card, not a multi-level hierarchy of site, building, floor, room and system that an EAM uses to model where an asset lives functionally.
• FA posting groups: the mapping that ties each asset to the correct general ledger accounts for acquisition, depreciation, disposal and gain or loss, ensuring consistent and auditable posting.
• Dimensions: Business Central's flexible tagging, which lets you attach department, cost center, project or custom analytics codes to assets and their postings, so you can slice asset cost and depreciation by whatever business dimension you care about.

On the reporting side, the module produces the reports a finance function needs: the fixed asset register itself, acquisition and disposal listings, depreciation books, book value reports, and analysis views that combine dimensions with asset data. These feed the balance sheet, satisfy the auditor, and support tax filing. Within the boundary of "what is this asset worth and what has it cost us financially," Business Central answers comprehensively.

Where the register stops being enough: the FA location field and the class structure look, at a glance, like an asset hierarchy, and teams sometimes try to run operational asset management out of them. It does not work. A single flat location code and a financial class cannot express the functional parent-child relationships, the system groupings, or the criticality context that maintenance planning depends on. The financial register tells you what an asset is worth and where you last recorded it sitting. It cannot tell you which pump feeds which chiller, which failure would stop production, or what maintenance is due. Those are questions the operational hierarchy exists to answer, and the fixed asset register was never designed to.

5. The boundary: where financial asset management ends and EAM begins

This is the section that should settle every "can Business Central do asset management" argument. The honest answer is: it does financial asset management well and operational asset management barely at all, and the line between them is clear once you know where to look for it.

Business Central's Fixed Assets module ends at the point where the question stops being about money and starts being about the physical machine. It can tell you an asset's book value, its depreciation schedule, its cumulative repair spend and its disposal position. It cannot tell you the asset's condition, its criticality, its maintenance schedule, its failure history, its remaining useful life in engineering terms, or its work order backlog. Those are the defining outputs of enterprise asset management, and they simply are not in the ERP's remit.

The most common trap is the word "maintenance." Because the Fixed Assets module has a maintenance registration feature, people assume it does maintenance management. It does not. The Business Central maintenance feature records the cost of maintenance against the asset for accounting purposes. It has no concept of a work order, a maintenance schedule, a preventive routine, a technician assignment, a failure code, a spare part reservation or a criticality rating. It is a cost bucket, not a maintenance system. Reading that feature as EAM capability is the single most expensive misunderstanding I see in this space, because it leads organizations to skip a real CMMS and then discover, a year in, that they have no operational control over their physical assets at all.

The clean way to state the boundary: if the question can be answered from the ledger, Business Central owns it. If the question requires knowing the physical state, function, criticality or maintenance status of the asset, it belongs to EAM or CMMS. Draw that line honestly at selection time and you avoid the whole category of disappointment that comes from expecting the ERP to run the plant floor.

6. What EAM and CMMS add: condition, maintenance, criticality, lifecycle, work orders

If Business Central handles the financial face of the asset, the operational face is the domain of a dedicated EAM or CMMS, and it is worth spelling out exactly what those systems add, because it is substantial and none of it overlaps with the ERP's strengths.

• Functional asset hierarchy: EAM models assets in a multi-level parent-child structure, site to building to system to equipment to component, so you can see what depends on what, roll costs and failures up the tree, and understand the operational context of every asset. This is a fundamentally richer structure than the flat FA location field.
• Work order management: the operational heart of a CMMS. Corrective, preventive and inspection work orders, with planning, scheduling, labour and parts, status tracking and closure. This is the transactional backbone of maintenance and it has no equivalent in Business Central.
• Preventive and condition-based maintenance: time-based and meter-based schedules that generate work automatically, plus condition triggers that raise work when a monitored parameter crosses a threshold. Managing planned maintenance is the core reliability discipline the ERP cannot touch.
• Asset criticality and risk: a structured ranking of which assets matter most to safety, production and cost, used to prioritize maintenance investment and spares holding. The criticality view drives almost every operational decision and has no financial equivalent. See the asset criticality classification pillar.
• Failure history and reliability: structured failure coding, downtime capture and reliability metrics such as mean time between failures, which turn maintenance records into the data that drives improvement. The ERP records repair cost; the CMMS records why the asset failed and what it cost in downtime.
• Maintenance, repair and operations inventory: management of spare parts specifically for maintenance, reservations against work orders, and the balance between carrying cost and availability, which is a different discipline from the financial stock valuation the ERP performs.

Put together, these capabilities are the operational asset lifecycle, and they are exactly what keeps physical equipment running safely and economically. An organization that has Business Central and believes it therefore has asset management is missing this entire layer. For how condition monitoring and prediction sit on top of this foundation, see the predictive maintenance pillar.

7. Keeping the financial and operational asset registers aligned

Once you accept that you have two registers, one financial in Business Central and one operational in the EAM, the practical problem becomes keeping them aligned, because the same physical assets are being tracked in both and they must not drift apart. This is where the real integration work lives, and it is more subtle than it first appears.

The two registers are almost never a one-to-one match, and that is the first thing to understand. Finance capitalizes assets by cost and materiality thresholds, so a group of components might be one capitalized asset on the books. Operations tracks assets by maintainable unit, so that same group might be five separately maintained items in the EAM, or conversely several small capitalized items might be maintained as one system. Trying to force a rigid one-to-one link between the two registers usually fails because the granularities genuinely differ. The workable approach is a defined mapping, not a mirror: agree how financial assets relate to operational assets, maintain a cross-reference, and accept that the relationship is sometimes one-to-many in both directions.

The events that must stay synchronized across the boundary are the lifecycle transitions: a new asset acquired and capitalized in Business Central needs to appear in the EAM so it can be maintained, and an asset disposed of operationally needs to trigger the financial disposal so the books reflect reality. When these events are not synchronized, you get the two classic failures. The first is ghost assets: equipment scrapped in the field but still depreciating on the books, inflating the balance sheet and the insurance bill. The second is untracked assets: equipment installed and running but never set up for maintenance because nobody told the EAM it existed. Both are common, both are expensive, and both come from a broken link between the registers.

Integration can range from a periodic reconciliation, where someone compares the two registers and fixes discrepancies, up to a real-time interface where asset creation and disposal events flow automatically between the systems. The right level depends on asset volume and change rate. What matters is that the link exists and is owned, rather than left to chance. For the technical patterns behind connecting Business Central to a maintenance system, see the Business Central CMMS integration pillar.

8. Asset lifecycle and total cost of ownership across both worlds

The reason it is worth doing the integration work, rather than just running two disconnected registers, is that the genuinely valuable questions about an asset can only be answered when the financial and operational views are joined. Total cost of ownership and lifecycle decisions live exactly on that seam.

Consider the question every asset-intensive organization eventually asks: should we repair this asset again or replace it? Answering it well requires data from both worlds. From the financial side you need the acquisition cost, the accumulated depreciation, the current book value and the replacement capital cost. From the operational side you need the failure frequency, the accumulating maintenance and downtime cost, the criticality, and the trend in condition. Neither system alone can answer the repair-or-replace question. Business Central knows what the asset is worth on paper but not how much pain it is causing in the field. The EAM knows the failure and maintenance history but not the capital position. Joined together, they let you see the true total cost of ownership, the sum of capital, depreciation, maintenance and downtime over the asset's life, which is the only number that supports a sound lifecycle decision.

This is also where the difference between accounting useful life and engineering useful life becomes concrete. The depreciation schedule assumes an asset is consumed evenly over an assumed life. The physical asset does not cooperate with that assumption. It might last far longer than its depreciated life with good maintenance, or fail far sooner if it is critical and poorly maintained. The organizations that manage assets well use the operational data to inform the financial view and vice versa: rising maintenance cost and falling reliability signal that an asset near the end of its economic life should be planned for replacement, and that replacement is then a financial capital decision made with operational evidence behind it.

The payoff of joining the two views: the highest-value asset decisions, repair or replace, extend or retire, invest or run to failure, cannot be made from the ledger alone or the maintenance system alone. They require the total cost of ownership picture that only appears when the financial register in Business Central and the operational register in the EAM are aligned. That alignment is the real return on doing asset management properly, and it is invisible to anyone who thinks a single system is enough.

9. Best-fit: BC alone versus BC plus EAM

Not every organization needs both systems, and it would be dishonest to imply otherwise. The right answer depends entirely on how asset-intensive the operation is, and there is a clear way to reason about it.

Business Central alone is genuinely sufficient for organizations whose assets are largely passive from a maintenance point of view. A professional services firm, a software company, a distributor or a light office-based business has assets, computers, furniture, vehicles, leasehold improvements, that need to be capitalized, depreciated and eventually disposed, but that do not require structured maintenance management. For these organizations the Fixed Assets module covers the real requirement completely, and adding an EAM would be solving a problem they do not have. The asset management they need is financial, and Business Central delivers it.

Business Central plus a dedicated EAM or CMMS is the correct architecture for asset-intensive operations: utilities, manufacturing, oil and gas, healthcare estates, transport, real estate and facilities management, and anywhere physical equipment must be kept running safely and reliably. These organizations have the same financial asset requirement as everyone else, and Business Central handles it, but they also have a substantial operational asset requirement that the ERP cannot touch. For them, trying to run maintenance out of the Fixed Assets module is not a cost saving, it is an operational blind spot that shows up as unplanned downtime, safety exposure and runaway repair cost. The two-system architecture is not duplication, it is the correct division of two genuinely different disciplines.

The honest test I use to place an organization: look at what happens when an asset fails unexpectedly. If the answer is "we buy a new one and expense it," you probably need only the financial register. If the answer is "production stops, or a building goes offline, or a safety system is compromised," you need operational asset management, and Business Central is only half the picture. The consequence of failure, not the number of assets, is what decides whether you need the EAM layer. For how this plays out specifically in a buildings and facilities context, see the Business Central for facility management pillar.

10. A practical path to joined-up asset management

For an organization that concludes it needs both the financial and operational views, the sequence of getting there matters as much as the tool choice. The path I would advise, drawn from doing this on real implementations rather than slideware:

• Step 1: settle the definition per asset class. Agree which assets are purely financial, needing only Business Central, and which are operational, needing EAM as well. Most organizations have both kinds, and clarity here prevents endless later confusion about which system owns what.
• Step 2: get the financial register clean in Business Central first. Accurate classes, correct depreciation books, complete acquisition data and a disposal process that actually runs. A clean financial register is the easier of the two to establish and it becomes the reliable anchor for the operational side.
• Step 3: design the operational hierarchy independently. Do not try to derive the maintenance hierarchy from the financial classes. Build it around function and maintainable units, following sound hierarchy design, so it serves reliability rather than accounting. The two structures will differ, and that is correct.
• Step 4: define the mapping between the two registers. Establish the cross-reference between financial assets and operational assets, accepting one-to-many relationships, and decide which system is the master for which attributes so there is no ambiguity about the source of truth.
• Step 5: synchronize the lifecycle events. Put a process in place, manual reconciliation at first if needed, then automated integration, so acquisitions and disposals flow across the boundary and neither ghost assets nor untracked assets accumulate.
• Step 6: report across both to drive decisions. Bring the financial and operational cost data together for total cost of ownership and repair-or-replace analysis. This is the endpoint that justifies the whole effort, and it is where joined-up asset management finally pays back.

The pattern to notice is that the financial and operational registers are built on their own terms, for their own purposes, and then deliberately linked, rather than one being forced to serve both jobs. That is the architecture that works. Every attempt I have seen to make a single system carry both faces of the asset has ended with one of the two disciplines badly served, usually the operational one, because the ERP looks close enough to fool people into skipping the EAM. Respect the boundary, build both sides properly, and join them at the seam.

Final thoughts

Business Central is a strong financial asset management system, and it deserves the credit for that. The Fixed Assets module handles acquisition, multi-book depreciation, revaluation and disposal cleanly, posts everything straight to the ledger with an audit trail, and gives finance exactly the control over asset value that they need. Within its domain it is genuinely good, and for organizations whose assets are financial rather than operational it is entirely sufficient on its own.

What it is not, and was never designed to be, is an enterprise asset management or maintenance system. It does not run work orders, does not schedule preventive maintenance, does not rank criticality, does not hold failure history, and its "maintenance" feature is a cost bucket rather than maintenance management. Asset-intensive organizations that need to keep physical equipment running safely need a dedicated EAM or CMMS alongside Business Central, and the discipline that makes the whole thing work is keeping the two registers aligned so the financial and operational views of each asset stay in step.

The clarity to take away is simple. Ask which meaning of asset management you need. If it is the value on the books, Business Central owns it. If it is the machine in the field, that is EAM territory, and Business Central is only half the answer. Most serious operations need both, built properly and joined deliberately, and the organizations that understand the boundary manage their assets far better than the ones that hope a single system will quietly do both jobs.

Related reading: Business Central fixed assets management, Asset hierarchy design for CAFM and EAM, Asset criticality classification, Business Central for facility management, Business Central to CMMS integration, Predictive maintenance and failure prediction.