A fixed asset register audit checks that the register is complete, internally consistent, and tied to the general ledger before any asset in it is tested. That means confirming every asset carries a unique tag, location, cost, accumulated depreciation and useful life; agreeing the register's gross block and accumulated depreciation to the trial balance; and specifically hunting for assets that are fully depreciated but still in use, and assets on the ground with no tag in the register at all. A register that fails these checks cannot support depreciation testing, physical verification, or the fixed asset note in the financial statements.
Why the register audit comes first
Depreciation testing, physical verification, the CWIP schedule and the fixed asset note in the financial statements all read from the same register. If the register has a gap — an asset missing a useful life, a block total that does not tie to the ledger, a disposal that was never removed — every downstream procedure inherits the error without anyone seeing it happen, because each of those procedures tests rows, not the register as a whole.
On a Tally-based client the register is usually not Tally's own fixed asset master, which many mid-market companies do not maintain at all. It is a spreadsheet kept outside the accounting system, updated by whoever handles additions that year, and reconciled to the ledger only at year end if at all. Treat it as a client-prepared schedule that needs the same scrutiny as any other.
What the register must contain
| Field | Needed for | Common gap |
|---|---|---|
| Unique asset tag or code | Physical verification and disposal tracking | Older assets never tagged; new ones tagged inconsistently by site |
| Description and asset class | Grouping for Schedule II useful life, and for the financial statement note | Generic descriptions like 'machinery' that hide multiple distinct items at one cost figure |
| Location / cost centre | Physical verification planning and third-party asset tracking | Not updated when an asset is moved between plants or sent to a customer site |
| Date put to use | Pro-rating depreciation on additions and the Companies Act trigger for commencing depreciation | Invoice date used instead, overstating depreciation on assets installed weeks or months later |
| Gross cost (original cost plus directly attributable costs) | Tying to the ledger and recomputing depreciation | Freight, installation and duties left out, or capitalised separately and never linked back to the parent asset |
| Useful life and depreciation method | Recomputation and Schedule II compliance | A single life applied to a whole class regardless of how individual items are actually used |
| Accumulated depreciation and WDV | Tying to the ledger and spotting fully depreciated assets | Carried forward as a single opening figure with no visible build-up by year |
| Disposal date and reference | Removing assets from the register and the physical count | Scrapped assets left in the register indefinitely because nobody is responsible for updating it |
Common practice, not a requirement
Asking for the register before fieldwork starts, not during it, is standard practice, not a requirement. The reason is practical: a register missing half these columns needs to be rebuilt or supplemented, and that conversation is far cheaper in week one than in week three.
Tying the register to the general ledger
- 01Reconcile gross block by asset classSum the register by class — land, buildings, plant and machinery, furniture, vehicles, computers — and agree each total to the corresponding GL account, not just the aggregate fixed assets figure. A class-level mismatch that nets off in the total is the most common way this slips through.
- 02Reconcile accumulated depreciation the same wayOpening accumulated depreciation plus the year's charge minus depreciation on disposals should equal the closing balance in both the register and the ledger. Any manual adjustment entry posted directly to the depreciation account outside the standard monthly charge deserves its own explanation.
- 03Trace additions from the register to the GL and backPick additions from the register and trace to the purchase invoice and the GL posting; separately pick large capital additions from the GL and trace to the register. The second direction catches capitalised cost that never made it into the asset master.
- 04Trace disposals the same way, in both directionsAn asset removed from the register with no corresponding GL entry, or a GL disposal entry with no register update, both point to the same underlying control gap.
- 05Cast the register's own totalsA spreadsheet-maintained register frequently has formula errors introduced by manual edits — a row inserted that falls outside a SUM range, a copied formula referencing the wrong column. Recast the totals independently rather than trusting the file's own subtotal row.
The two gaps worth hunting for specifically
Two defects recur often enough on Indian mid-market registers that they deserve a dedicated look rather than waiting to surface incidentally during other testing.
- Fully depreciated assets still in use. An asset carried at nil or token value in the register, with no retirement recorded, that is still physically in operation. This is not usually fraud — it is simply that nobody updates the register once an asset's WDV hits zero, because there is no depreciation entry left to prompt it. It matters because these assets still need to appear in the physical verification count and the insurance schedule, and because a cluster of them can indicate a useful life policy that no longer reflects how long assets are actually used.
- Assets missing tags, or tagged assets missing from the register. Run a sample physical walk-through for a handful of high-value items and check the tag against the register, and separately pick a sample of asset tags found on the floor and check each exists in the register. The first direction tests completeness of tagging; the second tests completeness of the register itself, and is the one teams skip.
A register total that agrees exactly to the trial balance is reassuring and proves almost nothing about the individual rows underneath it. A register can net a fictitious addition against an untracked disposal and still tie to the ledger to the rupee. The reconciliation is a necessary check, not a substitute for testing the composition of the register.
Documenting the register audit
- The exact file tested, with version, date received and row count, since fixed asset registers are frequently revised mid-audit without the revision being flagged.
- The class-level reconciliation to the GL, with every difference explained rather than netted into an overall rounding figure.
- The population and results of the additions and disposals trace, in both directions.
- Fully depreciated assets still carried as in use, quantified and cross-referenced to the physical verification working paper.
- Any field missing from the register and how the gap was covered — supplemented from another source, or scoped out with the reason stated.
How we think about this
Tying a register to a ledger, casting a spreadsheet, and finding duplicate tags are rule-based checks that a computer does exactly the same way on the tenth review as the first. Deciding whether a cluster of fully depreciated assets reflects a genuine change in how long machinery lasts, or a stale useful-life policy nobody has revisited, is a judgement call that belongs to the audit team, informed by what the reconciliation surfaces rather than replaced by it.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Fixed assets & capexDepreciation testing: audit procedure and recomputationChecking useful lives against Schedule II, recomputing the charge independently for a sample, and handling mid-year additions, disposals and changes in estimate.
- Fixed assets & capexPhysical verification of fixed assets: how to plan itA rotational verification policy, reconciling the count to the register, handling assets at customer or third-party sites, and the link to CARO 3(i).
- Fixed assets & capexCapex vs revenue expenditure: the audit testThe capitalisation criteria, the repairs-versus-improvement judgement calls that actually come up, and how to sample repairs and maintenance for misclassified capex.
- CARO & Companies ActCARO fixed asset and inventory clauses: what auditors testWhat the fixed asset and inventory points under CARO actually require in evidence: physical verification, title deeds, revaluation, and count discrepancies.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.