How to Invoice for Hours Worked (Hourly Invoicing Guide)

Billing by the hour sounds simple: you worked, you multiply hours by your rate, you send the invoice. In practice it's where most disputes start. Was that 6 hours or 6.5? Do you bill the 20 minutes you spent on a phone call? Why does the client think the total is too high when every line is accurate?

This guide covers the whole loop: how to track your hours so the numbers are defensible, what an hourly invoice needs, how to structure line items so each task reads as hours × rate = amount, how to handle rounding and minimum increments, when hourly beats fixed-fee, and how to get the invoice approved without a back-and-forth. By the end you'll be able to turn a week of work into a clean invoice in a few minutes.

Track your hours first — the invoice comes second

You can't invoice hours you didn't record. The biggest cause of underbilling among hourly freelancers is reconstructing the week from memory on Friday afternoon. You always round down, you always forget the small tasks, and you leave money on the table.

Two ways to track:

Manual. A spreadsheet or notebook where you log start/stop times per task. Cheap and flexible, but only as good as your discipline. Works if you bill in big blocks (half-days, full days).
Time-tracking software. Toggl, Harvest, Clockify, and similar tools run a timer you start and stop per task, then export a timesheet. Worth it the moment you bill in sub-hour increments or juggle several clients, because the timestamps are your evidence if a client questions a line.

Whichever you use, log the task description as you go, not only the duration. "2.5 hrs" means nothing to a client three weeks later. "Homepage hero section — layout + 2 revisions, 2.5 hrs" gets approved without questions. Which of those hours count as billable in the first place, and how to price for them, is in the guide to billable hours.

Pick a billing cycle

Decide how often you invoice before the first hour goes on the clock. The cycle shapes your cash flow and the client's:

Weekly: tight cash flow, good for new clients you don't fully trust yet, or short engagements. More admin overhead (52 invoices a year).
Biweekly: a common middle ground for ongoing hourly contracts.
Monthly: least admin, standard for established clients, but you're floating up to a month of work. Pair it with reasonable payment terms so you're not waiting 60 days for cash.

State the cycle in your contract so there are no surprises: "Invoiced biweekly, Net 15."

What an hourly invoice needs

Everything a normal invoice needs (see the 10-field checklist), plus a few hourly-specific items:

Your hourly rate, stated explicitly, even if it's the same on every line. The client should never have to divide the amount by the hours to reverse-engineer your rate.
The billing period, e.g. "Hours worked May 16–31, 2026". This anchors the invoice to a span of time and stops the "is this the same work as last month?" confusion.
Hours per line item, broken down by task, not lumped into one "consulting, 40 hrs" line (more on that below).
Your rounding policy: one line in the footer if you round to an increment. "Time billed in 15-minute increments."
A timesheet or breakdown, either as line items on the invoice itself or as an attached detail sheet.

Structuring line items: hours × rate = amount

The core of an hourly invoice is the line-item table. Each row is one task, and each row should make the math obvious: the hours you worked, your rate, and the two multiplied together.

Don't collapse a month into a single "Development — 40 hrs" line. It gives the client nothing to approve and everything to question. Break the work into the tasks the client recognizes from your conversations. Here's a clean two-week breakdown:

| Description | Hours | Rate | Amount | |---|---|---|---| | Homepage redesign — hero + layout, 2 revisions | 6.5 | $85 | $552.50 | | Product page template (responsive) | 8.0 | $85 | $680.00 | | Checkout flow bug fixes | 3.25 | $85 | $276.25 | | Client calls + async updates (Slack, email) | 2.5 | $85 | $212.50 | | Deployment + QA on staging | 1.75 | $85 | $148.75 | | Subtotal | 22.0 | | $1,870.00 |

A few things this does well:

Every line shows its hours. The client can sanity-check each task against what they remember asking for.
Communication is its own line. Calls, Slack, and email are billable if they're work. Burying them is how you end up underbilling. Naming them sets the expectation that your time on the relationship counts.
The subtotal sums the hours as well as the dollars. "22.0 hrs across two weeks" is an easy number for a client to accept; a bare "$1,870" invites scrutiny.

If you bill multiple rates (e.g. design at one rate, strategy at another), add a Rate column that varies per line and group the lines by rate. Don't average rates into one blended number. Clients want to see what they're paying for the expensive work versus the cheap work.

Rounding and minimum increments

Nobody bills to the literal second. You round, so decide the increment and whether you disclose it.

The common increments:

6-minute (0.1 hr): the legal/accounting standard. Precise, slightly fiddly. Overkill for most freelancers.
15-minute (0.25 hr): the freelance sweet spot. Easy mental math, fair to both sides.
30-minute (0.5 hr): coarser; fine for big-block work, generous-feeling to clients on small tasks.

Two rules keep rounding fair:

