Key takeaways
- CARO 2020 clause 3(i)(a) asks whether the company keeps proper records with full particulars, including quantitative details and situation, so quantity, location and custodian are not optional columns.
- Keep the purchase date and the put-to-use date in separate columns: depreciation starts when the asset is available for use, not when the invoice is dated.
- Record only non-creditable taxes in cost. GST on which input tax credit is claimed stays out of the asset value in both books.
- Carry two depreciation trails: the Companies Act book per asset and the Income-tax block the asset belongs to, with opening balances at one cut-over date.
- A register is only as good as its totals: gross block and accumulated depreciation per class should agree with the audited Schedule III note.
On this page
Why the format matters
Section 128 of the Companies Act, 2013 requires every company to keep books of account that give a true and fair view of its state of affairs. For most organisations, the fixed asset register is the subsidiary record behind the property, plant and equipment figures in those books. If the register cannot explain the balance sheet, the balance sheet has no support.
Three readers look at the register, each with a different question:
- The statutory auditor reports under CARO 2020 clause 3(i)(a) whether the company maintains proper records showing full particulars, including quantitative details and situation of property, plant and equipment, and whether proper records of intangible assets are kept.
- The preparer of the financial statements needs the Schedule III fixed-asset note: gross block, accumulated depreciation and net block per class, with opening, additions, disposals and closing figures.
- The tax auditor needs the block-wise written-down value for clause 18 of Form 3CD, with additions split by whether the asset was used for 180 days or more in the year.
A register designed around those three questions rarely needs rework at year end. A register designed around whatever columns the first spreadsheet happened to have usually does.
The column groups at a glance
The groups below follow the asset import template that FixedAsset Pro publishes. The column names are the ones its importer recognises, so a register built this way can be loaded without remapping.
| Group | Typical columns | Who relies on it |
|---|---|---|
| Identification | asset_code, asset_tag, asset_name, description | Everyone; the code is the key that ties every record together |
| Classification | category, asset_type, asset_class_code | Accounts (Schedule III class), depreciation defaults |
| Make and model | manufacturer, brand, model, serial_number | Verification teams, warranty claims, insurers |
| Dates | purchase_date, invoice_date, capitalization_date, put_to_use_date | Depreciation start, 180-day test, ageing |
| Procurement | vendor, po_number, invoice_number, grn_number, quantity, unit | Auditors vouching additions |
| Cost build-up | purchase_cost, taxes, freight, installation_cost, other_cost, capitalized_cost | Gross block, GST treatment |
| Companies Act depreciation | residual_value, useful_life_years, dep_method, dep_rate | Schedule II computation |
| Organisation and place | branch, location, department, cost_centre, custodian, used_by, building, floor, room | CARO situation, physical verification, cost allocation |
| Cover | warranty_start, warranty_end, amc_end, insurance_end | Operations, claims, renewals |
| Status | status, condition, disposal_date, notes | Verification, disposals, impairment review |
| Opening balances | ca_cutover_date, ca_opening_accum_dep, ca_opening_nbv, it_cutover_date, it_block, it_opening_accum_dep, it_opening_wdv | Migration from an earlier register |
The core columns and why each matters
Not every column is equally important. The ones below are the minimum for a register an auditor can rely on. In the FixedAsset Pro template, asset_name, category, purchase_date, purchase_cost and location are mandatory; the rest are strongly recommended.
| Column | What goes in it | Why it matters |
|---|---|---|
| asset_code | A unique code per asset, such as FA-PM-000057 | The permanent key; never reuse a code after disposal |
| asset_tag | The number on the physical label | Links the label on the asset to the record during verification |
| asset_name | A short, specific name | A generic name such as 'Machine' cannot be matched on the floor |
| category | Category code or name | Drives the default useful life, method and Income-tax rate |
| serial_number | The manufacturer's serial | Proves the right unit was found, not a similar one |
| purchase_date | Invoice or purchase date | Vouching and procurement ageing |
| put_to_use_date | Date first available for use | Depreciation starts here; also decides the 180-day test |
| purchase_cost | Basic cost, excluding GST for which ITC is claimed | The base of gross block |
| taxes | Non-creditable taxes only (blocked GST, customs duty) | Prevents double benefit of ITC and depreciation |
| quantity and unit | 1 Nos, or a count for a pooled item | CARO asks for quantitative details |
| location and custodian | Where it is and who is answerable | CARO asks for situation; verification needs both |
| useful_life_years and dep_method | Life in years; SLM or WDV | Schedule II computation and the accounting policy note |
| it_block | The Income-tax block, such as PM15 | Tax depreciation is computed on blocks, not assets |
| status | Active, In Store, Under Maintenance, Missing, Disposed | Separates what should be counted from what should not |
Cost build-up
Split the cost rather than typing one total. Purchase cost, non-creditable taxes, freight, installation and other directly attributable costs each sit in their own column, and capitalized_cost is the check total. When an auditor asks why a machine costs more than its invoice, the answer is already in the row.
Two depreciation trails
The Companies Act book is computed asset by asset under Schedule II: useful life, a residual value normally not more than 5% of cost, and the company's chosen method. The Income-tax book under section 32 works on blocks of assets at prescribed rates. A register needs both: the life and method per asset, and the block each asset belongs to. You can check lives against the useful life table.
Location, custodian and cover
The words 'situation' and 'quantitative details' in CARO clause 3(i)(a) are why location and quantity belong in the register itself and not in a separate list kept by the administration team. A useful location column is specific enough for a person to walk to it: a branch, then a location code such as PUN-PLT-MS1, and where it helps, a building, floor and room.
The custodian is the person answerable for the asset. Where the user differs (a pool laptop issued to a trainee, for example), a used_by column keeps both. Department and cost centre let depreciation be charged to the right part of the business.
Warranty, AMC and insurance end dates are not accounting columns, but they are the ones operations teams open the register for. Keeping them in the same row means the register is used every month, not only at year end, and a register that is used is a register that is kept up to date.
Opening balances at cut-over
When you move from one register to another, pick a single cut-over date, normally the last audited balance sheet date. For each asset, record the accumulated depreciation in the Companies Act book up to and including that date. That is the closing figure of that year, not the opening column of the schedule.
For Income-tax, enter each block's written-down value at the cut-over date, taken from the closing figure of Form 3CD clause 18. Per-asset tax figures are useful but only indicative; the block figure is the one that carries forward.
Finally, total the gross block and accumulated depreciation per class and compare them with the audited Schedule III note. If the register does not agree with the audited totals, find the difference before you start depreciating, not after. The Excel migration guide walks through this step in more detail.
A sample row, worked through
Every figure in that row can be traced to a document: the invoice, the freight bill, the installation contract and the commissioning record. That traceability is what an auditor tests when vouching additions. To check the arithmetic for your own assets, try the Schedule II depreciation calculator.
Common mistakes
Purchase date used as the depreciation start
An asset bought in March but installed in June is not available for use in March. Under AS 10 and Ind AS 16, depreciation starts when the asset is available for use. Until then the cost sits in capital work-in-progress. A single 'date' column hides this; two columns expose it.
GST included in cost when ITC is claimed
Section 16(3) of the CGST Act denies input tax credit on the tax component if depreciation is claimed on it under the Income-tax Act. If the credit is taken, the GST must stay out of the asset cost in both books. Only blocked or otherwise non-creditable tax belongs in the taxes column. See the GST on capital goods guide.
Pooled items without a count
Twenty chairs bought on one invoice can sit on one row, but only with quantity 20 and a unit. Without the count, the auditor cannot test 'quantitative details', and a verification team cannot tell whether eighteen chairs is a shortfall. Keep pooling for genuinely low-value, identical items.
Missing or vague location
'Head office' is not a situation anyone can verify. A location code that a person can walk to, plus a custodian, turns the register into something that can be counted.
Reused or edited codes
Once a code is on a label and in the books, changing it breaks the link to past depreciation and verification. Retire codes with the asset; never recycle them.
Start from a free template
FixedAsset Pro publishes its asset import workbook on the templates page. It is an .xlsx file whose columns match the product's importer, with a row of notes under each header, dropdowns for fixed values, example rows, a sheet for Income-tax block opening values and a control-totals sheet for your audited Schedule III figures.
You can use the workbook as a register on its own. If you later move to the software, the same file loads through the import wizard, which checks every row in a dry run before anything is saved. For a fuller comparison of the two approaches, see Excel vs FixedAsset Pro.
General information, not tax or legal advice
How FixedAsset Pro handles this
FixedAsset Pro keeps these columns on one asset record and checks them on the way in.
- A register with code, location, custodian, cost and book value, saved filters and exports to Excel, CSV or PDF. Fixed Asset Management
- Import from Excel or CSV with a dry run, an error report and an all-or-nothing commit, including opening balances for both books tied to audited totals. Import templates
- Companies Act and Income-tax books out of the box, with depreciation pro-rata by day from the put-to-use date. Depreciation
- Over 140 built-in reports, including the depreciation register and the Schedule III fixed asset schedule. Reporting and Analytics
