The fundraising data model in the new Nonprofit Cloud (NPC) differs significantly from the older NPSP "Recurring Donations" object. NPC utilizes the Fundraising feature set, which is built on a high-performance architecture shared with other Industry Clouds.
To manage recurring giving, two primary objects are required:
Gift Commitment: This object represents the donor's "promise" or agreement to give a certain amount over time. It stores high-level information such as the total amount of the commitment, the donor (Person Account), and the status (e.g., Active, Paused, or Fulfilled).
Gift Commitment Schedule: This is the engine that drives the frequency of the gift. It defines when and how often the donation should be processed (e.g., Monthly on the 15th, or Weekly on Mondays). A single Gift Commitment can actually have multiple schedules if a donor has a complex giving plan.
The Workflow for a Consultant:
Create the Gift Commitment: When a donor signs up for a monthly giving program, the consultant (or the automated system) creates a Gift Commitment record.
Define the Schedule: A Gift Commitment Schedule record is then linked to that commitment, specifying the recurring transaction amount and the transaction period.
Automated Processing: Once these are active, the Nonprofit Cloud's Gift Processing engine uses the schedule to automatically generate Gift Transaction records (which are the equivalent of "received" donations) on the specified dates.
Option A is incorrect because "Opportunity" is part of the legacy NPSP model or standard Sales Cloud; while NPC can use Opportunities, the specific recurring logic in NPC is handled by Gift Commitments. Option C is incorrect because Gift Designation is used to track the fund or purpose the money is for (e.g., "Scholarship Fund"), which is applicable to both one-time and recurring gifts, but is not the object that establishes the recurring nature of the gift.
