Pest control software that syncs with QuickBooks Online

Connecting QuickBooks Online is a single OAuth handshake, done by someone with the office role or above. Hunter sends you to Intuit’s consent screen, you pick the company file, and Intuit sends you back with the company identified — Hunter never sees or stores your Intuit password.

Hunter requests Intuit’s accounting scope, which is the single permission that covers customers, invoices, payments and the chart of accounts. Hunter holds one active ledger connection per workspace, so a workspace posts to one QuickBooks company. Reconnecting to a different company clears your account mapping and every stored QuickBooks id, because those ids belong to the file you just left.

Access tokens refresh in the background, with one automatic retry if Intuit rejects a token mid-call. If the connection genuinely lapses, the integrations page shows a red "Reconnect QuickBooks" prompt and the daily ledger-health routine tells the owner; anything that failed while it was down stays queued and is retried on reconnect. When Intuit returns an error, Hunter records the Intuit transaction id alongside it, which is the reference Intuit support will ask for if a specific push ever needs escalating. Disconnecting clears Hunter’s tokens; removing the app inside QuickBooks is a separate step you should also take if that’s the intent.

It arrives line by line, not as a single summary line. Each Hunter invoice line becomes a QuickBooks sales line with its own description, quantity, rate and income account, so a job with materials and labour reports as materials and labour. Hunter’s invoice number becomes the QuickBooks document number, so a customer query about INV-1043 finds INV-1043 in both systems and your bank reconciliation matches the reference the customer quoted.

GST is exclusive on every line, with a per-line tax code, so an invoice mixing taxed and GST-free lines posts correctly rather than averaging to a wrong total. You map which QuickBooks tax code means taxed and which means GST-free once, at setup.

Issue date and due date come across as set in Hunter. The rendered Hunter PDF — the document your customer actually received, with your logo, payment instructions and pay link — is attached to the QuickBooks invoice on first push. If you use classes, Hunter applies your configured class to every invoice line so revenue splits by branch or division without re-keying.

Payments run in both directions. Record one in Hunter and it posts against the QuickBooks invoice into the account you mapped. Record it in QuickBooks, or let it come in through your bank feed there, and Hunter pulls it back — nightly, and whenever Intuit’s webhook fires — marks its own invoice paid and stops chasing the customer for money you already have.

The payment pull is incremental on the QuickBooks side: Hunter asks Intuit only for what has changed since the last run rather than re-reading your whole payment history, which keeps the nightly job fast as your file grows.

Credit notes issue as QuickBooks credit memos, and voiding in Hunter voids the QuickBooks invoice. Card processing fees are opt-in: map a fees expense account and Hunter books each Stripe merchant fee as a purchase so the amount that reaches your bank and the amount on the invoice reconcile. Leave it blank and nothing is booked.

The two integrations run on the same sync engine and cover the same objects, but the underlying APIs are not equivalent and pretending otherwise would cost you a month-end. Three differences are worth knowing before you commit.

Contact matching is narrower. Before creating a customer, Hunter searches QuickBooks for an exact display-name match; it cannot match on email address the way it does in Xero, because QuickBooks doesn’t filter on email cheaply. In practice that means a customer stored in QuickBooks under a slightly different trading name will be created rather than linked, so it’s worth tidying obvious name variants before you connect.

Credit memo application is QuickBooks’ decision, not Hunter’s. In Xero, Hunter explicitly allocates a credit note against the original invoice for the exact amount it offset. QuickBooks has a company-level "automatically apply credits" setting that owns this behaviour, so Hunter creates the credit memo and lets your file apply it. If that setting is off, expect to apply credits in QuickBooks yourself.

GST rates are inferred rather than read. Hunter reads your QuickBooks tax codes and identifies zero-rated ones by name, treating the rest as standard-rated. Xero publishes the actual effective rate on each tax rate, so Hunter reads the real number there. This affects the quality of the automatic mapping suggestion at setup, not the tax on your invoices — the tax code you map is what posts, and Hunter’s own tax rates drive the invoice figures either way. Check the suggested mapping rather than accepting it, which is good practice on either ledger.

On connect, Hunter reads your chart of accounts and tax codes and proposes a mapping — an income account for sales, an account for payments to land in, tax codes for taxed and GST-free lines, and a merchant-fee expense account if one is obviously named for it. The suggestion fills blanks only and never overwrites a choice you’ve made, so you can connect on day one and refine over your first week. Revenue can be split so materials, labour and fees each post to their own income account.

Hunter remembers the QuickBooks id of every record it has synced and fingerprints what it sent, so unchanged records aren’t pushed again. When Intuit rate-limits a call, Hunter waits the interval it asks for and retries; if it still can’t get through, the record is queued rather than dropped.

Drift is handled the same way as on Xero. Hunter subscribes to Intuit’s webhooks, and when a synced invoice changes it compares the two versions: a payment it pulls in automatically, but a changed total or a one-sided void is flagged for a person to resolve rather than overwritten in either direction. Failures group by cause on the integrations page with the specific fix and affected invoices, a self-healing routine clears the fixable ones each morning, and a monthly close check tells you if anything issued this month never made it to the ledger.

Hunter does not sync your pricebook to QuickBooks items — invoice lines post as descriptions against an income account, not against an item reference, so stock and inventory stay in Hunter. It does not sync bills, supplier invoices or purchase orders, so the accounts-payable side of your file is untouched. There is no payroll integration and no bank feed; timesheets export as CSV for whatever you run payroll in.

Credit memos are push-only — one raised directly in QuickBooks doesn’t come back to Hunter — and a ledger-side edit to a synced invoice is surfaced as drift rather than applied automatically. QuickBooks Desktop is not supported; this is QuickBooks Online only. Hunter connects to one company file at a time, and MYOB is not currently supported on either rail.