Treat unpaid invoices like a small state machine, not an email campaign

By Alex Reynolds, Synthos

If you freelance as a developer, an unpaid invoice can tempt you to build the wrong automation: a scheduled email that gets firmer every week.

Before writing that job, decide what state the invoice is actually in. A message that makes sense for an invoice nobody has acknowledged can be inappropriate when a valid payment promise is waiting to settle, or when the client has raised a genuine dispute.

The design below is an operational model, not a legal collection process.

Model evidence, not emotion

For each invoice, keep a small record:

invoice_id
currency
issued_total
credits_recorded
receipts_confirmed
due_date
status
last_evidence_reference
next_action
review_date
owner

Keep sensitive documents in your business system rather than copying them into every task or AI chat. The balance is issued total minus recorded credits minus confirmed receipts. A promise to pay is not a receipt.

Use statuses such as:

• Not yet due
• Overdue, awaiting response
• Payment promised
• Amount disputed
• Receipt awaiting reconciliation
• Closed after reconciliation

These statuses describe what you know. They do not establish the customer's motives or your legal rights.

Make transitions require evidence

A useful transition rule might be:

IF a payment promise is recorded:
    set the expected settlement date
    schedule a bank reconciliation review
    suppress the ordinary reminder

IF a dispute is recorded:
    route to a human investigation
    do not run the ordinary reminder sequence

IF a receipt is confirmed:
    reconcile the amount and reference
    close only the settled balance

This is pseudocode for designing your process, not deployable collection software. A review date means "look at the evidence again," not "send another email regardless."

Australian business.gov.au recommends a clear process for unpaid invoices, starting with a polite reminder by phone or email.[1] Business Queensland's invoicing tips include clear payment terms and relevant customer reference or order numbers.[2] That suggests a useful first investigation: did your invoice actually reach a person who can approve it, with the reference they need?

Ask one processing question

Here is a fictional reminder:

Hello Morgan, I am checking on invoice F-104 for AUD 1,800, due 18 September. Our records do not yet show payment. Could you confirm receipt and let me know whether you need any information to process it? If payment is already arranged, please share the expected date and reference. Thank you, Casey.

Before using a message like this, check the bank, the due date, the supported balance and the correct recipient. Do not add fees or legal claims because a text generator suggests them.

An optional AI tool can help shorten a draft. Give it redacted facts, tell it not to invent missing information, and keep sending authority with a person. A prompt alone is not a privacy control.

Test timing, not just the final balance

Consider a fictional four-week cash plan in AUD. Start with 3,000 available cash. Outflows are 1,400, 1,300, 1,200 and 1,100. Expected receipts are 1,800 in week one and 2,400 in week three.

The base-case closing balances are 3,400, 2,100, 3,300 and 2,200. Delay the first receipt until week three and those balances become 1,600, 300, 3,300 and 2,200.

The month ends at the same number. The week-two buffer does not. This is why an invoice's next action belongs beside your cash scenario rather than in a disconnected email thread.

Neither scenario predicts what a customer will do. Use it to decide when you need to review options. Formal collection, changes to contractual terms, service suspension and debt write-offs can require professional advice; don't automate those decisions from a blog post.

A paper-first version

If you prefer to work through the process before automating anything, I created The Freelancer Payment Reset Workbook, an 18-page printable PDF from Synthos, priced at AUD 14.

It includes an evidence register, approval-chain map, reminder examples, promise and dispute review pages, four-week cash exercises and a weekly operating routine. It is a manual workbook, not an interactive calculator, accounting system or legal demand-letter pack.

Start with five invoices. The useful outcome is not five messages sent. It is five supported balances with an owner, a next action and a review date.

Synthos by Alex Reynolds
[e-mail]

Sources

[1] https://business.gov.au/finance/payments-and-invoicing/payment-terms
[2] https://www.business.qld.gov.au/running-business/finance/essentials/cash-flow-payments