Fox & SantiagoTechnology, applied.Call (877) 244-9687

Problem guide

The accounting system and the app that runs the work don't talk

They don't talk because every connector carries only some record types, under strict matching rules, and a person handles whatever it refuses. Jobber syncs one way and not at all with QuickBooks Desktop. Procore holds budgets and commitments for an accounting approver before Sage 300 CRE sees them. Write down what your connector refuses, then design the work around that list.

Tangled cables and an old desktop tower under an office desk

How it actually happens

Most businesses that say the two systems don't talk have a connector installed. The trouble is what the connector agrees to carry, and the conditions it sets before it carries anything.

Start where the work is recorded. A technician finishes a repair and takes a card payment on the tablet. A store ships an order and later refunds half of it. A clinic posts a visit and waits on the insurer. The invoice or the sale is the easy part: on most pairs it crosses to the books once the office batches it or the sync fires. The payment, the fee, the refund and the vendor bill are another story. Even ServiceTitan's own help pages disagree on whether vendor bills reach QuickBooks Online. Housecall Pro sends every payment to Undeposited Funds on QuickBooks Desktop and leaves the card fee for a manual journal entry. Simpro will not send an overpayment to Xero at all, because Xero cannot take one. Each of those records still has to reach the books, so the bookkeeper types it.

One user in a small ServiceTitan forum put the end state in a sentence in April 2025: that user does not upload payments at all, but enters them in QuickBooks and then a second time in ServiceTitan. In a 2024 thread, a consultant described a client whose payroll administrator spent three days a week typing in each employee's hours. Those are single businesses, not rates, but the mechanism is the same everywhere: the connector covers the common record, and a person covers the rest.

Then come the match rules. A new customer exported from ServiceTitan to QuickBooks Desktop has to match an existing name exactly, commas and spaces included, or QuickBooks creates a second customer. Housecall Pro needs tax rate names to match down to a trailing space. Touchless journal entries fail on an account name with different capitals. Nobody's job description says "keep the names identical in two systems," so nobody does it until an export fails.

Then the machinery. A desktop connector needs one particular office computer awake, logged in and running a QuickBooks version no more than three years old. On Procore with Sage 300 CRE, the project manager's budget, commitments and change orders go to an accounting approver by default, and nothing moves until that person accepts them. A bookkeeper on r/Bookkeeping described the ServiceTitan link as one that randomly stops connecting and leaves a backlog of unexported payments in the register.

Put together, the connection is not a pipe. It is a set of refusals, rules and queues, and a person works all three every day without anyone calling it a job.

Name the person who is the connection

Every business with this problem already has an integration: it is the bookkeeper, office manager or accountant who knows which records need typing, which names have to match and which queue to check. Write down what that person does in a week. That list is the specification for whatever replaces the manual work, and it is the first thing lost when that person leaves.

Signs you have this problem

  • A bookkeeper keys bills, payments or refunds into the books that already exist in the system where the work is recorded
  • The accounting system shows two records for the same customer, one with a number on the end
  • The sync stops when one office computer is asleep, logged off or upgraded
  • Budgets, orders or invoices sit waiting for someone in accounting to accept them
  • Export errors pile up and get cleared in a rush at month end

What usually causes it

  • The connector refuses whole record types, so a person enters them by hand on the accounting sideThe re-entry trap
  • Customer names, tax rates, accounts and codes have to match exactly in both systems, and nobody owns keeping them matchedThe field-to-office split
  • Failed exports and items awaiting approval sit in a queue only one person opensThe invisible queue
  • Overpayments, split payments, card fees, refunds and imported records fall outside what the sync can carryThe exception swamp

Find your cause

Ask these in order. The first yes is usually where yours starts.

  1. Does someone enter bills, payments, refunds or card fees in the books that the operating system already has?If yes: the connector refuses that record type. Start with the refusal list.
  2. Do customers show up twice in the books, or do exports fail on a tax rate or account name?If yes: the match rules are breaking. Fix names before the first export, not after.
  3. Does the sync stop when one computer is off, asleep or upgraded?If yes: the connector has no home. Give it one machine and one owner.
  4. Do budgets, commitments, orders or change orders wait in accounting for days?If yes: the approval queue is the bottleneck. Make it the first screen of the day and name a backup approver.
  5. Do export errors only get cleared when the month closes?If yes: nobody reads the error list daily. Clear it every morning and export before closing the period.

