What we learned when churches started submitting Gift Aid to HMRC

The £560M problem nobody talks about

Here's the uncomfortable truth: UK churches leave roughly £560 million in Gift Aid unclaimed every single year. Not because they don't want it. Because the process is broken.

Gift Aid is straightforward in principle. A donor gives £80. Because they've paid tax, the church can claim £20 back from HMRC. That's the scheme. But submitting it? That requires navigating HMRC Charities Online, understanding filing deadlines, tracking declarations, matching them to donations, and doing it all without making mistakes that trigger compliance queries.

Most church treasurers are volunteers. They work nights and weekends. They're not accountants. So the claim either doesn't happen, or it happens late, or it happens wrong. And the money that should flow back to mission work, community projects, or pastoral care just sits in the HMRC system.

When we started building Givr, this was the problem we couldn't ignore. Giving could be frictionless for the congregation - that part was solvable with a QR code and 15 seconds. But Gift Aid was still a wall of friction on the church's side.

Why automating the submission actually matters

The Gift Aid declaration capture part was the easier piece. We built that into the donation flow so when someone gives through the platform, we ask them (once) to tick the Gift Aid box. No extra friction. Their data gets stored securely. That bit works well.

But the submission to HMRC Charities Online is where most churches stumbled. You need to batch the claims. You need to file within the calendar year. You need to report the total number of claims, the total amount claimed, and keep records that HMRC can audit if they ask. Miss a deadline or misfile, and you're explaining yourself to a compliance officer. Miss it several times, and you lose the ability to claim at all.

We decided early on that Givr would handle the entire submission. The church treasurer wouldn't log into HMRC at all. We'd do it for them.

The first time a church used the automated submission feature, I watched the process end to end. Givr calculated the claim amount, formatted it to HMRC's exact specification, submitted it to Charities Online, and generated a receipt. Total time on the church's side: they needed to authorise it. That's it. No spreadsheets. No compliance anxiety. No filing deadline panic.

That's not a feature. That's permission to not worry.

What we got wrong, and what we fixed

The Gather tier was where automated HMRC submission lived, so it made sense to layer in the other things churches needed: GoCardless for recurring giving (because standing orders are how most churches actually fund their work), and GASDS support (the small-donation scheme, which has different rules and can actually be more valuable if you're claiming under £1,000).

But we made one mistake early on. We assumed churches would understand that the HMRC submission happens automatically, invisibly, on their behalf. We were wrong. Some treasurers wanted to see it happen. They wanted to verify the numbers before they hit HMRC's servers.

So we built it in. The dashboard now shows you exactly what's being claimed, when it's due to submit, and a clear summary before the submission goes through. It's still automated - the church doesn't have to do anything - but it's transparent. You can see the working.

That changed things. Treasurers started trusting it faster. And we started getting fewer support queries that boiled down to 'did this actually work?'

The other thing we learned: not every church fits the same Gift Aid pattern. Some are small and only file once a year. Others are large enough to file quarterly. So we built flexibility. The system can hold claims and batch them on whatever schedule makes sense, rather than forcing a one-size-fits-all deadline.

The conversation with an actual HMRC caseworker

A few months in, we were preparing the platform for scale, and I wanted to understand something nobody had explained clearly: how does HMRC actually see these submissions from Givr? Are we filing them as the church? As ourselves? As some kind of intermediary?

The answer mattered legally and operationally.

After a few calls with HMRC's technical team, it became clear: we file on the church's behalf, using their charity number and their authorisation. From HMRC's perspective, it's the same as if the treasurer logged in and did it themselves. We're just handling the mechanics. The church is the declarant.

That meant we had to make sure our submission process was bulletproof. An error on our side is an error on the church's record. A late submission is the church missing the deadline. So we built in redundancy, testing, and audit trails that are probably overkill but feel right when you're touching a government system.

It also meant we could never position this as 'we handle your compliance for you.' We can automate. We can make it easier. But the responsibility for accuracy stays with the church. That's why the dashboard shows the exact numbers before submission. Radical transparency.

Why the platform fee scales the way it does

The Free tier works for small churches wanting to try it. You get the dashboard, donor tracking, and fund tracking. Platform fee is 1% of what people give. Simple.

Move to Gather (£25 a month or £245 a year), and the platform fee drops to 0.5%. That's the Gift Aid tier. On top of the subscription, we also take 2% of whatever Gift Aid you successfully claim from HMRC. That feels fair to us. You're reclaiming money that existed but you weren't capturing before. We're helping you unlock it. We share a bit of the upside.

The point is that the Fee scales because the value scales. A church claiming £4,200 in extra Gift Aid because of Givr wasn't paying for that somehow before. We're not extracting profit from existing money. We're helping money flow that wasn't flowing.

Some platforms hide this kind of thinking behind marketing language. We just wanted to be direct about it.

What actually happens on submission day

I want to be specific about what HMRC submission looks like in practice, because I think it removes some of the fog.

A church using Gather has been collecting Gift Aid declarations for, say, three months. The dashboard shows them: 47 donors, £1,840 claimed, all properly declared. The submission window opens. The church treasurer (or the vicar, or whoever has Givr access) logs in, reviews the numbers, and authorises submission.

Givr formats that data to HMRC's exact specification, submits it through Charities Online, and stores the submission receipt. HMRC processes it within their normal timeframe - usually a few weeks - and the money gets paid directly to the church's bank account.

The church sees the claim in their Givr dashboard, marked as submitted. Once HMRC pays, it's marked as completed. No spreadsheets. No guessing whether it went through. No calling HMRC to ask where the money is.

That process takes about three minutes of active work from the church. Everything else is automated. And that's the practice of it.