Using QuickBooks Online for a pool service company

What belongs in QuickBooks versus in field software

The most common bookkeeping problem in pool service companies is not a missing account or a wrong category — it is double entry. Someone writes a service ticket by hand or in a route app, then a different person re-types the same information into QuickBooks to build an invoice. Every re-type is a chance for the amount, the customer, or the line items to drift from what actually happened at the pool, and reconciling that drift is where office hours quietly disappear.

The cleaner model treats QuickBooks Online and field software as two different systems of record for two different kinds of truth. Field software should own operational detail: which technician visited which pool, what chemicals went in, what parts were used, what the customer approved, and what the resulting invoice line items should be. QuickBooks Online should own financial truth: the general ledger, the chart of accounts, tax treatment, and the reports you or your accountant use to understand the business. The invoice itself should be created once, from the recorded work, and then flow into QuickBooks — not typed twice into two systems that are supposed to agree with each other by coincidence.

A sensible chart-of-accounts and item-mapping approach

Many pool companies start with a single "Service Income" account and a single "Supplies" expense account, which is simple but hides the numbers that actually matter — repair margin versus route margin, chemical cost trend, and how much revenue trip charges and one-off work actually contribute. A modest amount of structure up front pays for itself the first time you try to answer "are repairs actually profitable" from the books instead of a guess.

• Recurring service income — separate from repair income, so you can see route revenue independent of project work.
• Repair labor income — billed labor hours on equipment jobs, distinct from recurring service.
• Parts income and parts cost of goods sold — the markup on equipment and parts is a real margin line; collapsing it into general income hides it.
• Chemicals as cost of goods sold, not a general operating expense — chemical cost scales with account count and season, and treating it as COGS lets it net against service income to show a true route margin.
• Trip charges or diagnostic fees — often small individually but worth their own item so you can see how often they are actually collected versus waived.
• Write-offs or bad debt — its own account, reviewed periodically rather than buried in a miscellaneous expense line.

In QuickBooks Online terms, this generally means creating distinct products and services items (Recurring Service, Repair Labor, Parts, Chemicals, Trip Charge) each mapped to the appropriate income or COGS account, so that every invoice line item lands in the right bucket automatically instead of requiring someone to remember the mapping invoice by invoice.

Customer and entity matching: the duplicate risk

When field software syncs customers to QuickBooks Online, the two systems have to agree on which customer record in QuickBooks corresponds to which customer in the field system. This sounds trivial until you consider how pool company customer lists actually get built over years: the same household might appear as "Bob Smith," "Robert Smith," and "Smith Residence — 123 Oak St" depending on who entered it and when.

• A sync that matches purely on customer name will eventually create duplicates — two QuickBooks customers for one real household, splitting their invoice history and confusing statements.
• A sync that matches on a stable identifier, such as an internal customer ID created at first sync and stored on both sides, is more reliable but requires an initial cleanup pass to merge existing duplicates before the identifier is assigned.
• Commercial accounts with multiple bodies of water or multiple properties under one billing entity are the highest-duplicate-risk case — verify how your field software represents "one customer, several properties" and that QuickBooks receives one customer record, not one per property.
• After any bulk import or migration, run a duplicate check in QuickBooks before your first sync of new invoices, since a sync will happily create new records rather than silently merging into ones that look similar.

Getting payments and processing fees to actually reconcile

A second common source of QuickBooks frustration is a bank deposit that does not match the invoice total, because a card processor deducts its fee before depositing. If a $200 invoice is paid by card and the processor takes a percentage, the deposit that hits your bank account is less than $200 — and if that difference is not recorded, either the invoice looks unpaid or the deposit looks unexplained.

The correct pattern is to record the full invoice amount as paid, then post the processing fee as its own expense line (commonly "Merchant Fees" or "Payment Processing") so the net amount deposited matches what actually lands in the bank. Payment integrations that post directly to QuickBooks should do this automatically per transaction; if you are recording payments manually, this is the single most common place a manual entry stops matching the bank feed.

Sales tax: a caveat, not a formula

Whether pool service labor, chemicals, and parts are taxable — and at what rate — varies significantly by state and sometimes by municipality, and some jurisdictions tax parts but not labor, or tax both differently depending on whether the work is characterized as repair versus maintenance. Getting this wrong is not a bookkeeping inconvenience; it can create real liability if tax is under-collected over time.

What to reconcile every month

A monthly reconciliation routine catches sync drift and entry errors before they compound across a full year of books. This does not need to be exhaustive, but it needs to happen on a calendar, not "when something looks off."

Recovering when sync conflicts happen

Even a well-built two-way sync will occasionally hit a conflict — the same invoice edited on both sides before syncing, a customer merged in QuickBooks that the field system still sees as two separate records, or a payment recorded in both systems independently. The goal when this happens is not to panic-fix it inside QuickBooks directly, which can make the two systems disagree even more.

1. 1Identify which system has the source-of-truth record

   For operational details like work performed, the field system is usually correct. For payment and tax treatment, QuickBooks is usually correct. Fix the conflict by correcting the system that is wrong, not by editing both independently.

2. 2Check for duplicate records before merging

   If a customer or invoice appears twice, confirm which one has the complete history before merging or deleting either — merging the wrong direction can silently drop payment history.

3. 3Re-run the sync rather than hand-entering the fix

   A manual correction inside QuickBooks that is never reflected back to the field system just creates the next conflict. Let the sync reconcile the correction where possible.

4. 4Keep a short log of conflicts and resolutions

   A repeated conflict pattern usually points to a workflow problem — for example, staff editing invoices directly in QuickBooks after they were created from field software — worth fixing at the source rather than resolving the same conflict every month.