MSP billing problem
Shared Mailbox and Kiosk User Billing Count Review
Shared mailboxes, kiosk or frontline users, service accounts, and unusual user-license patterns can confuse MSP billing review when mailbox, user, and license counts do not tell the same story.
Why this billing mismatch happens
Mailbox, user, and license counts can diverge depending on how accounts are configured and how the MSP packages and bills the service. A shared mailbox, kiosk user, frontline user, or service account may need a different review path than a standard user.
The practical review is to confirm what should be included before invoice day. MSP teams should review against their billing policy instead of assuming a universal rule for every shared mailbox or unusual account.
Common examples
A shared mailbox appears in a source list but should be reviewed against the MSP's billing policy
Kiosk or frontline users are packaged differently than full user services
A service account has a license assignment that needs review before billing
Mailbox counts are higher than user counts because of shared or resource mailboxes
A bundle includes users and services that do not map one-to-one to PSA quantities
What to compare
Mailbox, user, license, subscription, and SKU counts from the source system
Shared mailbox, kiosk, frontline, service-account, and resource-account context
PSA service, agreement, product, and invoice quantities
Service packaging and billing policy for the client
Client, tenant, and service mapping before invoice approval
Manual review checklist
- 1
Identify the source counts used for the service being reviewed.
- 2
Separate standard users from shared mailboxes, kiosk users, frontline users, and service accounts where possible.
- 3
Review each unusual account type against your billing policy.
- 4
Compare the intended count against PSA billed quantities.
- 5
Confirm what should be included before invoice day.
How BillingReconcile helps organize the review
BillingReconcile helps keep source counts, PSA billed quantities, and review context visible. It supports count review while the MSP team confirms how each account type should be handled.
Review license count mismatches involving unusual account patterns
Keep source evidence visible beside PSA billed quantities
Separate billing issues from mapping cleanup
Support human review before invoice quantities are finalized
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 checklist
Use a practical checklist for mapping, count review, and final invoice review.
Open guideFAQ
Questions MSP teams ask
Review unusual user and mailbox count patterns before invoice day
Use BillingReconcile to compare source counts against PSA billed quantities while keeping billing policy review visible.