Your Aging Report Is Not a List of Debts

More than five accounts sitting in one restoration company's collections file had no signed estimate or change order behind them.

Those balances were not late. They were unenforceable, and they had been unenforceable since the day the work was done. Everyone in the room had been treating them as a collections problem for months.

What Should a Restoration Accounts Receivable Review Actually Look For?

Which balances are collectible, before anyone decides who to chase. That sounds obvious and it is almost never how the review runs, because an aging report presents every balance as the same kind of thing and sorts them by age rather than by whether they are owed.

A working review sorts into three buckets instead: debts a customer genuinely owes and has not paid; work that is still being earned and was never billable yet; and balances that exist because of a documentation gap, a setup error, or a payment applied to the wrong place. Only the first bucket responds to collections effort.

Run line by line rather than by aging bucket. Buckets hide exactly the accounts that most need a decision, because a balance that was never enforceable ages at the same speed as one that is simply late.

Why Are Some Balances Unenforceable Rather Than Late?

Because the work happened before the paperwork did. In restoration this is structural rather than sloppy: a scope expands mid-job, a customer verbally approves, crews keep moving because the alternative is stopping a job in someone's house, and the signature that turns that work into a debt never gets collected.

At one restoration client of ours, a line-by-line review of the open receivables found more than five accounts in collections with no signed estimate or change order attached. The team stopped billing those accounts entirely rather than continuing to chase them, because a demand letter on an undocumented balance invites a dispute the company would lose.

The practical effect is that a share of what looks like a collections backlog is really a back-office backlog, and it can only be fixed by going back for signatures, not by calling harder.

How Do You Tell a Collections Problem From a Documentation Problem?

Ask one question per account: if this customer refused to pay tomorrow, what document would we hold up? If the answer is a signed estimate, a signed change order, or an approved scope, it is a collections problem. If the answer is an internal note, it is a documentation problem wearing a collections problem's clothes.

The same review at that client surfaced a disputed balance where the customer acknowledged owing roughly ten to eleven thousand dollars against an invoice near twenty thousand. The decision was not to argue the full amount. It was to collect the undisputed portion immediately and treat the remainder as a separate, documented negotiation.

That split is worth copying. Arguing about the whole balance delays the part nobody disputes, and the undisputed part is usually the majority of the money.

What Does an Escalation Ladder Look Like in Practice?

It looks like a rule with dates attached, applied the same way to every account, so nobody decides case by case how hard to push. Inconsistency is what makes collections feel confrontational, because the customer who gets chased notices that others were not.

At the same client the standard landed at three documented contact attempts inside fourteen calendar days, then a written notice. Preparation for lien filing starts immediately rather than waiting out the notice period, which matters because lien rights expire. In one account on that same list they already had: the customer had gone unresponsive since midsummer and the filing window had closed while the team was still sending messages.

The ladder is not about aggression. It is about making sure the clock the law gives you does not run out while a polite process is still going.

Why Do Carrier and Program Accounts Behave Differently?

Because their payment timing is a property of their process, not of your effort, and no amount of follow-up moves it. Treating them like ordinary customers produces wasted calls and a forecast that is wrong every month.

In the same weekly review, roughly a hundred and sixty-two thousand dollars sat in promise-to-pay status, concentrated in the past-thirty bucket, against nearly nine hundred thousand in the zero-to-thirty bucket. One account had received about ten voicemails with no response since late July despite the insurer having already released funds. A separate program account had prepaid across two claims and then sat on hold for three months, which looks like a receivable problem and is actually a scheduling one. At a second restoration client, jobs were routinely waiting on insurance, supplements, change orders, or adjuster contact rather than on the customer.

Segment these out and forecast them on their observed cycle. Then stop counting follow-up calls on them as collections work.

What Should You Stop Doing in Collections?

Stop running the aging report as a status meeting. If the same names are read aloud every week with no owner and no date attached, the meeting is documenting the problem rather than reducing it.

Stop chasing balances that are not yet billable. Work still being earned appears on the report, gets counted in the total, and pulls attention away from money that is actually owed. Separating it out usually shrinks the apparent problem by more than anyone expects. Our page on restoration-specific CFO work covers how that review runs as an ongoing rhythm.

Stop settling balances verbally. A write-down agreed on a phone call and never documented leaves two different numbers live in the business — the one the customer believes and the one still sitting on the report. At the client above, settlements were routed through a completed credit-memo form before anything came off the balance, which sounds bureaucratic and is the only thing that makes a settled account actually settled.

And stop letting late fees exist only on paper. A fee printed on every invoice and charged almost never is not a deterrent; it is a thing customers learn to ignore, and reinstating it later reads as retaliation rather than policy.

Where Does Backbone CFO Start on Receivables?

With a single line-by-line pass that assigns every open balance to one of the three buckets and puts a name and a date on each one in the first bucket. That pass is unglamorous and it is the whole job in the first month.

If an agency does eventually make sense, treat it as a vendor decision rather than a relief valve: a signed contract, a confidentiality agreement, and a secure method of transferring customer data. At the client above that review was deliberately deferred until those three were settled, because handing over a customer list is a data decision before it is a collections one.

What usually comes out of it is that the collectible number is smaller than the report says and the documentation gap is larger than anyone believed. Both of those are better to know. A smaller, real receivable balance you can actually pursue beats a larger one that includes money nobody was ever going to send.

We also look at the meeting itself. At that client the weekly format was rebuilt into a short backlog pass of twenty to thirty minutes followed by account-specific operating issues, rather than one long meeting that covered both badly. Separating the two matters because the operating problems behind a stuck balance — an unsigned document, an incomplete scope, a job that never got inspected — are solved by different people than the ones making collection calls.

We do not start by recommending a collections agency. That decision is downstream of knowing which balances are enforceable, and handing an agency a file full of undocumented work damages relationships for no return.