Web development invoice
Invoice template for web developers: feature implementation, responsive build, and deployment and checks. Fill it in online or download Excel or Word.
Templates by industry
- Feature implementation
- Responsive build
- Deployment and checks
Preparation guide
Example workflow
Confirm scope and quantities
Example: reconcile the approval and work record for "Feature implementation" to establish the quantity for this invoice.
Record delivery and acceptance
Check completion for every line, including "Deployment and checks". Deliver the agreed test results and configuration notes, and assign owners for outstanding items.
Send the billing record
Send the final charges, delivery reference and due date to the customer, then reconcile payment against the invoice number.
Web projects are often invoiced by milestone, and each milestone invoice should show that a defined piece of work is finished. This template does that with three lines: the features built, the work to make them behave on phones, tablets and desktops, and the release to the live server with the checks that followed. Tying each invoice to its quotation or milestone stops the client paying twice for one feature, or not at all for work added along the way.
Fields to prepare
- Deliverables and line items
- Feature implementation, Responsive build, Deployment and checks: record the quantities actually supplied and the service period.
- Feature implementation
- Name the features delivered in this milestone, such as a booking form with email confirmation and a member login, and the ticket or milestone numbers they match.
- Responsive build
- Give the breakpoints or devices tested, for example phone, tablet and desktop widths, and which pages or templates were made responsive.
- Deployment and checks
- State the release date, the environment deployed to and what was checked afterwards, such as forms, redirects and page speed, so the client can sign off.
- Environment and dependencies
- Record target systems, integration counts, data volume and who supplies test access.
- Acceptance and support
- Set acceptance scenarios, the review window, support duration after handover and excluded work.
- Scope to agree
- List the features built and the browsers supported, the environment deployed to, and how change requests are handled after handover.
Before sending
- Does “Feature implementation” show the quantity actually supplied, not the quantity first quoted?
- Is “Responsive build” charged at the rate the customer agreed to, with any change approved?
- Is “Deployment and checks” finished and accepted, or does it belong on a later invoice?
Show 3 more
- Separate third-party service charges from implementation fees.
- Agree who handles the production transition and what recovery work is included if it fails.
- Match completed work to the order or approval record, and confirm the payment due date and amounts already received.
Worked example with sample figures
The figures below are invented to show how the template adds up: 3 lines in USD, with an example tax rate of 8%.
| Item | Quantity × unit price | Amount |
|---|---|---|
| Feature implementation | 20 × $95.00 | $1,900.00 |
| Responsive build | 2 × $450.00 | $900.00 |
| Deployment and checks | 12 × $60.00 | $720.00 |
| Subtotal | $3,520.00 | |
| Sales tax (8%) | $281.60 | |
| Total | $3,801.60 | |
Net amount $3,520.00, sales tax $281.60, total payable $3,801.60.
What the document must show
The details an invoice has to show, and why each one matters, are set out in the guide below.
The sales tax depends on where the work is supplied, so set the rate that applies to your customer before sending.
Official rate reference: US government: state and local taxes
Full requirements: How to write an invoice: a step-by-step example
Frequently asked questions
How do I bill changes the client asked for during the build?
Keep them off the milestone lines. Add each approved change as its own line with the date it was requested and its estimated or actual hours, so the original scope and the additions stay separate in both the invoice and the project record.
Should domain, hosting or plugin costs appear here?
Only if you bought them for the client and your agreement says you pass them on. Bill them at cost with the renewal date, and make sure the accounts are in the client's name or will be transferred, because they keep renewing after your work ends.
How is the sales tax worked out on this invoice?
The worked example above uses an example rate of 8%: $281.60 on a net amount of $3,520.00, for a total of $3,801.60. The editor recalculates all three when you change a quantity, a price or the country.
Can I use it in another language or currency?
Yes. The document language can be set to any of 33 languages, and changing the country setting updates the currency, the date format and the tax rate.
Can I email it to the customer?
Yes, from your own mail app. With a free account, the editor’s download menu offers Email this document, which opens your mail app with a message about the document already written. QuoteBill sends nothing itself, so save the PDF and attach it before you send.
Read next
Reading for the Web development invoice: How to write an invoice: a step-by-step example and Credit note vs invoice (and credit memo): how to issue one. The VAT and GST calculator works out the tax line for you.