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

Problem guide

Reports for the owner are built by hand

Owner reports get built by hand because each system holds a different slice of the business, updated on its own schedule, and one person has to make the slices agree. The operating system has work accounting has not received, and accounting has costs the operating system has not seen. ServiceTitan's help center says batches are not sent to QuickBooks Online, so exported work is matched transaction by transaction. Set one cutoff per number and check exports before building.

Tangled cables and an old desktop tower under an office desk

How it actually happens

Picture a Monday at a contractor that runs a field system, a project system and QuickBooks or Sage. The owner wants last week on one page: revenue, gross margin by division, cash collected, open change orders and backlog. The controller builds it, and the order she builds it in matters more than any formula in the template.

She starts in the field system, because that is where the jobs are. In a ServiceTitan business, last week's revenue there counts every completed job, while QuickBooks Online holds only the invoices somebody batched, posted and exported. A job a technician left open on Friday afternoon is not in the Accounting tab at all. So the first hour goes to deciding which revenue figure is true, and the honest answer is both, taken at different moments.

Then she reconciles. The batch she exported does not exist as a batch on the QuickBooks side, so she ties transactions one at a time by number, date and amount. Returns had to be keyed into QuickBooks by hand, so they show on one side and not the other until someone enters them. Anything that failed to export waits in the Pending Export Report until a person opens it.

On the construction side, the project managers' figures live in Procore. A prime contract change order approved on Thursday is already on the Procore budget, but Sage 300 CRE does not have it until it syncs and posts, and Sage folds it into one Approved Estimate Changes column beside the budget changes. A supplier bill entered in Sage Payables on Friday is in the books and still absent from Procore job cost until it is posted in Job Cost. If an owner invoice released retainage, Sage never received the release, and someone repeats it in Sage Receivables.

Last come the facts no system holds. Two superintendents get a text asking which jobs went sideways this week. A project manager is asked whether the change orders he mentioned are signed yet. Those answers go into the template by hand, along with a note explaining every difference she could not close.

Other businesses build the same page from different systems. A restaurant group combines point-of-sale sales, time clock labor and a stack of vendor invoices for each location. An online brand pastes storefront orders, marketplace payouts and ad spend side by side. A property manager pulls rent, vacancies and work orders building by building. The systems change; the Monday morning does not.

None of these steps is a mistake. Each one follows a rule for how one system hands data to another. The report is built by hand because a person is the only place all those rules meet, and she applies them from memory every week. When she is out, the report waits, or it goes out with numbers nobody can explain.

What the owner is actually reading

The finished page mixes cutoffs. Revenue can be as of the last export, cost as of the last posting, and change orders as of a phone call. The owner reads it as a single moment. That is why his first question is so often one the page cannot answer: the figures were never taken at the same time. A report that prints the cutoff beside each number is already more useful than a cleaner one that hides it.

Signs you have this problem

  • Someone spends most of a morning every week copying numbers into the owner's template
  • Revenue on the owner's page and revenue in the accounting system differ, and the gap changes every week
  • Contract value, sales or cost in one system and in the books disagree for the same period
  • Only one person knows how to build the report, and it waits when she is out
  • The owner's first follow-up question is one the page cannot answer without more digging

What usually causes it

  • Numbers are exported from each system and retyped into one template, along with the transactions that never crossed on their ownThe re-entry trap
  • Exports that failed, work left open and changes waiting to sync sit in queues nobody checks before the report is builtThe invisible queue
  • Problems and unsigned changes the owner cares about never reach a system, so they arrive by text and phone callThe field-to-office split
  • Accounting, operations and each location or department send their piece on their own schedule, and the report waits for the slowestThe handoff gap

Find your cause

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

  1. Does the person building the report spend the first hour fixing exports or hunting for transactions?If yes: data is failing to cross between systems before the build even starts. Make the export check the first step and count what it finds.
  2. Does revenue on the report differ from the accounting system by an amount that changes every week?If yes: the two numbers have different cutoffs. Write the cutoff next to the number and list completed but unexported work on its own line.
  3. Does gross margin look wrong to the owner on work he knows well?If yes: check the costing setup before blaming the people doing the work: income account mapping on price list items, staff missing from payroll at completion, and purchase order items on the invoice.
  4. Does one system's contract value, sales or cost differ from the books for the same period?If yes: look for changes approved but not yet synced and posted, and for costs posted in one module but not the one the report reads.
  5. Does the report wait, or go out unexplained, when its usual builder is out?If yes: the rules for combining the systems live in one person. Write the build down and have someone else run it once.