How it breaks in each industry

HVAC and plumbing service
The technician collects payment on site in ServiceTitan, Housecall Pro or Jobber, and the invoice crosses to QuickBooks. The payment, the card fee and any overpayment are where it breaks: depending on the pair, the bookkeeper deposits, splits or re-enters them by hand before the bank reconciliation can tie out.
Specialty and general contractors on Procore
The project manager builds budgets, commitments and change orders in Procore. By default each one waits in an approval queue until accounting accepts it into Sage 300 CRE, and cost codes have to exist in the ERP first, so the PM and the controller see different jobs for days at a time.
Electrical, fire and security contractors on Simpro and Xero
Customer payments are the weak spot. An overpayment never reaches Xero, a payment spread over several invoices arrives as separate payments, and a contact created in Xero after the first import never comes back to Simpro.
E-commerce and consumer brands
The store records each order, refund, discount and processor fee, and the payout lands in the bank as one net deposit. The bookkeeper breaks that deposit back into sales, fees and refunds by hand, and every partial refund or chargeback is another line that has to match.
Healthcare practices and clinics
Visits, charges and insurance payments live in the practice management system. A payer pays many claims in one deposit, with adjustments and denials attached, and the books see only the deposit until someone posts the detail across.
Law firms
Time, invoices and retainers live in the practice management system, and the general ledger lives in accounting. A retainer deposited to trust and later moved to operating as fees are earned has to be recorded correctly on both sides, and a mismatch is found at reconciliation.

Where it breaks between systems

ServiceTitan and QuickBooks Online
ServiceTitan's own documentation disagrees on vendor bills: its batch article says they cannot be exported to QuickBooks Online, while its bill-export article (May 2026) describes bill fields crossing to QuickBooks Online, so whether bills sync depends on how the account is set up. Everything else moves in three steps, batch, post, then export, and once a transaction is posted or exported it changes only through an adjustment invoice.[2]
ServiceTitan and QuickBooks Desktop (customer records)
On a customer's first exported invoice, the ServiceTitan name has to match the existing QuickBooks customer exactly, including commas and spaces, or QuickBooks gets a duplicate customer. After the first match, ServiceTitan syncs on its own ID, which it appends to the QuickBooks name.[3]
ServiceTitan and QuickBooks Desktop (field lengths)
Error 3070 means a ServiceTitan value is longer than QuickBooks allows. For invoice and purchase order numbers, ServiceTitan says to keep them under 11 characters.[4]
ServiceTitan Web Connector
The QuickBooks company file and the Web Connector both have to be open on the same computer, and the QuickBooks version can be no more than 3 years old. The export depends on that office machine being up.[5]
ServiceTitan Touchless Integration and QuickBooks Online
Journal entries fail when the QuickBooks period is closed, when account names differ in spelling, spacing or capitals, when an account is inactive, or when a business unit is missing. A closed-period failure is fixed by opening the period in QuickBooks, resyncing from ServiceTitan, and closing it again.[6]
Jobber and QuickBooks
Jobber connects only to QuickBooks Online, and the current sync runs one way, Jobber to QuickBooks, with Jobber as the source of truth for clients, products and services. QuickBooks Desktop users have no sync at all.[7]
Jobber and QuickBooks Online (rounding)
Jobber keeps the decimals and rounds only the invoice total; QuickBooks rounds every line. With a discount and a mix of taxable and non-taxable lines, Jobber applies the discount to non-taxable lines first while QuickBooks spreads it across all lines, so totals can land a few cents apart. The invoice still syncs, with a warning.[8]
Housecall Pro and QuickBooks Desktop
After connection the sync runs one way. Inventory items and multiple tax codes are not supported, every payment lands in Undeposited Funds, card processing fees need a manual journal entry, and payments or changes on jobs imported from QuickBooks have to be added to QuickBooks by hand.[9]
Housecall Pro and QuickBooks Online
Tax rate names must match exactly in both systems, down to capitals, punctuation and a trailing space, and compound tax rates are not supported. Estimates never push to QuickBooks Online.[10]
Procore and Sage 300 CRE
Budgets, commitments, commitment change orders and prime contract change orders have no on-demand sync; they go to an accounting approver who accepts or rejects them for export. Projects already underway when the connector is installed cannot be synced without paid professional services, and new cost codes must be created in the ERP.[11]
Procore and Sage 300 CRE (sync timing)
For most auto syncs, the Sage server pushes to the hh2 service about every 5 minutes and Procore checks hh2 every 30 minutes. A change entered in Sage is not in front of the project manager the moment it is posted.[12]
Procore and Sage 300 CRE (subcontractor invoices)
Lines that net to zero dollars are not sent, a subcontractor invoice over the approved amount plus Sage's tolerance is rejected as overbilling, and an invoice with no expense account in the distribution is rejected, often because Sage control accounts are turned on.[13]
Simpro and Xero
A payment larger than its invoice does not export, because Xero cannot process overpayments, and contacts created in Xero after the initial import never transfer to Simpro.[14]
BuildOps and QuickBooks Online
BuildOps integrates only with Non-Inventory and Service type items in QuickBooks, and new items have to be created in BuildOps, which exports them when saved.[15]
FieldEdge Connector and QuickBooks Desktop
FieldEdge works with one connector at a time; more than one can create double entries. Entries post under whoever is logged into QuickBooks on that computer, a password change can mean redoing the connector certificate, and Xplor tells users to keep that computer from going to sleep.[16]

