Invoice Generator
Create a clean, professional invoice your client can understand and pay quickly. Add your details, line items, due date, tax, and payment instructions — then review the preview and copy the result. No account required.
Invoice fields
| Description | Qty | Rate | Amount | Action |
|---|---|---|---|---|
| $1,200.00 |
Invoice
Your Studio
Bill to: Client Name
Invoice INV-001
Issue: 2026-04-21 · Due: 2026-05-05
| Description | Qty | Rate | Amount |
|---|---|---|---|
| Discovery and strategy | 1 | $1,200.00 | $1,200.00 |
Subtotal: $1,200.00
Tax: $0.00
Total: $1,200.00
Thanks for your business.
Payment details: Bank transfer within 14 days.
What a professional invoice needs to include
An invoice is a payment request, not just a summary of work done. Its job is to make it as easy as possible for the client's accounts team to process payment — quickly, accurately, and without needing to contact you for missing information. Most invoice payment delays are caused by missing or incorrect details that stall internal processing, not by clients who do not intend to pay.
The essentials: your legal name or business name, the client's correct billing name and address, a sequential invoice number, an explicit due date (not “upon receipt”), itemised line items that match the agreed scope, all payment details in one place, and your tax registration number if applicable.
What each field does and why it matters
| Field | Why it matters | Common mistake |
|---|---|---|
| Invoice number | Makes the invoice searchable in both your records and the client's accounts system | Inconsistent numbering or reusing numbers |
| Due date | Creates a processing trigger for the client's accounts team | “Payment upon receipt” — this is not a deadline |
| Line items | Ties the payment to specific agreed deliverables, reducing disputes | Vague descriptions like “design work” |
| Payment reference | Allows incoming bank transfers to be matched to the invoice immediately | Omitting it — transfers arrive without context |
| Late payment terms | Makes the cost of late payment visible before the due date passes | Only in the contract, not on the invoice itself |
Common reasons invoices get delayed
- Sent to the wrong person or email address. Larger companies have dedicated accounts payable contacts different from your day-to-day client. Ask before the first invoice.
- Missing or wrong payment details. A bank transfer without a payment reference often lands in a general account with no clear invoice to close. Include the invoice number as the payment reference.
- Invoice total does not match the agreed amount. Discrepancies — however small — stall payment while someone investigates. Confirm amounts before sending.
- No explicit due date. Invoices without deadlines are routinely deprioritised in payment queues. Net 14 or Net 30 from issue date is standard.
- Sent too late. Invoice immediately after a milestone or delivery. Every day you delay is a day added to your wait for payment.
Deposit vs milestone vs final invoices
Different invoice types serve different purposes in a project payment structure:
- Deposit invoice: sent before work starts, labelled “Deposit Invoice”, payment is a condition of starting. Non-refundable terms should be stated.
- Milestone invoice: issued when a defined phase is complete. Reference the milestone name from your contract (“Phase 1: Discovery”).
- Final invoice: the remaining balance due on or before final file handover. Often the trigger for IP transfer if that is in the contract.
- Recurring invoice: for retainers, use a consistent format with the period in the description (“May 2026 Retainer”).
If a payment becomes overdue, use the Late Payment Fee Calculator to get the accurate updated balance before chasing, and copy the reminder language from the Late Payment Email Template. For a plain-text version of the invoice format, see the Invoice Template.
How to use the output
Review the invoice preview carefully before sending. Check that line items match the agreed scope, the due date is correct, and all payment details are complete — missing or wrong information is the most common cause of payment delays.
Fill in freelancer details, client details, and line items. Set the due date as a specific calendar date — not a vague term. Add payment bank details and confirm the total. Then copy or print the invoice preview and send it immediately after delivery of the work or milestone.
Best practice
Invoice on the day work is delivered, not at the end of the month. Every day between delivery and invoice is a day added to your payment wait. Most late payment problems start with late invoicing.
Worked example
A milestone invoice for £2,400 with Net 14 payment terms, referencing 'Phase 1: Brand Discovery' in the line item, gives the client's accounts team everything they need to process payment without chasing you for more information.
Swap your own assumptions to create a quote-ready number or policy clause.
Sponsored
FAQ
Net 14 is standard for most freelance work and is recommended as a default. Net 30 is common for larger corporate clients with internal payment cycles. Anything beyond 60 days is typically unreasonable for small business suppliers and can be challenged under UK late payment legislation.
Only if you are registered for VAT (UK), GST (Australia/Canada), or another applicable sales tax. If you are not registered, omit the tax line entirely. Do not include a tax line at 0% — it just creates confusion. UK VAT registration is required once taxable turnover exceeds £90,000 (2025/26 threshold).
Not mandatory, but good practice. A brief 'payment received' email confirming the invoice number and amount builds trust and closes the paper trail cleanly. Some accounting tools do this automatically.
Issue separate invoices for each instalment — one per payment with its own due date and invoice number. Do not put multiple due dates on a single invoice; it creates ambiguity about which amount is due when.