Think of a bustling digital agency that just delivered a beautiful e-commerce platform. The client is thrilled, the launch is successful, and you send the final invoice. Then... crickets. Chasing payments is the most universally hated task in business. It feels awkward, it damages rapport, and it steals time you could spend building.

By delegating this to a machine, you completely remove the emotional friction. The client receives a polite, perfectly timed email. They know it's a system notification, not you personally breathing down their neck. You preserve the relationship while ensuring your cash flow remains healthy.

Workflow Architecture

Before we look at nodes and credentials, we need to map out the exact logic our virtual accountant will follow.

graph TD
    A[Cron Trigger: 9:00 AM] --> B[Query Database: Unpaid Invoices]
    B --> C{Is Due Date Past?}
    C -->|No| D[Do Nothing]
    C -->|Yes| E{Days Overdue?}
    E -->|3 Days| F[Send Gentle Reminder]
    E -->|7 Days| G[Send Firm Reminder]
    E -->|14+ Days| H[Send Final Notice + Late Fee]
    F --> I[Update DB: last_reminder_date]
    G --> I
    H --> I

Progressive Implementation: Database Queries

While n8n handles the visual routing, the core of this workflow relies on how you query your data. Let's look at how this evolves from a simple prototype to a production-ready system.

1. Simple (The Prototype)

When you are just starting out, you might fetch everything that is unpaid and filter it inside n8n using an IF node. This is fine for a dozen invoices, but terrible for performance.

-- Avoid pulling all data into memory
SELECT id, customer_email, amount, due_date 
FROM invoices 
WHERE status = 'unpaid';

2. Intermediate (The Filtered Approach)

A better approach is to make the database do the heavy lifting. We only pull invoices that are actually overdue.

-- Let the database filter the dates
SELECT id, customer_email, amount, due_date 
FROM invoices 
WHERE status = 'unpaid' 
  AND due_date < CURRENT_DATE;

3. Production (The Idempotent Query)

In a production system, we must ensure we don't spam the client. We need to check when we last sent a reminder to enforce a cooldown period (e.g., don't send another reminder for at least 3 days).

-- Safe, production-ready query with a cooldown
SELECT id, customer_email, amount, due_date 
FROM invoices 
WHERE status = 'unpaid' 
  AND due_date < CURRENT_DATE
  AND (last_reminder_sent IS NULL OR last_reminder_sent < CURRENT_DATE - INTERVAL '3 days');

Building the Workflow

Sample Data Payload

Use this mock JSON to test your email templates without querying a live database.

{
  "invoice_id": "INV-2026-004",
  "customer_name": "Acme Corp",
  "amount_due": "1250.00",
  "due_date": "2026-05-10",
  "days_overdue": 2
}

Interview Questions

Test your understanding of automated billing systems with these questions.