The One Job on the List With No Deadline
Almost every business hiring an accounts person puts chasing debtors on the list. In most of them, a year later, it is still the one thing that is not getting done, and the reason has nothing to do with who they hired.
Does the work of
- Accounts Administrator
- Accounts Officer
- Accounts & Administration Officer
- Office & Accounts Administrator
- Finance Administrator
There is a moment every Thursday afternoon where the choice is between finishing the payment run and ringing four customers about money they owe. The payment run has a deadline and a supplier who will notice. The phone calls have neither, so they move to next week, and they have been moving to next week since March.
In short
- The problem
- Chasing debtors is one duty of nine in a typical accounts role, and the only one with no external deadline attached.
- Why it slips
- Nobody rings to complain that you did not chase them, so in any week that runs over it is the strand that gives. A second hire mostly gives you two people with the same queue.
- What we would automate
- One strand only: the calls and messages due on day seven, day twenty-one and day forty, and the four replies that come back.
- What stays with a person
- Deciding who gets credit, negotiating a plan, judging when the relationship outranks the invoice, anything contested, and the front desk phone.
Want the whole thing by email?
This paper, plus the rest of the library. One click to stop them.
The Short Version
Chasing debtors is the only duty in an accounts role with no external deadline. Staff notice when payroll is late. Suppliers stop supplying. The ATO issues penalties. Nobody rings to complain that you did not chase them. So in any week that runs over, it is the strand that gives, and a second hire mostly gives you two people with the same queue.
What we do is take that one strand out of the queue, and we already have the thing that does it. Office Voice is our own product and it is live today: it makes the calls and sends the messages that should go out on day seven, day twenty-one and day forty whether or not anyone had time, and it handles the replies that come back. It reads your Xero directly, so it knows the balance on the call and stops the moment an invoice is paid. Voice-led, because money that is genuinely stuck is stuck behind a conversation rather than behind a missing reminder.
It is a subscription, not a build. There is no implementation project, and everything else on that job description stays exactly where it is, with the person you hired to do it.
What we do first is tell you whether it is worth doing at all. A large share of what shows as overdue on an Australian ledger was never late: 60 day terms that are the contract, retention held to practical completion, a payment claim running under a Security of Payment Act. If your book is mostly that, we will say so, and you should not buy anything from us or from anyone else in this category.
The rest of this paper, if you want the reasoning
- • Why the chase is structurally the strand that slips, and why hiring at it does not hold
- • How much of your aged receivables list is genuinely chaseable, which is usually less than the report implies
- • What actually stops a chase: four sentences, and only one of them needs a person
1. Nine Duties, One With No Deadline
In most Australian small businesses there is no collections department. There is one person who does the accounts, and the accounts are eight or nine different jobs: supplier invoices, payroll, the bank reconciliation, statements, the month-end pack, the BAS, the phone, and somewhere down the list, the debtors.
Those jobs do not compete on equal terms, and the reason has nothing to do with how good the person is. Look at what forces each of them to happen.
| Duty | What forces it to happen |
|---|---|
| Payroll | Staff are paid Tuesday |
| Supplier payment run | Suppliers stop supplying |
| Bank reconciliation | Daily, or the ledger drifts |
| Statement run | Month end |
| Month-end reporting | The board, or the accountant |
| BAS and compliance | The ATO, quarterly |
| Chasing overdue invoices | Nothing |
Two things follow from that last row, and the second one is the expensive one.
It does not slip evenly. The chase gives way when everything else is heavy: a big month, someone on leave, a system changeover, the end of the financial year. Those are precisely the periods when the business has the most money sitting out on invoice. The strand that fails is the one you most needed working, and it fails quietly enough that the first sign is a cash position nobody can quite explain.
It does not respond to headcount. Give the same nine duties to two people and you have two queues sorted by the same rule, so the undated work still settles to the bottom of both. This is why businesses hire into this problem repeatedly and stay surprised by the result. The work only moves when it either leaves the queue altogether, or acquires a deadline of its own. A scheduled sequence of contacts that runs without anyone deciding to start it is, functionally, a deadline.
Which is the whole idea, and it is a narrow one. Take the one strand with no date on it. Leave the other eight with the person you hired to do them.
2. Not Everything Overdue Is Late
Before any of this is worth automating, there is a question most vendors in this category skip: how much of your aged receivables list is actually chaseable?
The aged view does not distinguish between four completely different things, and only one of them responds to being chased.
Late by agreement
In construction, mining services and a lot of enterprise supply, 60 or 90 day terms are the contract. It shows in the ageing as overdue and it is nothing of the kind. Some businesses have almost no receivables genuinely outside terms, and chasing that book harder damages relationships without moving a dollar.
Retention
Commonly 5% of each payment, deliberately withheld until practical completion and the end of the defects liability period. It is not late, it is not forgotten, and it is not a collections problem. It is a diary problem, and a different one.
Statutory payment claims
A progress claim can be a payment claim under the relevant state Security of Payment Act, carrying a statutory response clock and a fast adjudication path. An AI has no business anywhere near one of those, and ours is built not to touch them. If that is where your money is stuck, you need an adjudication process, not a chaser.
Contested
Certified down, short paid, or held against a defect. This is a conversation between two people who disagree, and it needs one of yours.
What is left after those four is the ordinary overdue slice: invoices that are simply late, usually because nobody has asked. That slice is where automation earns its keep, and on most ledgers it is a good deal smaller than the ageing report implies.
Why we lead with this
Any vendor can quote you a days-sales-outstanding improvement off your total ageing. The number that matters is the improvement against the chaseable slice, and working out which is which takes fifteen minutes with your real list. We would rather do that first and tell you it is not worth automating than sell you a chaser for a book that is behaving exactly as contracted.
3. Why Reminder Emails Take Part of the Loop
Most tools in this category are email sequence engines. They send reminder one at day seven, reminder two at day fourteen, and a firmer one at day thirty. They are genuinely useful and they are genuinely cheap, and if you have none of it today, some of it beats none of it.
The limit is structural. Emailed reminders work best on the debt that was going to be paid anyway, and their effect decays as the invoice ages, because the longer something sits, the more likely it is sitting behind a reason rather than an oversight. A query nobody answered. A missing purchase order number. An approver who has not approved. None of those are resolved by a fourth reminder, and a sequence has no way to find out which one it is up against.
This is why real collections desks are phone-led and always have been, and it shows up plainly in how the roles are written: where a business advertises specifically for collections work, it asks for phone and email, not one or the other.
The honest version
An inbox-led tool takes part of the loop, not the loop. If your debtors mostly pay a bit late out of habit, reminder emails will recover most of it and you do not need us. If your money is stuck behind conversations, the sequence will run its course and the invoice will still be sitting there on day sixty.
What we build is voice-led and message-supported: a call that can actually have the conversation, with the invoice and the ledger balance in front of it, backed by SMS and email for the parts that are better in writing. The channel follows the debtor, not a fixed ladder.
4. The Four Sentences That Stop a Chase
When a chase stalls, it almost always stalls on one of a small number of sentences. This is the part of receivables work people underestimate: handling the query is the job, not sending the reminder. Ask anyone who has run a debtor ledger and they will tell you the same thing, and it is the duty that comes up most often when businesses write down what they need a receivables person to do.
Most automation treats every one of these as “disputed”, stops, and hands the invoice back to a person, which means the tool does the easy half and returns the half you were trying to offload. Handled properly, most of them are not a person’s job at all.
“We never got the invoice.”
Resend it during the call, confirm the address it should go to next time, and keep going. Nobody needs to be interrupted for this.
“It’s waiting on our manager to approve.”
The most valuable answer you can get, and the one an email sequence never gets. Capture the approver’s name and number, and chase the person who can actually release it.
“I paid that last week.”
Never argue and never confirm. Take the date, the amount and the account it came from, then watch the ledger and close it off automatically when the payment appears.
“The amount is wrong” / “that work was never finished”
This one is yours. A genuine contest over what is owed goes straight to a person, with the reason attached so they are not starting from scratch. We do not negotiate on your behalf.
The difference between those four is the difference between a tool that reduces your interruptions and one that redistributes them.
5. What We Do Not Touch
We are not proposing you cancel the hire. Eight of the nine duties on that ad are a person’s job, and several of them are the reason you want a person in the first place.
Still a person’s job: deciding who gets credit and how much. Negotiating a settlement or a payment plan. Judging when a customer relationship matters more than an invoice. Anything contested. Coding a transaction that does not look like the last one. The month-end judgement calls. And the phone at the front desk.
What we take: one strand. The routine, repeated, undated part of getting paid: the calls and messages that should go out on day seven and day twenty-one and day forty whether or not anyone had time, and the four sentences above when they come back.
Hire the person for the other eight. The chase runs on the days they do not get to it.
6. It Runs on What You Already Have
There is no single accounting system in this market and there is not close to one. Xero is the most common single answer among Australian small businesses, MYOB sits behind it, and after those two the tail is long: Pronto, SAP, NetSuite, TechnologyOne, Business Central, Sage, and a substantial number of businesses running the ledger without any of them.
We took that seriously when we built this. There is a direct Xero connection because Xero is the most common single answer, and it is the one where we can read the invoice, see the balance, and stop chasing the moment a payment lands. Where there is no supported connection, the chase still runs off an aged receivables export. You keep your system, and nothing gets migrated.
Results come back to you where you already look: on your aged receivables list, in the order you already read it, rather than in another dashboard nobody opens.
7. The Thing That Does This Already Exists
Everything described above is not a project we would scope and quote you for. It is a product we build and run: Office Voice, the AI admin that gets you paid. It is live now, with Australian businesses on it.
Connected to your ledger
Live Xero connection. It knows the invoice and the balance on the call, and stops chasing the moment a payment lands, so nobody gets rung about something they already paid.
Paid during the conversation
Payment links sent mid-call, to the number you are already speaking to. No card details are ever taken over the phone, deliberately.
Promises that get kept
A commitment to pay on a date is recorded and followed up on that date, including where the payment is coming by EFT rather than through a link.
Australian compliance built in
Calling hours, Do Not Call handling, AI disclosure and recording consent on every call. Not a setting you have to remember.
If you run a bookkeeping or accounting practice, it bills per client ledger and works across a portfolio rather than one org at a time.
Where a build still makes sense
Credit control rules, remittance allocation, or an unusual ledger we do not connect to yet are a scoped piece of work around the product rather than instead of it. Trial the subscription first. It answers most of the question for a fraction of the commitment, and it tells you whether the build is worth commissioning.
Where this comes from
Two places. The first is the work: we build and run receivables automation for Australian businesses, and the four sentences in section 4 and the carve-outs in section 2 are what that work teaches you. The second is a standing read of the market. We track the Australian job ads for accounts roles as a check on whether what we believe about this work still matches what businesses are actually asking for.
In a recent thirteen-day window, 92 small and mid-sized businesses advertised for someone to chase overdue accounts. Their ads listed 9.5 duties on average; 65% also covered accounts payable and 39% also covered reception or general admin. That is the pattern section 1 describes, and we would rather show you the check than ask you to take the claim on faith.
8. Getting Started
The useful first conversation is not a demo. It is fifteen minutes on your actual ledger: how much is past sixty days, how much of that is genuinely late as opposed to contested or on agreed terms, and who chased last week.
Quite often that conversation ends with us saying the honest thing: your debtor book is small enough, or clean enough, that a person with a reminder schedule will do. We would rather tell you that in the first fifteen minutes than in the third month.
If you want to read further first, AI Voice Agents for Accounts Receivable covers how the calls actually work, and our compliance paper covers the rules around contacting your customers: the Do Not Call Register, calling hours, AI disclosure and recording consent.
Not ready to talk yet?
Leave your email and we’ll send this paper to your inbox, with a link to the rest of the library. We publish a new one every few weeks and you’ll get those too, one click to stop them.
Your email is used to send you the papers and nothing else. We don’t share it.
Which of your overdue invoices are actually chaseable?
Get in touch with AI Pathway. Fifteen minutes on your real aged list: what is past sixty days, how much of it is genuinely late rather than contested or on agreed terms, and whether this is worth automating at all for a book your size.