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

Problem guide

Two systems show different numbers

Two systems disagree because each counts the same job, order or sale at a different moment and under different rules. An operating system, such as a field app, a store or a point of sale, counts revenue when the work is invoiced or the order is placed; the accounting system counts it when the record arrives there. Corrections made after the handoff travel as adjustments and credit memos, some edits can be saved to one side only, and lines that do not map arrive as a generic item. Pick the book of record for each number, reconcile item by item every month, and make corrections in one place.

Tangled cables and an old desktop tower under an office desk

How it actually happens

Two systems that disagree are usually both doing exactly what they were set up to do. They count the same job, order or sale at different moments, under different rules.

Take a service company running ServiceTitan for the field and QuickBooks for the books. A job is invoiced in ServiceTitan on Tuesday, and the owner's dashboard shows the revenue. QuickBooks gets nothing until the invoice is batched, posted and exported, so on any day before the export runs, the two are apart by every unexported invoice. Then the details pull them further apart. A refund after export does not change the original invoice; it becomes an adjustment invoice that lands in QuickBooks as a credit memo. A class shows up only if someone created the same class in QuickBooks by hand. Job type and job summary never cross at all. Each rule is documented, and each one is a small, permanent difference.

A bookkeeper described on Reddit's r/Bookkeeping in July 2026 what that looks like at month end: about $20,000 in deposits on the ServiceTitan deposit report that never reached the bank, and about $50,000 that reached the bank and was missing from the ServiceTitan report.

The same shape holds anywhere an operating system feeds the books. An online store reports orders; the bank receives payouts net of fees and refunds. A restaurant's point of sale reports covers and comps by day; the bank receives card settlements and delivery app payouts on other days. A law firm's billing system shows a bill paid from trust; the ledger waits for someone to post the transfer.

Some differences are made by people. ServiceTitan's newer QuickBooks Desktop connector lets permitted users edit an exported invoice and choose Save and Sync or Save and Bypass. Bypass updates ServiceTitan only. Every bypassed edit is a deliberate difference that someone has to remember at month end.

Construction has the same shape at a larger scale. The project manager reads job cost in Procore; the controller reads Spectrum, Vista or Sage. Spectrum costs arrive in Procore as lump sums by budget code. Prime contract invoices, commitment invoices, payments and timecards do not cross between Procore and Spectrum at all. The two cost reports are each correct for what they hold and cannot match.

Why the argument repeats every month

The month-end meeting about whose number is right never ends, because each side is right about its own system. The question that ends it is a different one: for this job, order or day, which rule made the difference? Asked record by record for one month, the answers fall into a handful of reasons, and each reason has a fix.

Signs you have this problem

  • The owner's revenue number from the operating system does not match the controller's from the books
  • The manager's cost for a job, client or project and accounting's cost disagree
  • Month-end starts with an argument about whose report is wrong
  • Invoices show as unpaid in one system and paid in the other
  • A correction made in one system never shows up in the other

What usually causes it

  • The same information is entered separately into each systemThe re-entry trap
  • Each system updates on its own schedule, so one is always behind the otherThe handoff gap
  • Credits, refunds, partial work and rework are recorded differently in each placeThe exception swamp

Find your cause

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

  1. Is the difference largest just after month end and smaller a week later?If yes: it is mostly timing: invoices or sales not yet sent to accounting. Run the transfer daily and reconcile after it.
  2. Are corrections made in one system and not the other?If yes: the systems are being edited separately, or edits are being bypassed. Pick one place to correct.
  3. Do some lines arrive in the books under a generic item or with no class?If yes: items and classes are not mapped. Map every item once.
  4. Does a job's or project's cost differ between the manager's report and accounting's?If yes: the operating system is showing summary cost on a schedule. Compare by cost code or category on the same date before deciding either is wrong.

How it breaks in each industry