How it breaks in each industry

HVAC, plumbing and electrical service
Revenue on the owner's page depends on which completed jobs were batched and exported, not on which jobs the crews finished. Gross margin by job depends on setup the owner never sees: whether every pricebook item is mapped to an income account and whether each technician was in payroll when the job closed.
Commercial contractors on Procore and Sage 300 CRE
The project manager reports contract value and cost from Procore, and the controller reports from Sage. An approved change order lands in Procore first, a supplier bill lands in Sage first, and retainage released on an owner invoice never crosses at all, so the two halves of the report describe different moments.
Restaurants and hospitality
The weekly numbers come from three places: sales from the point-of-sale system, labor from the scheduling or time clock system, and food and beverage cost from vendor invoices. Each location closes its week on its own, and someone combines them into one page by location.
E-commerce and consumer brands
Sales come from each storefront and marketplace, payouts from the processors, ad spend from each ad platform and stock from the inventory system or a fulfillment partner. None of them shares a cutoff, so the weekly page is several exports pasted side by side.

Where it breaks between systems

ServiceTitan and QuickBooks Online (batches)
ServiceTitan groups exported transactions into batches, but batch numbers and names are not sent to QuickBooks Online. Whoever ties last week's export to the books searches QuickBooks for the individual transactions, one at a time.[1]
ServiceTitan accounting tab (open jobs)
An invoice shows up in the Accounting tab only after its job is completed, so a job a technician leaves open keeps its revenue out of every batch. ServiceTitan's advice is to batch, post and export every day.[2]
ServiceTitan and QuickBooks Online (returns and transfers)
Inventory returns and transfers do not export to QuickBooks Online and have to be created there by hand. With Payables enabled, the vendor credit can export. Each hand entry is a line that exists on one side until someone keys it.[3]
ServiceTitan export errors
Invoices or payments that fail to reach QuickBooks Online are listed in the Pending Export Report under Reports, Legacy Reports. A report built without opening it treats a failed export as revenue that never happened.[4]
ServiceTitan job costing report
ServiceTitan lists three causes of a job costing report showing the wrong numbers: a pricebook item not mapped to an income account (revenue reads low), purchase order items double counted against the invoice, and a technician who was not in payroll when the job completed (labor burden missing). The page covers the legacy job costing model.[5]
Procore and Sage 300 CRE (contract value)
An approved prime contract change order shows on the Procore budget at once but reaches Sage only after it syncs and posts. Sage combines budget changes and change orders in one Approved Estimate Changes column where Procore shows two, and estimate changes keyed directly in Sage do not sync back to Procore.[6]
Procore and Sage 300 CRE (job cost)
Costs reach Procore only after they are fully posted in Sage Job Cost. A supplier bill or payroll run posted only in Accounts Payable or Payroll is in the books and still missing from the project manager's cost view.[7]
Procore and Sage 300 CRE (owner billing)
Owner invoices export only to Sage Quickbill contracts set up for lump-sum billing, and only from an approved or pending-owner-approval status. Work completed and retainage held are sent, but the Retainage Released this Period field is ignored, so releasing retainage is done again in Sage Accounts Receivable.[8]
Jobber and QuickBooks Online
The current QuickBooks integration runs one way, from Jobber to QuickBooks, and Jobber's help center says Paid status no longer syncs back from QuickBooks. A payment recorded in QuickBooks leaves the Jobber invoice looking unpaid.[9]
Housecall Pro and QuickBooks Online
New customers, invoices, payments and newly used price book items cross into QuickBooks Online. Estimates never do, and an invoice deleted or canceled in Housecall Pro has to be deleted or canceled in QuickBooks by hand, so pipeline and canceled work disagree between the two.[10]

