Chart of Accounts for MSPs: A Practical Structure Guide

A chart of accounts (COA) for an MSP is an indexed list of every financial account used to record transactions, organized so the resulting P&L and balance sheet reflect how a managed services business actually generates revenue and incurs costs. For an MSP, that means the COA must distinguish between recurring managed services, hardware and software resale, and project work — because each stream carries a different margin profile and requires different management decisions. A generic small-business COA won't do this: it lumps all revenue into one or two lines and buries your cost structure in broad expense categories, making it impossible to tell whether your managed services contracts are profitable or whether hardware resale is dragging down gross margin.

As Investopedia notes, a COA is fundamentally an organizational tool — and for MSPs, the organization has to match the business model.

Key Takeaways

• An MSP chart of accounts must separate recurring managed services revenue, hardware/software resale revenue, and project/T&M revenue into distinct income accounts — mixing them makes margin analysis impossible.
• Hardware and software resale costs belong in Cost of Goods Sold (COGS), not operating expenses — they move with revenue and must be tracked separately from managed services delivery costs.
• Deferred revenue is a liability, not income — prepaid contracts must sit on the balance sheet until the service period is earned.
• Tech labor allocation is one of the most consequential decisions in an MSP COA: labor that directly delivers client services belongs in COGS; internal IT and sales support belongs in operating expenses.
• A COA with too many accounts creates as many problems as one with too few — build for the decisions you need to make, not for theoretical completeness.

How Should an MSP Structure Its Chart of Accounts?

An MSP chart of accounts follows the standard five-section structure — Assets, Liabilities, Equity, Revenue, and Expenses — but the Revenue and COGS sections require MSP-specific design. The goal, as Stride Services describes, is to separate product revenue from service revenue at the top level, then build sub-accounts underneath that give you the visibility you need to manage the business.

Think of the COA as a filing cabinet system for your financial data. Too few drawers and everything gets mixed together. Too many and the overhead of keeping them organized outweighs the insight. The right structure is the minimum number of accounts that lets you answer your most important financial questions — primarily: what is my gross margin by revenue type?

Here is a practical MSP COA skeleton:

This numbering convention is common across MSP-focused accounting frameworks and maps cleanly to QuickBooks Online's default account structure.

How Do You Separate Recurring from Project Revenue in the COA?

The revenue section is where most MSP COAs either succeed or fail. Beancount.io's MSP COA guide identifies four distinct revenue streams that should each have their own account:

1. Recurring Managed Services Revenue — Monthly recurring revenue (MRR) from managed services contracts. This is the core of most MSPs and should be its own top-level account.
2. Hardware and Software Resale Revenue — Revenue from selling hardware, software licenses, or other products to clients. Margin here is structurally different from services.
3. Project / Time-and-Materials Revenue — One-time or variable project work billed hourly or by milestone.
4. Deferred Revenue — A liability account (not income) for prepaid contracts where service hasn't yet been delivered.

Stride Services frames this as two top-level buckets — Product Revenue (4000) and Service Revenue (4100) — with sub-accounts underneath each. That structure works well in practice because it keeps the P&L readable at a glance while still allowing drill-down.

A practical revenue section might look like this:

Why deferred revenue belongs on the balance sheet

Deferred revenue is a liability — not income — because you've received cash for a service you haven't yet delivered. If a client pays a quarterly managed services retainer upfront, only the portion earned in the current month belongs on the P&L. The remainder sits in the deferred revenue liability account until it's earned. Misclassifying this as income overstates revenue and distorts your monthly close. For more on how this flows through a monthly close, see our balance sheet reconciliation checklist.

Where Do Hardware Resale and Licence Costs Sit?

Hardware and software costs that are directly tied to client deliverables belong in Cost of Goods Sold (COGS), not operating expenses. This distinction matters because COGS moves with revenue — it's what you spend to deliver what you sell — while operating expenses are the overhead you carry regardless of revenue volume.

For an MSP, the COGS section typically includes:

• Hardware cost of goods — the wholesale cost of equipment you resell to clients
• Software/license cost of goods — the vendor cost of licenses you resell or provision for clients (e.g., Microsoft 365 seats, security software)
• Tech labor — delivery — the portion of technical staff time spent directly delivering managed services to clients
• Subcontractors — third-party labor used to deliver client services
• Vendor tools used for service delivery — RMM platforms, PSA tools, backup software billed per endpoint

