What is device count reconciliation?

It is the process of comparing billed device quantities against source systems that show active endpoints, servers, workstations, protected devices, or managed devices.

Which device sources should MSPs compare?

Common sources include RMM, MDM, backup, endpoint security, and device management systems. The right source depends on how the service is billed.

Does every stale device mean the client is overbilled?

No. A stale device can indicate overbilling, cleanup work, client mapping issues, or a device lifecycle question. The team should review context before changing billing.

Does BillingReconcile replace the RMM?

No. BillingReconcile uses connected source data for billing review. It does not replace the operational tools that manage devices.

Workflow guide

MSP Device Count Reconciliation

Device count reconciliation helps MSPs compare billed endpoint, workstation, server, backup, or security quantities against the systems that show current devices.

Book a Demo View NinjaOne Guide

The billing issue

Device-based services are easy to underbill or overbill when endpoints are added, retired, renamed, duplicated, or moved between clients. PSA quantities can lag behind the RMM, security, backup, or management system that shows the current device footprint.

A device reconciliation workflow compares the billed quantity against the source count and keeps exceptions visible for review.

Common examples

Managed endpoints are active in an RMM but missing from billed quantities

Decommissioned or stale devices remain in recurring billing

Servers and workstations are billed under the wrong service type

Client-device mapping is incomplete or assigned to the wrong PSA account

Backup or security coverage differs from the billed device count

How MSPs typically review it manually

1
Export PSA service quantities for endpoint, backup, security, or managed device services.
2
Open RMM, MDM, backup, or security tools to count active devices.
3
Confirm which devices belong to which client and billing model.
4
Separate stale devices from active billable endpoints.
5
Review count differences before updating invoice quantities.

How BillingReconcile helps organize the review

BillingReconcile helps organize device count differences in one review workspace. The team can compare billed quantities against connected device counts, review client mappings, and decide whether a discrepancy reflects billing, setup, or stale data.

Compare device counts against mapped PSA billing items

Surface missed endpoints, stale devices, and mapping gaps for review

Keep service and client context visible beside the count difference

Support review before invoices are finalized

Related guides

Continue the billing review workflow

NinjaOne + ConnectWise device reconciliation

Compare NinjaOne device counts against ConnectWise billed device quantities.

Open guide

NinjaOne device count discrepancies

Review active devices, inactive endpoints, device classes, and PSA quantity drift.

Open guide

NinjaOne billing reconciliation

Compare active endpoints and client-device mappings against billed quantities.

Open guide

FAQ

Questions MSP teams ask

Review device counts before invoice day

Compare billed endpoint quantities against connected device counts and keep exceptions visible for human review.

Book a Demo View NinjaOne Guide