UI/UX Designer Invoice Template: Free Guide and Examples

A clear UI/UX designer invoice template is the difference between getting paid in a week and chasing a client for a month. Design work is intangible - your client cannot weigh a wireframe or measure a user flow - so your invoice has to do the heavy lifting of showing exactly what you delivered and what it cost. This guide gives you a ready-to-use UI/UX designer invoice template, explains every line item that belongs on it, and walks through a realistic worked example with believable figures.

Whether you are a solo freelancer running discovery sprints, a contractor embedded in a product team, or a small studio shipping full design systems, the principles are the same. Itemize clearly, set firm terms, protect yourself with deposits, and make payment effortless. Let's build the invoice properly.

Why UI/UX Designers Need a Proper Invoice Template

Design is one of the easier services to dispute and one of the harder ones to prove. "I thought that included the mobile screens" or "we never agreed to three rounds of revisions" are conversations that happen constantly when the invoice is vague. A structured template forces you to spell out scope on the document the client actually pays.

There's also a positioning angle. UI/UX designers sell taste and craft, so a sloppy, mismatched invoice undercuts everything you just delivered in Figma. A clean, well-itemized invoice reinforces that you are a professional who runs a tight business - and that quietly justifies your rate. For more on this, our guide on why professional invoices get paid faster covers the psychology in depth.

Finally, design projects often span weeks and multiple phases. A good template lets you bill in milestones, reference the original scope, and keep a running record that doubles as your accounting trail at tax time.

What to Include on a UI/UX Designer Invoice

Every UI/UX designer invoice should contain a consistent set of fields. Miss one and you invite delay. Here's the full checklist.

Core invoice details

• Your business name, address and contact details - plus your logo if you have a brand.
• Your tax/VAT/EIN/ABN number where applicable to your country.
• The client's legal business name and billing contact - bill the entity, not the individual you Slack with.
• A unique invoice number - sequential and never reused. See invoice numbering explained for systems that scale.
• Invoice date and due date - spell out the actual calendar due date, not just "Net 14".

Design-specific line items

This is where a UI/UX invoice differs from a generic one. Your line items should map to recognisable phases and deliverables:

• Discovery and research - stakeholder interviews, competitor audits, user research, surveys.
• Information architecture and user flows - sitemaps, flow diagrams, content structure.
• Wireframes - low-fidelity layouts, by screen count or phase.
• High-fidelity UI design - mockups, visual design, by screen or component.
• Prototyping - interactive Figma prototypes, micro-interactions.
• Usability testing - session setup, moderation, synthesis reports.
• Design system / component library - tokens, components, documentation.
• Revisions - included rounds vs additional rounds (charged separately).
• Developer handoff - annotations, specs, source-file delivery.

Money fields

• Quantity (hours, screens, days or a flat "1" for fixed fees).
• Unit rate.
• Line subtotal.
• Subtotal, tax, less any deposit already paid, and the final balance due.
• Accepted payment methods and a payment link.
• Notes and your revisions/scope policy in plain language.

How UI/UX Designers Bill: Hourly, Fixed, Milestone and Retainer

UI/UX designers rarely use a single billing model across all clients. Choosing the right one per engagement changes how your invoice is structured.

Hourly

Best for open-ended work where scope genuinely cannot be pinned down - early discovery, ongoing tweaks, or "we'll figure it out as we go" engagements. Your invoice itemizes hours per task. The risk is that clients fixate on the clock, so pair it with a clear time log. Our hourly rate calculator helps you set a defensible number.

Fixed-fee / project

Best for defined deliverables - "a 12-screen mobile app design with one prototype and two revision rounds." You price the outcome, not the hours, which protects your margin if you work fast. The invoice shows a single project fee (often split across milestones). This is the most common model for experienced freelancers.

Milestone billing

For larger projects, split the fixed fee into milestones tied to deliverables: deposit, discovery sign-off, wireframe approval, final delivery. Each milestone is its own invoice. This protects your cash flow and limits exposure if a client disappears mid-project. See milestone billing guide for structures that work.

Retainer

For ongoing product design - a set number of hours or a fixed monthly fee for continuous UI/UX support. You invoice on a recurring schedule. Retainers smooth out the feast-or-famine cash flow most freelancers know too well. Retainer billing explained covers the details.

How to Itemize Design Work the Right Way

Vague line items like "Design - $4,000" are dispute magnets. The fix is to itemize by deliverable or phase, even when you're charging a fixed fee.

Here's a comparison of how the same project can be presented well or badly:

The deliverable-based and phase-based approaches are almost always the strongest. They let the client tick off what they received and they map directly to the statement of work, which kills most disputes before they start.

Billing units that make sense for design

