Unpaid invoices are an interest-free loan to your customers — and chasing them manually is nobody's favorite job. This template is your automated accounts-receivable assistant, running every morning: Daily 8AM AR Check fires, List Open Invoices pulls all unpaid invoices from Stripe, and Compute Days Overdue calculates how overdue each one is, skipping invoices not due yet and flagging whether today is reminder day 1, 7, or 14. The workflow syncs everything into your AR sheet — new invoices appended with status UNPAID, existing rows refreshed — then sends reminders: a friendly nudge on day 1, a firm "payment overdue" on day 7, a final notice on day 14, each with invoice number, amount, and pay link, flipping rows to REMINDER_SENT_DAY_1 / _DAY_7 / _DAY_14. Invoices 14+ days overdue escalate to your Slack channel, the sheet flips to ESCALATED, and Telegram — Send AR Summary gives you the morning brief: total outstanding, oldest overdue invoice, reminders sent, escalations today.
Freelancer or small agency with 20–40 open invoices
A designer or dev shop billing $5k–$50k a month usually has a handful of invoices quietly aging past 30 days. Fill in CONFIG — AR (business name, sender name, reminder days, escalation channel) once, and the morning run handles the rest: the day-1 nudge goes out in your name with your sign-off, day-7 firms up the tone, day-14 is the final notice — all from the templates in Build Reminder Email, which you can tune to your voice or add your logo signature to. You only ever see the exceptions: the Slack escalation for 14-day laggards and the Telegram summary. Practical tip: most late payers pay at day 1 or day 7 — the automation captures that money without the awkward "just bumping this" email you were avoiding.
SaaS company with manual or annual invoices
Stripe handles the subscriptions, but enterprise annuals and setup fees are manual invoices that age silently. This workflow watches exactly those: List Open Invoices reads Stripe's open invoices regardless of how they were created, and the AR sheet becomes the single aging report the finance lead checks over coffee. Set escalation_day to 14 (or lower for big tickets) so the owner gets a Slack message with customer, amount, days overdue, and pay link the moment an invoice crosses the line — that visibility alone shortens payment cycles. Variation: add a second Stripe webhook on invoice.paid that flips the row to PAID, and the AR tab becomes a full invoice lifecycle instead of just the chase list.
Digital agency where the owner chases and the team doesn't
The classic agency problem: the founder knows which clients owe money, everyone else doesn't, and reminders happen "when someone remembers." This workflow institutionalizes the chase: the day 1/7/14 cadence runs regardless of who's on holiday, the Slack — Escalate to Owner post makes delinquency visible to the whole team channel, and the Telegram summary quantifies it — total outstanding, oldest overdue, reminders sent. That shared visibility changes behavior: account managers start nudging clients before day 14 because they can see the escalation coming. Tip: change reminder_days in CONFIG — AR to match your terms — net-15 clients might need 1,7,10, while enterprise net-30 can stay at 1,7,14.
Contractor or trades business with progress billing
A contractor billing in milestones — deposit, rough-in, completion — has invoices tied to job stages, and late final payments eat the margin. The AR sheet's columns (Invoice ID, Number, Customer, Email, Amount, Due Date, Days Overdue, Status) double as the job-billing tracker: filter by customer to see every milestone's state. The friendly→firm→final email progression suits trade relationships where you still want the next job from the same client — the day-1 nudge is polite enough to send to anyone. Practical variation: add a tiered escalation — a second IF branch at 30+ days that emails you directly or pings a different channel — so ancient invoices get personal attention instead of sitting at ESCALATED forever.
Bookkeeper managing AR for multiple clients
A bookkeeper running AR for five small businesses can duplicate this workflow per client: each gets its own CONFIG — AR (business name, sender name, escalation channel) and its own AR tab, all running off one n8n instance. The Telegram summaries arrive per client each morning — a 30-second scan tells the bookkeeper which clients need a human touch today. Because the reminder copy lives in the Build Reminder Email Code node, the bookkeeper can match each client's voice (formal for the law firm, friendly for the café) and CC the client's accountant on the day-14 notice. Tip: the workflow skips invoices not yet due, so early-paying clients never get a reminder by mistake — the most important trust property of any automated chase.