What does not belong in COGS: internal IT costs, sales team salaries, administrative overhead, or software used for running your own business rather than delivering client services.

A practical COGS section:

The tech labor allocation problem

Allocating tech labor is the most consequential — and most commonly mishandled — decision in an MSP COA. MSP CFO and Accounting identifies this as a core challenge: engineers often split time between billable client delivery, internal projects, sales support, and training. Only the client-delivery portion belongs in COGS.

In practice, most MSPs use one of two approaches:

• Time-tracking allocation: Engineers log time by category; payroll is split between COGS and OpEx based on actual hours.
• Percentage allocation: A fixed percentage of tech payroll is applied each period based on historical patterns.

Time tracking is more accurate but requires discipline. Percentage allocation is simpler but should be reviewed quarterly to stay calibrated. Either way, the decision needs to be made explicitly — defaulting all tech labor to operating expenses understates your true cost of delivery and inflates gross margin.

What Operating Expense Accounts Does an MSP Need?

Operating expenses (OpEx) cover everything that isn't directly tied to delivering client services. For an MSP, this typically includes:

Keep operating expenses distinct from COGS. If an expense disappears when you stop serving clients, it's probably COGS. If it persists regardless of client volume, it's an operating expense.

How Does the COA Connect to Gross Margin Analysis?

The reason MSP-specific COA structure matters is gross margin. As Enkel's bookkeeping guide for managed services businesses explains, gross margin is calculated by subtracting COGS from revenue and dividing by revenue. But that calculation is only useful if revenue and COGS are organized to match.

With a properly structured COA, you can calculate gross margin separately for:

• Recurring managed services (typically the highest-margin stream)
• Hardware and software resale (often lower-margin, sometimes a loss-leader)
• Project/T&M work (variable, depends on labor efficiency)

Without that separation, you get a blended gross margin that tells you very little. A strong managed services margin can mask a hardware resale business that's barely breaking even — or vice versa.

For a deeper look at how these margin streams interact and what to expect from a finance partner, see our guide to outsourced accounting for MSPs.

Common MSP COA Mistakes to Avoid

1. Lumping all revenue into one account. If your P&L shows a single "Revenue" line, you cannot manage the business by the numbers. Separate recurring, resale, and project revenue from day one.

2. Putting deferred revenue in income. Prepaid contracts are a liability until earned. Booking them as income on receipt overstates revenue and creates a reconciliation problem at month-end.

3. Putting all tech labor in operating expenses. This understates COGS and inflates gross margin. It also makes it impossible to understand your true cost of service delivery.

4. Over-engineering the COA. More accounts is not always better. If you have 15 revenue sub-accounts but only review the P&L quarterly, the granularity creates work without generating insight. Build for the decisions you actually make.

5. Not aligning the COA to your PSA. Your PSA (ConnectWise, Autotask, HaloPSA) generates service data that should map to your COA categories. Misalignment means manual reconciliation every month. For help setting up QuickBooks to match your MSP's revenue structure, see our QuickBooks Online setup service.

When Should an MSP Build or Rebuild Its Chart of Accounts?

The right time to build a clean MSP chart of accounts is before revenue complexity makes it painful. As contract types, vendor relationships, and client counts grow, reclassifying transactions under a new structure becomes progressively more expensive. Building the right structure early — while the books are still relatively simple — avoids a costly cleanup later.

If your books are already messy, a COA restructure typically requires a historical cleanup pass to reclassify transactions under the new structure. That's a one-time cost that pays for itself quickly in the form of financial clarity. See what that process typically costs in our catch-up bookkeeping cost guide.

A well-structured COA won't run your business for you — but it will make sure your P&L reflects what's actually happening, so you can make decisions on real numbers rather than instinct.

Disclaimer: Laya provides this content for informational purposes only. This material does not constitute tax, legal, or accounting advice. Please consult your own tax, legal, and accounting advisors before engaging in any transaction.

If you want to see what a clean MSP close looks like in practice — with revenue properly separated and COGS allocated — view a sample close or book an intro call.