How are you using Gift Codes?
"Gift Code" has been a field we have historically not been using. I am wondering how other people/organizations use it to get an idea of how it could be helpful. Thanks!
Answers
-
Our use of gift code is done for finance/accounting. For their work they want to know if in more detail than pay method, the channel/source of payment.
Examples of our codes: Cash, Check, BBMS, EFT, ACH, payroll deduction, stock, PayPal, Venmo, ABC giving platform, Revocable Pledge, etc. Yes, some is same a pay method but they run their reports based on gift code is my understanding.
2 -
Similar for me - generally as a "deeper dive" for payment method, especially helpful for EFT direct to bank transfers which come from multiple sources so that we can easily reconcile. BBMS, Stripe, CanadaHelps, etc. This does mean a small amount of overlap, with things like Cash, Cheque which are in payment type, but if you start using the field, it's best to use consistently and not have blank entries, in my opinion. :)
Realizing I mis-read the question. This is what I do for Gift Subtype, not Code, sorry for confusion! I've more often used Gift Code for adding the identifier from third party processors, which helps with reconciliation. Gift code is really a catch-all field, it's ideal for "there's no where else for this thing that it's important for finance to know, but I don't want it part of the posted gift."
2 -
Interesting responses. Some of the codes that @JoAnn Strommen listed here are designed to go in Gift Subtype, not Gift Code. Gift Subtypes can be attached to funds and are used to designate specific debit account GL numbers, which each payment source would have (though I imagine both 'cash' and 'check' in your methodology would use the same GL account).
That said, there are indeed further subdivisions that wouldn't make any sense as a gift subtype. We use this field to define IRA/QCD, Charitable Gift Annuity, and DAF.
0 -
I used gift sub-type at previous org. Have not seen it used here. I don't necessarily agree with methods used by finance but they were determined long before I came and it's not my responsibility.
They all go into same debit GL. A gift validation report is run for each gift code for them to work from for reconciling - gift code is also a gift attribute. There's not a filter on those reports for gift sub-type.
We have a relatively new CEO and are wrapping up capital campaign. My understanding is some changes will be coming on accounting side. I hope to have a voice. :)
2 -
@JoAnn Strommen Sometimes we have to pick our battles. :)
0 -
We use the Gift Code field to track the "source" of where a gift came from. We have gifts that flow to us through a lot of different sources, such as third-party processing companies, pass-thru agreements with other organizations, trusts & estates, etc. It's really helpful for us. We can tell if this was a gift from an estate (so not a living person we can solicit again), from our text-to-give vendor, from one of our online portals and which one (we have more than one for various reasons). It's great for our internal purposes and reporting!
4 -
We also use Gift Code to track the source, as Deven mentioned. Examples are: Direct Mail, Benevity, Facebook, Fidelity, etc. - other than Direct Mail, the sources are typically third-party processing companies.
1 -
Thank you everyone! I like Devan and Jocelyn's method - we have historically used the reference field for things like noting if it was a benevity or which DAF it is (Fidelity vs Schwab/DAF360 etc) but code might be useful because it's queriable.
0 -
Same as a few above, I have always used gift code to track source. To add to the list of already mentioned I also include Online Giving, Payroll Deduction, EFT …
0
Categories
- All Categories
- 6 Blackbaud Community Help
- 206 bbcon®
- 1.4K Blackbaud Altru®
- 394 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 357 Blackbaud eTapestry®
- 2.5K Blackbaud Financial Edge NXT®
- 646 Blackbaud Grantmaking™
- 561 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 934 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.4K Blackbaud Raiser's Edge NXT®
- 3.6K SKY Developer
- 242 ResearchPoint™
- 117 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 238 The Tap (Just for Fun)
- 33 Blackbaud Community Challenges
- 28 PowerUp Challenges
- 3 (Open) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 778 Community News
- 2.9K Jobs Board
- 53 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)






