Payment Reminders Invoices

Ship this workflow

Pick how you want to build it.

Try it in the dashboard Fastest Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow. Try it
Build with the SuprSend Agent Try the agent
Build with SuprSend MCP Set up MCP

When to use this workflow

    Invoices sent once go unpaid. With no follow-up, the customer misses the due date and the invoice sits open.

    Customers forget a due date until it has passed. A nudge only after the invoice is overdue arrives too late to keep them on time.

    One overdue notice rarely gets a late payer to act. Without escalating follow-ups, the invoice stays unpaid.

    Reminders keep chasing an invoice that is already paid. A customer who paid still gets "your invoice is overdue".

How it works

1

Invoice sent

When an invoice is created (INVOICE_CREATED), the customer gets it by email.

TriggerEmail
2

Reminder before the due date

Three days before the due date, a reminder goes out if the invoice is unpaid.

Wait UntilSmart Channel Routing
3

Overdue notice

Three days after the due date, an overdue notice follows if it is still unpaid.

Wait UntilSmart Channel Routing
4

Final overdue notice

About two weeks after the due date, a final notice goes out.

Wait UntilSmart Channel Routing
5

Paying ends it

Paying (PAYMENT_SUCCEEDED) at any point stops the remaining reminders.

Wait UntilExit

Best practices

    Send an invoice the customer can pay right away

    The first email should carry the amount, the due date, and a pay link, not just say an invoice exists. A customer who is ready then pays without waiting for a reminder.

    Reserve SMS and push for the overdue notices

    The invoice goes by email, where it belongs. Once it is overdue, Smart Channel Routing adds SMS and push to reach a customer who is ignoring email; do not text someone the day the invoice is raised.

    Check the balance with a Fetch when partial payments are allowed

    A customer can pay part of an invoice and still owe the rest. Add a Fetch to pull the current amount due before each reminder, so the message shows what is still owed and the reminders stop only once it is fully paid.

Common mistakes to avoid

    Sending overdue notices that just say "please pay"

    An overdue notice with no real consequence is easy to ignore. State what happens if the invoice stays unpaid, like a late fee or a service hold, so the follow-ups carry weight.

    Letting the reminders run on after the due date is extended

    If you give a customer more time, the reminders still fire on the original due date. Re-issue the invoice with the new date, or they get "overdue" notices for a date you moved.

    Sending the invoice to someone who cannot pay it

    In a business, the contact who receives the invoice is often not the one who pays it. Add the person who settles the bill, like accounts payable, to the email CC so it reaches them too.

What users receive

The actual notifications this workflow sends, on each channel.

Payment Due Soon

Email
Payment Due Soon — Email
SMS
Payment Due Soon — SMS
In-app inbox
Payment Due Soon — In-app inbox

What good looks like

Primary signal On-time

More invoices paid on time

More invoices are paid by the due date once the reminders are running, compared with sending the invoice alone.

Fatigue signal Complaints

Frustration from over-chasing

When customers who already paid still get overdue notices, the reminders are not stopping on payment as they should.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

Yes. A successful payment (PAYMENT_SUCCEEDED) for that invoice stops every remaining reminder at once, matched on invoice_id.

Both. Each invoice starts its own run on INVOICE_CREATED, so a monthly subscription invoice and a one-off invoice are each reminded, and stopped, on their own payment.

No. The workflow sends reminders only. A late fee and a receipt are handled by your billing system; you can add a receipt by sending a confirmation on the payment branch.

The invoice is sent by email. The reminders use Smart Channel Routing across email, in-app inbox, SMS, and mobile push, one at a time until the customer sees it.

Trigger a payload shaped like INVOICE_CREATED with an invoice_id and a due_date, then fire PAYMENT_SUCCEEDED with the same invoice_id to confirm the reminders stop. You can do this from the Test button in the workflow editor, by asking the SuprSend Agent in the dashboard, or through the API, CLI, or MCP.

Ship Payment Reminders Invoices in under 5 minutes.

Build with the SuprSend Agent

Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.

Try the agent

Build it with SuprSend MCP

Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.

Set up MCP