By the numbers

No industry association or government survey publishes a figure for this. The measurement below gives you your own.

Measure it in your own shop

From: Your last four owner reports, the exports and spreadsheets they were built from, and the current figures for the same periods in your operating systems and your accounting system.

  1. For each of the last four reports, write down how long the build took and the date and time each source was exported.
  2. Pick the three to five headline figures, such as revenue, gross margin, cash collected and backlog. Compare each to what the source system shows today for the same period.
  3. Match operating records to accounting records on transaction number, date and amount, not on batch or summary total, since ServiceTitan batches, for one, do not reach QuickBooks.
  4. Tag each difference you choose to chase: not yet exported, failed export, keyed by hand, different definition, or typing error.

Reading it: The build hours are the running cost. The tags show where the hours go. Mostly timing means the fix is cutoffs. Mostly failed or hand-keyed transactions means the gap sits between systems. Mostly definitions means a one-page glossary will settle most of the arguments.

What does not fix it

A dashboard on top of the systems
It reads the same exports the spreadsheet did. Returns keyed only in QuickBooks, retainage released only in Sage and work left open in the operating system are still missing, now on a nicer screen.
Another administrator
More hands do not make returns export or make changes keyed in one system flow back to the other. They spread the same matching work across two people who then disagree about the method.
A bigger template
More tabs and formulas make the build harder to hand over and easier to break, and they tend to bury the reconciling line the owner most needs to see.

What to try this week

  1. Time the next build, step by stepHave the person who builds the report log each step and its minutes for one full cycle: every export, every lookup, every text to a manager. The log is the baseline for everything else.
  2. Cut the page to what the owner acts onSit with the owner and mark each number he has used to make a decision in the last quarter. Drop or move to an appendix every number nobody acts on.
  3. Give every number a cutoff and a homeNext to each remaining figure, write which system it comes from and in which status. For example: revenue means invoices exported to QuickBooks through Sunday night, with completed but unexported work listed on its own line.
  4. Clear the export queues before you buildMake the first step of the build a check of what failed to cross. In a ServiceTitan and QuickBooks Online business that is the Pending Export Report. In a Procore and Sage 300 CRE business it is the unposted budget batches and the posting journals for rejected entries. Every sync between systems has an equivalent.
  5. Show the difference as its own lineWhen the operating system and the books disagree, put the difference on the page with its reason instead of forcing a match. A labelled reconciling line is something the owner can question. A silent adjustment is not.
  6. Write the build down for a second personTurn the timed log into a numbered checklist with the menu paths, the cutoffs and the known hand entries. Have someone else build one report from it while the usual builder watches.

Where do-it-yourself stops

These steps make the report shorter, honest about its cutoffs and buildable by a second person. They do not change what crosses between your operating, project and accounting systems, so someone still matches transactions, keys the ones that never cross, and chases managers for what no system holds. The lasting fix is a tool built around the systems you already run, so the owner's numbers arrive with their cutoffs in the right shape without anyone retyping them. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Why don't our ServiceTitan numbers match QuickBooks Online?

Usually timing and hand entries. An invoice reaches the Accounting tab only once its job is completed, it reaches QuickBooks only once a batch is posted and exported, and returns and transfers have to be keyed in QuickBooks by hand. The batch itself does not travel, so the match is done transaction by transaction.

Why does contract value in Procore differ from Sage 300 CRE?

An approved change order shows in Procore immediately and in Sage only after it syncs and posts. Sage also puts budget changes and change orders in one column where Procore shows them separately, so the lines will not tie one for one even when the totals do.

Will a reporting tool or dashboard fix it?

Only if the numbers underneath share a cutoff and every transaction actually crossed. A dashboard over failed exports and hand-keyed corrections is quicker to read and just as wrong.

How many numbers should the owner report carry?

Only the ones the owner has acted on recently, each with its source and its cutoff written next to it. Most owner reports shrink by half once that question is asked line by line.

Who should own the owner report?

Whoever owns the cutoffs, usually the controller. The managers who run the work own getting their records closed and posted before the cutoff, which is where most of the build time is really lost.

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.