What your year-end giving statements must include

It is the second week of January and someone has emailed the church office asking what they gave last year. They need the number for their return. It should be a two-minute answer.

It is rarely a two-minute answer. The card gifts are in a payment processor. The gifts through the church's own payment links are in a bank statement. The person who gave under two email addresses appears twice. And the treasurer — usually a volunteer with a job — has to reconcile those lists well enough that a document going out under the church's name can be relied on by someone filing taxes.

That reconciliation is the actual work of year-end receipting. The document is easy. Knowing the document is right is not.

What the IRS actually requires

Worth being precise about, because much church advice here is folklore. Two separate rules apply, at different thresholds.

The $250 rule. A donor cannot claim a federal income tax deduction for any single contribution of $250 or more without a contemporaneous written acknowledgment from the organisation. The IRS is direct about where the burden sits: "An organization that does not acknowledge a contribution incurs no penalty; but, without a contemporaneous written acknowledgment, the donor cannot claim the federal income tax deduction." The cost of getting this wrong lands on the giver, not the church.

That acknowledgment must contain, per Publication 1771:

1. the name of the organization
2. the amount of any monetary contribution
3. a description (but not the fair market value) of any contribution of property
4. a statement that no goods or services were provided by the organization in return for the contribution, if that was the case
5. if the organization did provide goods or services in return, a description and good faith estimate of their fair market value
6. if the organization only provided intangible religious benefits in return, a statement so providing

Item six is the one churches most often miss and most often need. Intangible religious benefits are, in the IRS's words, "benefits provided by a charitable organization organized exclusively for religious purposes, and are not usually sold in commercial transactions outside a donative (gift) context" — admission to a religious ceremony, for instance. Where only those were provided, the acknowledgment need not describe or value them.

"Contemporaneous" has a deadline. The donor must receive the acknowledgment on or before the earlier of the date they file their return for the year of the contribution, or that return's due date including extensions. The IRS notes the convention: "Charities typically send written acknowledgments to donors no later than January 31 of the year following the donation." That is a norm rather than the rule, but it is the norm because it clears the rule for almost everyone.

The $75 rule is a different rule. Where a donor makes a quid pro quo contribution — partly a gift, partly payment for goods or services — in excess of $75, the organisation must provide a written disclosure statement. Here there is a penalty on the church: $10 per contribution, up to $5,000 per fundraising event or mailing. A banquet ticket or a benefit concert seat walks into this rule without anyone deciding to.

Sources: IRS Publication 1771 (irs.gov/pub/irs-pdf/p1771.pdf) and "Substantiating charitable contributions" (irs.gov), both read September 10, 2026. General information, not tax advice.

Keep that checklist whether or not you ever use Harvest. Hold any statement your church sends against those six items and the two thresholds and you will catch most of what goes wrong.

The part that is actually hard

Nothing in the requirements is difficult to write. The difficulty is upstream, in knowing who gave what.

A payment processor knows about transactions. It has no concept of a member, so it cannot know that a gift from one email address in March and one from another in October came from the same family. A church management system knows about members but has never seen a transaction. So reconciliation happens by hand, once a year, under time pressure, by someone matching names across exports — and every duplicate in that pile is a household that gets two statements, each understating what they gave.

That is the cost of assembling a back office out of parts: a giving processor, a separate member database, a separate email tool to send the statements. Three subscriptions, three logins, three lists drifting apart since the day they were set up. The full cost of that stack is usually larger than churches expect, and January is where the hidden part gets paid.

How Harvest handles it

On every paid plan, your church publishes its own payment links — PayPal, Cash App, Venmo, Zelle, Revolut and Wise — on one giving page, and a member taps the account they already use. The gift goes straight to your church; Harvest is never in the flow, holds nothing and charges 0% on all three paid plans. Because Harvest never sees that payment, the record is something you make: a gift recorded in the CRM writes an invoice, and that one entry reaches your dashboard, your accounting ledger, the giver's own history, their downloadable receipt and the year-end statement this article is about. Contacts are deduplicated by email, so one person does not scatter across three rows. The giving page starts on Individual, at $20/mo; Forever Free has no giving page, so giving begins on the cheapest paid plan.

Tax receipts and giving statements themselves are a Ministry feature — the top of the three paid plans, $80/mo, or $752/yr, which the pricing page shows as $62.67/mo, billed as $752 every 12 months. Ministry is also where the accounting and receipt ledger lives: every donation receipt and event ticket Harvest issues, each with a numbered PDF, on a tier holding 2,000 contacts and 15 admins. Custom branding is on the same tier and reaches the artifacts people keep — receipts, certificates and forms carry the church's own name, logo and colour rather than ours. All four tiers sit side by side on pricing.

No platform can decide for your church whether a gift was quid pro quo. Check any generated statement against the six-item list above before it goes out, ours included.

The loop this closes

Receipting is not really a document problem. It is a knowing who gave problem, and the record that knows who gave is the same record carrying everything else the church knows about that person. Courses sit on every tier. QR check-in starts on Small Team. Community groups and event registration are Ministry. A standalone receipting tool starts from zero every January — handed a pile of transactions, asked to guess which are the same household.

One member record does not have to guess, because it was never assembling the answer — it has been keeping it since the first gift landed. The January reconciliation exists only because giving and membership were kept in different systems. One subscription, one member record, one login, and the answer to "what did I give last year?" is already written.

On why a church should handle money visibly and not merely correctly, there is an older argument.