Who owns a donor-advised fund gift record?

Record a donor-advised fund gift as one received gift with three distinct roles: the sponsoring organization sends the payment, the advisor recommends the grant when identified, and your nonprofit receives it. Keep those roles connected, but never create a second gift to make the advisor visible in fundraising reports.

That rule gives finance the real payment source and gives fundraising the right relationship without adding the same money twice.

Separate control, recommendation, and receipt

A donor-advised fund, or DAF, is maintained by a sponsoring charitable organization. The IRS describes that organization as having legal control of the account after a donor contributes, while the donor or representative keeps advisory privileges over distributions and investments.

Your database should preserve that distinction when a grant arrives:

1. The sponsoring organization is the payment source.
2. The named advisor is the person or organization that recommended the grant.
3. Your nonprofit is the recipient, with one received gift and one payment to reconcile.

The fund name may add useful context, but it does not replace any of those roles. Store it as supplied on the grant detail instead of guessing which person or institution it represents.

Capture four parts of the grant before you close it

Start with the evidence that arrived with the money. Keep four parts together on the gift or its intake record:

• sponsor name and payment source;
• grant amount, received date, and payment identifier;
• fund name, grant ID, purpose, and message exactly as supplied;
• recommending advisor and contact details only when disclosed.

Current fundraising systems implement those relationships differently. MonkeyPod's DAF guide records the donation on the sponsoring institution and relates the advisor through a soft credit. DonorPerfect's DAF FAQ describes that model alongside an alternative that creates a record for the named fund.

Choose the model your system can report consistently. Then document where each role lives. A custom payer field, relationship, or recognition field can work when it preserves one received amount and remains visible to the people who reconcile and acknowledge the grant.

If your team uses soft credits, apply the boundary in A soft credit should never create a second gift: recognition may connect the advisor to the gift, while cash-received reporting continues to count the gift once.

Leave an undisclosed advisor undisclosed

Some grant details name the advisor and provide contact information. Others provide only a fund name or say the grant is anonymous. Do not turn a familiar fund name, mailing pattern, or staff hunch into a donor identity.

Record the sponsoring organization, payment, supplied fund name, and an explicit `advisor not disclosed` state. That is more useful than attaching the gift to the wrong person, and it gives future staff a clear reason the advisor field is empty.

This is also a visibility decision. The anonymous-gift record framework can help your team distinguish unavailable identity from a known person whose name must be suppressed. Never use private knowledge to override the grant detail.

Close the same gift in three views

A DAF grant is ready to close when three views agree.

Finance view

The bank or deposit record matches the sponsor's payment amount, date, and identifier. The received amount appears once. Any fund designation or restriction supplied with the grant has an accountable owner for review outside this record-entry workflow.

Fundraising view

The advisor relationship appears only when disclosed, and recognition reports exclude it from cash totals. The fund name remains searchable without becoming another received gift. If your CRM cannot keep recognition and revenue separate, use a relationship or tagged note instead of a second transaction.

Follow-up view

The next message goes to a real destination. Fidelity Charitable, for example, says advisor contact information may appear on its grant detail when the advisor supplies it, and mail sent to Fidelity Charitable cannot be forwarded. Follow the sponsor's current instructions and the information actually provided rather than routing advisor correspondence to the payment address.

These checks fit naturally into a broader gift-processing intake packet. The DAF-specific addition is the explicit split between payment source, disclosed advisor, and fund detail.

Test the policy with one grant

Suppose a $2,500 payment arrives from a sponsoring organization. Its grant detail names the “Harbor Family Fund” and identifies Jordan Lee as the recommending advisor.

Create one $2,500 gift tied to the sponsor's payment. Save the fund name and grant identifier with that gift. Relate Jordan as the disclosed advisor using the recognition method your system supports. Finance should find $2,500 from the sponsor; fundraising should find Jordan's relationship to that same $2,500; a combined cash report should still total $2,500.

Now remove Jordan's name from the grant detail. The payment and gift stay the same, while the advisor relationship becomes undisclosed. That branch is the fastest test of whether your policy follows evidence or fills empty fields by habit.