Planning Center reporting

Planning Center giving reports: what you can get, and what you have to build

Planning Center Giving is a strong system of record. It is less strong as an analysis tool — which is why so many church staff end up exporting to a spreadsheet every month. Here is an honest map of where the built-in reports land, and what it takes to answer the questions a board or budget committee actually asks.

What Planning Center Giving reports do well

  • Totals and counts for a date range you pick, filtered by fund.
  • Per-donor statements and contribution history for year-end receipts.
  • Batch and deposit reconciliation against your bank and processor.
  • CSV exports of donations, funds and people for downstream work.

If your question is "what came in, to which fund, in this window, and does it reconcile," the built-in reports are the right tool and you should keep using them.

Where church staff usually hit a wall

Year over year, same chart

Comparing this year to last by week, month or quarter means running two reports and lining them up in a spreadsheet — every time you want to look.

Giving by campus or membership

Donations live in Giving; campus and membership live in People. Answering 'how is our second campus giving' requires joining the two data sets.

Fund concentration risk

Knowing what share of a fund comes from its top handful of households is a concentration question, not a totals question — and it changes how you budget.

Forecasting a budget year

Budget planning needs a projected range with seasonality, not last year's total divided by twelve.

The five questions worth reporting on every month

  1. Trend versus prior year. Same fund, same period length, plotted together — so a soft month is visible as a trend rather than a feeling.
  2. Active giver count. Households that gave in the last 90 days. Total dollars can hold steady while the number of participating households quietly falls.
  3. Fund concentration. The share of a fund carried by its largest givers, so you know how exposed a ministry budget is.
  4. Lifecycle movement. New, growing, steady, lapsing — movement between those groups is your earliest warning signal.
  5. Forecast with a range. A low, expected and high case for the coming quarter or fiscal year.

A note on donor privacy

Giving data is pastorally sensitive. Reporting for a leadership meeting almost never needs names — it needs shape: trends, shares, cohorts and counts. Keep individual donor detail inside Planning Center where your existing permissions already govern it, and keep the analysis layer aggregate-only. Disciplytics is built that way on purpose: it never shows individual donor names or donor-level lists anywhere.

Doing this without the monthly spreadsheet

Disciplytics connects to Planning Center through the official OAuth flow — read-only, revocable, no passwords shared — syncs your giving, people and check-in history, and keeps it current nightly. From there you get year-over-year trend charts by day, week, month or quarter, breakdowns by fund, campus and membership, fund health and concentration, donor lifecycle cohorts, and budget forecasts with uncertainty ranges. It reads your Planning Center data; it never writes to it.

Common questions

Does Planning Center Giving have year-over-year reports?

You can compare two periods by running reports separately and exporting them, but there is no built-in chart that plots this year against last year by week, month or quarter for the same fund.

Can I break giving down by campus or membership status?

Not directly — donations live in Giving and those attributes live on the People record. It takes joining both data sets, either by hand or with a tool that reads both.

How do I forecast next year's giving?

Planning Center does not forecast. A usable forecast needs full donation history with seasonality plus an uncertainty range, so a committee can plan against a realistic low and high case.

Is it safe to connect a reporting tool to Planning Center?

Connect only through Planning Center's official OAuth flow, and look for read-only scopes, encrypted tokens, and reporting that shows aggregates instead of individual donor lists.