Sign in Start free trial
IT

IT Asset Management

Track every device and licence from purchase to disposal and the ledger.

IT asset management keeps one register of hardware, software licences and SaaS apps, linked to purchasing, people and finance. It tells you what you own, what you are short of and what to take back, and counts savings only when an invoice proves them. IT prepares the money entries; Finance approves and posts them.

42 features available 7 planned 8 capability areas
Highlights

What stands out

Purchase to ledger, tied out daily

A daily three-way check catches received-but-not-registered and cost mismatches before the auditors do.

Savings you can prove

Savings count only when the invoice shows them, so the number is credible.

Licence position at a glance

Owned against deployed per product shows the shortfall and its cost.

Leaver take-back

When someone leaves, the device and seats are recovered on a schedule.

Shadow IT found

Apps nobody sanctioned appear from sign-on and spend.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Hardware register

Every laptop, phone, server and screen, from order to disposal.

11 features
  • One asset, one tag, one itemEach physical asset has one row, one tag and one configuration item that follows its state, holder and place.
  • Lifecycle statesOn order, in stock, assigned, in repair, retired and disposed, with every move written to an append-only history.
  • Unique serial numbersA serial is registered once; a duplicate in any letter case is refused.
  • Refresh datesThe refresh date comes from the class's cycle and the purchase date.
  • Assignment to a workerAssign from stock to a person picked from Human Capital; leavers and unknown people are refused.
  • Leaver take-backA leaver event opens a take-back task per reclaimable device, due after a grace period; recovered or waived by a person.
  • Received goodsGoods received in Procurement arrive as pending lines with the order's price; register them by serial number, partly if the delivery is partial, or record a return to the vendor.
  • Stock rooms and auditsAudit a room by scanning tags or serials; missing, extra and in-another-room differences are listed and nothing changes until a person resolves each.
  • Asset classesClasses say whether an asset holds data, its refresh cycle and its fixed asset class.
  • Contract facts into assetsExecuted IT contracts publish vendor, product, term and renewal as facts that assets link to.
  • Device feed matchingDiscovery and device management feeds update the register on an exact serial match and propose uncertain matches.

Disposal

Retire hardware with a wipe record and the right approval.

4 features
  • Wipe certificateRecord how and when data was wiped; disposal is blocked without it for classes that hold data when the company requires it.
  • Threshold approvalSmall-value disposals are approved by an IT manager; larger ones go through workflow; the requester never approves.
  • Carry out and hand to FinanceA person carries out the approved disposal and the Fixed Assets disposal request is prepared.
  • Gain or loss copied backFinance's carrying amount and gain or loss on disposal are shown next to the disposal.

Purchase to ledger money chain

One chain from the purchase to the asset to depreciation to disposal.

5 features
  • Send to FinanceA costed asset is registered in Fixed Assets and a capitalisation is prepared; a person in Finance approves and posts it.
  • Transfers and impairmentsPrepare a transfer between companies or an impairment from the asset; Finance posts.
  • Daily three-way tie-outEvery morning compares the purchase, the asset register, the fixed asset register and the ledger and lists breaks; it only reads and reports.
  • IT never posts moneyIT prepares; a different person in Finance approves and posts through the ledger's one posting path.
  • Landed cost allocationPlannedFreight and landed costs added to an asset's cost; today assets are registered at the order's unit price.

Software licences

Know what runs, what you own and where you fall short.

9 features
  • Rule packs for major publishersRules are an estimate, not audit advice.
  • Name normalisationRaw install names become publisher, product, edition and version; unknown names wait in a queue with a suggested mapping for a person to confirm.
  • Installs from device sourcesInstalls arrive from agents, device management or the configuration database; re-sends are harmless.
  • Entitlements from contractsExecuted contracts add their licences by themselves and amendments update the same record.
  • Counting methods
  • Licence positionOwned against deployed per product, with the shortfall, surplus and what a shortfall would cost.
  • Append-only mapping historyEvery mapping decision is audited and kept in an append-only history.
  • One position figure everywhereThe screen,  AI, the API and reports read the same licence position calculation.
  • Usage readingsUsage readings support peak concurrent counting and finding unused seats.

SaaS discovery and spend

Find the apps people use and what they cost, including those nobody approved.

