An entity is asked for four asset registers and builds one

Start with the small question, because the large one hides inside it.

An entity owns some desks. They cost a few hundred each, they fall well below any sensible capitalisation threshold, and the published guidance says plainly that they should be expensed rather than capitalised. So they are not assets for reporting purposes. Does that mean nobody should know where they are?

Obviously not. Somebody has to know, because the desks can be stolen, moved, insured and eventually replaced. The instinct that they belong on a register is correct. The error is assuming there is only one register for them to belong to.

Four registers, two authorities

Ministry of Finance guidance for the accrual conversion asks a government entity for three distinct records. A fixed asset register, built for reporting. A register of the assets of projects under execution, holding cost until it transfers. And, for items that meet the definition of property, plant and equipment but fall below the capitalisation threshold, a control register for tracking, with the cost expensed when the item is issued from stores.

Separately, the National Manual for Assets and Facilities Management, issued by the Expenditure and Projects Efficiency Authority, devotes a chapter to an asset register of its own.

The useful shorthand is that the first three are versions of a financial asset register, owned by finance, and the fourth is a technical asset register, owned and operated by the functions that run the estate. Those two names are not standard terminology and neither authority uses them, but they name the distinction better than the documents do.

Four registers a Saudi public entity is asked to hold, and what each is organised around. Three come from Ministry of Finance guidance for the accrual conversion and are built on cost. The fourth comes from the national asset and facilities manual and is built on criticality, location and replacement value, with original cost optional.

Register	Organised around	How value is held
Fixed asset register	Recognition and reporting	Historical cost, depreciated
Projects under execution	Accumulating cost before transfer	Cost incurred to date
Control register, below threshold	Custody of items that are not assets	None. Expensed on issue
Operational asset register	Criticality, location and service	Current and replacement value

The first three sort assets by what they cost. The fourth sorts them by what their failure would cost, which is a different question about the same building. An entity holding one file has answered whichever question had a deadline attached.

They are not versions of one another

The tempting reading is that these are the same list at different levels of detail. They are not, and the manual's own required fields settle it.

The national operational register requires, as a minimum for every asset: the region, the building, the floor, GPS latitude and longitude, a functional code physically affixed to the asset, a unique asset code recorded in the asset management system, and a criticality rating in which first priority is assets critical to public health, safety, security or the environment, and second priority is assets critical to the entity's mission.

Then the values. Current value and replacement value are mandatory fields. Original cost is optional, entered only if known.

A financial register is the exact inverse. It is built on original cost, because recognition and depreciation require it, and replacement value has no place in it at all under the cost model. One register cannot hold both dispositions, because they disagree about which number is the real one.

Why entities build one anyway

Not carelessness. Deadlines.

The accrual conversion has a date, a central committee, an opening balance sheet and an auditor waiting at the end of it. The operational register has none of those. When one of two obligations carries a deadline and the other does not, the one with the deadline is built first, and the other is quietly redefined as a subset of it.

That is the mechanism behind an exercise that puzzles everyone who sees it: an entity holding billions in real estate, sending teams to tag, classify and depreciate individual desks and monitors. The team was not told to build an operational register. It was told to complete the fixed asset register, and a desk is a thing, and things go in the register. The threshold that should have excluded it was either never set or never applied, and the custody purpose that legitimately requires tracking got served through the only file anybody had funded.

Why the standard leaves the capitalisation threshold to management

, read: The date a project becomes an asset is not the date on the certificateThe date a project becomes an asset is not the date on the certificate

What the guidance already permits

The resolution does not require anybody to invent anything, which is worth saying because the usual response to this problem is a new system.

So the separate register for low value items is not a workaround. It is the prescribed treatment, and it has been published since 2024. The international standard supports the same aggregation, naming the same categories.

Sequence, not conflict

It is tempting to read all this as two authorities pulling in different directions and to call for a reconciliation between them. That is the wrong conclusion, and worth resisting.

