Insight

Decide capitalisation while the work order is open

Capitalisation reconstructed at year-end from work order text costs both registers. Decide it at work order approval, against a mapped asset record.

7 min read By Jonathan Heward, Head of Account Management
Cover image for the insight: Decide capitalisation while the work order is open
AnalysisCapitalisationFixed Asset RegisterCapital PlanningAsset Data Governance

In the first week of April, a management accountant at a cement producer works through 180 closed maintenance work orders above £25,000 and decides which of them added value to plant and which were repairs. The evidence available is the work order long description and the supplier invoice. A £210,000 kiln drive gearbox replacement reads “gearbox changed out, unit returned to service” (figures illustrative). It is capitalised, because the invoice is large and the job took a fortnight. The gearbox that came out was never carried as a separate line in the fixed asset register, so nothing is derecognised, and the register now depreciates two gearboxes on one kiln drive. In June, the external auditor samples thirty of those 180 decisions.

Capitalisation is a plant decision being taken eight months late by the one person in the chain who never saw the plant. The planner who scoped the job in August had the drawings, the vendor quote and the removal plan, and answered the question implicitly by choosing a work type. Nothing in the configuration caused the loss: the decision was never asked for at the point it was cheap to answer.

Four kinds of spend land on one asset record

Under IAS 16 the treatment of work on plant depends on what the work did, not on what it cost. The plant events are distinguishable at the point of scoping.

Plant eventTreatment under IAS 16What the record must carryWhere it sits in Maximo Manage
Servicing and statutory inspection to keep the unit runningExpensed as incurredAsset, work type, actual labour and materialsActuals on the work order, rolled up to the asset
Replacement of a significant component: gearbox, stator, heat exchanger bundleNew part capitalised, carrying amount of the replaced part derecognisedComponent asset number, its cost, the removal dateAsset hierarchy, plus a swap or split of the depreciation schedule
Major inspection or overhaul required for continued operation: dry dock, turnaround, statutory overhaulCapitalised and depreciated to the next overhaulOne scheme reference holding the overhaul scope and costCapital work type with the overhaul GL debit account
Duty or capacity change: uprated motor, added filtration trainCapitalised as a new or enhanced assetNew asset record, in-service date, depreciation basisAssets application, new depreciation schedule

Only the first row is unambiguously operating expenditure. The other three need component-level identity to be accounted for, and each of them needs a classification recorded by someone who understands the mechanical scope.

Depreciation units and maintainable items need separate identifiers

The ledger depreciates units whose carrying amount can be written out when the unit is replaced. Maintenance works at the level a job plan attaches, a permit is raised and a failure is coded. On a kiln drive those two levels differ by one or two tiers: finance carries the drive train, reliability carries the gearbox, the motor and the coupling.

The arrangement that holds is a maintenance register cut finer than the fixed asset register, with each asset record carrying the fixed asset register line as an attribute populated at asset creation. The mapping is many-to-one and it lives as data on the asset record. Maximo Manage rolls labour, material, tool and service costs from a closed work order up to the top-level asset in the hierarchy, and rollups are manual by default until the organisation sets them to run automatically. Where the hierarchy mirrors the plant and the fixed asset reference sits on the nodes that are depreciation units, the maintenance cost report and the capital reconciliation are drawn from the same tree rather than from two spreadsheets that disagree by £400,000. That tree is also what makes an asset register capable of underwriting a capital case rather than merely describing one.

The capitalisation call belongs at work order approval

Three configuration surfaces carry the decision, and all three are ordinary Maximo Manage administration.

  1. A capital work type in the WORKTYPE domain, distinct from corrective and preventive work, selected by the planner when the scope is a component replacement, an overhaul or a duty change. The planner answers once, in the week the quote arrives.
  2. GL defaulting and validation. The asset GL account is the default debit account for work orders and purchase orders raised against that asset. The Chart of Accounts application holds the account structure and resource codes, and its validation options can require a valid GL account on all transactions and validate component combinations, so capital work cannot be approved against a cost centre with no capital resource code.
  3. An approval gate on the work order. Workflow holds a capital work order short of approved status until the scheme reference and the target depreciation unit are populated, the second defaulted from the asset’s fixed asset attribute and editable by the planner. The supervisor who releases the work confirms where the money lands, at the same moment they confirm the crew.

