Loading
Salesforce Enforces New Security Requirements in Summer 2026Read More

Salesforce NPSP: Customizable Rollups not calculating and records not populating as expected

Publish Date: Jul 16, 2026
Description

This article explains why NPSP Customizable Rollups produce incomplete or missing totals on donor records and how you diagnose which jobs ran and whether they errored.

The symptom appears on Contact, Account, and Opportunity records and on custom summary fields such as [Gifts_Last_Year__c] and GAU allocation totals.

Triggers include: the NPSP rollup batch not being scheduled, a batch failing partway through, or specific donations missing a Contact or an Opportunity Contact Role so they are excluded from hard and soft credit rollups. 

This affects users with the NPSP Administrator or comparable permission set and applies to orgs on the NPSP managed package (release 262 and comparable).

No error banner appears on the record when a rollup is simply skipped; a debug/flow error such as "Unfortunately, there was a problem. Please try again. If the problem continues, get in touch with your administrator with the error ID shown here" may appear when a related automation fails.

Resolution

Work through the causes below in order and stop when the missing values populate.

Cause 1: The rollup batch job is not scheduled or has not run recently.
1. Go to Setup > Scheduled Jobs and confirm an NPSP rollup job is listed and shows a recent Next Scheduled Run.
2. If no rollup job exists, go to App Launcher > NPSP Settings > Bulk Data Processes > Customizable Rollups.
3. Set [Rollups Account Batch Size], [Rollups Contact Batch Size], and [Rollups Opportunity Batch Size] to 200.
4. Return to NPSP Settings > Schedule Jobs and click Schedule Jobs to register the default NPSP nightly jobs.

Cause 2: A rollup batch ran but failed or skipped records - you need to confirm which jobs ran and whether they errored.
1. Go to Setup > Apex Jobs to review recently run batch jobs. Match by the class name shown (for example the NPSP rollup batch class) and read the Status, Total Batches, Batches Processed, and Failures columns.
2. For flow-based automation failures, go to Setup > Process Automation > Automations, or open the flow under Setup > Flows, then use Debug to reproduce the error and read the fault path. If a screen shows "Unfortunately, there was a problem. Please try again. If the problem continues, get in touch with your administrator with the error ID shown here", copy the error ID and open Setup > Debug Logs to add a trace on the running user and re-run.
3. To monitor recently run jobs and errors for a consultant troubleshooting subledger or rollup records, use Setup > Apex Jobs (recent batch executions and failure counts) and Setup > Scheduled Jobs (next/last run). This is the correct place to see which jobs ran and whether there were errors.

Cause 3: Individual donations are excluded because they lack a Contact or Opportunity Contact Role.
1. Open one of the affected donations (Opportunity) that did not roll up.
2. On the Opportunity, confirm the [Primary_Contact__c] field is populated and that an Opportunity Contact Role exists with a role that counts for rollups.
3. For hard credit to roll up to both an Organization Account and a Contact, in NPSP Settings > Donations > Contact Roles set the Always Roll Up to Primary Contact Role checkbox to checked - this applies only to gifts from an Organization Account with the Primary Contact populated.
4. For soft credits, in NPSP Settings > Donations > Contact Roles confirm the roles you use are listed under the soft credit role settings so those Opportunity Contact Roles are counted.
5. After associating the missing Contact or Opportunity Contact Role, recalculate: open the affected Account or Contact record, and from NPSP Settings > Bulk Data Processes > Recalculate Rollups run the recalculation for the affected object.

Cause 4: GAU (General Accounting Unit) fund totals are incorrect.
1. Confirm each contributing donation has a GAU Allocation record. Go to the Opportunity and check the GAU Allocations related list.
2. Run NPSP Settings > Bulk Data Processes > Recalculate Rollups and select the GAU / Allocations recalculation to refresh Total Allocation and remaining balances.

Confirm the issue is resolved by opening a previously affected Contact, Account, or GAU record after the recalculation completes and verifying the rollup field (for example [Gifts_Last_Year__c], [npo02__OppAmountLastYear__c], or the GAU total) now shows the expected value without a manual per-record run.

Knowledge Article Number

005389143

 
Loading
Salesforce Help | Article