Loading

Salesforce NPSP: Rollups and Gift/Payment Records Not Updating After Donation Opportunities Close

Date de publication: Jul 16, 2026
Description

In Salesforce Nonprofit Success Pack (NPSP), administrators may occasionally find that donation rollups (such as "Gifts Last Year" or "Total Gifts"), auto-created payment records, or recurring donation installments fail to update. These issues typically affect only a subset of records and occur silently without displaying an error message in the user interface.

Common symptoms reported by users include:

  • "NPSP rollup values are incorrect for some contacts, while others are fine."

  • "Payment records are not being created automatically when I win a donation Opportunity."

  • "The Recurring Donation batch reports successes and failures but doesn't create future installments."

  • "The 'Gifts This Year' or 'Gifts Last Year' fields are not populating on persistent outlier accounts."

Résolution

Troubleshoot the following causes in sequence.

Cause 1: The Opportunity lacks an associated Primary Contact

Root Cause: NPSP's scheduled rollup engines use the Opportunity Contact Role (OCR) to calculate Contact-level and Account-level giving statistics. If an Opportunity is created without a primary OCR (often because of data imports via third-party tools like GiveSmart), NPSP ignores it during rollup runs.

How to Fix:

  1. Open the affected Opportunity record.

  2. Scroll to the Contact Roles related list.

  3. If the related list is empty, click New or Add Contact Roles.

  4. Select the target donor Contact, set the Role to Donor, check the Primary box, and click Save.

  5. To update statistics immediately, go to the App Launcher (waffle icon) > NPSP Settings > Bulk Data Processes > Rollup Donors (or Recalculate Donor Statistics) and trigger a manual recalculation for the affected records.

Cause 2: Payment records are not auto-creating

Root Cause: NPSP will not auto-generate a Payment record if the Opportunity's Amount is blank/zero, the Stage is not mapped to a "Closed/Won" status, or the Record Type is explicitly excluded in NPSP mapping settings.

How to Fix:

  1. Open the Opportunity and verify that the Amount field contains a value greater than zero ($0). If blank, enter the value and save.

  2. Confirm that the Opportunity is in a Closed Won (or equivalent won) stage.

  3. Go to App Launcher > NPSP Settings > Donations > Payments.

  4. Confirm that payments are enabled globally, and verify under Payment Mappings that the Opportunity’s Record Type has not been deliberately excluded from automatic payment creation.

Cause 3: Recurring Donation batch runs but fails to create future installments

Root Cause: A Recurring Donation record must have an Active status, a valid Next Payment Date, and correct installment settings to generate future records.

How to Fix:

  1. Navigate to the affected Recurring Donation record.

  2. Verify that its status is set to Active (or Open) and that the Next Payment Date is populated with a valid future date.

  3. Go to App Launcher > NPSP Settings > Recurring Donations and check the Number of Future Installments setting (typically set to 12).

  4. To run the batch manually and find failures, go to NPSP Settings > Bulk Data Processes > Process Recurring Donations and click Run Batch.

  5. Monitor progress via Setup > Apex Jobs (AsyncApexJob). Look for skipped or failed jobs, which point to records lacking linked Accounts/Contacts.

Cause 4: Scheduled nightly batch jobs are failing silently

Root Cause: NPSP batch operations run under the context of the user who originally scheduled them. If that administrator's license was deactivated, downgraded (e.g., changed to a "Salesforce Integration" or "Minimum Access - API Only" profile), or had their NPSP permission sets removed, the nightly scheduled jobs fail silently.

How to Fix:

  1. Navigate to Setup > Scheduled Jobs.

  2. Locate the NPSP Rollup and Recurring Donation jobs and check the Submitted By column.

  3. If the user shown is inactive or has a restricted license, Delete the scheduled jobs from this screen.

  4. Log in as an active System Administrator with a full Salesforce license and assigned NPSP permission sets.

  5. Navigate to App Launcher > NPSP Settings > Bulk Data Processes > Schedule Jobs and click Schedule Jobs to re-schedule all default NPSP nightly runs under the active admin's security context.

Cause 5: Rollup values are accurate as of the last nightly run, not real-time

Root Cause: Fields like Gifts Last Year (npo02__OppAmountLastYear__c) are calculated asynchronously. Between nightly batch runs, these fields can display stale data.

How to Fix:

  1. To force real-time calculations on demand, navigate to NPSP Settings > Bulk Data Processes > Rollup Donors and run the batch.

  2. If you are tracking donor status changes (like "Active" to "Lapsed") and require historical audits:

    • Go to Setup > Object Manager > Contact > Fields & Relationships.

    • Click Set History Tracking and check the boxes for critical rollup fields to log their changes in the Contact History related list.

Validation

Verify the configuration is restored by completing these steps:

  1. Create a test Opportunity record under an active Household Account.

  2. Ensure a Primary Contact Role is designated on the record.

  3. Set the Stage to Closed Won.

  4. Check that a Payment record is auto-generated in the related list.

  5. Navigate to NPSP Settings > Bulk Data Processes > Rollup Donors and click Recalculate.

  6. Open the associated Contact and Account records and verify that rollup summary fields reflect the updated donation.

Numéro d’article de la base de connaissances

005389139

 
Chargement
Salesforce Help | Article