By KYN AI Advisory Team — AI implementation specialists, Singapore
An invoice chasing agent sends a reminder ladder after the due date: a friendly note on day 3, a firm one on day 14 and a final notice on day 30. It stops the moment the invoice is paid or disputed, and a named person approves anything sent. This article gives the three templates, the rules behind them and the stop conditions. KYN runs this ladder on its own receivables.
What is a reminder ladder, and why three steps?
A ladder is a fixed schedule of messages, each firmer than the last. Three steps work for most SMEs because each has a different purpose.
| Step | Days after due date | Purpose | Tone | |---|---|---|---| | 1 | 3 | Catch the honest oversight | Friendly, short | | 2 | 14 | Confirm the invoice was received and is scheduled | Firm, specific | | 3 | 30 | State the consequence and ask for a date | Formal, plain |
The days are a choice, not a rule. Pick them to match your payment terms. For a 7-day customer, the ladder can run faster. What matters is that it is written down and applied to everyone the same way.
What rules does the agent follow?
The agent works from the ledger, so the rules are about data, not judgement.
- Trigger. Invoice status is open and today minus the due date equals the step day.
- Skip. Do not send if the invoice is paid, in dispute, on a payment plan, or the customer is flagged "do not chase".
- Stop. A payment, a dispute note, or a reply that promises a date pauses the ladder.
- Channel. Email by default. WhatsApp where the customer already uses it with you.
- Copy. Use the template for the step. Fill the fields from the ledger: name, invoice number, amount, due date, payment details.
- Approval. A named person approves each message, or a batch, before it goes. Step 3 always needs a person.
- Log. Record what was sent, to whom, when, and who approved it.
Sending is outbound and carries your name. That is why approval stays with a person. See approval gates for high-risk agent actions.
Template 1: day 3
Subject: Invoice {number} due {due date}
Hello {first name},
Our records show invoice {number} for {currency} {amount}, due on {due date}, is still open.
If you have paid, please ignore this note and send the remittance so we can match it. If not, payment details are below.
{payment details}
Thank you, {sender name}
Why it works: it assumes an oversight, gives the facts and asks for one thing.
Template 2: day 14
Subject: Invoice {number}: {currency} {amount}, 14 days overdue
Hello {first name},
Invoice {number} for {currency} {amount} was due on {due date} and is now 14 days overdue. We sent a reminder on {date of step 1}.
Please confirm one of the following by {date, 3 working days ahead}:
- the payment date;
- the reason for any delay;
- a query on the invoice.
A copy of the invoice is attached.
Regards, {sender name}
Why it works: it names the history, offers three clear replies and sets a date.
Template 3: day 30
Subject: Final notice: invoice {number}
Hello {first name},
Invoice {number} for {currency} {amount} is 30 days overdue. We have written on {date 1} and {date 2}.
Please pay by {date} or contact us with a payment date. If we do not hear from you, we will {next action stated in your terms, for example pause new orders}.
Regards, {sender name}
Only state a consequence that your contract allows and you intend to apply. Check late-payment terms with your adviser before you name any fee or legal step. Do not let the agent invent consequences. The template holds the wording, and the agent fills fields only.
How does the agent handle replies?
Replies are where the ladder meets people. The agent reads each one and labels it:
- Paid, remittance attached. Pause the ladder and flag the payment for matching to the bank line.
- Promise to pay with a date. Pause until that date, then resume if unpaid.
- Dispute or query. Stop. Route to the person who owns the account.
- Wrong contact. Ask for the right contact and update the record.
- Hostile or legal language. Stop and alert a named person.
Labelling a reply costs about S$0.01 in our live reply desk. The label drives the next step. Nothing is sent in response without a person.
What can go wrong?
- Chasing a paid invoice. The most damaging error. Cause: payment not yet matched to the invoice. Fix: match bank lines first, and send reminders only after the day's reconciliation. See bank reconciliation with an AI agent.
- Wrong amount. Cause: partial payments or credit notes. Fix: chase the open balance, not the original total.
- Tone mismatch. A key customer receives a firm template. Fix: a customer flag that routes to a person for a personal note.
- Wrong contact. Fix: store the accounts-payable contact separately from the sales contact.
Which customers should skip the ladder?
Not every overdue invoice belongs in a standard ladder. Set these cases aside before the first message goes out.
- Disputed invoices. If the customer has raised a query, stop the ladder until it is resolved. A reminder on a disputed bill damages the relationship and proves nothing.
- Large accounts with a named contact. A phone call from the account owner beats three templates. The agent flags the invoice to that person instead.
- Payment plans. If you agreed instalments, the ladder follows the plan dates, not the original due date.
- Government and large-company payers. Their payment runs are scheduled. A day 3 reminder adds noise. Adjust the first step to the customer's known run date.
A simple hold list handles all four. The agent checks it before drafting. Anyone on the list gets a note to the owner rather than a template.
Worked example (illustrative): 30 invoices fall overdue in a month. Four are disputed, two belong to key accounts and one is on a plan. The agent drafts 23 day 3 messages and sends the other seven to their owners with a reason each.
How do you tune the tone?
Tone matters more than timing. Read each template aloud and ask whether you would send it to a customer you want to keep. Day 3 should sound like a helpful note: the invoice number, the amount, the due date and how to pay. Day 14 states that the invoice is overdue and asks for a payment date. Day 30 names the consequence you have agreed in your terms, such as a hold on new orders, and offers a call. Do not threaten anything you will not do. Have the person who owns the customer relationship edit each template once, then lock the wording so every customer sees the same message. Review reply rates quarterly and change one template at a time, so you know which edit made the difference.
Where KYN fits
KYN chases its own receivables at 3, 14 and 30 days. The messages are drafted from the ledger and wait on a reply desk for a named person. Every action is logged with the actor, and outbound messages, money and filings wait for a person. Systems run in a cloud account in the client's name.
Before building a reminder ladder we review how you invoice today, who owns each customer relationship and which accounts need a call instead of a template. That review takes the first 14 days. A full build ships in under 90 days. See finance systems.
For the effect on cash, read how to reduce days sales outstanding with automated reminders.
Frequently asked questions
Should reminders go before the due date?
A pre-due reminder is an option and many teams use one. It is a courtesy, so keep it short and send it only to customers with a history of late payment.
Can the agent send reminders without approval?
Technically yes. We recommend against it for the first months. Approve batches until the error rate is known, and keep step 3 under a named person permanently.
What if a customer is in dispute?
The ladder stops for that invoice. The dispute goes to the account owner, and the ladder restarts only when a person lifts the flag.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
