Live HMRC submissions, every week · Cascade 2.0 is hereYou are accountable for a Gift Aid position you cannot see. Cascade shows you every claim, every exclusion, and the reason behind both — going back years, and updated every time your data changes.25%added to every eligible donationDaysto claiming again, not monthsEveryclaim decision recorded and explainableDirectHMRC submission, no middleman
Cascade brings your donor data, declarations and HMRC submissions together around one donor record and one audit trail, giving you one complete Gift Aid position and making sure you claim everything you are entitled to.
Gift Aid Hub sorts every donation you hold into what has already been claimed, what is ready to go, and what could still be repaired — then drafts the claim, files it with HMRC and manages what comes back.
Search by name or supporter reference and get their giving, their Gift Aid position and their declaration state on one screen — without opening the CRM.
Scans, correspondence and forms filed against the supporter they belong to — so the evidence behind a claim is one click from the record, not a morning in a filing room.
Every query about your Gift Aid data, raised against the record it concerns and tracked to a decision. A correction, an exclusion, a repair — logged, reviewed, applied and resolved, with the full history sitting on the row instead of in someone’s inbox.
Point-and-click segmentation and drillable income reports over one governed model of your data — so the figure on your dashboard and the figure in your board pack are the same figure.
That was all. A tidy piece of admin, by someone doing their job properly.
The next Gift Aid claim excluded that supporter, and an action was raised asking why. We had claimed on the named individual for years without issue. The answer was in the record’s change history. The update had turned an individual supporter record into a joint record, where you can no longer identify which individual is the taxpayer.
The historic claims were valid, and we could show it. That is the question an auditor actually asks — not “were you wrong?”, but “why did this change?”
The next claim would not have been. Without the exclusion, they would have carried on claiming on a joint record. That is money you give back.
Nobody did anything wrong. No CRM flagged it. No human would have found it.
Every donation that fails an HMRC compliance rule is locked and excluded from the claim. But Exclusions goes further. We can build exclusions around your own in-house rules too: test records, event-specific Gift Aid exclusions, out-of-date source codes, or anything else you need kept out of a claim.
If you can describe what worries you, we can fence it off.
Fix the problem, release the money, and watch your next tax claim build as excluded donations become claimable.
Every exclusion tells you something.
If address exclusions start rising, that is not really a Gift Aid problem. It tells you something has changed in the way data is entering your system, and you can see it before it starts costing you Gift Aid.
Most data quality tools tell you that twelve per cent of your addresses are incomplete. That produces a percentage, perhaps a ticket, and very often not much else.
We tell you what those incomplete addresses cost you last quarter, whether that cost is rising, and where to look for the cause.
A number with a pound sign gets fixed. A percentage gets filed.
1.0 gave you separate tools over separate data, and the numbers could drift — the dashboard, the board report and the export could each work it out differently. 2.0 runs on one governed model with one definition of a supporter, a gift and Gift Aid eligibility. Fix an address once and it is fixed everywhere. Ask the same question twice and get the same answer.
1.0 could tell you something was wrong. It could not tell you who was fixing it. Actions turns every flag into a unit of work with an owner, a value at risk and a reason recorded when it closes — so nothing worth chasing quietly stops being chased.
Gift Aid rules used to live in our code, so a change meant a release. 2.0 runs a declarative rules engine configured per charity — your eligibility rules are yours to set and yours to change.
Ask a question in plain English and get the answer with the working behind it, on near-live data rather than last month’s extract. Harmony reads the same governed model as everything else, so it cannot disagree with your dashboard.
1.0 audited claims. 2.0 audits every change to every record. When HMRC asks why a donation was included, excluded or repaired, the answer is one click away — who, when and why.
Cascade 2.0 runs on Google Cloud, giving Analytics the infrastructure to work interactively on near-live data rather than relying on overnight batches.
The reason Cascade 2.0 works differently is underneath it. Every product reads and writes the same donor record and the same donation record — so there is no sync between modules, because there is nothing to sync.
Fix a supporter’s address once and it is fixed in the claim, in the declaration, in the report and in the next mailing. No reconciliation, no overnight job that might not have run.
Your Gift Aid eligibility rules are configured for your charity, not buried in code. Change what your charity treats as claimable without waiting for a release or raising a ticket.
Every change to every record is recorded — who, when and why. When HMRC or a trustee asks how a figure was reached, the answer is one click away rather than a week of spreadsheet archaeology.
No. Cascade is not a CRM and is not trying to become one. Your CRM stays where it is and keeps doing what it does. Cascade takes the supporter and donation data you already hold and builds one canonical supporter record and one canonical donation record on top of it.
Gift Aid Hub, Analytics, Smart View, Media Hub, Actions and Harmony all work on that same record. There is no sync between them, because there is nothing to sync.
That is the normal case, not the awkward one. Cascade builds its canonical supporter and donation records from whatever you can export — a CRM, a finance system, a giving platform, or spreadsheets.
The point of 2.0 is what happens once it lands. It stops being several data sets and becomes one governed model: one definition of a supporter, one of a gift, one of Gift Aid eligibility, used by every product. That is why the figure on your dashboard, the figure in your board pack and the figure Harmony gives you agree. Before 2.0 each was worked out separately and they drifted.
Transfers run automatically on a cadence we agree with you, rather than someone remembering to run an export.
You do. Cascade 2.0 runs a declarative rules engine that is configured per charity. It ships with the HMRC defaults already in it — benefit cap, connected persons, sponsored event splits, GASDS caps, community building rules — and your own rules sit on top of those.
“This regular giving product is never claimable” or “this restricted fund needs manager sign-off” is a setting you change, not a support ticket and not a software release. In 1.0 those rules lived in our code and a change meant waiting for us.
You see it line by line, in English. Rejects and queries land in a reconciliation view with the HMRC reason code translated and a suggested fix against it — bad NI number, missing address, declaration expired at the time of the donation, supporter over the benefit cap.
One click turns a rejected line into an Action with the fix already scaffolded and somebody’s name against it. The retry and repair loop is now automatic; it used to be a support ticket to us.
Not in the path that produces your numbers. The reporting engine behind Cascade and Harmony is deterministic — no model sits between your data and the figure on the screen — and every chart carries a receipt showing exactly where its figures came from. Because it is the same engine everywhere, a report cannot disagree with itself across products.
Harmony is the part that takes a plain-English question, and it gives you the answer with the working behind it rather than a number to take on trust. The genuinely predictive things — suggested next steps on an Action, natural-language querying inside Analytics — are on the roadmap. We will tell you when they land, not before.
The record. Cascade 2.0 audits every change to every record, not just claims — who changed it, when, and why. A submitted claim keeps its HMRC receipt ID in the app rather than in somebody’s inbox.
Work done on a supporter keeps its Action: who picked it up, every state it moved through, and the reason code it was closed with from your own taxonomy. You cannot close an Action without one. That is the difference between answering “why was this donation excluded” in a click and reconstructing a decision somebody made eighteen months ago.
