Recurring invoices: the retainer setup that runs itself

Retainer work is the best revenue a freelancer can have and the most annoying to administer. The amount is identical every month, the client is identical every month, and yet a surprising number of freelancers spend the first Monday of each month duplicating last month's invoice and editing the dates.

That is a scheduled task pretending to be creative work. Here is how to set it up so it disappears.

What belongs on a recurring template

A recurring invoice template is just a normal invoice plus a cadence. What you configure once:

• Client and currency. Locked, because the whole point is that nothing varies.
• Line items. Usually a single line, "Monthly retainer, September 2026" or "Design retainer, 20 hours reserved."
• Cadence and next run date. Monthly on the 1st is the default. Quarterly works for advisory retainers.
• Payment terms. Retainers should be due on receipt or Net 7, because you are being paid for capacity you are about to reserve.
• Whether it sends automatically. Most freelancers want the invoice generated and emailed with no touch at all. Some prefer generated as a draft so they can add a line for overage.

Bill in advance, not in arrears

The single most useful change to a retainer is billing on the 1st for the month ahead rather than on the 30th for the month behind. Three reasons:

• You are paid for reserved capacity, which is exactly what a retainer is.
• Your cash flow leads your work rather than trailing it by six weeks.
• A client who stops paying stops before you have done the work, not after.

If you are currently billing in arrears, the switch is one transitional month. Tell the client in advance, and offer to split the transition invoice across two months if the double hit is awkward.

Handling the parts that do vary

Retainers drift. Extra hours, an out of scope request, a reimbursable expense. Keep the template clean and handle variance separately:

• Overage hours. Add them as a separate line on the recurring invoice before it sends, or issue a small separate invoice. Do not silently absorb them, that is how a retainer becomes unprofitable without anyone noticing.
• Reimbursable expenses. Tag the receipt to the client's project and pull it onto the invoice as its own line. It should read as a pass through cost, not part of your fee.
• Annual increases. Put the review date in the agreement. A retainer that has not moved in three years is a pay cut you agreed to by inaction.

The failure modes to design around

• Templates that keep firing after a client leaves. Deactivate rather than delete, so the history stays intact.
• Duplicate invoice numbers. The recurring sequence must be the same sequence as your manual invoices.
• Silent failures. If a generated invoice fails to email, you need to know that day, not at month end.
• Forgetting what the retainer covers. Keep the scope in the template description so the invoice itself reminds both sides what was agreed.

What we built

Invoicy generates invoices from recurring templates on a daily job, allocates numbers from the same sequence as everything else, and lets you pause a template without deleting it. Recurring templates sit on the Pro plan and above.

TL;DR

• Configure once: client, currency, line items, cadence, terms.
• Bill on the 1st for the month ahead, not the 30th for the month behind.
• Handle overage and expenses as separate lines rather than absorbing them.
• Pause rather than delete, keep one number sequence, and get alerted when a send fails.