The money you earned but haven't been paid
Every field-service operation carries a pile of money it has already earned and not yet collected — work done, parts installed, invoices sent, and nothing in the bank for it. A little of that is normal: invoices in flight, customers who pay on a cycle. But the pile has an age to it, and the older it gets, the worse it pays. An invoice that's a week old almost always lands. One that's ninety days old is a coin flip, and one that crosses into a year is mostly a write-off with a date on it. Aged receivables are the slow leak at the bottom of the boat — not dramatic, easy to ignore, and capable of sinking the cash flow of a profitable shop that's simply bad at collecting.
The trap is treating receivables as a single number on a statement instead of a set of buckets with very different odds. "We're owed forty grand" tells you nothing actionable. "Eight grand is current, twelve is 30 days, fifteen is 60-plus, and five is past 90" tells you exactly where the money is rotting and which dollars to chase first. The job is twofold: stop invoices from aging in the first place, and work the ones that already have before they age out of recoverable entirely.
Stop the bleed before it starts
The cheapest receivable to recover is the one that never ages, and most of that battle is won at the door, not in the back office. The same disciplines that get you paid at the door are your first and best defense against an aging pile — every dollar collected while the tech is on-site is a dollar that never enters a 30-day bucket. For the work that genuinely has to be invoiced — larger commercial jobs, accounts on terms — the goal is to send a clean, fast, undisputable invoice so the customer has no reason to sit on it.
That starts with the invoice being right and immediate. When a job converts to an invoice in one click the moment work is complete — labor, parts, and expenses already itemized as line items — the bill goes out while the work is fresh, not days later when the customer has half-forgotten the visit. In Hosting Field, a finished job flows straight into Hosting Books as a real, sendable invoice with the line items intact, so there's no transcription lag and no "we'll bill you later" gap where the job goes cold. An invoice that arrives the same day, itemized and matching what the customer saw happen, is an invoice that gets paid on time far more often than one that shows up two weeks later with vague line items.
Two more habits keep invoices out of the aging pile entirely:
- Take a deposit on the big ones. For larger jobs, collecting a deposit up front means part of the money is already in hand before the work starts — and a customer who's paid a deposit is far more likely to settle the balance promptly. Deposits shrink the amount that can ever age.
- Make the work undisputable. A surprising share of aged receivables are really disputes in disguise — a customer who isn't paying because they question the bill. An on-site sign-off captured as proof of completion, and photo evidence of the finished work, take "I'm not sure I approved that" off the table. The fewer disputes, the fewer invoices that stall.
Read the aging buckets like a clock
Once an invoice has aged, recovery is a game of odds and timing, and the aging report is your map. Sort what you're owed into buckets — current, 1–30, 31–60, 61–90, and 90-plus — because each bucket pays at a different rate and demands a different touch. The point isn't to chase everything equally; it's to put your effort where it still moves money.
- Current and 1–30: a friendly reminder is usually all it takes. Most of this pays itself with a single nudge — a statement, a "just a heads-up your invoice is due" note. Don't over-rotate here; these are mostly fine.
- 31–60: this is where attention pays off most. The invoice is late enough to need a real follow-up but recent enough that the customer remembers the job and the relationship is intact. A direct, polite call here recovers far more than the same call made at 90 days. Working the 60-day bucket hard is the single highest-leverage collection habit.
- 61–90: the tone firms up. A clear statement of what's owed, for which job, with the proof attached, and a specific ask for payment by a date. This is your last comfortable window.
- 90-plus: odds drop sharply. Decide deliberately whether each one is worth continued effort, a payment plan, or a write-off. Throwing equal energy at a 120-day invoice as a 40-day one is how shops let recoverable money slip while burning hours on money that's gone.
The discipline is to work the buckets on a schedule — a weekly pass through the aging report — rather than reacting only when cash gets tight. Receivables you touch weekly age far slower than receivables you remember when the bank balance scares you.
Where Hosting Field ends and your books begin
Be honest about the boundary, because it matters for how you set this up. Hosting Field's job is to make the invoice clean, fast, and undisputable — the one-click job-to-invoice flow, the deposits, the sign-off proof, and the itemized line items that prevent disputes. The aging report itself, the buckets, the statements, and the dunning live in Hosting Books, where the invoice lands — that's the accounting layer, and that's where you read who owes what and how old it is. Hosting Field is not an accounts-receivable or collections system, and it doesn't pretend to be a debt-collection tool.
What that means practically: you prevent aging in the field with good capture and fast, clean invoicing, and you work the aging in your books with a weekly pass through the receivables report. The two halves connect because the invoice carries the job's full context — the line items, the completion proof — so when you do make a 60-day collection call, you have the evidence at hand instead of reconstructing what the job even was.
Don't torch the relationship to collect the dollar
A real caution: aggressive collection on a current customer can cost you more than the invoice is worth. The customer sitting at 45 days might be your best repeat account having one slow month — and a heavy-handed dunning sequence can turn a loyal customer into a former one. Match the firmness to the age and the relationship. A long-standing account gets a call and a conversation; a one-time customer who's gone dark at 90 days gets a firmer, more formal track.
The other discipline is to separate "won't pay" from "can't pay right now." A customer who's struggling but wants to settle is often best served by a payment plan that gets you most of the money over time — far better than a write-off and a lost customer. Save the hard line for genuine non-payment, not for cash-flow timing on an otherwise good account.
What to measure
- Days Sales Outstanding (DSO) — the average age of your receivables. The single best gauge of how fast you turn finished work into cash. Falling DSO means your at-the-door and fast-invoice habits are working.
- Percentage of receivables past 60 days — the share of what you're owed sitting in the dangerous buckets. This is where money goes to die; watch it more than the headline total.
- Collection rate by bucket — what share of each aging band you actually recover. If your 30-day recovery is strong but 60-plus falls off a cliff, your follow-up is starting too late — push the effort earlier.
The work you've already done is the work you most deserve to be paid for. Stop invoices from aging by collecting at the door and sending clean bills the same day, work the buckets that are still recoverable on a weekly schedule, and read the difference between a slow month and a real non-payment before you decide how hard to push. The receivables pile never goes to zero — but a shop that works it deliberately keeps the leak small enough to stay afloat, instead of slowly drowning in money it earned and never collected.