IT Services Invoice Template for MSPs: Per-User Billing

Quick answer: A managed services invoice should show the plan, the user or device count and rate, and the service period, followed by prorated adds or removals, resold licenses, block hours or overage time, project work and hardware on separate lines. Apply sales tax only to taxable items, then subtract credits and payments to reach the balance due.

Managed service providers (MSPs) sell something that is hard to see: ongoing support, monitoring, security and maintenance that keeps a client's technology running. The invoice is often the only monthly reminder of what the client is paying for. A clear IT invoice template turns a long list of seats, licenses and tickets into something the client's finance team can check in a few minutes.

This guide covers MSP pricing models, how to show a managed services invoice line by line, how to handle mid-month proration, block hours, project work and hardware resale, and what a complete invoice looks like with the arithmetic shown. It is written for small MSPs and independent IT consultants who support businesses on a recurring basis.

MSP pricing models

Most providers use one or more of the models below. Prices are not shown because they vary by region, service scope, security stack and client size.

Model	How it works	How it appears on the invoice
Per user	Monthly fee per supported user, covering their devices and accounts	Users x rate, with the count date stated
Per device	Monthly fee per workstation, server or network device	One line per device type: count x rate
Tiered packages	Bundles such as basic, standard and premium with different coverage	Package name, unit count and rate
All-inclusive flat fee	A fixed monthly price for a defined environment	One plan line, with scope summarized in notes
Block hours	Prepaid bank of support or project hours	Block purchase line, then hours used and balance in notes
Time and materials	Hourly support with parts billed as used	Hours by ticket or task x rate, plus parts
Usage-based add-ons	Backup storage, cloud resources, metered security tools	Quantity used x unit rate, billed in arrears

Per-user and per-device plans are the most common foundation. They make revenue predictable and give clients a simple way to budget: add a person, add a seat. Usage-based add-ons follow the same principles as metered SaaS billing, covered in detail in our guide to usage-based billing invoices.

Defining users and devices

Every per-unit model needs definitions. Is a shared mailbox a user? Does a part-time employee count? Is a phone a device? Write the answer into the agreement and use the same terms on the invoice. A line such as "Managed user, standard tier (count as of Nov 1): 24" leaves little room for argument, especially if you can share the user list on request.

Structuring a managed services invoice

A well-built MSP invoice groups lines into sections that match how the client thinks about the spend:

1. Recurring managed services. The plan fee, per-user or per-device counts and any fixed add-ons, usually billed in advance for the coming month.
2. Adjustments. Prorated charges for users or devices added during the previous month, and credits for removals.
3. Licenses and subscriptions. Resold software and cloud subscriptions, each with quantity and unit price.
4. Additional time. Work outside the agreement, block hours purchased, or overage hours billed in arrears.
5. Projects. Fixed-price or hourly project work referenced to a quote or statement of work.
6. Hardware. Equipment sold to the client, with sales tax where applicable.

Label each line with its service period. When advance and arrears charges sit on one invoice, dates are what stop the client from thinking they have been billed twice. The principles for repeating monthly bills are explained in our recurring invoices guide.

Proration, block hours and project work

Prorating adds and removals

Clients hire and leave mid-month. A common approach is to charge the full plan in advance for the current headcount and then, on the next invoice, add prorated charges for anyone added and credits for anyone removed during the month. The formula is rate x units x days active / days in the month. Some MSPs instead bill a full month for any user active on any day, which is simpler but should be stated in the agreement. Our prorated invoice guide shows daily and monthly proration in more detail.

Block hours

Block hours give clients a discount for prepaying and give you cash upfront. Invoice the block when sold. On every later invoice, show the hours used this period, the remaining balance and the expiry date if there is one, even when the line amount is zero. When the block runs out, overage hours are billed in arrears at the agreed rate. Time records matter here; see how to invoice for hourly work for practical rules on increments and descriptions.

Prepaid blocks and annual plans paid upfront also have an accounting consequence: you receive cash before you deliver the service. Our explainer on deferred vs accrued revenue covers how to treat that money in your books.

Project work

Migrations, office moves, new server deployments and security remediation projects should not be billed as support. Quote them separately, ideally with a statement of work that defines deliverables, assumptions and exclusions, and bill them on their own invoice or in a clearly labeled section. If the client asks for additional work mid-project, use a written change order, as covered in our guide to handling scope creep.

Hardware and license resale

Many MSPs resell laptops, firewalls, switches and software licenses. These lines have different economics from services: you usually pay the distributor before the client pays you, and margins are thinner. Practical rules:

