A benevolence fund creates a strange kind of record. The board wants to see that the money went somewhere real and was handled honestly. The family who received help wants, understandably, for as few people as possible to know they needed it. Both of those are legitimate. The record-keeping problem is building a system where satisfying the first does not require sacrificing the second.
Most small churches solve this badly by accident, not by design. The rent assistance goes through the same spreadsheet as everything else, a line item reads “J. Martinez — $400 — utility bill,” and six months later that spreadsheet is open on a laptop during a finance meeting with three volunteers in the room who did not need to learn that. Nobody meant harm. The structure just did not separate the two things people were trying to protect: proof of stewardship, and a family’s privacy.
Separate the transaction from the story
The fix starts with a distinction that is easy to state and a little harder to hold onto in practice: the transaction (an amount, a date, a fund) is a financial record. The story (why this family, what happened, who referred them, what was said in the living room) is a pastoral record. They belong in different places, seen by different people, for different reasons.
The transaction has to exist somewhere your treasurer and your accountant can find it, because it is real money leaving a real account and someone will ask about it eventually — an auditor, a new board member, the IRS if you are ever selected for review. The story does not need to travel that far. It needs to exist somewhere your pastor or a designated deacon can find it if the same family asks for help again next year, or if the board specifically asks who was served and why. It does not need to be visible to whoever is reconciling this week’s offering count.
What the board actually needs to see
Ask your board directly what they are trying to verify, because it is usually narrower than “every name.” In most churches the honest answer is something like: how much came into the fund, how much went out, that the disbursements match documented need rather than favoritism, and that no single person is quietly controlling the fund without oversight. All four of those can be shown with a summary — total in, total out, count of families served, largest single gift, disbursements by month — and none of them require a name on the page the whole board is looking at.
Where the tension shows up is the audit trail underneath that summary. Somebody has to be able to open a specific line and confirm it was real: a receipt, a case number, a signature. That somebody is usually the treasurer, sometimes alongside the pastor or a benevolence committee chair, and it should be a named, agreed-upon short list — not “whoever happens to have the login today.”
A structure that holds up
A workable pattern for a church of 60 to 250 people looks like this. Every benevolence gift gets logged as a giving transaction against a “Benevolence Fund” category — date, amount, and a case number or initials instead of a full name in the description field. The full name, the circumstances, who requested help, and what was decided live in a separate pastoral care note, referenced by that same case number. Anyone pulling a giving report or a fund total sees the numbers. Anyone with a legitimate reason to know who was helped — typically the pastor, working a case — can look up the case number and find the rest.
In SundayBridge, this maps onto two things that already exist for different reasons: contributions recorded against a fund, and pastoral care cases with their own comment history. Recording the disbursement as a contribution keeps it inside your normal giving reports and year-end reconciliation. Keeping the case detail in pastoral care keeps it out of the giving list a volunteer counter might glance at.
Worth saying plainly: SundayBridge has one login per church, not separate staff roles, so this separation is a matter of where you choose to type the information — not a lock the software puts on a door for you. If your board decides even that is not private enough for a particularly sensitive case, the old, low-tech answer still works fine alongside it: a locked drawer or a single paper folder the pastor controls, referenced by number only.
Naming a fund without naming a person
Case numbers do not have to be bureaucratic. “BF-2025-14” works, and so does something more human like a month-and-sequence code your pastor can keep in their head. What matters is consistency: the same identifier appears on the transaction and on the case note, and nowhere does the transaction description include a last name, an address, or a detail specific enough to identify someone to a person who happens to see the report on a screen across the room.
Resist the temptation to make the code descriptive enough that it defeats the point — “eviction-Smith-Oct” is not meaningfully more private than the name itself. A plain sequential number, cross-referenced only in the pastoral file, is doing its job precisely because it tells a stranger nothing.
What to write down for every gift
Whatever system you use, capture the same handful of facts every time, because consistency is what makes an audit trail defensible rather than a pile of good intentions:
- Date and amount of the disbursement.
- Fund the money came from, if you run more than one benevolence-type fund.
- A case identifier, not a name, on the financial record.
- Who approved it — a name or role, so approval itself is never anonymous.
- A one-line reason category (housing, utilities, medical, funeral) for reporting, without narrative detail.
- Where the fuller story lives, if someone with a legitimate reason needs it.
That last line is easy to skip and it is the one that saves you later. Six months from now, when a new board member asks how the fund is governed, “the detail is in pastoral care, ask the pastor” is a complete, confident answer. Without it, the honest answer is “I’m not sure who knows,” which is exactly the gap that erodes trust in a fund that depends on it.
Setting the rule before you need it
The best time to decide who can see a recipient’s name is before anyone asks, in a calm meeting, not in the middle of an audit or a disagreement. Write one paragraph into your finance policy: who approves benevolence disbursements, who can see case-level detail versus fund-level summaries, and how long records are kept. It does not need a lawyer. It needs to exist, so that when a board member asks a pointed question, the answer is a policy you already agreed to, not a judgment call made under pressure about one specific family.
That written rule also protects the treasurer, who is often the person caught in the middle — expected by the board to prove diligence and expected by the pastor to protect confidentiality. A clear policy means the treasurer is following a rule the whole board signed off on, not making a discretionary call about a neighbor’s business every time a check goes out.
When the fund grows past what one person can track
Small funds run fine on a treasurer’s memory and a shoebox of receipts. Once a church is disbursing benevolence regularly — a few gifts a month rather than a few a year — the informal version starts to strain, usually around the same time other giving patterns start needing more than a glance to understand. That is a good moment to formalize the case-number system above, even if you have been getting by without it, and to check that your fund total reconciles against actual disbursements the way it would need to for your year-end statements and any outside review. It is also a good moment to confirm your household and contact records are current, since a benevolence case is one of the few places where an out-of-date address or a name spelled two different ways in your directory becomes more than a minor annoyance.
None of this requires elaborate software or a committee. It requires deciding, once, where the number goes and where the story goes — and then actually keeping them apart every time, even on the Tuesday afternoon when it would be faster to just write the name.