Skip to content

Giving

Connecting giving to the rest of your church records

Most small and midsize churches end up running two parallel databases without ever deciding to: a people database for membership, households, groups, and attendance, and a giving database that lives inside whatever platform processes payments. Both are usually accurate on their own. The trouble starts when leadership asks a question that crosses them. Keeping giving on the same person and household record the rest of the platform uses is what removes the second database and the reconciliation work that comes with it.

By Congregation Portal · Published · Reviewed · Updated · ~7 min read

The accidental second database

Parallel donor database
A separate record of donors and gifts that lives in the church's payment platform, independent of the people database the rest of the administration uses.

Almost no church chooses a parallel donor database on purpose. It accumulates. The payment platform onboards donors directly. The people database tracks members. Names are entered slightly differently. Six months in, the church has two accurate but inconsistent records of the same congregation. Every cross-database question becomes a reconciliation project.

What changes when giving lives next to people

When giving is part of the same record as membership, household, and group participation, four things become possible without exporting anything.

  • Donor history attaches to the person, so any leader with appropriate access sees it in context.
  • Fund designations are reported against the same fund definitions the church already uses.
  • Recurring gifts are visible alongside other person-level commitments, not buried in a separate tool.
  • Reports that cross giving and participation answer in seconds, not days.

An example: a stewardship report that no longer takes a week

A 400-attender church we spoke with prepared a quarterly stewardship update for elders that required four hours of spreadsheet matching every quarter. Exports from the giving platform, exports from the people database, manual fuzzy matching by name and email, and a final round of corrections. Once giving moved onto the same record as the rest of the people data, the same report became a five-minute pull from a single source. Nothing about the underlying generosity changed. The week of reconciliation work disappeared because the parallel database disappeared.

What integrated giving does and does not mean

Integrated giving means the records are connected. It does not mean any leader can browse any donor's history. Role-appropriate access still applies, often more strictly than in a separate platform, because the connected system can express finer-grained permissions.

Parallel donor database vs integrated giving
Parallel donor databaseIntegrated giving
Two sources of truthOne source of truth
Manual reconciliation each quarterReports pull from one record
Donor and member records drift apartRecords stay in sync by default
Access is platform-levelAccess is role-appropriate
Migration off is painfulExport remains straightforward

How to consolidate without disruption

Consolidating giving onto the same record as the people database is mostly a sequencing problem. Done in the right order, no donor sees anything change in their experience.

  1. Confirm that the people database has accurate household structure and contact information first.
  2. Map donor records from the payment platform to person records by household, not just by name.
  3. Move recurring gifts before one-time history so future revenue is recorded correctly on day one.
  4. Import historical gifts in date order, attached to the person record.
  5. Communicate the change to donors only after verifying the first weekend of integrated reporting.

How Congregation Portal thinks about giving information

Giving information is among the most sensitive data a church holds. Congregation Portal approaches it with thoughtful permissions, careful handling, and honest communication. Role-appropriate access so the right team members see the right records. Administrative views for reporting and reconciliation. No claims about certifications or capabilities the product has not delivered. As specific capabilities are confirmed, the Giving page describes them in plain language.

The leadership benefit is fewer parallel systems

The goal is not more dashboards. It is fewer parallel systems. When giving sits on the same record as the rest of the administration, reconciliation becomes ordinary instead of quarterly, and the questions a leadership team most often asks about stewardship can be answered with the same trustworthy records the staff already maintains. That is the practical case for integrated giving, with or without Congregation Portal.

References

  1. ECFA and Lake Institute on Faith and Giving, donor-record guidance