Unlike a plumber billing call-out fees or an electrician billing per socket, UI/UX work is best measured in units that mirror your process. The most useful billing units are:

• Per screen or per page - clean for UI design where the deliverable is countable. "12 screens @ $260" is easy to verify.
• Per component - for design-system work, charge per component built and documented (buttons, modals, form fields, navigation).
• Per phase - discovery, design, testing and handoff as discrete fixed sums.
• Per session - for research and usability testing, price each moderated session plus synthesis.
• Per day (day rate) - common for contract designers embedded in a product team. Our contractor day rate calculator helps you set it.

Mixing units on one invoice is fine and often clearest - a flat fee for discovery, per-screen pricing for UI, and per-session pricing for testing. The goal is that the client can read down the invoice and recognize exactly what each number bought.

For revisions specifically, state the included rounds in your scope and add any extra rounds as separate, clearly labeled line items. Never quietly absorb them; never silently bill them either.

Deposits, Payment Terms and Norms for Design Work

Design has a strong norm around upfront deposits, and you should use it.

Deposits

A 30-50% deposit before work begins is standard for freelance UI/UX projects. For new or unknown clients, lean toward 50%. The deposit does two things: it filters out clients who won't pay, and it funds your time during the longest, least visible phase (research and wireframing). On the final invoice, show the deposit as a deduction so the client clearly sees the remaining balance. Read how deposit invoices protect your business for the full case.

Payment terms

• Net 7 to Net 14 is typical for freelancers and small studios - design clients move fast, so don't give them 30 days unless an enterprise procurement team demands it.
• Milestone terms for larger projects: deposit upfront, then payment on each milestone sign-off.
• Retainers: invoice at the start of each period, due on receipt or Net 7.

Late fees and kill fees

State a late fee (e.g. 5% or statutory interest) in your terms. For project work, include a kill fee clause - if the client cancels mid-project, you're paid for work completed plus an agreed percentage. This is standard and reasonable in creative work.

Worked Example: A Freelance UI/UX Designer Invoice

Meet Priya Anand, a freelance UI/UX designer trading as Anand Product Design. She's been hired by Northwind Retail Ltd to redesign the checkout flow of their e-commerce app. The agreed project fee is $6,400, billed across milestones, with a 40% deposit ($2,560) already paid. This is the final invoice for the remaining balance.

Anand Product Design

123 Maker Street, Bristol, BS1 4QA

VAT No: GB123456789

Email: priya@anandproductdesign.com

Invoice to: Northwind Retail Ltd, 88 Commerce Park, Leeds, LS1 2AB

Invoice number: APD-2026-041

Invoice date: 14 June 2026

Due date: 28 June 2026 (Net 14)

Subtotal: $6,400.00

VAT @ 20%: $1,280.00

Total: $7,680.00

Less deposit paid (40% incl. VAT): −$3,072.00

Balance due: $4,608.00

Payment methods: Bank transfer or card via the payment link below.

Notes: Per SOW dated 2 May 2026. Includes 2 revision rounds; a third round is itemized above. Source Figma files transferred on receipt of final payment. Late payments subject to statutory interest.

Notice what this invoice does: every deliverable is visible, the deposit is clearly deducted, VAT is shown separately, the extra revision is itemized rather than hidden, and a single line ("Per SOW dated 2 May") anchors the whole thing to the agreement.

Licensing, Usage Rights, Insurance and Tax Notes

These vary by country and you should confirm specifics locally, but the principles apply broadly.

Usage rights and source files

Design carries intellectual-property considerations that most trades don't. Decide and state on the invoice:

• When IP transfers - typically on full payment, not before. "Ownership of deliverables transfers on receipt of final payment" is a sensible default.
• Source files vs flattened deliverables - some designers charge extra for editable Figma/source files, or transfer them only after final payment.
• Stock assets and fonts - licensed assets (icons, fonts, photography) are often the client's responsibility or billed as a pass-through cost. Itemize them separately.

Insurance

Professional indemnity insurance is worth having if you advise on accessibility, conversion or anything a client could claim damages over. It's not usually shown on the invoice, but it protects the business behind it.

Tax

You're responsible for your own income tax and, above your country's threshold, sales tax/VAT/GST. If you're VAT-registered in the UK, show VAT as a separate line - see UK VAT invoice requirements. For international clients, currency, tax treatment and reverse-charge rules matter; how to invoice international clients walks through it. Keep every invoice for your records regardless of where you bill.

Common Billing Disputes in UI/UX Design (and How to Prevent Them)

Design billing disputes are predictable, which means they're preventable. Here are the big ones.

"That wasn't in the quote" (scope creep)

The classic. A client asks for "just a couple of extra screens" and assumes it's free. Prevention: define screen count and deliverables in the SOW, reference it on the invoice, and bill additions as explicit line items with a change-order note.

