A freelancer’s invoice follow-up workflow

Make the invoice easy to process from the start.

Before issuing an invoice, confirm the billing contact, the agreed amount, the due date, and any purchase-order or approval reference. Use payment instructions the client expects. Record where you sent it so you can find the original conversation later.

Keep one place where you can see the invoice reference, client, outstanding amount, and status. It can begin as a spreadsheet. The useful part is maintaining a clear record rather than relying on a collection of unread emails.

Give yourself a short review window.

Set aside a regular admin slot that fits your working week. Before deciding which reminders to send, check payment records and the client’s last reply. A routine with current information is more useful than a large automatic queue with old balances.

1. Record new payments and correct remaining balances.
2. Read replies, promised payment dates, and questions.
3. Pause invoices that are disputed or need a conversation.
4. Choose one next action for each overdue invoice.
5. Review the message and recipient before sending.

Keep invoice currencies separate if you track several currencies. The current Dunlio release supports EUR amounts; do not import a different currency as EUR merely to fit it into the app.

Choose a cadence that leaves room for a reply.

Build the timing around your agreement and the actual conversation. For a straightforward overdue invoice, you might begin with a short email after the due date, leave several business days for a response, then ask for a payment date. If there is still no response, check that you have the right contact before increasing the pressure.

These are workflow suggestions, not rules about when a debt must be paid. Do not add charges or formal escalation wording automatically. If an invoice needs a formal process, review the agreement and seek suitable advice for the place where you and your client operate.

Record the answer, then change the next action.

A promised payment date changes the task from “send another reminder” to “check after that date.” A missing reference changes it to “provide the document.” A dispute changes it to “review the agreement.” Record these decisions where you manage the invoice.

Hi [client name],

I’m checking the next step for invoice [invoice number], with [amount] still outstanding.

Could you confirm the expected payment date, or let me know what you need from me to move it forward?

Thanks,
[your name]

Use the template collection when a client needs a more specific reply. Once payment is received, mark the invoice paid promptly and stop its reminders.

Let automation handle the routine cases.

Automation is useful when the account, recipient, invoice, and balance are all ready. In Dunlio, first confirm your account email, use that mailbox for replies, and obtain early-access sending approval. Add or import the invoice, choose a saved reminder template, and check a manual preview.

If you enable automatic follow-ups, review the days after the due date and your business timezone. The worker sends in a weekday 09:00–17:00 window. Automation also needs the operator’s configured email service and signed delivery webhook. Paid, paused, disputed, stale, and suppressed invoices are held.

Keep confirming the balance from your own records: Dunlio does not connect to your bank or read an accounting payment feed. Its default freshness window is 72 hours, so an old balance confirmation cannot keep a reminder sequence running indefinitely. Review the automatic reminder requirements when a message is held.

Start small, then make the routine yours.

Begin with one or two invoices and one useful template. Check the preview, record what happens, and expand only once the process is comfortable. You do not need a large sequence to make the next step clearer.

Invoice Follow-ups brings the list, templates, and sending activity into one personal workspace. The first release is free early access, with no card required and reviewed sending setup. You can explore the sample demo before creating an account; the demo does not send email.