Finance function transitions are among the highest-risk events in a company’s operational life. When a controller or CFO leaves - or when a company brings one in for the first time - the window between the departure of the previous person and the full operational effectiveness of the new one is a period where significant things can go wrong quietly.
Month-end closes get delayed. Supplier payments miss their dates. A bank covenant question arrives and nobody knows the answer. A tax deadline approaches and the filing has not been started. Each of these is manageable in isolation, but in combination, during a handover period with a new person finding their feet and an outgoing person whose attention is elsewhere, they can compound into a genuine operational problem.
This article covers what a well-structured handover looks like from the controller’s perspective: what documentation to prepare, how to structure the knowledge transfer, and the failure points that most transitions encounter and how to avoid them.
The Principle: Knowledge That Lives in One Person’s Head Is a Liability
The most common reason finance function handovers are painful is that the departing controller was the sole repository of critical operational knowledge. They knew which bank accounts to use for which payments. They knew which supplier calls for advance notice. They knew where the SAP configuration documentation was stored, or that it did not exist and the system only worked because of a workaround they had maintained for two years.
This knowledge is invisible until the person who holds it is no longer available to answer questions. A well-run finance function documents its processes continuously, not just at transition time. The handover should be the transfer of already-documented knowledge, not a race to document everything before the departure date.
The practical implication: if you are a controller reading this in a stable period with no transition on the horizon, the right response is to build the documentation now. The value of doing so is not just continuity - it is the discipline of writing down processes that surfaces the ones that need to be improved.
What to Document Before the Transition
The departing controller should produce or update the following documentation before the handover begins, ideally with two to four weeks before their final date.
Month-end close playbook. A step-by-step description of the month-end close process, including: the close calendar with specific tasks and deadlines, the sequence of accruals and allocations, which entries require which approvals, the ERP transactions used for each close step, the reconciliations performed and where they are stored, and the management report template with instructions for updating it. This document should be detailed enough that someone with solid accounting and ERP knowledge but no knowledge of this specific company could perform a close using it.
Banking and treasury manual. Payment authorisation structures, the list of bank accounts and their purposes, the credit facilities and their terms, the covenant schedule and next review dates, and the contact names at each bank. This is the document that prevents payroll from being missed when the person who always handled it is gone.
Supplier and vendor register. The list of key suppliers with the payment terms agreed for each, any suppliers who require advance notice or who have specific invoice processing requirements, and any supplier relationships that carry commercial sensitivity.
Tax and compliance calendar. The full schedule of statutory deadlines: MWST filings, AHV/ALV/BVG payments, direct tax instalments, audit dates, and the annual accounts filing deadline. With the name of the external party responsible for each item (Treuhänder, payroll provider, pension fund administrator) and the internal action required to prepare for it.
System access and configuration notes. Login details for every finance system (stored securely, ideally in a password manager). Notes on any non-standard ERP configuration or known system quirks that affect the close or reporting process. The location of financial models, budget files, and management report templates.
Key relationship contacts. The relationship manager at the bank, the contact at the Treuhänder, the audit engagement manager, the pension fund administrator, the payroll provider, and any other external parties whose cooperation the finance function depends on.
The Handover Structure: Overlap Is Not Optional
The single most important structural decision in a finance function transition is whether there is an overlap period: time during which both the outgoing and incoming person are present and actively working together.
A handover without overlap is a handover that depends on documentation alone. Documentation is important, but it is never complete. There will always be questions that arise in the first month of a new role that the documentation does not answer. Without access to the person who knows the answer, those questions take longer to resolve and the risk of errors increases.
A four-week overlap is the minimum for a straightforward single-entity Swiss SME. During this period, the incoming controller should shadow at least one month-end close from start to finish, attend any regular management meetings where financial reporting is presented, and be introduced to all key external relationships.
A structured handover log, maintained during the overlap period, captures every question the incoming person asks and the answer given. By the end of the overlap, this log is a supplementary FAQ for the first months of independent operation.
The First 90 Days: What the New Controller Should Focus On
The incoming controller should not immediately try to change everything. The first 30 days are for learning: how the business works, how the finance function works, where the pain points are, and who the key relationships are internally and externally.
The first month-end close should be completed as close to the existing process as possible, even if the process has obvious inefficiencies. Making changes before understanding why things work the way they do is a reliable way to introduce new errors. Once the close has been completed once, the controller has the context to assess what should change.
The first 60 to 90 days are appropriate for identifying the two or three highest-priority improvements to the finance function and presenting a structured plan to the CEO or board. Not a comprehensive reorganisation, but a focused set of changes with clear rationale and expected outcomes.
When There Is No Overlap: The Emergency Protocol
When a controller leaves without notice, the immediate priorities are:
Payroll must run. Identify who has access to the payroll system and the payment authorisations, and confirm the next payroll date and the steps required.
Supplier payments must continue. The accounts payable ageing needs to be reviewed and critical payments authorised through the normal approval structure, even if the processing steps are being done by someone who does not normally handle them.
The bank must be informed. A brief notification to the relationship manager that the finance function is in transition, with confirmation that business continues as normal, prevents unnecessary concern and demonstrates professional management.
The Treuhänder must be briefed. They will need to provide more active support during the transition period and should know as soon as possible that it has begun.
For the month-end close, the question is whether it can be completed adequately with internal resources and Treuhänder support, or whether external interim support is needed for a period. Article 46 covers this scenario in detail.
Considering a fractional controller or CFO? Book a free 30-minute call to discuss what makes sense for your business.
Alessandro Ratzenberger is a fractional CFO and business controller based in Zurich, with 15 years of operational finance experience at Dufry Group and Bomi (UPS Group).