6 features
  • Discovery from sign-onFind apps from your single sign-on provider, supplier invoices and card purchases.
  • Spend matchingCertain matches are made; uncertain ones are suggested for a person to confirm, assign or ignore.
  • Shadow IT flagsFlag unsanctioned apps; a person sanctions or retires them.
  • No stored credentialsA source names its saved connection; no secret is stored in the asset module.
  • Duplicate app flagsDuplicate and unsanctioned apps are flagged using a directory of known SaaS vendors.
  • Spend from supplier bills and cardsSpend reads posted supplier bills and card purchases, with credits counted negative.

Reclaiming seats and licences

Take back what nobody needs, and count only the savings an invoice proves.

5 features
  • Reclaim proposalsDaily proposals for leavers' seats and for seats unused for a set window.
  • Submit, approve, carry outOne person submits, another approves through workflow, and a person carries it out.
  • Proven savingsA saving is counted only when a later invoice shows the lower amount; the rest is a forecast.
  • Renewal visibilitySee what renews in the coming weeks.
  • Seat releaseRelease a seat through the directory when connected, or remove it at the vendor with the screen saying so.

Contracts, vendors and costs

6 features
  • Vendor management and renewalsPlanned
  • IT cost showback and chargebackPlannedAllocate IT cost to business units and post to the ledger.
  • Hardware in the public APIPlannedRead the hardware register through the public API.
  • Renewal workflow with usage evidencePlannedA renewal clock with an owner task, usage evidence from the licence position and a decision to renew, renegotiate, cancel or replace.
  • Commitments and true-upsPlannedTrack cloud and enterprise agreement commitments, consumption and true-up dates.
  • IT budget against actualPlannedCompare IT budget with actual by category, reading from the finance planning hubs.

Settings and governance

Safe defaults for every policy.

3 features
  • Policy settingsDisposal threshold, audit cycle, reclaim grace, wipe requirement, tie-out tolerance and grace, and the default fixed asset class, each with a safe default.
  • Separation of dutiesAsset manager, IT manager and finance rights are separate; preparers never approve.
  • Software add-on licenceSoftware and SaaS is a separately licensed part of the hub.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Find assets, goods waiting to be registered, devices due back, stock rooms, audits, disposals and the latest tie-out
  • Prepare registering an asset or received goods, assigning, taking back, repair, retiring, linking a contract (ready for confirmation)
  • Start and count an audit; run the tie-out
  • Prepare a draft disposal
  • Answer: where are we short of licences, which install names are waiting, which apps are shadow IT, what renews soon, what can we reclaim, how much have we really saved
  • Add a product, entitlement or app, read spend, and propose a reclaim
  • Never: submit, approve or carry out a disposal or reclaim, record a wipe certificate, send cost to Finance, capitalise, transfer, impair, post, confirm a mapping or sanction an app.
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to IT Asset Management.

Workflow

Disposals above a threshold and reclaim requests go through the shared workflow module; the requester is never the approver.

  • Disposal above the threshold approved through the authority matrix
  • Small disposal approved by the IT manager
  • Reclaim request approved by an IT manager other than the submitter
  • Capitalisation approved and posted in Fixed Assets by a person other than the preparer

Reporting and analytics

Asset, licence and spend views on the shared reporting module; savings shown as proven or forecast.

Datasets

Hardware assetsSoftware installs and entitlementsSaaS apps and spendReclaims and proven savingsTie-out results

Dashboards

Asset register healthLicence positionReclaim and savings

Integration

Software installs and SSO accounts arrive through data integration feeds; asset changes publish events that the configuration database adopts.

Data integration feeds itam.software_installs and itam.saas_accounts

Events

Asset change events consumed by the configuration databaseContract executed events from Contract Lifecycle

Connectors

OktaGoogle WorkspaceIntuneJamf

Migration

Fixed-asset registers have a migration slot that is not yet built; asset import uses the data import tools.

  • Fixed-asset registers and depreciation historyplanned
  • Data import (CSV)available
Mobile

On the phone

Planned on the single  AI phone app (for example scanning tags in a stock audit). Not available yet.

Who uses it

IT asset managerIT managerFinance and controllerService desk agentService ownerAuditor
Questions

Frequently asked

Does IT asset management post to the ledger?

No. It prepares requests; Fixed Assets and the ledger post, and a different person approves.

Can the same serial number be registered twice?

No.

How are savings counted?

Only when a later invoice shows the reduced amount; the rest is a forecast.

Which software publishers are covered?

They are an estimate, not audit advice.

What happens when someone leaves?

Take-back tasks open for devices and reclaim proposals for seats, due after a grace period.

Can a disposal happen without a wipe?

Not for classes that hold data when the company requires a wipe record, which is the default.

See IT Asset Management on  AI

Talk to us