Multiple overdue invoices for one customer: keep each balance clear

Build a current list before contacting accounts

List each invoice number, agreed due date and current outstanding amount from the records you actually use. Include the customer reference where it helps accounts match the work. Check recent payments, corrections and correspondence before copying a total into a message. A list assembled last week may no longer reflect the position you are asking the customer to confirm.

Keep status alongside each row. One invoice may be awaiting a reference, another may be disputed and a third may simply need a payment date. A single “customer overdue” label hides those differences. Also confirm that the invoices belong to the same customer and currency before presenting any combined amount. If those details differ, state them separately and avoid an ambiguous total.

Coordinate contact without merging responsibilities

Review the messages already scheduled or prepared for that customer. If several would arrive together asking for a status update, decide whether one deliberate personal contact would make the request clearer. Record which invoices it covers and pause overlapping routine messages while you await the response. This is a business process choice, not a promise that your reminder software provides grouped-invoice messaging.

Where you contact accounts about several invoices, identify each reference and ask for the status of each one. You can use a short list in your normal business email. Make the request easy to answer, such as confirming which invoices are approved and their expected payment dates. Do not turn a summary into a replacement invoice or silently change the original terms.

Match replies and payments to specific invoices

A reply saying “payment is being processed” may be unclear when three invoices are open. Ask which references it covers and what date is expected. Record the answer separately for each invoice. If the customer identifies a query on one item, pause that item's routine reminders while investigating it; do not assume they have disputed or accepted the others.

Likewise, check how a received amount is allocated through your normal accounting records. A transfer with a vague reference does not tell you which invoice should be marked paid. Establish that match before updating statuses. If part-payment leaves a balance, record the remaining amount accurately and make any later request consistent with it. Keep the explanation with the relevant invoice.

A worked example with three different next actions

A fictional supplier reviews three overdue GBP invoices for one customer. Original amounts were £300, £450 and £600. The owner has matched a £300 payment to SU-101 and a £200 part-payment to SU-103 in their normal records. Accounts requests a purchase order for SU-102 and gives a planned date for the rest of SU-103.

The outstanding total is £850: £1,350 invoiced less £500 matched. That total is not a reason to send one identical chase for every row. A personal reply can ask for the PO on SU-102 and confirm the promised date relates to the £400 on SU-103, while leaving SU-101 out of the payment request. This ledger is an owner worksheet outside PayerPing, not a grouped-message feature.

Check for overlapping follow-up work

• Does every amount match the current invoice record?
• Can accounts identify each invoice and customer reference?
• Does each reply have a clear invoice or set of invoices attached to it?
• Have you checked scheduled reminders as well as personally drafted messages?
• Does every invoice have its own next action or stopping decision?

Review the list after each useful response. Coordinating contact does not mean treating every invoice identically. A clear record of separate balances and decisions lets you have one coherent customer conversation while preventing a paid or queried invoice from remaining in an unrelated routine chase.