Church Money, Donations & Financial Controls

Documenting Benevolence Decisions for the Auditor

Published 2026-09-05 · Church Money, Donations & Financial Controls

Short answer: for each payment, the file should hold the application, the verification of the underlying need, the approval with the right number of signatures for that amount, the payee and payment record, and one line of reasoning. Those five things, tied to a general ledger entry, answer every question an auditor asks. Sensitive personal detail stays out of the accounting file and in a restricted one.

An auditor, a new treasurer or a diligent board member pulls a sample of ten benevolence payments and asks a simple question about each: what was this, who approved it, and how do I know?

If your answer is "I remember that one," you've got a documentation problem rather than an integrity problem. From the outside those look identical, and that's the difficulty. Benevolence documentation isn't about suspicion. Half of it is settled the moment you write down who may approve what. The rest is being able to show, two years later, that a charitable decision was made on charitable grounds by the church, which is what exempt status assumes (IRS, Exemption requirements for 501(c)(3) organizations).

What does an auditor actually look for?

Four things, and none of them are exotic.

Authorization. Was this approved by someone with authority to approve it, at that amount, under a written policy the board adopted? This is the one that fails most often, usually because the policy sets a two-signature threshold and only one signature is in the file.

Support. Is there evidence of the need itself? A utility notice, a landlord statement, an invoice, a note of a phone call confirming a balance. Not proof beyond doubt. Evidence that somebody checked.

Payee and payment. Who received the money, and does the payment record match what was approved? Direct payment to a provider makes this trivial. Cash makes it nearly impossible.

Classification. Did the expense land in the right account, and is the benevolence fund's activity tracked separately from the general fund and from designated giving?

The audit isn't testing whether the church was generous enough. It's testing whether the control described in the policy actually operated.

What belongs in each file?

Keep it to one physical or digital folder per payment, containing:

1. The completed application. Who asked, their relationship to the church, the specific need, the amount, what else they've tried, and their signature and date. What to ask for on the application covers the fields in detail.
2. Verification of the need. The disconnection notice, the arrears statement, the repair quote, or a dated note recording a call to the provider. One line is enough: "Called utility 3/14, balance confirmed $412, payment stops disconnection."
3. The approval block, completed. Amount approved (which may differ from the amount requested), payee, approvers with the correct count for that tier, and the date.
4. The payment record. Check number or transaction reference, and the invoice or account number paid.
5. One line of reasoning. "First request, one month's arrears, verified with the utility." In three years this sentence will be the entire institutional memory of the decision.

Add a sixth item when it applies: a note of anything offered besides money, such as a referral, a budgeting conversation, or a connection to an agency. Churches that record this find their own patterns much faster.

How do we keep it confidential and still auditable?

This tension is real and it has a clean answer: split the file.

The accounting file holds what an auditor needs: application summary, amount, payee, approvals, payment record, the one-line reason. It contains no medical detail, no family circumstances, no narrative.

The restricted file holds anything sensitive that informed the decision, and only a named short list can open it. Most churches settle on the treasurer and the board chair, or a two-person benevolence committee.

Two habits make this work. Collect the minimum that supports the decision in the first place, because you may need to know a prescription is unaffordable but you don't need the diagnosis. And keep benevolence files out of any shared drive the whole staff can browse.

An auditor can test a control without reading a family's medical history. If yours insists otherwise, that's a conversation to have with your CPA about scope.

How does it tie to the books?

Three connections, and all three get checked:

The ledger. Each payment posts to a benevolence expense account, not to a miscellaneous line. If your chart of accounts has no benevolence account, add one before your next payment.

The fund balance. Benevolence contributions in, benevolence payments out, running balance reported to the board. That doesn't require a separate bank account. It requires separate tracking. Many churches assume the opposite and open an account they then have to reconcile.

Designated gifts. Contributions to the benevolence *fund* are ordinary charitable gifts, because the church retains discretion over their use. Money handed over for a named individual is a different animal and generally isn't a deductible contribution at all (IRS Publication 526, Charitable Contributions). Keep the two apart in the records, because an auditor who finds them mixed will have questions that go beyond documentation. The wider picture is in helping people without risking your exemption.

A worked example

Here's what a complete file looks like.

Request: March 14. Regular attender, not a member, no employment relationship with the church. Past-due electric bill, $412, disconnection notice dated March 11 attached. Applicant has contacted the utility's hardship program and been declined. No prior assistance.

Verification: Staff note reading "Called utility 3/14 at 10:20am, account balance confirmed $412, payment by 3/18 stops disconnection."

Approval: $412 approved, Tier 2, signed by the pastor and the board chair on March 14. Payee: the utility, on account number ending 4471.

Payment: Check 2214, March 15, $412, posted to Benevolence Expense.

Reason line: "One month's arrears, verified with provider, first request."

Five documents, one folder, about twenty minutes of staff time. When the auditor pulls this one in eighteen months, there's nothing to explain.

Now the version that fails. Same family, same need, but a staff member pays it from petty cash, writes "benevolence" on the receipt, and the application gets filled in the following week from memory with no verification and one signature. Nothing dishonest happened. There's simply no way to show that, and the auditor's finding will say the control didn't operate.

How do churches get this wrong?

Reconstructing files afterward. A file assembled at audit time is visibly a file assembled at audit time. Complete it at the moment of the decision or not at all.

Cash. It leaves no trail, it's the hardest thing to defend, and it removes the one document that would otherwise prove the point for you: the provider's invoice.

One signature above the threshold. The most common finding by a distance. Build the tier onto the form so the blank space is visible.

Filing everything in one drawer. Sensitive detail and accounting support have different audiences. Split them.

No policy behind the file. Documentation shows that a standard was applied. Without an adopted policy there's no standard to apply, and each file just shows one person's judgment. The essential sections of a benevolence policy is the place to start.

Discarding files early. Keep them with your financial records on the same retention schedule your record retention policy sets, and make sure that policy actually names them.

Common questions

Does our church even get audited?

Many churches never engage a formal audit, and most churches aren't required to file the annual information return that other exempt organizations file (IRS Publication 1828, Tax Guide for Churches). Confirm your own filing obligations with your CPA, though, because state-level requirements and unrelated business income can change the answer (IRS, Unrelated business income tax). Either way, the same file answers a bank, an insurer, a grant-maker, a new treasurer, or a member who asks a pointed question at an annual meeting.

Can an auditor demand names?

Scope is something you agree in the engagement. It's entirely reasonable to discuss how sensitive information will be handled before fieldwork starts, and a firm experienced with churches will have a settled approach.

How long do we keep the files?

On the same schedule as your other financial records, and treat them as confidential throughout. If your retention policy doesn't mention benevolence files, amend it so nobody has to guess.

What if a payment was made outside the policy?

Document what happened, report it to the board, and record the board's ratification or correction. A documented exception is a manageable finding. An undocumented one looks like something else entirely.

The practical wrap

Five items per file, completed at the time of the decision, split between an accounting folder and a restricted one. Post every payment to a benevolence account and report the fund balance to the board at every meeting.

Do that and the audit conversation takes ten minutes. Skip it and the same conversation takes a month and never fully resolves, not because anyone did anything wrong, but because you can't prove a decision that was never written down. If you're weighing what level of outside review your church needs, audit, review or compilation sets out the difference.

---

Make the file build itself. The Benevolence Fund Policy is the policy, the application and the approval record in one place, built around the documentation this area calls for, so each payment closes with the evidence already assembled. $49, instant download.

*Faith Docs provides self-help document templates, not legal advice. We are not a law firm. For representation, consult a licensed attorney.*