How to Invoice as a Freelance Developer: Rates and Terms
Software work is invisible to most clients. They see a working feature or website, but not the planning, debugging, testing and deployment that made it possible. Learning how to invoice as a freelance developer means turning that invisible effort into a clear, defensible bill. It also means choosing a billing model that suits the project, handling scope changes gracefully and setting terms that protect your income. This guide walks through each of those decisions.
Choose a Billing Model First
Developers usually bill in one of three ways. The right choice depends on how well the work is defined and how much risk each side is willing to carry.
Hourly rate
You track time and bill for the hours worked. This suits open-ended work, maintenance and projects where requirements will evolve. The invoice should show hours, rate and a short summary of what was done.
Fixed price
You quote a total for a defined scope. This works when requirements are clear and deliverables are specific. The invoice lists each deliverable or milestone with its price.
Retainer
The client pays a regular amount for an agreed block of time or availability, for example support and small updates each month. The invoice is the same each period, with a note describing the month covered.
Each approach has trade-offs for cash flow and risk. Our guide to hourly vs flat rate invoicing compares them in more depth.
What to Put on a Developer Invoice
Clients are more comfortable paying when they can match the bill to something tangible. Useful line items include:
- Feature or module names, for example "User authentication and password reset".
- Hours and rate, if billing hourly.
- Third-party costs such as hosting, licences or paid APIs, if you buy them on the client's behalf.
- Project management or meetings, if they are billable under your agreement.
- Deployment, handover and documentation.
If you bill by the hour, consider attaching a short time log. It does not have to be elaborate, just a list of dates, tasks and hours. This one habit prevents many billing disputes.
Example: a mixed invoice
Here is an illustrative invoice that combines a fixed-price feature with hourly maintenance. The figures are examples only.
| Description | Quantity | Rate | Amount |
|---|---|---|---|
| Checkout integration (fixed price, milestone 2 of 3) | 1 | 1,500.00 | 1,500.00 |
| Bug fixes and maintenance (hours) | 6 | 60.00 | 360.00 |
| Code review and deployment support (hours) | 2 | 60.00 | 120.00 |
| Hosting reimbursement, October | 1 | 25.00 | 25.00 |
| Total due | 2,005.00 | ||
Good to know: If you charge a currency different from the client's, state the currency on the invoice. Our guide on invoicing in multiple currencies covers the details.
Handling Scope Creep
Scope creep is the quiet enemy of freelance developers. A small request here and an extra feature there can add up to a lot of unpaid work. The solution is a clear agreement and a simple process for changes.
- Define the scope in writing. List features, platforms and what is not included.
- Use a change request. When the client asks for something new, reply with a short estimate and wait for approval.
- Bill changes separately. Add them as their own lines so the original price stays intact.
- Keep communication in writing. A short email recap after calls creates a record.
Tip: Reference the original agreement on every invoice, for example "Per proposal dated 3 March". It reminds the client that the price is tied to an agreed scope.
Payment Terms for Development Projects
Code takes time, so most developers do not wait until the end to be paid. Common patterns include a deposit of 25 to 50 percent upfront, milestone payments tied to delivered features and a final payment on launch. This spreads risk between you and the client, and keeps your cash flow stable. See our guide on deposit and milestone invoicing for step-by-step examples.
For ongoing support, use a retainer with a regular invoice date. If you want to avoid sending the same invoice by hand each month, read about recurring invoices.
Ownership, Handover and Final Payment
Be clear about when the client receives ownership of the code and access to repositories or servers. Many developers state in their contract that ownership transfers on full payment. This gives clients a strong reason to pay on time and protects you if something goes wrong. Intellectual property rules vary by country, so ask a legal professional to review your standard agreement.
Watch out: Avoid handing over production credentials or admin access before the final invoice is settled, unless your agreement says otherwise.
Good invoices for software work answer two questions: what exactly did I get, and why does it cost this much? Make both easy to see.
Working With Clients in Other Countries
Many developers work remotely for clients abroad. When that happens, specify the currency, the payment method and who covers transfer fees. Tax treatment can also differ, so confirm what applies to you with a local tax professional. Our article on how to invoice international clients explains the practical side.
Frequently Asked Questions
Should I bill for meetings and communication?
That depends on your agreement. Many developers include a set amount in a fixed price and bill extra meetings hourly. State your policy upfront so the client knows what to expect.
How do I bill for work that took longer than I quoted?
For fixed-price work, you usually absorb overruns unless the scope changed. If the client added requirements, bill those changes separately. For hourly work, bill the actual hours, but keep the client updated if the project is running over their expectations.
Do I need to include a tax number on my invoice?
If you are registered for VAT, GST or a similar tax, you will typically need to include it. Rules differ, so check with a local professional.
Ready to send your next bill? Create a free invoice now and present your work professionally.