Who it's for: finance managers, controllers and team leads in SaaS and tech, and anyone in the team who wants month-end and busy season to feel less like a siege.
What you'll get: a practical playbook for workload, communication and recovery, a busy season planning checklist, worked examples of a capacity plan and a team thank-you lunch, AI notes, and a one-slide pitch for your boss.
Reading time: about 12 minutes. Read it before the next year-end, not during it.
Why it matters: tired teams make expensive mistakes
Every finance team has peaks: the first five days of the month, quarter-end, year-end and audit, budget season. The work is fixed; the hours aren't. When people run on long days for weeks, error rates go up, review gets skipped and good people start updating their CVs.
Keeping the team going isn't about pizza. It's about planning the load, protecting the review step and making recovery a normal part of the calendar.
Key terms
- Busy season: the weeks around year-end close, the audit and the budget, when workload peaks.
- Capacity plan: a simple table of hours needed against hours available, by person and by week.
- Time off in lieu (TOIL): time off given back for extra hours worked, under whatever policy your company has.
- Single point of failure: a task only one person knows how to do.
- Close retrospective: a short meeting after the close to note what slowed things down and fix one thing.
Step 1: plan the peak before it arrives
The best time to sort busy season is six to eight weeks before it starts. Many teams build the plan alongside the year-end close calendar.
| Task | What "done" looks like | |
|---|---|---|
| ☐ | List every peak in the next 12 months: month-ends, quarter-ends, year-end, audit fieldwork, budget, board dates | One shared calendar showing every peak week |
| ☐ | Estimate hours for each big task (from last year's timings or the close calendar) | A task list with hours and an owner |
| ☐ | Compare hours needed with hours available, after holidays and training | A capacity plan showing any week where someone is over 100% |
| ☐ | Agree a holiday approach for peak weeks, early and fairly | People know which weeks are tight before they book anything |
| ☐ | Decide what can move out of the peak: projects, system changes, non-urgent reports | A short "not now" list agreed with your manager |
| ☐ | Line up extra help if the plan shows a gap: temps, contractors, help from FP&A | Cover booked, with system access ready before day one |
AI shortcut: give an approved AI assistant your close calendar and last year's task timings (task, owner, hours; no salaries or personal data), and ask it to lay out hours per person per week and flag anyone over capacity. Check its sums and its assumptions before you share the plan.
Step 2: remove single points of failure
If one person is the only one who can run payroll journals, reconcile Stripe or roll forward deferred revenue, then their sick day is everyone's problem. It also means they can never take a week off in a peak month.
- List the month-end tasks and who can do each one.
- Mark any task with only one name against it.
- Pick the two riskiest and pair someone up on them for the next close: watch once, do once with help.
- Make sure there's a written process note for each, stored in the team drive.
This also gives junior team members a route to more interesting work, which keeps them around.
Step 3: protect the hours
| Habit | What "done" looks like | |
|---|---|---|
| ☐ | Block focus time during the close, with meetings outside it | No routine meetings on Days 1 to 3, except the daily stand-up |
| ☐ | Run a 10-minute daily stand-up in peak weeks | Everyone knows what's blocked and who's helping |
| ☐ | Set a team "lights out" time on most days | Late nights are the exception and are spotted, not expected |
| ☐ | Batch questions to other teams | One list per day to sales, ops or HR, not twenty separate messages |
| ☐ | Keep the review step, even when tired | No journal or reconciliation signed off by its own preparer |
| ☐ | Track extra hours and give them back under company policy | TOIL or time off taken within an agreed window after the peak |
Leaders set the tone here. If the manager sends emails at midnight, the team reads that as the standard, whatever the policy says. Scheduling messages to send in the morning is a small, useful habit.
Step 4: communicate early and often
- Before the peak: share the plan, the deadlines and the "not now" list with the team and with the teams you depend on.
- During the peak: a short daily stand-up and a visible tracker (a shared sheet with task, owner, status works fine).
- When something slips: say so early, with the knock-on effect and a new date. Late surprises cause more stress than late tasks.
- Outside finance: tell budget holders and sales ops what you need from them and by when. A cut-off reminder on Day -3 saves a lot of Day 3 chasing.
AI shortcut: at the end of each day, paste the tracker into an approved AI assistant and ask for a three-line status update for leadership: done, at risk, needed from others. It takes a minute to check and saves the manager twenty minutes of writing.
Step 5: recover and say thank you
Recovery is the step most teams skip. Build it in.
- Put a "quiet week" in the calendar after year-end or the audit, with no new projects.
- Make sure TOIL or time off is actually taken, not just recorded.
- Hold a close retrospective within a week, while people remember what hurt. Ask three questions: what slowed us down, what helped, what one thing we change next time.
- Say thank you specifically. "Thanks for clearing the Stripe reconciliation by Day 2, it meant revenue was done a day early" lands better than a general "great work, everyone".
- Mark the end of the peak with the team: lunch, an early finish, something small and shared.
If your company pays for team thank-yous, there are UK tax rules on staff gifts and events. As at October 2026, gov.uk guidance says small non-cash gifts can be tax-free as "trivial benefits" if each costs £50 or less (including VAT), isn't cash or a cash voucher, and isn't a reward for work or performance or part of a contract. For directors of close companies there is a £300 annual cap. A separate exemption covers an annual staff party or event open to all employees, up to £150 per head. Payroll or your tax team usually check these before anything is bought; the gov.uk pages on trivial benefits and on social functions and parties have the detail.
Worked example 1: a year-end capacity plan
MonthEndClub Co Ltd, a fictional UK SaaS company, has a finance team of four. Year-end close and audit preparation run across two weeks in January. Each person has 37.5 contracted hours a week. The team estimates the work from last year's timings.
| Person | Hours available (2 weeks) | Hours needed | Load |
|---|---|---|---|
| Financial controller | 75 | 90 | 120% |
| Management accountant | 75 | 84 | 112% |
| Accounts assistant | 75 | 60 | 80% |
| Payroll and AP (part-time, 22.5 hours a week) | 45 | 30 | 67% |
| Team total | 270 | 264 | 98% |
Checks: 75 + 75 + 75 + 45 = 270; 90 + 84 + 60 + 30 = 264; 264 ÷ 270 = 98%. Individually, 90 ÷ 75 = 120%, 84 ÷ 75 = 112%, 60 ÷ 75 = 80%, 30 ÷ 45 = 67%.
The team as a whole has just enough hours, but two people are overloaded and two have slack. The plan moves 12 hours of prepayment and accrual schedules from the controller to the accounts assistant (who shadowed them in the autumn) and 6 hours of supplier statement reconciliations from the management accountant to the payroll and AP role.
| Person | Hours needed after changes | Load |
|---|---|---|
| Financial controller | 78 | 104% |
| Management accountant | 78 | 104% |
| Accounts assistant | 72 | 96% |
| Payroll and AP | 36 | 80% |
| Team total | 264 | 98% |
Checks: 90 − 12 = 78; 84 − 6 = 78; 60 + 12 = 72; 30 + 6 = 36; total still 264. 78 ÷ 75 = 104%; 72 ÷ 75 = 96%; 36 ÷ 45 = 80%.
No one is now far over capacity, and the plan has a small buffer for surprises (there are always surprises). The board pack redesign is moved to the "not now" list.
Worked example 2: booking a team thank-you lunch
After the audit, MonthEndClub Co Ltd takes its finance team of four out for lunch. The bill is £144 including £24 VAT, so £36 a head, and it's open to everyone in the team as a thank-you, not a reward linked to performance. Payroll checks it against the trivial benefits rules before booking. It's posted as staff welfare. In this example the company treats the VAT as recoverable on staff entertainment; VAT rules on entertaining have conditions, so many teams check the treatment with their tax adviser or HMRC's guidance.
| Account | Dr | Cr |
|---|---|---|
| Staff welfare (admin expenses) | £120 | |
| VAT input tax | £24 | |
| Company credit card | £144 |
Check: £120 + £24 = £144; £144 ÷ 4 = £36 a head, under the £50 trivial benefit limit as at October 2026.
Common mistakes
- Planning the work but not the people. A close calendar without a capacity check hides who is about to burn out.
- Treating long hours as normal. A week of late nights in a peak is one thing. Every month-end needing them is a process problem.
- Dropping review under pressure. Tired preparers make more mistakes, so review matters more in peak weeks, not less.
- Recording TOIL but never giving it back. People notice.
- Generic thanks. "Well done team" is fine. Specific thanks is better.
- Letting AI take the review step. AI can draft status updates and flag unusual items, but a person still reviews and signs off. Only use tools your company has approved for financial or staff data.
Tools that can help
A shared tracker in Google Sheets or Excel is enough for most small teams. Close management features in tools such as NetSuite or dedicated close software help larger teams see status at a glance. Team chat with scheduled sending stops late-night messages landing at 11pm. An approved AI assistant helps with capacity sums, status updates and retrospective notes. None of these replace a manager who looks at the plan and moves work before people are overloaded.
Take it to your boss: one slide
A busy season that doesn't break the team
The problem
- Peak weeks rely on long hours from the same two or three people
- Key tasks have only one person who can do them
- No planned recovery time, so tiredness carries into the next close
Three changes
- Capacity plan six weeks ahead: hours needed vs available, by person and week.
- Cover for the top two single-person tasks: paired up at the next close.
- A quiet week and a retrospective after each peak: time off taken, one fix agreed.
| Risk | Control |
|---|---|
| Errors from tired preparers | Review step kept in peak weeks; no self-approval |
| Key person off sick in the peak | Two people trained on each critical task |
| Staff turnover after busy season | Recovery time and TOIL actually taken |
| AI errors or data leaks | Approved tools only; every AI output checked |
How we'll measure it: close days, late adjustments, extra hours worked in peak weeks, and TOIL taken within a month.
Rates, thresholds and rules in this guide
Figures were checked against the pages below in October 2026. They change regularly (often each April or at Budget time), and we can't guarantee they're still current or right for your situation. Always check the official page before relying on them.
- EIM21864: trivial benefits, conditions to be satisfied (GOV.UK, HMRC): the four conditions for tax-free trivial benefits, including the £50 limit
- EIM21865: trivial benefits, the cost of the benefit (GOV.UK, HMRC): that the £50 limit is measured including VAT
- EIM21870: trivial benefits, directors of close companies (GOV.UK, HMRC): the £300 annual cap for directors of close companies
- Expenses and benefits: social functions and parties, what's exempt (GOV.UK): the £150 per head annual staff event exemption
- Business entertainment and VAT (VAT Notice 700/65) (GOV.UK, HMRC): when VAT on staff entertainment can be recovered
Key takeaways
- Plan the peak six to eight weeks ahead, with hours by person, not just tasks by day.
- Remove single points of failure by pairing people on the riskiest tasks.
- Protect focus time, keep the review step and make late nights the exception.
- Communicate early, especially when something slips.
- Build recovery into the calendar and say thank you specifically.
FAQs
How do I stop month-end overtime becoming normal?
Look at where the hours go. Most regular overtime comes from waiting for inputs, manual matching or tasks bunched at the end. Moving requests earlier and automating routine matching usually does more than asking people to work faster.
What's a sensible holiday approach for busy season?
Many teams ask people to avoid the core close days and audit fieldwork weeks, agree it early and apply it fairly. Some rotate who covers the Christmas period each year.
Can AI reduce the busy season workload?
Yes, for the right tasks: matching bank and payout data, comparing reports, drafting commentary and status updates, and building first-draft capacity plans. It doesn't remove the need for review. A person checks every output, and only company-approved tools are used for financial or staff data.
Are team thank-you gifts taxable in the UK?
Some are and some aren't. As at October 2026, gov.uk guidance treats small non-cash gifts costing £50 or less each as tax-free trivial benefits if they meet the conditions, and an annual event open to all staff can be exempt up to £150 per head. The gov.uk pages set out the conditions, and payroll or your tax adviser can confirm specific cases.
Related guides
- How to Build a Month-End Close Calendar (Day -3 to Day +5)
- Year-End Close Checklist for SaaS Companies
- Who Does What at Month-End: A Role Chart for Small Finance Teams
- The Busy Season Survival Kit
More in Careers guides.
From the Club
Matching mugs won't shorten the close, but they do make the stand-up look organised. The Team Mug · The Beanie
Join the Club. New guides, early access and members-only batches. Join here.
This guide is general information about common practice. It isn't tailored to any business, and standards, tax rules and figures change. Check your own circumstances, the latest rules and, where needed, a qualified professional before acting.
Last reviewed: October 2026.