Introduction: the question I ask every business owner
At Kinore we have a name for the risk that most businesses never get around to measuring. We call it the lotto factor.
It works like this. Take the person who runs your bookkeeping, and ask yourself one question. If they won the lotto today and didn’t come back tomorrow, how would your business cope without them?
Most owners answer honestly, and the honest answer is usually uncomfortable.
I hear a version of it constantly. A prospect will say, almost as a joke, “my bookkeeper goes on annual leave for two weeks and everything just stops.” It’s said lightly. It’s not a light problem. If two weeks of annual leave brings your finance function to a standstill, a resignation isn’t an inconvenience. It’s a continuity risk.
The biggest risk isn’t that your bookkeeper leaves. It’s discovering how much of your finance function was living in their head.
I lead the Cloud Services team at Kinore, and my team spends most of their time helping Irish businesses digitalise their finance function, migrate between systems, and get through exactly this moment. What follows is the roadmap I give owners when the resignation letter has already landed.
One thing before we start. In almost every case I’ve worked on, the issues didn’t come from the person doing the bookkeeping. They came from the systems that person was handed. That matters, because it tells you where to point your energy: at the process, not at the individual who’s leaving.
Why losing a bookkeeper creates more risk than most businesses realise
Let me tell you about a business we worked with, because established firms tend to hear a lot of themselves in this one.
It was a family-run company that had been trading for decades. Strong reputation, loyal customers, a successful part of its local community. But the systems hadn’t changed in years, because everyone had grown comfortable with them. An old desktop accounting package that had served them perfectly well for a long time.
The real challenge was one person. One person had run the entire finance function for thirty years. She knew the business inside out. Every supplier, every customer, every employee, every quirk in the system, every little workaround that had been built in along the way. She knew all of it.
And all of it lived in her head. It wasn’t documented. It wasn’t a process. It was her.
Then she announced her retirement.
At that point it stopped being an efficiency problem and became a continuity one. That’s the shift most owners don’t see coming, because the two look identical right up until the moment someone hands in their notice.
There is a second risk that people are less comfortable discussing. Concentrating financial control in one person, with no separation of duties and no independent review, is the same condition that makes fraud possible. The Association of Certified Fraud Examiners’ Occupational Fraud 2024: A Report to the Nations found that more than half of the cases studied were linked to a lack of internal controls, or to controls being overridden. Organisations with fewer than 100 employees recorded a median loss of USD 141,000, and smaller businesses typically have the fewest controls in place.
Then there’s the piece that catches people cold. The legal obligation never transferred. Revenue is explicit that where an agent or accountant keeps records on your behalf, you remain ultimately responsible for your record keeping. Records supporting Income Tax, Corporation Tax and CGT must generally be kept for six years. Under section 285 of the Companies Act 2014, failing to keep adequate accounting records is a criminal offence, and directors can be held personally liable.
A resignation pauses none of that.
The first 24 hours after a bookkeeper resigns
What you do on day one sets up everything that follows. The goal is to protect the business without insulting someone who has, in most cases, done nothing wrong.
1. Accept the resignation in writing and confirm the last day. Get it acknowledged by email. Under Irish law, where a contract doesn’t specify a notice period and the employee has at least 13 weeks’ service, the statutory minimum is one week’s notice, under the Minimum Notice and Terms of Employment Acts 1973 to 2005. Check the contract first. Many finance roles carry four weeks or more, and that changes your entire plan.
2. Ask specifically what’s in flight. Not “how are things?” Ask which VAT return is part-prepared, which payment run is scheduled, which reconciliation is incomplete, which payroll is mid-cycle, what’s sitting unapproved. Write the answers down the same day.
3. Review access, don’t reflexively revoke it. This is where I see owners make things worse. Unless you have a specific, evidenced concern, cutting someone’s access on day one is counterproductive. They can’t hand over what they can’t see. Instead, audit the access: list every system they can log into, and flag anything where they are the only administrator or account holder.
4. Run the lotto test on every task, not just the person. Go through the finance calendar line by line. VAT, payroll, bank authorisation, ROS certificate, supplier portals, the accounting subscription itself. For each one, ask who else could do this on Monday. Anywhere the answer is “nobody” needs a named second person this week.
5. Agree the handover as a deliverable, not a courtesy. Say plainly that you want a written handover document, and set a date for a first draft inside week one. Most bookkeepers will do this willingly if you ask early. Ask in week three of a four-week notice period and you’ll get a rushed page of bullet points.
6. Tell your accountant the same day. We can usually flag the deadlines you’re now exposed on, and in many cases hold the line on VAT and payroll while you recruit.
A resignation doesn’t create the problem. It reveals it.
What information you should secure immediately
Some of this is technical and some of it is boringly administrative. In my experience the boring items cause the most pain three months later.
| Category | What to secure | Why it matters |
|---|---|---|
| System access | Every login: accounting software, banking, ROS, payroll, expense tools, supplier and sales portals | Shows you where a single administrator exists with no route back in |
| Subscription ownership | The named subscriber or billing owner for each system | The subscriber typically controls the plan and user management. If that’s the leaver, move it before the last day |
| Revenue and CRO | ROS digital certificate location and password, filing calendar, agent links | Lost ROS access after a departure delays returns and triggers avoidable penalties |
| Banking | Mandate holders, authorisers, approval limits, token custody | Bank mandate changes take weeks. Start on day one |
| Local files | Anything held on a personal drive or desktop: spreadsheets, scanned invoices, working papers | Invisible to you, and still legally your record |
| In-flight work | Open VAT period, unposted journals, unreconciled items, draft payroll, unapproved bills | This is what breaks first |
| Relationships | Contacts at suppliers, customers, the bank, the payroll provider, software support | A warm handover of contacts is worth more than people expect |
| Undocumented rules | Coding conventions, recurring adjustments, accruals, tracking categories, workarounds | The “why” behind the numbers |
One practical note on ownership. In Xero, the subscriber for an organisation automatically holds the permission to manage users, and where a subscription needs to move to someone else, the incoming subscriber has to accept the transfer invitation within 14 days. Fourteen days isn’t long if the person who needs to action it has already left and stopped checking that inbox. Do it while they’re still at their desk.
What documents should a departing bookkeeper provide?
If you ask for one thing, ask for the process. If you can ask for more, here’s the full list.
Process documentation – The month-end close sequence, step by step, in order, with timings – The daily and weekly routine: bank feeds, invoice processing, credit control – How the VAT return is built and checked, and in which tool – The payroll process and cut-off dates – Recurring journals, accruals and prepayments, with the logic behind each one
Reference material – Chart of accounts, with notes on any code that isn’t self-explanatory – Tracking category structure and what each one is used for – Supplier and customer list with payment terms and known quirks – Every integration and app connected to the accounting system
Status and position – Reconciliation status of every bank, credit card and loan account – Aged debtors and creditors, with commentary on disputed items – Open queries with Revenue, suppliers, customers or the bank – A twelve-month filing calendar
Credentials – An access register listing every system and username. Passwords should be reset and rotated through a password manager, never emailed.
A recorded walkthrough – Thirty to sixty minutes of screen-share, recorded. This is often more valuable than twenty pages of documentation, because it captures the things people forget to write down.
A word on how to build that documentation, because there’s a right way and a wrong way. When we mapped the retiring bookkeeper’s role in the case study above, we didn’t document what the software was producing. We documented what she actually did, step by step, in her own sequence. Those are different things, and the gap between them is exactly where the undocumented knowledge hides. Once we understood the real workflow, we could rebuild it properly.
How long should a bookkeeping handover take?
This applies when hiring in house.
Short answer: three to four weeks of overlap, structured around at least one complete month-end.
Anything shorter hands over the routine but misses the exceptions, and the exceptions are where things break. Anything much longer usually means the process was never documented and is being reconstructed from scratch.
| Week | Focus | Output |
|---|---|---|
| Week 1 | Discovery and security | Access register complete, subscription ownership transferred, in-flight work listed, first draft of process notes |
| Week 2 | Documentation and shadowing | Written month-end sequence, recorded walkthrough, successor observes the daily routine |
| Week 3 | Reverse shadowing | Successor does the work, leaver observes and corrects. This is the week that matters most |
| Week 4 | Close-out | Full month-end run by the successor, reconciliation status signed off, open queries listed, final access review |
If notice is only a week or two, prioritise ruthlessly: access and system ownership first, then the recorded walkthrough, then in-flight work, then documentation. Documentation can be rebuilt later. Access is much harder to recover.
Common bookkeeping handover mistakes
Treating the handover as a document rather than a process. A written handover nobody tests is a work of fiction. The only way to know it works is to have someone else follow it while the author is still there to answer questions.
Leaving it to the last week. Notice periods compress. Holidays get taken. Handover work slips behind live work, because live work has deadlines.
Not overlapping a month-end. Most bookkeeping problems only surface at month-end. If the successor never sees a close with the leaver present, they’ll find the gaps alone, under time pressure.
Assuming the accounting system holds everything. It rarely does. The spreadsheet that calculates the commission accrual, the folder of scanned dockets, the cashflow model the MD relies on. These live outside the system and disappear quietly.
Rushing into new software mid-handover. I’ll come back to this below, but installing a new system during a handover is one of the few ways to make this situation worse.
Hiring for the old role instead of the current one. The job your bookkeeper was doing may not be the job your business needs now. A departure is an unusually good moment to ask whether the role should be redesigned, part-automated or split differently. It’s a moment that only comes around every few years.
Why cloud accounting makes transitions easier, and what it won’t fix
I need to challenge something first, because it’s the single most common misconception I deal with.
Business owners often assume that moving to cloud software will improve their bookkeeping quality by itself. It won’t. The setup is the most important part, and if the setup is wrong, cloud software can make things worse rather than better. What you end up with isn’t a better process. It’s the same mistakes, made faster.
The same applies to integrations. A badly configured integration is arguably worse than no integration at all, because you’re now relying on information that isn’t reliable, and you don’t know it.
So no, a system on its own won’t save you. But with the setup done properly, there are four structural reasons cloud accounting makes a departure far less damaging.
The records belong to the business, not to a device. With desktop software, the data file sits on a machine, often in an office, often accessible to one person. Cloud systems exist independently of any individual login.
Access is granular and reversible. Xero’s user roles and permissions let you assign advisor, standard, read-only or invoice-only access, plus task-specific permissions for things like managing users or editing contact bank details. You can give a new bookkeeper exactly what they need on day one, and remove a leaver’s access cleanly on their last day, without anyone losing the records.
There’s a trail. Every time a transaction is created or edited in Xero, the change is logged with the user’s name, date and time in History and Notes, with an activity report summarising this across the organisation. When someone inherits a set of books, that trail is how they reconstruct decisions nobody wrote down. It’s also a real internal control. It doesn’t prevent errors, but it makes them visible and attributable.
Two people can work in the file at once. Overlap is only possible if the outgoing and incoming bookkeeper can both be in the system. That sounds trivial. It’s the main reason handovers on cloud systems are less painful than handovers on single-user desktop software.
Revenue permits electronic records, with conditions. Revenue’s guidance on books and records notes that where records are held electronically and Revenue requests them, you’re obliged to supply full details of the software used, with a €3,000 penalty for failing to comply. Knowing which systems hold your records, and being able to get into them, isn’t optional.
There’s one Irish quirk worth knowing if you’re on Xero. Xero’s global edition doesn’t handle Irish VAT3 reporting natively, so Xero partnered with Parolla to provide a free plugin that prepares VAT3 returns for direct upload to ROS. If your departing bookkeeper was preparing VAT manually, this is one of the quickest wins available to you.
Two more tools our clients get value from: Pleo and Expensify for expense management. If you’ve ever chased a staff member for a receipt, these change the game. Staff photograph the receipt in an app, choose a category or job code, and it feeds straight through. No petty cash pile at month-end, no “I’ll give you that receipt later” that never arrives. The team gets freedom, you keep oversight.
When to migrate. Not during a handover. Stabilise first, migrate second. If a resignation has exposed how fragile your desktop setup is, that’s a strong signal, but the sequence matters. In the retirement case above, the migration happened before the last day precisely so that the systems were doing the heavy lifting by the time she walked out. That’s the ideal. If you don’t have that runway, get through the handover, then plan the move properly.
Should you recruit internally or outsource bookkeeping?
There’s no universally right answer. There’s a right answer for your business at its current size, and it may not be the answer you’d have given two years ago.
Worth knowing before you decide: the Irish finance market is tight. Hays research reported in ACCA’s 2026 Europe recruitment outlook found 96% of employers in Ireland reporting skills shortages, with 59% of professionals planning to change roles. Internationally, 42% of finance teams surveyed in 2026 still needed 60 days or more to fill an open accounting role. Plan for the vacancy lasting longer than you’d like.
| Recruit in-house | Outsource | Hybrid | |
|---|---|---|---|
| Best when | High, consistent volume; you need someone embedded in operations | Moderate volume; continuity and specialist coverage matter more than presence | You have a finance manager buried in processing |
| Continuity risk | Concentrated in one person again, unless you change the process | Held by a team, so illness, holidays and turnover are covered | Processing is covered, internal knowledge is retained |
| Cost profile | Salary, PRSI, pension, licences, recruitment fees, management time | Predictable monthly fee, scales up and down | Between the two |
| Speed to cover | Typically 6 to 12 weeks including notice | Days to weeks | Days to weeks for the outsourced element |
| Specialist depth | Limited to one person’s experience | Access to VAT, payroll and management accounting specialists | Both |
| Watch out for | Recreating the same lotto factor | Poor onboarding. A provider still needs your process mapped | Unclear boundaries on who owns what |
The honest framing: outsourcing doesn’t remove the need for documentation, it changes who maintains it. A provider who takes you on without mapping your processes properly will recreate exactly the same fragility, one step further from you.
The option I’d encourage more owners to consider is the middle one. Plenty of the businesses we work with have a capable finance manager spending most of the week on data entry and reconciliations. Moving the processing to an outsourced bookkeeping team doesn’t replace that person. It lets them do the job you actually hired them for. When we onboard established SMEs, discovery includes a risk assessment that looks specifically for critical tasks resting on one person. That assessment is usually more uncomfortable, and more useful, than clients expect.
How to future-proof your bookkeeping function
Whatever you decide about this vacancy, here’s what stops you having this conversation again.
1. Document what people actually do, not what the system produces. One page for the month-end sequence, one for the weekly routine, one for recurring adjustments and the reasoning behind them. Three pages, reviewed twice a year. It’s the highest-return hour of admin in the business.
2. Keep a live access register. Every system, user, administrator and subscription owner, with a review date. Store it outside the accounting system and outside any one person’s control.
3. Separate duties, even in a small team. Whoever enters supplier invoices shouldn’t be the only person approving payments. If you can’t separate the roles, insert a review. A director signing off the payment run weekly is a real control and takes ten minutes.
4. Write down the approval hierarchy. Who approves what, up to what value, and what happens above that threshold.
5. Close monthly, on a fixed date. Not because reporting is the point, but because a close that has to happen on the 12th forces the process to be repeatable. A repeatable process is a transferable one.
6. Use the month-end question as a diagnostic. Ask your finance person for a deep dive on a specific product line or cost centre. If the answer is “I can get that to you at month-end”, that’s your red flag: the books are running behind and you’re making decisions on history. If the answer is “everything’s reconciled to Friday, I’ll run that for you now”, you’re in good shape. It’s the simplest test I know, and it takes one email.
7. Automate the repetitive layer. Bank feeds, invoice capture, reconciliation rules, recurring bills, expense apps. Every process you automate is a process that can’t leave with a person. AI-assisted coding and matching help here, but treat them as a first pass that reduces effort, not a replacement for review. Automation removes the typing. It doesn’t remove the judgement, and it doesn’t remove your responsibility for what’s in the records.
Good bookkeeping should never depend on one person. It should depend on good systems.
Frequently asked questions
What should I do if my bookkeeper resigns?
Confirm the resignation and last working day in writing, ask immediately what work is in flight, audit every system they can access, transfer any subscriptions or accounts where they are the sole owner, and agree a written handover as a formal deliverable in week one of the notice period rather than the last. Tell your accountant the same day so upcoming VAT, payroll and CRO deadlines are covered.
How do I hand over bookkeeping properly?
Build the overlap around a full month-end cycle. Week one is discovery and securing access. Week two is documentation and shadowing. Week three is reverse shadowing, where the successor does the work and the leaver observes. Week four is a complete month-end run by the successor with reconciliation status signed off. Record at least one screen-share walkthrough.
What documents should a departing bookkeeper provide?
A step-by-step month-end process, the weekly routine, VAT and payroll preparation methods, the chart of accounts with notes, recurring journals and their logic, current reconciliation status for every account, aged debtors and creditors with commentary, open queries, a twelve-month filing calendar, and an access register listing every system and username.
How do I protect my financial records when a bookkeeper leaves?
Confirm all records sit in systems the business controls, not on personal devices. Transfer subscription and administrator ownership before the last working day. Reset and rotate credentials rather than inheriting them. Remember that Revenue holds you, not your bookkeeper, responsible for record keeping, and that records supporting your tax returns must generally be kept for six years.
How long should a bookkeeping handover take?
Three to four weeks of overlap covering at least one complete month-end. Shorter handovers transfer the routine but miss the exceptions, which is where errors surface. If notice is shorter, prioritise access and system ownership first, then a recorded walkthrough, then in-flight work.
Should I outsource bookkeeping instead of hiring a replacement?
Outsourcing suits businesses with moderate volumes that value continuity, specialist coverage and predictable cost over on-site presence. Hiring suits high, consistent volume and close operational integration. A hybrid, keeping an internal finance manager while outsourcing the processing, often works best for growing SMEs. Outsourcing doesn’t remove the need for documented processes, it changes who maintains them.
Can cloud accounting reduce the impact of staff turnover?
Yes, substantially, provided the setup is done properly. Cloud accounting keeps records with the business rather than a device, allows permissions to be granted and revoked cleanly, logs who changed what and when, and lets outgoing and incoming bookkeepers work in the file simultaneously. It won’t fix a poorly configured system. Set up badly, it just makes the same mistakes faster.
Who is legally responsible for our books if the bookkeeper leaves?
You are. Revenue states that where an agent or accountant maintains records on your behalf, the business remains ultimately responsible for record keeping. Under the Companies Act 2014, failing to keep adequate accounting records is an offence and directors can be held personally liable.
Final thoughts
The family business I described at the start did make the change. We mapped what the retiring bookkeeper actually did, moved them onto a cloud system, automated the repetitive work she’d been doing manually for years, and built workflows that didn’t depend on anyone’s memory. We brought the historical data across so they kept their comparatives.
By the time the project finished, management had real-time numbers for the first time ever. No more waiting on one person to run a report by the end of the week. And when the retirement finally came, the handover was smooth, because the system was doing the heavy lifting.
For that business it wasn’t just a software change. It was a generational and cultural shift, and they were right to be nervous about it. But they knew it had to happen. If they could do it after thirty years, any business can.
So if you’re reading this because a resignation letter landed this week, do three things today. List every system that person can access. Ask them what’s in flight. Get the handover meetings into the diary before the notice period fills up with everything else. The longer-term structure can wait until next week.
And if you’re reading this because you’ve just realised what your own lotto factor looks like, that’s the better position to be in. You have time. Use it to write the three pages.
I’d much rather have that conversation now than the Monday morning one.
Kiera McFeely is Head of Cloud Services at Kinore, where she leads the team supporting Irish, Northern Irish and UK businesses with cloud bookkeeping, finance process design and system migration.
