Microsoft 365 Seats Not Billed? How MSPs Stop Seat Drift

A new hire starts at a client on Monday. A tech adds them to Microsoft 365 before lunch and assigns a license. Nobody opens the PSA ticket to change the contract, so the client is billed for 40 seats while the tenant now has 41. The difference is one seat. Repeat that across 60 clients over a year and you have a real margin problem that nobody has put a number on.

How common is this?

No public study we could find counts MSPs with seat drift specifically, so we will not invent a percentage. The closest published data comes from license vendors. CoreView, which sells Microsoft 365 license management, analyzed Office 365 use across about five million enterprise users in 2020 and found that 56% of licenses were not fully used. That figure includes licenses that were inactive, underused, oversized or unassigned, so it is not the same as billing drift. A later CoreView estimate, based on hundreds of health checks, put unused or unassigned licenses at 10 to 20%.

Those numbers describe license waste inside companies, not missed invoices at MSPs. What they do show is that license counts drift from actual use almost everywhere. An MSP managing dozens of tenants has more places for that drift to hide.

Why the numbers drift apart

Your license count lives in at least two places. The tenant, whether it is Microsoft 365, Google Workspace or an endpoint tool, shows what is in use. The PSA, such as ConnectWise, Autotask or HaloPSA, shows what the client agreed to pay for. Each change happens in one tool, and the other is updated by hand, if at all.

Usually the cause is not carelessness. Techs are busy, the change happens in a different portal, and nothing in the process forces the second update. When the process depends on someone remembering, the numbers will drift.

Signs you have this problem

• For at least one client, the active user count in the tenant is higher than the contracted quantity in the PSA.
• Onboarding and billing updates happen in different weeks, or the billing update is sometimes skipped.
• Someone exports user counts by hand before each invoice run.
• A client asks why the invoice does not match the user list they can see.
• A renewal or audit turns up a seat count that nobody expected.

What the drift costs

Here is a simple way to size it. Take the number of unbilled seats, multiply by what you pay for each license and the margin you planned on top, then multiply by the number of months the gap went unnoticed. For example, five unbilled seats at a planned margin of $20 each is $100 a month, or $1,200 a year, for one client. Repeat that across the clients with gaps.

Industry estimates for billing losses are broader and mostly come from vendors. One summary of research by MGI Research and Aria Systems puts typical billing inefficiency at 3 to 7% of annual revenue for service providers. A vendor case study from Gradient describes one MSP that found about $3,000 in unbilled services soon after connecting its PSA. It shows how quickly a single check can pay for itself.

How to measure your own gap

You do not need a survey to know if this affects you. Set aside one afternoon and do this:

• Pick the five clients with the most users.
• For each one, export the active licensed users from the tenant's admin portal.
• Pull the contracted quantity for the same client from your PSA.
• Subtract. Each difference is either billing you are missing or an agreed exception, such as a shared mailbox or a trial license.

Write down the total. That number is more useful than any industry statistic, because it is yours. If the total is zero, repeat the check for your ten largest clients before you relax.

Best practice: fix it in three layers

You do not need a new platform to start. You need three habits that people will actually follow.

• Decide which system owns the number. Most MSPs treat the PSA contract as the billing record and the tenant as the usage record. Write that down, so everyone knows which one wins when they disagree.
• Add a billing step to onboarding and offboarding. A user is not provisioned until the contract quantity is updated, or the ticket is marked as pending billing. This one step prevents most drift.
• Reconcile on a schedule. Once a week, compare active licensed users in each tenant with the contracted quantity, and flag every difference. Small gaps can be fixed quickly. Gaps that keep coming back point to a process problem.

The goal is not a perfect audit. It is that a missed seat gets caught in the same week it happened.

Where automation helps

A manual check works for ten clients. At fifty, it becomes a job of its own. A scheduled job can read license counts from the tenant's API and contract quantities from the PSA's API, compare them every night, and send a short list of differences to the person who approves invoices.

At Asauvia, we build this kind of reconciliation for MSPs. The comparison is the easy part. The careful work is in the rules: which differences to report, which to ignore, and how a change gets approved before it reaches a client's bill. A person stays in the loop for every change to an invoice.

A typical first engagement starts with read-only access to your tenants and PSA. In the first week we run the comparison for your clients and agree the exception rules with you. By the end of the second week you have a weekly report and an approval step. We do not change tenants or contracts without your sign-off.

Before you start, check what your tools allow. Most major platforms expose license and user data through an API, but access and permissions depend on your plan.