• Show each item with model, quantity and unit price; include serial numbers in the notes if the client tracks assets.
• Decide whether to show cost plus markup or a single client price, and apply your markup consistently. Our markup vs margin guide explains why a 15% markup is not a 15% margin.
• For expensive orders, require payment or a deposit before ordering.
• Keep hardware separate from services, because sales tax often applies to goods even when it does not apply to services.

Sales tax on IT services, software and cloud subscriptions varies by US state and by how the item is delivered. Our overview of sales tax on US invoices covers the basics, but get advice if you sell into several states.

Sample managed services invoice

The following is an illustrative November invoice for a 24-user office. All rates are examples. The plan is billed in advance at $125 per user per month; three users were added on October 15 and are prorated in arrears for October. The client also pays for two managed servers, resold productivity licenses and a firewall replacement project. In this example only hardware is taxed, at 6%.

Description	Period	Qty	Rate	Amount
Managed services, standard tier, per user (count as of Nov 1)	Nov 1 to Nov 30	24	$125.00	$3,000.00
Proration: 3 users added Oct 15 (17 of 31 days)	Oct 15 to Oct 31	3	$68.55	$205.65
Managed server monitoring and patching	Nov 1 to Nov 30	2	$150.00	$300.00
Productivity suite licenses (resold)	Nov 1 to Nov 30	24	$22.00	$528.00
Firewall replacement project, labor (quote Q-118)	Oct 22	6	$150.00	$900.00
Firewall appliance (cost $1,400.00 + 15% markup)	Oct 22	1	$1,610.00	$1,610.00
Subtotal				$6,543.65
Sales tax, 6% on hardware ($1,610.00)				$96.60
Total due				$6,640.25

The arithmetic:

• Plan: 24 x $125.00 = $3,000.00.
• Proration: $125.00 x 3 x 17/31 = $375.00 x 0.548387 = $205.65 (shown as $68.55 per user, rounded).
• Servers: 2 x $150.00 = $300.00.
• Licenses: 24 x $22.00 = $528.00.
• Project labor: 6 x $150.00 = $900.00.
• Firewall: $1,400.00 x 1.15 = $1,610.00.
• Subtotal: $3,000.00 + $205.65 + $300.00 + $528.00 + $900.00 + $1,610.00 = $6,543.65.
• Tax: $1,610.00 x 6% = $96.60. Total: $6,543.65 + $96.60 = $6,640.25.

When the per-user proration does not divide evenly, calculate the line total first and round once, so the line total stays accurate even if the displayed unit rate is rounded. A notes line such as "Block hours: 4.5 used in October, 5.5 remaining, expires Dec 31" would complete the picture if the client also held a block.

You can lay this out in our online invoice generator: add each line with its quantity and rate, include the service period in the description, apply tax and download the PDF. A clean, technical design such as the slate invoice template handles long line descriptions well.

What to include in an IT invoice template

• Your company name, logo, address, contact details and tax ID.
• Client legal name, billing address, PO number and agreement reference.
• Unique invoice number, invoice date and due date.
• Service period on every recurring and adjustment line.
• Plan name, unit type (user or device), count, count date and rate.
• Prorated adds and credits for removals with dates and days.
• Resold licenses and subscriptions with quantities.
• Block hours purchased, used and remaining; overage hours with ticket references.
• Project work with quote or SOW reference.
• Hardware with model, quantity, price and tax.
• Credits, payments received and balance due; payment methods and terms.

Common mistakes on MSP invoices

• Stale user counts. Billing last quarter's headcount loses revenue or overcharges. Reconcile counts against your records before each cycle.
• No service periods. Mixing advance and arrears lines without dates looks like double billing.
• Project hours inside the support plan. Folding projects into support hides profitability and sets the wrong expectation for next month.
• Untracked block hours. If clients cannot see their balance, they dispute overage charges.
• Taxing everything or nothing. Hardware, software and services can have different tax treatment; separate them.
• Ordering hardware on credit. Carrying a large equipment order for a slow-paying client strains cash flow.
• Inconsistent proration. Prorating adds but not removals, or vice versa, erodes trust quickly.

When to move to automated billing

Manual invoicing works for a handful of clients. As you grow, user counts change weekly, license quantities shift and ticket time has to be reconciled each month. That is when MSPs typically adopt professional services automation (PSA) software that syncs counts and generates recurring invoices. Industry associations such as CompTIA publish resources on running a managed services business. If you also build websites or custom software, our web development invoice template covers project-based billing that complements recurring support.

Whatever tools you use, the goal of a managed services invoice is the same: every line should map to a count, a period and a rate the client can verify. When it does, the monthly invoice reinforces the value of the relationship instead of starting an argument about it.