Maintenance and the balance sheet

A maintenance system keeps two sets of books

A computerised maintenance management system exists to keep machines running. It holds an asset register of the physical things a business owns and operates: pumps, chillers, forklifts, generators, production lines, vehicles. Against each of those assets it holds work orders, both the ones raised because something broke and the ones raised on a schedule. It holds preventive maintenance plans triggered by calendar date or by meter reading, so a compressor is serviced every two thousand running hours rather than every quarter regardless of use. It holds spare parts and their consumption, technician time booked against jobs, contractor invoices, and the periods during which an asset was not available for production.

Read that list again with the eye of an accountant. An asset register. A record of expenditure incurred on each asset, split by labour, materials and third-party services. A history of component replacements. Evidence of how intensively each asset has been used. Those are the inputs a fixed-asset accountant needs and usually does not have. The maintenance team is, without intending to be, maintaining a subsidiary ledger.

The problem is that it is a subsidiary ledger nobody reconciles. Maintenance and finance describe the same machines in different systems, in different units, for different purposes, and over a few years the two descriptions stop matching.

The question every work order raises

Every maintenance expenditure poses the same accounting question: is this a period cost, or does it belong on the balance sheet. The general position is well settled. Routine repairs and maintenance, the day-to-day servicing that keeps an asset in its expected operating condition, are recognised in profit or loss as incurred. Expenditure that instead enhances the asset beyond its previously assessed standard of performance, extending its useful life or increasing its capacity or output quality, may qualify for capitalisation.

IAS 16 adds two mechanisms that matter on a shop floor. Where an entity performs a major inspection as a condition of continuing to operate an asset, the cost of that inspection can be recognised in the carrying amount as a replacement, with any remaining carrying amount of the previous inspection derecognised. The same logic applies to physical parts: when a significant component is replaced, its cost is capitalised if the recognition criteria are met, and the carrying amount of the part that was removed is derecognised, whether or not it was depreciated separately.

That derecognition step is the one most often missed. If a new engine goes onto the balance sheet and the old engine stays there too, the asset is now carried at more than it is worth, and the overstatement compounds every time the cycle repeats. A maintenance system knows the old engine came out; the ledger usually does not.

None of this is mechanical. Whether a particular overhaul enhances performance or merely restores it, whether the recognition criteria are met, whether an amount is material enough to bother with, are judgements that rest with the preparer, applied consistently under a stated policy and reviewed by the auditor. Software can surface the facts and route the decision; it cannot make the decision.

Componentisation, and why it usually stays theoretical

IAS 16 requires that each part of an item of property, plant and equipment with a cost significant in relation to the total cost, and with a different useful life or consumption pattern, be depreciated separately. A vehicle body and its engine. A building shell and its lifts, chillers and roof membrane. A production line and the tooling that wears out every eighteen months.

Most finance teams accept the principle and then quietly capitalise the whole machine as one line, because componentising requires knowing which components exist, what each cost, when each was fitted and when each was removed. That information does not live in the accounting system. It lives, if anywhere, in the maintenance system, where components are already tracked as serialised items with installation and removal history because that is how technicians work.

Componentisation is therefore less an accounting policy question than a data question. Where a maintenance system already carries the component hierarchy, splitting depreciation is a reporting exercise. Where it does not, it stays a note in the accounting manual.

The spare part that is not obviously an asset

Spare parts sit awkwardly across two standards. Most are inventory under IAS 2: consumables and minor spares held to be used in production or in providing services, expensed or absorbed as consumed. But major spare parts and standby equipment qualify as property, plant and equipment under IAS 16 when they are expected to be used over more than one period, and spares that can be used only in connection with a particular item are accounted for on the same basis.

The practical consequence is the same physical shelf holding items with two different accounting treatments. A critical standby pump held for a single production line and expected to sit unused for years is capitalised and depreciated. A box of seals from the same manufacturer is inventory. The distinction turns on how the item is held and used, not on what it costs, and it can only be applied if the store knows which parts are dedicated, critical and long-lived. A maintenance system already carries that classification for reasons of its own.

What a work order costs, and where the cost goes

A closed work order accumulates labour hours at a charge rate, parts issued from stores at their carrying cost, and contractor charges from purchase orders or invoices. That total is the natural unit of maintenance cost. The accounting question is where it lands: repair and maintenance expense for the cost centre that owns the asset, or an addition to the carrying amount of the asset, or a mixture, since a single shutdown often contains both an overhaul that qualifies for capitalisation and routine servicing that does not.

This is where integration earns its place. If the work order and the ledger share one asset identity, the cost can be classified at the point it is captured, by people who know what the work actually was, and posted with the work order attached as its supporting document. If they do not, someone in finance reads an invoice description months later and guesses.

Skyline Nexus is built so that the maintenance module and the fixed-asset register address the same asset record rather than two parallel lists. A work order closed against an asset carries its costs into the ledger under the treatment chosen for it, and a capitalised replacement can be posted alongside the derecognition of the part it replaced.

Idle assets still depreciate

A persistent misconception is that an asset stops depreciating while it is out of service. Under IAS 16 depreciation does not cease when an asset becomes idle or is retired from active use, and continues until the asset is derecognised or classified as held for sale. Depreciation ends when the asset is derecognised, not when it stops earning.

There is a narrow exception in method rather than principle: where the depreciation method is usage-based, such as units of production, the charge can legitimately be nil during a period of no production. That is a consequence of the chosen method, not a general suspension. Extended idleness is, separately, an indicator that the asset may be impaired, which is a different test under a different standard.

How the two lists drift apart

The failure is rarely dramatic. It accumulates. A machine is scrapped on the floor and the disposal is never notified to finance, so it keeps depreciating for years and eventually sits at a residual value nobody can explain. An asset is moved between sites and appears twice. A replacement is capitalised while the replaced component remains on the register. Assets are tagged by maintenance with one numbering scheme and by finance with another, so no join is possible without a spreadsheet and a week of somebody time.

The consequences run past the financial statements. Insurance is placed against the wrong schedule, property or asset-based taxes are computed on assets that no longer exist, capital budgets are built on a fictional fleet, and the physical verification count that should catch all of this becomes so laborious that it is done rarely, or partially, or not at all.

• Ghost assets: capitalised costs on the register with no corresponding machine in the plant.
• Unrecorded disposals: equipment scrapped or sold with no derecognition entry, overstating both assets and the depreciation charge.
• Orphan equipment: machines maintained, insured and consuming spares that were never capitalised at all.
• Duplicate capitalisation: a replacement added while the part it replaced is still carried.
• Divergent identifiers: no shared asset number, so the two registers cannot be reconciled mechanically.

One asset, one identity

The remedy is structural rather than procedural. When the asset record that the technician opens to log a work order is the same record the accountant opens to view cost, accumulated depreciation and net book value, the two lists cannot diverge, because there are not two lists. A disposal recorded by the maintenance team is visible to finance as an asset awaiting derecognition. An asset with no maintenance history and no meter movement is visible as a candidate for impairment review or physical verification.

In Skyline Nexus the maintenance, fixed-asset and inventory functions sit on shared master data within one system, so a spare part classified as a capitalised standby, a component fitted under a work order, and the depreciation schedule that follows all reference the same asset. It does not remove the judgement about what to capitalise. It removes the excuse that the information was not available when the judgement had to be made.

For finance teams in Saudi Arabia and the wider Gulf, where IFRS as endorsed locally governs the treatment and where asset-heavy sectors dominate, the reconciliation between the shop floor and the register is not a housekeeping matter. It is the evidence behind a material line of the balance sheet.