Guides · Invoice follow-up

How to track overdue freelance invoices in Notion (without another paid CRM)

Updated Nov 2, 2026 · ~9 min read · FollowRail

You finished the work two weeks ago. The invoice went out. The client said “will pay Friday.” It is now the Friday after that Friday. The unpaid amount is still sitting in a spreadsheet column you stopped sorting. That is not a “second brain” problem. It is an overdue-invoice memory problem. This guide builds a narrow Notion overdue invoice tracker that surfaces who owes you, how many days late, and when to chase next—without pretending Notion sends email or collects cards.

Why invoices go quiet (and why a sheet stops helping)

Most freelancers already have a place that “knows” the invoice exists: Wave, Stripe, PayPal, or a bookkeeping export. The failure mode is rarely “I never billed.” It is “I billed, then delivery got loud, and the reminder never got a date.” Spreadsheets fail the same way: you open them when you feel anxious, not when the due date passes.

A good invoice follow up system answers three questions before you open Gmail:

1. Who is late? — Status is still Sent or Partial, and Due date is in the past.
2. How late? — Days overdue so you escalate calmly instead of guessing.
3. What is the next chase? — A Next chase date (or Follow-ups Due date) that appears on a Today view.

If your tracker cannot answer those in under a minute, you will invent the chase list in your head again—and head-lists lose to whoever is pinging you right now.

What “overdue” must mean in the database

If Status is only Draft / Sent / Paid, you will still miss money. Partial payments, voids, and “sent but not due yet” need explicit states. Keep the property count near twelve—extra tax categories or bank-feed fields are how freelance trackers rot.

• Invoice # — stable id for chase notes.
• Client (relation) — one truth source per person.
• Amount — unpaid cash you can sum on a dashboard.
• Status — Draft / Sent / Partial / Paid / Void.
• Issue date and Due date — bill date and contractual deadline.
• Overdue — true when Status is Sent/Partial and Due date < today.
• Days overdue — e.g. dateBetween(now(), Due date, "days") when overdue.
• Next chase date — the date the Today view cares about.
• Paid date / Paid amount — close the loop; Partial needs Paid amount.

Overdue formulas only help when Due date is correct the day you mark Status = Sent. Set both fields in the same minute you send the PDF or payment link.

The Follow-ups database is the real product

Invoices tell you the money state. Follow-ups tell you the action. Put them beside the same clients you already track for proposals—see the companion client follow up tracker guide.

Minimum Follow-ups fields: Client relation (optional Invoice), Type = Invoice chase, Due date, Status Open/Done/Skipped, Cadence D+3/D+7/D+14/D+30, and a short Script snippet you paste into your own inbox.

Views that matter:

1. Follow up today — Due ≤ today, Status = Open.
2. Overdue — same filter, sorted by Days overdue on the linked invoice.
3. This week — planning, not panic.

Open Follow up today first each morning, then an Invoices view filtered to Overdue. A client kanban alone still leaves you inventing the chase list in your head.

A simple chase cadence that does not feel spammy

After Status becomes Sent, count from the due date (or from send day if Net-0):

• D+3: friendly landing check—“checking this landed; happy to resend the PDF.”
• D+7: firm, still short—“invoice #… was due …; can you confirm payment timing?”
• D+14: firm + next step—“still open on my side; should I pause new work until this clears?”
• D+30: last polite escalation or hand to your contract terms.

Hi [Name], quick note that invoice #[number] for [amount] was due [date]. Happy to resend the PDF or payment link if it got buried. Could you confirm timing on your side?

Create the next Follow-up row when you mark the current one Done. Notion will not email for you—that boundary is intentional. Keep proposal nudges and invoice chases as different Types so you never mix “payment was due” into a warm proposal. Pair this with a proposal follow up cadence when both pipelines are active.

Why not HoneyBook / Dubsado for this job alone

Those tools win when you need proposals, e-sign, a client portal, and card checkout in one login. They are weaker when your only failure mode is forgetting to chase while Wave, Stripe, PayPal, or bank transfer already move money. A subscription CRM used as an expensive reminder list is how freelancers bounce back to Sheets. A four-database Notion desk (Clients, Deals, Follow-ups, Invoices) plus a Today page is enough for solo discipline on Notion Free—payment rails move money; Notion holds memory and next action.

How FollowRail fits

FollowRail is a focused freelance CRM Notion template built for that job: clients, proposal stages, a follow-ups desk with today / upcoming / overdue views, and invoice status next to the same people—without wiring every relation from scratch.

Pay once ($23.99), open the Duplicate link, and set up in about five minutes. It stays in your Notion workspace. It tracks status and dates; it does not replace Stripe or Wave, and it does not send chase email for you.

Copy-paste Start Here (about ten minutes)

1. Create four databases with the must fields above (thin Deals board optional).
2. Link Follow-ups and Invoices to Clients.
3. Build Dashboard views: Follow up today, Invoices Overdue, open pipeline value.
4. Add friendly / firm script snippets as templates or a text default.
5. Add one real client, one invoice, one chase due today—confirm Today lights up.

If setup takes longer than about ten minutes, delete properties until it does not.

Honesty checklist

• Notion does not send the chase email.
• Notion does not replace Stripe/Wave invoicing; it tracks status.
• Overdue formulas need a correct Due date.
• Multi-currency books and tax filing stay in accounting software.
• Void is progress when the balance will never clear—stop endless D+30s.

More on FollowRail: product overview · client follow up tracker · proposal follow up cadence · FAQ