You already automated your invoice reminders and the same people still don't pay

A reminder sequence assumes the customer wants to pay and needs prompting. That holds for most of your ledger. It fails completely on the accounts that hurt. The people who owe you the most have decided, consciously or not, that your invoice sits behind their own cash pressures. Another email does not change their ranking. It adds to a pile they have already learned to ignore. An Australian owner on r/ausbusiness put the mechanism plainly: "A tool to prompt them to pay doesn’t do or solve anything, it just becomes noise and they will ignore it much like ignoring follow up texts or phone calls etc." Another, after doing exactly what the accounting software told them to do: "I've tried automated email reminders but no luck. I use XERO." These are recurring themes in the threads, not a survey result, but the pattern is consistent enough to plan around. If your collection strategy is entirely made of messages, your only tool is the customer's goodwill. Reminders are a memory tool. Non-payment is a power problem.

Sequence the money, not the nagging. A deposit before work starts filters out people who cannot or will not pay, and it applies to everyone, especially new customers. Progress claims tied to milestones cap your exposure to one stage instead of the whole job, which matters most on larger or longer work. The automated reminder sequence catches genuine forgetting among the honest majority. A documented escalation with dates and amounts creates a record and a consequence for chronic late payers. Deposits and progress claims do the heavy lifting because they happen while you still hold something the customer wants. Once the job is finished, your only remaining lever is the relationship and the paperwork. A service business owner on r/smallbusiness described the switch: "I used to do 30-50% upfront and the rest on a big final invoice, which left me with a few unpaid or very late payments. Now I am testing smaller milestones where each step has a clear deliverable and is paid before I start that part of the work." Smaller claims are easier to approve and much cheaper to lose. Splitting one final invoice into three staged claims is a process change, not a software change.

Because one customer is too big to annoy. When a single client is a meaningful slice of your revenue, the automated sequence becomes a risk. You do not want a stern day-30 email going out to the account that keeps your quarter alive, so you exclude them. Then you exclude the one who complained. Within a few months the sequence only runs on customers who were going to pay anyway, and the manual chase ritual returns for the ones who matter. A related bind shows up on r/ausbusiness, where the owner keeps chasing rather than enforcing terms: "It's driving me insane to have to do this over and over, but this person is not an insignificant part of my very marginal business, and I really cannot afford to lose him." That is not a technology failure. It is concentration risk showing up as a billing problem. If losing one customer would end your year, you cannot enforce terms on them. The honest fix is slow: reduce the concentration. In the meantime, treat that account differently on purpose rather than by exception, with shorter stages, smaller claims and payment before the next phase begins.

Late money moves down the chain and you are the one who has to make the awkward phone call. An owner on r/ausbusiness showed the chain in a single sentence: "Had 3 clients pay late this month, one still owes $2.8k from last month which meant i had to delay paying a contractor $4.5k and it got awkward af real quick." This is why treating late payment as a cost of doing business is misleading. The cost is the subcontractor who now rates you as slow, the supplier who tightens your account, and the BAS or payroll date that does not move because your customer decided to pay in six weeks. Two consequences follow. First, set your escalation timeline by your own payables calendar, not by a generic 7, 14, 30 day template. If your subcontractors are paid weekly, a 30 day first escalation is too late. Second, track ageing by customer, not by total dollars outstanding. Total debtors tells you how much. Ageing by customer tells you who to stop extending credit to.

Write it once and apply it the same way every time. Consistency is what makes it credible. Before the job: written terms, a deposit, and stated payment dates on the quote, not "due upon receipt". On the day of invoice: send it immediately with the payment method already set up, because delay on your side invites delay on theirs. Then two or three friendly automated reminders on a fixed schedule, no exceptions. Then first human contact, a phone call rather than an email, with a specific date and a specific amount. Then a documented escalation restating the amount, the original due date, the days overdue and what happens next. Then stop work or stop supply on anything new until the account is clear. Finally, formal recovery through a letter of demand or a debt collector, decided in advance so it is not an emotional choice. The first three steps can be automated in Xero, MYOB, ServiceM8 or Tradify. The rest are decisions, and what you automate there is the trigger, the reporting and the record: who crossed the line today, how much they owe, what was sent and when.

Partly. Reminders solve the top layer and the rest is commercial policy. Software genuinely helps with getting invoices out on the day of completion instead of the weekend, making sure nothing falls through when the person who normally chases is on leave, and giving an accurate daily view of who is overdue and by how much so escalation happens on schedule rather than when you get frustrated. Software does not make a customer who has decided not to pay change their mind. This matters for how you buy help. The useful work is diagnosis and process design, not building the message sequence. An outside agency can install a reminder flow in a day. What they cannot do from outside is decide which of your customers gets a deposit requirement, when you stop supply, and how your ageing ladder maps to your own payables. Those calls belong to someone inside the business who understands the customer relationships. That is why 13Labs runs buildAutomation as capability transfer: we train two or three of your own people to map the process, build the triggers and reporting, and own it afterwards. Automations die when the only person who understands them is an outside agency that sends an invoice every month. A collections process needs an owner who can change the rules when a customer changes their behaviour.

**Do automated invoice reminders in Xero actually work?** They work on customers who simply forgot, which is a real and useful share of overdue invoices. They do not work on customers who are deliberately holding your money. An Australian owner in the threads below reports setting up Xero reminders and seeing no change on their worst accounts. Treat reminders as the baseline, not the strategy. **Should I charge late payment fees?** Only if you will actually enforce them and your terms state them clearly before the work starts. Late fees are not a reliable deterrent on chronic non-payers. One owner in the threads below describes a client who simply pays the late fees and keeps paying late. Fees work better as a reason to escalate consistently than as a deterrent by themselves. **Is asking for a deposit going to cost me work?** Some customers will decline, and a portion of those were the ones who would have paid late anyway. The greater risk is finishing a whole job for someone who was never going to pay in full. **What should I do when the late payer is my biggest client?** Stop treating it as a billing problem. Shorten the stages so less money is exposed at any moment, invoice on milestones rather than completion, and work on reducing what share of revenue that client represents. Enforcement is not credible while losing them would end your year. **Can I automate the escalation itself?** You can automate the trigger and the record: who crossed a threshold today, the amount, the days overdue, and what has already been sent. The escalation contact itself is better done by a person. Automating the detection is what makes escalation happen on time. **Who should build this inside a small business?** Whoever owns the customer relationships and understands the process, usually an office manager or the owner. The skill needed is process mapping and diagnosis, not tool expertise. That skill stays with the business, which is why an internal owner beats an outsourced build.

Quotes are reproduced verbatim from public Reddit threads and attributed to the subreddit only. r/ausbusiness: https://www.reddit.com/r/ausbusiness/comments/1t57mex/australian_businesses_really_just_accept_late/ ; r/ausbusiness: https://www.reddit.com/r/ausbusiness/comments/1mi20md/help_chasing_late_invoices_tradies_sole_traders/ ; r/ausbusiness: https://www.reddit.com/r/ausbusiness/comments/1sylx4r/consistent_late_payments_driving_me_nuts/ ; r/ausbusiness: https://www.reddit.com/r/ausbusiness/comments/1udin2w/chasing_payments_is_killing_my_productivity/ ; r/smallbusiness: https://www.reddit.com/r/smallbusiness/comments/1p7z21w/how_do_you_structure_project_payments_to_avoid/ . No statistics are cited in this article. Where the text says a pattern is recurring, that reflects repeated comments in the threads above, not a survey.