RECUPO OS

Unpaid invoices are a quiet, persistent issue in many companies. Somewhere there is a list of receivables, maintained alongside the day-to-day business, and no one knows off-hand which reminder went to whom, and when. Incoming payments have to be matched against open items by hand, follow-ups slip out of mind, and if a case does end up in court, the hunt for evidence begins: when was the delivery, when the reminder, what was agreed? Anyone who handles receivables knows this piecing-together from email inboxes, filing folders and accounting software — and knows how much time it costs. Yet the work itself is clearly regulated; it is the administration around it that eats up the day.

The problem has grown; nobody chose it. The invoice is created in the accounting software, the reminder as a text template in the word processor, the correspondence sits in the case handler's inbox, the payment appears on the bank statement. Four places for a single case — and none of them shows the case as a whole. The more receivables there are, the more working time flows into gathering information instead of into the actual processing.

A system for receivables management would have to run each case as one continuous process: from the open invoice through the individual reminder stages to the incoming payment. Reminder runs should follow fixed, predefined rules instead of depending on whether someone remembers in time. A payment link in the reminder would make it easy for the recipient to pay straight away, and the incoming payment would be assigned to the right case automatically — no retyping, no searching. If the recipient does not pay, the next step would already be set, and whoever opens the case would see at a glance where it stands: which stage has been reached, what has been sent, what comes next.

What matters most here is documentation. Every step — every reminder sent, every deadline set, every incoming payment — should be recorded with a timestamp, so that an unbroken chain of evidence emerges that can be relied on later. Data protection is just as important: receivables data always concerns people too, and the General Data Protection Regulation (GDPR) sets the framework for it. RECUPO OS is therefore planned with a data held in the EU, and the data belongs to the company that brings it in — not to the software provider.

RECUPO OS is in development and not yet in use with any customer. The planned approach: a documented process from the first reminder to the incoming payment, with automated reminder runs, a payment link and a case file in which every step remains traceable. The technology is deliberately open, with no lock-in to any particular provider, so a company could take its data with it at any time. If you would like to know how far development has come, get in touch — we will say openly what is in place and what is still missing.