How to prepare for a finance-system handover

Define the boundary of the handover

Write down what is moving, what is staying and the effective date. The scope may include bookkeeping processes, reporting, payment preparation, payroll inputs, expenses, billing, collections, forecasting or selected system administration. Avoid broad labels such as 'the finance function' unless the underlying activities are listed.

Record the organisations, entities, bank accounts, currencies, systems and reporting periods in scope. Name the outgoing owner, incoming owner and approver for each activity. If another provider or internal team remains involved, make the hand-off points explicit.

• Activity and expected output.
• Frequency, timetable and cut-off.
• Preparer, reviewer and final approver.
• Required inputs and where they originate.
• Dependencies, exceptions and known constraints.

Create a complete systems and access map

List every application and data source used in the workflow, not only the general ledger. This may include banking portals, billing tools, expense systems, payroll platforms, payment gateways, stock systems, document stores and reporting models. Note how information passes between them and which transfers are automated or manual.

Access should be granted through named accounts with permissions appropriate to the role. Avoid circulating shared passwords in a handover document. Record who can add or remove users, who approves changes and how access will be tested. Plan the removal or adjustment of outgoing access for the agreed transition point, following the organisation's security procedures.

Establish a clean data cut-off

Agree the date and state in which records will transfer. Complete or clearly identify outstanding bank reconciliations, posting queues, expense claims, invoices, credit notes and journals. Where an item cannot be resolved before handover, log it with an owner, supporting evidence and expected next action.

Retain the relevant closing reports and control totals so the incoming team can confirm that the opening position agrees with the approved handover point. Where data will move between systems, test the migration with representative records and reconcile totals rather than relying on a successful import message alone.

• Last completed and reviewed reporting period.
• Reconciliation status for each bank and control account.
• Receivables and payables ageing, including disputed items.
• Unposted, duplicated or suspense items requiring attention.
• Current chart of accounts, tracking fields and reporting mappings.
• Open forecasts, budgets and material assumptions.

Document the operating rhythm

A useful process note explains the sequence of work, the evidence retained and the review performed. It should be clear enough for a capable person to follow without depending on unwritten knowledge, but concise enough to remain maintainable.

Include daily, weekly, monthly, quarterly and annual routines where relevant. Capture normal timing and the escalation route when information is late, a reconciliation does not agree or an approval is unavailable. A calendar view helps expose clashes and dependencies that individual process notes can hide.

• Input source and expected arrival time.
• Steps performed, including system and report names.
• Review evidence and approval threshold.
• Output location, naming convention and retention approach.
• Common exception, resolution route and escalation owner.

Surface judgement and unfinished work

The most valuable handover conversations often concern items that are not obvious from the ledger: unusual customer arrangements, recurring estimates, disputed balances, manual workarounds, fragile spreadsheets and deadlines dependent on one person. Record these openly rather than allowing the incoming team to discover them during the first close.

Maintain an issues log with a description, financial or operational effect, evidence available, current position, owner and next review date. Distinguish confirmed facts from assumptions or matters still under investigation.

Transfer knowledge through demonstration

Documents are necessary but do not replace observing the process. Use walkthroughs in which the outgoing owner demonstrates a complete task, explains the reason for each control and shows how exceptions are handled. The incoming owner should then perform the task while the outgoing owner observes and answers questions.

Record questions and update the process note during the session. If timing permits, run a limited parallel cycle for the highest-risk routines. The objective is to reveal gaps before responsibility changes, not to reproduce every task indefinitely.

Set acceptance criteria for the first cycle

Agree what a successful first reporting or processing cycle will look like. Criteria might cover completion of reconciliations, delivery of agreed reports, clearance of priority exceptions, review sign-off and adherence to the new responsibility map. Name the person who will accept the handover and the date of the review.

Hold a short retrospective after the first cycle. Confirm what worked, which instructions were incomplete and whether roles or access need adjustment. Keep a time-limited transition log until the important gaps have named resolutions; do not allow it to become a permanent substitute for the normal process documentation.

• All in-scope systems and permissions tested.
• Opening balances or control totals agreed to the handover record.
• Priority routines completed and independently reviewed.
• Known issues assigned, prioritised and dated.
• Outgoing access changed at the agreed point.
• Process documents updated to reflect the live method.

The handover pack at a glance

Keep the final pack in an access-controlled location with clear version dates. It should point to authoritative source files rather than creating unmanaged copies. Assign an owner to review the pack when systems, people or processes change.

• Scope, responsibility matrix and key contacts.
• Systems map, access owners and data-flow overview.
• Close calendar and recurring activity schedule.
• Process notes, controls and approval routes.
• Closing reports, reconciliations and migration checks.
• Open items, risks, assumptions and decisions log.
• First-cycle acceptance criteria and review date.