From timesheets to client invoices: how agencies stop leaking billable hours
Updated 2026-07-08 · For founders, delivery managers and accountants at IT services companies
The quiet leak between delivery and billing
In most 5–50-person services companies, delivery and billing live in different tools owned by different people. Engineers log time in one place (or don't), the delivery manager keeps allocations in a spreadsheet, and once a month an accountant reconstructs what happened from Slack threads and memory. Every gap in that chain is money: hours nobody logged, hours logged against the wrong project, people who joined a project mid-month and never appeared on the invoice at all.
Industry surveys of professional-services firms regularly put revenue leakage from poor time capture and billing handoffs in the single-digit percents of revenue — at a 10-person shop billing $50/hour, even 3% is roughly a junior developer's salary, silently gone.
Pick the right billing model per project — and write it down
Time & materials (T&M). Invoice = logged billable hours × rate. Fair for evolving scope; demands disciplined time tracking, because every unlogged hour is unbilled revenue.
Retainer. A flat monthly amount for an agreed capacity. Predictable cash; the risk is silent overservicing — you still need timesheets to see when a $6,000 retainer consistently consumes $9,000 of work.
Fixed price. One agreed total for a defined scope. Time tracking stops driving the invoice and starts answering "are we still in margin?" — a different question, but one you still can't answer without the hours.
The failure mode isn't choosing wrong — it's not recording the choice. When the billing model lives in someone's head, the person generating invoices guesses, and retainer clients get T&M invoices (or worse, the reverse).
Where billable hours actually leak
Unlogged time. The classic. Fix is cultural + mechanical: weekly is too late to remember Tuesday; make logging take seconds and chase gaps weekly.
Orphan hours. Someone helped a project for a week without a formal assignment — their hours exist but no invoice line picks them up. Your billing step must sweep all logged hours on a billable project, not just the planned people.
Mid-month joiners and roll-offs. Plans drift; if invoices are generated from a stale allocation snapshot instead of actuals, drift becomes leakage.
Late invoices. Every week between delivery and invoice worsens collection odds and stretches your cash cycle. The firms that get paid fastest invoice within days of month-end, every month, boringly.
Estimates billed as facts. If a line is based on planned hours because actuals aren't in yet, mark it — silent estimates erode client trust the first time they audit an invoice.
A monthly billing ritual that takes an hour
Close timesheets for the month; chase the 2–3 people with gaps (it is always the same 2–3 people).
Generate draft invoices per project from actual billable hours — T&M from hours × rate, retainers at their flat amount, fixed-price per its schedule.
Review drafts against the plan. Overservicing on retainers, surprise orphan hours, anything flagged as an estimate — decide, adjust the line, note why.
Send, with due dates and your bank details on the document — then track receivables as statuses (draft → sent → paid → overdue), not as a feeling.
Look at margin per project while the month is fresh: revenue vs the cost of the hours that earned it. One consistently underwater project is a pricing conversation, not a delivery failure.
How Helia HR does this
Helia HR connects the chain end to end — the same people, projects and assignments that drive capacity planning also drive billing:
Timesheets tied to projects and assignments, with billable flags on both people and projects, so billable hours are computed honestly.
Per-project billing models — T&M, monthly retainer, or fixed price — recorded on the project, so invoice generation follows the contract, not memory.
"Bill a month" in one step: draft invoices for every billable project at once, idempotent (safe to re-run), sweeping orphan hours so helpers don't vanish from revenue; lines based on planned hours are explicitly flagged as estimates, and drafts stay editable before sending.
Numbering, VAT, due dates, PDF, email, receivables — plus per-project profitability and margins, FX-consolidated when clients pay in different currencies.
FAQ
Do we need timesheets if all our clients are on retainers?
Yes — not to build the invoice, but to see whether each retainer is profitable. A retainer without hour tracking is a fixed price with unlimited scope.
When should invoices go out?
Within the first 2–3 business days after month-end (or the milestone). Consistency matters more than speed: clients pay predictable vendors faster.
Spreadsheet invoicing works today — when does it stop working?
Usually at the second concurrent failure: two projects billing in the same week, a person split across three clients, or the first month someone else has to run billing and can't reconstruct the rules.
Run HR and delivery ops in one system
Helia HR combines the HR basics with the capacity matrix, bench view, timesheets and client invoicing IT services teams actually run on. Start free, no card. GDPR-grade security, role-gated PII, audit-logged access.