MSPs that bundle hardware resale into a single revenue line cannot tell where their margin actually lives. The fix is two revenue lines, not one.
Modern managed service providers and IT consulting practices almost always blend services revenue and hardware revenue. The client buys ongoing managed services and also asks the MSP to source and configure hardware (servers, switches, end-user devices, peripherals). The MSP procures the hardware, marks it up, and delivers it as part of the engagement.
This setup is operationally normal. Bookkeeping-wise, it is the most common source of margin invisibility we see in IT consulting. Practices that mix services and hardware in a single revenue line cannot answer the questions that matter for pricing, hiring, and strategy: what is our actual services margin? What is our hardware margin? Are we compensating for thin hardware margin with our services rate, or vice versa?
Why services and hardware are economically distinct
Services revenue is high-margin and low-COGS. The cost of delivering a managed services hour is the technician's loaded comp plus a small allocation of overhead. Gross margin on professional services is typically 40 to 70 percent for a healthy MSP. The financial picture is straightforward.
Hardware revenue is low-margin and high-COGS. The cost of delivering hardware is the wholesale cost from the distributor (Ingram Micro, Tech Data, D&H, others) plus a small allocation of procurement overhead. Gross margin on hardware is typically 10 to 25 percent depending on the practice's negotiated terms and the product category.
Lumping them together produces a blended margin that hides both pictures. A practice doing 60 percent services and 40 percent hardware might show a blended gross margin of 35 percent, which feels healthy but obscures the fact that services are at 55 percent and hardware is at 17 percent. Decisions about hiring, pricing, and product mix all suffer.
The chart of accounts
The minimum useful structure for an IT consulting or MSP practice.
Service revenue (parent). Sub-accounts for "Managed services (recurring)," "Project services (one-time)," "Cybersecurity and compliance," "Cloud and DevOps consulting," "T&M billings." Each has its own delivery model and margin profile.
Hardware revenue (parent). Sub-accounts for "Server and infrastructure hardware," "End-user devices," "Networking equipment," "Peripherals." Practices doing significant volume in specific categories add more granularity.
Software license revenue (parent). Software licenses bought on behalf of clients and rebilled flow through here. The categorization depends on whether you are reselling at margin or passing through at cost (see clearing accounts below).
Hardware COGS. Tracked separately by category, mirroring the hardware revenue side. Margin per category becomes computable.
Vendor pass-throughs (clearing account). Software licenses, cloud subscriptions, and other vendor charges that you procure on behalf of the client and rebill at cost should flow through clearing accounts. They should not inflate either revenue or expense.
Recurring revenue tracking. Monthly recurring revenue (MRR) from managed services contracts is the single most important metric for an MSP. Track it explicitly, separate from project revenue, with month-over-month visibility.
When to use clearing accounts vs revenue/COGS
The choice depends on how the client agreement is structured.
If you mark up the vendor charge. The vendor cost goes to COGS. The full rebill amount goes to revenue. Margin is the markup. This is appropriate for hardware resale where you are taking commercial risk on the procurement, holding inventory briefly, and providing meaningful procurement value.
If you pass through at cost. The vendor charge and the rebill flow through a clearing account. Neither side touches the P&L. Margin is recognized only if you charge a separate management fee. This is appropriate for software license rebilling where you are not providing meaningful procurement value, just convenience.
Practices that book pass-throughs as expense and revenue without distinguishing the markup case from the no-markup case end up with revenue and expense both inflated, gross margin nominally fine, and every percentage-based ratio wrong.
Monthly recurring revenue and the contract value picture
MSPs live and die on MRR. The most useful metrics are.
MRR base. Total contracted MRR across all clients. Visibility on this number tells you whether the practice is growing, flat, or churning.
Net new MRR (per month). New contracts plus expansions minus churn. Healthy MSPs are net positive every month.
Average contract value (ACV). Total contracted annual revenue divided by client count. Knowing your ACV trend tells you whether you are moving up-market or down-market.
Net revenue retention. What percentage of last year's contracted revenue is still in place this year, including expansion. Best-in-class MSPs are at 110 to 120 percent.
Most generic bookkeeping does not surface any of this. Modern practice management platforms (ConnectWise, Autotask, Halo) handle the MRR side natively. The piece that fails is the sync to QuickBooks. We capture the data and reconcile monthly so the financial picture matches the operational picture.
1099 vs W-2 for IT contractors
IT consulting practices often work with a stable bench of contractors. Long-running, full-time-equivalent IT contractors using the practice's tools, working on the practice's clients, paid monthly, look like W-2 employees to state labor departments.
The IRS test (covered in IRS guidance on independent contractor versus employee) and state ABC tests apply. Tech contractors fail these tests routinely. The fix is conversion to W-2 once the working relationship has stabilized.
Tax implications
The structural setup has direct tax-planning consequences.
QBI and SSTB phaseout. IT consulting is a specified service trade under Section 199A. Hardware resale is generally not SSTB. The split in the books opens the possibility of preserving a portion of the QBI deduction on hardware revenue at high income levels.
Reasonable compensation. IT consultant S-Corp reasonable comp benchmarks against BLS wage data, with adjustments for specialty (cybersecurity, cloud, software) and the consultant's actual mix of clinical, managerial, and sales work.
Multi-state nexus. Remote-first MSPs often have clients in multiple states. State income tax exposure depends on the state and the volume. Track revenue by state to surface the picture.
Inventory accounting. Practices holding hardware inventory may need to track under IRC Section 471 rules. Most MSPs do drop-ship rather than holding stock, which keeps inventory accounting simple, but practices that warehouse hardware need real inventory tracking.
Key takeaways.
- Services and hardware should never share a revenue line. Their margin profiles are completely different and lumping them together hides both pictures.
- Vendor pass-throughs should flow through clearing accounts when there is no markup. Booking them as expense and revenue distorts every margin metric.
- MRR is the single most important MSP metric. Track it explicitly with month-over-month visibility.
- Long-running 1099 IT contractors often fail classification tests. Conversion to W-2 is usually the right fix.
Common questions
I am a solo IT consultant, no hardware resale. Do I need this complexity?
No. Pure services consultants have simpler books. The complexity exists to manage hardware and pass-through dynamics. Solo consultants who only sell their own time can stay simple.
How do you integrate with ConnectWise, Autotask, or Halo?
We pull billing, MRR, and project data from your PSA into QuickBooks Online. Your PSA stays the system of record for tickets, contracts, and recurring revenue; QBO is the system of record for finance.
What about reseller programs (Microsoft 365, Dell PartnerDirect, similar)?
These vary by vendor. Microsoft 365 reselling under CSP can be high-margin recurring revenue and should be tracked as recurring services, not hardware. Hardware partner programs (Dell, HP, Lenovo) are hardware revenue. We help practices set up the categorization correctly during onboarding.
How do you handle subscription software bundled into managed services?
If the client pays a single fee that includes the practice's services and a bundled software subscription (e.g., Microsoft 365 included in the managed services fee), we recommend pricing the bundle so the services and software components are separately identifiable in the contract and recognizable in the books. This matters for both QBI optimization and for clean revenue analytics.
Should my IT consulting practice be an S-Corp?
Usually yes once profit clears about $100,000 for a solo consultant or $200,000 for a small partnership. IT consulting is SSTB so QBI phases out quickly, but the self-employment tax savings on owner draws are still meaningful. We model the specific situation during onboarding.
Keep reading
- Bookkeeping & Accounting Services
- Retainer Accounting for Solo Consultants — same principles applied to broader consulting practice
- What Is Reasonable Compensation for S-Corp Owners?
- Why We Focus on Private Practices
- Bookkeeping for Professional Practices
See if we are the right fit
If your MSP cannot tell you services margin and hardware margin separately, book a free 30-minute consult. Bring a recent month's invoices and a typical client agreement. We will walk through what cleaner books would look like.