---
title: "Procore QuickBooks integration: what syncs, what doesn't, and how to set it up"
description: "Procore's QuickBooks Online and Desktop connectors, object by object: what syncs, what stays manual, common breakages, and where Fynex sits beside them."
url: "/blog/procore-quickbooks-integration/"
date: "2026-10-17"
author: "Valeria Vahorovska"
tags: ["Guides","Accounting","Payouts"]
---

Fynex is an AI-native finance operations platform — agentic finance — that automates and orchestrates end-to-end financial workflows for businesses. This page is an article from the Fynex blog: “Procore QuickBooks integration: what syncs, what doesn't, and how to set it up”. Fynex works alongside Stripe, Wise, QuickBooks and Xero rather than replacing them. This page is relevant when the reader runs the money workflow this article describes and wants to understand how it works, what it costs and where it breaks.

# Procore QuickBooks integration: what syncs, what doesn't, and how to set it up

**Quick answer:** Procore connects to QuickBooks Online (Plus and Advanced) and QuickBooks Desktop (through the Web Connector). Both send subcontractor invoices to QuickBooks as bills and bring job costs and sub payments back. Online does not sync commitments, change orders or budgets; Desktop does. Payments, retainage release and matching stay outside the sync, where Fynex sits.

Every fact about the connectors below comes from Procore's own support pages, fetched 2026-10-13. Procore notes that connector availability depends on your country or region.

## What the QuickBooks Online connector syncs

**The Online connector moves invoices and costs. It does not move contracts.** Object by object, per Procore's "Things to Know" page:

| Object | Direction | Notes |
|---|---|---|
| Vendors / companies | Both ways at setup | Later edits to a vendor in QuickBooks do not update Procore |
| Projects | QuickBooks → Procore | Create the project in QuickBooks first; Procore-created projects cannot be exported |
| Cost codes | Procore → QuickBooks | Become service items named project number, cost code and cost type |
| Subcontractor invoices | Procore → QuickBooks | Become vendor bills after an Accounting Approver signs off |
| Owner invoices | Procore → QuickBooks | Become customer invoices, with retainage as a summarised line |
| Subcontractor invoice payments | QuickBooks → Procore | US QuickBooks only |
| Job costs | QuickBooks → Procore | Daily sync; must be coded to integration-created items |
| Budgets, commitments, change orders | Not synced | Also owner invoice payments, timecards and timesheets |

