Member Giving Records: Pledges, Statements & Confidentiality
Recording who gave what is the most sensitive data a church holds, and the most useful. Pledges against actual giving, statements members can check, and the confidentiality discipline that determines whether people trust you with the record at all.
Churches split into two camps on giving records, and both positions are held sincerely. One says giving should be anonymous, because the moment leadership knows who gave what, giving is no longer purely between the member and God. The other says a church that cannot tell a member what they gave last year is failing at basic stewardship of information the member is entitled to.
In practice most churches end up needing attributed records for some giving — pledges, building fund commitments, anything a member may need a statement for — and genuinely anonymous handling for the general offering. What matters is that the split is deliberate and stated, rather than discovered by a member who is surprised to learn a record exists.
Decide the policy before the system
This is a governance decision, not a software configuration, and it should be settled and communicated first. Three questions, answered in public.
-
Which giving is attributed?
Common answer: pledges, standing contributions and anything given by bank or mobile transfer where the identity is unavoidable. The loose offering stays unattributed because it genuinely can be.
-
Who may see an individual's record?
The narrowest defensible list — typically a treasurer and one other, and specifically not the pastoral team. Members are far more comfortable with a finance officer knowing than with the person who counsels them knowing.
-
What is the record used for?
Statements to the member, pledge follow-up, and the annual accounts. Not for pastoral decisions, not for leadership selection, and never as an input to how somebody is treated. Say this out loud, because members assume the opposite.
Say it from the front, once a year
A short, plain statement of what is recorded, who can see it, and what it is used for — repeated annually — does more for giving confidence than any assurance given individually when somebody asks. Most suspicion about church giving records comes from the absence of an explanation rather than from the records themselves.
Members are rarely uncomfortable that a record exists. They are uncomfortable that nobody told them who can see it — and that silence is the thing you can fix in one announcement a year.
Pledges are a receivable that is not a debt
A building-fund pledge is a promise, not an obligation, and treating it as either extreme causes problems. Treated as a debt, follow-up becomes coercive and members resent it. Treated as nothing, the church budgets on a total that never arrives and a project stalls halfway.
The workable position is to track pledges against fulfilment honestly, use the fulfilment rate for planning, and follow up as a reminder rather than a demand. Every church that runs a capital project learns the fulfilment rate matters more than the pledge total; the ones that learn it early plan on the right number.
Why the pledge total is the wrong planning figure
Illustrative, in KES. The pledges were made in good faith and much of the balance will arrive eventually — but the timing is the problem, not the sincerity. Committing on the pledge total rather than on the observed fulfilment rate is how well-supported church projects end up half-built and quietly embarrassing. The fund-tracking discipline is in church building and project fund tracking.
Statements are the trust mechanism
An annual statement to each contributing member showing what was recorded against them is the single practice that makes attributed giving comfortable rather than uncomfortable. It converts an opaque record into one the member can verify, and verification is what makes a record trustworthy.
It also catches errors, which is the underrated benefit. Mobile money transfers attributed to the wrong member, a standing order misread, a pledge recorded twice — members find these immediately and nobody else ever would. A church issuing statements has a giving record that gets corrected annually; a church that does not has one that drifts.
Where a statement may serve a tax purpose for the giver, that is a question for a qualified adviser and depends on the church's own status. We state nothing about it here beyond this: do not describe a statement as a tax document unless you have taken advice that it is one.
The counting controls still apply
Attributed giving arrives increasingly by mobile money and bank transfer, which is a genuine control improvement — the transaction exists independently of anybody's honesty. Cash offering still needs the physical disciplines: two unrelated counters, a count recorded before banking, and banking intact rather than net of expenses.
The one addition attribution introduces is a reconciliation: the sum of attributed contributions plus unattributed offering should equal what was banked. A persistent gap means either an attribution error or a counting problem, and it is worth finding while it is small. The counting side is covered in offering and tithe reconciliation.
What we do and do not do
What AWRA OpsHub does today
- Contributors as customer records with contact details and full transaction history.
- Receipts and statements produced per contributor, showing what was recorded against them.
- Contributions coded to a fund or category, so building fund, tithe and general offering are separable.
- Permission-gated access, so the giving record can be restricted to a named few — including keeping it away from pastoral staff.
- An audit trail on the underlying records, with actor, action and time.
- Reporting and scheduled delivery, so a treasurer receives the position without asking for it.
What it does not do
- No pledge object. A pledge and its fulfilment are tracked using custom fields and reporting, not as a modelled commitment with a schedule.
- No church management system. Membership, attendance, small groups and pastoral records are not part of this.
- No giving portal or online donation collection. Members give by whatever channel you already use; the record is created from those transactions.
- No tax-receipt formats. Nothing produces a statement in any prescribed form, and nothing here should be described to members as a tax document.
The first line is the practical one for building campaigns: a pledge register with fulfilment tracking is a custom-field-and-report arrangement rather than a feature, and it works, but somebody has to set it up deliberately.
Our take
Decide which giving is attributed and who may see it, say so from the front once a year, and issue annual statements so members can verify their own record. Plan capital projects on observed fulfilment rates rather than pledge totals. And keep the giving record away from the pastoral team — that single boundary does more for member confidence than any assurance you can offer.
See contributor records and statements
Contributor history, receipts and statements, contributions coded by fund, permission-gated access and an audit trail behind it.
Explore statementsFrequently asked questions
Should a church record who gave what?
That is a governance decision rather than a technical one, and most churches settle on a split: attributed for pledges, standing contributions and anything arriving by traceable transfer, unattributed for the loose offering. What matters far more than which side you land on is that the policy is decided, stated publicly and applied consistently. Members are rarely troubled that a record exists; they are troubled by learning about it accidentally.
Who should be able to see individual giving?
The narrowest list you can operate with — typically a treasurer and one other — and specifically not the pastoral team. Members are considerably more comfortable with a finance officer knowing what they gave than with the person who counsels them knowing, and separating the two is a permission setting rather than a promise. Say the boundary out loud from the front, because members will otherwise assume the worst arrangement.
How should we track building-fund pledges?
As promises with a fulfilment rate rather than as debts. There is no pledge object in the system, so the practical arrangement is custom fields carrying the pledge amount and schedule, with reporting comparing pledged against received. Plan the project on the observed fulfilment rate rather than the pledge total — the pledges are usually sincere and the timing is what stalls projects.
Why issue annual giving statements?
Two reasons, and the second is underrated. It makes attributed giving comfortable, because a member can verify the record rather than trusting it. And it corrects errors nobody else would ever find — a mobile money transfer attributed to the wrong member, a standing order misread, a duplicate entry. A church that issues statements has a giving record that is corrected annually; one that does not has a record that drifts quietly for years.
Can we issue tax receipts to givers?
Nothing here produces a statement in any prescribed tax format, and whether a contribution to your church carries any tax consequence for the giver depends on the church's status and on current law. Take advice from a qualified adviser before describing any document you issue as a tax receipt — a statement of what was recorded is straightforward and useful; a claim about its tax treatment is not something to make casually.
