I look at a lot of invoices from other providers. It usually happens during an assessment, and the pattern is consistent enough to write down. The owner can tell us roughly what they pay each month, and can't tell us what any single line is for.
That isn't a failure of attention. Most IT invoices are written for the accounting system that produced them. But an invoice you can't read is an invoice you can't check, and unchecked bills are where the quiet money goes. Here's how to read yours.
Start with the unit counts on your IT invoice
Almost every recurring IT charge is a unit price times a number of units. The units are usually users, devices, mailboxes, or servers. Before you look at any dollar figure, find the counts and check them against reality. I check these first on every invoice I read.
This is the single most productive thing an owner can do with an IT bill, because counts drift in one direction. People leave and the seat stays billed. A laptop is retired and the management fee for it keeps running, and the same happens to the backup line for a decommissioned server.
Nobody is being dishonest. The count was simply never reconciled against what you have.
If your invoice doesn't show counts at all, that's your first question. A bill that says only managed services and a total isn't telling you what you bought.
Separate the three kinds of line
Once you can see the units, sort the lines into three groups.
Recurring service is what you pay every month for the managed IT arrangement itself: monitoring, patching, maintenance, and access to support. It should be stable and predictable, and it should be obvious which units it applies to.
Pass-through subscriptions are things your provider buys on your behalf and rebills to you: Microsoft 365 licenses, backup capacity, email security, cybersecurity tooling, domain and certificate renewals. These are legitimate, and they should be identifiable as what they are.
Project and time-based work is everything else: the migration, the new firewall, the after-hours cutover, the hours spent on something outside the agreement. It should be occasional, and it should reference something you agreed to in advance.
A healthy invoice keeps the three groups visually distinct. If project work is folded into the recurring line, you can't tell whether your monthly cost went up because you bought something or because your provider raised prices.
What belongs on a clear invoice
- The billing period, stated plainly, including whether the recurring portion is billed ahead or behind.
- Each recurring line with its unit, its count, and its unit price, so the arithmetic is visible.
- Licenses named as licenses, with the quantity and the product they belong to.
- Project and hourly work with a date, a short description, and a reference to the quote or approval it came from.
- Any pass-through cost identified as a pass-through.
- The contract or agreement reference, so the invoice can be checked against what you actually signed.
None of that is exotic. It's what any competent professional services bill looks like, and IT bills usually fall short of it out of habit.
The four lines worth questioning
Seats you no longer have. This is covered above, and it stays the most common finding, especially on Microsoft 365 licenses. I'd ask for a list of the named users and devices being billed, and read it. You'll recognize the names, which is exactly what makes this check easy for a non-technical owner to run.
Licenses billed at a markup you were never told about. Reselling licenses is normal, and marking them up is defensible, especially when the provider is managing them. What isn't defensible is being unable to find out.
I'd ask what a license costs you per user per month and what the provider pays. A provider who won't answer that has told you something.
Vague bundles. A single line that reads managed IT services for a large round number, with no unit and no count, is the invoice equivalent of a shrug. It can be a perfectly fair price, but you have no way to know, and neither will the next provider you ask to quote against it.
Work you thought was included. This is the one that causes actual arguments. I'd find out where your agreement draws the line between covered support and billable project work, and check a few recent time entries against it. If that line moves depending on who you ask, resolve it before the next large piece of work.
The question that clears up most confusion
Ask your provider for a one-page summary of your agreement in plain language: what's included, what's billed separately, what the counts are, and what happens when the counts change.
It's a reasonable request for a document a well-run provider already has, and producing it takes very little time. In my experience the response tells you something either way. Some providers send it the same week. Some can't produce one, which usually means it doesn't exist internally either.
Why reading your IT invoice matters
There are two reasons, and only one of them is money.
The obvious one is that unreconciled counts and unexplained bundles cost a small business a real amount over a few years, and the amount is invisible precisely because it arrives in monthly installments.
The less obvious one is that an invoice is a decent proxy for how a provider operates. A bill with accurate counts comes from a provider whose records match your environment. A bill that has been charging you for two departed employees since spring is telling you something about the documentation behind it, and about whether anyone looks at your account when no ticket is open.
That second reason is why we read the invoice during an assessment. It's one page, you already have it, and it's often the fastest way I have to understand what has actually been happening.
If you want a second read on your current bill, that's part of the assessment we do before anything changes, and you keep the write-up regardless of what you decide afterward. It pairs well with the real cost of running several separate vendors, which is the version of this problem where there's no single invoice to read at all. Book a call and I'll go through it with you.