The Ledger Says Who Owes You. Nobody Has Time to Ask

1. Three Jobs, One Title

Advertise for an accounts receivable officer and you are advertising for three distinct kinds of work. There is chasing: someone has to ask for money that is already earned. There is credit control: deciding who gets terms, how much, and when to stop supplying. And there is allocation: matching the payments that arrive against the invoices they were meant for, and reconciling the statements that follow.

These fail differently. Chasing fails because nobody wants to do it, so it gets deferred to Friday and then not done. Credit control fails because it happens too late: the risk was visible before the order was accepted and nobody was watching. Allocation fails silently, in the form of a month-end that takes two days instead of two hours.

Automating them as one thing is the usual mistake. They want different treatments, in a particular order, and the order is not the one most businesses pick.

2. Payment Chasing

An emailed reminder asks the customer to do something later. It lands in the same inbox as everything else and gets archived unread. The one thing that reliably moves an invoice is somebody asking directly, and that is the thing nobody in the business wants to do.

So the automation is not “send more reminders”. It is a sequence with escalating contact types, where each step is triggered by the ledger rather than by anyone remembering: a reminder before the due date, a firmer one after it, then a call. The call reads the live balance at dial time, states the specific invoice, sends a payment link mid-conversation if the customer agrees, and records a promise-to-pay with a date if they do not pay on the spot.

The thing that makes it work is coverage rather than persuasion. Most debtors pay when someone asks; the problem is that nobody has the hours to ask all of them, so the calls that happen go to the largest balances and everything under a few thousand dollars ages out unattended.

3. Credit Control

Chasing is what you do after the decision. Credit control is the decision, and it is where the cheaper wins are, because a debt you never took on costs nothing to collect.

In most small businesses credit control is not a process, it is a memory: somebody knows that a particular customer is slow, and sometimes mentions it. Automating it means writing that knowledge down as rules the ledger can act on.

None of this needs a model to be clever. It needs the rules to exist and something to enforce them on every order rather than on the ones somebody happens to look at.

4. Statement and Remittance Reconciliation

This is the invisible third of the job. Payments arrive as a lump sum with a reference that means something only to the customer. A remittance advice turns up separately, as a PDF, an email body, or a spreadsheet, listing which invoices the lump was meant to cover. Somebody reads one and types the other.

Automating it is document work, and it is the same shape as invoice capture on the payables side: read the remittance, extract the invoice numbers and amounts, and allocate the receipt across them. The interesting cases are the ones that do not add up (a short payment, a deduction nobody explained, a credit note applied without warning), and those go to a person as a short exception list instead of as a bank statement to reverse-engineer.

Customer statements are the other half. Sending them is trivially automatable and most businesses still do it by hand or not at all, which matters more than it sounds: a statement is often what surfaces the invoice the customer genuinely never received, and it costs nothing to send on a schedule.

5. Key Benefits

6. End-to-End Workflow

1. 1New customer onboarded with ABN, GST and trading checks, and a credit limit recorded
2. 2Order checked against the limit and the current balance before it is accepted
3. 3Invoice issued from the ledger, with the customer's terms applied
4. 4Reminder sent before the due date, and again after it, triggered by the ledger
5. 5Overdue accounts prioritised by age, amount and contact history
6. 6Call placed against live balances, with a payment link sent mid-conversation
7. 7Promise-to-pay captured with a date, or dispute detail recorded for a person
8. 8Incoming payments matched to remittance advices and allocated across invoices
9. 9Short payments and unexplained deductions raised as an exception list
10. 10Risk score updated from behaviour; terms stepped down or a stop-supply proposed

7. What Stays With a Person

Receivables touches customers you want to keep, so the boundary matters more here than almost anywhere else in a back office.

8. Potential Tech Stack

One workable shape. The layers matter more than the specific products.

9. ROI Snapshot

Illustrative figures for a business carrying $150,000 in receivables with an average of 52 debtor days. Your numbers will differ: the point is which levers move.

The largest single gain is usually not the invoices you eventually recover. It is the ones you recover four weeks earlier, and the bad debt you never took on because the limit was checked when the order came in.

10. Getting Started

1. 1

   Get your baseline

   Average debtor days, total overdue, the ageing distribution, and how much cash is sitting unallocated. The last number is usually the surprise.

2. 2

   Fix allocation first

   Counter-intuitive, but chasing runs on the ageing report. If receipts are not allocated, you will ring people who have already paid, and once is enough to lose trust in the whole thing.

3. 3

   Clean the contact data

   Voice chasing is only as good as your phone numbers. Wrong numbers are the single biggest cause of poor contact rates.

4. 4

   Write the credit policy down

   Limits, terms, what triggers a step-down, what triggers a proposed stop-supply, what an agent may agree to unaided. This is the product decision and it is yours.

5. 5

   Start with one ageing bucket

   Run the 30 to 60 day band first. Recent enough that goodwill is intact, overdue enough that a call is clearly warranted.