# Contribution Reporting the Board Can Trust for an Environmental Nonprofit

> An environmental nonprofit could not report its financial, in-kind and volunteer contributions consistently, and its history was wrong. We rebuilt 14 reports and KPI dashboards, corrected the data model and reimported 553 historical contribution records, then scoped what comes next.

- Source: https://synconai.com/case-studies/nonprofit-contribution-reporting-the-board-can-trust
- Publisher: SynconAI (https://synconai.com)
- Type: Case study
- Evidence: Delivered client engagement. The client is anonymised; the industry, products and outcomes are theirs.
- Organisation: A community environmental nonprofit in Australia that coordinates volunteers, landholders and partners on land restoration and planting projects
- Industry: Nonprofit
- Products: Salesforce Platform, Reports and Dashboards, Data Loader, Flow, Person Accounts
- Service: Salesforce Administrator Services (https://synconai.com/salesforce-administrator-services)
- Reading time: 6 minutes

## In short

We gave an Australian environmental nonprofit contribution reporting it can stand behind. We corrected the Person Account model, fields and formulas, remapped and reimported 553 historical contribution records, and configured 14 reports and KPI dashboards covering financial, in-kind and volunteer contributions, reconciled in a sandbox before moving to production.

## Key points

- Fix the history before you build the dashboard. A KPI built on records mapped to the wrong place is precise and wrong at the same time.
- Count in-kind and volunteer contributions as seriously as money. For many nonprofits they are the larger share of what the community gives.
- Reconcile against an independent figure. Agreeing the totals with the organization’s own records is what makes the dashboards believable.
- Separate what was delivered from what was scoped. Next-phase ideas are valuable, and they belong in a plan, not in the current reports.

## Contribution reporting, before and after

Before the work, contributions were recorded inconsistently, some historical records were mapped to the wrong fields or people, and reports disagreed with each other, so the organization could not state its financial, in-kind and volunteer contributions with confidence. After the work, the data model and formulas were corrected, 553 historical contribution records were remapped and reimported, and 14 reports and KPI dashboards present the three kinds of contribution consistently, reconciled and checked in a sandbox before moving to production.

### 1. Before

- Inconsistent contribution records
- Historical mapping errors
- Reports that disagreed
- Manual reconciliation

Every report needed a caveat.

### 2. After

- Corrected data model and formulas
- 553 records reimported
- 14 reports and KPI dashboards
- Reconciled figures

One set of numbers for the board and funders.

## The starting position

Community environmental groups depend on three kinds of support. There is money, from grants, donations and partners. There is in-kind support, such as donated plants, materials, machinery and professional services. And there is volunteer time, often the largest contribution of all, from the people who turn up on weekends to plant, weed and monitor sites.

The organization in this engagement coordinates volunteers, landholders and partners on land restoration and planting projects. It already used Salesforce to record its contributions. The problem was that it could not report them consistently. Different reports produced different totals. Some historical contributions had been mapped to the wrong fields or linked to the wrong people when they were first entered or imported, so any report that included them was distorted. Formulas did not always calculate what people assumed they did.

For a nonprofit, that is more than an inconvenience. Funders want evidence of community contribution. Grant applications often ask for it. The board needs to know whether programs are growing. When every figure comes with a caveat, the organization spends time defending its numbers instead of using them.

The brief was to make contribution reporting reliable: correct the data, fix the model underneath it and give leaders a set of reports and dashboards they could trust.

## What we built and fixed

### 01 The data model, corrected

We reviewed how contributions were recorded and fixed the underlying structure: the Person Account setup that represents individual supporters, the fields that hold each type of contribution and the formulas that calculate values from them. The aim was simple: every contribution recorded once, in the right place, and counted the same way by every report.

### 02 553 historical records, remapped and reimported

Historical contributions that had been mapped incorrectly were identified, remapped to the corrected model and reimported with Data Loader, 553 records in total. Doing this as one controlled pass, instead of editing records one at a time, meant the fix was complete and checkable.

### 03 14 reports and KPI dashboards

We configured and refined 14 reports and KPI dashboards covering financial, in-kind and volunteer contribution activity. Leaders can see each kind of contribution separately and in total, over time and by the dimensions the organization reports on.

### 04 Reconciliation

The corrected figures were reconciled against the organization's own records, so the totals in Salesforce could be explained and defended.

### 05 Sandbox first, then production

Corrections to fields, formulas and reports were made and checked in a sandbox before being moved to production, so the live system was never in a half-fixed state.

### 06 Discovery for the next phase

Alongside the delivered work, we ran discovery on what the organization wants next: unified data entry, records for species and planting, volunteer and event management, and integrations with third-party tools. That work is scoped as a further phase and is not part of what has been delivered.

## Why history matters more than dashboards

It is tempting, when reports disagree, to build a new dashboard and hope it settles the argument. It never does. A dashboard can only summarize the records underneath it, and if those records are mapped to the wrong fields, the dashboard reports the error with great precision.

That is why most of the effort in this engagement went into the data before the dashboards. Correcting the model and the historical records was slower and less visible than designing charts, and it was the part that made the charts worth looking at. Once 553 records were in the right place and the formulas calculated what everyone assumed, the 14 reports agreed with each other and with the organization's own figures.

There is a second reason. Nonprofits keep supporters for a long time, and reporting often looks back over years. A mistake in historical data does not age out. It keeps distorting multi-year comparisons until someone fixes it at the source.

## Counting all three kinds of contribution

Many organizations report money carefully and estimate everything else. For a community environmental group, that undersells the community. Donated materials and services, and thousands of volunteer hours, are a large part of what makes the work possible, and funders increasingly want to see them.

The dashboards were therefore designed to treat financial, in-kind and volunteer contributions as equals: recorded consistently, valued by the organization's agreed rules and reported side by side. That gives the board and funders a fuller and more accurate picture of what the community gives.

## What reliable reporting changes for a small team

Nonprofits rarely have a dedicated data team. The people who produce the reports are usually the same people who coordinate volunteers, manage partners and write grant applications. Every hour spent reconciling figures by hand is an hour not spent on the work the organization exists to do.

Reliable reporting changes that in practical ways. A coordinator preparing a grant application can pull the contribution figures for a program straight from a report, instead of building them in a spreadsheet and hoping they match last year's submission. The treasurer can present financial contributions to the board knowing they agree with the organization's records. Program leads can see whether volunteer participation is growing or falling at each site, early enough to do something about it.

It also changes conversations with funders and partners. When an organization can show, consistently and over several years, what its community has contributed in money, materials and time, it is making a stronger case for support. The numbers stop being a source of anxiety and become evidence of impact.

Finally, it makes the next phase possible. The workflows the organization wants next, from unified data entry to species and planting records, all depend on a trustworthy model underneath. Building them on corrected data means they can be added without reopening the problems this phase solved.

## How we delivered it, end to end

**Diagnose before changing anything.** We traced how each type of contribution was recorded and where reports diverged, so every fix had a reason.

**Correct the model.** Person Accounts, fields and formulas were fixed first, because both the historical reimport and the reports depend on them.

**Fix the history in one pass.** The 553 affected records were remapped and reimported together, then checked.

**Build and reconcile the reports.** The 14 reports and dashboards were configured on the corrected data and reconciled against the organization's records.

**Promote safely.** Each change was checked in a sandbox and then moved to production.

**Plan the next phase separately.** Discovery for new workflows and integrations was recorded as a scoped plan, kept apart from the delivered work.

## The decisions that mattered

**Data before design.** Fixing records first meant the dashboards were right the first time.

**One controlled reimport.** Remapping and reimporting the 553 records in one pass made the correction complete and auditable.

**Equal weight for in-kind and volunteer support.** Reporting all three kinds of contribution shows the true scale of community effort.

## What changed

| Area | Before | After |
| --- | --- | --- |
| Contribution totals | Reports disagreed | One reconciled set of figures |
| Historical records | Mapping errors distorted reports | 553 records remapped and reimported |
| Data model | Fields and formulas inconsistent | Person Accounts, fields and formulas corrected |
| Reporting | Caveats on every figure | 14 reports and KPI dashboards |
| Contribution types | Money reported, the rest estimated | Financial, in-kind and volunteer reported side by side |
| Next steps | Ideas in conversation | Scoped next phase for workflows and integrations |

## What we would tell a nonprofit starting this

If your reports disagree, the problem is almost always in the records, not the reports. Find the records that were mapped wrongly, fix the model so it cannot happen again, and correct the history in one controlled pass. Then build the dashboards, and give volunteer and in-kind contributions the same care as money. Your funders and your board will notice the difference.

## Questions

### Why did historical records need to be reimported?

Some past contributions had been mapped to the wrong fields or linked incorrectly, so any report that included them was distorted. Correcting them in place, record by record, would have been slow and error-prone. Remapping the 553 affected records and reimporting them with Data Loader fixed the history in one controlled pass.

### What do the dashboards show?

Fourteen reports and KPI dashboards cover the three kinds of contribution the organization relies on: financial contributions, in-kind support such as donated materials and services, and volunteer time. Leaders and the board can see each one and the total from the same corrected data.

### What happens next?

We have run further discovery on unified data entry, species and planting records, volunteer and event management, and third-party integrations. Those are scoped as a next phase. They are not part of what has been delivered so far.

---

SynconAI. https://synconai.com/case-studies/nonprofit-contribution-reporting-the-board-can-trust