Automated Payment Reminders: Timing and Stop Rules Source: https://www.getinvoiceagent.com/invoicing/automated-payment-reminders Reviewed: 2026-09-07 | Owner: InvoiceAgent editorial team Illustrative example; adapt to your agreement. Not a record of a real client invoice. InvoiceAgent example: an invoice due September 14 1. September 14: payment is due Example: a sent $1,500 service invoice is due September 14, 2026. With the default three-day first delay, no automatic reminder is created for September 14 itself. Check any payment received and record it before the overdue sequence. These are calendar-day examples, not a recommended policy for every client. 2. September 17: first overdue reminder If the invoice is still marked Sent and follow-up is enabled and unpaused, the first reminder becomes due three days after the payment deadline. If the client reports a dispute or a promised payment date, pause follow-up and handle that conversation before another automated message is sent. 3. September 21: final automated reminder The final stage is four days after the first, making it seven days after the due date in this example. Changing the first delay to five days moves the stages to September 19 and September 23. These intervals do not skip weekends. After the last stage, review the account manually; final means the last automated stage, not an automatic legal escalation. YOUR BILLING REVIEW Client: ____________________ Invoice/reference: ____________________ Reviewer: __________________ Review date: _________________________ Send date/time: ____________ Due date: ____________________________ Amount/currency: ___________ Next action/owner: ____________________ [ ] Agreed due date entered; fallback to send date avoided where inappropriate [ ] First overdue delay selected [ ] Final stage calculated as first delay plus four days [ ] Calendar dates and send hour reviewed, including weekends [ ] Payment checked and paid status updated when confirmed [ ] Disputes assigned to an owner and follow-up paused [ ] Payment promises given a manual review date [ ] Already-due stages reviewed before resuming [ ] Account assigned a manual next action after the final stage EXCEPTIONS AND LIMITS Payment has arrived outside the app Confirm the payment using your bank or chosen payment method and mark the invoice paid. InvoiceAgent cancels pending follow-ups when it is marked paid. The app does not automatically reconcile every external payment, so leaving the invoice marked Sent can cause an unnecessary reminder. The client disputes the charge Pause follow-up and resolve the specific issue: missing approval, incorrect amount, wrong entity, or unclear scope. Keep the conversation with a named owner. A scheduled reminder cannot decide whether the invoice is correct or whether the dispute is resolved. A promised date changes the context Pause while reviewing a credible payment commitment and record the next manual check in your own process. Before resuming, inspect the reminder schedule: an already-due pending stage can become eligible immediately. Resume does not automatically move the sequence to a newly promised date. RELATED RESOURCES Plan a reminder cadence and compare its assumptions: https://www.getinvoiceagent.com/tools/invoice-reminder-schedule-planner Evaluate InvoiceAgent's payment reminder workflow: https://www.getinvoiceagent.com/automated-payment-reminders Calculate the deadline before planning reminders: https://www.getinvoiceagent.com/tools/invoice-due-date-calculator Keep recurring sends separate from payment follow-up: https://www.getinvoiceagent.com/features/recurring-invoice-runs