Two funds sit on most small-church budgets under names that sound almost interchangeable: a benevolence fund and a member assistance fund. They are not the same thing, and treating them as if they were is one of the quieter ways a church gets into trouble with the IRS. One fund exists to help anyone who walks through the door with a real need. The other, narrower and riskier, exists to help members specifically — and the rules for who can run it, approve it, and benefit from it are stricter because the temptation for self-dealing is higher.
This is not a distinction most treasurers learn on purpose. It usually surfaces the hard way — a denominational audit asks who approved a gift to the board chair’s adult son, or a visiting family asks for help and someone has to decide, on the spot, whether the fund even covers them. Getting the two funds straight before you need the answer is cheaper than sorting it out afterward.
What a general benevolence fund actually is
A general benevolence fund is charitable relief for anyone in genuine need — the family stranded by a car repair, the neighbor two months behind on rent, the stranger who called the church office because someone told them this church helps people. Membership is not a qualifying test. Need is. The IRS treats this kind of giving the same way it treats any other charitable activity a 501(c)(3) undertakes: it has to serve a charitable class broad enough that no single person or small group is the real, intended beneficiary.
That breadth is the whole point, and it is also the fund’s built-in protection. A benevolence fund that in practice only ever pays out to people the pastor already knows well starts to look less like charity and more like a private slush fund, even if every gift was sincere. Writing the fund’s purpose broadly — and then actually granting from it broadly — is what keeps it defensible.
What a member assistance fund is, and why it is riskier
A member assistance fund narrows the pool on purpose: help for people already in the congregation, often tied to a membership roll or a minimum attendance history. Churches build these for good reasons — a sense that the church takes care of its own first, or a wish to route help through people who already know the family’s situation. The risk is structural, not moral: the smaller and more insular the pool of eligible recipients, the easier it is for a fund like this to drift into private benefit, where insiders quietly funnel money to each other under a charitable label.
None of this means a member assistance fund is illegal. It means it needs tighter guardrails than the general fund does: a documented needs test, an approval process that does not run through one person alone, and recusal whenever a request touches the approver’s own family. The narrower the eligible group, the more the paperwork has to do the work that breadth would otherwise do for you.
The line that actually matters: the needs test
Whichever fund you run, the IRS wants to see evidence that a real need existed and that the gift was sized to it, not handed out as a flat amount regardless of circumstance. A workable needs test asks, in writing, for each request:
- What is the need, in specific terms — not “financial hardship” but “March rent, $850, eviction notice dated”.
- What amount was requested, and what amount was actually approved, and why the two might differ.
- Who approved it, and whether that person has any relationship to the recipient that would call the decision into question.
- Whether the payment went directly to the landlord, utility, or funeral home rather than as cash to the individual — the stronger practice, and the one that survives scrutiny best.
A flat $200 handed to whoever asks, no questions, no documentation, is the pattern auditors flag fastest — not because $200 is a large sum, but because a fund with no needs test looks indistinguishable from a gift registry.
Setting the fund up so the paperwork exists before you need it
The policy that protects a benevolence fund is boring, and that is the point: a one-page written policy naming who can approve requests, what documentation each request needs, a dollar threshold above which a second signer is required, and a rule that no approver can sign off on their own household. Board minutes should reference the policy’s existence, even if the individual case files stay confidential. A church that can produce that one page in an audit answers most of the hard questions before they are asked.
Where a church management system earns its keep here is unglamorous: it keeps the request, the amount, and the approver attached to a real contribution record rather than a sticky note, so the treasurer six months from now can find it without asking three people. SundayBridge records that kind of gift like any other contribution — recorded, editable, tied to a giving history — while keeping the underlying case notes in pastoral care, which stays discreet and separate from the giving ledger.
How the two funds show up differently in your records
In practice, the distinction is mostly about which bucket a gift lands in and who is allowed to see the reasoning behind it. A benevolence gift to a stranger is a straightforward line: fund, amount, date, brief note on the need. A member assistance gift usually carries more context — history with the family, whether this is a repeat request, what else the church has already tried. That context belongs in a pastoral case file, not scattered across email threads that outlast whoever wrote them. Keeping that separation clean is part of the same discipline covered in tracking giving that respects the giver — a benevolence recipient did not ask to have their situation discussed at the next board meeting, and the records should reflect that.
At year end, benevolence gifts the church makes out are a different animal from the contributions members make in. If your church also issues giving statements to donors who fund the benevolence line, the mechanics for that are the same ones covered in year-end giving statements, and they are worth getting right independently of how the assistance side is run.
The one thing worth deciding before your next request comes in
Most churches do not fail this test because they meant to cut corners. They fail it because the first request came in before anyone had written the policy down, and by the time a second request arrived, whatever was decided the first time had already become the unwritten rule. Deciding now — general or member-specific, who approves, what documentation is required — costs an hour of a board meeting. Deciding it in the middle of an audit costs considerably more. Folding that hour into whatever cadence your treasurer already keeps for reviewing the books, as covered in a weekly church admin rhythm, is usually enough to keep the policy from going stale.