An overdue-invoice view people can act on

A balance is not a follow-up plan

Most businesses already have a place where invoices are created. The gap appears after an invoice becomes overdue. One employee sends a reminder, another speaks to the customer, and a promised payment date is written in an email or notebook. The ledger still shows an amount, but it cannot explain the latest conversation or the next sensible action.

That distinction matters. A useful collection view should not pretend to replace the accounting source of truth. It should help people coordinate the work around that source: reminders, promises, disputes, and escalation.

Build an action layer, not another ledger

A small first version could read or receive a list of open invoices and group them into ageing bands. Each invoice would show the responsible person, last contact, customer response, promised date, and next reminder. A daily queue could surface accounts requiring attention without sending anything automatically until wording and approval rules are agreed.

• Keep the invoice number and balance tied to the accounting record.
• Separate disputed invoices from ordinary late payment.
• Record promises and next actions with dates and owners.

Protect the relationship and the record

Reminder frequency and tone should match the business, customer type, and local requirements. The first version can begin with drafts for staff review instead of automatic sending. It also needs a clear rule for marking an invoice paid, written off, or under dispute. The goal is not to pressure every customer identically. It is to make the current state visible so staff can follow up consistently and stop duplicate or contradictory messages.