Notice before the due date
Detail
A short call a few days before the invoice falls due. It is the most effective of all and the least awkward, because there is nothing to chase yet.
Accounts receivable
The overdue invoice nobody wants to call about
Chasing a payment is awkward, so it gets postponed and ends up happening late, when it costs twice as much. Elop makes the reminder on time, in a proper tone and with no personal wear, and records what each customer said and when they promised to pay.
- A notice before the due date, not weeks after
- The same tone on the tenth call as on the first
- Every payment promise recorded with a date
Why payment comes in late
It is almost never because the customer does not want to pay. It is that the call which would have solved it did not happen when it should.
It is a call nobody wants to make
Detail
Asking for money is uncomfortable. It slips one day, then another, and by the time it happens the invoice is six weeks overdue and the conversation is already tense.
A late call becomes a late payment.
The reminder goes out on the day it should, with nobody having to steel themselves.
Chased late and all at once
Detail
When somebody finally reviews the aged debt, twenty invoices get chased in one sitting. That is days of work done in an hour, in a hurry, so it is done badly.
Rushed chasing that damages the relationship.
A steady flow instead of one batch a quarter.
The tone changes with the day
Detail
The fifth chase of the morning does not sound like the first. The fatigue shows, and with a customer who was always going to pay it can cost far more than the invoice.
A commercial relationship damaged by one badly handled call.
The same correct tone on every call, always.
Promises nobody writes down
Detail
“I will pay you on Friday.” If that is not recorded somewhere, on Friday nobody checks, and two weeks later the conversation starts again from zero.
The same debt chased twice, and credibility lost.
Every promise dated and checked automatically.
Nobody knows why it is unpaid
Detail
An invoice unpaid because of a wrong address, a query on a line item or a service problem gets treated exactly like genuine non-payment. They are not the same thing.
An admin problem chased as if it were a bad debt.
The reason is captured and classified on the first call.
The volume does not fit the team
Detail
A small finance team can only chase the large invoices. All the mid-value aged debt goes uncalled — and in aggregate it is usually more money.
The mid-value queue never gets chased.
The whole aged ledger gets chased, not just the biggest items.
What Elop handles in collections
The reminder and the follow-up. Negotiating terms, write-offs and any decision about the commercial relationship stay with your team.
Overdue invoice reminder
Detail
Contact as soon as the due date passes, with the invoice number, amount and date, and the payment route that applies to that customer.
Agreeing a payment date
Detail
Captures the specific commitment — amount and day — and records it in the system, so the later follow-up starts from a fact rather than a memory.
Checking the promise
Detail
If the agreed date arrives and the payment is not showing, the follow-up call happens without anyone having to watch a calendar.
Identifying the reason
Detail
It distinguishes not having received the invoice, a query on a line item, a service problem and genuine payment difficulty. Each reason goes to a different place in your process.
Resending the invoice
Detail
When the problem is that they do not have it, the resend fires to the address the customer confirms during the call itself.
Updating contact details
Detail
A good share of old aged debt goes uncollected because the contact phone or email stopped being valid. The agent spots that and corrects it.
Immediate escalation to the team
Detail
A dispute over the amount, a request to pay in instalments, or a customer in difficulty goes to a person with the history captured. That kind of conversation is not for an automated agent.
What changes in collections
The indicators are the ones finance already tracks: days sales outstanding, aged debt by bucket, and the share of promises kept.
- Earlier
When the notice lands
The reminder arrives before the due date, not weeks after.
- All of it
Ledger chased
Mid-value aged debt stops going uncalled.
- Recorded
Every promise
Amount and date in the system, checkable afterwards.
- Consistent
Tone of the call
The relationship does not depend on the caller’s day.
With your accounts and your ERP
The agent has to know what has been paid before it dials. Calling someone who has already paid is the costliest mistake in this operation, and it is always a stale-data problem.
Sync payment status at the highest frequency your system allows. A daily refresh already prevents most calls to invoices that were paid yesterday.
Integrations- ERP and accounting software (API or webhook)
- Invoicing and payment status
- CRM, for the history of the commercial relationship
- Payment gateways and links, to send the payment route on the call
- SMS, WhatsApp Business and email for resending invoices
- Financial reporting tools
Hear a reminder call
Leave your number and take the call the way one of your customers would. Dispute the amount, say it never arrived, ask for another date.
- The call arrives within seconds.
- Talk normally: interrupt, ask, change the subject.
- No cost, no commitment, and the conversation is not recorded.
What a finance manager asks us
Here the questions are not technical — they are about the customer relationship and about limits.
Will it not upset customers I want to keep?
What upsets people is being chased late, in the wrong tone, or twice for the same thing. A prompt, correct reminder with the exact figure in front of it is usually received well, and often the customer is grateful because the invoice had been mislaid. You can also define customers or segments the agent never calls.
Can it negotiate an extension?
No, and that is deliberate. It captures the request and escalates it to your team. Any decision about terms, instalments or write-offs affects the relationship and the P&L: a person decides that.
How many times will it call?
As many as you define. The maximum number of attempts, the interval between them and the calling window are configured, and honoured without exception. Chasing without limit does not collect faster and does destroy the relationship.
What if a customer asks not to be called again?
It is recorded on the spot and honoured. The case moves to your team through whatever route you choose; the agent does not dial that number again.
Could it call someone who has already paid?
That is the real risk in this operation, and it depends on the integration rather than the agent. Which is why payment status is synced at the highest frequency your system allows and checked immediately before dialling. It is the first thing we verify in testing.
Does this replace a debt collection agency?
It is not the same thing and does not try to be. This is early-stage management: the window where a timely call stops an invoice reaching a recovery situation. Anything already with a third party or in legal proceedings carries on as it is.
Start with the notice before the due date
It is the easiest call to make, the one no customer takes badly, and the one that stops the most invoices going overdue at all. With that running, extending into aged debt is a small step.
Other solutions
