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

Problem guide

The cash forecast is a guess

A cash forecast becomes a guess when its inputs run on different clocks. Finished work is not an invoice until someone closes it and sends it to accounting, payment terms set in one system do not always carry into the next, and a card payment marked paid in an app reaches the bank days later. ServiceTitan, for example, does not send the invoice's payment term to QuickBooks Online. Forecast each input by the date it really turns into cash, refresh it weekly, and check last week's forecast against the bank.

Tangled cables and an old desktop tower under an office desk

How it actually happens

The owner asks a simple question on a Tuesday: can we buy the new vehicle this month, or will cash be tight? The controller opens last month's forecast spreadsheet and starts again.

Receivables and payables come out of QuickBooks or Sage first. That part looks solid, but it only holds what has already crossed into accounting. In a typical service company running ServiceTitan, a job reaches the Accounting tab only when the technician or dispatcher marks it complete, and the invoice reaches QuickBooks only when someone posts and exports the batch. Two dozen jobs finished last week may still be open on the board, and nothing about them is in the receivables total the controller just pasted. A law firm has the same pile as unbilled time on open matters. A clinic has it as visits not yet coded and submitted.

Then the due dates. The customer agreed to net 30, but ServiceTitan does not carry the payment term across to QuickBooks Online, so the exported invoice carries whatever term QuickBooks prefers. An invoice with no term at all has no due date and drops out of the aging buckets. The controller's week-by-week cash-in column is built on dates nobody chose.

Payroll goes in from memory, adjusted for overtime she heard about. For the largest customers she calls the managers. One expects to bill next week, if the customer signs off on the change. Another quotes a number that includes retainage, which will not come back until the job is accepted. A third cannot say, because the field has not sent quantities.

Cash in from the field or the storefront is the last trap. A customer paid by card on Friday and the app shows the invoice paid. The money is in a payout that clears days later, bundled with other payments, so no single deposit matches it. A bookkeeper on r/Bookkeeping described a ServiceTitan client with about $20,000 on the ServiceTitan deposit report that never reached the bank, and about $50,000 that reached the bank but was missing from the report. That is one poster's account, but it shows the mechanism: the operating system's paid and the bank's received are different events. Marketplace and delivery app payouts work the same way, net of fees and refunds.

The forecast she sends says cash is fine. It is built from real numbers, each taken at a different point in its life. Three weeks later the company draws on the credit line to make payroll, and nobody can say which line was wrong, because nobody scored last month's forecast against the bank.

Four clocks, one spreadsheet

Every cash line has a clock: when the work finished, when it was invoiced, when it was due, and when the money cleared. Accounting software sees the middle two. The operating system, whether a field app, a practice system or a store, sees the first. Only the bank sees the last. A forecast that names those four dates for its biggest items, instead of one, stops being a guess and becomes something you can check.

Signs you have this problem

  • The forecast is rebuilt from scratch whenever the owner asks about a big purchase
  • Cash surprises trace back to work that was finished but not yet invoiced
  • Due dates in the accounting system do not match the terms the customer agreed to
  • A payment an app shows as paid is not in the bank when the forecast expected it
  • Nobody compares last month's forecast with what actually came in and went out

What usually causes it

  • Finished work that is not closed, invoiced or sent to accounting sits in a pile the forecast cannot seeThe invisible queue
  • Receivables, payables, payroll and work status are copied from separate systems into one spreadsheetThe re-entry trap
  • Expected billing dates come from managers by phone, from memoryThe field-to-office split
  • Change orders, commitments and large bills wait for an accounting approver before they reach the booksApproval drag

Find your cause

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

  1. Is cash in on the forecast built only from invoices already in accounting?If yes: finished but unbilled work is missing. Add the line for completed work not yet invoiced.
  2. Do due dates in the accounting system differ from the terms on your quotes, contracts or engagement letters?If yes: the payment term is being set by the accounting system, not by you. Check the term on invoices as they arrive there.
  3. Do card, marketplace or bank payments show up as cash on the day an app marked them paid?If yes: the forecast is early by the payout lag. Forecast deposits instead.
  4. Are known commitments, change orders or large bills missing from the books the forecast reads?If yes: they may be waiting for an accounting approver. Check the approval queue before each refresh.
  5. Does anyone compare last week's forecast with the bank?If yes: good. If not, that comparison is the first habit to start; without it nobody knows which line misses.