By the numbers

FigureWhat it measures
37%, 29%, 16%[17]Contractors who move data between apps that do not integrate by CSV file (37%), through a custom-built integration (29%) or by email (16%); more than one answer allowed (JBKnowledge 2020 ConTech Report, reported by Construction Dive, January 2021; sample size not given).
5% and 34%[17]Respondents saying all of their apps integrate (5%), against those saying three or fewer of their apps integrate (34%), same JBKnowledge 2020 report.
25%[18]Lack of integration as the top reason contractors were dissatisfied with technology bought from vendors, ahead of difficult to use (22%) and poor mobile access (20%), in FMI's 2020 Industry Report, a study sponsored by Procore.
34% vs 16%[18]In the same FMI report's list of challenges with construction technology, not being adopted by everyone (34%) ranked well above not integrating (16%). A connector cannot sync data the crew never enters.
36%[19]Construction leaders who named poor fit with current processes and procedures as the main reason technology fails them; 25% blamed low adoption (FMI, Q2 2019 quarterly).

Rules that apply

FAR 22.406-6(a) and (b), federal certified payrolls[20]
On federal contracts with the Davis-Bacon clauses, weekly payrolls and statements of compliance for the contractor and every subcontractor are due within 7 calendar days after the regular payment date. If they are late, the contracting officer withholds an amount from payments due. Hours that live in the field app and pay rates that live in payroll have to meet every week.
29 CFR 5.5(a)(3)(ii)(A), certified payroll responsibility[21]
The contractor or subcontractor submits certified payrolls for each week covered work is performed, and the prime is responsible for submitting the payrolls of all its subcontractors.
40 U.S.C. 3133(b), Miller Act payment bond[22]
A supplier or subcontractor not paid in full within 90 days after last furnishing labor or material may sue on the federal payment bond; a second-tier claimant must give the prime written notice within 90 days of last furnishing, and suit must be filed within one year. These clocks run from the work, not from when the books record it.
49 CFR 26.29(a) and (b), DOT-assisted prompt payment[23]
On work funded through state DOTs, transit agencies and airports, primes must pay subcontractors within 30 days of receiving each payment, and release retainage within 30 days after the sub's work is satisfactorily completed. A customer payment that never crosses from the field app to the books cannot start that clock on time.

Measure it in your own shop

