Skip to content

Part 5 of 7 · Gift Aid claimer series ~5 min read

The evidence has to outlive the claim by six years

The claim is money in the bank within a few weeks. The obligation it creates lasts years, and it is an obligation to produce evidence rather than to have been right.

Key takeaways

  • Keep the declaration, not a note that one existed.
  • Freeze the donation record as it was when claimed.
  • Store the reason for every exclusion as well as every inclusion.
  • Six years after the end of the accounting period, not six years from now.
  • Cancellation and correction are events to keep, not edits to make.

What an audit actually asks

What an audit asks for and what has to already existThree boxes across the top sit outside the AWS account. A question about one donation years later. The claim: what was submitted and when. And The rules then: rates and limits as they stood. Each connects by an arrow to the AWS account container below, labelled asks, identifies and governs. Inside are three components. The declaration, meaning the actual document rather than a flag. The donation, frozen as it was when claimed. And The reasoning: why this one qualified. A note says none of the three boxes inside can be produced later from a live system because a live system has moved on, so they are written at claim time or not at all.AWS ACCOUNTA questionabout one donation,years laterThe claimwhat was submittedand whenThe rules thenrates and limits asthey stoodThe declarationthe actual document,not a flagThe donationfrozen as it waswhen claimedThe reasoningwhy this onequalifiedasksidentifiesgovernsNone of the three boxes inside can be produced later from a live system, because a live system has moved on. They are written at claim time or not at all.
Fig 1. Three inputs to an audit and three things it needs to see. The system’s job is that all three still exist and still line up.
  • Machine learning
  • Security & identity
  • Analytics

A flag is not evidence

The single most common shape of failure is a donor record with a Gift Aid box ticked and no document behind it. It is enough to build a claim from and not enough to defend one, and the gap between those two states is invisible until somebody asks.

So the declaration itself is kept: the scan, the web submission with its timestamp, or the written confirmation sent after a verbal declaration. It is a small file, there is one per donor rather than one per donation, and it is the cheapest thing in the system to store and the most expensive to be missing.

Six years, counted from the right place

Retention measured from the end of the accounting periodA horizontal row of five boxes joined by arrows. Donation, the money arrives. Period close, the accounting year ends. Claim, submitted and paid. Retention runs six years from the period end. Then delete, and record that you did. A note says a donation in the first month of a financial year is held nearly seven years, and getting the start date wrong deletes evidence while it is still required.THE CLOCK STARTS AT THE PERIOD END, NOT THE DONATIONDonationthe moneyarrivesPeriod closethe accountingyear endsClaimsubmitted andpaidRetention runssix years from theperiod endThen deleteand record thatyou didA donation in the first month of a financial year is held nearly seven years. Getting the start date wrong deletes evidence while it is still required.
Fig 2. Five stages, and the fourth is longer than people assume. The clock does not start when the money arrives.
  • Storage
  • Machine learning
  • Security & identity

Corrections are events

A donor cancels. A declaration turns out to have the wrong address. A donation is refunded. Each of these changes what should have been claimed, and each is a new fact with its own date rather than a reason to edit an old one.

Keeping them as events costs nothing and makes the difference between a system that can say this was correct when claimed and changed in March and one that can only say this is wrong now. The first is a conversation with HMRC. The second is a repayment.

The sentence the evidence has to be able to write

  • This donation of 40 pounds was received on 12 March.
  • It was matched to a donor whose declaration took effect on 3 February.
  • That declaration is attached, with the home address HMRC matches on.
  • It was claimed in the schedule submitted on 30 June, line 1,844.
  • The declaration was cancelled on 9 September, which is after this donation.

Where this ends

The system does not make the charity compliant, because compliance is a thing people do rather than a thing software has. What it does is make the compliant answer the cheap one: the declaration is already stored, the routing already has a reason against every donation, and the claim already froze its own inputs.

The next post prices it and the one after gives the service names, the tables and the IAM. The interesting thing about the cost is that almost none of it scales with donations, because the expensive step happens once per donor rather than once per gift.

All posts