AR & collections
Construction AR software: know who to chase today
Every open invoice ranked by dollars at risk, a reminder ladder that escalates and ends, one statement per builder rather than per invoice, and promises to pay that pause the chase on their own.
A finite reminder ladder drops your oldest debt off the list
The classic failure of a reminder system is that once the last rung has gone out, the invoice disappears from the worklist entirely, so the oldest, largest balances in the book become the only ones nobody is reminded about, and the screen reads as an empty morning.
The second failure is ranking by age. A $400 invoice ninety days out and a $90,000 invoice forty days out are not the same problem, and a morning spent on the first one collects nothing.
What you get
What it does
Four lanes, not one queue
Call, email, hold, wait. Anything where email has had a fair run is ranked above everything else, because that is the money most at risk.
Ranked by dollars at risk
Balance multiplied by days late, with the fewest invoices that make up eighty percent of the debt named. If you can make four calls today, those are the four.
Promises pause the ladder
"We will pay on the fifteenth" is recorded against the job and the reminders stop until the date passes. A promise that passes with no money escalates and becomes the strongest signal in the book.
Disputes stop it entirely
With no automatic release, because nothing in software knows when an argument is over.
One email per builder
A statement covering every chaseable invoice for that customer, with one balance to settle. Four separate emails get filed individually; one statement gets one decision.
Your words, your ladder
Edit the wording per tier and the cadence itself. Balances and dates are tokens the document computes, so a copy edit cannot move the money.
How it works
Start to finish
- 1
Invoices become receivables automatically
Dated from the invoice, on the net terms for that trade, the ones actually printed on the document.
- 2
Open the worklist
Worst first. Every row carries the invoice, its age, its days past due, its aging bucket, the balance, and who the reminder goes to by name.
- 3
Send, or call and log it
The rung is claimed before the email is composed, so two people working the list cannot double-chase one customer.
- 4
Record what they said
A promise, a dispute, or a note. The next person to open the row sees the whole conversation with dates.
Nothing sends on its own
There is no unattended dispatcher, and that is a decision rather than a gap: outbound mail resolves the sending mailbox from the person sending it, so an automatic send would be going out under somebody's name while they were not looking. A human reads the email and presses send.
Read the restShow less
Aging and lateness are kept as separate numbers throughout. Days since the invoice went out is how a receivable is reported; days past due is how hard to push. On net 30 those are thirty days apart, and conflating them is how a screen ends up describing an invoice two different ways.
Day counts are computed on your company's calendar in your company's time zone, not on the reader's device. Otherwise the office in Nashville and the owner in California read the same invoice as 31 and 30 days late.
Common questions
- No. Every message is read by a person before it goes. The list tells you what is due to go out; the send is always a decision.
See it on your own jobs.
A 20-minute walkthrough, on your real pipeline. No slide deck, no pressure.