Invoice Follow-Up Automation for Freelancers Using OpenClaw

The Invoice Follow-Up Problem

Most freelancers hate chasing invoices. It feels awkward, it's time-consuming, and it has nothing to do with the actual work. But it's also unavoidable — late payments are the norm, not the exception, and the operators who follow up consistently get paid faster than those who don't.

The good news: invoice follow-up is one of the most automatable tasks in a freelance business. It's pattern-based, it's template-driven, and the decision logic is simple. With the right OpenClaw configuration, your agent handles the entire follow-up sequence without you touching it.

The Billing Rules Pattern in AGENTS.md

Start with explicit billing rules in AGENTS.md. This is the section that tells your agent how to behave around money — and billing rules always belong in Tier 3 by default, with specific carve-outs for automated follow-ups.

```

Billing Rules

### Invoice Tracking

- All invoices are logged to /memory/invoices.md on creation

- Invoice log format: Client | Amount | Issue Date | Due Date | Status | Last Contact

### Automated Follow-Up Sequence (Tier 2)

After invoice due date passes with no payment recorded:

Day +7: Send template invoice-followup-7day.md. Notify operator. Log contact.

Day +14: Send template invoice-followup-14day.md. Notify operator. Log contact.

Day +30: Escalate to Tier 3 — notify operator, do not send automatically.

Flag in morning brief as OVERDUE ESCALATION.

### Tier 3 Billing Actions (Always Require Approval)

- Sending any communication after Day +30

- Modifying invoice amounts or terms

- Marking any invoice as uncollectable

- Any action involving a retainer adjustment

```

The Day +30 escalation is deliberate. At that point, the situation has left the routine zone — you need to make a judgment call about whether to continue following up, send a formal demand, or write it off. That's a human decision.

The Invoice Log

The invoice log in /memory/invoices.md is what makes the whole system work. Your agent reads it to determine what needs follow-up, and writes to it after each action.

```markdown

# Invoice Log

| Client | Amount | Issue Date | Due Date | Status | Last Contact |

|--------|--------|------------|----------|--------|--------------|

| Rivera Studios | $3,200 | 2026-03-01 | 2026-03-15 | OVERDUE +7 | 2026-03-22 |

| Chen Consulting | $1,800 | 2026-03-10 | 2026-03-24 | PENDING | — |

| Webb Creative | $4,500 | 2026-02-15 | 2026-03-01 | PAID | — |

```

Keep it simple. The agent updates Status and Last Contact after each action. You can read the whole picture in 30 seconds.

The Follow-Up Templates

Each stage of the sequence needs its own template. Here's the three-stage set:

Day +7 (Gentle reminder):

```

Subject: Invoice #[INVOICE_NUMBER] — quick follow-up

Hi [CLIENT_NAME],

Just a quick note to follow up on invoice #[INVOICE_NUMBER] for $[AMOUNT],

which was due on [DUE_DATE]. Please let me know if you have any questions

or if there's anything I can help with on your end.

Thanks,

Kade

```

Day +14 (Direct follow-up):

```

Subject: Invoice #[INVOICE_NUMBER] — now 14 days past due

Hi [CLIENT_NAME],

Following up again on invoice #[INVOICE_NUMBER] for $[AMOUNT], now 14 days

past the [DUE_DATE] due date. If there's a timing issue or you need to

discuss payment terms, I'm happy to work something out — just let me know.

Thanks,

Kade

```

Day +30 (Operator handles this one):

This is flagged in the morning brief with full context. You decide the tone.

The Morning Brief Integration

The agent should include billing status in the morning brief automatically. Here's the format:

```

Billing Status

OVERDUE:

- Rivera Studios: $3,200 — 7 days overdue. Follow-up sent yesterday.

- [Any others]

FOLLOW-UP TODAY:

- [Invoices hitting Day +7 or +14 today]

ESCALATION NEEDED:

- [Any invoices at Day +30 or beyond — requires your action]

UPCOMING DUE:

- Chen Consulting: $1,800 due 2026-03-24 (2 days)

```

You see the full billing picture every morning without opening a spreadsheet.

What This System Doesn't Replace

This setup handles the mechanics of invoice follow-up. It doesn't replace judgment on edge cases — clients with legitimate payment issues, projects where the relationship matters more than the payment, invoices that are genuinely disputed.

The escalation to Tier 3 at Day +30 is specifically designed to preserve that judgment. The routine sequence runs automatically. The hard calls come back to you.

The result is that invoice follow-up happens consistently without you thinking about it — until it needs your thinking.