Do you assign a cons code or attribute to donors giving via DAF, IRA, etc?

@Cathy Spencer I'm right in there with @Heather MacKenzie and @Joe Moretti with the response and also in enjoying the community members involved in this thread! So sad to not be going to bbcon in person this year.

I created a gift attribute of IRA Rollover: Firm/Bank and we have a table with the common sources that the gift entry person can add to. It is one of the few tables that I haven't completely locked down. This helps as we so often get checks with no identification of which donor to attribute it to. This way we can narrow down some calling to known IRA donors first.

At our org our policy is to consider our gift date to be the postmark date or the check date whichever is later. For IRA rollovers we want to capture the date it was actually received and we include that in our acknowledgements.

We are still entering most gives through the DBV and have a separate batch template for IRA rollover entries so we can capture all the things we need to without having to think too much about it since we might get 20 to 30 a year.

In the reference field, I have a prompt: “IRA Rollover; Copies of checks made”
This helps to remember that we share a copy of the check with the acknowledgement

We set the receipt amount to $0 as they have already received their tax benefit and our letter is truly a thank you.

We insert the Firm/Bank into that letter as well.

Right now we have a gift subtype of IRA Rollover. I'm cogitating if I want to keep this or not. Part of a bigger redesign to accommodate how to use the web view with its limited fields.

It is our regular acknowledgement letter and the formulas change the letter for IRA Rollovers.

Here are some visuals

@Cathy Spencer
I've set it up as a Gift Attribute. Easy enough to pull from there.

@Cathy Spencer

We add an organization relationship to the DAF holder for every donor who gives through DAFs, with the name of their fund in that relationship record (as their position or in the notes if the donor is an organization). We also have a constituent code. We add a standard “DAF no tax receipt” in the reference of the gifts.

Thus far, I've only needed to pull DAF donors together in a list for staff at my organization, but we have the capability to pull lists of who gives through which financial institution and the gifts if needed.

I'm not a big fan of creating codes or attributes without a use case. As @Heather MacKenzie pointed out, donors usually have multiple methods of making their gifts, and may not use a DAF or IRA QCD for all of their donations.

My org uses gift attributes to note things like this, and as they are tied to the gift and not the donor record itself, it makes more sense. @Christine Cooke bCREPro mentioned something like this as well. It's very easy to run a gift query for these items and output the constituent information. But I would not put that information on the constituent record.