How to Set Up Recurring Invoices for Retainer Clients

The short version

To put a retainer client on recurring invoices, do five things:

1. Pick your billing model first — fixed monthly fee, a prepaid bank of hours, or paid access. The model decides how you set everything else up.
2. Build one clean template invoice — the line items, rates, and taxes that will repeat. Date-stamp the description: "Design retainer — April 2026," not just "Design retainer."
3. Set the cadence — usually monthly, on a fixed day (the 1st is the common choice), sent in advance.
4. Decide auto-send or review-first — auto-send when the amount never changes; draft-for-review when it might.
5. Set an end condition and turn on reminders — cap the series to the contract term so it stops on its own, and make sure the generated invoices still chase themselves if they go unpaid.

The two mistakes almost everyone makes: they treat every retainer the same when the billing model should drive the setup, and they auto-send on faith and forget about the invoice until a wrong amount has gone out three months running. Below is how to avoid both, plus the one thing you'll still handle by hand — the first partial month.

First, decide how you're billing the retainer

Every guide jumps straight to "create a template and set a schedule." That skips the decision that actually shapes the invoice. Retainers are how most agencies now prefer to work — 85% said they prefer retainer arrangements in SparkToro's 2025 State of Digital Agencies survey, up from 81% the year before (n=376, so read it as "among surveyed agencies") — but "retainer" isn't one thing. There are three real billing models, and they don't invoice the same way.

Model	What the client pays for	How to invoice it
Fixed monthly fee	A defined ongoing scope, same amount every month	One flat recurring invoice. Safe to auto-send. Cap it to the contract term.
Hours-bank (prepaid block)	A block of hours (e.g. 10/month) that draws down	Recurring invoice for the base block; bill overage separately. Auto-send the base, review overages.
Pay-for-access (on-call)	Your availability, whether or not they use it	Mechanically identical to a fixed fee. The difference is in the contract, not the invoice.

One accounting note worth knowing if you bill any of these in advance: money a client prepays isn't income the day it lands. Under the US revenue-recognition standard (ASC 606), an advance payment is a liability — deferred revenue — that you recognize as you actually do the work (RevenueHub, BYU School of Accountancy; Corporate Finance Institute). For a fixed retainer that usually smooths out to the monthly fee. For a prepaid hours-bank, the unused hours a client has paid for are a real obligation you still owe them, which is exactly why the "what happens to unused hours" question below matters.

Most freelancers and small agencies run a fixed monthly fee, so the rest of this guide uses that as the default and flags where the other two differ.

The five-step setup

Step 1 — Build one clean template invoice

The recurring invoice is a template that copies itself every cycle, so anything wrong on it is wrong every single time. QuickBooks puts it plainly in their own recurring-invoice guidance: make sure everything is accurate before you save, because any error here repeats every billing cycle. A mistyped rate doesn't cost you once. It costs you until you notice.

Build the invoice exactly as you'd bill this client normally: their details, the line items, your rate, and both tax lines if you use them. One small habit that pays off later: put the period in the line-item description and let it move with each cycle — "Retainer — [month] [year]" reads clearly on the client's end and in your own records, where a bare "Monthly retainer" turns into twelve identical rows you can't tell apart.

Step 2 — Set the cadence

For a retainer, monthly on a fixed day is the standard, and billing in advance (at the start of the period, not the end) is the norm — the client is reserving your capacity, so you invoice for it up front.

Under the hood, a proper recurring engine stores this as a recurrence rule — the same RFC 5545 "RRULE" standard calendars use. In Pushsilver that means a real rule, not a vague "monthly" toggle: you pick weekly, monthly, or yearly, and for monthly you set the day of the month, including a proper end-of-month option so a series billed on "the last day" doesn't break in February. It also stores a send time in the client's timezone, so a 9am invoice goes at 9am their time, not yours.

Two things to get right here:

• Pick a day and stick to it. Billing every client on the 1st makes your month legible — you know what's going out and when. Scattering send dates across the month buys you nothing.
• Don't over-reach on frequency. Weekly, monthly, and yearly cover essentially every real retainer. If a tool promises "every 9 days" flexibility, ask yourself when you'd ever use it. Pushsilver deliberately supports weekly, monthly, and yearly and stops there, because a retainer that bills on some arbitrary interval is a retainer nobody can predict.

Step 3 — Decide auto-send or draft-for-review

