Retainer Billing for Freelancers: Time Tracking + Invoices
Retainers feel simple until the first quiet month, the first overflow week, or the first client who asks, “What did we use the hours on?” A retainer is not a vibe. It is a billing design: when you invoice, what hours are included, what happens at the cap, and how time logs prove the story without turning every month into a courtroom.
This is a workflow guide, not another best-of list. It pairs with How to invoice clients as a freelancer, How to turn time logs into invoices, and How to get clients to pay invoices faster. For tool context on time → invoice loops, see the Harvest review.
Pricing disclaimer: Tool fees and payment processing change. Figures are orientation only — verify on the vendor site. Independent guidance; no affiliate links by default. Not legal advice — put retainer terms in a written agreement.
What a freelancer retainer actually is
A retainer is a recurring commercial commitment: the client pays a fixed amount on a schedule for ongoing access, a pool of hours, or a defined set of outcomes. Variants freelancers actually use:
| Model | Client pays | Hours role | Risk |
|---|---|---|---|
| Prepaid hours pool | Fixed fee for N hours | Logs consume the pool | Unused hours disputes if rollover is vague |
| Access / advisory | Fixed fee for availability | Logs for scope control | Scope creep disguised as “quick questions” |
| Deliverable retainer | Fixed fee for a monthly package | Logs for profitability | Package unbounded by “unlimited” language |
| Hybrid | Base fee + overflow T&M | Logs split carefully | Needs clear overflow rates |
Pick one primary model per client. Mixing silently creates unpaid work.
Design the money before you design the Notion board
Put these in the estimate / agreement:
- Fee and cadence (e.g. billed on the 1st for the upcoming month)
- Included hours or deliverables
- Overflow rate and approval rule
- Rollover (none / capped / expires)
- Response-time expectations (so “access” is not 24/7)
- Pause / kill fee if either side stops mid-cycle
- Invoice currency and payment methods
If it is not written, it will be renegotiated while you are tired.
Prepaid vs true-up: when to invoice
Pattern A — Invoice in advance (cash-flow friendly)
- Send retainer invoice before the period starts.
- Collect payment (or at least Net terms that still start early).
- Track hours against the pool during the month.
- At month end, send a short usage summary; invoice overflow separately if approved.
Best for: ongoing advisory, marketing retainers, retainers with trust already built.
Pattern B — Invoice in arrears with true-up
- Track all hours during the period.
- Invoice the base retainer + documented overflow after the period.
- Attach a simple hour summary.
Best for: new clients who refuse prepay; project-ish retainers. Cash-flow is weaker — price that risk in.
Pattern C — Split deposit
- 50% at start of period, 50% mid-period or on delivery milestones.
- Still track the full pool.
Best for: larger retainers where full prepay feels heavy to the client.
Most solos should prefer Pattern A once trust exists. Getting paid faster is a system — see our pay-faster guide.
Time tracking that makes retainers sane
Even flat retainers need logs.
Why
- You know when you are at 80% of the pool
- Overflow conversations stay factual
- You can raise the fee with evidence next quarter
- You protect yourself when the client forgets how much was asked
How
- One project per retainer month or one ongoing project with monthly tags — pick a convention and stick to it.
- Billable flags for included work; separate overflow project once approved.
- Non-billable for your sales/admin (do not hide overhead inside the client pool). See billable vs non-billable.
- Weekly glance at remaining hours — not a month-end surprise.
Tools: Toggl/Clockify for capture; Harvest when you want invoices from unbilled time in one loop.
Caps, soft warnings, and overflow
| Threshold | Action |
|---|---|
| 50% | Optional sanity check |
| 80% | Message client: remaining hours + priority list |
| 100% | Stop unpaid overflow; offer T&M / expand retainer / defer work |
| Post-approval overflow | Track in a clearly named overflow project; invoice at agreed rate |
Never silently work past the cap and then argue. Never silently invoice overflow without the written rule.
Rollover: decide explicitly
| Policy | Pros | Cons |
|---|---|---|
| No rollover | Clean accounting; encourages use | Clients may feel punitive |
| Cap rollover (e.g. max 25% one month) | Fair middle | Needs tracking discipline |
| Full rollover | Client-friendly | You become a bank of unpaid future work |
State the policy on every estimate. If you allow rollover, track remaining banked hours in the same system as the timer — a sticky note will fail.
Invoice line shapes that AP accepts
Prefer
November advisory retainer — includes up to 10 hrsOverflow hours Nov 18–22 — 3.5 hrs @ agreed rate (email approval 2026-11-17)Retainer period: 2026-11-01 → 2026-11-30
Avoid
Services- Mixing three months of mystery work into one line
- Attaching raw private task titles with venting
If the client wants a timesheet, export billable-only detail for the period and attach it. Keep the PDF boring.
Tooling shortlist (verify current features)
- Wave — free-first invoices for prepaid retainers; pair with a timer
- FreshBooks / Harvest — stronger when hours and reminders are central
- PayPal Invoicing — fine for collection; weaker as a practice OS
- QuickBooks — when books depth matters more than retainer UX
Process beats brand. One system of record for invoice numbers.
Mini workflows (composite)
Workflow 1 — Designer, 12-hour monthly pool, billed in advance
Invoice on the 25th for the next month. Track in Harvest/Toggl. Soft warning at 10 hours. Overflow only after Slack approval. Month-end: one-line usage email + optional timesheet.
Workflow 2 — Developer, access retainer, no hour promise
Flat fee for defined response windows and a backlog groomed weekly. Still track time privately for profitability. If weekly load exceeds a soft internal cap three times, renegotiate scope or fee — do not martyr quietly.
Workflow 3 — Coach, hybrid
Base retainer for group calls; 1:1 overflow at T&M. Separate projects so the invoice never blends pools.
Common retainer failures
| Failure | Fix |
|---|---|
| “Unlimited revisions” | Cap rounds or hours; define acceptance |
| Working past cap unpaid | 80% warning ritual |
| Rollover ambiguity | Write the rule; track banked hours |
| Invoicing late every month | Calendar the send date; prefer prepay |
| No logs “because it’s flat” | Track anyway for your business |
| Scope via DM forever | Route requests into a single backlog |
One-afternoon retainer setup
- Choose model (hours pool vs access vs deliverable).
- Write fee, cap, overflow, rollover, cadence.
- Create tracker projects + invoice template lines.
- Put send date and 80% review on the calendar.
- Dry-run one month with a friendly client or yourself.
- Save a one-page SOP for future-you.
FAQ
Should every retainer include hours?
No — but if it does not, define deliverables or response rules so “access” is bounded.
Do I send a timesheet every month?
Only if the client or contract needs it. Many prefer a short usage summary; keep detail available.
Can I raise a retainer mid-year?
Yes with notice and evidence from your logs. Do not ambush.
Is this legal advice?
No. Use a proper agreement for your jurisdiction.
Affiliate links?
None by default.
Bottom line
Retainers work when cash timing, hour caps, and overflow rules are designed before the work starts — then enforced with calm tracking and boring invoices. Prepay when you can; warn at 80%; never invent unlimited labor. Time logs are not bureaucracy; they are how freelancers keep retainers profitable and relationships adult. Pair the habit with a reliable invoice cadence and you will renegotiate from data, not resentment.