As of 13 August 2026, AI can only partly send invoice reminders automatically.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Hand it to a person

   Second choice

   A person who owns the outcome does this end to end, worth it when the failure is dear.

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open your invoicing or accounting system and email platform, then write down their names, available integrations, invoice-status fields, due-date fields and the authorised account that may send messages.
   2. Gather your written reminder policy, including when reminders may be sent, which invoices must be excluded, when reminders stop, the sender address, the reply-to address and the payment link format.
   3. Paste the prompt and those details into an AI assistant, then ask it to produce the workflow, required fields, message drafts, failure cases and test plan without claiming unconfirmed integrations.
   4. Open the recommended integration or agent platform, connect only the required accounts and ask it to implement the documented workflow, using a test email address and sample invoice records.
   5. Create sample records for paid, unpaid, overdue, disputed, part-paid and missing-email invoices, then run each test in the plan and compare the results with the expected outcomes.
   6. Inspect the draft emails, recipient addresses, invoice amounts, payment links, exclusions and stopping conditions against your accounting records and reminder policy before activation.
   7. Activate the workflow with sending disabled or approval required, observe the first test run in the logs, and enable automatic sending only after the recipients and messages are correct.

   Prompt

   Design an automatic invoice-reminder workflow for a UK business. Use the information below and do not invent any system capability, field, date, customer detail or legal requirement.
   
   Business and systems:
   - Invoicing or accounting system: [name]
   - Email or messaging system: [name]
   - Available integrations or API access: [details]
   - Time zone: Europe/London
   
   Reminder policy:
   - Send reminders at these stages: [for example, a few days before the due date, on the due date, and after the due date]
   - Do not send reminders when: [disputed, paid, part-paid, on an agreed payment plan, or other conditions]
   - Stop sending reminders after: [condition]
   - Sender name and reply-to address: [details]
   - Tone: plain, polite and firm
   
   Required output:
   1. Describe the workflow in numbered steps.
   2. List the exact fields and permissions required from each system.
   3. Give the trigger and stopping conditions in a table.
   4. Draft the reminder messages with placeholders for invoice number, amount, due date, payment link and contact details.
   5. List failure cases, including duplicate sends, missing email addresses, credit notes, disputed invoices, part-payments and changes to due dates.
   6. Give a test plan using sample invoices only, including the expected result for each test.
   7. Explain which actions need my approval before activation.
   
   Do not send anything, access any system or claim that an integration exists. Mark any point that requires confirmation from the software documentation or an accounts professional.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.