In production

IntegralDots AssetSense Assets register automation

AI agents that keep the asset register in step with what you own.

AssetSense runs AI agents that find assets across your systems, compare the register with every source, and propose a fix when they disagree. A person approves each change. Every asset keeps its owner, its location and a full history, and the year-end count and the audit start from a register that is already reconciled.

  • ComparesERP, CMDB, discovery, HR and procurement
  • RunsInside your network or private cloud
  • ChangesProposed by agents, approved by people
  • Built forFinance, IT asset and facilities teams
AssetSense overview of a bank's fixed asset register: 48,312 assets worth SAR 1.27 billion, a map of the Kingdom with sites sized by asset count and the sites where the agents found something this week, five findings with the book value affected, value by asset class, and the share of the register confirmed by a second system against a 98% target
  1. The register at a glanceNumber of assets, net book value and the share confirmed by a second system, with the changes waiting for approval.
  2. Sites across the KingdomEach site is sized by its asset count. Amber dots mark the sites where the agents found something this week.
  3. Found this weekEach finding in plain words, with the book value affected. Review opens the changes waiting for approval.
  4. Accuracy against targetThe share of the register confirmed by a second system, month by month, against the 98% target.

Product screens show demo data.

Why it matters

Most asset registers start to drift the day they are signed off.

The register lives in the ERP. The facts live elsewhere: network scans, the service desk, HR leaver lists, branch transfer forms, purchase orders and invoices. Teams close the gap once a year with exports, spreadsheets and a physical count, and it opens again the next morning.

  • Spreadsheet reconciliationEvery count means exports from several systems, matched by hand on tag and serial number, in workbooks only one person understands.
  • Ghost and missing assetsDisposed equipment keeps depreciating, while equipment bought on an invoice never reaches the register.
  • Stale ownershipPeople leave, branches refit and equipment moves, but custodians and cost centres stay as they were.
  • Audit pressureAuditors ask who changed what, when and on what evidence. The answer sits in email threads and old workbooks.
How it works

How the agents keep the register current.

Agents do the reading, matching and drafting. Your finance and asset teams keep every decision.

  1. Connect

    Read-only links to the ERP fixed-asset module, CMDB, endpoint and network discovery, procurement, HR and facilities systems.

  2. Discover

    The discovery agent finds assets in each source, including ones the register has never seen, and matches them on tag, serial, invoice and location.

  3. Reconcile

    The reconciliation agent compares every asset with every source, on the schedule you set, and raises a finding where they disagree.

  4. Propose

    For each finding an agent drafts the fix (add, transfer, reassign, retire, merge or correct) with the evidence attached.

  5. Approve and record

    People approve under your maker-checker rules. Approved changes are posted to the register and added to the asset's history.

Capabilities

What the agents cover.

Discovery

Find what the register is missing

Agents read discovery scans, the CMDB, purchase orders and invoices, and draft register entries for assets that were bought or installed but never recorded.

Reconciliation

Checked on the schedule you set

Every asset is checked against every connected source. Differences in location, serial, custodian, status or cost become findings, ranked by value.

Lifecycle

From purchase order to disposal

Requests, receipts, capitalisation, transfers, counts and disposals form one lifecycle, each step linked to the document behind it.

Ownership

Owners and custodians that stay current

Leavers, branch moves and cost-centre changes are picked up from source systems, and reassignments are proposed before assets go unaccounted for.

Approvals

People approve every change

Maker-checker rules by asset class and value. Agents never change the register on their own, and every decision records its reviewer.

Reporting

Reports for finance and audit

Attestation packs, reconciliation status, open findings and full change history, exported for finance, internal audit and external auditors.

Inside the product

What finance and asset teams see.

AssetSense approvals: 18 changes waiting with SAR 312,400 of book value affected, an ATM transfer showing the register before and after approval with its evidence and Approve and Reject buttons, two smaller cards for a new firewall and 14 retired laptops, and a side panel with changes approved this month, time to a decision and changes waiting by type

Approvals with the evidence attached

Every change an agent proposes reaches the approver with the register values before and after, and the documents behind it. The decision is made on the card.

  1. Waiting for youChanges waiting, the book value they affect and how long the oldest has waited.
  2. Before and afterThe register today and after approval, field by field, with the changed values highlighted.
  3. EvidenceThe documents and system readings that support the change, in plain words.
  4. Approve or rejectOne decision per card, with the due date. Nothing is posted to the ERP before approval.
  5. Time to a decisionChanges approved this month and the average time to decide, compared with approval by email.
AssetSense page for one ATM: bought for SAR 168,000 and worth SAR 92,750 today, book value over its life against the cost to replace it, a timeline of six events from purchase to planned replacement with the document for each, the asset details, and next steps with an Approve button

The story of one asset

Open any asset to see what it cost, what it is worth today, what happened to it and the document behind each event.

  1. Cost and valueWhat the asset cost, what it is worth today and how much useful life is left.
  2. Value over its lifeBook value from purchase to the end of its useful life, against the cost to replace it.
  3. Its storyPurchase, service, count, value review and transfer in date order, then the planned replacement.
  4. DocumentsEach event links to its document: order and invoice, service report, count photo, review memo, transfer form.
  5. Next stepsWhat still needs doing on this asset, by whom and by when.
Security & deployment

Runs inside your boundary.

Asset records hold locations, people and values. They stay in your environment, under your access rules and your records policy.

Deployment

  • Your data centre or private cloud tenancy
  • Agents run in your environment, against your own systems
  • Read-only connections to source systems by default
  • High-availability setup with health checks and alerting

Security

  • Single sign-on with your identity provider and role-based access
  • A least-privilege service account for each source system
  • Encryption in transit and at rest
  • Values and personal data visible only to the roles that need them

Governance

  • Maker-checker approval by asset class and value
  • Agents can propose changes; only approved changes are posted
  • Every finding, proposal and decision logged with its evidence
  • Retention that follows your records policy

Integration

  • ERP fixed-asset modules through APIs, database views or file exchange
  • CMDB, service desk, endpoint and network discovery tools
  • HR, procurement and facilities systems for ownership and lifecycle events
  • Exports to finance reporting and audit tools
Designed around
  • PDPL data handling
  • SAMA Cyber Security Framework controls
  • IAS 16 asset records
  • SAML and OpenID Connect SSO
FAQ

Questions finance and asset teams ask

Does it replace our ERP fixed-asset module?

No. The ERP stays the book of record for cost and depreciation. AssetSense keeps it accurate: it finds differences, proposes corrections and, once a person approves them, posts them through the integration you choose.

Can the agents change the register on their own?

No. Agents read sources and draft changes with the evidence attached. A person approves every change under your maker-checker rules, and the reviewer, time and evidence are logged.

Which systems can it compare?

Any system that holds a fact about an asset: the ERP, CMDB, service desk, endpoint and network discovery, ATM and device monitoring, procurement, HR and facilities. Connections are read-only by default, through APIs, database views or file exchange.

Do we still need a physical count?

For assets no system can see, such as furniture or generators, yes. AssetSense points counts at the assets with the weakest evidence and records the result, so a count can cover only those assets.

How does a rollout usually start?

With one asset class, such as IT hardware or ATMs, and two or three sources. Most of the effort goes into agreeing matching rules and approval thresholds with finance; more classes and sources follow.

See your register reconciled.

Book a demo, or ask about a pilot on one asset class to see the findings the agents raise against your own sources.