Skip to content

Procore + QuickBooks

Procore and QuickBooks, without the re-keying in between.

Procore's QuickBooks connector covers the basics for QuickBooks Desktop and QuickBooks Online. We close the gaps it documents (cost types, existing projects, journal entries, deleted transactions), so your team stops reconciling the two by hand.

Written by Roberto Postolovski, Founder & Tech LeadUpdated

Today

How it works now

The connector syncs part of the job. The rest still moves by hand.

For contractors who run Procore on top of QuickBooks and still keep a spreadsheet to make the numbers agree.

  1. 01A commitment is approved in Procore and exported to QuickBooks, if the project was set up after the connector went live.
  2. 02Costs coded to G/L accounts or journal entries don't come back to Procore as direct costs, so someone adds them manually.
  3. 03A transaction deleted in QuickBooks Online stays on the Procore project until someone notices.
  4. 04Cost types show as "Other" in Procore, so job cost reports are rebuilt in Excel.
  5. 05Every month, someone reconciles Procore budgets against QuickBooks job reports line by line.

The native connector

Where Procore's QuickBooks connector stops

These limits come from Procore's own documentation for its QuickBooks Desktop and QuickBooks Online connectors:

Sources

  • One QuickBooks company per Procore site. A separate company file per project or entity isn't supported.
  • QuickBooks Desktop: cost types aren't supported and display as "Other" in Procore.
  • QuickBooks Desktop: project-specific cost codes aren't supported, and jobs at tier 3 or deeper can't be imported.
  • QuickBooks Desktop: an existing Procore project can't be linked to an existing QuickBooks job.
  • QuickBooks Desktop: ERP professional services aren't included in the implementation.
  • QuickBooks Online: projects in progress, or created before the connector was set up, can't be synced without paid help.
  • QuickBooks Online: transactions coded to unsynced items or directly to G/L accounts (journal entries, for example) don't come back as direct costs.
  • QuickBooks Online: deletions aren't detected, so a deleted transaction stays in Procore, and the connector doesn't write to the Class field.

The automation

How we replace it

We keep the connector for what it does well and add a small, monitored integration for what it doesn't.

  1. 01

    Audit

    Which of the documented limits actually affect you. Often it is two or three, not all of them, and that decides the scope.

  2. 02

    Map

    Cost codes, cost types and Class values are mapped between Procore and QuickBooks in a table your accountant signs off.

  3. 03

    Backfill

    Projects that pre-date the connector are matched once, by job number, name and customer, with every proposed match reviewed.

  4. 04

    Sync

    Journal entries and G/L-coded costs are brought back to the right Procore project. Deleted and voided transactions are detected and flagged.

  5. 05

    Approve

    Nothing changes in QuickBooks without accounting approval.

  6. 06

    Reconcile

    A scheduled comparison of both systems lists every difference, so it is handled the week it appears instead of at month end.

Typical gaps we close

  • Cost types and cost code structures
  • Projects that pre-date the connector
  • Journal entries as job costs
  • Deleted and voided transactions
  • The QuickBooks Class field
  • Monthly Procore-to-QuickBooks reconciliation

Systems involved

  • Procore
  • QuickBooks Desktop
  • QuickBooks Desktop Enterprise
  • QuickBooks Online
  • QuickBooks Web Connector
  • Excel

What stays with your team

Automation should remove the repetition, not the responsibility.

  • Approval of anything written to QuickBooks
  • Decisions on cost code and Class structure
  • Matching ambiguous projects during backfill
  • Differences the reconciliation can't explain

What changes

Measured against your own baseline, not against a benchmark.

  • Job costs in Procore match QuickBooks without a monthly line-by-line check
  • Journal entries and G/L-coded costs appear on the project they belong to
  • Deleted or voided transactions are flagged instead of lingering
  • Your existing connector stays in place and supported

Questions

Common questions

Should we use Procore's QuickBooks connector at all?
Usually, yes. It is supported by Procore and handles the standard flow. The question is which of its documented limits affect your company. We start there, and only build for the gaps you actually have.
We're on QuickBooks Desktop. Is it being discontinued?
Intuit stopped selling QuickBooks Desktop Pro Plus, Premier Plus and Mac Plus to new US subscribers in 2024. Existing subscribers can keep renewing, and QuickBooks Desktop Enterprise is still sold. If a move to QuickBooks Online is on your roadmap, we design the integration so it survives the switch.
Can you sync projects that already exist in both systems?
Yes. Existing projects are matched once (by job number, name and customer) and every proposed match is reviewed by your team before it is linked.
What access do you need to QuickBooks?
The minimum that lets the integration read and write the records in scope, agreed in writing before work starts. For QuickBooks Desktop, that typically means a connection through Intuit's Web Connector on the machine that hosts the company file.

What’s one repetitive process your team does every day?

Tell us about it. We’ll help you determine whether it can be automated, what it would take, and whether the numbers make sense.