Every UK tax deadline, on one calendar.
FigsFlow is deadline tracking software for UK accountancy practices. Year ends, corporation tax, VAT staggers, PAYE and P11Ds, Self Assessment and MTD quarterly updates — dated per client from the client record, owned by a named person, chased before they bite, and evidenced after.
FigsFlow runs the practice. Your tax and ledger software do the filing. Nothing on this page claims otherwise.
Partner or practice manager, start with the live tour below. Compliance or year-end lead, the calendar in full and the escalation rules are what you want.
The tour runs in your browser. No form until you want one.
- VAT · Q to 31 Jul7 September 2026 · with the client
- Confirmation stmt22 September 2026 · ready to file
- MTD Q2 · director7 November 2026 · chasing records
- CT600 · y/e 31 Dec31 December 2026 · in preparation
- OwnerA. Shrestha · one named person
nothing typed into a spreadsheet
Every obligation selected is dated from the client record — year end, VAT stagger, payroll frequency. Deselect one and the calendar is rebuilt from the same record. No second list to keep in step.
The deadline that gets missed is the one nobody owned
Not the January returns. Those have a partner watching them. It is the P11D for the client who took a car in November, the VAT stagger that moved when the client registered, the confirmation statement on a dormant company. Small, dated, spread across four lists, and owned by whoever happened to open the spreadsheet last.
Still doing it this way?
Five places a date can live, and none of them is the client record.
- 01A master deadline spreadsheet, updated by hand
- 02Outlook reminders in one person's calendar
- 03Dates inside the tax software, seen only when you open it
- 04A chase email thread, if someone remembers
- 05Whatever the manager keeps in their head
Then the client changes their year end, or takes on staff, and only one of those five is ever corrected.
Two steps between you and a dated calendar
The listing, the dating and the chasing are already done.
- 01Say what you do for the client
- 02Confirm the year end, stagger and payroll frequency
The obligations, the dates, the internal target dates, the owner and the chase sequence are already attached — and they move together when the client changes.
What happens in the three weeks before a deadline?
Work, mostly without you. A due date is an object in FigsFlow with a schedule behind it, not a line in a spreadsheet somebody has to read.
The job exists already.
Recurring statutory work is a first-class object, not a task somebody remembers to create. The job for the next VAT quarter is on the board before the current one is filed.
Records chasing starts on its own.
The request goes to the client portal in plain English, on the schedule you set, and repeats until it is answered. Nobody drafts the third reminder.
An internal target date, not the statutory one.
The team works to the practice's own date with review time built in. The statutory date is the backstop, and clients never see the raw one.
Slippage escalates before it matters.
A date at risk moves up the deadline radar and reaches the manager while there is still time to move capacity, rather than at the end of the week it was due.
Filed elsewhere, evidenced here.
You file in your tax or ledger software. FigsFlow records what was due, who did it, when the records arrived and when it was marked filed — dated, on the client record.
The deadline stops being something to remember and becomes something to review.
Whose dates go on the calendar?
The client's. Every date is derived from the client record — the year end, the VAT stagger, the payroll frequency, whether they are in MTD for Income Tax — so it is right for that client rather than right on average. Change the year end once and every dependent date moves with it, including the internal target dates and the chase schedule.
The UK compliance calendar, by tax
The obligations FigsFlow dates and tracks per client. This is the rule each date is calculated from, not a fixed list of days — because a company with a 31 December year end and a company with a 31 March year end do not share a calendar.
Deadline positions verified 1 September 2026 against current HMRC and Companies House guidance. Re-verify and date-stamp before relying on any date, and read it alongside the client's own circumstances.
Five dates a year where there used to be one
Making Tax Digital for Income Tax became mandatory on 6 April 2026 for sole traders and landlords with qualifying income over £50,000. HMRC put more than 864,000 people in scope, with the first quarterly update due 7 August 2026. For an affected client, the deadline count goes from one return to four cumulative updates plus the return. FigsFlow schedules that cycle; the update itself is submitted through the client's or the practice's compatible software.
Over £50,000. Sole traders and landlords with qualifying income above £50,000 on their 2024–25 return are in scope now.
Over £30,000. The second wave. This is the one to plan onboarding capacity around, because it is materially larger.
Over £20,000. Announced. Treat it as announced rather than settled law when you plan, and re-check before you quote on it.
What FigsFlow does with a deadline, and what it does not
Deadline software attracts vague claims, and on a site read by regulated professionals a vague claim is worse than a gap. So here is the plain version, so nothing on a demo call comes as a surprise.
Ask on a demo call about anything not listed here. Capability and regulatory statements should be re-verified and date-stamped before release.
What this looks like at your size
One calendar you can trust on a Monday morning, without keeping a deadline spreadsheet in step with the client list.
Every date has a named owner, so nothing depends on which person opened the spreadsheet last.
Internal target dates and review gates hold as you add people, and January stops eating the review discipline.
Partner-level visibility of the whole book by due date, with the evidence trail inside your own Microsoft tenant.
Where the calendar connects
A deadline is only useful next to the client it belongs to. These are the parts of FigsFlow that read the same record.
Companies House
Accounting reference dates and confirmation statement dates, read from the register rather than typed.
See Companies House →AML and client due diligence
Periodic reviews are dated obligations too, and they sit on the same client record.
See AML and CDD →Risk assessment
A pattern of late records is a fact about the client, and it belongs next to the risk rating.
See risk assessment →Jobs, capacity and the practice dashboard
Where the dated work becomes a board, a workload and a decision about who does what.
See the platform →What practices ask before they switch
No. FigsFlow tracks, schedules, chases and evidences the deadline. Returns and MTD quarterly updates are submitted through your tax, ledger or MTD software. Nothing on this page should be read as saying otherwise.
Self Assessment, corporation tax and company accounts, VAT under all the common staggers and schemes, PAYE and RTI, P11D and Class 1A, CIS, MTD for Income Tax quarterly updates, and the Companies House confirmation statement. The calendar section above sets out the rule each date is calculated from.
The client record. The year end, the VAT stagger, the payroll frequency and whether the client is in MTD for Income Tax drive the dates, so they are right for that client. Change the year end once and everything dependent on it moves, including internal target dates.
Yes, and that is the default. Each obligation carries a statutory date and a practice target date with review time built in. Clients see the practice's target date; the raw statutory date is not shown to them.
Yes. Requests go to the client portal in plain English on the schedule you set and repeat until they are answered. Received documents are filed to the right client and job, so nobody drafts a third reminder by hand.
It turns four cumulative quarterly updates plus the return into scheduled recurring work per client, with records chasing and a dated trail. The update is still submitted through compatible software — FigsFlow manages the cycle around it.
What was due and when, who owned it, when the records arrived, what was reviewed and by whom, and when it was marked filed. Dated, on one client record, and exportable — which is the shape of evidence a supervision visit asks for.
No, and we will not claim it does. Compliance obligations sit on the practice and its principals. FigsFlow enforces the workflow, evidences what was done and holds the trail. The judgement, the filings and the responsibility stay with you.
Bring your worst week of the year to the demo
Thirty minutes, one real client with a year end, a VAT stagger and a payroll, and the whole calendar built on screen by a practice specialist who has filed against it.
Some of those dates come from the register rather than from HMRC. Companies House and the register