Autotask QuickBooks integration: choosing a billing and payment operating model

"Did Harbor Dental pay?"

Your account director drops the question in Slack. Your billing lead opens Autotask, and the invoice is still open. Your bookkeeper opens QuickBooks Online and finds a payment sitting in Undeposited Funds. The payment portal says the client paid on Tuesday.

Everyone is looking at a real record, and nobody can give a straight answer.

This type of confusion matters more than it sounds. When nobody owns the answer, account managers ask clients about invoices that are already paid, your bookkeeper matches deposits manually, and month-end drags on while all three systems keep disagreeing. Oh, and every new client you get just adds to the pile.

If you run a managed services business on Autotask PSA and keep your books in QuickBooks Online, you've probably had a version of that thread. And if your connection between the two ran on Kaseya's older app, you may be rebuilding it right now. Kaseya's help center says its legacy QuickBooks Online integration relies on Intuit's AppConnect platform, which was scheduled to retire on September 30, 2026, and it points customers to the newer Smart Accounting Hub.

That makes this a good moment to settle the question underneath the connector: who should own invoicing, payment status, and the accounting records?

This guide is for MSP owners, controllers, and finance operations leads. It covers two operating models with Alternative Payments connected to both Autotask and QuickBooks Online, a worksheet for choosing between them, and the spots where Alti, our financial AI, saves your team from checking three systems to answer one question.

How Alternative Payments connects Autotask and QuickBooks Online

