Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How Do We Keep Our MSP's Client Asset Lists Matching What Is Actually on the Network?
Problems We Solve

How Do We Keep Our MSP's Client Asset Lists Matching What Is Actually on the Network?

MSP asset lists in the PSA, RMM and documentation tool disagree, so billing and support suffer. We build a nightly reconciliation of every client's devices.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Most MSPs keep client devices in three places, the RMM, the PSA configuration items and the documentation tool, plus a seat count on the contract, and each drifts differently. We build a nightly reconciliation that compares all of them per client, lists devices missing from one or more, spots offline or retired machines still counted, and feeds the corrected count into billing.

Three lists, three answers

Ask how many devices a client has. The RMM says forty-one agents, four of them offline for months. The PSA has thirty-eight configuration items, including two laptops that were replaced last year. The documentation tool lists thirty-five, because nobody updated it after the last refresh. The contract bills for thirty-six devices, the number agreed at onboarding.

Each list is right about something. None of them is right about everything. When the engineer is on a call about 'Sarah's laptop', they check the wrong asset. When the account manager prepares renewal, they use the contract figure. And the security tool is licensed on yet another count.

How the lists drift apart

Every tool is updated by a different event, and none of them notices when the others change.

  • New devices get an RMM agent but no PSA record.
  • Retired devices are unplugged but never removed from the RMM or documentation.
  • Replacements are recorded as new devices without the old ones closed off.
  • Devices change owner when staff leave, and the user field stays the same.
  • The contract seat count is only updated at renewal.

Clients add to it themselves. A manager buys a laptop on a company card, a member of staff connects a personal device to the tenant, a new site gets a printer the MSP never heard about. Each is legitimate from the client's side and invisible from yours until something breaks.

What drift costs you

DriftEffect
Unbilled devicesManaged and licensed but not charged for
Retired devices still countedSecurity and RMM licences paid for dead machines
Devices without agentsUnpatched machines nobody is watching
Wrong owner recordedSlower support and confused tickets
No trustworthy countArguments with clients at renewal

The nightly reconciliation we build

  1. A nightly pull of devices from your RMM (NinjaOne, Datto RMM, N-able or similar), PSA configuration items, documentation tool and, where relevant, Microsoft Intune or the tenant's device list.
  2. Matching rules on serial number, hostname and MAC address, so the same device is recognised across tools even when names differ.
  3. A per-client exceptions list: in RMM but not PSA, in PSA but not RMM, offline beyond a threshold you set, duplicates, and devices with a user who has left.
  4. One-click fixes where the tool allows, such as creating the missing PSA configuration item or archiving a retired device, always with a person confirming.
  5. A reconciled device count per client, compared with the billed count on the contract.
  6. A monthly summary for account managers of changes in each client's estate.

What the service desk and billing see

Each morning, the service coordinator works through a short exceptions list rather than discovering problems mid-call. Devices that went offline months ago are confirmed as retired and removed from the RMM and security licensing. New laptops that appeared overnight get their PSA records. The count billed each month is the reconciled count, or the difference is flagged for the account manager to decide under the contract.

Engineers trust the asset records again, because they match what is actually there.

Hardware refreshes are where the difference shows most. When a client replaces a batch of laptops, the new machines appear in the RMM as their agents go on, and the old ones start ageing on the offline list. The reconciliation pairs them up by user, prompts the engineer to confirm each old laptop as retired, wiped or reassigned, and closes the old records across every tool in one pass. Without it, the old laptops tend to live on in the documentation for years and keep drawing a security licence each month.

It also helps with the security tools that bill per device. The reconciled count gives you a single number to compare with the endpoint protection and backup consoles, so a licence paid for a machine that no longer exists is spotted within days rather than at the annual true-up.

Signs your asset lists have drifted

  • Your RMM, PSA and documentation disagree on device counts.
  • You pay for security licences on machines that no longer exist.
  • Devices appear on the network with no PSA record.
  • Contract device counts are only updated at renewal.
  • Engineers regularly look up the wrong device for a user.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Will it delete devices automatically?

No. It proposes changes and a person confirms them. Nothing is removed without a decision.

Does this change what we bill clients?

It gives you an accurate count. Whether and how that changes billing depends on your contracts.

How does it match devices with different names?

Mainly on serial number, which rarely changes, with hostname and MAC address as backups.

What if we only use two tools?

It still helps, and it is simpler to build. We will tell you if the drift is small enough not to need it.

What affects the cost?

Mainly the number of tools to reconcile and the quality of the serial number data in each.

Keep reading

More on Problems We Solve

Start here

Tell us where your MSP loses time between the PSA and the invoice

Describe the tools you run (PSA, RMM, documentation, distributor portals) and the step that is still done by hand. We will tell you what we would build on top of them, and if a setting or integration you already pay for would do the job, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →