Quick answer

An hourly invoice needs itemized time, a clear rate, and payment terms with a due date. Getting paid on time is a separate discipline: specific line items that prevent disputes, terms like Net 15, an upfront deposit, and a late fee that gives the due date teeth.

This guide is written for freelancers and small teams that bill clients by the hour who want time tracking to support better planning, billing, reporting, and project decisions.

What an hourly invoice must contain

Every hourly invoice needs the same core parts, and missing one is a reason for a client to delay. Include your details and theirs, a unique invoice number, the date, an itemized list of the work with hours and rate, the total due, accepted payment methods, and explicit payment terms with a due date. That last part is the one people skip and the one that decides when you get paid.

Put the total due where the eye lands first. A client scanning an invoice on their phone should see what they owe and when it is due without reading a table. Everything else supports that number; do not bury it.

  • Your name or business, the client's details, and a unique invoice number
  • Itemized work with hours, rate, and a description for each line
  • The total due, stated prominently
  • Payment terms and a specific due date, not just "thanks"
  • How to pay: bank details, card link, or payment platform

Turn tracked time into clear line items

A single line reading "Consulting, 40 hours" is an invitation to question the bill. Group the hours by project or task and give each group a plain description of what was delivered. "Homepage redesign, 12 hours" and "Checkout bug fixes, 6 hours" tell the client what their money bought, and a client who understands the charge pays it faster.

This is far easier when the time was tracked against clients, projects, and tasks as the work happened. Then the invoice is a summary of records that already exist, not an act of reconstruction the night before. If you are rebuilding the month from memory, you are both losing hours and producing the vague line items that trigger disputes.

Payment terms that actually get you paid

Payment terms are the clause that sets when money is due, and vague terms produce vague payment behavior. "Due upon receipt" asks for immediate payment. "Net 15" and "Net 30" give the client 15 or 30 days. Shorter terms get you paid sooner, and for most freelance and small-team work Net 15 is a reasonable default that respects the client without financing their cash flow for a month.

State the exact due date on the invoice, not just the term. "Net 15" means nothing to a client who has to do the arithmetic; "Due August 5, 2026" is a date they can put in a calendar. Removing that small friction measurably speeds up payment.

Deposits, late fees, and the 71 percent problem

With late payment hitting most independent professionals, the invoice needs teeth and the engagement needs a deposit. Requesting 25 to 50 percent upfront before starting work is standard practice: it secures the client's commitment, protects your cash flow, and filters out the clients who were never going to pay well. A client who will not put down a deposit is telling you something.

A late fee turns a due date from a suggestion into a term. A common clause is 1.5 percent per month on overdue balances, stated on the invoice from the start so it is never a surprise. You will rarely need to enforce it; its job is to make paying on time the path of least resistance. Check that late fees are permitted and reasonable in your jurisdiction before relying on the clause.

When hourly invoicing is the wrong model

Hourly billing is honest and low-risk, but it punishes you for getting faster and caps your income at your available hours. If you have done the same kind of project enough times to estimate it reliably, a fixed price often pays better and removes the line-by-line scrutiny that hourly invoices attract in the first place.

Reach for hourly when scope is genuinely unknown or likely to change, so the client carries the estimation risk fairly. Reach for fixed pricing when you can predict the work. The invoicing mechanics in this guide apply either way, but do not default to hourly out of habit when a flat fee would serve both sides better.

Where Zeitio fits

Zeitio helps teams connect tracked hours to clients, projects, tasks, reports, approvals, and invoices so time data becomes useful business context instead of another spreadsheet.

Start with simple time entries, review them weekly, and use the data to improve project planning, billing accuracy, and team workload decisions.

Compare Zeitio pricing or create a workspace to try the workflow.

Further reading

FAQs

What should an hourly invoice include?

Your details and the client's, a unique invoice number, the date, itemized work with hours and rate, the total due stated prominently, accepted payment methods, and explicit payment terms with a specific due date.

What are good payment terms for hourly work?

Net 15 is a reasonable default for freelance and small-team work: it gets you paid within two weeks without financing the client's cash flow. Use "due upon receipt" for faster payment, and always state the exact due date, not just the term.

Should freelancers ask for a deposit?

Yes. Requesting 25 to 50 percent upfront before starting is standard practice. It secures the client's commitment, protects your cash flow, and filters out clients unlikely to pay well, which matters when most independent professionals face late payments.

Can I charge a late fee on an invoice?

Commonly yes, with a clause such as 1.5 percent per month on overdue balances stated on the invoice from the start. Its main purpose is to make on-time payment the easier choice. Confirm that late fees are permitted and reasonable in your jurisdiction first.

How do I avoid invoice disputes?

Group hours by project or task with a plain description of what each covered, rather than one large undifferentiated line. Clients pay charges they understand faster, and specific line items are far easier to produce when time was tracked against projects as the work happened.