IT Consultant Invoice Template — Hourly, Project
Hourly break-fix, project implementations, managed-services retainers, hardware pass-throughs, after-hours surcharges. The template handles a solo IT consultant or a small MSP.
Open the free generator → Need a quote first?
Free forever · PDF export · Multi-currency · Runs in your browser
What goes on an IT consulting invoice
●Consulting / support (hourly). Often billed in 15-min increments.
●Project fee (implementation, migration). Fixed or T&M; per SOW.
●Managed-services retainer (monthly per device or flat). Defined scope.
●After-hours / emergency surcharge. 1.5× or 2×; disclose.
●Hardware / software pass-through (with markup or at cost). State which.
●Subscription pass-through (Microsoft, etc.). Often at cost or wrapped.
●Travel beyond service area. Per-mile or fixed.
How IT consultants and MSPs usually bill
Break-fix: invoice per ticket or weekly aggregate, paid 15- or 30-day.
Managed services: monthly invoice in advance; auto-pay common.
Projects: 30/40/30 milestone billing; deposit covers hardware order.
Always reference the ticket or work-order number — required for client's audit trail.
Tax notes
IT services are typically fully taxable. Hardware sales are taxable as goods. Cross-border B2B services often reverse-charge under EU/UK rules. State your tax/VAT number on the invoice for international clients.
Frequently asked questions
Should hardware be marked up?
Either way works — state which on the invoice. Pass-through at cost is most transparent. Markup (10-20%) covers your sourcing time and warranty exposure. Many MSPs prefer the client owns hardware purchases directly.
How do I bill after-hours emergencies?
Set a clearly published emergency rate (1.5× or 2×) and confirm with the client before dispatch. Invoice as 'Emergency / after-hours support' so it's never a surprise.
How do I invoice a managed-services retainer?
Monthly invoice for the agreed amount (per device, per user, or flat). Track hours; reconcile at quarter-end if you bill against an hour budget.
Do I invoice for software subscriptions?
Either pass-through at cost (with subscription reference) or have the client own the subscription directly. Direct ownership is cleaner if the relationship ends — they keep the software without your help.
Sample wording for an IT consulting invoice
Realistic, copy-and-paste-ready line items IT consultants typically use. The rates here are ballpark for a mid-cost US market, so adjust them to yours.
●IT-strategy engagement — 90-day infrastructure assessment (60 hrs at $225/hr): $13,500
●Cloud-migration plan — AWS-to-Azure with cost modelling (28 hrs): $6,300
●Security audit — SOC 2 readiness gap analysis (22 hrs): $4,950
●Implementation oversight — 6-month retainer post-strategy (8 hrs/mo for 6 mo): $10,800
●Emergency response — Saturday incident, 4 hrs on-call resolution (after-hours rate at 1.5×): $1,350
●Software pass-through — monitoring, asset-discovery, project tools (per engagement): $385
●Travel — quarterly on-site review with leadership (receipts attached, pass-through): $1,485
Notes: Engagement per SOW dated __ / __. Deliverables licensed for internal client use. Implementation oversight is hourly above retainer; pre-paid hours roll one month then expire. After-hours support at 1.5× standard rate. NDA on file; client data confidential. Net 30; 1.5%/month late fee.
How IT engagements actually pay
IT consulting splits cleanly by engagement type. Strategic engagements (architecture review, cloud migration plans, security audits) pay fixed-fee with 30-50% deposit. MSP-style ongoing managed services pay retainer monthly in advance — IT consulting and managed services overlap heavily, and the retainer model is what separates a profitable practice from one that constantly chases one-off work. Project work (implementation, migration, integration) pays in milestones tied to deliverables.
Corporate clients pay Net 30-60; mid-market SMBs pay Net 30; small businesses often pay on completion via card. Procurement is the slowest gating factor — for any company over 200 employees, vendor onboarding (W-9, MSA, SOC-2 questionnaire, NDA, insurance verification) can take 30-90 days before the first invoice. After-hours and emergency work commands premium rates (1.5-2× standard) and pays fast because the issue is mission-critical.
Five billing mistakes that hold up your payments
●Bundling 'strategy and implementation' into one engagement. Strategy and execution are separate engagements with different rate structures. Bundling lets the client extract execution for the strategy rate. Sell strategy first, deliver, then sell implementation as a separate engagement.
●Quoting per-hour with no NTE. Hourly billing with no not-to-exceed exposes both parties: client to runaway cost, consultant to client refusing to pay above their internal estimate. Cap each phase: 'Discovery and assessment: up to 60 hrs ($13,500 NTE).' Below the cap, bill actuals; above the cap, change-order required.
●Skipping the SOW addendum on scope changes. 'While we're in there, can you also fix the legacy SQL Server?' is scope creep. Each scope addition is a written addendum, signed, with hour estimate and pricing. Don't do it verbally; the bill at month 3 will be disputed.
●Forgetting to charge for after-hours and emergency response. Saturday data-restoration calls are 1.5-2× standard rate. State the policy on engagement: 'Standard hours Mon-Fri 9-5; after-hours/weekend at 1.5× rate; emergency response within 1 hr at 2× rate.' Bill it. Otherwise free emergency response trains clients to call you at 9 PM.
●Letting clients pay you 'when the project completes'. Long projects with backloaded payment expose you to scope-creep risk and client funding-cycle changes. Always milestone-bill: 25% on signing, 25% at design approval, 25% at implementation, 25% at acceptance. Each milestone is its own invoice.
US tax notes for it consultants
IT-consulting services are non-taxable in most states (professional service). The exceptions are the gross-receipts states: Hawaii (GET), New Mexico (GRT), Washington (B&O), plus South Dakota's services tax. The tax issue specific to IT consultants is that SaaS resold to clients, custom software developed for clients, and cloud infrastructure passed through can each carry a different sales-tax treatment. Software-as-a-service, for example, is taxed as tangible digital property in some states. Coordinate with the client's accountant on any resold software or hosting.
Federal: 1099-NEC at $600 from every business client. IT-consultant deductibles often missed: cloud subscriptions for development and testing (AWS, Azure, GCP, used for client demos and proof-of-concepts), software licences (developer tools, monitoring, security software), home-office or coworking expense, certifications (AWS, Azure, CISSP, GCP, where exam fees and recertification costs are substantial), continuing-ed (Pluralsight, Linux Academy, conference attendance like AWS re:Invent, KubeCon), and the under-claimed line for home network upgrades essential to client-facing work (faster internet, business-grade router, VPN service).
Not tax advice — confirm specifics with your CPA or state department of revenue.
A few more billing questions
Should I price hourly or flat-fee for IT projects?
Flat-fee for clearly scoped work (cloud migration, security audit, implementation of known software). Hourly for advisory and discovery work where the scope is unclear. Retainer for ongoing managed services. Mix appropriately based on engagement type; don't quote hourly when the client wants certainty (it signals you don't know the work).
How do I structure a managed-services retainer?
Monthly fixed fee covering defined services (response SLA, included hours, monitoring, security updates). Above-cap work billed hourly. State explicitly: 'Retainer covers up to 20 hrs/month of advisory and incident response; overage billed at $X/hr.' Auto-draft. Annual review for scope and rate adjustment.
Can I bill for tools and software resold to the client?
Yes — pass-through at cost is standard. If you're adding management value (configuring, monitoring, integrating), charge a management margin. Two lines: 'AWS infrastructure (pass-through): $X/mo' and 'Infrastructure management — monitoring, deployment, incident response: $Y/mo.' Don't hide the infrastructure cost inside management; transparent pricing builds trust.
How do I handle a project where the client supplies their own outdated stack?
Set the policy upfront. State on engagement: 'Engagements require maintained framework and OS versions; migration to current versions quoted separately as Phase 0.' Don't accept work on Windows Server 2008 R2 or PHP 5.6 at modern rates — the maintenance burden is real and the security risk is yours if you're the consultant of record.
Other professions
→ Contractors → Electricians → Plumbers → Photographers → Graphic designers → Web developers
Ready to invoice?
Open the generator. Fill in your details. Export the PDF. Two minutes.