Many cashbook programmes allow you to import statements direct from your bank's web site, keeping the time you spend on administration to the minimum.
The second reminder email should be sent as a FORWARD so it can use the K.I.S.S. principle (Keep It Short and Simple). It doesn’t need to repeat details of the overdue invoice as those can be seen in the first one.
By doing this, it serves two purposes. It reminds the debtor
1: of the overdue account and
2: that he or she has been reminded before.
The wording used is still deliberately “soft”:
- “hope to”…. instead of “will”
- “help you with” …. Instead of “contact me”.
Such a gentle approach is less “threatening” to debtors and as a result, more debtors will contact the creditor if they do have any queries or disputes.
Wording for a SECOND Reminder Email:
|
From: accounts Dear Sir or Madam, The amount below was for a December invoice. Please advise when you hope to be forwarding this balance or Regards, ________________________________________ Dear Sir or Madam, Invoice for: Your Debtor Pty Ltd According to our records, the above amount appears to be outstanding. If payment has been made, thank you. Please contact me if you have any queries or if I can be of any assistance. Kind Regards, |
In our experience, these are the results that can be expected using this two-tier email reminder process:-
•About one third (33%) of debtors that receive First Email Reminder will respond. Some pay, some make a part-payment, some dispute, some ask for an invoice copy but they respond.
•About half (50%) of debtors that are sent an Second Email Reminder will respond to this second reminder.
In other words, if there were 100 overdue accounts.
33 would respond after receiving the First Email Reminder.
33 (50% of the remaining 67) will respond after the second.
Leaving only 34 debtors who have not responded at all.
And all done using non-confrontational wording and at low cost. But the “trick”, as always is to Start Early.
You will find an article on how to word the first reminder here.
Comments
Post new comment