Software Development Invoice Template - UK

Most software development services provided to UK or EU clients are subject to 20% VAT. If your client is VAT-registered outside the UK, you may apply the reverse charge mechanism and invoice without VAT. You must be VAT-registered yourself to charge VAT. Always verify your client's VAT status and check if any specific exemptions apply to your services. Document this clearly on your invoice for HMRC compliance and to avoid disputes about the final amount owed.

Under HMRC requirements, your invoice must include your business name and address, VAT registration number (if registered), client's name and address, invoice date, unique invoice number, clear descriptions of services provided, quantities and rates, VAT amount and total due, and payment terms. For software development specifically, descriptions should reference the type of work (e.g., "Frontend Development," "API Integration") and project or phase names where applicable. Issue the invoice in English to ensure compliance and maintain records for at least six years.

Hourly billing works well for maintenance, support, and undefined-scope work, while fixed fees suit well-defined projects with clear deliverables. Many UK developers combine both approaches: hourly rates with a project cap, or milestone-based pricing where you invoice as deliverables complete. Choose hourly billing if requirements change frequently; choose fixed pricing if scope is locked. Your invoice template should support both models. Clear terms upfront prevent disputes over whether additional work is included or billable at extra cost.

Descriptions should be specific enough to justify your charges and support audit requirements. Include the type of work (e.g., "React Component Development"), hours or units completed, and relevant project context. Vague descriptions like "Development Work" invite disputes and create HMRC compliance risks. For example, "Backend API Development - User Authentication Module, 35 hours" is clearer than "coding services." This detail protects you if a client disputes the invoice, helps them understand exactly what they paid for, and ensures proper VAT treatment of your services.

Create a recurring invoice on the agreed schedule (monthly, quarterly) with a fixed retainer amount or estimated hours based on typical workload. Specify the support scope clearly: response time commitments, included updates, whether additional work is billed separately, and any usage limits. Include a note referencing the retainer agreement date. VAT applies to retainer fees at the standard 20% rate. If you do additional work beyond the retainer, invoice separately in the same period to show the distinction clearly. Document the arrangement in writing beforehand to avoid misunderstandings.

Standard UK practice is 14 to 30 days from invoice date, with many developers requesting payment before starting work or upon milestone completion. For established clients, 30 days is common; for new clients or risky situations, consider payment upfront or on delivery. Clearly state your terms on the invoice (e.g., "Payment due within 14 days of invoice date"). Include late payment fees if terms allow (typically 8% annual interest plus reasonable costs under UK legislation). Shorter payment windows reduce cash flow risk when managing development teams or contractors.

Itemize each service type separately to show the breakdown clearly. For example, create separate line items for "Frontend Development - React," "Backend Development - Node.js," "Testing and QA," and "Deployment Setup," each with quantity, hourly rate or fixed fee, and subtotal. This structure helps clients understand value, supports audit requirements, and makes VAT calculations transparent. If some services are taxable and others exempt (rare in software development), this approach ensures correct VAT application to each item. Group related items logically by project phase or technology area for readability.

First, refer to any signed project agreement or scope document that backs your charges. Contact the client promptly to clarify what work triggered the dispute and provide additional detail if needed (e.g., timesheets, commit logs, delivery evidence). If you invoiced for hourly work, clear descriptions and time records are your strongest defense. For fixed-fee projects, show how deliverables were completed as promised. If you cannot resolve it directly, consider mediation before pursuing legal action. Always keep detailed records of work performed, communications, and change requests to prevent disputes from becoming serious issues.