MSP billing problem
User Count vs License Count Billing for MSPs
User counts and license counts are not always the same billing signal. MSP teams often need to review both before deciding how a service should appear on an invoice.
Why this billing mismatch happens
A client may have more licenses than users, more users than billable licenses, or several licenses assigned to the same user. The right invoice quantity depends on the MSP's billing policy, service packaging, and source system being reviewed.
This page is not legal or accounting advice. The practical goal is to separate count review from billing policy decisions so the team can confirm what should be included before invoice day.
Common examples
One user has multiple licenses tied to different services or bundles
A source system shows unassigned licenses that still need invoice review
Shared or service accounts appear in user lists but are billed differently by the MSP
A bundled service is billed per user even though several underlying licenses are present
The PSA quantity reflects a service package while the source system reports individual license counts
What to compare
User counts from the source system used for the service
License, subscription, SKU, seat, or entitlement quantities
Assigned, unassigned, suspended, shared, or service-account context
PSA agreement, service, product, and invoice quantities
Service packaging and billing policy the MSP uses for that client
Manual review checklist
- 1
Identify whether the client service is billed per user, per license, per bundle, or another agreed approach.
- 2
Compare source user counts against source license or subscription counts.
- 3
Separate assigned licenses from unassigned or unusual account patterns where the source allows it.
- 4
Review PSA quantities against the count type the service is supposed to use.
- 5
Document whether the issue is a billing decision, mapping cleanup, or source-count review item.
How BillingReconcile helps organize the review
BillingReconcile helps organize the count comparison by keeping source counts, PSA billed quantities, and mapping context visible. The MSP team still decides how each service should be billed.
Review license count mismatches without assuming a single billing policy
Keep user, license, SKU, and service context visible
Compare PSA billed quantities against the selected source counts
Surface billing mismatches for human review before invoices go out
Related guides
Continue the billing review workflow
Pax8 billing reconciliation
Review Pax8 subscription, SKU, tenant, and license quantities against PSA billing.
Open guideConnectWise billing reconciliation
Review ConnectWise agreement, service, product, and invoice quantities against source counts.
Open guideMSP license count reconciliation
Compare license, subscription, user, and seat 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 guides
Browse practical billing review guides for license, device, PSA, and count mismatches.
Open guideFAQ
Questions MSP teams ask
Review user and license count mismatches before invoices go out
Use BillingReconcile to compare billed quantities against source counts while keeping billing policy decisions under team review.
