Pool Service Software With a QuickBooks Integration That Holds Up
Customers, invoices, payments and items sync both ways with QuickBooks Online — and the invoice your technician triggered at a pool this morning does not arrive in your books twice.
What the connection actually does
- Six record typesCustomers, invoices, payments, items, refunds and tax codes
- Every fifteen minutesPlus webhooks inbound and an immediate push outbound
- Three duplicate defencesIdempotent creates, a single-writer claim, number recovery
- Seven-step setupSelf-serve, with match review before anything is written
Why a Pool Route Breaks a Generic QuickBooks Workflow
Most small businesses raise a handful of invoices a month, and typing them into QuickBooks by hand is a perfectly reasonable way to run the books. A pool route is not that shape. Sixty accounts billed monthly, plus chemical charges that differ stop by stop, plus the filter clean somebody authorised on Tuesday, is several hundred line items a month that all originate at a pool rather than at a desk.
The usual result is a second set of books. The office rekeys the month into QuickBooks, and from that moment the two systems disagree in small ways that only surface at year end — a payment recorded in one place and not the other, a customer name spelled two ways, a chemical charge that never made it across because the technician logged it after the batch went out.
An integration is meant to remove that rekeying. Whether it actually does depends on some unglamorous questions most feature lists skip: which direction does each record travel, what happens when the same invoice is created on both sides, and what does the software do when your bookkeeper has already used invoice number 1041?
What Syncs, and Which Direction It Goes
“Two-way sync” is a phrase that hides a lot of detail. Here is the honest version, record type by record type, including the one place the two directions are deliberately not symmetrical.
Customers
Both directions
A customer added in either system appears in the other. You choose upfront whether Pool Runs or QuickBooks wins when the same record changes on both sides.
Invoices
Both directions, asymmetric
Invoices raised in Pool Runs are created in QuickBooks and stay in step. Invoices raised in QuickBooks are mirrored back read-only, so you can see them without Pool Runs claiming to own them.
Payments
Both directions
A card or ACH payment taken in Pool Runs lands in QuickBooks; a cheque your bookkeeper records in QuickBooks closes the invoice in Pool Runs.
Items and products
Both directions
Parts, chemicals, fee types and work-order types map to QuickBooks items, so a chemical charge on a stop arrives in the books already categorised.
Refunds
Both directions
Handled as QuickBooks refund receipts. Credit memos are not part of the integration — worth knowing before you build a process around them.
Tax codes and rates
QuickBooks to Pool Runs
Read and importable during setup so both systems agree on what is taxable. Pool Runs never writes tax codes back into QuickBooks.
The one asymmetry, stated plainly
An invoice your bookkeeper writes directly in QuickBooks has no work order and no service behind it in Pool Runs. Rather than inventing one, Pool Runs mirrors that invoice read-only, on the customer record and on a dedicated tab, so the office can see the full picture of what a customer owes. Editing it stays in QuickBooks. We would rather tell you that than let you discover it during a reconciliation.
Duplicate Invoices Are the Real Failure Mode
Ask anyone who has run an accounting integration what went wrong and you will not hear about missing features. You will hear about the month a customer received two invoices for the same service, or the reconciliation that would not balance because the same job existed twice in the books under different numbers.
It happens for boring reasons. A request times out and gets retried, and the first one had actually succeeded. Two processes pick up the same pending invoice a second apart. Or your bookkeeper, working in QuickBooks that morning, has already used the number the software was about to use.
Pool Runs treats each of those as a separate problem with a separate defence, rather than hoping none of them happens.
A deterministic request ID
Every invoice creation carries an ID derived from the invoice itself. If the call is retried after a timeout, Intuit recognises the replay and returns the original rather than writing a second invoice.
A single-writer claim
Before creating an invoice, a worker claims it in the database. The scheduled pass and the immediate push cannot both succeed, so a race between them cannot produce two documents.
Duplicate-number recovery
When QuickBooks rejects an invoice because the number is taken, Pool Runs checks whether that existing invoice is its own earlier attempt and adopts it, or allocates a fresh number, reconciles the sequence, and re-sends.
Alongside those, the scheduled pass reconciles the Pool Runs invoice-number sequence against QuickBooks, so numbers your bookkeeper used by hand are accounted for before the next batch goes out rather than after.
Connecting It Takes Seven Steps, Once
You do this yourself, from Settings, without booking an onboarding call. Nothing is written to QuickBooks until you have reviewed the matches.
Connect
Authorise Pool Runs from Settings using Intuit's standard consent screen. Tokens are encrypted and refreshed automatically.
Map accounts
Point income, payment and fee activity at the right accounts in your chart of accounts.
Match customers
Pool Runs proposes matches between your Pool Runs customers and your QuickBooks ones. You confirm, link or skip each.
Match products
The same review pass for parts, chemicals, fee types and work-order types.
Agree on tax
Compare tax rates side by side and import the QuickBooks ones you want Pool Runs to use.
Set the rules
Choose which record types sync and who wins a customer conflict.
Review and run
The initial sync runs with a progress indicator. After that the fifteen-minute pass takes over.
Afterwards there is a sync health panel showing what is synced, pending or erroring by record type, a filterable activity log of every operation with its direction and outcome, and review queues for the customers and items the matcher was not confident about. If a token expires, the connection says so rather than failing quietly.
Pricing does not change because you connected it. The integration is part of the standard plan — see Pool Runs pricing for what that includes — and the rest of the billing surface it feeds, from one-click invoices to AutoPay, is covered on invoicing and payments.
Trusted by Pool Service Professionals
How pool service companies keep the field and the books telling the same story.
“Switching from paper invoices to Pool Runs cut our billing time in half. AutoPay has been a game-changer.”
“Before Pool Runs, I was spending two hours every Friday creating invoices and chasing payments. Now invoices go out the second a job is done and most customers are on AutoPay. I barely think about billing anymore.”
Pool Service Software QuickBooks FAQ
Explore More Pool Runs Features
The books are downstream of the route. See where the numbers come from.
Stop Keeping Two Sets of Books
Connect QuickBooks Online once and let the route fill the ledger itself. Start your 30-day free trial.