You did the work three weeks ago. The invoice went out the same day. And every Friday since, you have spent twenty minutes deciding whether to text the customer again or let it ride another week. That is not a collections problem — it is a design problem. Businesses that get paid on time did not find more honest customers. They built a system — a deposit, a card on file, and a way to send automatic payment reminders to customers — where paying late takes effort and paying on time is the default.
Late payment is a system problem, not a customer problem
A late invoice usually is not someone refusing to pay. It is an invoice sitting in an inbox behind forty other emails, waiting for the customer to remember it, find a check, and mail it. Every one of those steps is a place the payment stalls. When you chase by hand, you are the reminder system — an inconsistent one, because chasing feels rude and you skip weeks.
The fix is to move the effort off yourself and onto the workflow. Three levers do almost all of it: a deposit captured at signature, a card or bank draft (ACH) kept on file, and an automatic reminder ladder that fires before, on, and after the due date. Set them once and they run on every job — no bad-guy phone calls required.
Lever one: a deposit captured at signature
The cheapest money to collect is the money you collect before the truck leaves the yard. A deposit at signature — 25% to 50% on larger jobs — does three things: it funds your materials so you are not floating them, it filters out the tire-kickers, and it turns the customer from a stranger into someone with skin in the game.
The mechanism matters. If the deposit is a separate phone call after the quote is signed, half of them never happen. Fold it into the signature step instead: the customer opens the quote, picks options, signs on their phone, and pays the deposit in the same flow. In Mortar the signed quote and the deposit are one action on one screen — no gap between "yes" and "paid."
A deposit is a filter, not just a down payment
The customer who balks at a deposit is telling you something — and it is far cheaper to learn it at the quote stage than after you have bought $2,000 in materials and blocked out a Tuesday.
Lever two: a card or bank draft (ACH) kept on file
The single biggest cause of a slow-paying invoice is the gap between "I owe this" and "I have done the thing that pays it." A card or bank draft (ACH) on file closes that gap. The customer authorizes it once — usually at deposit — and the balance charges automatically when the job is marked done. No check to write, no portal to log into, no envelope to find.
This is not you holding their card in a shoebox. Payments run on your own connected Stripe account, so the money settles directly to you — Mortar never touches it. Stripe stores the details securely; you get a saved payment method to charge against the balance. Stripe's standard processing fee applies, and that fee is Stripe's, not ours. On a large job, offer a bank draft (ACH) too — it costs a flat few cents instead of a card percentage. For recurring work like a mowing route or a maintenance plan, the same saved method bills itself weekly, biweekly, or monthly, so the customer never sees an invoice to act on. That recurring engine is on Mortar's Core and Suite plans.
Lever three: automatic payment reminders before, on, and after due
Not every customer will leave a card on file. For the rest, the answer is not you remembering to text — it is a reminder ladder that runs itself. This is where automatic payment reminders to customers replace the Friday-afternoon guilt: you write the messages once, and the system sends them on schedule.
Before due — 3 days out
A short, friendly heads-up: "Invoice #1042 for $1,850 is due Friday. Pay here." Half of late payments are just forgotten, and this one message catches most of them before they are ever late.
On the due date
A plain reminder the day it is due, with the same pay link — just the number, the date, and one tap to pay.
After due — day 3 and day 7
A firmer nudge that the invoice is past due, then a second one a week later. Consistent, unemotional, and identical for every customer — no one gets chased, no one gets forgotten.
Writing the ladder down removes your judgment from the loop. You stop deciding whether it is "too soon" to remind someone — the schedule decided that, the same way for everyone, so the awkwardness disappears. And the more of the earlier levers you use — a deposit at signature, a card or bank draft on file, recurring work that bills itself — the shorter the ladder has to be, because most invoices are settled before a reminder is ever due.
The cash-flow math of shrinking days-to-pay
Days-to-pay is the number of days between sending an invoice and the money hitting your account. Most small service businesses run 20 to 45 days without meaning to. Cut that in half and you have not earned a dollar more — but thousands of dollars of your own money now sit in your account instead of the customer's inbox.
Work a simple version. Say you bill $40,000 a month and your average days-to-pay is 30. On any given day, roughly $40,000 of finished work is out there unpaid — a month of revenue you cannot touch. Drop days-to-pay to 15 and that balance falls to about $20,000, freeing $20,000 of cash for materials or payroll instead of a credit card. Deposits collect part up front, cards on file collect the rest the day the job closes, and the reminder ladder mops up whatever is left.
Faster pay is a raise you give yourself
Shrinking days-to-pay does not add a cent to your revenue. It just means the money you already earned is in your account instead of parked in someone else's inbox — the cheapest cash your business will ever raise.
Where a paper-check workflow quietly adds a week
A check is not free just because there is no processing fee. Look at the timeline: the customer opens the mail, finds the checkbook, writes it, and mails it — then it rides the mail for days, sits in your truck until you get to the bank, and takes another day or two to clear. That is easily a week of dead time built into every invoice, and a week you spend wondering whether to chase.
Digital payment collapses that week to a tap. The customer opens one link and pays by card or bank draft; the money is on its way the same day and posts to your books when it clears. Still take a check from the customer who insists — just do not let the check be your default, because the default is where your days-to-pay gets set.
Put the three levers together and the chasing stops being your job. The deposit funds the work, the saved payment method closes the balance, and a short reminder ladder handles the stragglers. For the whole picture of running the money side, start with how to run a service business, or see the one-off flow in how to send a quote and get paid. For repeat work, how to bill recurring service customers covers the saved-method version.
How do I send automatic payment reminders to customers?
Write a short reminder for three points in the cycle — a few days before due, on the due date, and after it is late — then send them on that schedule instead of deciding every Friday whether to nudge someone. The surer fix is to need fewer reminders: take a deposit at signature and keep a card or bank draft on file so the balance charges itself when the work is done.
Is it rude to charge a deposit or keep a card on file?
No — it is standard practice, and most customers expect it on a job of any size. A deposit funds your materials and filters out non-payers; a saved card or bank draft (ACH) just means the balance charges when the work is done instead of after a round of reminders. Both run on your own Stripe account, so the money settles to you.
How do I collect payments from lawn care and other recurring customers?
Keep a card or bank draft on file at signup and let the recurring engine bill it weekly, biweekly, or monthly. The customer authorizes it once and never has to act on an invoice again — the route bills itself. That recurring billing is on Mortar's Core and Suite plans.
Building Mortar — the all-in-one CRM for service businesses. One shared record, one number behind every job.