We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Guide6 min readPublished

Capex vs revenue expenditure: the audit test

The capitalisation criteria behind the capex-versus-revenue distinction, how to judge repairs against improvement on a real invoice, and the procedure for testing a sample of large repairs and maintenance postings for expenditure that should have been capitalised.

The audit test for capex versus revenue expenditure is to apply the capitalisation criteria — probable future economic benefit beyond the current period, and cost reliably measurable — to a sample of large postings, concentrating on accounts where misclassification is most likely: repairs and maintenance, consumables, and any account that spiked during the year. An expenditure that merely restores an asset to its original performance is revenue; one that extends its useful life, increases its capacity, or improves the quality of output is capital. The test is not run on the whole ledger — it is run on a targeted sample where the risk actually sits.

The capitalisation criteria, stated plainly

Ind AS 16 and AS 10 both set the same two-part test for recognising subsequent expenditure on an existing item of property, plant and equipment as part of its carrying amount: it must be probable that future economic benefits associated with the item will flow to the entity beyond what was already expected, and the cost must be measurable reliably. Routine servicing — day-to-day repairs, lubrication, minor part replacement — fails the first limb by design. It maintains the asset's existing performance; it does not add to it.

Regulatory requirement

Under Ind AS 16 / AS 10, subsequent expenditure on PPE is capitalised only when it meets the recognition criteria of probable future economic benefit and reliable measurement. The standard explicitly treats the costs of day-to-day servicing as expense when incurred, describing them as primarily labour and consumables, possibly including small parts — this is the language auditors use to draw the line in practice.

Where the judgement actually sits

The principle is clean; invoices are not. In practice, the calls that take real judgement cluster into a handful of recurring patterns on a manufacturing or process client.

Repairs vs improvement: how the same account hides both
ScenarioUsual treatmentWhy
Replacing a worn component with an identical part, same capacityRevenueRestores original performance; no benefit beyond what the asset already provided
Replacing a component with a higher-capacity or longer-life versionCapital, to the extent of the incremental costFuture economic benefit beyond the original expectation — higher output or a longer remaining life
Overhaul of a major equipment item after several years of useCapital if it extends useful life materially; componentised and depreciated over the extensionA major overhaul is often economically closer to a part replacement than a repair, even when booked as one
Structural work to a leased or owned building — new flooring, partitioningCapital if it improves the asset or extends its life; revenue if it merely restores finishPainting and patching is revenue; a new roof or structural reinforcement is capital
Software licence renewal versus a new module with added functionalityRenewal is revenue; a functionally new module is capitalSame test applied to intangible assets under Ind AS 38 / AS 26
Mould or die replacement for an existing product lineCapital, as a separate short-life assetA distinct asset with its own useful life, often shorter than the parent machine's
Repairs vs improvement: how the same account hides both

Common practice, not a requirement

Many firms use a value threshold — for instance, treating repairs postings below a set rupee amount as revenue without individual review — as a practical filter to focus judgement on postings large enough to matter. This is a sampling convenience, not a rule in the standard, and it should be set and documented by the engagement team based on materiality, not applied as if it were authoritative.

Testing a sample of repairs and maintenance postings

  1. 01Pull the repairs and maintenance ledger, split by sub-headPlant and machinery repairs, building repairs, and vehicle repairs behave differently and should not be sampled as one pool. Sort each by value.
  2. 02Set a sampling threshold and select the large and unusual itemsSelect every posting above a materiality-linked threshold, plus any posting with a description suggesting scope beyond routine work — 'upgrade', 'replacement', 'new', 'overhaul', 'enhancement' are the words to search for in the narration field.
  3. 03Read the underlying invoice and work order, not just the voucher narrationThe GL narration is often abbreviated or copied from a prior entry. The vendor's invoice and, where one exists, the internal work order or purchase requisition usually describe the actual scope of work done.
  4. 04Apply the two-part test to the scope describedAsk whether the work restores the asset to how it already performed, or changes what it can do, how long it lasts, or how much it produces. Where an invoice mixes genuine repair with a capital component — a common pattern in overhaul invoices — split the two and capitalise only the capital portion.
  5. 05Cross-check against the capex budget and fixed asset additions for the same periodAn item that should have been capitalised sometimes appears nowhere in the additions schedule at all, because it was booked straight to the P&L account and never flagged. Comparing the repairs ledger against what was actually added to the register for the same assets in the same window surfaces this.
  6. 06Quantify and aggregate the misclassifications foundA single understated capitalisation might be immaterial; a pattern across several sites or several months, aggregated, often is not. Present the aggregate effect on profit, depreciation and the fixed asset note, not just the individual items.

The direction of the error that management is more likely to prefer depends on circumstances, but a company under pressure to show profit, or operating under a loan covenant tied to EBITDA or net worth, has an incentive to capitalise expenditure that should be expensed — it defers the hit to the P&L. A company closer to a tax deduction incentive, or one not under profit pressure, may lean the other way. Either direction is worth considering based on what the client's incentives actually are that year, rather than assuming one is more likely by default.

Recording the conclusion

  • The threshold and search criteria used to select the sample, and why they were set at that level.
  • For each item tested, the scope of work as described in the source document and the conclusion reached against the two-part test.
  • Any reclassification proposed to management, with the effect on profit, accumulated depreciation and the fixed asset note stated separately.
  • The aggregate effect of all misclassifications found, assessed against materiality, even where no individual item is material on its own.

How we think about this

Flagging every posting above a threshold, or every narration containing the word 'upgrade', is a search a rule can run across a full year's ledger without missing a row. Reading the invoice behind each flagged item and deciding whether the described work meets the recognition criteria is a judgement that has to stay with the auditor — the two tasks are different in kind, not just in difficulty.

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.

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.