Getting invoices paid, without chasing the wrong people

Every morning it reads the open invoices and the money that came in, works out who actually still owes, and writes a polite reminder only to them. Everything else goes to a person or to nothing at all.

Tested 23 Sep 2026 on 8 invoices and 3 payments: 9 decisions, 2 reminders written, 3 handed to a person.

9 / 9invoices accounted for
2reminders written and approved
3handed to a person
37 / 37rule checks passing

How it runs

Five steps, in the order they happen each morning.

The workflow on the n8n canvas, left to right
  1. It reads both sides at once

    The invoices still open, and the money that arrived recently. Neither one on its own is enough to decide anything.

  2. Payments are matched before a word is written

    The worst thing an automatic reminder can do is chase somebody who has already paid. So the matching happens first, and it is deliberately cautious.

    Invoice
    INV-1005, 5 days overdue
    Result
    Payment arrived yesterday → closed, no reminder
  3. Each invoice gets exactly one outcome

    Send the invoice, send a reminder, hand it to a person, or do nothing. Part payments, overpayments and money nobody can place all go to a person.

    From 9 decisions
    1 invoice sent, 2 reminders, 3 to review
    No action
    3 — not due, or already reminded
  4. The AI writes it, a separate check approves it

    The AI (Claude) writes the wording. A plain rule then decides whether that wording may be used at all — and the invoice number, amount and due date are added by the system, not by the AI.

    Drafts written
    2
    Approved to send
    2 of 2
  5. Every morning leaves a record

    One line per invoice, with what was decided and why. A day with nothing to do still writes a line, so the log proves the run happened rather than silently skipping.

    Still outstanding
    9,140.00
    Of that, overdue
    7,110.00

How it’s built

Three decisions that do most of the work.

Match the money first, then write

The worst failure for a system like this is reminding a good customer about an invoice they settled last week. Matching before drafting, rather than drafting and then checking, makes that failure impossible instead of merely unlikely. INV-1005 in the test was five days overdue; the payment had landed the previous day with the invoice number in the reference, so it closed as paid and no reminder was written.

The AI writes the words, plain rules decide

A reminder is rejected unless it carries the exact invoice number and amount, and rejected for quoting any other sum of money, for any link, for leftover brackets, for running past 1200 characters, or for arriving without a subject line. The figures are appended by the system afterwards, so a wrong number cannot reach a customer whatever the AI writes. If the AI is unavailable a fixed template goes out instead — the outage costs the personal touch, never the reminder.

Guessing is not allowed

A payment is matched by the invoice number in its reference, or failing that by an exact amount from the same customer — and only when exactly one invoice fits. Two invoices of the same amount from one customer are deliberately not guessed between. Everything the system is unsure about ends up in front of somebody, carrying the reason, rather than resolving itself into an email.

What was verified

Run for real on 23 September 2026, with the items counted at each step rather than taken on trust: 9 decisions in, 9 recorded out, nothing lost in the middle.

Four situations were tested: a normal day, a day with nothing open, unreadable input, and an invoice with a broken email address. The last three all ended with a person being asked and nothing sent.

Separately, 37 of 37 rule checks pass, covering every way the approval step can reject a draft — wrong amount, invented fee, missing invoice number, a link, a blank left unfilled, and the AI failing outright.

Not verified: no reminder has been sent to a real customer. The sending step is switched off and holds no email account, so the test run reported what would have gone out rather than sending it.

INV-1005 — 5 days overdue, payment received yesterday with the invoice number in the reference. Closed as paid; no reminder sent.

The line the test run produced for the invoice that mattered most: the one the system had every reason to chase, and correctly did not.