What goes wrong when receipts and deposits drift apart
Picture a small community nonprofit the week after its fall fundraiser. Gifts came in four ways: checks in the mail, cash and checks at the event, online donations through a payment processor, and a few employer matching gifts. A volunteer sends thank-you receipts from a spreadsheet. Weeks later the treasurer reconciles the bank statement and finds that the spreadsheet total, the receipts sent, and the deposits do not match, and nobody can say which donor was receipted twice and which one was missed. That scene is an illustration, not a TwoQM client.
Donor receipts and bank deposits are usually handled by different people at different times. The receipt goes out quickly because donors expect it. The deposit is reconciled later because that is how bookkeeping works. When the two are never tied together, small errors pile up until year-end, when donors ask for annual statements and the board asks for clean numbers.
This is an operations article, not tax or legal advice. The IRS publishes rules for written acknowledgments of charitable contributions and for quid pro quo contributions, where a donor receives something in return, and Publication 1771 explains substantiation and disclosure requirements. Your organization's accountant and those official sources decide what a receipt must say. This article is about keeping receipts and deposits in step.
TwoQM has already written about grant deadline calendars and document packs and volunteer shift signups. This piece is different. It is about individual gifts: grouping them into batches that match real deposits, so every receipt can be traced to money in the bank.
Here is an original example, not a measured result. A nonprofit receives gifts by mail, at events, and online. Without batches, the common failures look like this:
Receipts go out before the money is confirmed. A check bounces or an online gift is refunded, but the receipt already went out.
Online payouts are lumped together. The processor deposits several days of gifts at once, minus fees, so no single gift matches the deposit line.
Event gifts lose their details. Cash and checks from a table get counted, but the donor names are on a separate sign-in sheet.
Duplicates slip through. A donor who gave online and by check at the event gets one combined receipt, two receipts, or none.
Year-end statements are rebuilt by hand. Someone re-adds a year of gifts to answer one donor's question.
One batch per deposit
The fix is to group gifts into a batch that matches one deposit:
Batch header. Deposit date, deposit method, the person who prepared it, and the person who reviewed it.
Gift lines. Each donor, date received, amount, method, check number or processor reference, and any restriction or designation the donor named.
Goods or services. Whether the donor received anything in return, such as an event meal, so the receipt follows your organization's policy for those gifts.
Fees and adjustments. For online gifts, the processor fees and refunds that explain the difference between gross gifts and the payout.
Totals check. The batch total, adjusted for fees, must equal the deposit on the bank statement before the batch is marked reconciled.
Receipt status. For each gift, whether a receipt was drafted, reviewed, sent, or held.
The rule is simple. A gift can be thanked right away, but its receipt is tied to a batch, and a batch that does not match its deposit is flagged before more receipts go out from it.
Let the systems do the matching
This is where connected systems help. Online gifts can flow from the payment processor into the donor database already grouped by payout, with fees and refunds attached. Mail and event batches can be entered once, by the person who prepares the deposit, instead of being retyped by the receipt volunteer. A CRM can keep each donor's gifts on one record, which makes duplicate checks and year-end statements a report instead of a project.
Plain business automation covers the reminders: batches waiting for review, deposits with no matching batch, receipts held because a check has not cleared, and donors with more than one gift in the same week.
Where AI helps, and where it stops
AI can read a scanned check list or event sheet and draft gift lines for review, suggest possible duplicate donors, and draft thank-you letters in English or Spanish from your approved templates. A person reviews every draft. AI does not decide what a receipt must legally say, value goods or services, mark a batch reconciled, or send receipts on its own.
Where to start this week
Take last month's bank statement and pick three deposits. For each one, try to list the donors and receipts behind it. If that takes more than a few minutes, write down the batch fields above, name who prepares and who reviews each batch, and start with the next deposit.
TwoQM builds connected systems, automation, and custom software for nonprofits. If receipts and deposits keep drifting apart, TwoQM can scope a donor batch workflow around the tools you already use. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Donor Receipt Workflow · Explore TwoQM business automation