Government & Public Sector use case

Heavy Plant Depreciated Two Different Ways in Two Systems

Who this fitsA PSU where engineering and finance keep separate records
Asset rangeHigh-value plant across units
What it producesOne record engineering and finance both use
One record
Shared

The physical asset and its book value, together

Depreciation
Consistent

Computed on the basis public sector reporting requires

Audit trail
Locked

Entries cannot be altered after the fact

ERP
Posted

Values flow across instead of being re-keyed

1. The Problem

In most public sector undertakings the same machine exists twice. Engineering holds a plant record with its make, capacity, location, service history and condition. Finance holds a fixed asset register with a cost, a capitalisation date and accumulated depreciation. The two were created separately, use different identifiers, and have drifted apart for years.

Reconciling them is a pre-audit ritual. Somebody maps engineering asset numbers to finance codes by hand, discovers plant that finance is depreciating and engineering scrapped, and finds machines in service that were never capitalised. The audit observations that follow are about the reconciliation rather than the assets, and the same exercise repeats next year because nothing structural changed.

2. How ASTITVAAMS Handles It

The first phase is usually mapping the two existing registers rather than tagging, since both already exist. Four things do the work:

One record, two views

The machine and its book value sit on the same record. Engineering sees condition and service history; finance sees cost and depreciation. Neither maintains a separate list.

Depreciation on the required basis

Computed to the standards public sector reporting expects, so the figure in the accounts and the figure in the register are the same figure.

An audit trail that cannot be edited

Changes are recorded as additions rather than overwrites, so what a value was in March is still visible in December.

Posted back to the ERP

Values flow into the system finance already reports from, rather than being typed in twice with the differences that follow.

The short version

The annual reconciliation between engineering and finance stops being necessary, because ASTITVAAMS puts both on one record. Plant that was scrapped stops being depreciated, and machines in service stop being invisible to the accounts.

Where this applies
PSUs and CPSEs with high-value plant and separate engineering and finance registers

3. What Changes for You

  • The pre-audit reconciliation goes away: There is one register, so there is nothing to reconcile. The weeks that went into mapping identifiers are returned.
  • Scrapped plant stops carrying value: When engineering records a disposal, finance sees it, so the accounts stop depreciating machines that no longer exist.
  • Observations are about assets, not bookkeeping: Audit attention moves from whether the registers agree to questions actually worth answering.

Take This Away

A PDF covering how the two registers are mapped, how depreciation is computed and posted, and what the audit trail records. Useful for finance and engineering heads to read together.

Other Use Cases

Government & Public Sector

Civic Assets With No Value Attached to Them

Government & Public Sector

An Annual Stock Check That Takes Months of Staff Time