The money that's already yours, finally visible

Most owners carry a running list somewhere — a notebook, a Numbers file, a memory — of the jobs that are done but not paid. It's rarely current. The customer who was going to "mail the check this week" three weeks ago. The invoice that was sent but never opened. The repeat client whose balance quietly grew across four visits.

The work shipped. The revenue is real. It's just sitting in someone else's bank account, and the only record of it is a spreadsheet you keep meaning to update.

The Receivables surface is that spreadsheet, kept current for you. Every completed job with an open balance, in one table, refreshed the moment a payment lands.

Each row shows the job's total value, amount paid, and remaining balance — derived live by joining the job to its invoices and summing the payment ledger. Nobody keys in "amount due" and nobody lets it drift; it's always the truth as of this second.

Alongside it: how they paid (card, check, cash), whether the invoice was sent, the site location, the contact, and when the last reminder went out.

Then group it the way you think about it — by client, by aging bucket (0–30 / 31–60 / 61–90 / 90+), by service area, by "never paid a cent," or by tax year — and every group carries its own subtotals and a payment-method rollup. Export the filtered view to CSV for your accountant in one click.

Turn on an escalating reminder ladder and Business Dash works the list for you: a gentle nudge a few days after due, a firmer one at two weeks, a final notice at thirty. Each send is logged against the job, so the "Last Reminder Sent" column is always honest and you never accidentally dun the same customer twice in a day.

Every reminder — automated or the ones you send by hand — lands in one collection timeline on the job, so anyone who picks up the account sees the whole history of the conversation.

A customer owes you for the last job and calls to book the next one. Business Dash catches it at the moment the new work is created and tells you — notify, warn, or hard-block, your choice per org. And because "always block" is a great way to lose a good customer over a billing mix-up, a manager can override on the spot, with the override logged.

When a balance is genuinely never coming — insurance loss, bad-debt tax write-off, sold to collections, or forgiven — record it once and it drops off receivables into a bad-debt report grouped by tax year, ready for your accountant.