October 8, 2026 · Mitt Patel · 6 min read
Monday morning, three technicians turn in a stack of checks, a wad of cash, and a phone full of card taps from last week. The bank shows one lump deposit for $750. Somewhere in that pile is a customer who still owes you $400, and you have no fast way to find them.
Why this happens
Field service work doesn't pay like a store. A technician finishes a job, the customer hands over a check or taps a card, and that payment doesn't touch your books until someone enters it later, sometimes days later. In the meantime, the bank doesn't deposit payments one at a time. It batches them. A Tuesday card batch might include four jobs. A Friday bank run might include six checks and two cash drops.
When payments get entered late, or entered as a lump sum instead of against specific invoices, two things go wrong. First, invoices sit open even though the customer already paid, so your accounts receivable list is wrong and you might chase someone who doesn't owe you anything. Second, and worse, an invoice that's genuinely unpaid looks identical to one that's paid and just hasn't been recorded yet. Both show up as "open." You can't tell them apart without digging through paper receipts or texting technicians to ask what happened on a job from ten days ago.
The cost shows up in decisions you make without realizing the numbers are off. You think you're owed more than you are, so you feel more cushion than you have. Or you think a customer paid when they didn't, so you never follow up, and that job quietly becomes a loss. Owners who run this way for months can find, at year-end, a handful of invoices that were never actually collected and never actually chased, because nothing in the system flagged them.
A worked example
Say your technician Dave does three jobs on Monday:
- Job A: $150, paid by cash
- Job B: $600, paid by check
- Job C: $400, invoiced, customer says they'll mail a check later
Dave turns in $150 cash and a $600 check at the end of the day. You deposit both at the bank together, so your bank statement shows one deposit of $750.
If you record that deposit as a single lump sum, your books show $750 came in, but you have no link back to Job A or Job B specifically, and Job C still sits open with no obvious reason why. A week later, when the customer's check for Job C actually arrives, it's easy to assume it already got credited, especially if someone glances at the account and sees it showing a balance close to zero after other adjustments.
Instead, if you record Job A's payment and Job B's payment against their invoices the same day Dave turns them in, both invoices close out immediately. Job C stays open, clearly, because nothing has been applied to it. When the $750 deposit hits the bank, you match it to the two payments you already recorded, not to the jobs themselves. The deposit total agrees with your books, and Job C remains visibly unpaid until that check shows up.
How to set it up
- Record payments against the invoice, not as general income. Every cash, check, or card payment a technician collects should be applied directly to the specific invoice it belongs to, the same day it's collected.
- Have technicians report payments daily, not weekly. A simple end-of-day note, a text, a shared form, or an entry into QuickBooks Online from the field, whatever fits how your crew works, as long as it happens that day.
- Use undeposited funds correctly. In QuickBooks Online, payments you've recorded but haven't yet taken to the bank should sit in the undeposited funds account until the actual deposit happens. This keeps your records matching the bank's timing instead of guessing at it.
- When you make a bank deposit, select the exact payments included. Don't enter deposits as a flat dollar amount. Choose the specific invoice payments that make up that deposit, so the deposit total is built from real, already-recorded payments.
- Reconcile the bank account monthly and check that every deposit matches a group of recorded payments. If a deposit amount doesn't match anything in your undeposited funds, that's your signal something wasn't recorded.
- Review open invoices weekly, not just at month-end, so an invoice that's been sitting unpaid for two weeks gets noticed while it's still fresh enough to follow up on.
What undoes it
- Entering deposits as a single lump sum instead of linking them to individual payments. This is the single most common way deposits stop matching invoices.
- Technicians holding onto cash or checks for several days before turning them in, which delays recording and makes it harder to remember which payment belonged to which job.
- Recording a payment as a deposit directly, skipping the invoice entirely. This makes the invoice look unpaid forever, even though money came in.
- Letting one person collect payment info verbally without a paper or digital trail, so by the time it reaches the books, details are fuzzy.
- Assuming a "paid" conversation with a customer means the payment was recorded. A technician saying "they paid me" isn't the same as that payment being applied to the invoice.
Monthly checklist
- Every invoice from the past month shows a payment date that matches when the technician actually collected it, not when it was entered weeks later.
- Every bank deposit has been matched to specific recorded payments, not entered as a round or estimated number.
- The list of open invoices has been reviewed, and anything open longer than two or three weeks has a clear reason why.
- Cash collected in the field has been counted and recorded separately from checks and cards, so each payment type is traceable.
- Undeposited funds account has been checked to confirm nothing is sitting there that should have been deposited weeks ago.
Common questions
What if a technician collects payment but forgets to report it that day?
Record it as soon as you find out, dated for the day it was actually collected if you can confirm that date. The goal is accuracy, not perfection in timing, but the longer the gap, the more likely something gets missed entirely.
Should technicians take partial payments in the field?
That depends on how your business prices and schedules jobs, and it's worth deciding on a clear policy rather than leaving it to each technician's judgment. Whatever you decide, partial payments need to be recorded against the invoice just like full payments, so the remaining balance is visible.
How do I handle a customer who pays by both check and card for the same job?
Record each payment method separately against the same invoice. QuickBooks Online allows multiple payments on one invoice, and keeping them separate makes it easier to match each one to the right bank deposit later, since checks and card batches usually land in your account on different days.
What if I already have months of lump-sum deposits in my books?
That can be untangled, but it takes going back through old deposits and bank statements to separate out what was actually collected on each invoice. It's easier to fix going forward and clean up the backlog gradually than to try to fix everything at once.
North Hudson Bookkeeping sets up this kind of daily payment tracking for plumbing businesses and keeps it current month after month. The first call is free.