The two registers describe different levels of organisational maturity, and they arrive in an order. A financial register can be built by a finance function against a deadline, from procurement records, contracts and valuations. A technical register cannot be built by anybody, because it presumes an asset management function that can say what an asset is for, how critical it is and what condition it is in. Many entities do not have that function yet, centralised or dispersed, and asking them for a technical register is asking for an output of a capability they have not built.

So the absence of a map between the two is not straightforwardly a defect. A map drawn now would freeze a relationship between a record that exists and a record that mostly does not.

The alignment problem does have a standard of its own. ISO/TS 55010 gives guidance on aligning the financial and non-financial functions in asset management, and the national manual lists it among its own references. The authority that wrote the operational register knew the reconciliation would be needed. What it did not do, correctly, is require it before there is anything to reconcile.

Criticality is not a property of the asset

The operational register's most demanding field is the one that looks simplest. A criticality rating is not read off the asset. It is derived from what the organisation is for, which means it cannot be assigned until somebody has written that down.

Two regions holding physically similar estates will rate them differently, and should. A region receiving pilgrimage at scale is organised around crowd movement, safety and traffic, so its roads, tunnels and junction control carry consequences that the same assets do not carry elsewhere. A region whose purpose is tourism and residence is organised around environment, landscape and resident satisfaction, and its priorities fall on different assets entirely. Neither ranking is transferable. Copying one into the other produces a register that is complete and misleading.

This is what the strategic asset management plan is for. ISO 55001:2024 gives it Clause 6.2.1, at the head of the objectives clause, precisely as the translation layer between organisational purpose and asset objectives. An entity populating a criticality column without a SAMP is filling in a field whose values it has no basis to choose, and that is a worse outcome than leaving it empty, because it looks answered.

The test of whether a strategic asset plan is doing anything

, read: A strategic asset management plan that has never stopped anything is a descriptionA strategic asset management plan that has never stopped anything is a description

What to examine

• Ask how many asset registers exist, and then ask to see them. The common answer is one, described as serving both purposes, which usually means it serves reporting and is consulted by nobody in operations.
• Ask whether the register carries a criticality rating. If it does not, it is a financial record whatever it is called, and no maintenance decision can be made from it. If it does, ask what the ratings were derived from. A criticality column populated without a strategic asset management plan behind it is an opinion formatted as data.
• Ask which register the entity is currently able to complete, and whether the sequence is understood as a sequence. An entity building its first financial register and being asked simultaneously for technical attributes will produce a poor version of both.
• Ask whether it carries replacement value. A register with original cost and no replacement value cannot support a renewal plan.
• For anything below the capitalisation threshold, ask which register it sits on and what that register is for. If the answer is the fixed asset register, the threshold is not being applied and somebody is depreciating furniture.

---

Sources. Expenditure and Projects Efficiency Authority, National Manual for Assets and Facilities Management, Volume 2, Chapter 2, Asset Register, document EOM-ZA0-PR-000004-AR, revision 000, issued 29 March 2020, for the minimum required attributes, the tagging and functional coding requirement, the criticality priorities, the mandatory current and replacement values against optional original cost, and the list of referenced standards including ISO/TS 55010. The manual runs to seventeen volumes and is published on the authority's knowledge centre.

Ministry of Finance, Kingdom of Saudi Arabia, Accrual Accounting Center, The Comprehensive Guide for the Inventory and Valuation of Assets for Government Entities, the edition marked «الطبعة الثانية» and published by the ministry, page 35, for the fixed asset register and the separate register of assets of projects under execution. The Frequently Asked Questions Guide for the Asset Inventory, Stocktaking and Valuation Initiative in Government Entities, first edition, June 2024, for the treatment of items below the capitalisation threshold and the control register, citing Section 15, Policy 2 of the accounting policies and guidance manual. The ministry maintains a public FAQ page for the programme.

IPSASB, IPSAS 45, Property, Plant, and Equipment, paragraph 8, for the aggregation of individually insignificant items. ISO/TS 55010:2019, guidance on the alignment of the financial and non-financial functions in asset management.

The cited government documents are published in Arabic. English quotations are translated by Projects Advisors; the Arabic original governs.