Autotask is where the work lives. It holds tickets, time tracking, contracts, quotes, assets, and the resources (Autotask's word for your techs) who do the work. QuickBooks Online is where the money gets accounted for. Alternative Payments is the payment platform in the middle, integrated with both.

With dual integrations, you pick one system as your primary. Our help center describes the primary as "the integration your invoices sync from" and "the system of record for your AR." The other system will receive payment status. Your Customer Success Manager helps you configure all of this during onboarding.

What the Autotask integration sends: invoices, line items, and payments

Per our Autotask integration guide:

• New invoices every hour, and updates to existing invoices once a day
• Invoice details, line items, and PDF invoices
• Customers, every hour
• Payments in real time. Payment status syncs both ways, so an invoice updated in Autotask shows the same status in Alternative Payments
• Partial payments and credits applied in Autotask, reflected in the balance your client sees

Two things don't come across. Deposits don't sync to Autotask, which is fine, because deposits belong in your accounting system. And invoices or customers you delete in Autotask aren't archived automatically, so someone has to archive them in Alternative Payments.

What lands in QuickBooks Online

Per our QuickBooks Online guide and reconciliation guide:

• Each payment syncs in real time, and invoice status syncs both ways
• Processing fees post to a fees account, and Alternative Payments will create one if you don't pick your own
• You can match payouts in the bank feed (the default), or have Alternative Payments create deposits to the bank account you choose
• Refunds show up as a negative line in a later deposit
• Chargebacks come out of a future payout and get recorded as an adjustment

Where the Smart Accounting Hub fits

Alternative Payments handles the payment side of things. Moving Autotask invoices into QuickBooks is a separate job, and for many Autotask shops that job now belongs to Kaseya's Smart Accounting Hub, which Kaseya calls a new API connector.

According to the setup guide, it syncs invoices on a 15-minute interval, logs errors in real time, maps existing accounts and invoiced items, and supports QuickBooks Online Plus and Advanced. Keep it (or one of the other sync tools you trust) passing invoices across on a regular basis, and let Alternative Payments run payments.

Some MSPs have developers build a custom integration on the Autotask API instead.

With Alternative Payments, when an invoice doesn't show up where it should, ask Alti. It checks what's holding up the invoice or customer in Autotask or QuickBooks and when it last synced. Alti reads your setup but never changes it, and if a person needs to step in, it can open a support ticket for you.

Two operating models: who owns invoicing?

In both models, Alternative Payments collects payments, and QuickBooks Online maintains your accounting ledger, deposits, and fees. The choice that you make is where invoices get finalized, because that system becomes your primary system.

Autotask as the system of record: tickets, contracts, and time tracking

Here, Autotask is the master record for customers and invoices. Contracts and time entries produce the invoice and its line items, Alternative Payments picks it up within the hour, and your clients open the same Autotask PDF your team built. QuickBooks gets the invoice from your sync tool and payment status from Alternative Payments.

It's the simplest model for teams that live in Autotask, and it keeps time tracking, billing, and the client's invoice in one place. The trade-off is that your invoices are only as accurate as your tickets. When Kaseya announced its agentic platform in April, Advisor ICT's Koos Ligtenberg said miscategorized tickets cause "all kinds of downstream issues," including "billing inaccuracies."

Here are two things you need to plan for:

• A fix takes a day: Changes to unpaid invoices reach Alternative Payments once a day, so a corrected amount won't show up in the payment portal right away.
• Voids need an owner: When someone deletes an invoice in Autotask, someone else archives the match in Alternative Payments. That can be as quick as asking Alti to archive it. Alti shows you exactly what it's about to do and waits for your OK before taking any action.

QuickBooks Online as the system of record

Here, Autotask still tracks the work, but the invoice your client pays is the one in QuickBooks. Autotask's Smart Accounting Hub for QBO moves Autotask billing over, your bookkeeper finalizes it, and Alternative Payments picks up the invoice in real time. Autotask receives the payment status.

This fits MSPs whose bookkeeper adjusts tax, discounts, or terms before invoices go out, and MSPs that bill some revenue outside Autotask, for example, hardware resale or one-off projects. Modifications to unpaid invoices sync in real time, and invoices you delete in QuickBooks archive automatically.

One note on timing: invoices reach clients only after they land in QuickBooks, so the Hub's 15-minute cycle becomes part of your billing day.

A nice side effect for the accounting side of things is that your bookkeeper can ask Alti for "a monthly report for last month" instead of exporting data from three places.

The system-of-record decision worksheet

Fill this in with your controller and bookkeeper, and keep it as a reference for go-live. Count which column wins rows 1 through 7, and make that system your primary system. Rows 8 through 10 are assigned before anything goes live, because the edge cases (voids, checks, failed payments) are where setups tend to break down.

Row 2 is the one teams usually forget to account for. If you resell telecom, Datagate can export telecom charges and taxes into Autotask, which keeps that revenue on the Autotask side of the worksheet.

A blank owner cell is a gap that you need to fix, and a row with two owners is where duplicate records come from, which also needs to be fixed.

Payment status needs exactly one writer

By default, Alternative Payments sends payment status to both systems, so invoices automatically update in Autotask and QuickBooks when a client pays. Nobody has to re-enter a payment anywhere.

The catch is your connector. Kaseya's legacy app was built to "update the payment status in Autotask when a payment is received" in QuickBooks Online, and Autotask's QuickBooks Desktop integration syncs paid dates back too. If your connector still does that, Autotask hears about the same payment twice.

Our help center covers this exact situation for HaloPSA and QuickBooks Online, where you choose which system gets payment updates. If your Autotask integration with QuickBooks writes payments back, contact our team before you go live, and we'll help you pick one app as the writer for payments.

Checks and wires

Checks are here to stay, seriously. In AFP's 2026 Payments Fraud and Control Survey, paper checks were the most targeted payment type, cited by 58% of respondents, and 72% of organizations that use checks still plan to keep using them. Truist's Chris Ward put it plainly in AFP's release: "Fraud prevention today is an operating model, not a single control."

Recording payments works the same way. Set the process once, then stick to it:

• Record a check in your primary system first. The update syncs back to Alternative Payments, and it can take up to an hour.
• Don't mark a synced invoice paid only in Alternative Payments. The next sync can flip it back to outstanding.
• Keep the invoice number identical in both systems.
• Keep one customer record per client, with the same name and account number in both systems.
• Map each Autotask billing code to the same QuickBooks product or service item and income account. Accurate mapping is what makes your financial reports trustworthy.

If something still doesn't line up, describe it to Alti, and it will explain what happened to the records coming from Autotask and QuickBooks, so you know exactly what to fix.

Paid isn't the same as settled, and your controller needs to see both

"Paid" describes an invoice. "Settled" describes your bank balance. With card and ACH, they land on different days:

1. The client pays in a click from the link on their invoice, and the invoice can read paid right away.
2. QuickBooks parks that payment in Undeposited Funds (some files call it "Payments to deposit").
3. Your processor rolls several payments into one payout and takes fees out first.
4. A single deposit reaches the bank, and your books need a single deposit record to match it.

Post every payment as its own deposit, and your bank reconciliation won't tie out. Intuit's guide to recording bank deposits shows the fix: group the payments and enter fees as a negative line.

That's how Alternative Payments builds deposits when deposit creation is on. Each payment posts at the full invoice amount, and fees go on a separate negative line, so the deposit matches what landed in your bank.

ACH adds one more wrinkle. According to our ACH chargebacks guide, bank rejections typically show up within 48 hours and move the transaction from Processing to Failed, while customer disputes can sometimes come up to 60 days later.

Alti draws the same line. Its own FAQ says a successful charge means "the payment is on its way," not that the money has settled. When your controller wants the pattern, they can ask, "Which payments failed last month, card or bank, and what were the top decline reasons?" and save the answer as a weekly Routine Report.

For the complete path from invoice to deposit, see our responsibility map for ConnectWise and QuickBooks. The money moves the same way with Autotask.

Give every owner the right seat

Intuit's Ashley Still said in an August announcement that finance teams need AI "they can stand behind when asked how a number was reached." That's a fair bar for any assistant that touches your receivables.

Alti is built into the Alternative Payments dashboard and answers from your live data. It can only do what someone's role already allows it to do. Anything that changes your account waits for approval, and every confirmed action is logged with who approved it. Here's how that maps to the owners in your worksheet, using our access levels:

• Controller or finance lead (Administrator or Sub-Admin): Handles refund requests through Alti. It issues full refunds only, a reason is required, and refunds typically reach customers in three to five business days.
• Billing team (Member): Asks how things work and handles everyday tasks like tagging customers. Alti answers from the same help articles your team reads, so the steps are current.
• Account managers (Read-Only): Ask whether a client paid and get a summary without being able to change anything. Read-only users can still ask questions and open a support ticket.
• You, the owner: Ask Alti to "give me a summary of what happened this week" and get one answer drawn from live payment data, instead of three opinions from three systems.
• Your clients: Pay by ACH or card from the payment link in their invoice email, pay part of a balance, and use Auto-Pay with a payment method on file. If a client says the billing link won't load, Alti checks whether the URL resolves and your custom domain is verified.

For the numbers your team checks every week, save the question as a Routine Report. It runs daily, weekly, or monthly, and emails up to five users on your account as a PDF, XLSX, or CSV.

See it with your own Autotask account and QuickBooks data

Fill in the worksheet for the setup you have today and send it to your bookkeeper for feedback. Then see how Alternative Payments connects Autotask and QuickBooks Online on our integrations page, or meet Alti and bring your worksheet to a demo.

Common questions

Does Autotask integrate with QuickBooks Online?

Yes. Kaseya's Smart Accounting Hub moves Autotask invoices into QuickBooks Online and replaces the older AppConnect-based integration. Alternative Payments connects to both systems for the payment side, so payments, payment status, deposits, and fees end up where they belong.

What about QuickBooks Desktop?

The Autotask integration for QuickBooks Desktop runs through Intuit's QuickBooks Web Connector, which moves invoices, timesheets, expense reports, and purchase orders from Autotask into QuickBooks. Alternative Payments has a QuickBooks Desktop integration too, and every ownership question in this guide still applies.

Do clients need an Autotask account to pay?

No. Clients pay through the Alternative Payments portal. They verify their email with a one-time code, choose the invoices they want to pay, and pick a payment method. First-time clients add basic business information once, and that's it.

Is it safe to let Alti work with our financial data?

Security works the way your dashboard already does. Alti only works with your own account's data, answers questions from a secure, read-only view, and checks every question before it runs. Per our privacy and safety page, it also filters incoming data for hidden instructions, so text planted in an invoice field to manipulate an AI gets removed before Alti reads it.