Troubleshooting the TaxCloud QuickBooks Plugin

Most issues fall into one of the cases below. If none of them resolves it, jump to Send a debug log bundle at the end.

A saved invoice has no tax line

There's no "Calculate Tax" button — tax is added a few seconds after you click Save. If it doesn't appear, work through these in order:

1. Reopen the invoice from Customers → Customer Center → Transactions. QuickBooks doesn't always refresh the window you saved in; the line is usually there on reopen.
2. Check the customer's Tax Code (customer record → Sales Tax Settings). It must be Tax, not Non. See Mark a customer tax-exempt.
3. Check the invoice's TAX dropdown is set to TaxCloud Tax.
4. Check tax collection is enabled for the destination state in TaxCloud (under Thresholds). A state without collection enabled returns $0 by design.
5. Check the plugin is running — look for the tray icon; if it's missing, launch the shortcut and wait 10 seconds.
6. Confirm you restarted QuickBooks after installing or updating the plugin.
7. Open the Capture History tab in Settings to see whether the invoice was captured. If it isn't listed, send a debug log bundle (see the end of this article) — the log records why it was skipped.

"TaxCloud can't open a QuickBooks session (0x80040408)"

QuickBooks is running and the plugin can hear it, but can't open its own connection back in. The usual cause is a privilege-level mismatch — QuickBooks is running as administrator and the plugin isn't (or vice versa). Restarting QuickBooks alone won't fix it.

1. Close both QuickBooks (File → Exit) and the plugin (tray icon → Exit).
2. Right-click the QuickBooks shortcut → Properties → Compatibility and uncheck "Run this program as an administrator." Do the same for the TaxCloud plugin shortcut so both run at the same level.
3. Reopen QuickBooks first, then start the plugin.

The status keeps saying "Restart QuickBooks to enable tax calculation"

QuickBooks caches its list of integrated apps when the company file opens. Close QuickBooks completely (File → Exit, not just the window) and reopen it. Give it a full minute — the status updates on the next monitoring tick.

Tax stopped calculating in multi-user mode (0x80040410)

If it worked in single-user mode but stops when you switch to multi-user, the integration was granted with the "even when QuickBooks isn't running" option, which only works in single-user mode. Re-grant it as the attended option — you can keep running multi-user:

1. In QuickBooks: Edit → Preferences → Integrated Applications → Company Preferences.
2. Select TaxCloud QuickBooks Plugin and Remove it.
3. Restart QuickBooks. When the Application Certificate dialog reappears, choose "Yes, whenever this QuickBooks company file is open."

Automatic updates aren't applying

The plugin updates itself on launch when QuickBooks is closed. To force it: close QuickBooks, right-click the tray icon → Exit, then relaunch the plugin from its shortcut. If it still doesn't update, a firewall or a redirected %LOCALAPPDATA% may be blocking it — see Keeping the TaxCloud QuickBooks Plugin updated for the manual fallback.

QuickBooks feels slow

Usually one of:

• Antivirus scanning the plugin folders or your company file — add exclusions for %LOCALAPPDATA%\TaxCloud.QuickBooks.Plugin\, %APPDATA%\QuickBooksInvoicePlugin\, and your .QBW file.
• A second tax integration still installed (e.g. Avalara) — both fire on every save and can fight over QuickBooks. See Migrating to TaxCloud from Avalara.
• A company file on a slow network share — multi-user mode adds network round-trips to every save.

TaxCloud returned $0 when you expected tax

Check, in order:

1. Tax collection is enabled for the destination state (under Thresholds).
2. The customer isn't set to Non.
3. The item's tax code isn't a category that's exempt in that state.
4. The line has a non-zero quantity and price.
5. At least one line is taxable.

Two TaxCloud tax lines on one invoice

You should only ever see one. If you see two, the most common cause is two tax items in your Item List (one Service, one older OtherCharge), usually from an upgrade. Open Lists → Item List, find the duplicate TaxCloud Sales Tax items, and mark the OtherCharge one inactive. To clean up an affected invoice, delete the extra line and click Save.

You can't find the tray icon

1. Click the ^ chevron next to the clock — it's usually just hidden.
2. Still missing? Open Task Manager (Ctrl+Shift+Esc) → Details and look for TaxCloud.QuickBooks.Plugin.exe. If it's running but invisible, sign out of Windows and back in. If it's not running, launch the Desktop shortcut.
3. If the shortcut is gone too, re-run the installer from the releases page.

Verify the install with PowerShell

Paste this into PowerShell on the machine to run the same checks our smoke test runs:

$base = "$env:LocalAppData\TaxCloud.QuickBooks.Plugin"
$current = Join-Path $base "current"
$log = Join-Path $current "Logs\plugin.log"
$settings = "$env:APPDATA\QuickBooksInvoicePlugin\settings.json"
$run = Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Run' -EA SilentlyContinue
$proc = @(Get-Process -Name TaxCloud.QuickBooks.Plugin -EA SilentlyContinue)

[ordered]@{
  "Install present"          = Test-Path (Join-Path $current "TaxCloud.QuickBooks.Plugin.exe")
  "Update.exe present"       = Test-Path (Join-Path $base "Update.exe")
  "Plugin process alive"     = $proc.Count -gt 0
  "Process count (should=1)" = $proc.Count
  "Auto-start at login"      = $null -ne $run.'TaxCloud.QuickBooks.Plugin'
  "Log file growing"         = (Test-Path $log) -and (Get-Item $log).Length -gt 0
  "Settings.json present"    = Test-Path $settings
} | Format-Table -AutoSize

Everything should return True and process count should be 1.

Files worth knowing

• Install folder: %LOCALAPPDATA%\TaxCloud.QuickBooks.Plugin\
• Settings: %APPDATA%\QuickBooksInvoicePlugin\settings.json
• Log: %LOCALAPPDATA%\TaxCloud.QuickBooks.Plugin\current\Logs\plugin.log

Send a debug log bundle

When the cases above don't resolve it:

1. Right-click the TaxCloud tray icon.
2. Choose Save debug logs….
3. Pick a location (Desktop is fine) — the plugin writes a zip with your logs, settings (API key redacted), and basic environment details.
4. Reply to your support thread with the zip attached.

:::info The bundle never contains your API key in plain text. If support asks for detailed logs, switch Settings → Logging → Log Level to Debug, reproduce the issue, save the bundle, then switch back to Error.

:::