billable.devRetainer invoice template
A retainer invoice looks simpler than an hourly one, often a single line, and that's exactly why it goes wrong. The wording of that one line decides whether you're being paid for availability or for hours consumed, and those two readings lead to very different conversations in a quiet month. Here's how to structure it.
What a retainer actually sells
A retainer is a standing claim on your capacity. The client is buying the guarantee that when something breaks or a decision needs making, you are already engaged and can start now rather than in three weeks. That guarantee has value in months where nothing breaks — which is the part the invoice has to communicate, because it's the part that gets questioned.
Almost every retainer dispute traces back to an invoice that described hours instead of availability. Once the line item reads like a block of prepaid time, an unused month looks like an overpaid month, and you are defending the model rather than doing the work.
The line item
One line, naming the period and the commitment:
- Retainer — September 2026, engineering availability
- Retainer — Q3 2026, technical advisory and on-call escalation
Not "20 hours of development". If the agreement includes a soft ceiling on hours, that belongs in the contract and can be restated in the invoice notes as context — but it is not the thing you are charging for, so it does not belong in the description of the charge.
Show the period on its own
Retainer invoices repeat, which makes them easy to mistake for duplicates — both by finance systems and by the humans reviewing them. Put the period in the line item, keep the invoice number sequential, and set an issue date that is consistent every cycle. If your client's accounts payable system flags a possible duplicate payment, the period on the line is what resolves it in seconds.
Handle overage without touching the retainer line
When a month runs past what the arrangement covers, add a second line. Keep the retainer at its fixed figure:
- Retainer — September 2026, engineering availability — $4,000
- Additional work beyond retainer scope: data migration tooling, 12 hrs @ $150 — $1,800
The fixed line stays fixed. The moment you start adjusting the retainer amount up in busy months and down in quiet ones, you have converted it into hourly billing with extra steps, and you have invited a negotiation on every invoice. Overage rates should be agreed when the retainer is agreed, not discovered on a bill — the same rule that applies to hourly overruns.
Bill in advance, on a fixed date
Invoice at the start of the period the retainer covers. Billing in arrears contradicts what's being sold: the client already had the availability, and now you're asking to be paid for a month of standby that has already passed. Advance billing on the same date each cycle also makes the payment predictable enough that most finance teams will schedule it, which is the quietest way to get paid on time.
What to leave off
Resist attaching a running tally of hours used against hours available. It looks like transparency and functions as an invitation to audit — a client looking at "7 of 20 hours used" is being prompted to ask for a refund on the other thirteen. If you want to show the value of a quiet month, a short note listing what was covered (monitoring, two escalations, one advisory call) does that without framing the retainer as a meter.
Recurring invoices without the retyping
Retainers are the case where regenerating the same invoice every period is most of the work. Billable saves invoices in your browser, so duplicating last period's and changing the period label takes seconds, and Pro adds recurring helpers and per-client defaults for the clients you bill on a cycle. Everything runs client-side — your rates and client names never leave your machine.
Generate your retainer invoice
Common questions
- What should the retainer line item actually say?
- Name the period and what the retainer secures, not the hours consumed. 'Retainer — September 2026, engineering availability' is the line. A retainer buys reserved capacity, and describing it as a block of hours quietly reframes it as prepaid hourly work, which is the argument you don't want to have when a quiet month comes around.
- Do unused hours roll over?
- Only if the contract says so, and there are good reasons to say no. Rollover turns a retainer into a credit balance the client can draw down during a busy month, which removes the predictability that made the arrangement worth offering. If you do allow it, cap the rollover at one period so the balance can't compound into a large unbilled liability.
- How do I bill work beyond the retainer?
- As a separate, clearly labeled line on the same invoice, at a rate agreed in advance. Keep the retainer line at its fixed amount and never adjust it to absorb overflow — the moment the retainer figure starts moving month to month, it stops reading as a fixed commitment and every invoice becomes negotiable.
- Should I invoice at the start or the end of the period?
- In advance, at the start. A retainer is payment for reserved availability during the period, so billing after the fact contradicts what the client is buying and puts you in the position of financing their access. Invoicing on the same date each period also makes the payment predictable enough to be automated on their side.
- How is this different from a deposit?
- A deposit is money against a specific piece of work, drawn down until it's gone. A retainer recurs and buys availability for a period whether or not it gets used in full. They're often confused in contracts, and the confusion surfaces at exactly the wrong moment — when someone wants a refund for a quiet month.