Round per task, not per day, and definitely not per invoice. Rounding each 10-minute task up to 15 minutes across 12 tasks adds an hour you didn't work. Round the day's total for a task, or use a real timer.
State the policy on the invoice. A single footer line ("Time billed in 15-minute increments") means the client agreed to your rounding up front instead of discovering it later.

Hourly vs fixed-fee: when each is right

Hourly isn't always the answer.

Bill hourly when:

The scope is unclear or likely to change ("we'll know more after the first sprint").
The work is open-ended: ongoing maintenance, support, ad-hoc requests.
You're new to the client and neither side can estimate the job confidently yet.
The client keeps adding "small" requests. Hourly makes scope creep cost them, not you.

Bill fixed-fee when:

The deliverable is well-defined ("a 5-page marketing site").
You're fast and good. Fixed-fee rewards efficiency; hourly punishes it by paying you less for finishing early.
The client wants budget certainty and you can scope confidently.

A common hybrid: fixed fee for the defined project, hourly for anything outside the agreed scope. For larger projects you can also break the work into milestone billing, where each milestone is its own invoice. Many freelancers run hourly for new clients, then switch to fixed-fee or retainers once they can estimate the work reliably.

Presenting the timesheet

For hourly work, the timesheet is your evidence. How much detail to show depends on the client and the trust level:

Line items only: the table above, tasks rolled up. Fine for established clients who don't audit.
Line items + attached timesheet: the invoice shows summarized tasks; a separate sheet (or a second page) lists every timer entry with dates. Best for new clients, larger invoices, or anyone who's ever questioned a total.
Full daily log: date, task, start/stop, duration. Necessary for some corporate clients and most agency-of-record relationships.

Match the detail to what the client expects. A startup founder wants the summary; a corporate procurement team wants the daily log with timestamps. When in doubt, attach the detail. It's far easier to include it than to reconstruct it after a dispute.

Getting it approved and paid

A few habits that turn "I'll review it" into "paid":

Send promptly. Invoice the day the billing period closes, while the work is fresh in the client's mind. A monthly invoice that lands three weeks late reads like a surprise.
Summarize in the email body. "22 hours across two weeks: homepage, product template, checkout fixes, deploys. Detail and timesheet attached. Net 15, due June 20." The client shouldn't have to open the PDF to know what they're approving.
Pre-empt the big numbers. If this period ran high because of extra requests, say so before they ask: "Higher than usual. The checkout rework you approved on the 22nd added ~6 hours."
Make payment frictionless. Bank details and accepted methods on the invoice (see payment terms). The faster they can pay, the faster they do.
Follow up on a cadence. Net 15 unpaid at day 18 gets a polite nudge. Hourly clients especially need a rhythm, since the next period's hours are already piling up.

The fastest way to ship a clean hourly invoice is to start from a freelance invoice template you've used before (your details, rate, and rounding policy already filled in) and swap the line items. Or generate one from scratch with InvoicePeak's free invoice generator: add each task as a line item with hours and rate, and the totals calculate themselves.

FAQ

How do I round hours on an invoice?

Pick an increment (15 minutes, or 0.25 hr, is the freelance standard) and round each task to it, not each day or the whole invoice. State the policy in a footer line so the client agreed to it in advance. Rounding individual sub-tasks up repeatedly is how you accidentally overbill.

Should I bill for calls, emails, and Slack messages?

Yes, if they're work. A 30-minute strategy call is billable; so are substantive emails and async updates. Give communication its own line item rather than hiding it inside other tasks. Many freelancers set a minimum increment (e.g. 15 minutes) per contact so a flurry of "quick questions" doesn't become free labor.

How detailed should my line items be?

Detailed enough that the client recognizes each task from your conversations, but not a minute-by-minute log on the invoice face. "Homepage redesign — hero + 2 revisions, 6.5 hrs" is the right altitude. Keep the granular timer entries in an attached timesheet if the client wants them.

What's a good billing cycle for hourly work?

Biweekly is the common middle ground. Weekly tightens your cash flow and suits new or risky clients; monthly is lowest-admin but floats up to a month of unpaid work. Whatever you choose, write it into the contract and pair it with sensible payment terms.

Hourly or fixed-fee — which should I use?

Hourly when scope is unclear, open-ended, or prone to change. Fixed-fee when the deliverable is well-defined and you're efficient (fixed-fee rewards speed; hourly penalizes it). A common hybrid is fixed-fee for the defined project plus hourly for out-of-scope requests. For phased projects, consider milestone billing.

Do I need to attach a timesheet?

Not always. Established clients usually accept summarized line items. New clients, large invoices, and corporate procurement teams often expect a detailed timesheet with dates and durations. When unsure, attach it. Including the detail upfront is far easier than reconstructing it during a dispute.

How do I handle a client who says the hours are too high?

Lead with the timesheet. That's why you tracked. Walk through the tasks and the hours each took, and point to anything they approved mid-period. If a specific line is fuzzy, it's usually cheaper for the relationship to adjust it than to win the argument. From then on, send invoices promptly and summarize in the email so high totals are never a surprise.