The output is a closed work order that already states its treatment. The April exercise becomes a reconciliation of totals rather than a reconstruction of 180 mechanical decisions from free text.

Component replacement writes to both registers

The new component is received as a rotating item and installed as a child asset. The removed unit keeps its asset number, moves to the repair shop or disposal location, and carries its own failure history against the serial that actually failed. Depreciation schedules in Maximo Manage can be date-based or usage-based against an asset meter, and a schedule can be swapped between an original asset and its replacement, or split from a parent across its children where the component was never valued separately. Finance receives a derecognition amount with a date and an asset number. Reliability keeps a failure record against a serial number rather than against the drive train as a whole.

The artefact that makes this auditable is a monthly asset change note listing additions, disposals and transfers between cost centres, produced from the asset record and signed by both functions. It is the same control discipline that applies to changes to asset master data after go-live, extended to the one class of change that moves money.

Running the alignment costs a named half-day each month

The recurring cost is small and specific: the asset data steward reconciles asset additions, disposals and transfers against the fixed asset register, and samples twenty capital work orders for work type, GL account and depreciation unit. The review is a standing monthly item with a management accountant and a reliability engineer in the room. At steady state that is three to four hours a month (illustrative), against a year-end exercise that currently consumes a fortnight of accountant time plus the audit sample.

The one-off cost is the mapping of the existing register, and it is the reason this work gets deferred. On an estate of 40,000 asset records against 5,000 fixed asset lines, mapping is a data project with a scope and a budget, best run against the highest-value 20% of the register first and completed opportunistically as assets are touched. ISO/TS 55010 covers the alignment of financial and non-financial functions in asset management, and it is the document to cite when this control is written into the asset management system rather than into a finance workbook.

What stays hard

Components that were never valued separately cannot be derecognised precisely. The auditor will accept a reasoned estimation method, and the method needs writing down once so it is not reinvented each March.

Registers built before componentisation cannot be recut retrospectively. Where one line covers a whole pumping station, the split starts at the next replacement and the estate converges over a decade.

Lump-sum contracted work resists the split. A framework invoice priced per visit gives no labour and material breakdown, so the capitalised cost is whatever the invoice says, and the data schedule in the next tender is the only place to change that.

Finance still owns the classification. A capitalisation threshold in the accounting policy overrides the planner’s work type on small component swaps, so the flag on the work order is a recommendation carrying evidence and the accountant still posts the entry.

Regulated reporting adds a third dimension. Totex submissions in water and energy need cost cut by scheme as well as by asset, and scheme is a separate attribute from both registers.

The position

The cheapest moment to classify capital spend is the week the job is scoped, by the engineer holding the vendor quote. The most expensive is the April after the year in which it was spent, from a description written for a maintenance audience. Operators who want both registers to hold should add the capital work type, put the fixed asset reference on the asset record, gate approval on both, and give one named person on each side a monthly reconciliation to sign.

The measure to take into the next finance and asset management review is the share of capitalised spend traceable to a work order that names its depreciation unit. Where that figure sits below 90%, the fixed asset register is being rebuilt once a year from maintenance free text by someone who has never stood next to the kiln, and both registers carry the cost of that.

Sources

Who stands behind this piece

Jonathan Heward

Head of Account Management

The argument above, including where it stops and what still has to be true on a live estate before it applies.

Talk to them directly →

Read next in the river

Neighbouring arguments and the delivery page

Where this leads

This piece takes a position. The delivery side of it sits on Business process optimisation, and the buyer guides work the same decisions end to end.

Disagree with it on your own estate before you circulate it as settled fact.

Disagree with this on your own estate

An insight argues one thing in general. Thirty minutes with a senior MaxIron engineer is where it gets tested against your version, your integrations and your operating model. Start with Business process optimisation if you would rather read first.

Useful to have to hand

  • Your current Maximo or MAS version, and the database behind it.
  • The part of this piece you think does not apply to you.
  • The decision this feeds, and who has to sign it off.