Collections tracking: how an overdue receivable becomes visible

Example scenario: Picture a machine spare parts supplier in Ostim, Ankara. Most of its customers buy on credit terms. One factory pays half the invoice and says the rest will come next month. Another says a line arrived short and holds the payment. A third pays by cheque, with a due date further out. All of them are open receivables, but each needs a different kind of follow-up.

• Due date: when the invoice has to be paid.
• Partial payment: the amount received and the balance left, under the same invoice.
• Promise to pay: the date the customer gave and whom they gave it to.
• Dispute: the item holding up payment and why.
• Cheques and notes: their due dates and whether they have cleared.

When each of these items is kept somewhere different, tracking turns into collecting pieces. The due date is in accounting's spreadsheet, the promise to pay in the salesperson's notebook, the dispute in an email thread. The first job of tracking is to bring them together under the same invoice.

In most businesses the receivables list is a spreadsheet updated once a week. It is correct on the day it is updated and starts going stale the next. A payment received, a promise made, or a dispute raised in between only gets in at the next update. And when the person who updates it goes on leave, the updates wait with them.

Then there is silence. The customer does not dispute the invoice, and does not pay it either. It is past due, but nobody has called, because everyone assumes someone else has. Sales sees it as accounting's job, accounting sees the customer relationship as sales' job. The receivable caught in between quietly gets older.

The real problem is on the sales side. The salesperson discusses new work with the customer without knowing the open balance, sends a new quote, and the customer moves on to a new order without the old debt ever coming up. When accounting calls, it does not know the customer complained to the salesperson last week, and the conversation starts from the wrong place.

An ageing table splits receivables into bands such as not yet due, recently overdue, and long overdue. Even if the total stays the same, the distribution says a lot. If most of it is not yet due, things are on track; if the long-overdue band is growing, a customer or a process is causing trouble.

The table can be read by customer too. If every invoice from the same customer runs slightly past its due date, that is a habit and needs a conversation. If a single large invoice has been open for a long time, there is usually a dispute behind it, and no reminder will work until the dispute is resolved.

It helps to make ageing a weekly habit. The same person looks at the table on the same day and writes the next step for every row in the long-overdue band: a call, a reconciliation, resolving a dispute, or escalating to a manager. That turns the table from a report into a to-do list.

A reminder is there to protect the relationship as much as to collect the money. A short note before the due date gives the customer's accounts team the chance to put the invoice on their payment run. The message after the due date should leave nothing vague. The tone stays the same at every stage: informative, not accusatory.

• Which invoice: its number and date.
• How much: the open amount, or the remainder if part has been paid.
• When: the due date.
• How: the payment method and account details.
• Whom to contact: the person to ask or raise a dispute with.

If the customer gives a date, that date goes on the record and is checked on the day. If the promise stays in a salesperson's head, the next reminder opens with the same question and the customer has to repeat themselves.

The channel for the reminder matters too. With a corporate customer, email leaves a trace and goes straight to the accounts team; with a small business, a phone call to the owner may work faster. Whatever the channel, a summary of the conversation goes on the customer's record. How collection starts on small service invoices is covered in collections at a service business.

At the same Ostim supplier, the salesperson is preparing a new quote for the factory on Monday morning. On the customer card there is an open invoice and last week's dispute note. Before sending the quote, the salesperson talks the dispute through with accounting and sends the customer the fix for the missing line along with the new quote. The collection gets resolved inside a sales conversation.

Meeting in the middle needs a shared language. Sales should see the open balance not as an obstacle but as a topic to raise with the customer, and accounting should know about the work in progress with the customer before calling. Two teams looking at the same card do not approach the same customer in two different tones.

So when you choose collections tracking software, look past the due-date list and check whether that list sits in the same place as the customer record. You can see how sales and accounting look at the same card on the accounting and HR page.

In Corex360 the contract sales had signed sits in the Contracts tab of the customer card, and the invoice is issued in the Accounting module of the same core. Email from the customer is read by X AI and filed on the right card, so a payment notice and a dispute sit in the same history. We describe how contracts and quotes sit on the customer card on the CRM module page.