A freelance web developer invoice template should make the work delivered, amount due, and next payment step immediately clear. This guide shows how to bill fixed-price website projects, milestones, retainers, hourly work, change requests, and reimbursable expenses without losing the connection between the approved estimate and the final invoice.
Overview
Web development rarely follows one billing pattern. A small landing page may be quoted as a fixed project, while a larger build may be divided into discovery, design implementation, testing, and launch milestones. Maintenance clients may pay for a monthly retainer, and additional fixes may be billed hourly. Your invoice format should reflect that structure instead of combining unrelated work into one vague line such as “website services.”
A useful web developer invoice has four jobs:
- Identify the client, developer, project, and invoice clearly.
- Connect each charge to an approved estimate, milestone, retainer period, or request.
- Separate development fees, changes, expenses, discounts, and tax or VAT where applicable.
- Explain exactly how and when the client should pay.
Use the following structure as a blank invoice template for a new project, or adapt it into an invoice template PDF, Word document, or spreadsheet. For the general required fields and invoice format, see How to Make an Invoice. A broader hourly, fixed-price, and expense layout is also available in this freelance and contractor invoice template.
Web developer invoice template
- From: Your legal or trading name, address, contact details, and tax registration details if relevant.
- Bill to: Client or company name, billing address, contact person, and purchase order or reference number if required.
- Invoice details: Invoice number, issue date, payment due date, currency, and project name.
- Project reference: Approved estimate, proposal, statement of work, milestone name, or retainer period.
- Line items: Description, quantity or hours, unit rate, and line total.
- Adjustments: Approved change requests, expenses, discounts, tax, or VAT.
- Payment instructions: Accepted method, account or payment link, payment terms, and contact for billing questions.
How to estimate
Start with the approved estimate rather than building the invoice from memory. Divide the scope into billable units that a client can recognize and verify. The unit may be a milestone, month, hour, deliverable, or approved expense.
For a fixed-price project, calculate the amount for a milestone as:
Milestone amount = approved project price × milestone percentage
If the contract uses fixed milestone amounts, use those amounts instead of recalculating percentages. Do not apply a percentage merely because it feels convenient; the invoice should follow the agreed commercial terms.
For hourly work, use:
Hourly subtotal = billable hours × hourly rate
Record the date range and a concise description of the work. A time entry such as “12 hours” is less useful than “12 hours — responsive layout implementation and browser testing, 1–15 May.” Keep detailed time records separately if the invoice would become too long.
For a retainer, calculate the recurring charge from the agreed period and included service. State whether unused hours expire, roll forward, or are handled under the contract. If work exceeds the included amount, list the additional hours separately rather than silently increasing the retainer line.
Example line items
| Billing model | Invoice description | Quantity | Rate or amount |
|---|---|---|---|
| Milestone | Milestone 2: CMS implementation and content-entry support | 1 | Agreed milestone amount |
| Hourly | Frontend development and responsive testing, 1–15 May | 18 hours | Agreed hourly rate |
| Retainer | Website maintenance retainer for June | 1 month | Agreed monthly fee |
| Expense | Approved plugin or hosting expense, receipt attached | 1 | Actual reimbursable cost |
For a quote-to-invoice handoff, compare the approved estimate with the work log and change register before issuing the invoice. The quote to invoice workflow can help standardize that transition.
Inputs and assumptions
Before calculating the total, gather the inputs that control the invoice. This prevents a correct arithmetic result from becoming an incorrect bill.
- Commercial model: Fixed price, milestone, hourly, retainer, or a combination.
- Approved scope: Deliverables, exclusions, revisions, support period, and acceptance criteria.
- Rate basis: Hourly rate, day rate, fixed milestone amount, or recurring fee.
- Actual delivery: Completed milestones, billable hours, retainer dates, and accepted deliverables.
- Changes: Written approvals, added hours, revised features, and their agreed prices.
- Expenses: Only costs that the agreement permits you to pass through, with receipts or notes.
- Tax treatment: Apply the tax or VAT treatment appropriate to your business and the transaction. If uncertain, confirm the requirement with a qualified local adviser.
- Payment terms: Due on receipt, a specified number of days after issue, or a date tied to an agreed event.
Use this basic calculation:
Subtotal = fixed fees + hourly fees + approved expenses + approved changes − discounts
Total due = subtotal + applicable tax or VAT
Show discounts as their own line, with a reason or reference when useful. A change-request section is particularly important for web projects because a new page, integration, content migration task, or browser-support requirement can alter both the price and delivery schedule.
Change-request section
Add a separate heading or group of line items such as:
- CR-03 — Add member dashboard filtering, approved 8 May — 6 hours × agreed rate.
- CR-04 — Import additional product records — fixed approved amount.
- Third-party service fee — approved by client, receipt attached.
Do not label unapproved work as a change request. First record the request, impact, price, and approval. If you need a formal approval trail, pair the invoice with a simple approval process; see the invoice approval matrix template.
Worked examples
Example 1: milestone invoice
Assume an approved website project has four agreed milestones. The invoice is for “Content implementation and pre-launch testing,” and the client has accepted that milestone. List the milestone name, completion period, related estimate or statement-of-work reference, and the fixed amount. Add any separately approved expense or change request below the milestone. This gives the client a clear path from deliverable to amount due without requiring a full project audit.
Example 2: hourly maintenance invoice
Assume a client requests maintenance during a defined billing period. Your work log records code updates, dependency review, accessibility fixes, and deployment support. Group related entries by task, then show the hours and agreed rate. For example: “Dependency updates and regression testing — 4.5 hours × agreed rate.” Include the period covered and link the work to the client’s ticket or request number when available.
Example 3: retainer plus overage
List the monthly retainer as one line and any work beyond the included allowance as additional lines. Separate approved expenses from labor. This lets the client see what the recurring agreement covers and what changed during the period. If the retainer is prepaid, the invoice may instead document the next service period and remaining balance according to the agreement.
For payment terms, choose wording that matches the contract: “Due on [date],” “Payment due within [agreed period] of invoice date,” or “Due before work begins.” Include late-payment language only if it is part of your agreement and permitted where you operate. A reminder schedule can be prepared using these invoice reminder templates.
When to recalculate
Recalculate the invoice whenever an input changes, not only when you reach the end of a project. Review it before each milestone invoice, retainer renewal, and final invoice. Also recalculate after a written scope change, a revised hourly total, an approved expense, a discount, a currency change, or a change in tax treatment.
Use this handoff checklist:
- Match the invoice to the approved estimate, proposal, or statement of work.
- Confirm the invoice number, client details, project reference, currency, and dates.
- Verify completed milestones, logged hours, retainer coverage, and accepted deliverables.
- Move every approved change and reimbursable expense into a clearly labeled line item.
- Recalculate subtotal, discount, tax or VAT, and final amount.
- Check payment instructions and due date against the contract.
- Attach receipts, time detail, acceptance notes, or approval records where appropriate.
- Record the issued invoice in your invoice register and schedule a follow-up.
At month-end, reconcile issued invoices, payments, credits, and outstanding balances using a consistent tracker. The month-end reconciliation checklist can support that review. Reusing the same developer billing template while updating its inputs gives each client a familiar document and gives you a repeatable control from estimate through final payment.