Disputes over revision rounds

Endless tweaks erode your margin. Prevention: state included rounds clearly ("includes 2 rounds of revisions"), then itemize extra rounds at a stated rate. Make this visible before work starts, not after.

"We never used the designs"

A client shelves the project and refuses to pay. Prevention: payment is for the work, not the outcome - state this, take deposits, and bill milestones so unused work is still paid work.

Source file expectations

The client expects editable Figma files; you intended to hand over a prototype only. Prevention: specify exactly what's delivered (and what costs extra) in the scope and on the invoice.

Slow internal sign-off

Milestone approvals stall because the client's stakeholders go quiet. Prevention: define a sign-off window in your terms ("approval assumed if no feedback within 5 business days") and keep invoicing on schedule. Our piece on why clients pay late digs into the patterns.

Pros and Cons of Different Billing Models

No single model wins for every project. Here's an honest breakdown.

Hourly billing

Pros:

• Fair when scope is genuinely unknown.
• No risk of underpricing a vague brief.
• Easy to extend ongoing work.

Cons:

• Clients watch the clock and question hours.
• Punishes your efficiency - the faster you are, the less you earn.
• Harder to forecast revenue.

Fixed-fee / milestone

Pros:

• Predictable for both sides.
• Rewards efficiency and seniority.
• Milestones protect cash flow.

Cons:

• Scope creep eats your margin if you don't manage it.
• Requires a tight SOW upfront.
• Mispricing hurts more.

Retainer

Pros:

• Stable, recurring income.
• Deepens the client relationship.
• Less time spent re-selling.

Cons:

• You can be over-committed in busy months.
• Clients may under-use and question value.
• Needs clear scope on what the retainer covers.

For most freelance UI/UX designers, fixed-fee with milestone billing is the sweet spot, with retainers layered on for ongoing product clients.

Common Mistakes UI/UX Designers Make on Invoices

Even strong designers lose money to avoidable invoicing errors. Watch for these.

• Starting work with no deposit. You fund weeks of research before seeing a penny, and if the client ghosts you, you're unpaid. Always take 30-50% upfront.
• One vague "design" line item. It invites haggling and disputes. Itemize by deliverable every time.
• Burying extra revision rounds. Either you absorb them and lose margin, or you surprise-bill them and damage trust. Itemize extras openly at a stated rate.
• No due date, just "Net 14". Clients interpret ambiguity in their favor. Put a real calendar date on it.
• Forgetting tax. Adding VAT or sales tax after the fact looks unprofessional and can cost you. Build it into the quote.
• Inconsistent invoice numbers. Random or reused numbers create accounting chaos and look amateur at tax time.
• Sending the invoice days late. Momentum matters - a milestone approved on Monday should be invoiced Monday, not the following week.
• No payment link. Forcing clients to type out bank details adds friction and delay. See our roundup of common invoice mistakes.
• Not stating IP transfer terms. If you don't say files transfer on final payment, clients may assume they own everything the moment you share a Figma link.

Best Practices for UI/UX Designer Invoices

Follow these and you'll get paid faster with fewer arguments.

1. Take a deposit on every project. 30-50% before you open Figma. Non-negotiable for new clients.
2. Itemize by deliverable, not just hours. Let the client see the wireframes, mockups, prototype and handoff as distinct value.
3. Reference the SOW on the invoice. One line that anchors scope kills most disputes.
4. State your revisions policy in writing. Included rounds vs paid extra rounds, with the rate.
5. Bill milestones on bigger projects. Don't carry weeks of unpaid work.
6. Set short, specific payment terms. Net 7-14 with a real calendar due date.
7. Make paying effortless. Include a payment link and accept card and bank transfer. See how to accept online payments.
8. Tie IP transfer to final payment. Files and ownership move when the balance clears.
9. Number invoices sequentially and keep every copy for tax and reconciliation.
10. Send promptly. Invoice the day a milestone is approved - momentum gets you paid.

Modern invoicing tools make all of this routine. Instead of rebuilding a template in a document each time, you can describe the work in plain language and have a polished, itemized invoice generated in seconds - deposit deducted, VAT calculated, payment link attached. That's exactly what Aviy's AI invoice generator is built for, and it keeps every invoice consistent across hourly, fixed and retainer work.

Summary

A strong UI/UX designer invoice template does three jobs: it shows exactly what you delivered, it ties money to agreed scope, and it makes paying easy. Itemize by deliverable - research, wireframes, hi-fi UI, prototype, testing, handoff - take a deposit, set short payment terms, and reference your SOW on the document itself. Bill fixed-fee with milestones for projects and retainers for ongoing product work.

