A Donation Receipt Is a Legal Document, Not a Mail Merge

Every January, church offices across North America run the same ritual: export the year's giving, mail-merge it into a letter with the logo at the top, and send thousands of "receipts" to grateful donors. It feels like an administrative chore. In Canada, it is the production of a legal document with a mandatory field set, sequencing rules, and math the CRA has opinions about — and a surprising amount of church software treats it like a newsletter.

The risk lands on the charity, not the vendor. So it's worth being precise about what these documents actually are.

Canada: the official donation receipt

A CRA official donation receipt is not "a receipt, officially." It's a defined document. Among other things, it must include:

• The words "Official donation receipt for income tax purposes"
• The charity's legal name, address, and registration (BN) number
• A unique serial number
• The date of the donation and the date and place the receipt was issued
• The donor's name and address
• The eligible amount of the gift for tax purposes
• The name and website of the CRA
• An authorized signature

Two of these trip up software constantly.

Serial numbers must be sequential and accounted for. Receipt 2026-000481 implies 480 receipts before it, and if number 344 was issued in error, it doesn't vanish — it's marked cancelled, keeps its number, and the replacement cites the original. A system that generates receipt "numbers" from random IDs, or renumbers when a receipt is deleted, isn't producing CRA-compliant receipts. It's producing decorated PDFs.

The eligible amount is not the amount paid. This is split-receipting, and it's where mail-merge receipting fails hardest. When a donor pays $250 for a gala ticket and receives a dinner with a fair market value of $85, the receiptable amount is $165 — and the advantage must be described on the receipt. If the advantage crosses CRA's thresholds, the payment isn't receiptable at all. Software that can't model the advantage will happily issue a $250 receipt, and every one of those is wrong.

There's a quieter requirement underneath all of this: receipts must be reproducible. If a donor asks for their 2023 receipt in 2027, the charity must produce the same document — same number, same amounts, same charity details as they were at issue. That means receipts have to be immutable snapshots, not reports re-run against live data. It also means you can never hard-delete a person who has giving history, no matter how tidy it feels.

The United States: acknowledgments and disclosures

The US regime is different in shape but just as easy to fumble:

• Any single gift of $250 or more needs a contemporaneous written acknowledgment for the donor to claim the deduction.
• A payment over $75 that's partly a purchase — the fundraising dinner again — needs a quid-pro-quo disclosure stating the deductible portion (payment minus the fair market value of what the donor received).
• Where nothing was received in return, the acknowledgment should say so: the "no goods or services were provided" language donors' accountants look for.
• Non-cash gifts get described, not valued — the church does not assign an FMV.

None of this is exotic. But it has to be modeled, not formatted: the software has to know what an advantage is, which fund is deductible, and what the donor actually received.

Why so much software gets Canada wrong

Most ChMS products are US-born. Receipting ships as an annual-statement generator that matches IRS expectations, and Canadian churches make do — hand-typing BN numbers into letter templates, tracking serials in a spreadsheet, and quietly hoping the gala tickets never come up. Add the multi-campus wrinkle — a campus that's its own registered charity needs its own registration number and its own independent serial sequence — and the spreadsheet era ends badly.

We built SundayHQ's giving module with the compliance engine at the center rather than the edge: receipt regimes per organization (and per campus where campuses are separate charities), gap-tracked sequential serials per legal entity per tax year, split-receipting with the advantage printed, void-and-reissue with an audit trail when a receipted gift is refunded, and immutable snapshots so every receipt reproduces forever. The full write-up is here.

Three questions to ask your current system

1. Show me last year's receipt #200. Now show me it again, identical, after we corrected a gift from that donor.
2. Enter a $250 gala ticket with an $85 dinner. What does the receipt say the eligible amount is?
3. Our second campus is its own registered charity. Whose BN and serial sequence go on its receipts?

If any answer involves the word "workaround," the mail merge is writing legal documents on your behalf. That's worth fixing before next January — and the demo will show you what fixed looks like in about two minutes.