Bookkeeping for IT service providers on ConnectWise, Autotask and HaloPSA

The short answer

Managed service providers (MSPs) and IT service firms run the actual business in a professional services automation (PSA) platform: agreements, tickets, time, products, and invoices. QuickBooks, or another ledger, remains the system of record for cash, AR, AP, payroll, and financial statements. Bookkeeping works when closed PSA invoices and payments flow into the GL with stable product and customer mapping, and when recurring revenue, project work, and product COGS don't collapse into a single "IT income" dump pulled straight from the bank feed.

Quick reference

Exact connector names and versions change; the operating model doesn't. The PSA bills, the GL books, the bank proves cash actually moved.

ConnectWise PSA

ConnectWise is where agreements, time, products, and invoices get built, and ConnectWise's own documentation confirms exactly how the handoff works: invoices move through an internal module called the Accounting Interface, specifically the "Unposted Invoices" screen, and once an invoice is moved to closed status with autosync enabled, it syncs to QuickBooks or Xero immediately, through a third-party sync layer such as Wise-Sync rather than any native ConnectWise-to-QuickBooks connection (Wise-Sync). Wise-Sync itself is a well-established, long-running tool in this space, built in 2012 specifically to solve this gap, by a former MSP owner who felt the same pain directly.

Customer identifiers and product or line-item names have to match exactly what QuickBooks expects, or syncs fail outright or create duplicate records. Payment tools often sit between the PSA and QuickBooks so a client receipt updates both sides correctly, rather than landing in only one.

Bookkeeping focus: separate agreement revenue (MRR) from time-and-materials revenue from product revenue; confirm correct income accounts on every catalog item; track COGS for hardware and license pass-throughs specifically; and watch for double-posting when both a payment processor and QuickBooks independently record the same receipt.

Autotask PSA

Autotask generates invoices and operational financial views but isn't a full GL. Here's something worth getting right, since it directly affects which integration a reader should actually be using: the older Autotask-to-QuickBooks Online integration, built on Intuit's AppConnect platform, is being retired, and Kaseya's own published retirement date for it has moved more than once. One of Kaseya's own help pages states support ended August 30, 2026 with the integration stopping entirely on September 30, 2026; another, apparently more recent, page states the end-of-life date was "extended to July 1st, 2026"; a still-earlier version of the same help article cited December 31, 2025. Every one of those dates has already passed as of this writing. In practice, that means the legacy AppConnect-based integration should be treated as already retired, not merely scheduled for retirement, and Kaseya's Smart Accounting Hub, confirmed directly as "an API connector that is built, maintained, and supported directly by Kaseya" and independent of AppConnect, is the integration that's actually functioning today (Kaseya).

The Smart Accounting Hub supports QuickBooks Online Plus and Advanced specifically, syncs invoices, expenses, and purchase orders depending on which modules a firm enables, and includes its own activity logs and error reporting that the older integration didn't have.

Bookkeeping focus: confirm which integration is actually connected before relying on anything else here, since a firm still assuming the legacy AppConnect apps are live may be looking at a broken or already-disconnected sync without realizing it; align billing codes to QuickBooks items and income accounts; sync expenses and POs only if those specific modules are actually in use; and match AR in QuickBooks to the Autotask invoice register every single month regardless of which connector is running.

HaloPSA

HaloPSA covers tickets, contracts, projects, and billing for IT service providers, and unlike ConnectWise, its QuickBooks Online connection is genuinely native to the product, not a third-party layer bolted on. HaloPSA's own guides confirm bidirectional sync and spell out a compulsory setup step worth knowing before a sync fails silently: each customer in Halo has to be assigned a QuickBooks Online ID, and if a customer exists in Halo without that mapping, their invoices simply won't sync; the same requirement applies to items, or the invoice sync fails entirely (HaloPSA). Third-party platforms such as Zynk also offer two-way sync across customers, invoices, invoice payments, purchase orders, and suppliers for firms that want that layer instead of or alongside the native one.

One specific conflict worth flagging: running HaloPSA's native QuickBooks sync at the same time as a separate third-party payment platform, such as Alternative Payments or BenjiPays, is a documented cause of duplicate or conflicting invoice data. Setup guides for those payment platforms are explicit that the native sync has to be disabled first before connecting them.

Bookkeeping focus: distinguish contract-based invoice coding from ad-hoc invoice coding; separate supplier bills from client product sales clearly; and keep a clean customer match between Halo and QuickBooks, since a missing QuickBooks ID on either side is the single most common reason an invoice simply never shows up where it's expected.

Shared MSP failure mode

One typical month for an MSP:

Wrong books record the full deposit total as "consulting income," with no COGS, no AR movement, and the fees simply ignored. Right books break revenue out by type from the PSA's own invoice register, pull COGS from actual product costs, show AR from the invoices still unpaid, book fees as an expense, and match the bank to payments specifically, never to revenue as a whole.

Recurring agreements make this materially worse when deferred or prepaid amounts get ignored and every invoice is treated as immediately earned with no actual policy behind that assumption.

Month-end checklist, for any of the three PSAs

1. Freeze the invoice batch. Only closed or posted PSA invoices are eligible to hit the GL.

2. Confirm the sync or export actually completed. Resolve any failed customer, item, or tax mapping before moving on.

3. Tie the PSA's invoice total to the QuickBooks invoice register for the exact same period.

4. Tie payments to bank deposits, and to processor payout reports where those apply.

5. Review AR aging in QuickBooks against the PSA's own aging report.

6. Post payroll, non-PSA AP, loans, and owner activity, none of which the PSA will ever touch.

7. Review MRR versus project versus product revenue for plain reasonableness, not just that the totals tie.

How Numetix works with MSP stacks

We work in your accounting system alongside ConnectWise, Autotask, or HaloPSA, whichever one actually runs your business. AI helps categorize bank and processor activity; a CPA-overseen team owns invoice-to-GL tie-out, AR, and the monthly close, so agreement revenue, project billings, and product sales stay distinct instead of collapsing into one number, and cash ties cleanly to the bank.

A practical first step: send us one month's PSA invoice register, broken out by type, the QuickBooks P&L and AR aging, and your processor deposits for the same period. We'll show you the matched totals and exactly where the mapping gaps are. Book 30 minutes with our team. More on how Numetix serves MSPs and professional services firms.

Frequently asked questions

Is the PSA our actual accounting system? No. It's the operational billing system. The GL owns the financial statements and tax reporting, always.

Do we need middleware specifically for ConnectWise? Most MSPs run a dedicated sync tool between ConnectWise and QuickBooks or Xero, since there's no native connection. Plan on real mapping work either way, regardless of which sync tool is used.

Should every ticket create a QuickBooks entry? No. Closed invoices, and any agreed expense or PO flows, should. Ordinary ticket noise has no place in the GL at all.

How should we treat Microsoft or other vendor license pass-throughs? With clear product records, revenue and COGS booked separately, or agency treatment specifically if the firm is genuinely acting as an agent rather than a reseller, applied consistently every month.

Is Autotask's older QuickBooks Online integration still usable? Treat it as already retired. Kaseya has published several different end-of-life dates for the legacy AppConnect-based integration, and every one of them has already passed. The Smart Accounting Hub is the connector that's actually functioning now; confirm directly which one a given firm is running before assuming anything is syncing correctly.

What breaks month-end most often across all three PSAs? Item and customer mismatches, payments recorded in two systems at once, and bank-feed "income" that bypasses the PSA's own invoice register entirely.