Donor acknowledgement letters, receipts and Gift Aid records, prepared automatically
We build a workflow that sends each donor an acknowledgement letter or receipt with the details tax rules require, such as the IRS written acknowledgement for US gifts of $250 or more, checks Gift Aid declarations and benefit limits before each UK claim, and drafts charity invoices for corporate sponsors and event partners in Xero. Staff review exceptions, and only authorised people submit claims. A typical build costs $1,000 to $2,500 and takes about four to five weeks.
The problem
Why receipts and Gift Aid records go wrong
Receipts are where small errors become real problems. In the US, a donor needs a written acknowledgement for a gift of $250 or more that names the charity, the amount and whether anything was given in return; event tickets and auctions add a quid pro quo statement once a payment exceeds $75.
In the UK, Gift Aid depends on a valid declaration and on benefits staying within HMRC limits, and claims are only as good as the records behind them. Corporate supporters, meanwhile, want proper invoices for sponsorships and event packages, which are a different thing from a donation receipt.
What we build
What our donor acknowledgement automation includes
Acknowledgements with the right details
Letters and emails from your own templates including the charity name, amount or non-cash description and a goods-or-services statement.
Quid pro quo statements
For tickets, dinners and auction lots, a good-faith estimate of value and the deductible-amount statement added automatically.
Gift Aid record checks
Before each claim, gifts without a valid declaration or with benefits over the limit are listed for staff.
Year-end summaries
Annual giving statements for donors who ask, generated from the CRM.
Charity invoices
Invoices for corporate sponsorships and event packages drafted in Xero, separate from donation receipts.
Exception list
Unusual gifts, such as shares, property or gifts with conditions, sent to finance for a person to handle.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Gift recorded
A gift in the CRM triggers the right acknowledgement template.
-
02
Automated
Receipt sent
The donor gets a letter or email with the required details.
-
03
Automated
Claim records checked
Gift Aid declarations and benefit limits are checked before each claim.
-
04
Staff review
Finance reviews
Finance staff review exceptions, invoices and the claim list.
-
05
Charity lead or trustees decide
Tax filings
Gift Aid claims and tax filings are submitted only by authorised staff.
How it behaves
How receipts and Gift Aid checks behave
What donors see
- A prompt acknowledgement with the details they need for tax
- A clear statement when they received tickets or benefits
- A year-end summary on request
What finance sees
- A Gift Aid exception list before each claim
- Invoice drafts for sponsorships in Xero
- A log of every receipt sent
What the automation does
- Chooses the right template per gift type and country
- Adds quid pro quo statements where needed
- Checks declarations and benefit limits
Edge cases and fallbacks
- Non-cash gift such as shares
- Sent to finance; the receipt describes the gift without valuing it.
- Gift Aid declaration missing
- Excluded from the claim list and the supporter is invited to declare.
- Donor address incomplete
- Flagged for staff before any letter is printed.
- CRM or Xero unavailable
- Receipts queue and retry; nothing is sent from partial data.
Architecture
Receipts, Gift Aid and invoices at a glance.
- Input
- Logic and services
- Output
- People
- Data
How it flows
- 1 A gift or sponsorship recorded in the CRM starts the workflow.
- 2 The right acknowledgement goes to the donor, and sponsorships get an invoice draft in Xero.
- 3 Gift Aid declarations and benefit limits are checked and exceptions go to finance.
- 4 Every receipt, invoice and claim list is logged for audit.
Project planner
How the project runs, phase by phase.
Donation receipts, Gift Aid records & charity invoices project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Gift types, receipt templates, Gift Aid process, event benefits and invoicing today.
-
02
Design
2 to 3 days
Template rules per gift type and country, check rules, invoice mapping and exceptions.
-
03
Build
About 2 weeks
Acknowledgements, quid pro quo statements, Gift Aid checks, invoices and the log.
-
04
Shadow run
About 1 week
Receipts prepared in parallel and checked by finance before any are sent.
-
05
Launch
1 to 2 days
Switch on for new gifts.
-
06
Support
Ongoing
Template changes, year-end runs and rule updates.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Gift types, templates, check rules and invoice mapping.
$250 – $450
-
Build
Acknowledgements, statements, checks and invoices.
$500 – $1,250
-
Integrations
CRM, Xero and email or print.
$150 – $400
-
Testing and shadow run
QA and parallel receipts checked by finance.
$50 – $250
-
Launch and training
Switch-on and finance walkthrough.
$50 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Templates are reviewed by your finance lead or adviser. CRM, Xero and n8n plans are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Accounting: Your Xero plan, including any nonprofit pricing.
- n8n: Self-hosted Community edition, or n8n Cloud from about €20 a month (Starter), billed annually.
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: written acknowledgement for $250 or more
A gift of $250 or more needs a written acknowledgement naming the charity, the cash amount or non-cash description, and whether goods or services were provided in return.
Source: www.irs.govUS: quid pro quo over $75
Payments over $75 that are part gift, part goods or services need a disclosure statement with a good-faith value estimate; the penalty is $10 per contribution, up to $5,000 per event or mailing.
Source: www.irs.govUK: Gift Aid declarations and benefit limits
Donors must make a Gift Aid declaration, charities must keep records, and benefits are capped (25% of gifts up to £100, then 5% of the excess, up to £2,500).
Source: www.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Donor acknowledgement letter questions questions, answered.
For a gift of $250 or more: the charity's name, the cash amount or a description of a non-cash gift without its value, and a statement on whether goods or services were given in return, with a good-faith estimate if they were. Your template is checked by your finance lead.
Yes. Your templates are filled from the CRM for each gift type, sent by email or queued for print, and logged.
It checks that each gift you plan to claim on has a valid declaration and that donor benefits stay within HMRC limits, and lists the exceptions. The claim is submitted by authorised staff through HMRC's own service.
A donation is a gift, so it gets a receipt or acknowledgement. Sponsorships and event packages where the supporter receives something are usually invoiced, and VAT treatment differs, so your finance lead decides which applies. The workflow keeps the two apart.
Templates can follow the CRA or ATO rules where you are registered; the exact receipt contents are confirmed per project with your finance lead.
Time from gift to acknowledgement, receipts needing correction, Gift Aid exceptions per claim and invoices raised on time.
Free 20-minute call
Want this for your charity?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for charities
All servicesCharity CRM & donor management automation
Every gift, supporter and enquiry from online giving, events, post and forms in one charity CRM, with duplicates merged, consent recorded, thank-you tasks and a monthly income view by source.
From $1,000 · About 4 weeks Details
Automated donation & peer-to-peer fundraising pages
One-step registration that creates a supporter's fundraising page automatically, donation pages that process gifts straight into your CRM, and progress nudges that keep fundraisers going.
From $1,000 · About 4 to 5 weeks Details
Volunteer onboarding & rota reminders
Volunteer applications acknowledged, references and checks tracked for staff, role induction and policies sent in order, shift reminders and a simple hours log, with safeguarding decisions kept human.
From $1,000 · About 4 weeks Details