By KYN AI Advisory Team — AI implementation specialists, Singapore
Automated reminders reduce days sales outstanding (DSO) by closing the gap between the due date and the day someone asks for payment. They work on late payers who forgot or lost the invoice. They do not fix disputed invoices, long contractual terms or customers who cannot pay. Measure DSO before you start, change one thing at a time, and read the result by customer group, not as one average.
What is DSO and how do you calculate it?
DSO is the average number of days it takes to collect payment after a sale. The common formula:
DSO = (accounts receivable at period end ÷ credit sales in the period) × days in the period
Example: receivables of S$120,000 at the end of a 30-day month, with credit sales of S$150,000 in that month, give DSO = (120,000 ÷ 150,000) × 30 = 24 days.
Two cautions. First, DSO moves with sales timing: a large invoice raised on the last day inflates it. Second, an average hides the spread. Ten customers paying at 20 days and one paying at 120 days produce a figure that describes neither. Track the open invoices past due by age band (1 to 30, 31 to 60, over 60 days) next to DSO.
Where do the days actually go?
Late payment has a few causes, and reminders address only some.
| Cause | Do reminders help? | |---|---| | Customer forgot or lost the invoice | Yes | | Invoice went to the wrong contact | Yes, if the reply fixes the contact | | Invoice sits in an approval queue at the customer | Partly: a nudge to the right person | | Dispute over amount or delivery | No: needs a person to resolve | | Customer's own cash is tight | No: needs a conversation and maybe a plan | | Your terms are long (60 or 90 days) | No: change the terms | | Your invoice is late or wrong | No: fix billing first |
Look at your own aged list before you build anything. If most of the overdue value is disputes, reminders will not move DSO much.
What do automated reminders change?
Three things shorten the tail.
- Consistency. Every overdue invoice gets the same schedule. Manual chasing depends on who has time that week.
- Speed. The first nudge goes out on day 3, not when someone reviews the aged list at month end.
- Specificity. Each message states the invoice number, amount, due date and payment details, and attaches the invoice. The customer's accounts team can act without a search.
The ladder is described in full, with templates, in invoice chasing agent: 3, 14 and 30 day reminders.
What else shortens DSO besides reminders?
Reminders are the last step in a chain. Upstream fixes often move DSO more.
- Invoice on time. Raise the invoice on the day of delivery or milestone. Every day of billing delay adds a day to DSO.
- Invoice correctly. Purchase order number, correct entity, correct amount. Errors create disputes.
- Send to the right person. Record the accounts-payable contact, not just the buyer.
- Make paying easy. Put bank details or a payment link on the invoice.
- State terms clearly. Due date in the document, not only in the contract.
- Match payments fast. An unmatched payment looks like an unpaid invoice and triggers a wrong reminder. See bank reconciliation with an AI agent.
How do you measure whether reminders worked?
Run it as a test, not a belief.
- Baseline. Record DSO and the aged-receivables split for the last three months.
- Define the group. Apply reminders to all new overdue invoices from a start date. Keep notes on anything else you change, such as terms or billing speed.
- Track weekly. Percentage of reminded invoices paid within 7 days of each step, and average days past due when paid.
- Compare after 90 days. DSO, days past due at payment, and value over 60 days.
- Check side effects. Customer complaints, replies that say "already paid", and invoices wrongly chased.
The side effects are a quality signal. Each "already paid" reply points to a matching delay or a data error. Fix the cause. Do not lengthen the ladder to hide it.
What should a person still do?
- Approve outgoing reminders, at least until the error rate is known.
- Call the top customers by value before step 2. A call often beats a third email.
- Resolve disputes. The agent routes them and stops chasing.
- Decide on credit holds, late fees and legal steps. These touch the relationship and the contract.
Outbound messages and money-related actions wait for a named person. See approval gates for high-risk agent actions.
Can a small business justify the build?
Work out the value from your own figures. If DSO falls by 5 days on S$150,000 of monthly credit sales, the cash released is about S$25,000 (150,000 ÷ 30 × 5). Whether that justifies a build depends on your cost of capital, your overdraft and how often cash tightness forces a decision. If your overdue list is short and your customers pay on time, the build does not pay back. A reminder spreadsheet and a calendar will do.
What does a before-and-after example look like?
Use illustrative numbers to see how the arithmetic works. A company invoices S$300,000 in a quarter of 90 days and holds S$110,000 in open receivables at the end. Its DSO is 110,000 divided by 300,000, times 90, which is 33 days.
Suppose reminders bring in S$15,000 of that balance about ten days earlier on average. The balance falls to S$95,000 and DSO falls to about 29 days. The cash did not change in total. It arrived sooner, and that is the whole benefit.
| Item (illustrative) | Before | After | |---|---|---| | Invoiced in quarter | S$300,000 | S$300,000 | | Open receivables at quarter end | S$110,000 | S$95,000 | | DSO | 33 days | about 29 days |
Check your own ledger first. If most late invoices are late because of disputes or missing purchase orders, reminders will move DSO very little. Fix the cause upstream, then add the ladder.
What should you do in the first month?
Start with measurement, not messages. In week one, export the open invoices with issue date, due date and customer. In week two, calculate DSO and list the ten customers with the oldest balances. In week three, agree the ladder, the hold list and the person who approves each reminder. In week four, send the first batch to a small group of customers and track the replies. Resist adding customer segments or tone variants in the first month. One ladder and one measure give you a clean before-and-after, and you can add refinements once the base result is clear.
Where KYN fits
KYN chases its own receivables at 3, 14 and 30 days, and the same pattern runs in client finance systems. Reminders are drafted from the ledger and wait for a named person. Every action is logged with the actor. Systems run in a cloud account in the client's name.
The first 14 days are a review of your stack and interviews with your team. A full build ships in under 90 days. See finance systems and cash flow forecasting from open invoices and bills.
Frequently asked questions
What is a good DSO?
It depends on your terms and sector. Compare your DSO with your own payment terms: if terms are 30 days and DSO is 45, the gap is 15 days of late payment. That gap is the number to reduce.
Will reminders upset customers?
Polite, specific reminders on a fixed schedule are normal business practice. Complaints come from chasing paid invoices or wrong amounts, which is why matching payments first matters.
How fast can DSO improve?
Expect the first effect within one to two billing cycles on late payers who forgot. Slower payers and disputes take longer and need a person.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
