Handle the congregation's giving with the transparency it deserves

No, and we say so plainly. AWRA is the financial and operations backbone — offerings, funds, procurement, assets, payroll, and reporting. It does not manage membership rolls, attendance, or pastoral records; dedicated church-management tools do that. Most churches run a membership tool for people and AWRA for money and operations, and the two coexist.

By building dual control into the counting and reconciliation: collections are recorded by service and counted by more than one person, then reconciled to what was banked, with every step attributed. That protects the funds from loss and — just as importantly — protects honest counters and treasurers, because the record clears them rather than leaving them exposed to suspicion.

Received and spent, yes — and it is worth knowing exactly how, because two words in that question are not product features. A building fund is modelled as a project: receipts are coded to it as they come in, every disbursement is attributed to it with a document attached, and the report shows what came in, what went out and what remains. That is the number you present at a meeting and it is solid. What does not exist is a fund entity — nothing structurally prevents a receipt being coded to the wrong project, so the discipline is yours and the system records it faithfully rather than enforcing it. And there is no pledge record: a pledge is not an object here, so pledged-versus-received is only available if you raise each pledge as an invoice against the member, which works and is more administration than most congregations want. If the pledge side is the reason you are buying, weigh that before you do.

Yes — smaller churches benefit most, because they rarely have a finance office and rely on volunteers whom good controls protect. Start with offering recording and reconciliation, which delivers trust and protection immediately, and add fund tracking, procurement, and assets as capacity allows.