Freelance admin has a rhythm. Most of the year it is a low hum: a receipt here, an invoice there. Then January arrives, and the whole year's paperwork lands on your desk at once. The trick is not to be more organised in January — it is to have somewhere to put things in April, July and November so that January is boring.
Notion suits that job well, because freelance admin is mostly a set of lists that need to talk to each other: clients, invoices, expenses, and the dates HMRC cares about. Here is a template plan built around the UK tax year, with the fields and views that do the actual work.
Start with the tax year, not the template
Everything in a UK freelance setup runs on a tax year that begins on 6 April and ends on 5 April. Before you build a single database, decide that yours will work the same way. Every invoice and expense gets a Tax year value — a select with options such as 2025/26 and 2026/27. That one property lets you filter the whole workspace down to the year you are filing, rather than scrolling through three years of mixed records and guessing.
It also keeps the deadline page manageable, because you can group dates by tax year and archive the old ones.
Four databases that cover almost everything
You do not need an elaborate system. Four linked databases carry the bulk of freelance admin:
- Clients — one row per client, with contact details, payment terms and a default rate.
- Invoices — one row per invoice, linked to a client, with amounts, dates and status.
- Expenses — one row per purchase, with a category, amount, date and a place to store the receipt.
- Deadlines — one row per date that matters, from filing deadlines to your own quarterly check-ins.
Relate Invoices to Clients, and Expenses to Clients where relevant. Rollups then give you a total invoiced figure per client without any manual adding up.
The invoice tracker, field by field
Properties that earn their place
Property design is where most Notion finance templates fall down: too many fields, none of them used. Keep these and ignore the rest.
- Invoice number — the title property, sequential, so you can search for it instantly.
- Client — a relation, not a plain text field.
- Status — Draft, Sent, Paid, Overdue. A status property works better than a select here.
- Issue date and Due date.
- Amount — a number property formatted as currency, holding the net figure.
- Tax year — the select described above.
- Paid on — the date the money actually landed.
If you are VAT registered, track VAT in its own field rather than bending the net amount into two jobs. If you are not registered, leave those fields out entirely. Empty properties are clutter you will skip past every time.
Views that save you time
Three views on the Invoices database do most of the daily work. A board grouped by status gives you a quick sense of what is outstanding. A table filtered to Status is Sent and sorted by due date becomes your chase list — work down it on a Friday morning. A calendar view showing due dates helps you spot the weeks where three invoices fall on the same day.
Add a filter for the current tax year to each one, and the database stays useful in year three instead of becoming an archive you never open.
Expenses without the shoebox
The value of an expense database is not the list, it is the proof. For every purchase, attach the receipt to the row: a photo, a PDF or a forwarded email. One row per receipt takes seconds at the time and saves an evening in January.
Keep the categories simple and consistent: software, equipment, travel, professional fees, phone and internet, training. Use the same words every time. Ten tidy categories beat forty precise ones you cannot remember from month to month.
HMRC expects you to keep business records for a set period after the filing deadline, and to produce them if asked. Check the current guidance on gov.uk for how long that is and what counts, and ask an accountant if your situation is not straightforward.
A monthly view grouped by category, with a rollup for the total, tells you whether the year is going roughly as you expected. Better to find that out in October than on 31 January.
A deadlines page that pays for itself
Late filing carries penalties, and the dates are entirely predictable, so put them somewhere you will see them. A simple table with the date, the tax year and a status works fine. The core UK dates to include are:
- 5 October — the deadline to register for self assessment if you are newly self-employed and need to file.
- 31 October — the deadline for a paper return.
- 31 January — the deadline for online returns and for paying the tax owed.
- 31 July — the deadline for the second payment on account, where payments on account apply to you.
Add your own dates alongside them: quarterly VAT returns if you are registered, company accounts and confirmation statement deadlines if you run a limited company, and a monthly reminder to chase unpaid invoices. Confirm what applies to you on gov.uk, and if you are unsure about payments on account or your filing obligations, speak to an accountant. One conversation usually costs less than one penalty.
The weekly ten minutes
A system only works if it is maintained, and the maintenance does not need to be much. Put ten minutes in your calendar every Friday and do the same four things:
- Raise invoices for work completed that week.
- Update the status of anything that has been paid.
- File the week's receipts as expense rows.
- Check the deadline list for anything coming up in the next fortnight.
Ten minutes weekly is far easier to keep than a four-hour session in January. It also means you always have a rough idea of what you are owed — useful when a client asks about a discount.
Begin with one database this weekend
Do not build all four at once. Start with Invoices, because it is the one that puts money in your account. Add the properties above, create the three views, and enter every outstanding invoice. Use it for a fortnight before adding anything else.
Once invoicing feels natural, add Expenses, then Deadlines. By the time the next 31 January comes round, the year will already be documented, and filing becomes a matter of checking figures rather than reconstructing nine months of your working life from bank statements.
Photo: tookapic / Pixabay
