Who owes you money, and for how long
The balances report lists every customer who still owes you, ages each unpaid job from the day the work was finished rather than from any invoice date, and sorts it into 0–30, 31–60, 61–90 and over-90-day buckets so the oldest money is the first thing you see.
Two visits a year and a few hundred customers means the gap between finishing work and being paid for it is measured in weeks, not days. Most of it comes in on its own. The balances report is for the part that does not.
What it shows
Every customer with money outstanding, most owed first, with each unpaid job underneath and how many days old it is. Four buckets across the top: 0–30, 31–60, 61–90, and over 90 days.
Age runs from the day the work was finished. There are no invoices in LakeOps and therefore no invoice dates, so the clock starts the day the crew finished — which is also the day the customer got their email. Nothing else would be honest.
What counts as owed
A completed job with a price on it, minus what has been paid against it net of refunds, plus any late fee. Three things deliberately do not count:
- An open job. That is work, not debt — it has no price until it closes.
- A canceled job.
- A job priced at zero: a warranty return, a goodwill call.
A job that finished but could not be priced does not count either, and is worth knowing about: if a service is marked taxable and the property's postal code is not covered by a tax group, the job closes without a price rather than guessing. See sales tax.
There is no date window, on purpose
Every other report asks "what happened between these dates". This one asks "what is still out there", and a window would hide the oldest debt — which is the only debt anybody opens an aging report to find.
It works whichever way you bill
A shop that takes payments through LakeOps and a shop that posts its own bills and banks its own cheques both get the same report. If anything the second needs it more: recording a cheque by hand is what keeps this accurate, and there is no bank feed doing it for you.
From here you can send somebody a statement, or let LakeOps do it on a schedule.
Still stuck? Ask us — or go back to the help center.