Fund, campaign, or appeal? One gift may need all three

A fund, campaign, and appeal answer different questions about the same gift. Use the fund for intended use, the campaign for the broader fundraising objective, and the appeal for the specific ask that prompted the response. When your source evidence does not answer one of those questions, leave that field blank or use an approved default instead of guessing.

The labels vary by fundraising system. The three questions are more durable than the labels.

Give each field one job

Start with the gift record. Its donor, amount, date, payment state, and source evidence should not change merely because your team wants a different report.

Then classify the gift with three separate questions:

1. Fund or designation: Where is the gift intended to go? This may be an unrestricted default, a program, or another approved purpose. Microsoft's nonprofit fundraising documentation uses “designation” for how raised funds should be spent, while Salesforce describes gift designations as funds set aside for a specific purpose. Those are product definitions, not a substitute for your organization's legal or accounting review.
2. Campaign: What fundraising objective does this gift support? Think annual giving, a capital effort, or a time-bound emergency push. A campaign groups progress toward the objective even when gifts arrive through several asks or channels.
3. Appeal: Which specific solicitation prompted the gift? Think Spring Letter 2026, an email on August 12, or a board-member call list. The appeal identifies the ask your team can evaluate and follow up on.

Beacon's current guide makes the core distinction concrete: campaigns track where fundraising activity came from, while funds track what money will be spent on. Fundraise Up's documentation also shows that a campaign and a designation can coexist on one donation. Your database may name the objects differently, but it should preserve both answers.

Test the model on one gift

Suppose Maya gives $120 through a spring email for a food-pantry initiative. The form was configured with an approved pantry designation.

One useful gift record could carry:

• Fund or designation: `Food Pantry`
• Campaign: `2026 Annual Giving`
• Appeal: `Spring Email — May 14`
• Source key: `spring-email-may14-button`

Those values are not four names for the same thing. The fund supports the intended-use handoff. The campaign rolls the gift into the broader fundraising objective. The appeal identifies the solicitation. The source key preserves the exact placement or link that led to the form.

This separation also prevents a common reporting trap. If your team renames the spring email, the gift should not move to a different fund. If finance changes an internal code, the historical appeal should not disappear. Correct the affected field and preserve the original source evidence or change note.

Know when a field should stay blank

Completeness is not the goal. Accurate evidence is.

Use an approved unrestricted or general designation when your policy calls for one. Do not infer a restricted purpose merely because a donor arrived through a program page, event, tribute form, or campaign message. A fundraising context can explain why you asked without deciding how the gift must be treated.

Leave the appeal blank when no specific solicitation is known. A walk-in gift or an untracked check may still belong to a campaign, but adding the last email your team remembers would create false attribution.

Leave the campaign blank when the gift is genuinely outside an active fundraising objective. Do not create a permanent “miscellaneous campaign” that collects unrelated records and makes the report look complete.

If the source evidence and the selected fund disagree, move the gift into the exception lane in your gift-processing intake workflow. Preserve the donor's instruction, form configuration, check memo, or correspondence. Let the person authorized by your nonprofit decide the operational correction.

Assign owners before you clean old records

Salesforce recommends aligning leadership, programs, and finance before configuring designations. A lean team can turn that broad advice into three ownership rules:

• An authorized finance or operations owner maintains the approved fund or designation list and default.
• Fundraising owns campaign and appeal naming, dates, and retirement rules.
• Gift operations records the source evidence, stable IDs, and any correction note on the gift.

One person may perform all three jobs. The rules should still be distinct so a rushed cleanup does not turn a fundraising label into a finance decision.

Do not start by renaming every historical value. First map the current values to the question each one actually answers. Hold ambiguous records. Merge labels only when they have the same meaning, owner, and reporting use. The custom-field action test is useful here: if a field never changes a named decision or follow-up, it may not deserve to be collected.

Make each report prove the field works

Run three small reports before you trust the configuration:

• Fund report: Can the authorized owner review gifts by intended use without relying on campaign names?
• Campaign report: Can fundraising see progress toward one objective across multiple appeals and channels?
• Appeal report: Can the team compare specific asks without losing the gift's fund or campaign?

Open one gift from each report. The same gift should still show the same donor, payment, receipt, source evidence, and correction history. Only the grouping question changes.

That is the practical test for a nonprofit fund vs campaign vs appeal setup: one gift, three possible classifications, and no field forced to explain another field's job.