A treasurer who's served for years leaves, whether from moving, health, or simply because it's time to hand off, and takes with them accumulated knowledge that was never documented anywhere. Here is how to keep that departure from becoming a financial crisis.
Why this transition is riskier than it seems
A long-serving treasurer accumulates not just records, but tacit knowledge: where certain documents are, why a specific category exists, verbal agreements with vendors that were never formalized. None of it is written down anywhere until someone needs to find it and discovers it isn't.
What to document before the departure happens
- Access and credentials. Bank accounts, online systems, who's authorized for what, all of this needs to be clearly listed and transferable.
- Recurring processes. How and when regular payments are made, what approvals are needed, calendar of tax or legal obligations.
- Historical context for important decisions. Why a certain fund exists, why a specific recurring expense was approved, information that prevents future misinterpretation.
How to transition without a knowledge gap
An overlap period, even a short one, where the previous and new treasurer work together, is worth more than any written document alone. Questions that only come up in practice get immediate answers during that period.
What to do when the departure is unexpected
Not every departure allows for a planned transition. Keeping basic documentation always updated, not just at the moment of departure, is what protects the church when a treasurer leaves suddenly, due to illness or a personal emergency.
How to keep the next person from repeating the same problem
If documentation is only created when someone leaves, the cycle repeats with the next treasurer. Making documentation part of the ongoing process, not just an exit exercise, ensures real long-term continuity.
What this means in practice
A good treasurer transition protects decades of the church's financial history. The Ekklesias Finance module keeps all history and context in the system, not in one person's memory. You can see how the full platform works.
← Back to blog