Donation
A Donation in Salesforce represents a single contribution from a donor to a nonprofit organization.
Definition
A Donation in Salesforce represents a single contribution from a donor to a nonprofit organization. In the Nonprofit Success Pack (NPSP), Donations are stored on the standard Opportunity object with Type = Donation and configurable Stage values (Prospecting, Pledged, Posted, Paid, Closed Won) reflecting the donation lifecycle. In the modern Nonprofit Cloud, Donations live on the dedicated Gift Transaction object, separating them cleanly from the sales-pipeline Opportunity model.
Each Donation captures the donor (linked through Account, Contact, or Account-Soft-Credit), the Amount, the Close Date (gift date), payment method, designation (which fund or program receives the gift), associated Campaign, and any matching gift, in-kind valuation, or attribution details. Donations are the operational unit of nonprofit fundraising. Every dollar received maps to a Donation record, providing the queryable financial backbone for revenue reporting, donor stewardship, IRS Form 990 compliance, and grant-funder accountability.
How Donations work across NPSP and Nonprofit Cloud
The NPSP model: Donations as Opportunities
NPSP, the long-standing nonprofit toolkit on Salesforce, models Donations on the standard Opportunity object. Each donation is an Opportunity with Type = Donation, RecordType set to Donation (or Major Gift, Grant, Matching Gift), and a custom set of Stages that fit nonprofit pipelines (Prospecting, Pledged, Posted, Paid, Closed Won). This reuse means donations inherit the Opportunity engine: forecasting, sharing, related lists, and all the Sales Cloud tooling work on donations out of the box. The trade-off is conceptual: opportunity is a sales word, not a fundraising word, which trips up new admins.
Nonprofit Cloud and the Gift Transaction object
Nonprofit Cloud (the rebuilt platform launched in 2023, succeeding NPSP for new implementations) introduces dedicated objects. The Gift Transaction object replaces Opportunity for donations. The model is cleaner: Gift Transactions, Gift Commitments (multi-payment pledges), Gift Designations (which fund receives the dollars), and Gift Allocations (splits across funds). Existing NPSP orgs continue to work; new orgs default to Nonprofit Cloud and the Gift Transaction model.
Hard credit, soft credit, and household credit
Fundraising attribution is more complex than sales attribution. A single donation can have one hard credit (who paid) and multiple soft credits (who influenced or facilitated the gift). Hard credit is the legal donor for tax purposes. Soft credit includes the household, the influencer, the matching gift donor, and any team campaign captains. Both NPSP and Nonprofit Cloud track these relationships through dedicated junction objects: Opportunity Contact Roles in NPSP, Gift Contributor Roles in Nonprofit Cloud.
Recurring donations and pledges
A recurring donation (a $25 monthly gift) produces one parent record and a child record per payment. In NPSP, the parent is a Recurring Donation custom object; the children are Opportunities (Donations). In Nonprofit Cloud, the parent is a Gift Commitment; the children are Gift Transactions. The split lets you track lifetime giving from one donor across many payments while keeping each receipted gift as its own record.
In-kind donations and non-cash valuation
In-kind donations (donated goods, services, time) need a stated fair market value but no cash flows. The Donation record captures the in-kind value but flags the payment method as In-Kind. Reports separate cash from in-kind for accurate financial reporting; IRS Form 990 has different lines for each. Volunteer hours are typically not recorded as in-kind donations on the Donation record (the IRS does not allow valuation of volunteer time), but related Volunteer Hour records track them separately.
Matching gifts and corporate philanthropy
A matching gift is a donation from an employer to match an employee''s personal gift. In NPSP, the matching gift is its own Opportunity linked to the original through a custom lookup. In Nonprofit Cloud, Gift Transactions support a Matching Gift Transaction type that references the original Gift Transaction. Both models surface the matching gift on the donor''s giving history while keeping the company as the legal donor for the matched amount.
Reporting and the financial backbone
Donations report at three levels: the individual donor (lifetime giving, last gift, retention status), the campaign (revenue per campaign, ROI per dollar spent on fundraising), and the program (revenue per fund). Nonprofit dashboards typically lead with three or four of these reports: this month''s gifts vs forecast, donor retention rate, top donors, and revenue by program. Both NPSP and Nonprofit Cloud ship with starter reports; mature deployments customize heavily.
How to record a Donation in Salesforce
Recording a Donation in Salesforce depends on whether your org runs NPSP (Donations as Opportunities) or Nonprofit Cloud (Donations as Gift Transactions). The fields are similar; the navigation path differs.
- Identify the donor record
In Salesforce, search for the donor by name or email. If the donor exists, open their Contact (NPSP individual donor model) or Account (organizational donor or NPSP Account model). If new, create the contact first; donations link to donors, not the other way around.
- Create the Donation
On the donor''s record, find the related Donations list (Opportunities in NPSP; Gift Transactions in Nonprofit Cloud) and click New. Pick the appropriate record type (Donation, Major Gift, Grant, Pledge, Matching Gift) at the prompt.
- Fill the core fields
Amount, Close Date (the gift date), Stage (typically Posted or Paid), Type (Donation, In-Kind, Matching Gift), Payment Method (Check, Credit Card, ACH), and Campaign (the campaign that drove the gift).
- Set Designation and Allocation
If the donor restricted the gift to a specific fund or program, link to the GAU (General Accounting Unit in NPSP) or Gift Designation (in Nonprofit Cloud). Multi-fund splits go in the Allocations related list.
- Save the Donation
Salesforce validates required fields and saves. NPSP runs trigger logic to update Account totals; Nonprofit Cloud''s Gift Transaction triggers update the Gift Commitment and donor summary fields.
- Send an acknowledgement
Trigger the donor acknowledgement letter or email through your acknowledgement workflow. NPSP includes acknowledgement templates; Nonprofit Cloud uses Marketing Cloud Engagement or Email Studio for sends. The receipt should reach the donor within 24-48 hours for IRS compliance and stewardship.
The dollar value of the donation. Required for IRS-compliant receipting.
The gift date. Drives fiscal-year and campaign reporting.
The donation lifecycle stage. Posted and Paid are typical end states for recognized revenue.
The legal donor. Required for tax receipting and donor history.
- Stage names matter. NPSP-built reports filter on stage Posted or Paid; changing stage labels without updating reports breaks the dashboards.
- Soft credit junctions are not auto-created. Always check the Contact Roles or Gift Contributor Roles after entering a donation to confirm everyone who deserves credit gets it.
- Recurring donation child records create on a schedule, not immediately. Spinning up a 25-per-month commitment does not produce the first donation until the schedule runs.
- Salesforce does not generate IRS-compliant receipts automatically. Configure acknowledgement workflows to include the required IRS language (your organization is a 501(c)(3), the gift is tax-deductible to the extent permitted by law).
Trust & references
Straight from the source - Salesforce's reference material on Donation.
- Gift Transactions in Nonprofit CloudSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Discussion
Loading discussion…