If your Fixed Asset Register (FAR) is causing problems during statutory audits, there is a good chance the real issue is not missing assets — it is incorrect Parent-Child Asset Mapping. After conducting hundreds of asset tagging and physical verification projects across India, our team at TagMyAssets has seen this mistake repeated in manufacturing plants, hospitals, IT offices, and warehouses alike.
This guide explains everything you need to know about Parent-Child Asset Mapping in plain language — with real examples from our verification projects.
What is Parent-Child Asset Mapping?
In simple terms:
- A Parent Asset is a main asset — for example, a Generator.
- A Child Asset is a component attached to it — for example, the Battery, Control Panel, or Exhaust System of that same Generator.
The relationship between them in your FAR and asset tagging system is called Parent-Child Asset Mapping.
1. Most Indian Companies Are Mapping Assets Incorrectly
In a recent fixed asset verification project at a manufacturing plant in Pune, we found that the company had tagged every component of a CNC Machine as a separate, standalone asset — each with its own FAR entry, individual depreciation schedule, and separate insurance value.
The result? The FAR showed 47 assets. The physical count showed 1 machine with 47 components. The auditor raised a query. The finance team spent three days explaining.
This is not an isolated case. It is one of the most common problems we see during physical verification across India.
2. Wrong Mapping Inflates Your Fixed Asset Register
When components are entered as separate assets instead of child assets under a parent, your FAR becomes artificially inflated. This creates three serious problems:
- Depreciation is calculated incorrectly — you may be claiming more or less depreciation than you are entitled to.
- Insurance premiums are overstated — you are paying to insure components that are already covered under the parent asset policy.
- Auditors raise queries — because the physical asset count never matches the FAR count.
3. There is No Universal Rule — Industry Context Matters
One of the most common questions we get during asset tagging projects is: when should a component be a child asset versus a standalone asset?
The answer depends on three factors:
- Can the component function independently? A UPS battery that works across multiple machines should be a standalone asset.
- Does the component have its own useful life and depreciation rate? If yes, it may need its own FAR entry.
- Is the component permanently attached? A permanently fixed control panel is a child asset. A portable scanner used with multiple machines is not.
4. CARO 2020 Requires You to Get This Right
Under the Companies (Auditor’s Report) Order 2020, auditors must specifically report on whether your company maintains proper records showing full particulars — including quantitative details and the situation of fixed assets.
If your Parent-Child mapping is incorrect, your FAR does not reflect reality. This means:
- Your statutory auditor will flag it in the CARO report.
- Your management letter may contain adverse observations.
- Board and investor scrutiny increases.
5. ERP Systems Make the Problem Worse if Not Configured Correctly
Many companies use SAP, Oracle, or Microsoft Dynamics to manage their Fixed Asset Register. These ERP systems support Parent-Child asset structures — but only if they are configured correctly from the start.
In one hospital verification project in Delhi NCR, we found that the ERP had been set up with every medical equipment component entered as an individual asset. The CT Scanner — which should have been one parent asset with six child components — was showing as seven separate assets in SAP.
Fixing this required a complete FAR restructuring exercise before tagging could even begin — adding two full days to the project timeline.
6. Physical Verification Reveals the True Mapping — Not Your FAR
The FAR tells you what is supposed to exist. Physical verification tells you what actually exists.
During our Sheet-to-Floor and Floor-to-Sheet verification process, we physically inspect each asset, identify its components, and map the correct Parent-Child relationship based on what we see on the ground — not what the ERP says.
This ground-level verification is the only reliable way to correct faulty asset mapping. Software alone cannot do this — it requires trained field teams who understand asset classification.
7. Fixing It Is Easier Than You Think — If You Do It Before the Audit
The biggest mistake companies make is waiting until the auditor raises a query before fixing their Parent-Child mapping. By then, the damage is already done.
If you act before your next statutory audit, the fix involves three steps:
- Physical Verification — Identify what assets and components actually exist on the ground.
- FAR Restructuring — Reclassify components into correct Parent-Child relationships in your asset register.
- Asset Tagging — Tag each parent and child asset with unique QR codes or barcodes so the physical asset and digital record are permanently linked.
Quick Reference: Parent vs Child Asset
| Factor | Parent Asset | Child Asset |
| Example | CNC Machine, Generator, CT Scanner | Control Panel, Battery, Imaging Head |
| FAR Entry | Separate entry with full value | Linked under parent entry |
| Depreciation | Own schedule | May share parent schedule |
| Asset Tag | Unique QR / Barcode | Unique QR / Barcode with parent reference |
| Can work alone? | Yes | Usually No |
Is Your Parent-Child Asset Mapping Causing Audit Problems?
TagMyAssets specialises in physical asset verification, FAR restructuring, and asset tagging across PAN India. Our field teams have worked with manufacturing companies, hospitals, IT offices, and warehouses to fix exactly these problems — before the auditor finds them.
Contact us today for a Free Consultation: connect@tagmyassets.com | +91 96500 03293 | tagmyassets.com
TagMyAssets | Fixed Asset Verification & Tagging Services | PAN India | tagmyassets.com
