Legit Nonprofit-Cloud-Consultant Exam Download

In Nonprofit Cloud for Fundraising, correctly attributing "Hard Credit" and "Soft Credit" is essential for accurate financial reporting and donor stewardship.

In a peer-to-peer (P2P) scenario, the person who actually gave the money is the Donor. They receive the legal "Hard Credit" for tax purposes. The Team Organizer (the solicitor) is the influencer who motivated the gift. They receive the "Soft Credit" for recognition purposes.

Step-by-Step Entry Process:

Create the Gift Transaction: The consultant (or the automated P2P integration) creates a Gift Transaction record. The Donor field is populated with the Person Account of the individual who made the payment. This is the Hard Credit.

Assign the Soft Credit: To recognize the team organizer, a Gift Soft Credit record is created and linked to that specific Gift Transaction.

The Soft Credit Recipient is the Team Organizer's Person Account.

The Role is set to "Solicitor" or "P2P Organizer."

Automation: When these gifts are entered in bulk, the consultant can use a Gift Batch where a default "Soft Credit" can be applied to all transactions in the batch if they all belong to the same organizer.

Acknowledgement: By having both names linked to the transaction—one as the primary donor and one as a soft credit recipient—the organization can run two separate acknowledgment runs. One generates a "Tax Receipt" for the donor, and the other generates a "Thank You/Influence Alert" for the organizer.

Why other options are incorrect:

Option A: "Donor Cover Amount" is used for tracking when a donor pays for the credit card processing fees, not for attribution to a third party.

Option B: Gift Tribute is for "In Memory Of" or "In Honor Of" designations, which are purely sentimental and do not represent the solicitation influence of a peer-to-peer organizer. Gift Soft Credit is the standard NPC object for this business requirement.

The Case Plan Wizard in Nonprofit Cloud Case Management is a tool that allows caseworkers to quickly build a customized care plan for a participant. To make this "wizard" efficient and automated, the underlying "templates" must be set up beforehand.

Required Pre-configuration:

To "assign a group of services" effectively through the wizard, the consultant must ensure that the Program record is populated with:

Goals: These are the objectives the client wants to reach. In the wizard, the caseworker can select from these pre-defined goals rather than typing them from scratch.

Action Item Templates: These are the specific tasks or "steps" required to reach a goal. By creating Action Item Templates and linking them to a Goal within a Program, the consultant enables the "grouping" logic. When a caseworker selects a Goal in the wizard, the associated Action Items automatically appear as suggested tasks.

Workflow for the Consultant:

Navigate to the Program record.

Use the Goals related list to create standard goals for that program.

Use the Action Item Templates related list to define the repeatable steps for those goals.

Ensure the Case Plan Wizard component is added to the Contact or Case record page.

Why other options are insufficient:

Option A and B: If you only have Goals or only have Action Items, the wizard loses its primary value of providing a "ready-made" plan for the caseworker.

Option D: A "New Case Plan" is the result of using the wizard, not a prerequisite for the wizard's configuration.