This web development invoice example shows how web developers and web designers bill a real project: frontend and backend hours, project management, and hosting passed through at cost, with a 50% deposit and the balance due at launch. Use it as a reference for your first invoice, or copy the layout into your own.
Use the example above as a reference, then enter your actual business, customer and job details here. Start without an account; downloads follow the free-tool limits. Saving, tracked sending and reminders require an account.
Your business name and contact details, the client's name, a unique invoice number, issue and due dates, line items for each milestone or block of hours with rates, pass-through costs such as hosting or licences, tax where it applies, the total amount due and your payment terms.
Fixed fees suit well-scoped builds with clear milestones; hourly rates suit maintenance, support and research-heavy work. Many developers quote a fixed fee per milestone and bill approved change requests hourly.
Show them as separate lines with the supplier and the period covered, and say whether they are billed at cost or include a markup. If the client should own the hosting account, have them pay the provider directly.
It depends on where you are registered. In Australia you add 10% GST once registered (compulsory from $75,000 annual turnover). US states treat web development differently, and UK and EU VAT rules apply there — check your local rules before adding tax.
Templates for agencies, freelancers and specialists billing retainers, campaigns and project work.
Use the template as a starting layout, then replace its example information with the actual agreed work. The details below help you decide what to enter and what to check before sending.
Separate implementation, support and third-party costs. For milestones, define the deliverable and acceptance point; for time-based work, identify the service period and agreed rate. Keep a change request separate from a defect correction already included in the scope.
Include the project or support-ticket reference, service period and approved milestone. Check the legal billing name and delivery contact against the accepted work. Keep the statement of work, accepted change requests and time or delivery summary available to resolve questions. An invoice records the charge; it does not replace the underlying approval or supporting documents.
This example bills a completed milestone plus support outside its agreed scope. If hosting or licences are reimbursable, identify the supplier cost and period rather than adding an unexplained recurring amount.
| Description | Quantity | Rate | Amount |
|---|---|---|---|
| Implementation milestone — accepted release | 1 | 1,800.00 | 1,800.00 |
| Additional support hours — authorised | 3 | 90.00 | 270.00 |
| Example subtotal | 2,070.00 | ||
Copying last month’s support period into a new invoice obscures what was delivered. Check tickets, hours, subscription periods and whether any prepaid support balance applies.
If the client disputes completion, use the agreed acceptance criteria and delivery record. Keep the billing tool separate from issue tracking, release management and technical acceptance; invoice status alone does not prove that software was accepted.
The free browser tool prepares the document. Saving customers, sending tracked invoices and managing reminders require an account and are subject to plan limits. Payment status needs accurate payment records; an invoice view alone does not confirm payment.