Freelancer business dashboard for invoicing, payment tracking and late-payment chasing

Invoices sit unpaid in your inbox. You send a polite first reminder. Nothing. Two weeks later, you send another. Still silence. By month three, you've lost track of who owes what, and you're too frustrated to chase it properly. That missing £8,000 from three clients could've covered your software subscriptions for the next year, but instead it's just... forgotten debt floating in the ether. Most freelancers don't lose money to dishonesty. They lose it to disorganisation. You invoice on time, clients genuinely intend to pay, but somewhere between their inbox and their accounting system, your payment gets deprioritised. Without a systematic way to track and escalate overdue invoices, you're gambling with your cash flow every single month. Even a 5% improvement in on-time payments across your client base adds up to thousands annually. This workflow builds a freelancer's business dashboard that tracks invoice status, automatically escalates payment reminders, and integrates payment handling into a single, automated loop. No more manual spreadsheets. No more wondering whether you've followed up with a client. No more revenue sitting in limbo.

The Automated Workflow

The core idea is straightforward but powerful: when an invoice reaches a certain age without payment, the system automatically notifies you and the client, escalates the reminder, and prepares payment options. We'll use three tools in concert: a productivity app with reminders and nested AI chats (which serves as your central dashboard and notification hub), NextStep (which tracks invoice status and due dates with real-time visibility), and Payman AI (which handles payment reminders and follow-ups programmatically). The orchestration happens through n8n, a self-hosted or cloud-based workflow engine that sits between these tools and ensures data flows without manual intervention.

Step 1: Invoice Creation and Tracking

When you create a new invoice, add it to NextStep with a custom due date. NextStep allows you to set dynamic due dates based on payment terms (Net 30, Net 15, immediate, etc.), and it automatically tracks when each invoice approaches its deadline.

Step 2: Payment Status Monitoring

Every four hours, n8n polls NextStep via its API to fetch all invoices where the due date is within seven days or has already passed. This early warning system catches overdue invoices before they become a serious problem.

CopyGET https://api.nextstep.io/v1/invoices?status=overdue,pending&order_by=due_date
Headers: Authorization: Bearer YOUR_NEXTSTEP_API_KEY

Step 3: Intelligent Reminder Generation

When n8n identifies an at-risk invoice, it passes invoice details (amount, client name, invoice ID, days overdue) to Claude Sonnet 4.6 via the Anthropic API. Claude generates a personalised payment reminder message tailored to the client's payment history. If it's a first reminder, the tone is friendly and assumptive of a genuine oversight. If it's a third reminder, the tone shifts to more formal and urgent.

Copy{ "model": "claude-sonnet-4.6", "max_tokens": 300, "system": "You are a professional payment reminder writer. Generate brief, polite but firm payment reminder messages. Tailor tone based on reminder number and client payment history.", "messages": [ { "role": "user", "content": "Generate a payment reminder for invoice INV-2025-847 (£3,200) due on 2025-03-15, now 12 days overdue. Client: Acme Corp. This is the second reminder. Previous reminders ignored." } ]
}

Step 4: Multi-Channel Notification

The productivity app with reminders and nested AI chats receives the Claude-generated message via webhook and presents it in a nested chat interface. You can see the original invoice details, the AI-suggested message, and a direct communication thread with the client all in one place. The app automatically logs when you view the reminder, creating an audit trail.

Step 5: Escalation and Payment Triggering

If an invoice reaches 21 days overdue without payment confirmation, n8n triggers a Payman AI payment request. Payman AI can send a formal payment demand or, if you have the client's payment details on file, initiate a direct payment instruction. This removes the "I forgot" excuse from the equation.

CopyPOST https://api.payman.ai/v1/payment-requests
Headers: Authorization: Bearer YOUR_PAYMAN_API_KEY Content-Type: application/json { "client_id": "acme-corp-2025", "invoice_id": "INV-2025-847", "amount_pence": 320000, "currency": "GBP", "due_date": "2025-04-05", "message_template": "urgent", "callback_url": "https://your-domain.com/webhooks/payment-status"
}

Step 6: Closed-Loop Confirmation

When payment is received (confirmed via your bank API or manual entry), n8n updates the invoice status in NextStep and removes it from the overdue queue. The productivity app notifies you with a celebratory card or tag, and you manually mark the invoice as paid. This feedback loop ensures you always know which invoices are settled and which are still outstanding.

The n8n Workflow Structure

Here's a simplified schema of your n8n workflow:

CopyTrigger: Cron job (every 4 hours) ↓
Fetch overdue/pending invoices from NextStep API ↓
Filter invoices by days overdue (7+, 14+, 21+) ↓
For each overdue invoice: ↓ Call Claude Sonnet 4.6 to generate reminder message ↓ Post message + invoice details to productivity app via webhook ↓ If days overdue > 21: ↓ Trigger Payman AI payment request ↓
End loop ↓
Wait 4 hours, repeat

In n8n, this translates to a workflow with the following nodes: Schedule Trigger, HTTP Request (NextStep), Function Node (filter), Loop Node, HTTP Request (Claude API), HTTP Request (productivity app webhook), Conditional Node (days overdue check), HTTP Request (Payman AI), and a final Update Node that logs completion.

The Manual Alternative

If you prefer tighter control or don't have time to set up n8n, you can run a simpler version using the productivity app's built-in reminder rules. Create a rule that generates a reminder every seven days for any invoice past its due date. You then manually review these reminders each morning and decide whether to send a follow-up. This loses the AI-driven personalisation and automatic payment escalation, but it's much faster to set up and requires no coding.

Pro Tips

Watch your API rate limits.

NextStep allows 300 requests per hour on the free plan; Anthropic's API has rate limits that vary by subscription tier.

If you have more than 50 invoices, space out your n8n polling to every six hours rather than every four, or upgrade to a higher tier. Payman AI charges per payment request, not per API call, so costs scale with actual follow-ups, not polling frequency.

Use invoice templates with consistent due dates.

If you always use Net 30, NextStep can auto-calculate due dates when you create the invoice. This eliminates data entry errors and means n8n's filtering logic works reliably.

Store client payment history in NextStep.

Tag clients as "reliable", "occasional-delays", or "persistent-delays". Claude can use these tags to adjust reminder tone, and you get a quick visual sense of which clients need stricter follow-up.

Test the workflow with dummy invoices first.

Create five test invoices with dates set to the past, run your n8n workflow, and verify that reminders generate correctly before going live.

Archive old invoices quarterly.

Over time, your invoice list will grow and slow down API queries. Move paid invoices older than 90 days into an archive bucket in NextStep to keep active queries fast.

Cost Breakdown