Every late-payment statistic starts counting after you invoice. That's the bit worth knowing.

The number gets quoted at every small-business event in the country: the average Australian invoice is paid around six days past its due date. It's true, and it's properly measured — Xero tracks it across hundreds of thousands of real businesses, and payment times have actually been improving lately. The conclusion everyone draws from it is that your customers are the problem. Chase harder. Send the reminder. Get firmer.

But there's something in how that number is built that changes what you'd actually do about it. The clock doesn't start when you finish the job. It starts when you send the invoice.

Where the measurement actually begins

Read the methodology and it's plain enough. The headline figure measures how long a business waits to be paid after issuing an invoice. The lateness figure measures days past the nominal due date on that invoice. Both are anchored to a document you create, on a date you choose. Neither of them has any idea when the work was done.

So the stretch between the last day on site and the moment you get around to invoicing isn't late. It isn't early. It isn't in the statistic at all. It doesn't show up in your aged receivables either, because the receivable doesn't exist yet. For most service businesses that gap isn't zero — the job finishes Tuesday, the invoicing happens Sunday night, or at month-end when you finally sit down with the laptop.

The half you don't control is getting worse

It's worth knowing what you're up against on the other side of that line. Australia's Payment Times Reporting Scheme tracks how long large businesses take to clear their small-business invoices, and the measure the regulator watches most closely is the slow tail — the days needed to pay 95% of them. In the most recent full reporting period it went the wrong way: out to 64 days, up from 58. Median payment times held roughly steady. The slowest payers just got slower.

That's the honest read on the chase-harder strategy. Firmer emails work on the customers who were largely going to pay anyway. On the genuinely slow end — a big client whose accounts payable runs a fixed cycle regardless of what lands in the inbox — a sharper reminder doesn't move the date. You're not negotiating with a person, you're negotiating with a process, and the process isn't reading your email.

Which is what makes those invisible days worth far more than they look. They're the only part of the cycle where you don't have to persuade anybody.

The gap isn't laziness — it's batching

The reason invoicing drifts to Sunday night is structural, not moral. Invoicing is admin, admin gets batched, and batching genuinely is faster: doing twenty invoices in one sitting takes less total time than doing each one as its job ends. Month-end invoicing isn't irrational. It's a sensible trade of cash-flow speed for personal time, made by someone who was never shown the price.

Here's the price. A week of batching isn't a week's delay once — it's a week added to every invoice, on every job, permanently. If your terms are 14 days and you invoice a week after the work, you've quietly built yourself a 21-day business, and then you're annoyed on day 27. Your customer hit their terms. You just started the clock late and blamed the finish line.

The fixes, cheapest first

• Invoice at completion, not at month-end. This is the whole ballgame. It costs nothing but a change of habit — or better, a system that raises it the moment the job's marked done, so the habit isn't required.
• Treat your payment terms as a decision, not an inheritance. Thirty days isn't a law, it's a convention borrowed from businesses that ship goods on credit. Due on receipt, or seven days, is entirely normal for a service business that has already done the work. If you never actually chose your terms, someone else chose them for you.
• Put a real date on the invoice. "Net 30" is jargon to a domestic client and vague to half the commercial ones. An actual calendar date removes the argument before it starts.
• Automate the polite chase. Most owners under-chase because chasing feels personal and a bit rude. The fix isn't to toughen up — it's to make the reminder a scheduled process that goes out whether or not you felt like sending it.
• Don't let your worst payer redesign your system. If one big client runs a 60-day cycle no matter what, price that in and move on. Building your whole process around your slowest customer punishes the other nineteen who'd have paid on time.

None of that is clever, and none of it is new. It's just aimed at the half of the delay that's actually yours, rather than the half that gets all the attention because there's someone else to blame for it.

Where we land on it

This shaped how the money side of Dispatch works. The invoice is raised off the completed job rather than waiting for someone to sit down at the end of the month, terms default to due-on-receipt and can be set per invoice, and the follow-ups run on their own schedule instead of on how you're feeling about it that week. None of that makes a slow payer fast — nothing does. It just deletes the days that were never the customer's fault in the first place.

So next time you see the stat, read it properly. It's a measurement of your customers' behaviour that begins at a moment you pick. Move that moment earlier and you get paid earlier, with no one to persuade, no awkward phone call, and nothing to chase. It's the least exciting cash-flow improvement available to a small business, and it's the only one that's entirely within your gift.