One Gift, Two Records, No Thank-You: How a Donor-Advised Fund Gift Gets Lost

The check arrives with a familiar name in the memo and an unfamiliar organization in the sender field. The gift processor records the payment under the sponsoring organization. A fundraiser recognizes the family who recommended it. Both assume the other has the thank-you covered.

The payment is entered. The relationship is not.

This is a fictional example, but it illustrates a real operational problem: the organization receiving the money, the person who recommended the grant, and the people responsible for acknowledging it may all sit in different places in a fundraising system. A deposit can reconcile while the human handoff remains open.

One payment, several questions

Suppose a community organization receives a $5,000 grant from a donor-advised fund sponsor. The accompanying information identifies a donor who recommended the grant. The gift processor must record the payment accurately and reconcile it to the bank deposit. The relationship manager wants to know that the donor made the recommendation and whether a personal thank-you is appropriate. Finance may need to confirm the sponsor’s instructions and the organization’s acknowledgement practices.

Those are related jobs, but they are not interchangeable. The sponsoring organization and the recommending donor have different roles. Your team should follow its own accounting, gift acceptance and legal guidance when deciding how to record and acknowledge the transaction. The IRS describes a donor-advised fund as a fund maintained by a sponsoring organization; donors can advise on distributions, while the sponsor has legal control over the assets. IRS: Donor-advised funds.

The practical question for the fundraising team is simpler: once the gift is recorded, can someone see the next relationship action and who owns it?

The handoff that often goes missing

A useful workflow starts with a small set of explicit decisions:

• Identify the payment and its source. Capture the sponsor, amount, date and any reference information needed for reconciliation.
• Connect the relationship when supported by the information received. If the sponsor identifies the recommending donor, link that person to the transaction using your organization’s approved attribution rules. If the information is missing or ambiguous, flag it for review rather than guessing.
• Assign the next action. Name the person responsible for checking the acknowledgement and relationship follow-up. Give them a due date and a backup.
• Record what actually happened. A task can capture whether follow-up was sent, a question was referred to finance, or the sponsor’s instructions prevent a particular response. A closed deposit is not automatically a closed relationship task.

This need not mean putting sensitive financial details in front of every staff member. A fundraiser may only need the permitted relationship context, the amount and the next action; finance may need a different view. Decide those boundaries before building the workflow.

Ask a different question at the weekly meeting

Many teams already review gifts received and deposits reconciled. Add one question: Which gifts have reached the bank but still have an unresolved relationship action?

Start with a small sample of recent grants. For each one, can the team find the transaction, identify the right relationship when information was provided, and name the person responsible for follow-up? How long has the next action been open? Are there legitimate reasons a follow-up should wait?

The exercise may reveal a missing field. It may also reveal a missing agreement between teams. A better report cannot resolve an unclear owner on its own.

Where an AI teammate can help

An AI teammate could surface an unresolved handoff, gather the context a staff member is authorized to see, or prepare a thank-you draft for review. People still decide how to attribute the relationship, handle uncertainty and communicate with the donor. The useful measure is whether the right work gets completed with the right context—not how many messages the system can generate.

One gift can be correctly entered and still leave a person waiting. Connecting the record to a named next action is how the organization closes that gap.