Promises to pay and payment plans that actually work

"We'll pay next week." Every business that sells on credit hears it, and every collector knows how often next week becomes next month. A promise to pay is one of the most useful tools in collections, but only if it is recorded, checked on the day, and followed up when it is broken. Otherwise it is just a polite way to end a phone call.

Payment plans are the same. Splitting a large overdue balance into instalments can recover money that would otherwise turn into a write-off, but a plan nobody tracks quietly becomes a second, longer overdue balance.

Our earlier post, getting paid on time without becoming the bad guy, covers the habits that prevent late payment. This one is about what to do once an invoice is already late: how to take a promise that sticks, how to react when one is missed, and how to run payment plans that end with the money in the bank.

What makes a promise real

A vague promise ("we'll sort it soon") is not a promise. A real one has four parts:

An amount. The full balance, or a specific part of it.
A date. A day, not "end of the month" or "after our customer pays us".
Which invoices. Especially when a customer has several open, so the payment is applied where you both expect.
How it was made. On a call, by WhatsApp, by e-mail or in your customer portal, and by whom.

When a customer offers something vague, ask the two questions that turn it into a promise: "How much can you pay?" and "On which day?" Then repeat it back: "So that is 5,000 against invoices 1042 and 1051, by Thursday the 16th." Most people keep promises they said out loud and heard repeated.

Hold the reminders while a promise stands

Once a customer has promised, stop sending automatic reminders for those invoices until the day. A reminder that arrives the morning after a friendly call undoes the call. But do not stop thinking about it: the promise needs a check on its day, plus a few grace days for the transfer to arrive.

The day after: kept, partly kept or missed

When the date and the grace days have passed, there are only three outcomes:

Kept: the payments since the promise reach the promised amount. Thank the customer briefly. A short "received, thank you" builds the relationship that makes the next promise reliable.
Partly kept: some money arrived, not all. Acknowledge what came in and ask for a new date for the rest, right away.
Missed: nothing arrived. Contact the customer the same day, calmly and directly: "We agreed Thursday and nothing has arrived. What happened?" Then get a new, smaller and nearer promise, or move to a payment plan.

The worst reaction to a missed promise is no reaction. If nothing happens, the customer learns that your dates are suggestions. Track the share of promises kept per customer; a customer who breaks three in a row needs a different approach, such as payment before further deliveries.

When to offer a payment plan

A payment plan makes sense when the customer genuinely cannot pay the whole balance now but can pay steadily, and when you want to keep them as a customer. It is usually the wrong tool when the customer can pay and is simply choosing not to, or when the debt is disputed. A dispute needs resolving first; a plan on top of a disputed amount just delays the argument.

Before you agree, check:

The total the plan covers: all overdue invoices, or only some.
What the customer can really pay each week or month, based on what they tell you and what they have paid before.
What happens to new orders while the plan runs: cash only, a reduced credit limit, or business as usual.

How to set up a plan that works

Keep it short. A few months is easier to keep than two years. The longer a plan, the more likely something changes.

Make the instalments equal and regular, every week or every month, on a day that suits the customer's cash flow, such as the day after they pay salaries or receive their own big customer payments.

Ask for something up front when the balance is large. A first payment on the day you agree shows commitment.

Apply payments oldest first. Whatever way money arrives, it should pay the oldest instalment first, so the plan is never "a bit behind" in confusing ways.

Agree what breaks the plan. For example: an instalment more than five days late. When that happens, the plan ends, normal reminders resume and the case is escalated. Say this when you agree the plan, not when it breaks.

Put it in writing, with the schedule, and send it to the customer.

Remind for each instalment

A plan needs its own reminders: a friendly note a few days before each instalment is due, not the general overdue reminders for the original invoices. When an instalment is paid, say thanks. When one is late, call the same day.

Measure what matters

Three numbers tell you whether your promises and plans are working:

Promises kept, as a share of promises made, overall and per collector.
Plans completed compared with plans broken.
Days sales outstanding (DSO), which should come down as promises and plans bring money in sooner.

If promises are rarely kept, the way you take them needs work. If plans often break, they are too long or too large.

How to do it in Kluvan

Collections turns what customers owe on your Books invoices into a daily worklist of cases, with promises, payment plans, disputes, reminders and payments on one page. Kluvan runs online with nothing to install, so collectors can work the list from a laptop or a phone.

Work the case queue. The overview shows total owed, overdue, disputed, the ageing and key figures such as DSO and promises kept; My collections today lists the cases to work now. See work the case queue.
Record a promise. On the customer's case, tick the invoices (or none, to take the oldest first), enter the amount, the day and how it was made: phone call, WhatsApp, e-mail or customer portal. Reminders pause while it waits. After the grace days you set, Kluvan marks it kept, partly kept or missed, and a missed promise appears on Today and as an owner alert. See record a promise to pay on a case.
Make a payment plan. Split chosen overdue invoices, or all of a customer's overdue invoices, into 2 to 60 instalments every week or month. Reminders for those invoices stop and each instalment gets its own. Payments pay the oldest instalment first; an instalment unpaid after the grace days breaks the plan, moves the case to Escalated and restarts normal reminders. No interest or fees are added. See put overdue invoices on a payment plan.
Keep disputes apart. A disputed amount is not chased while the dispute is open; close it with a credit note, a redelivery, a rejection or a write-off. See open and resolve a dispute.
Reminders. Reminder sequences go out by e-mail and respect quiet hours. WhatsApp reminders wait in a list where a collector opens each message and sends it from their own WhatsApp with one tap.
Promises from the portal. In the Customer portal, a payer can promise a payment date on an invoice; it lands on their case like one taken on the phone.
Payment links. A link for all or part of what a customer owes, paid through your Paymob account and booked as a Books receipt, is in early access today.
Reports. What was collected and how, DSO, promises kept, payments after reminders, write-offs, collectors and dispute reasons. See read the Collections reports.

Collections needs Books. It is sold on its own and comes with the Service Business and Trade Business bundles and Kluvan One; see pricing.

Customers keep promises more often when paying is easy. Our post on a customer portal for invoices, quotes and payments shows how to give them one place to see what they owe and pay it.

This week, take every promise with an amount, a day and the invoices, and check each one on its day. That habit alone changes how customers treat your dates.