Overdue Customers Could Still Order, Until the System Said No

Old invoices were overdue, yet new orders were still accepted and delivered because collections had not been connected to the decision to fulfil the next order.

Illustration of mounting invoices becoming monitoring and a sequence of actions to stop orders. — Collections information is connected to action on the next order.

Conceptual illustration. The case is real; company details are disguised.

In 2024, collections from business customers and order acceptance followed separate paths. A delivery produced a valid invoice, then the next order was processed again. When earlier invoices remained unpaid past their deadlines, orders continued to flow. Unpaid amounts grew with each new delivery to the same customer.

Monitoring was separate too. Some reports were opened in the operational system, others in the accounting application. Getting a complete picture of collections meant checking both. No reminder arrived on its own with a status summary. The process depended on manual checks while new orders continued to arrive every day.

Illustration of separate collection records while customer deliveries continue. — New orders keep moving when earlier invoices are already overdue.

As head of the IT Division, I worked with the team to build a collections report connecting summaries to invoice details. It came into use in October 2024. Invoice statuses were brought into one operational report, giving follow-up a shared set of details. Reading the report was then connected to procedures for reminders, warning letters, and stopping orders.

The decision to stop orders remained with Management because it affected trading relationships with customers. Finance AR, the team responsible for receivables and collections, implemented that decision by changing customer account statuses in the system. The system supplied information and enforced restrictions, while people retained responsibility for considering the customer relationship.

The report implemented in 2024–2025 presented collection status, sales channel, customer group, and the staff member responsible for collections. Users could trace summary figures to the invoices behind them. These views helped direct follow-up to the right customer and person responsible. Receivables lists gained a clear connection to the collection work that needed to happen.

Illustration of customer invoices accumulating with repeated deliveries. — Invoices are recorded individually, but overdue balances need to be read alongside continuing orders.

During the same phase, collection status summaries were sent automatically to the Finance WhatsApp group. Messages brought invoice statuses into the place where work was coordinated. They showed items awaiting confirmation, ready for collection, and still unpaid. Details remained in the operational system whenever a status needed closer examination.

Action on overdue invoices followed stages. Customers received written reminders about invoices past their due dates. If reminders had not been acted on, Finance AR issued a warning letter listing invoices, due dates, and amounts. It also explained that orders might be stopped and opened discussion about payment arrangements, giving follow-up a clear basis.

These written stages made room to discuss payment before ordering was suspended. Stopping orders had consequences for customers and sales, so warnings needed to be clear. The invoices and deadlines in the letter provided a basis for discussions with customers and for deciding what came next when reminders had not resolved the overdue balance.

If payment still had not arrived, Management decided to deactivate the account and Finance AR carried out the decision. Inactive accounts stopped accepting orders until payment was received. Reactivation also followed Management’s decision. Collections thus had a real operational consequence for the next order, alongside a clear route for resuming the trading relationship.

By September 2026, warning procedures and account status changes were still in use. Warning letters that month listed overdue invoices, while customer account statuses were handled through the system. The main change lay in how processes connected: collection results informed whether the next order would be served, so adding invoices was linked to resolving overdue balances.

Illustration of reminders, warning letters, and account deactivation following human decisions. — Finance AR carries out Management’s decisions through warning stages and account status changes.

At that point, reports were being moved to a new tool, monitoring temporarily used the accounting application, and automated messages had been switched off after being judged too frequent. Written procedures provided a reference for continuing customer follow-up as the working tools changed.

This experience taught me that information about overdue balances needs to lead to action. Receivables lists help start the review, but the decision to serve the next order connects them to everyday business risk. A system becomes useful when someone owns that decision, the stages are understood, and the consequences are carried through on customer accounts.