Get the structure right and you'll spend less time chasing clients and more time designing. Use the worked example above as your starting point, adapt the line items to your own services, and keep your invoices as clean and considered as the interfaces you build.

Frequently asked questions

What should a UI/UX designer invoice include?

It should include your business and tax details, the client's legal name, a unique invoice number, invoice and due dates, and itemized design work such as discovery, wireframes, high-fidelity UI, prototyping, usability testing and handoff. Add quantities, rates, line subtotals, any deposit already paid, tax, the balance due, accepted payment methods and a short note referencing your scope and revisions policy.

How do freelance UX designers usually charge clients?

Most use one of four models: hourly for open-ended work, fixed-fee for defined deliverables, milestone billing for larger projects split into approved phases, and retainers for ongoing product support. Experienced freelancers tend to favor fixed-fee with milestones because it rewards efficiency and protects cash flow, while reserving hourly rates for genuinely undefined discovery work.

Should I bill hourly or fixed-fee for design work?

Use hourly when scope truly cannot be pinned down, and fixed-fee when deliverables are clear. Fixed-fee rewards your speed and seniority and is easier for clients to approve, but it requires a tight statement of work to control scope creep. Hourly is fairer for vague briefs but invites clients to scrutinise your time, so always pair it with a clear log.

How much deposit should a UI/UX designer ask for?

A 30-50% deposit before starting is standard. Lean toward 50% for new or unfamiliar clients. The deposit funds the longest, least visible phase of the work and filters out clients unlikely to pay. On the final invoice, show the deposit as a clear deduction so the client immediately sees the remaining balance due.

How do I handle revisions and scope creep on a design invoice?

State the number of included revision rounds in your scope, then itemize any extra rounds as separate, clearly labeled line items at a stated rate. When a client requests work beyond the agreed deliverables, treat it as a change order: confirm in writing, add it as its own line, and reference the original SOW on the invoice to keep everything traceable.

What payment terms work best for UI/UX design projects?

Net 7 to Net 14 suits most freelancers and small studios, with a real calendar due date rather than just "Net 14". For larger projects, use milestone terms - a deposit upfront and payment on each phase sign-off. Retainers are typically invoiced at the start of each period, due on receipt or Net 7. Add a late fee and a kill-fee clause for cancellations.

When does the client own the design files I create?

A common and sensible default is that intellectual property and editable source files transfer on receipt of final payment, not before. State this on the invoice and in your contract. Some designers charge extra for editable Figma or source files, or deliver only a prototype unless source files are purchased - decide this upfront and itemize it.

Do I need to charge VAT or sales tax on design work?

It depends on your country and whether you're above the registration threshold. If you're VAT-registered in the UK, show VAT as a separate line on the invoice. For US designers, sales-tax treatment of services varies by state. For international clients, reverse-charge and currency rules apply. When in doubt, confirm locally and keep every invoice for your records.

How do I invoice for a design retainer?

Set a fixed monthly fee or a defined number of hours, then invoice on a recurring schedule at the start of each period. Specify exactly what the retainer covers - number of revisions, response times, and what counts as out-of-scope. Recurring invoices automate this so you're never late raising them, which keeps your income predictable and your client relationship smooth.

How can I get paid faster as a UI/UX designer?

Send invoices immediately after a milestone is approved, take deposits, set short payment terms with a clear due date, and include a payment link so clients can pay by card or transfer instantly. Itemize deliverables so there's nothing to question, reference your scope to head off disputes, and use automated reminders for anything that drifts past due.

Conclusion

A well-built UI/UX designer invoice template protects your time, your margin and your professional reputation all at once. By itemizing your design work clearly, anchoring it to an agreed scope, taking a sensible deposit and setting short payment terms, you remove almost every reason a client could give for paying late. Design is intangible - your invoice is where it becomes concrete and billable.

Treat the worked example in this guide as a starting point and adapt the line items to your own services and country. Whether you bill hourly, fixed-fee, by milestone or on retainer, a consistent UI/UX designer invoice template means less admin, fewer disputes, and faster payments - so you can spend more time designing and less time chasing.

Related guides

• How Deposit Invoices Protect Your Business
• Milestone Billing Guide: How to Structure Payments and Get Paid Faster
• Retainer Billing Explained: How It Works and When to Use It
• Why Professional Invoices Increase Payment Speed (And How to Get Paid Faster)
• Graphic Designer Invoice Template: Free Guide and Examples
• Best Invoicing Software for Freelance Designers (2026 Guide)

Sources and further reading

• What to include on a VAT invoice (GOV.UK)
• Self-employed records you must keep (GOV.UK)
• Intellectual property and your work (GOV.UK)
• Independent contractor tax basics (IRS)
• Invoicing and payments overview (Stripe Docs)