Your books and your route, reading the same numbers.
Accounting integrations fail in predictable ways: duplicate customers, invoices posted to the wrong account, payments recorded twice, and a bookkeeper's edit silently reverted. POOLIO's QuickBooks integration is built around preventing exactly those four.
- Entity mapping between POOLIO and QuickBooks records
- Queued outbound sync with readiness checks before send
- Duplicate scoring and field-level conflict resolution
- Exact-once payment posting and a reconciliation view
Integration model
How the sync is structured
- Step 1
Connect securely
OAuth connection with encrypted token storage, connected and managed by an owner or admin from the integrations workspace.
- Step 2
Map accounts first
Income account, default line item, and write-off item are configured before anything syncs. Missing mapping blocks outbound documents rather than creating bad entries.
- Step 3
Link entities
Customers, items, invoices, estimates, and payments are linked one-to-one through a mapping table so identity is stable over time.
- Step 4
Sync in both directions
Outbound changes drain from a queue; inbound changes are pulled so edits made in QuickBooks are detected.
- Step 5
Resolve conflicts explicitly
When both sides changed, the difference is shown field by field and a human chooses. Duplicates are scored and linked or dismissed.
- Step 6
Reconcile the period
A reconciliation report compares what POOLIO believes against what QuickBooks holds, with a recovery path for stuck operations.
Operational outcomes
What the bookkeeper stops doing
Re-keying invoices
Invoices created from service and repair work queue straight into QuickBooks.
Hunting duplicate customers
Likely duplicates are scored and resolved in one workspace instead of found months later.
Chasing payment mismatches
Stripe payments post exactly once with a reconciliation report to verify the period.
POOLIO organizes the work and the follow-up. Results depend on your pricing, your route, and how your team uses the system — POOLIO does not guarantee revenue outcomes.
Who it is for
Who this is for
Owners who do their own books
Enough structure that the year-end cleanup is not a project.
Companies with an outside bookkeeper
Their edits in QuickBooks are detected and reconciled instead of being overwritten.
Companies switching to POOLIO
An initial sync wizard establishes mapping before ongoing sync is enabled.
Companies with mixed revenue
Recurring service and repair revenue mapped to the accounts you actually report on.
Buyer checklist
Accounting integration checklist
- Are records linked by ID, or matched by name each sync?
- Can outbound documents be blocked when mapping is incomplete?
- Are conflicting edits surfaced or silently resolved?
- Is duplicate detection part of the workflow?
- Can a payment be posted twice by a repeated webhook?
- Is there a reconciliation report for a period?
FAQ
Frequently asked questions
What does POOLIO sync with QuickBooks Online?
Customers, pricebook items, invoices, estimates, and payments. Records are linked through an entity mapping table so each POOLIO record has a known counterpart in QuickBooks rather than being matched by name every time.
Is the sync one-way?
The architecture is two-way: outbound changes queue into a sync outbox, and inbound changes are pulled from QuickBooks so edits made by your bookkeeper are detected rather than silently overwritten.
What happens when the same record is edited on both sides?
It becomes a conflict, surfaced in the workspace with the field-level differences so an owner or admin decides which value wins. POOLIO does not guess.
How are duplicates handled?
The workspace scores likely duplicate customers and items between the two systems and lets you link or dismiss each pair, which is where most accounting integrations quietly go wrong.
Do I need to configure anything before syncing?
Yes. Account mapping — income account, default item, and write-off item — must be set before outbound documents are allowed to send. POOLIO blocks documents that would create bad ledger entries and tells you exactly what is missing.
How are Stripe payments posted?
Payments are posted to QuickBooks with exact-once tracking so a payment cannot be recorded twice, even if a webhook is delivered more than once.
Review your QuickBooks setup with us
We will walk through mapping, duplicates, and reconciliation against your chart of accounts.