Unpaid invoices are easier to manage when every account follows the same path from issue date to payment. This overdue invoice workflow gives you aging buckets, review checkpoints, follow-up email templates, payment-plan guidance, and a monthly accounts receivable checklist you can adapt to your own terms and tools.
Overview
A consistent accounts receivable process should make three things clear: what is owed, what action is due next, and who owns that action. The aim is not to send increasingly forceful messages to every client. It is to create a predictable, documented process that separates simple administrative delays from genuine payment risk.
Start with one source of truth, such as your accounting system, finance workspace, or a carefully maintained spreadsheet. Each invoice record should include the client, invoice number, issue date, due date, amount, currency, tax treatment, payment method, contact person, current status, last follow-up date, next action, and notes. Use consistent statuses such as Draft, Sent, Due soon, Overdue, Disputed, Payment plan, and Paid.
Before following up, verify that the invoice was sent to the correct address, contains the agreed purchase-order or project reference, and reflects the correct scope and tax details. If you use different tax rates or need to separate tax from the net amount, review the VAT calculator guide for freelancers and small businesses as part of your invoicing setup. A reminder cannot resolve an invoice that was inaccurate or routed incorrectly.
What to track
Invoice-aging buckets
An aging table groups open invoices by how long they have been outstanding. The exact buckets can vary by business, but the following structure is practical for a weekly review:
| Bucket | What it usually means | Recommended action |
|---|---|---|
| Not yet due | The invoice is within the agreed payment period. | Confirm delivery and prepare a friendly reminder if appropriate. |
| Due in the next 7 days | Payment is approaching. | Check that the client has everything needed to process payment. |
| 1–7 days overdue | The due date has passed recently. | Send a polite confirmation request and ask whether there is an issue. |
| 8–30 days overdue | The delay is becoming material. | Contact the accounts-payable owner, restate the amount and due date, and request a payment date. |
| 31–60 days overdue | The account needs active management. | Escalate to the appropriate client decision-maker and discuss a documented plan if needed. |
| More than 60 days overdue | The balance may represent elevated collection or relationship risk. | Review contract rights, pause new work where appropriate, and decide on a formal escalation path. |
These buckets are workflow labels, not legal conclusions. Payment terms, late-fee rules, tax requirements, and collection options vary by contract and jurisdiction. Check the governing agreement and obtain appropriate professional advice before adding charges, suspending work, or taking formal action.
Minimum tracking fields
- Amount: Record the gross amount due and, where useful, the net and tax components.
- Age: Calculate days from the due date, not simply from the invoice date.
- Reason for delay: Use clear categories such as missing approval, disputed scope, incorrect details, cash-flow issue, or unknown.
- Commitment: Record the promised payment date and the person who made the commitment.
- Next action: Give every open invoice a date and an owner.
- Relationship context: Note active projects, renewal discussions, service issues, or previous payment patterns.
Separate collection activity from profitability analysis. An invoice can be paid on time and still belong to a low-margin project. For a broader review of project and retainer economics, use the client profitability calculator guide.
Cadence and checkpoints
At invoice issue
- Confirm the legal entity, billing contact, purchase-order reference, amount, currency, tax treatment, and payment instructions.
- State the issue date, due date, accepted payment methods, and the best contact for billing questions.
- Save the sent invoice and any delivery confirmation in the client record.
- Set the first checkpoint before the due date, rather than waiting for a missed payment.
Before the due date
Send a short, helpful message several business days before the due date when that fits your relationship and contract. The purpose is confirmation, not pressure.
Subject: Invoice [number] due on [date]
Hi [name],
I’m checking that invoice [number] for [amount] reached you and is scheduled for payment on [due date]. Please let me know if your accounts-payable team needs a purchase-order reference, vendor form, or any other information.
Thanks,
[name]
After the due date
For an invoice that is only recently overdue, keep the message factual and assume an administrative delay first.
Subject: Payment check: invoice [number]
Hi [name],
Our records show that invoice [number] for [amount] was due on [date] and remains open. Could you confirm its payment status and the expected payment date? If there is an issue with the invoice or the work, please tell me so we can resolve it promptly.
Best,
[name]
If there is no response, contact the named accounts-payable owner and copy the operational contact only when useful. Avoid sending several contradictory messages from different people. Keep one clear thread and update the internal record after each contact.
For a disputed invoice
Subject: Resolving invoice [number]
Hi [name],
Thanks for flagging the concern about [brief issue]. I have reviewed [relevant document or milestone]. Let’s separate the disputed amount from any undisputed balance so we can agree on the next step. Could you confirm the specific amount under review and the information needed to resolve it?
I’ll respond with [proposed action] by [date].
Best,
[name]
Do not label a disputed invoice as a routine late payment until you understand the issue. Track the disputed portion, the undisputed portion, the responsible owner, and the next review date.
For a payment plan
A payment plan should be written down and approved by the person authorized to make that commitment. Include the total balance, installment amounts, payment dates, payment method, treatment of new invoices, and what happens if an installment is missed. Keep the tone practical rather than punitive.
Subject: Confirming the payment plan for [account]
Hi [name],
To confirm our discussion, the outstanding balance is [amount]. We agreed to payments of [amount] on [dates], beginning [date], using [method]. New invoices will follow the existing terms unless we agree otherwise in writing.
Please reply to confirm these details, or let me know what needs correcting.
Best,
[name]
How to interpret changes
Review trends rather than reacting to one late invoice. Three measures are especially useful:
- Total open receivables: The unpaid balance across all invoices.
- Overdue concentration: How much of the open balance sits in older aging buckets.
- Collection friction: The number of invoices delayed by missing information, disputes, approval gaps, or unclear ownership.
A rising total may reflect more sales, longer payment terms, delayed billing, or weaker collection performance. Compare the balance with recently issued invoices before drawing a conclusion. A growing 31–60-day or 60-plus-day bucket generally deserves more attention than a temporary increase in invoices that are not yet due.
Look for operational causes. Repeated requests for corrected invoices may indicate a template or data-entry problem. Frequent disputes may point to unclear scope, weak acceptance records, or a mismatch between the contract and delivery process. Regularly late payments from one client may justify a conversation about billing contacts, purchase-order procedures, deposits, milestone billing, or revised terms for future work.
Do not use a late fee as a substitute for communication. If your agreement permits late fees or interest, apply the terms consistently and verify the relevant rules before calculating or adding a charge. Your tracker should show the original balance separately from any approved additional amount.
When to revisit
Use this workflow at three levels. Run a short weekly review for all open invoices, focusing on invoices approaching their due date and those that need a next action. Run a more detailed monthly review to reconcile payments, investigate aging changes, check promised payment dates, and assign owners to every overdue balance. Review the process quarterly or whenever your services, clients, billing system, payment terms, or tax handling changes.
At the monthly review, complete this checklist:
- Export or reconcile the open-invoice list with the accounting record.
- Confirm that each invoice has the correct status, amount, age, and next action.
- Move paid invoices out of the open balance and investigate unmatched receipts.
- Review every invoice older than 30 days and record a reason for delay.
- Contact clients whose promised payment dates have passed.
- Escalate unresolved disputes to an internal owner.
- Check whether any client has accumulated a balance that should affect new work or renewal decisions.
- Review whether payment terms still fit your cash-flow needs and client onboarding process.
Keep the templates current, but do not change wording merely for variety. Update them when your payment instructions, contact roles, invoice fields, terms, or escalation policy changes. A calm, specific message sent at a known checkpoint is more useful than an improvised reminder sent only after the balance becomes a problem. For related operational reviews, the cloud productivity stack audit checklist can help you examine whether your finance and workflow tools still support the process.
To put this into practice, create the aging tracker today, assign an owner to every open invoice, schedule the next weekly review, and save the four email templates in your shared workspace. Then use the same workflow for one complete billing cycle before adjusting the buckets or escalation points.