Service companies on ServiceTitan and QuickBooks
The dispatcher and the owner read revenue in ServiceTitan; the controller reads QuickBooks. A job counts in ServiceTitan when it is invoiced and in QuickBooks when the batch is exported. Refunds and corrections after export arrive as adjustment invoices and credit memos rather than edits, so the two sides only meet again at the end of the chain.
Contractors on Procore with Sage, Vista or Spectrum
The project manager reads job cost in Procore; the controller reads the ERP. Costs come across as summaries by cost code on a schedule, while commitments, change orders and payroll each post on different days, so the two reports are both right and still different.
E-commerce and consumer brands
The store counts a sale when the order is placed. The books see it when the payout lands, net of fees, refunds, chargebacks and reserves, often as one deposit covering many orders. A refund issued in the store weeks later pulls the two apart again unless someone matches it to the original order.
Restaurants and hospitality
The point of sale reports sales by day, with comps, voids, tips and delivery orders each handled its own way. The books see card settlements, delivery app payouts and cash deposits on later dates, so a day's sales in one system and the bank in the other never line up without a daily match.

Where it breaks between systems

ServiceTitan and QuickBooks Desktop (export)
Invoices with a net positive value export as invoices and those with a net negative value as credit memos. A class appears in QuickBooks only if the business unit has one in ServiceTitan and the same class was created by hand in QuickBooks, and customer names are limited to 41 characters. Job type and job summary do not export.[1]
ServiceTitan exported invoices
Once an invoice has been exported it cannot be changed or deleted directly; changes go through an adjustment invoice, which exports as an invoice if its net is positive and as a credit memo if negative.[2]
ServiceTitan Web Connector to QuickBooks Desktop
With the newer Web Connector and the right permission, exported invoices can be edited. Save and Sync updates both systems; Save and Bypass updates ServiceTitan only, and the invoice is marked Bypassed. A bypassed edit is a documented way for the two to disagree.[3]
ServiceTitan and QuickBooks Online
Transactions you bypass are marked Exported in ServiceTitan even though they never reach QuickBooks Online, and a batch can show Exported while items inside it are still Pending.[8]
ServiceTitan inventory and QuickBooks Online
Returns to vendors and truck-to-truck transfers do not export to QuickBooks Online; they are batched, bypassed and created there by hand. ServiceTitan recommends most shops not track inventory quantities in QuickBooks Online at all, so the two will never agree on what is on the trucks, by design.[7]
Housecall Pro and QuickBooks Online
After the first sync, changes to an invoice's line items, quantities, prices or descriptions do not update QuickBooks Online until someone syncs it again by hand, and invoices deleted or canceled in Housecall Pro have to be deleted in QuickBooks by hand.[9]
FieldEdge and QuickBooks
QuickBooks blocks any transaction dated on or before its Closing Date, so work finalized late for a closed month cannot post to it. Customers, jobs and items created in QuickBooks do not sync back to FieldEdge, and in QuickBooks Online jobs post as sub-customers, not projects.[10]
Simpro and Xero
Labor cost in Simpro is not posted to Xero, only hours against each pay rate, and inventory journals arrive in Xero as manual journals. Xero's inventory account is unrelated to the inventory Simpro tracks.[11]
Jobber and QuickBooks Online
The sync is one way, Jobber to QuickBooks, paid status no longer syncs from QuickBooks back to Jobber, and one-off line items arrive in QuickBooks under the name Custom Service.[4]
Procore and Trimble Spectrum
Spectrum costs come into Procore as lump sums against budget codes; transaction detail is a custom add-on. Commitment invoices, prime contract invoices, payments and timecards do not sync, the integration supports one Spectrum company file per Procore site, and sub jobs are not supported.[5]
Procore and Trimble Vista
Job cost syncs as a summary into an ERP Direct Costs column unless transaction-level syncing is enabled for the project, new cost codes have to be created in Vista, the automatic sync runs once an hour on a schedule that cannot be changed, and budget units of measure and quantities do not sync: the budget sync is amounts only.[6]

By the numbers

FigureWhat it measures
49%, 44%, 13%[12]What contractors said they do when their apps do not integrate: move data by hand (49%), through spreadsheets (44%), or not at all (13%); more than one answer allowed (JBKnowledge 2020 ConTech Report, as reported by Construction Dive, January 2021; sample size not given).
23%[13]Specialty contractors whose most frequent method for financial management is spreadsheets, with another 14% relying mostly on manual methods (Dodge Data and Analytics survey of 537 contractors in four countries, sponsored by Procore, 2022).

Rules that apply

