Bookkeeper for Managed Service Providers

Almost all of your revenue is subscription. You sign a client to a fixed fee per user or per device, you invoice monthly, and that contract repeats until the client leaves. That is the whole financial model underneath a managed IT business, and almost everything a bookkeeper does is tracing back to the same feature.

How does money flow through the managed IT services business?

Almost all of your revenue is subscription. You sign a client to a fixed fee per user or per device, you invoice monthly, and that contract repeats until the client leaves. That is the whole financial model underneath the managed IT business, and almost everything a bookkeeper does is tracing back to the same feature.

Almost all of it is monthly recurring. Per-user pricing is the structure you will see most, with contracts that vary by how much security, compliance, and strategy work the tier includes. Some clients pay annually, some just pay monthly, and most paying you is preauthorized debit, so the cash tends to show up on a schedule. The bookkeeping question is when a monthly subscription is earned. The answer is over the month it covers, not over the payment day. An annual contract paid in January still gets recorded as twelve months of revenue, one month at a time.

That deferred revenue is the central concept in managed IT bookkeeping. You receive cash up front, but you have not earned it all yet. You earn one month at a time, as you deliver the support, the monitoring, and the uptime the client is paying for.

• Monthly recurring contracts are the bulk of your revenue, with pricing set per user or per device.
• One-time project and implementation work is the second steam, and it can be large when a client is onboarding staff or moving offices.
• Annual contracts paid in advance are deferred: the cash lands now, the revenue is recognized over the twelve months it covers.
• Hardware and software the client wants through you is revenue too, and separate it from the subscription so the margins do blend.

The two payment patterns of your economics. Flat monthly subscribers come in on the schedule; they also leave on the schedule. A client whose subscription pauses because their card changed or an invoice was ignored without a follow-up is the single most common way cash flow turns against you here. The money is regular when it comes, but it does not come automatically. Invoicing on a fixed day, taking preauthorized debits, and following up every month keeps that stream intact.

Which costs are direct costs, and which are overhead?

The direct costs are the ones that exist only because you deliver the service: the engineers and technicians who take the tickets, and the software licenses that let them do the work. Overhead is the stuff that pays for the business itself: the office, the owner, the admin, the accounting, the insurance.

That separation is the single most important structure for the books in this trade. A typical managed IT business spends a large part of what it brings in on staff, and if the support engineers sit in the same expense account as the owner's salary and the office, you cannot see what the service line actually amounts to. The books should show a direct margin for the service once the engineers and tooling come out, then the operating margin after your overhead. Industry estimates on the net margin run anywhere from 7% for a broad IT services sector to 30% for a focused managed service shop. The only number that tells your story is your own cost structure, which the books cannot deliver unless COGS and overhead are separated.

How do you record a managed IT contract in the month it starts?

Record the month's earned revenue when the month is earned, meaning when the month of service is delivered, not when the client's check lands. Three clients go live in September with monthly contracts. Even if they all pay you a full year in advance, only one month of each contract counts as September revenue. The rest is a liability to you in the form of service.

The mistake is running the state on a cash basis and judging by the bank account. In September, the bank looks strong, so you feel good about the year. But you have already been signed up to serve them through next August, and October through August has no new money attached to it. The profit and loss recognized across the months tells the truth; the cash basis tells you December is paid. But it is not. December work you already agreed to do.

Why does a client's profitability keep hiding?

Because two contracts at the same price can cost very different amounts. A walk-up client on a broken ticket queue can be compared to one on a stable and modern environment. The work is the same per user, but the support load is not.

The problem is that time is usually in the PSA tool, and spend is in the books, and nothing connects them. The bookkeeping solution is simple in principle and hard in practice: the books need the direct cost allocated at least roughly to the client that caused it. Not necessarily each ticket one by one, but a monthly allocation that puts the heavy weight of engineering hours behind the reference clients. Then the profit and loss statement shows each managed service contract as its own line with its own gross margin, and the list of unprofitable clients stops being a hunch.

What reports tell you whether the business is healthy?

Three statements matter in this business, and decent bookkeeping will produce all three for the books: the profit and loss at the contract level, the profit and loss by income stream, and the cash flow by month. The first shows gross margin. The second shows whether recurring work is paying for the business or project work is covering a recurrent cost. The third shows whether the schedule of preauthorized debits is actually turning into cash you can count on.

The second one matters more than you'd think to service providers because the margin on resold hardware is thin, and the margin on managed services is much healthier. When the danger of blending them in one P&L, the project that sells hardware can make you look stronger than you are. The ones who separate the streams know that the recurring is what carries the project.

What should the books help you decide?

Two decisions, and both go back to margin.

Pricing: the contract you started last year at the market rate is run literally forever at that rate until you raise it. The books tell you whether your cost per employee has outrun the contract's margin so you raise the price with the inventory math in hand instead of a guess.

Hiring: the gross margin line tells you how much room you have to bring on a new engineer. If the service line clearly supports the next payroll, adding a person to absorb more clients is a decision the P&L can back. If the margin is already thin, hiring a head before you have the volume to justify it is the fastest way to lose runway.

Hardware purchasing and support tooling belong in the same account. The months with no purchases look stronger than they are, and the month everything renews looks weaker. A tool-license subaccount under cost of goods sold tells you whether the tool suite is a fixed cost you plan around or a monthly cost you react to. Which one it is should not stay hidden.

The same story is why an unprofitable client is usually not an annoying client but a price signal. If the books separate out the client that costs enough in engineer time to drag every total on the monthly margin, the decision writes itself: change the tier, put them on a different scope, or let them go. The conclusion comes from a system that starts with the subscriptions, carries the client costs, and puts the two side by side before the month closes.