Moving your asset register from Excel

A spreadsheet is a perfectly good first register. It becomes a risk when the register has to do more than list assets. Some signs that point to a move:

• Depreciation for the two books lives in separate workbooks, and the year-end reconciliation between them takes days.
• Formulas have been copied, overwritten or extended by hand, and nobody is fully sure which rows a total covers.
• Transfers, disposals and custodian changes are recorded by editing the row, so the history of how an asset got where it is has gone.
• The auditor asks who changed a cost or a date and when, and the file cannot say.
• Physical verification is a printed list ticked by hand and keyed back in.
• Several people need the file at once, and copies start to drift apart.

None of these is a crisis on its own. Together they make the year-end slower and the audit file weaker. If you want a side-by-side view, see Excel vs FixedAsset Pro.

An asset row refers to other lists: branch, location, department, cost centre, category, vendor and custodian. Build those lists first and import them before the assets. In FixedAsset Pro the masters can be imported together in one transaction, and the server orders them for you: branches, departments, cost centres, categories, vendors, locations, then employees.

• Codes are unique per master, up to 20 characters, using letters, digits and - _ / . only.
• Categories carry the Companies Act defaults (useful life, method, rate) and the income-tax block rate. Agree these with your accountant before import, because blank values on an asset row take the category default. The useful life table lists the Schedule II lives.
• Vendors carry GSTIN and PAN; both are format-checked, and the PAN must match characters 3 to 12 of the GSTIN.
• Locations should be places a person can walk to and scan, such as a room or a bay, not just a city.

Download the free Masters and Assets templates, or keep your own column headings and map them once in the import wizard; the mapping is saved for the next file.

Duplicates

Sort by serial number, then by tag, then by invoice number and amount. The same laptop entered twice, once by IT and once by finance, is a common pattern. Keep one row and record the other tag as history.

Missing put-to-use dates

Depreciation in the books starts on the date the asset is available for use, and the income-tax 180-day test depends on the date it is put to use. If only the purchase date is known, find the installation report, goods receipt or commissioning note. An asset bought but not yet installed belongs in CWIP, not in the register.

Pooled items

Registers often hold rows such as "20 office chairs". Decide, with your auditor, which pooled rows stay as one record with a quantity and which are split into individual assets that will each carry a tag. Either way, the quantity, unit and location must be clear: CARO 2020 clause 3(i)(a) asks for quantitative details and situation.

Locations and custodians

Replace entries such as "Head office" or "with IT" with a location code and a named custodian where one exists. These fields drive the first verification, so vague entries now mean an untidy count later.

Dates and amounts

The importer reads dates day first (03/04/2024 is 3 April 2024) and accepts Indian grouping such as ₹12,40,000. Negative amounts are not allowed; disposals are recorded with a status and a date, not a minus sign.

The cut-over date is the date up to which depreciation has already been charged in the old register. FixedAsset Pro computes depreciation only for periods after it, and the same date must be used on every row.

The natural choice is the last audited balance sheet date, for example 31 March 2026. The opening figures can then be tied to signed financial statements and a filed tax audit report, rather than to management numbers that may still move. Transactions between that date and the go-live date (additions, disposals, transfers) are then entered in the new system as ordinary transactions, so they carry their own documents and audit trail.

Tax depreciation is computed on blocks of assets under section 32, so the authoritative opening figure is the block WDV in clause 18, entered on the IT_Block_Opening sheet of the template. Assets bought after the cut-over date carry no accumulated depreciation. Disposed assets are imported only if you want their history, with status Disposed and a disposal date; they are left out of the opening balances.

On the Control_Totals sheet, enter gross block and accumulated depreciation for each category from the audited Schedule III note, plus a total row. The preview shows the difference between those totals and the imported register, and the import stays blocked until they agree within ₹1.

Every upload first goes through a dry run. It checks every row and produces a downloadable error report. Errors block the import; warnings do not. The commit is all-or-nothing: if any row has an error, nothing is saved, so the register is never partly loaded. Fix the rows, upload again and repeat until the preview is clean.

Tie the income-tax side the same way: the total of the block WDVs entered must equal the closing WDV total in clause 18 of the cut-over year.

Once the register is committed, generate tags for assets that do not have one and print labels on your own label sheets. The QR label generator shows the idea; inside the product the first scan confirms that a tag is in use.

Then run a first physical verification, scoped by branch and location. It is the quickest way to find what the spreadsheet got wrong: assets found elsewhere, custodian mismatches, items that are missing, and assets on the floor that were never in the register. Resolve each item through a transfer, a recovery or a write-off proposal, so the corrections carry their own documents. See physical verification.

For the order of work across the whole implementation, see the getting started guide.