Part 3 of 3 in our series Getting Ready for GivingTuesday and Year-End
The first two posts covered what donors see and the emails that bring them in. This one covers the back office: the accounts that touch money, your donor database, and how to keep everything steady from GivingTuesday on December 1 through December 31.
1. Lock down every account that touches money
- Turn on multi-factor authentication (MFA) for your donation platform, payment processor, bank, email platform, donor database, website admin, and social media accounts. Our October post [link: Not all MFA stops a phish] explains which kinds hold up best.
- Review who has admin access, and remove former staff, volunteers, interns, and vendors.
- Make sure at least two trusted people can get into each account, so nothing stalls if someone is out sick on December 1.
2. Make your donation form a harder target
Fraudsters use donation forms to check whether stolen card numbers still work, running small charges of a few dollars each. This is called card testing. Signs include a burst of tiny gifts, many declined transactions in a short time, and new donor records with names that don’t look real.
- Turn on the CAPTCHA or bot protection your donation platform offers.
- Ask your payment processor what fraud tools it has and whether they are turned on.
- Consider setting a minimum gift amount.
- Know who to call at your processor if it happens.
Expect more scams, too. Giving season is busy, and scammers know it. Watch for a “board member” asking for gift cards, a vendor emailing new bank details, or an urgent invoice you don’t recognize. Verify any request involving money by calling a number you already have. Our post [link: Write the callback rule down] covers how to set that up.
3. Set up your donor database before the gifts arrive
- Create a campaign or appeal code for GivingTuesday and another for year-end, and make sure online gifts are tagged automatically. In January, this is how you’ll know what worked.
- Merge duplicate records and fill in missing first names. A blank name field turns “Dear Maria” into “Dear,”. Set a default greeting in your email platform as a backstop.
- Confirm that your donation form, donor database, and accounting system are passing gifts to each other. The test gift from [link: Part 1] is the easiest way to check.
- Set up an automatic thank-you email that goes out as soon as a gift comes in. The IRS requires a written acknowledgment before a donor can deduct any single gift of $250 or more, and a disclosure statement when a donor pays more than $75 and gets something of value in return, like an event ticket. Have your accountant or tax advisor review the wording of your receipts.
- Export a backup of your donor list before December.
4. Hold off on big changes until January
December is the wrong month to launch a new website, switch donor databases, or move to a new donation platform. Do the routine maintenance now instead:
- Apply software and plugin updates and back up your website before December 1, so there is time to fix anything an update breaks.
- Write down who to call if something goes wrong: your web host, your donation platform’s support line and its hours, and whoever manages your domain.
- Decide who will watch donation notifications and the general inbox between December 24 and January 1. A donor with a problem on December 31 needs an answer that day.
Once the gifts come in, send thank-yous within 48 hours, and plan your January year-end giving statements now so donors have them at tax time.
Ask IT4Causes for help
IT4Causes helps nonprofits with this work every day: turning on MFA, setting up password managers, reviewing who has access to what, setting up donor databases, and planning for what happens when a system goes down. If you want a second set of eyes before December 1, or help after it, reach out. Email info@it4causes.org or call 804-608-6378.
The full series
Focus on your mission – we’ve got your tech.