New joiner Day 1. HR says the offer is active. IT’s spreadsheet still has last week’s batch. The laptop is in another city’s stockroom. Three weeks later the same employee resigns — last working day passes, SSO stays open, and the MacBook is “with a friend.” Nobody can prove custody. That is the joiner–mover–leaver gap between HR and ITAM.
Asset problems are usually identity problems
Separate IT asset tools track serial numbers well. They track people poorly. Employee location, band, manager and last working day live in HR. When those two systems disagree, you get delayed Day-1 productivity, ghost access after exit, and write-offs that finance discovers in year-end.
Mid-size Indian IT, SaaS and manufacturing teams feel this first: hundreds of laptops, phones and badges across cities, with exits every month. A Slack channel is not a lifecycle.
What a clean handover loop looks like
- Joiner: offer accepted → identity created → stockroom reservation → assignment with custody signature → access provisioned.
- Mover: department or site change → asset location and cost centre update without a new “shadow” record.
- Leaver: exit approved → return checklist → custody close → automatic access revoke on last working day.
- Audit: barcode / QR / RFID / NFC physical sweep proves the register matches the floor.
Who pays when HR and ITAM are separate
New joiners
Idle first week waiting for a machine that already exists in another tool.
Exit & security
Open accounts and missing devices after LWD — the expensive kind of “oops.”
IT ops
Duplicate directories, warranty chaos, and audits that take weeks of reconciliation.
Finance
Second SaaS bill plus unexplained asset write-offs every financial year.
Separate ITAM vs ITAM inside HRMS
| Moment | HRMS + separate ITAM | Native ITAM in HRMS |
|---|---|---|
| Day-1 laptop | Ticket + chase + delay | Assignment from same identity |
| Site / dept move | Two updates, often one missed | One change, both screens agree |
| Last working day | Manual revoke reminder | Exit-linked return + access release |
| Physical audit | Spreadsheet vs floor fight | Scan-backed custody trail |
IT asset management is not inventory theatre. It is custody tied to employment events. If assignment and revoke do not fire from the same join and exit records as HR, you own the gap — in rupees and in risk.
Questions to ask in the demo
- Create a joiner and show the asset assignment without leaving the HRMS.
- Run an exit to last working day — does access release without a separate IT ticket?
- Show procurement → GRN → assignment → disposal in one lifecycle.
- Scan a device and prove GPS-tagged audit history.
Bynarize IT Asset Management (17 sub-modules) shares identity, RBAC and notifications with Core HR and Exit — so Day-1 and Day-last stop being two different companies.
For IT heads and founders: every missing laptop after an exit was predictable. Wire assets to joiners and leavers, or keep paying for the reconciliation tax.
See joiner → laptop → exit revoke in one flow
Assignment. Return checklist. Access release. Thirty minutes.