This is the choice most guides wave past, and it's the one that saves you from an embarrassing email. The decision rule is simple:

• Auto-send when the amount and scope are genuinely fixed — a flat monthly retainer that's the same in July as it was in January. QuickBooks frames the test the same way: automate when you're billing the same customer the same amount on a consistent schedule.
• Draft-for-review when anything varies — an hours-bank with overages, a retainer with usage-based add-ons, or a client whose scope keeps shifting. Here you want a human glance before it goes.

In Pushsilver this is a single toggle per series. With auto-send on, each occurrence is created and sent the moment it's due. With it off, the occurrence is created as a draft and you get a "draft invoice ready" notification, so you can add the month's overage or fix a number before it reaches the client. Set it per client, not globally — your steady $2,000/month clients can run on autopilot while your variable ones wait for a look.

Step 4 — Set the end condition

A retainer has a term. The recurring invoice should know it. Set the series to stop either after a fixed number of occurrences or on an end date, and you never have to remember to switch it off — which is the single most common way people overbill an ex-client.

Pushsilver supports both: an occurrence counter that ticks down each cycle and deactivates the series when it hits zero, or an "until" date baked into the recurrence rule. Match it to the contract: a six-month engagement gets six occurrences. When the work ends early, pause or cancel the series that day. QuickBooks lists forgetting this — leaving a profile running after a relationship ends — as a leading cause of billing disputes, and they're right. An invoice that arrives after the client thinks they've left you is a support ticket and a chargeback waiting to happen.

Step 5 — Set payment terms, reminders, and online pay

The recurring invoice generates a normal invoice, which means everything you'd want on a one-off invoice should carry over.

• Payment terms. Pushsilver takes these from the client record — On Receipt, Net 7/15/30/45/60, or a custom date — defaulting to Net 30. Set the client's terms once and every generated invoice inherits them.
• Reminders. A recurring invoice that goes unpaid still needs chasing. In Pushsilver, generated invoices inherit your team's reminder schedule automatically, so they follow the same before-due and after-due cadence as everything else. If you haven't set one, our default fires three days before the due date, on the due date, and at seven and fourteen days past — the reminder schedule that gets you paid. Reminders matter more than wording: Chaser, analyzing data from more than 26,000 finance professionals, found that combining email and SMS reminders raised the odds of an invoice being paid within a week of its due date by 56% (Chaser 2022 Late Payments Report).
• Online payment. Leave card payment on. The gap between "I should pay this" and "it's paid" is where retainers drift late, and a pay-now link closes it.

The mid-cycle problem nobody automates: proration

Here's the case every "set it and forget it" guide ignores. A client signs on the 10th, but you bill on the 1st. What do you charge for those first eleven days?

The math is settled. Prorate it:

Prorated charge = full monthly fee × (days served ÷ days in the period)

The only real decision is your denominator, and billing platforms name two conventions: use the actual days in that month, or treat every month as a flat 30 days (Zuora; Recurly). They differ by a few dollars, so pick one and put it on the invoice.

Say a $3,000/month retainer starts March 10, billed on the 1st. March has 31 days; the client is served for 22 of them.

• Actual-days: $3,000 ÷ 31 = $96.77/day × 22 = $2,129.03
• 30-day convention: $3,000 ÷ 30 = $100/day × 22 = $2,200

That ~$71 gap is entirely the denominator, which is why you decide once and state it.

Now the honest part: a lot of invoicing tools, Pushsilver included, don't auto-calculate this first partial period. Big subscription platforms like Stripe Billing do prorate the opening stub automatically; most invoice-first tools built for freelancers don't. That's a deliberate scope line, not an oversight — proration is a genuinely fiddly feature and most retainers don't need it running on every cycle, only at the very start.

So handle the first month by hand: send one prorated invoice for the partial period, then start the clean recurring series on the next 1st. One manual invoice at signup, autopilot forever after. If a client starts only a few days before your billing date, it's often simpler to fold those days into the first full month or just start clean on the 1st — a three-day proration isn't worth the arithmetic.

A worked example

You land a $2,000/month design retainer. The client signs on March 12, the contract runs six months, and you bill on the 1st.

1. At signup: send a one-off prorated invoice for March 12–31. Actual-days: $2,000 ÷ 31 × 20 = $1,290.32, due on your standard terms.
2. Set up the recurring series: template at $2,000, monthly, day-of-month = 1, first run April 1, capped at six occurrences (April through September). Auto-send on, because the fee is fixed.
3. Confirm the client record carries Net 15 terms and reminders are on.
4. Tell the client what's coming: "You'll get an invoice on the 1st of each month, due by the 15th."

