Keep organization donors and their contacts separate

A company, foundation, or community group is not the person who answers your email. Give the organization its own record, keep each person as an individual contact, link them by role, and attach every gift to the payer shown by the transaction evidence. The contact can change later without rewriting who gave.

That is the central rule for nonprofit CRM organization records: payment ownership and relationship ownership are different facts.

Keep four records with four jobs

Use four connected records rather than one overloaded contact:

1. Organization: the company, foundation, government office, school, or other group your nonprofit works with.
2. Person: an individual with their own name, email, communication choices, and history.
3. Affiliation or role: the connection between that person and the organization, such as employee, program officer, board liaison, or primary contact.
4. Gift: the received transaction, attached to the person or organization that actually paid.

Current nonprofit CRM documentation reflects this separation. Salesforce NPSP distinguishes individual contacts, organization accounts, affiliations, and gifts. Keela likewise defines an organization record separately from a contact record and allows multiple people to be linked to one organization.

The field names will differ in your CRM. The test does not: can your team change a contact without moving the organization's old gifts?

Put the gift on the payer

Start with the transaction evidence, not the name your fundraiser recognizes first.

If Northside Builders sends a $2,500 company check, the organization owns that gift record. Maya, the controller who signed the check and answers questions, remains a linked person. She may receive the acknowledgment or the next stewardship task, but she did not become the payer merely because staff know her name.

If Maya later makes a $150 personal gift with her own card, that gift belongs to Maya. Her employer affiliation remains useful context, but it does not turn the personal payment into direct company giving.

This boundary matters because CRM rollups are not universal. CharityEngine documents direct organization gifts separately from gifts made by affiliated employees and warns that an extra soft credit can inflate its organization total. Test one organization gift and one employee gift in your own reports before automating any rule.

When another person deserves recognition for the same payment, use your documented soft-credit policy. Recognition may add a relationship. It should not create another received gift.

Let contacts change without moving history

A primary contact is a current routing choice, not the identity of the organization.

Give each affiliation a role and, when your system permits it, a start date, end date, and source. When Maya leaves Northside Builders, close or update her affiliation. Add the new controller as a linked person and change the primary-contact field. Keep the $2,500 gift on Northside Builders.

Do not rename Maya's record to the new employee. Do not replace her email with the new contact's address. Both actions destroy person-level history to save a few clicks.

The same principle applies when a person works with several organizations. One contact can hold several dated affiliations without becoming several duplicate people. If two records may represent the same individual, use the three checks for duplicate donor records before merging anything.

Separate direct giving from relationship context

Build reports that answer one question at a time. A useful organization view can show:

• direct gifts paid by the organization;
• people currently affiliated with it;
• individual gifts from those people, labeled as affiliated rather than direct; and
• recognition or influence relationships, when your policy permits them.

Do not add those amounts together unless the report explicitly defines what the combined total means. "Direct organization giving" and "giving connected to people at this organization" answer different fundraising questions.

This is where operator judgment often splits. In a current nonprofit discussion about employee-directed giving, practitioners disagreed about company versus individual ownership and stewardship. The disagreement is useful evidence of the decision, not a rule to copy. Resolve your case from the payer evidence, the program's documentation, and your nonprofit's approved reporting policy.

Run one turnover test before closing the setup

Use a real organization with at least two people and one gift. Then ask:

1. Can you identify the payer without opening the contact's notes?
2. Can you replace the primary contact without changing the gift owner?
3. Can you report direct organization gifts without silently adding employee gifts?
4. Can staff see who should receive the next message today?

If any answer is no, fix the relationship before adding more fields. A lean system does not need a complicated hierarchy. It needs stable identity, visible roles, and one defensible owner for each payment.

Start fundraising free →