In Nonprofit Cloud Fundraising, a Gift Commitment that is associated with an Opportunity carrying a Gift Default Soft Credit (GDSC) can end up with multiple, seemingly duplicate Gift Default Soft Credit records. The records appear after the scheduled Nonprofit Cloud automation runs, and additional records can be added on each subsequent run.
This happens because the automation compares the Gift Default Soft Credit on the Gift Commitment against the one on the related Opportunity and re-creates it whenever the two do not match. The automation checks all four of the following; if any one differs between the Commitment and the Opportunity, it creates a new GDSC record:
The most commonly observed trigger is a partial-payment (Partial Amount) difference between the Opportunity and the Commitment. Because the automation runs on a schedule, a persistent mismatch causes a new record to be created on every run, which is why the duplicates accumulate.
This is expected, by-design behavior, not a defect. The four-field comparison is what allows the automation to correctly create distinct soft credits when a Commitment legitimately needs one that differs from the Opportunity’s. The system cannot distinguish an intentional difference from an accidental mismatch — when the values differ, it creates a new record.
To stop new duplicate Gift Default Soft Credit records from being created:
Note on existing duplicates: Aligning the fields prevents new duplicates going forward; it does not merge or remove records already created. Review and remove any pre-existing duplicate GDSC records using your organization’s standard data-cleanup process.
005387796

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.