That's one manual invoice and about two minutes of setup. For the next six months the invoices generate, send, and chase themselves, and the series switches off after September on its own.

Common retainer-invoicing mistakes

• Auto-sending a stale rate. The flip side of automation: a recurring invoice keeps billing last year's price perfectly forever. Review your retainer rates on a fixed annual cadence — raising fees is now near-universal, with roughly 97% of agencies and 80% of accounting and tax firms planning increases, most in the 5–15% range (Ignition 2025 pricing benchmarks, reported by MarketingProfs and Accounting Today). Give 30 to 90 days' written notice, and put a rate-review clause in the contract so the increase isn't a renegotiation every year.
• Forgetting to stop the series. Cap every retainer to its term or cancel it the day the work ends. Overbilling a former client is worse than under-billing a current one.
• No heads-up before the first automated invoice. Tell a new retainer client the billing date and amount before the first one lands. An unexpected auto-charge is how you earn a dispute.
• Fuzzy unused-hours terms on an hours-bank. Decide up front whether unused hours expire or roll over, and say so in writing. The defensible default is use-it-or-lose-it — the client is paying for reserved capacity, not a growing IOU of your labor. If you do allow rollover, cap it (a common recommendation is around 25% of the monthly allotment, expiring after a month) rather than letting it compound (Ben Guttmann).
• Letting generated invoices go un-chased. A recurring invoice is still an invoice. If your tool doesn't apply reminders to auto-generated invoices, you've automated the sending and un-automated the collecting.

Automate it without losing control

Recurring invoices fix one slice of a bigger problem — forgetting to invoice at all. A retainer has no natural cue to bill, which is exactly why it slips. The point of a recurring invoice isn't to stop paying attention. It's to stop doing the keystrokes while keeping the judgment. That's the line Pushsilver is built to: a real recurrence rule you can actually predict (weekly, monthly, or yearly, on the day you choose), an occurrence cap or end date so a series ends when the contract does, a per-client auto-send toggle so your fixed retainers run themselves while your variable ones wait for a review, and reminders that follow every generated invoice so nothing sits unpaid because it was automatic.

The founder's-eye view after building this: automation earns its keep on the boring, unchanging retainers, and a review step earns its keep everywhere else. Set the fixed ones to auto-send and forget them on purpose. Keep the variable ones on draft and give them ten seconds a month. Recurring invoices are part of the Pushsilver Solo and Agency plans; the core invoicing, reminders, and late fees underneath them are free on every plan, because chasing money you're already owed shouldn't be the thing you pay extra for.

FAQ

What is a recurring invoice for a retainer? It's an invoice template that generates and sends itself on a schedule — usually monthly — so a retainer client is billed the same amount at the same time each period without you rebuilding the invoice. The recurring setup handles the sending; a written retainer agreement handles the scope and terms.

How often should I bill a retainer client — monthly or per project? Monthly, billed in advance, is the standard for an ongoing retainer, because the client is paying to reserve your capacity for the period. Per-project (milestone) billing is a different arrangement: you invoice on delivery, not on a recurring schedule, so it isn't a retainer.

Should recurring invoices auto-send or should I review them first? Auto-send when the amount and scope are fixed and unchanging. Switch to draft-for-review when anything varies — hours-bank overages, usage add-ons, or a shifting scope — so a human catches a wrong number before it reaches the client. Decide this per client, not once for everyone.

How do I handle a client who starts mid-month? Send one prorated invoice for the partial period, then start the recurring series on your next normal billing date. Prorate by charging the full fee times days-served divided by days-in-the-period, and pick one convention (actual days or a flat 30) so the math is consistent. For a start just a few days before your billing date, it's often simpler to fold it into the first full month.

Can I set a recurring invoice to stop after a number of months? Yes — set an occurrence cap or an end date matched to the contract term. A six-month retainer gets six occurrences and the series deactivates on its own. This is the reliable way to avoid billing a client after the engagement has ended.

Do recurring invoices still send payment reminders? They should. A generated invoice is a normal invoice, so it needs the same follow-up if it goes unpaid. In Pushsilver, recurring invoices inherit your team's reminder schedule automatically, so they chase themselves on the same cadence as everything else.