How it breaks in each industry

HVAC, plumbing and electrical service
Cash comes from hundreds of small invoices, many paid by card in the field. The forecast depends on how fast jobs are closed and exported, and on the payout lag between a card payment and the deposit.
Commercial subcontractors on progress billing
Cash comes from monthly pay applications, less retainage, on the owner's payment cycle. A late or rejected pay application moves a large inflow by a month, and retainage returns only at completion or acceptance.
Law firms and accounting firms
Time worked becomes cash only after it is reviewed, billed and paid, and retainers sit in trust until they are earned. Unbilled time on open matters or engagements is the biggest line the accounting system cannot see, and the date it gets billed depends on a partner's review.
E-commerce and consumer brands
Orders show as paid in the store the moment they are placed, but the money arrives in marketplace and processor payouts on their own schedules, net of fees, refunds and reserves. Purchase orders for inventory go out months before the sales that pay for them.

Where it breaks between systems

ServiceTitan (job status to accounting)
An invoice is visible in the Accounting tab only once its job is completed, and a person posts and exports each batch. If a batch partly exports, ServiceTitan's advice is to unpost it, post it again and re-export. Zero-dollar invoices inside projects never show in the Unbatched list.[1]
ServiceTitan invoice review
An invoice with no pricebook tasks, equipment or chargeable materials will not export, and an invoice cannot be edited once it has been exported. Each one that stalls is receivable cash the accounting side never sees.[2]
ServiceTitan and QuickBooks Online (due dates)
ServiceTitan does not export the invoice's payment term to QuickBooks Online, so QuickBooks applies its own preferred term and the due date shifts. The shift shows across the whole batch, not on one invoice.[3]
ServiceTitan AR Management
The collections screen pulls only posted invoices. An invoice still pending shows on the customer's profile but not where the collections team works.[4]
ServiceTitan aging
An invoice with no payment term has no due date and is left out of the aging bucket columns entirely, so the aging report understates what is coming due.[5]
QuickBooks Online Cash Flow Planner
Intuit's help article says the planner projects cash from your QuickBooks data, such as future invoices, bills and expenses, plus connected bank accounts, and that items added in the planner do not touch the books. Work not yet exported from the field system is outside its view.[6]
Jobber Payments
Jobber's help center describes card payouts on a two-business-day schedule once the authorization period ends, bank payments on a typical four-business-day schedule, and banks taking a day or two more to post. Payouts arrive bundled, so one deposit rarely equals one invoice.[7]
Procore and Sage 300 CRE (approvals)
Budgets, commitments, commitment change orders and prime contract change orders have no on-demand sync. By default they go to the ERP Integrations tool for an accounting approver to accept or reject before reaching Sage; Direct Export can remove that step.[8]
Procore Pay and Sage 300 CRE
Procore Pay is how a general contractor pays its subcontractors. For partial payments, the payment amount does not sync to Sage 300 CRE, so cash already out of the bank is not reflected there until someone enters it.[9]

By the numbers

FigureWhat it measures
27%[10]Specialty contractors who said they are typically paid within 30 days of invoicing completed work. Dodge Data and Analytics survey of 537 specialty contractors in the US, Canada, the UK and Australia and New Zealand, sponsored by Procore (2022); a four-region average, self-reported.
29%[10]Specialty contractors in the same Dodge survey who said their typical wait for payment exceeds 60 days.
2 and 4 business days[7]Published Jobber Payments payout schedules in the US and Canada: card payouts after the authorization period, and typical bank (ACH) payments. Vendor documentation; banks may add a day or two to post.

Rules that apply

48 CFR 52.232-27(a)(1)(i)(A), federal progress payment due date[12]
On federal construction, a progress payment is due 14 days after the designated billing office receives a proper payment request, unless the contract sets a longer period. That is the one inflow on a contractor's forecast with a due date fixed by regulation.
48 CFR 52.232-27(a)(2), improper invoices[12]
A defective payment request is returned within 7 days with the reasons. The due date runs only from a proper request, so a returned pay application pushes the inflow later on the forecast.
48 CFR 32.103 and 52.232-5(e), federal retainage[13]
On federal fixed-price construction, the contracting officer may retain up to 10 percent of a payment only when progress is unsatisfactory, and retained amounts are paid promptly once the contract requirements are complete. A federal ceiling, not a private or state rate.
48 CFR 52.232-27(c)(1), paying subcontractors[12]
On federal construction, the prime pays subcontractors for satisfactory performance within 7 days of receiving payment from the agency. For a general contractor, every federal inflow on the forecast carries a matching outflow a week behind it.

