Retainer terms
A note of the agreed monthly amount, retained hours or scope, billing day, and payment terms.
Freelance finance · Retainers
Keep retainer billing records clean, month after month
A monthly retainer looks simple until month four, when you can't remember whether the client used their full 20 hours in March, whether the April invoice was paid, or what the scope was when you signed. Without one consistent record per month, retainers quietly drift over-serviced and under-billed. Cash Workspace gives you one per-client retainer folder where every month's invoice, amount, status, and a manual note of hours used vs. retained live side by side.
The problem
Why retainer records slip out of sync
Retainers repeat every month, so it's easy to assume they take care of themselves. They don't — the same fields have to be recorded each cycle or the picture blurs.
- You can't recall whether the client used all 20 retained hours last month or only 11.
- Two or three months of retainer invoices are 'probably paid' but never marked.
- Scope crept — extra requests were done but never noted against the retainer.
- At renewal you have no month-by-month record to point to when discussing the rate.
- A retainer invoice for one client got mixed in with project invoices for another.
The workflow
Record each retainer month the same way
Set up one folder per retainer client, then repeat the same short routine on the same day each month.
- 1
Set up a per-client retainer folder
Create one folder per retainer client and note the agreed monthly amount and retained hours or scope at the top.
- 2
Record the invoice on billing day
On your fixed billing date, record that month's retainer invoice with its number, amount, issue date, and due date.
- 3
Note hours used vs. retained
Add a manual note of how much scope or how many hours were actually used that month against what was retained.
- 4
Set and update the status
Mark the invoice sent, then partially paid, paid, or overdue as the month progresses.
- 5
Review before renewal
Each quarter, scan the folder so you can see months that ran over or under the retained scope before any rate conversation.
Record structure
What to record for each retainer month
A consistent set of fields per month turns a retainer into a record you can actually read back.
- Billing month
- The month the retainer covers, e.g. March 2026, so cycles never overlap.
- Retainer invoice number
- The structured invoice number for that month's retainer charge.
- Monthly amount
- The agreed retainer fee and currency for the month.
- Retained scope or hours
- What the retainer entitles the client to that month, e.g. 20 hours or a defined deliverable set.
- Hours or scope used
- A manual note of what was actually delivered, so over- and under-use is visible.
- Status
- Sent, partially paid, paid, or overdue, updated as payment comes in.
- Issue and due dates
- When the retainer invoice went out and when payment is due.
- Notes
- Any out-of-scope requests, pauses, or agreed carry-over for the month.
Example setup
An example retainer folder
One way to structure a single retainer client inside your workspace.
Monthly retainer invoices
Each month's retainer invoice in date order with amount, status, and dates.
Hours-used notes
A short note per month of scope or hours used vs. retained, plus any out-of-scope work.
Common mistakes
Mistakes to avoid
- Skipping the hours-used note, so you can't tell an over-serviced month from a quiet one.
- Leaving retainer invoices unmarked, so 'probably paid' months pile up.
- Mixing retainer invoices in with one-off project invoices for the same client.
- Forgetting to record out-of-scope requests that should have been billed separately.
- Never reviewing the folder before renewal, so rate talks rely on memory.
How it helps
How Cash Workspace helps
One folder per retainer client
Keep every month's retainer invoice, amount, and status together in a single per-client folder.
Manual scope notes
Note hours or scope used vs. retained each month yourself, so the record reflects what really happened.
Clear statuses every month
Mark each retainer invoice sent, partially paid, paid, or overdue and update it as payment arrives.
Related
Related freelance finance workflows
Recurring invoice checklist
Run the same checklist each time a recurring invoice is due.
Client contact and rate records
Keep each client's agreed rate and contact details in one place.
Monthly finance routine
Fold retainer billing into a repeatable monthly close.
Unpaid invoice tracker
Organize any unpaid retainer invoices so follow-up is simple.
All finance workflows
Browse the full Cash Workspace workflow library.
FAQ
Retainer billing records FAQ
- Does Cash Workspace calculate hours used against the retainer?
- No. You record the retainer amount and add your own note of hours or scope used vs. retained; Cash Workspace keeps those records together so you can read them back, but it does not compute usage for you.
- Can I keep separate records for retainer and project work for the same client?
- Yes. You can keep the monthly retainer invoices in the retainer folder and record any one-off project invoices separately, so the two never blur together.
- How do I track whether a retainer invoice was paid?
- Set a status on each month's invoice — sent, partially paid, paid, or overdue — and update it as payment comes in. Cash Workspace does not sync with your bank, so you mark payments yourself.
Organizing help — not tax, accounting, or legal guidance
Cash Workspace is a free workspace for organizing invoices, expenses, receipts, clients, and documents. This page is organizing guidance only — not tax, accounting, legal, or bookkeeping guidance. Cash Workspace does not connect to your bank, does not scan or read your receipts for you, and does not move or collect payments. Whether an expense is deductible depends on your situation, so confirm it with a qualified accountant or tax professional.
Keep every retainer month in one folder
Start a free workspace and record each retainer invoice with its amount, status, and a note of hours used, so renewal conversations rest on records instead of memory.