How do you track and follow up on unpaid invoices?

Build the working list from the payment record

Choose the invoicing or accounting system that decides whether an invoice is draft, sent, partially paid, paid, overdue, disputed, or written off. An inbox or spreadsheet can display work that needs attention, but it should not create a competing version of payment status.

A useful queue shows the invoice number, customer, amount, due date, current balance, last contact, and next action. Payments received by check, bank transfer, or another route must be reconciled before a message is prepared. Otherwise the system can efficiently chase someone who has already paid.

Choose a cadence that matches your terms

Write the sequence before turning it on. A service company might send a receipt confirmation when the invoice is issued, a short reminder near the agreed due date, and a firmer message only after the invoice becomes overdue. The appropriate timing depends on the contract, customer relationship, and normal billing cycle.

Every message should identify the invoice, balance, due date, and a valid way to pay or ask a question. Avoid vague notes about an outstanding account. If late fees or collection steps are part of the process, keep them consistent with the written agreement and applicable rules.

Treat replies as state changes

A dispute, partial payment, promised payment date, returned message, or request for a copy is not another silent invoice. It changes the next action. Pause the ordinary sequence and assign the case to someone who can answer it.

Keep a dated history of messages and decisions. That history gives the customer a coherent conversation and helps the business distinguish a one-time delay from an account that repeatedly needs different terms.

Test the cases that create embarrassing reminders

Before launch, use made-up records to test a full payment, partial payment, duplicate invoice, changed due date, bounced email, dispute, and payment that arrives while a reminder is waiting to send. Confirm that the final escalation requires the level of approval your business expects.

• Can someone see every invoice requiring action today?
• Does payment stop the next message before it leaves?
• Do failures and replies reach a monitored queue?
• Can staff explain why a particular reminder was sent?