MSP billing problem
NinjaOne Device Count Billing Discrepancies
NinjaOne device counts can create billing review questions when active endpoints, inactive devices, device classes, and PSA billing quantities do not line up before month-end invoicing.
Why this billing mismatch happens
RMM device counts can move quickly as endpoints are added, retired, renamed, reclassified, or moved between clients. PSA quantities may only be reviewed during billing cleanup, so the numbers can drift before invoices go out.
The difference does not mean every NinjaOne device should be billed. It usually means the team needs to review active status, device class, client mapping, service packaging, and the billing approach before changing quantities.
Common examples
NinjaOne shows active workstations that are not reflected in the PSA device service quantity
Inactive or retired endpoints still appear in a billed recurring quantity
Servers and workstations are counted together in one system but billed through separate PSA services
A device moved between clients and now needs mapping review before billing is trusted
Month-end device additions were not reviewed before the invoice quantity was approved
What to compare
NinjaOne active device and endpoint counts
Inactive, stale, duplicate, recently added, or recently retired devices
Workstation, server, laptop, and other device-class context
PSA agreement, service, product, or invoice quantities used for device billing
Client mapping between NinjaOne organizations and PSA companies
Manual review checklist
- 1
Start with the PSA device billing quantity planned for the invoice.
- 2
Open the matching NinjaOne client or organization and review active device counts.
- 3
Separate inactive, retired, duplicate, or stale records from the review count.
- 4
Check server, workstation, and device-class context against how the service is billed.
- 5
Confirm client mapping and decide whether the gap needs billing review or cleanup.
How BillingReconcile helps organize the review
BillingReconcile helps organize device-count review by keeping PSA billed quantities, NinjaOne source counts, client mapping, and device context visible for human review.
Compare PSA billed quantities against NinjaOne source counts
Review device-count gaps before invoice day
Keep active status, device class, and client mapping context visible
Separate billing issues from stale device cleanup
Related guides
Continue the billing review workflow
NinjaOne billing reconciliation
Review NinjaOne endpoint, device, client, and device-class counts against PSA billing.
Open guideNinjaOne + ConnectWise device reconciliation
Review NinjaOne device counts beside ConnectWise agreement and invoice quantities.
Open guideMSP device count reconciliation
Compare RMM, endpoint, server, workstation, and device counts against billed quantities.
Open guidePSA invoice quantity review
Review PSA agreement, service, product, and invoice quantities before invoices go out.
Open guideMSP billing review checklist
Use a practical checklist for mapping, count review, and final invoice review.
Open guideFAQ
Questions MSP teams ask
Review NinjaOne device-count gaps before invoice day
Use BillingReconcile to compare device counts against PSA billed quantities and keep client mapping context visible for review.