A UX designer's CA needs evidence for income and costs, and a short account of any client or licence arrangement that is not obvious. Keep invoices, bills and statements together for the April to March year, and add a note on tester payouts and shared licences. Whether any item is claimable is for your CA to decide, and rules change, so confirm the current position with them.
Which documents do you need all year?
- Scope documents or emails that set each project's fee and milestones
- Invoices per milestone, numbered in one series
- Bank and card statements for every account that handled project money
- Licence invoices for fonts, icons, plugins and stock assets
- Records of payments to researchers, illustrators or prototype developers
- Notes for any hardware bought, with date, cost and who uses it
How do you record payments to research participants?
Participant payments are small and frequent, which makes them hard to reconstruct. Keep one sheet per study with the date, how each person was paid, the amount and a participant code. If a payment was by voucher, keep the voucher confirmation. Where no one gave you a bill, a signed or messaged acknowledgement is better than nothing; ask your CA what level of proof they want for small amounts.
What about licences used across clients?
If one font licence covers several clients, say so in your notes rather than attaching its whole cost to one project. If a client should own the licence, bill it to them as a separate line and keep the licence in their name. The more clearly the paper says who owns what, the fewer questions you will get.
| Item | Keep |
|---|---|
| Milestone invoice | Invoice, the approved deliverable and proof of payment |
| Licence | Vendor invoice, licence terms, client or project name |
| Participant payout | Study sheet, payment record, voucher confirmation |
| Hardware | Bill, date, split between work and personal use |
Which mistakes show up often for designers?
- Delivering the final milestone without raising the invoice, then forgetting it until the year ends
- Buying assets on a personal card and leaving the receipt in an email thread
- Accepting a revision round outside scope and not recording the extra fee agreed
- Using one account for studio, savings and household, so that business lines cannot be isolated
- Not noting who owns a licence when a client later takes the project in-house
What do you do when scope grows?
A client asks for another round of screens or an extra user flow. Before you start, write down the extra fee or the agreement to absorb it, and keep the message. At year end, a project that cost you more hours than billed is visible only if the scope changes are on paper. It also protects you in the one conversation that matters, which is about who agreed to what.
How do you hand it to the CA?
Send a tidy folder with invoices, statements, licence bills and the study sheets. Add a note of what share of any shared device or connection you treat as work, which clients were overseas if any, and any project that straddled two financial years. If you are unsure whether to register for GST or how foreign payments are handled, raise it early, since those rules change.
When can a tool help?
A quick first step is to pick your latest finished project and build its folder: scope, invoices, approved file, licence bills and any participant payments. Use that as the pattern for every project after it.
SpendixAI can import statements, flag possible duplicate imports and attach receipts to transactions, and the Export centre offers standard files for the common accounting packages. Its category and GST settings produce estimates, and your CA gives the final view.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

