--- title: "A finance colleague leaves: handing over cases without losing commitments" canonical: https://www.billabex.com/en/blog/finance-employee-departure-case-handover/ lang: en alternate: https://www.billabex.com/fr/blog/depart-collaborateur-finance-passation-dossiers.md updated: 2026-10-12 index: https://www.billabex.com/llms.txt --- # A finance colleague leaves: handing over cases without losing commitments The colleague responsible for outstanding invoices leaves on Friday. Invoices are in the accounting system, conversations are in their mailbox and several agreements exist only in their notes. Next week's main risk is not losing the total receivables balance. It is sending a reminder inconsistent with what was agreed. A successful handover allows the successor to understand the next action without reconstructing the entire history. It also arranges appropriate access, continuity of incoming customer replies and removal of the departing colleague's access. These three matters need coordinated preparation, with a distinct check for each. ## Transfer the next decision, not only an invoice list For every active case, retain the verified balance and its date, the useful contact, the last established fact, the current commitment and the next action. Identify the person who can decide when the case exceeds routine handling. “Difficult customer, ask Paul” stops being useful when Paul is unavailable. Replace general judgements with facts: “The customer disputes travel expenses on invoice F217; sales must provide the prior agreement before Thursday.” The successor then knows which evidence to find, whom to ask and why another demand for the full amount would be premature. The approach to [allocating invoice dispute decisions](https://www.billabex.com/en/blog/invoice-dispute-decision-owner/) provides a basis for these referrals. Taking over a portfolio does not automatically give someone authority to approve a credit note, payment extension or debt release. Their authority must match their role. ## Build the inventory around current situations Consider an entirely simulated portfolio of eighteen cases, representing €90,000 still open at handover. Each case belongs to only one main category here, avoiding double counting of the same amounts. | Main simulated situation | Cases | Open amount | Information to transfer | | ---------------------------- | ----: | ----------: | -------------------------------------------- | | Precise promise to check | 5 | €30,000 | Date, amount, documents and original message | | Dispute requiring a decision | 4 | €24,000 | Disputed component and decision-maker | | Evidence to provide | 3 | €18,000 | Expected document and responsible person | | Routine follow-up | 4 | €12,000 | Last action and next contact | | Payment to allocate | 2 | €6,000 | Bank reference and remaining investigation | | Total | 18 | €90,000 | Identified successor | Suppose the five promises, three document requests and two allocations require action within the following seven days. These are ten cases, or 55.6% of the total count, but €54,000, or 60% of open value. Sorting by the next required action therefore produces a different priority from invoice amount alone. These proportions describe this scenario, not a finance team benchmark. Reconcile the real inventory against accounting records and recent exchanges. An inventory omitting paused cases may appear complete while excluding the situations most dependent on the departing colleague's memory. Mark when the inventory was prepared. A payment arriving after that point should update the case before any reminder is sent. Handover evidence is a reference position, not a reason to stop checking the current balance during the transition. ## Preserve commitments in both directions Transfer what the customer promised and what your own business agreed to do. Supplying evidence, calling a particular contact or awaiting a sales response belongs in the case. Otherwise, the new owner may request payment while the obstacle remains within your company. For a promise, retain the relevant wording and source together with the exchange date. Distinguish “we will initiate the transfer on Friday” from “funds will be available on Friday”. The approach to [tracking a payment promise](https://www.billabex.com/en/blog/verifiable-payment-promises/) helps preserve that difference during a handover. Do not remove uncertainty simply to make the table cleaner. If a note says “verbal agreement to confirm”, preserve that limitation and identify who will resolve it. A summary should not turn an assumption into an accepted commitment or extend an agreement to invoices it did not cover. Include the reason for waiting. A date without its explanation can look like an arbitrary delay to the successor. Linking the date to the evidence request or agreed customer action makes the next decision easier to assess if circumstances change. ## Let the successor work through cases before departure Run a reverse demonstration: the successor opens a case themselves and explains what they would do next. The departing colleague intervenes only to add information or correct the interpretation. This reveals missing information faster than a presentation delivered entirely from one person's memory. Choose contrasting cases: a near-term promise, a dispute involving several people and an unallocated payment. Check that supporting documents open from the successor's account. A link that works for the departing person may depend on a personal sharing arrangement removed when they leave. The acceptance criterion is the ability to act: locate evidence, explain the amount, identify the approver and prepare a coherent response. If the successor still needs to ask why the team is waiting, the reason has not been documented sufficiently. Correct the case and apply the same check to comparable situations. ## Transfer access without transferring an identity CNIL recommends access limited to the role, approval of permissions and removal when access is no longer justified, including at the end of employment. Taking over a portfolio is therefore not a reason to share the departing person's password. [CNIL guidance on access permissions](https://www.cnil.fr/fr/securite-gerer-les-habilitations). The successor should use their own account with appropriate permissions. An administrator checks access to invoices, shared documents, histories and connected tools. They should also examine automations depending on the departing account: an export or synchronisation can stop after access removal even though the case list was transferred successfully. The roles complement each other. Finance explains what must continue working, the administrator arranges access changes and the responsible manager approves the scope. Temporary access granted for the handover needs an expected end and review once the transition is complete. ## Plan email continuity around content and destination CNIL calls for advance rules governing professional mailbox access, respect for messages identified as personal and notice to the employee of account closure. It then calls for deletion of the person's named email address. Service continuity must be arranged within those rules rather than by indiscriminately copying the whole mailbox. [CNIL on mailbox access during absence or departure](https://www.cnil.fr/fr/lacces-la-messagerie-dun-salarie-en-son-absence). Microsoft 365 documentation distinguishes blocking sign-in, preserving useful data, successor access and account deletion. It illustrates why deleting first and planning later can interrupt incoming mail. Available technical features do not replace French requirements concerning personal data and named addresses. [Microsoft 365 guidance for a departing employee](https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/remove-former-employee?view=o365-worldwide). With the responsible teams, arrange transfer of necessary professional material and a lasting customer contact point. Inform active contacts about the change while preserving existing commitments. The successor's introduction should confirm continuity, without automatically asking the customer to resend documents your company already holds. ## Check the first week after the handover Following departure, review actions falling due, replies actually received and links to supporting material. The ten priority cases in the example are not operationally handed over until their new owner can continue handling them. A name in a column does not establish either access or understanding. The [collections audit trail](https://www.billabex.com/en/blog/collections-audit-trail-automation/) helps follow actions before and after the transition. Preserve the original author of historical decisions and record new actions under the account of the person who actually takes them. The [Billabex customer view](https://www.billabex.com/en/product/customer-view-360/) helps assemble the operational information the team needs to take over. The intended result is observable continuity: consistent facts, preserved commitments, an identified new contact and a controlled next action, without depending on an old password or the availability of someone who has left the business. ## Sources - CNIL, access permission management, 13 March 2024. - CNIL, access to an employee's mailbox during absence, 27 July 2009, accessed 7 September 2026. - Microsoft Learn, removing a former employee in Microsoft 365, updated 15 June 2026.