Church accounting and fund stewardship: a practical guide

Church finances have a specific shape that most general-purpose accounting tools weren't built for. Donations are restricted or unrestricted. Funds have their own balances that must be preserved across fiscal years. Board reports look different from IRS filings, and both look different from what a member wants to see on a year-end statement.

This guide walks through the fundamentals of church fund accounting, why nonprofit standards (GAAP / ASC 958) matter, and how a built-in ledger inside your church operations platform is meaningfully different from bolting external accounting software onto a ChMS.

What "fund accounting" actually means

Fund accounting tracks money by purpose, not just by category. Every dollar received belongs to a fund — General, Missions, Building, Benevolence, a specific mission trip, a memorial — and that fund carries its own running balance.

A gift given "for the building fund" cannot be spent on operations, even if the operating account is short. Fund accounting is the discipline that keeps those boundaries visible and enforceable.

The three donor-restriction categories the FASB (ASC 958) recognizes:

• Without donor restrictions — general operating money the board can direct.
• With donor restrictions (purpose) — designated for a specific ministry, project, or program.
• With donor restrictions (time) — pledged for a future period, or held until a triggering event.

Every gift, every transfer, every expense in a well-run church ledger carries its fund and restriction class. Reports roll those up.

Why GAAP and ASC 958 matter for churches

Most US churches are 501(c)(3) organizations. Even where a full audit isn't required, external stakeholders — banks financing a building, denominations reviewing affiliates, grantmakers, insurance carriers — increasingly ask for GAAP-compliant statements.

The nonprofit-specific standard is ASC 958, which prescribes:

• The Statement of Financial Position (assets, liabilities, net assets — split by restriction).
• The Statement of Activities (revenue and expenses — again split by restriction, with releases from restriction shown explicitly).
• The Statement of Functional Expenses (expenses classified by both natural category and program vs. management vs. fundraising).
• The Statement of Cash Flows.

Producing these from a spreadsheet is possible; producing them accurately every month, tied out to your giving records, is where most churches lose weeks a year.

Chart of accounts for a church

A workable church chart of accounts usually looks like this:

• 1000–1999 Assets — checking, savings, restricted cash, receivables, fixed assets.
• 2000–2999 Liabilities — payroll liabilities, benevolence payables, loans.
• 3000–3999 Net assets — with vs. without donor restrictions, board-designated.
• 4000–4999 Revenue — tithes, offerings, designated giving, event revenue, rental income.
• 5000–5999 Program expenses — worship, discipleship, missions, care, youth, children.
• 6000–6999 Management & general — administration, insurance, utilities, IT.
• 7000–7999 Fundraising — where applicable.

Each account carries a natural classification. Each transaction also carries a fund and a restriction. That two-axis view is what makes GAAP reports possible.

The real problem: fragmented data

Most churches run this stack:

1. A ChMS (Planning Center, Breeze, Church Community Builder, etc.) that captures giving records.
2. QuickBooks or an equivalent that runs the general ledger.
3. A payroll provider (Gusto, ADP) for staff compensation.
4. A spreadsheet stitching them together for the finance team and board.

The ChMS knows who gave what and why. QuickBooks knows the bank balance and the P&L. Nothing knows both. When a donor asks whether their memorial gift was actually spent on the memorial garden, someone has to open three tools and hope the categories line up.

The consequences show up as:

• Reconciliation lag. Giving imports into QuickBooks weekly or monthly, and category mismatches accumulate.
• Restricted-fund drift. Purpose-restricted gifts get coded to the general fund because the mapping wasn't set up, and no one notices until year-end.
• Statement mismatches. A donor's year-end statement doesn't tie to what the ledger shows because the two systems diverged after a category rename.
• Audit trail gaps. Who approved the reclass? Who edited the gift after it was posted? The answer usually lives in someone's email.

Why a built-in ledger is different

A ledger built into the same platform as giving, people, and events removes the sync layer entirely. The gift record and the journal entry aren't two things that need to agree — they're the same event, viewed from two angles.

What that unlocks in practice:

• Every gift posts once. The donor's giving history, the fund balance, and the general ledger update in the same transaction. No import batches, no matching rules, no month-end surprises.
• Restricted funds enforce themselves. When a designated gift arrives, its fund tag rides with it through the ledger. Expense entries against the wrong fund are blocked or flagged at entry, not at audit.
• Statements always tie out. Because the giving records and the ledger are one dataset, a donor's year-end letter and the church's Statement of Activities cannot disagree.
• Board reports run on demand. A treasurer can produce a Statement of Financial Position or a fund-balance report from the same source as the giving report, filtered to the same period, with confidence they'll reconcile.
• Audit trail is native. Every posting carries who, when, and what changed — no third-party audit log to enable or configure.

This is the specific gap that shows up in almost every migration conversation with churches on Planning Center + QuickBooks: the two tools are individually fine, but the seam between them is where hours disappear and errors accumulate.

What good stewardship looks like day-to-day

The mechanics of accounting are only half of it. Stewardship is the practice around them:

• Publish a clear giving policy. How restricted gifts are honored, what happens if a fund is oversubscribed, how designations work.
• Reconcile weekly, not monthly. Weekly reconciliation catches errors while people still remember the context.
• Two-person deposit process. Counting teams of two, deposit slips signed by both, entries posted by a third party. It's a low bar that materially reduces risk.
• Board financial packet on a rhythm. Monthly Statement of Activities and fund-balance report, quarterly cash-flow, annual audited or reviewed statements depending on size.
• Year-end statements the first week of January. Members expect them, and delivering promptly is a signal of a well-run office.

Where to go from here in Forge

If you're setting up finance in Forge, the practical starting order is:

1. Configure funds (General, Missions, Building, plus any active designated funds).
2. Set the chart of accounts — start from the template and adjust names to match your board's language.
3. Wire the giving methods (online giving, in-service, mailed checks) so they post to the right fund automatically.
4. Turn on year-end statements and preview them with a small sample before the January send.
5. Establish the board packet as a scheduled report so it runs itself each month.

Fund accounting done right is invisible: gifts honor donor intent, restricted balances are always right, and the finance team spends its time on stewardship instead of stitching systems together.

Was this helpful, or missing something? Let us know.