From: One closed month of transactions in your accounting system with the user who entered each one (the QuickBooks audit log, or the entered-by field in Sage or Xero), plus the connector's export error list or approval history for the same month.

  1. Split the month's entries into those created by the integration user and those keyed by a person.
  2. For each hand-keyed entry, check whether the same order, bill or payment already exists in the operating system, and tag it by type: bill, payment, fee, refund, inventory, code, other.
  3. Count the export errors and approval-queue items for the month, and note how many days each one waited before it cleared.

Reading it: Hand-keyed entries that duplicate operating records are the work a person does as the connection, and the tags show which record types your connector refuses. The waiting days show how far the books ran behind the work. Fix the largest tag first.

What does not fix it

Swapping to a different connector
Many refusals sit on the accounting side. Xero cannot take an overpayment and BuildOps sends only non-inventory and service items to QuickBooks Online, so a new connector meets the same limits.
Installing a second connector as a backup
Xplor warns that more than one FieldEdge connector can post double entries. Two pipes into one company file make the reconciliation worse, not safer.
Hiring another bookkeeper
It adds hands to the retyping without shrinking it. The refusal list stays the same length, and now two people need to know it.
Moving everyone onto one big system
In FMI's 2020 construction report, technology not being adopted by everyone was the most common challenge, more than twice as common as failing to integrate. A system the team avoids moves the gap from the connector to the people doing the work.

What to try this week

  1. Write the refusal listOpen your connector's help page and list every record type it does not carry: vendor bills, payments, refunds, inventory, estimates, timecards, direct costs. Next to each, write who enters it on the accounting side today and how often.
  2. Match names before the first exportBefore a new customer, tax rate, GL account or class is first exported, compare its spelling in both systems character by character, commas, spaces and capitals included. Fix the copy in the operating system, not the books.
  3. Give a desktop connector a home and an ownerOn QuickBooks Desktop, run one connector on one computer that never sleeps, with the company file open and a named person who checks it each morning. A second connector installed as a backup is a source of double entries.
  4. Clear the error report before anything elseMake the export error list or the approval queue the first screen the bookkeeper opens every day. Name a backup approver so the queue does not wait for a vacation to end.
  5. Create codes in the books firstWhen the accounting system owns the chart of accounts, cost codes or service codes, create new ones there first. On Procore with Sage 300 CRE this is required. Put it in the setup checklist for every new job, client or product line so nobody waits on a code that does not exist yet.
  6. Export before you close the periodRun the last export of the month before closing the accounting period. A transaction dated inside a closed period either fails or forces someone to reopen the books.

Where do-it-yourself stops

These steps cut the duplicates and the surprises at month end. They leave the refusal list in place: every record the connector will not carry is still typed by a person, and the queue still depends on someone remembering to open it. Closing that gap takes a tool built around the system that runs your work and your accounting system, so the records your connector refuses arrive in the shape the books accept. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Why don't ServiceTitan payments show up in QuickBooks Online?

It depends on the account. ServiceTitan's batch article says vendor bills cannot be exported to QuickBooks Online, while its May 2026 bill-export article describes bills crossing over. Check your own settings, then test one bill end to end before trusting either page. Invoices export through batch, post and export.

Why does QuickBooks Desktop have two records for the same customer?

On the first invoice export, ServiceTitan looks for a QuickBooks customer whose name matches exactly, commas and spaces included. If none matches, it creates a new customer. After that it syncs on its own ID, appended to the name.

Does Jobber sync with QuickBooks Desktop?

No. Jobber's integration is with QuickBooks Online only, and the current version sends data one way, from Jobber to QuickBooks.

Why do Procore commitments take days to reach Sage 300 CRE?

By default they do not sync on demand. Budgets, commitments and change orders go to Procore's ERP Integrations tool, where an accounting approver accepts or rejects each one for export. Procore also offers a direct export option that skips that step.

Can a project already underway be connected between Procore and Sage 300 CRE?

Not by the standard connector. Procore says projects in progress or created before the integration was connected cannot be synced, and offers professional services for them at an additional fee.

Next step

How we fix this

This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.

Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.