Automatic Overdue Invoice Reminders with Power Automate

Month end. You open the customer invoice list, you see the due dates that have slipped, and you ask the usual question: who do I chase, and in what tone? You do it every other Friday, when you find the time. As a result, some invoices sit six weeks before the first reminder goes out.

Chasing late means lending money for free. Chasing badly means annoying a good client over an oversight. A Power Automate flow can chase on your behalf, with your rules and your tone, and leave you only the cases that genuinely need a phone call.

The payment schedule: the basis of any automatic overdue invoice reminder

The flow needs one thing: a reliable list of invoices with number, client, billing contact, amount, due date, status, payment date and a link to the PDF. That list comes from your invoicing software, through a connector or a daily export, or lives in a SharePoint list if you still invoice from Word or Excel.

Every morning, a scheduled trigger starts the flow. It works out how late each unpaid invoice is, checks which reminder step has already been reached, and decides whether to send anything today. The vital point: payments must be up to date before the run. Schedule the flow after the bank import, never before.

A reminder sequence with a rising tone

1. Day 3: the courteous nudge. "Perhaps an oversight on our side or yours", invoice attached, bank details, no threats.
2. Day 10: the firm reminder. Restate the payment terms, ask for a payment date, offer a call if there is any disagreement about the invoice.
3. Day 20: the final notice before formal demand. Copy to the managing director, mention of the late payment penalties in your terms and conditions, a precise deadline to respond.

After the third step, the flow stops sending emails and creates a task for a human: a phone call. At that point one more email adds nothing; a voice does. Each email template lives in a "Templates" list with its variables (name, number, amount, due date). You change the wording without touching the flow.

The exclusions that prevent the mistake that costs a client

A flow that chases everyone the same way will do something stupid in its first week. Plan a "Do not chase" field with a reason and an end date, which the flow checks before every send. The usual cases: an open dispute on the invoice, a credit note in progress, a negotiated payment plan, a key account that imposes its own supplier portal, and the client the managing director has said "leave that one to me" about.

Second safeguard: grouping. A client with three overdue invoices receives one email listing all three, not three emails the same morning. That is the difference between a professional reminder and harassment.

Sending from the company mailbox and keeping the record

The email goes out from a shared mailbox, accounts or billing, using the Outlook action built for that. Replies land in the right place, and sending does not depend on the inbox of someone on holiday. The invoice number sits in the subject line, the payment link or bank details in the body.

Every send is logged in the list: date, step, recipient. The invoice status moves to "Reminder 1 sent", then "Reminder 2", and so on. On Monday morning the managing director receives a summary: overdue total, the five most exposed clients, invoices that have reached the final step. Plus an immediate alert when a client passes a cumulative amount you set.

The classic mistakes and how the flow avoids them

• Chasing a client who has paid. The most expensive one for your image. The flow checks the payment date right before sending, and when in doubt (no bank import that morning), it sends nothing and tells you.
• The missing attachment. A reminder without the invoice triggers a "which invoice?" and loses three days. The flow checks that the PDF exists; otherwise it alerts and does not send.
• The wrong recipient. The reminder goes to the billing contact, not the salesperson who signed the deal. That is a dedicated field, filled in when the client is created.
• The wrong day. A reminder received on Saturday morning irritates. The flow shifts it to the next working day.

This is one of the flows where the gain shows fast: average days to payment drop, and you stop spending Fridays sorting due dates. It belongs among the automations to set up first. If your invoicing lives in a tool without a connector, a short scoping settles the choice between a daily export and a shared list, and the build is then delivered at a fixed price set during scoping.