Measure it in your own shop

From: Your last eight weekly forecasts (or the spreadsheets they came from), bank statements for the same weeks, payout reports from your payment processor, and a list of completed jobs with their invoice and export dates.

  1. For each of the last eight weeks, put forecast cash in and cash out next to the actual deposits and withdrawals.
  2. For each week's miss, name the items that caused it: finished work not yet invoiced, invoices due earlier or later than forecast, payouts that cleared later, and bills nobody expected.
  3. Total today's completed jobs that are not yet invoiced or not yet exported.
  4. Take 20 recent invoices and compare the due date in accounting with the term the customer agreed to.

Reading it: The category behind the most missed dollars is where to start. The unbilled total is cash your forecast cannot see at all. If due dates disagree on most of the 20 invoices, your aging report and any forecast built from it are wrong by the same amount.

What does not fix it

The forecasting tool in your accounting software
It projects from what is already in the books. Jobs finished in the field but not exported, and invoices due on the wrong date, go in wrong or not at all.
Forecasting from the bank balance
The balance does not show bills already committed, payouts still in transit, or partial payments to subcontractors that were never entered in accounting.
Asking project managers harder for billing dates
Their answer is still memory, given by phone. The dates you need already exist as job statuses and export dates; read them instead.
A longer horizon
Forecasting further out on inputs that are wrong next week only spreads the error. Get four weeks right before forecasting thirteen.

What to try this week

  1. Write down each input and its clockList every line of the forecast with the system it comes from and the status that counts: work completed, invoice sent to accounting, payment received, deposit cleared. The gaps between those statuses are where the forecast goes wrong.
  2. Add a line for finished, unbilled workEvery week, total the jobs, orders, matters or visits that are complete but not yet invoiced, each with the date you expect to bill it. This is usually the largest number missing from an accounting-based forecast.
  3. Fix due dates where they are setCheck that the due dates in your accounting system match your real terms, and make sure every invoice carries a payment term so it lands in the right aging bucket. If you invoice from ServiceTitan into QuickBooks Online, this check is required, because the term does not travel.
  4. Forecast deposits, not paymentsPut card, bank, marketplace and delivery app payments in the week they will clear, using the processor's published payout schedule, not the day an app marked the invoice or order paid.
  5. Give slow, rule-driven receipts their own linesRetainage, federal progress payments, insurance claims and any receipt with its own schedule belong on separate lines. Do not average them into general receivables.
  6. Score every forecast against the bankEach week, put last week's forecast beside actual deposits and payments, and write one line on the biggest miss. A forecast nobody scores never improves.

Where do-it-yourself stops

These steps make the forecast regular, honest about timing, and scored against the bank. They do not remove the copying of work status, invoices, bills and payroll from separate systems into one sheet, or the blind spot of finished work that has not reached accounting. The lasting fix is a tool built around your operating system, your accounting system and your bank, so the forecast reads each input at the moment it changes. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

Why is our cash forecast always wrong?

Usually because each input runs on its own clock. Work is finished before it is invoiced, invoiced before it is exported, due on a date the accounting system chose, and paid days before the money clears. A forecast that ignores those lags is early on cash in.

Can QuickBooks Online forecast our cash on its own?

Its Cash Flow Planner projects from what is already in QuickBooks plus connected bank accounts. Work your field system has not exported yet is not in QuickBooks, so the planner cannot see it.

When does a card payment become cash we can count?

When it clears your bank. Jobber, for example, describes card payouts on a two-business-day schedule after authorization, bank payments typically on four, and deposits bundled across several payments.

How should we forecast federal progress payments?

From the date the billing office receives a proper payment request: payment is due 14 days later unless the contract says longer. A request returned as defective starts over once corrected, so plan for that risk on new contracts.

How do we know if the forecast is getting better?

Score each week's forecast against the bank and track the size of the miss. If the miss shrinks over two or three months, the changes are working.

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.