IRS record retention[16]
No rule requires your field system to match your books. The records that count are the ones behind the return you file: the IRS says to keep them three years in most cases, at least four years for employment taxes, and longer in specific cases such as unreported income or bad-debt deductions.
26 U.S.C. 460, long-term contracts[14]
For tax, income on a long-term contract is reported on the percentage-of-completion method, with exemptions for home construction contracts and for contracts expected to finish within two years by a taxpayer under the section 448(c) gross receipts test. A contractor above that test can carry a tax number, a financial-statement number and a field-system number for the same job, each correct for its purpose.

Measure it in your own shop

From: Invoiced revenue by job from the field system and revenue by job or class from the ledger (QuickBooks, Sage, Vista or Spectrum), for one closed month.

  1. Export both lists and match them on job number.
  2. Sort every job into one of three groups: in the field system only, in the ledger only, or in both with a difference of more than a dollar.
  3. For the third group, note the reason for each difference: tax, discount, retainage, a credit memo, or a line that synced as a generic item.
  4. Do this before any cleanup journal entry.

Reading it: The first two groups are the gap: work not exported, or entered by hand in the books. The third group shows which rules differ between the systems. The reasons repeat, and each repeat is one fix.

What does not fix it

A new integration
If materials and classes still have to be created by hand in the accounting system and exported invoices still change only through adjustments, the new connector carries the same differences faster. Those are documented product behaviors, not setup mistakes.
Reconciling once a year
By December, each month's differences have been corrected one credit memo at a time, and the reasons are lost. Monthly, by job, the reasons are still fresh.
Telling project managers to use the accounting number
On Spectrum, the project manager sees accounting cost only as lump sums by budget code unless the transaction add-on is bought, and hours entered in Procore timesheets do not post to Spectrum. The PM needs both views, labeled.

What to try this week

  1. Name the book of record for each numberWrite down which system is right for each number people argue about: revenue and receivables from the books, work in progress from the operating system, committed cost from the project or purchasing system. Reports quote their source.
  2. Reconcile record by record before you close the monthMatch invoiced revenue by job, order, client or location between the operating system and the ledger, and settle every difference before the books close, not at year end.
  3. Correct in one place onlyDecide where corrections are made, usually the system where the work or sale happens, and make them so they flow to the books. A fix typed into each system separately is two chances to disagree.
  4. Map every item onceMake sure every service, product, part and fee in the operating system has a matching item and class in the accounting system, so nothing arrives as a generic line.

Where do-it-yourself stops

These steps make the gap smaller and explain what is left, but the two systems still count at different moments, and someone still reconciles them by hand every month. The lasting fix is a tool built around your operating system and your books, so each fact is captured once and arrives in both in the same shape. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Which number is right, the field system or the books?

The books are the record you report and file from. The field system is what operations runs on. The difference between them is mostly timing and mapping, and a monthly reconciliation by job tells you which.

Why can't we edit an invoice after it goes to QuickBooks?

ServiceTitan locks an exported invoice; changes go through an adjustment invoice, which arrives in QuickBooks as an invoice or a credit memo. With the newer QuickBooks Desktop Web Connector and the right permission, exported invoices can be edited and synced.

What does Save and Bypass do in ServiceTitan?

It saves an edit to an exported invoice in ServiceTitan only and marks it Bypassed; QuickBooks is not updated. Use it rarely, and reconcile every bypassed invoice by hand.

Why does Jobber show invoices as unpaid that QuickBooks shows as paid?

Jobber's current QuickBooks Online sync is one way, and paid status no longer syncs from QuickBooks back to Jobber. A payment recorded in QuickBooks does not close the invoice in Jobber.

Why does ServiceTitan say Exported for something that is not in QuickBooks Online?

Because it was bypassed. ServiceTitan's help center says bypassed transactions will not appear in QuickBooks Online but will show as Exported in ServiceTitan. Returns to vendors and inventory transfers are bypassed on purpose, since they cannot export to QuickBooks Online, and have to be entered there by hand; every one is a place the two can drift.

How long do we have to keep these records?

The IRS says three years in most cases, at least four years for employment tax records, six years if income was underreported by more than 25 percent, and seven years for a bad-debt or worthless-securities claim.

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.