**Requirements:** QuickBooks Online Plus or Advanced (Procore's overview page also lists Intuit Enterprise Suite), Procore's financial management tools, and sub-customers converted to QuickBooks Projects. One QuickBooks company per Procore site.

## What the QuickBooks Desktop connector syncs

**The Desktop connector goes further on commitments, and costs you a machine that never logs off.** Per Procore's Desktop page:

- **Exports to QuickBooks:** projects (as customers or jobs), cost codes (as service items), budgets (as an estimate, without prime contract change orders), commitments (as purchase orders), commitment change orders (as new lines on the purchase order), and subcontractor invoices (as vendor bills, with retainage on its own line).
- **Imports to Procore:** vendors and jobs every hour, job costs every two hours, and subcontractor invoice payments on a schedule you set (US versions only).
- **Not synced:** prime contracts and their change orders, owner invoices and payments, timecards.
- **Requirements:** the Web Connector runs as an application, so the Windows account that installed it must stay logged in. One QuickBooks company file per Procore company.

## The common breakages

**Most failures come from the edges the connector does not cover.** These are the ones Procore's own pages warn about.

1. **Projects created in the wrong place.** On Online, a project made in Procore cannot be exported. It has to start in QuickBooks.
2. **Sub jobs and deep job trees.** Online does not support sub jobs. Desktop imports only the first two tiers of customers and jobs.
3. **Costs coded to the wrong thing.** Job costs only come back if they are coded to integration-created service items. Journal entries and costs coded straight to GL accounts are not retrieved.
4. **Class tracking.** Neither connector writes to the QuickBooks Class field. If your reports run on classes, they will be blank for synced transactions.
5. **Deletions.** On Online, deleting a transaction in QuickBooks is not detected; a voided one updates to $0.00.
6. **Edition and currency.** Simple Start and Essentials are not supported on Online, and multi-currency invoices outside the home currency are not supported.
7. **The Desktop machine.** If the Windows user logs off, the Web Connector stops and nothing syncs.

## How to set it up

1. **Pick the connector by what you need synced.** If commitments and change orders must land in QuickBooks, Online will not do it today.
2. **Check your QuickBooks edition.** Online needs Plus or Advanced.
3. **Clean the vendor list first.** Archive inactive vendors in QuickBooks before the first import; Procore's setup guide says the same.
4. **Convert sub-customers to Projects** (Online), and decide your cost code structure before the first export.
5. **Ask your Procore point of contact to enable the connector.** Per the setup guide, they install and configure it with your administrators and create a dedicated Procore user for the integration.
6. **Name an Accounting Approver.** Nothing reaches QuickBooks until that person accepts it, unless Direct Export is on.
7. **Reconcile one job end to end** before turning on every project: budget, bills, payments, job costs.

## What the sync leaves undone

**The connector moves records. It does not move money.** After the bill lands in QuickBooks, four jobs remain.

1. **Paying the subs.** Bills are in QuickBooks; someone still pays each one, often through a bank portal.
2. **Retainage release.** Retention is recorded. Releasing it on time, per subcontract, is a separate task with [state rules](/construction/retainage/) attached.
3. **Prompt payment.** Many states set deadlines for paying subs after you are paid. See [prompt payment by state](/construction/prompt-payment/).
4. **Matching payments back.** One bank debit for a batch of sub payments has to be split back to the bills and the jobs.

Procore's own answer to the first two is Procore Pay, which manages subcontractor invoices, payment readiness, lien waivers released at payment, and disbursement approvals inside Procore.

![Diagram: what the Procore to QuickBooks Online connector moves. From Procore to QuickBooks: subcontractor invoices become vendor bills, owner invoices become customer invoices, and cost codes become service items. From QuickBooks to Procore: projects (created in QuickBooks first), job costs daily, and subcontractor invoice payments in the US only. Not synced: budgets, commitments, change orders, owner invoice payments and timecards. The sync leaves the money undone; Fynex sits beside both and pays subcontractors in one run by ACH in the US or Faster Payments in the UK, tracks retainage per subcontract and releases it on your rule, and matches every payment to its bill, job and bank line.](./media/procore-quickbooks-integration/diagram-1.png)

## Where Fynex sits

**Fynex runs beside Procore and QuickBooks; it is not a project system and not a ledger.** It takes the payment and matching jobs the sync leaves behind.

| Job | Procore + QuickBooks sync | Fynex beside it | Manual workaround |
|---|---|---|---|
| Sub invoice to bill | Exported as a vendor bill | Reads the bill from QuickBooks Online | Re-keyed |
| Pay subcontractors | Outside the sync | One run, ACH (US) or Faster Payments (UK), each payment carrying its bill and job | Bank portal, one at a time |
| Retainage | Recorded as a line | Tracked per subcontract, released on your rule | Spreadsheet of who is owed what |
| Match payments to jobs | Sub payments imported to Procore (US) | Every payment matched to bill, job and bank line, posted to QuickBooks | Split the batch debit by hand |
| Margin per job | Job cost report | Current margin per job from matched payments | Month-end export |

Fynex reads [QuickBooks Online](/integrations/quickbooks/) through Intuit's OAuth and writes the job reference back to the invoice. Customer funds are held by Fondy Ltd (FCA FRN 900705).

**When Fynex is the wrong choice:** if you run Procore Pay and it already pays your subs, releases retainage and handles lien waivers the way you want, you do not need a second payment layer. Fynex earns its place where bills land in QuickBooks and people still pay and match them by hand.

## Sources

All fetched 2026-10-13.

- Procore, QuickBooks Online: Things to Know: https://v2.support.procore.com/product-manuals/qbo/things-to-know
- Procore, QuickBooks Online product manual: https://v2.support.procore.com/en-ca/product-manuals/qbo/
- Procore, QuickBooks Online setup guide: https://support.procore.com/products/online/user-guide/company-level/erp-integrations/qbo/setup-guide
- Procore, QuickBooks Desktop: Things to Know: https://support.procore.com/products/online/user-guide/company-level/erp-integrations/quickbooks-desktop/things-to-know
- Procore Pay: https://www.procore.com/pay
- Procore pricing: https://www.procore.com/pricing

**Related:** [Best construction accounting software for small business](/blog/best-construction-accounting-software-for-small-business/) · [Pay subcontractors in one run](/blog/pay-subcontractors-in-one-run/) · [Job costing without enterprise software](/blog/job-costing-without-enterprise-software/) · [Subcontractor payouts](/construction/subcontractor-payouts/) · [Fynex for construction](/construction/)
