MSP billing is how managed service providers charge clients for ongoing IT services, and it's rarely as simple as a single monthly fee. Understanding the models and where they break down is the first step to fixing revenue leakage.
At its core, MSP billing means charging clients for a bundle of services delivered continuously: managed devices, resold software licences, monitoring, support hours, security tools, and more. Unlike a one-off project invoice, MSP billing is recurring, and it depends on data from several systems staying in sync month after month. That dependency is exactly where most billing problems start.
Every MSP eventually settles on a mix of models to price this work. None of them are wrong, but each creates a different reconciliation challenge if you don't have a system checking the numbers.
The main MSP billing models
Per-seat billing
Clients are charged a fixed amount per user or per licensed seat, typically for things like Microsoft 365, security tools, or helpdesk support. It's simple to explain to clients, but it depends entirely on seat counts staying accurate on both sides, yours and the distributor's, every single month.
Per-device billing
Clients are charged per managed endpoint, laptop, server, or workstation, usually pulled from RMM data. This model works well for MSPs without a formal PSA, since device counts are already tracked in the RMM tool. See our guide on billing clients without a PSA.
Tiered billing
Clients pick a tier (Bronze/Silver/Gold, or similarly named packages) which bundles a fixed set of services for a flat fee. Tiers simplify sales conversations but hide a lot of underlying complexity, since what's actually delivered against each tier still needs to be tracked accurately.
Bundled billing
A single line item on an invoice, "Managed IT Services," covers everything: devices, licences, support, monitoring. This is the easiest model for a client to understand, and the hardest one to reconcile, because there's no natural line-by-line comparison against distributor costs.
Why MSP billing breaks down
Whatever model you use, MSP billing depends on three systems staying aligned: your PSA (which usually holds the contract and the intended pricing), your distributors (Pax8, Microsoft 365 CSP, and others, who bill you for what's actually provisioned), and your accounting platform (which sends the client invoice). When any of these drift apart, revenue leaks.
- A technician adds a licence in a distributor portal but forgets to update the PSA contract
- A client's device count grows over months without anyone updating the billing line
- A distributor reprices at renewal and the increase never reaches the client invoice
- Mid-cycle seat changes get prorated by the distributor but billed flat to the client
Individually, each of these might be a few pounds a month. Across dozens or hundreds of clients, they add up to real revenue, usually invisible until someone does a manual audit. Read more about the scale of this in MSP revenue leakage.
Reconciliation is the fix
Billing reconciliation means systematically comparing what you're charged, what your contract says you should bill, and what you actually invoiced, for every client, every month. Done manually, it's a spreadsheet exercise most MSPs don't have time for. Done automatically, it becomes a standing check that catches leakage as it happens rather than a year later. See how it works in MSP billing reconciliation.
Choosing a model
There's no universally "correct" billing model, the right choice depends on your service mix and how your clients think about value. What matters more than the model itself is having a system that keeps whichever model you choose honest against what you're actually paying and delivering. For a direct comparison of the two most common approaches, see per-seat vs per-device billing.