What to include on a web development invoice
- Hours per feature or task, not one big “development” line.
- Your rounding rule, like 15 minute increments, if you round.
- Pass-through costs (hosting, plugins, licenses) as separate lines, with or without a markup you agreed on.
- The billing period, for example “May 1 to May 31”, on retainers.
And the basics every invoice needs: a unique number, the issue date, when it is due, your details and the client’s, and how to pay.
A tip for web developers
Clients rarely dispute hours when they can see the breakdown. Keep a time log with a note per entry and attach it, or offer it on request.
Questions
What should a web development invoice include?
Your details and the client’s, an invoice number, the issue and due date, a line for each piece of work, the total, and how to pay. For web developers it also helps to include: hours per feature or task, not one big “development” line; your rounding rule, like 15 minute increments, if you round; pass-through costs (hosting, plugins, licenses) as separate lines, with or without a markup you agreed on; the billing period, for example “May 1 to May 31”, on retainers.
Is this template free?
Yes. Edit it here and download a PDF. There is no account and no watermark, and your details stay in your browser.
Invoice from your tracked time
Sheaf tracks hours per client and project and builds the invoice for you, with a link your client can open. Free during beta.