Hourly Rate Invoice Template
Updated 2026-10-06
An hourly invoice gets questioned more than a flat-fee one, simply because there’s more surface area to ask about — how many hours, at what rate, doing what. Showing the breakdown up front heads off most of that back-and-forth.
What belongs on it
- Hours and rate shown separately, not pre-multiplied into one number — “14.5 hrs @ $85/hr — $1,232.50” lets the client verify the math themselves, which “Development work — $1,232.50” doesn’t
- A description per time block, if your hours span different kinds of work — “8 hrs — frontend implementation” and “6.5 hrs — bug fixes and QA” as separate lines, rather than one combined total, especially if different work was scoped or rated differently
- The billing period the hours were logged in — “Hours logged Sept 1–15, 2026” avoids any confusion with a previous or future invoice
- Rounding convention, if you round to the nearest quarter or half hour — stating this once (in your terms, or a one-line note) avoids a client re-adding your hours and getting a slightly different total
- Overtime or rush rates, as their own line item, if they applied — don’t blend a higher rate into the average; show the standard-rate hours and premium-rate hours separately
Common mistakes
No hours shown, only a total dollar amount. This is the single biggest driver of back-and-forth on hourly invoices — always show hours × rate, not just the result.
Mixing billing periods on one invoice without saying so. If an invoice includes hours from two different weeks or sprints, label which hours belong to which period.
Inconsistent rounding. If you bill in 15-minute increments sometimes and round to the nearest hour other times, a client who’s tracking your invoices over time will notice and may ask about it — pick one convention and state it.
Make a Hourly Rate Invoice
Pre-set for this use case below — change anything you like.
Doing this every month? North Invoice tracks invoices, expenses, and maps everything to your T2125 or Schedule C at tax time.